Best way to create a "tree" of linked mo

[JP]

Hi everybody,

I have a large system to model and therefore I need to manage and link a large number of various size models representing (ultimately) the smallest element.

It is a tree like structure where the nodes would be models containig models. The intermediate nodes of the tree are models with diagrams in which there are "links" to models belonging to a lower level in the tree.

In fact, in my mind, only the leaves of the tree do not contain other models.

And, of course, I would like to perform version control of each of these nodes (using CVS).

Would someone know or have an idea about what would be the best way to achieve this representation ?

I know it is possible to manage packages in configuration using the "package control" feature (contextual menu) then "version control". and saving the package using XMI (which version ?)

But this approach, apparently, does not give good results when you save a diagram whith embedded links to other models ! (you simply "lose" the link !). Also, in some cases, there are layout problems. Maybe this is simply a problem with the version of XMI (which should be higher than 1.0...)

I would be glad to hear you guys, because I believe this problem is a fairly common one and I am certain that many of you already solved it.

Many Thanks.
JP

[TrtnJohn]

I am not seeing the same problems you describe using source control.  (We use SourceSafe).  External links are not getting lost.  But, we did create a lot of individual XML files for each package layer we have.  And, I stayed away from putting nested packages in seperate source control files.  (Mainly because I couldn't see how to get it to work).   Instead we have a lot of packages that all have a seperate XML file that goes with it.  We split the system such that we could decide how low to go inside the tree so each package could be individually checked out or, in some cases, an entire sub-tree could be checked out.  But, once we put a package under source control, that package included all it's sub packages.  If we want to put any child package into a seperate source control we had to reorganize or remove the source control for the parent.

[Martin Terreni]

I think you better have an overall package for all the tree to save in a XMI file and one for each final package (containing the actual model).
You can reflect the tree in your project by putting all models embedded by another model right below it in browser tree, thus when importing an expoting the tree you will do it as a hole for the tree not loosing any thing, and by exporting final packages with actual models your developers can work on it.