Version control and linking to locked packages.

[ChrisBD]

We have a project under development that is being worked upon by many project teams. We are using EA with a DBMS repository under ClearCase control.
I'm charged with supporting the Teams in their use of EA.
I am aware that there are problems with EA and shared models under VC and so steps have been taken to split the main model up in such a way that each team can work without affecting another.
I could do with some advice though.
Team A produces component packages that are repeatedly used by other teams. These packages are kept locked by Team A. When a team uses one of these packages and checks in their work the link to the package is lost. I gather that this is because EA records the link in the XMI files for the packages at both ends, but because one is not checked out, when the check-in is made its file is not updated and that end of the link is lost.

Any ideas?

[Geert Bellekens]

Chris,

Do you have a concrete example of one of those losted links?
I thought that there would not be a problem if you take care of the dependencies properly.

So if the ComponentA is used by other teams there should only be links towards this component and not the other way around. (in other words, all arrow of all connectors should point to ComponentA)

There might be an issue with the direction in wich the connector is created as well. I think that it is safest to have ComponentA always as the supplier of a connector.

If you follow these rules you should be ok (in theory)

Geert