Hi Paolo,
Even if I separate the project using the XMI Import/Export, how can you manage each class element into the appropriate version?
For example, in the same package there is a Class in version 2 and a another Class in version 5! How could I replect it into EA + Version Control Tool?
Regards,
Carol
Carol,
I said that you had create packages at the correct level of granularity to suit your needs. It is NOT the absolute versions of the classes that matter but the way in which those items that are dependent upon them react to changes in one class or the other.
You may need to review your design for the
correct level of cohesion and coupling.We have classes evolving at different rates in the same package, but because of our design, the impact is manageable. If you aren't able to separate out the packages into manageable groups of classes, then that may, in fact, be your problem.
Our system is made up of a number of subsystems, which contain assemblies, components and sub components. They each (and the classes within them) evolve at different rates, but because of the cohesiveness and coupling of the designs, we limit the impact on the other parts.
Each project (Real project NOT EA project) gets its subset of the appropriate containers at the appropriate versions. Some packages are in ALL projects, some are in Some projects, and others are project specific. In your case, if you substitute Product for Project, you should be able to make the same statements.
It is not easy to manage, but it is manageable.
Does that help?
Paolo
