sure, what you could do is model a set of use-cases into a specific model and import that model as a module (MagicDraw allows this)
that way different people can work on different modules and check them in CVS without any conflicts the andromda is an example of this, we can keep updating it without disturbing your model (unless of course we remove things on which you depend, such as the datatype package) I use this mechanism to split the model into three parts: presentation (usecase), application (services only) and persistence (entities) -- Wouter Zoons - [EMAIL PROTECTED] http://www.andromda.org/ _________________________________________________________ Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=1909#1909 Posting to http://forum.andromda.org/ is preferred over posting to the mailing list! ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Andromda-user mailing list Andromda-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/andromda-user
