Team Working using EA

[neilrenaud]

Here at work we have the coporate version of EA and I am trying to set up a way for a whole team to work on a UML document at once.

All people will be working on different diagrams at any one time however I'm worried that if 2 people created a class with the same name that this would cause problems.

What is the best way to do team working in EA?

I have been looking at setting up the DBMS stuff but it seems to imply that a user has to import and export the diagrams and I'd prefer dynamic updating if at all possible.

Any suggestions/comments?

[thomaskilian]

You should have one person to coordinate all work (you have one already, do you?). This person will be responsible to allow/disallow others on working with dedicated packages. There is probably no way to work in "self organizing" groups  :-/

[Bruno.Cossi]

Hi,

working with a DBMS repository doesn't mean that everyone has to expot/imort the diagrams. From users' prospective, working with the repository and with the .EAP file is exactly the same.
You will likely want to structure your model in such a way that each user/team works within a distinct set of packages.
Locking becomes a must, preventing the users from overwriting each other's work.
Therr is no automated way to prevent people from creating duplicate elements, it's all about the organization. Should that happen though, it's not too hard to fix.

Hope this helps!

Bruno

Here at work we have the coporate version of EA and I am trying to set up a way for a whole team to work on a UML document at once.

All people will be working on different diagrams at any one time however I'm worried that if 2 people created a class with the same name that this would cause problems.

What is the best way to do team working in EA?

I have been looking at setting up the DBMS stuff but it seems to imply that a user has to import and export the diagrams and I'd prefer dynamic updating if at all possible.

Any suggestions/comments?