TeamWork

This section is composed by:

1. Multiple models consolidation
2. TeamWork solutions
1. Java Code synchronization
2. Diagrams creation with no Java code
3. Team work example using SVN inside Eclipse

EclipseUML is fully integrated with SVN and CVS Eclipse solutions.
You can also use EclipseUML with any other SCC tool but you will not be able to use the model compare feature before the commit.

It is important when you decide to start a project to select which team mode to use.
You can decide to work in a team by selecting :

• either multiple models approach (see more information...)
• or use immediately a teamWork solution

It is not recommended to:

• start a project using different projects on each desktop, even if the project have the same name and then try to merge these models. This is a dynamic Id creation limitation. This will not work !!
  
• use txt editor to manipulate the .uml model.
  

1. Multiple models approach limitations

You can model different pieces of the architecture and then just unify your models at the end of the modeling stage. This is an  easy way to work. Please note that the unify model is not incremental. It means that once models have been unified, then you can not not merge your single model with the unified model if you change it after.
The only solution is to unify again all models inside another single model. This is a static approach which is used if the modeling project is finished. You can also from this single unify model use team work for the second stage of modeling.
See multiple models inside a larger model in the picture below:




2. TeamWork solutions

You first need to create a single project on SVN or CVS.
Then to ask each member of your team to use this server and commit any change they make.
Finally you need to define each member commit permissions at the server level and not to try to do this administration in the EclipseUML tool.

When working in a team you should consider two options with EclipseUML:

• use eclipseuml live java code synchronization
• do not use java code synchronization

2.1 Java Code synchronization

If you use this live code and model option with your class or sequence diagrams then after each change you need to commit the following files:

• java code
• graphical diagram (e.g. .ucd, .usd, .uud etc..file)
• model file (e.g. .uml file)

2.2 Diagrams creation with no Java code

If you don't use the live code and model synchronization then after each change you need to commit the following files:

• graphical diagram (e.g. .ucd, .usd, .uud etc..file)
• model file (e.g. .uml file)

3. Team work example using SVN inside Eclipse


This is an example of using EclipseUML 2008 with SVN and Eclipse.
If you want for example to know what is the stage of your code compare with other commits.
Click on the Project inside the Package Explorer > Team > Show Resource History.