Gehel,
make sure that you partition your model into parts that have only unidirectional dependencies. As usual in software development, avoid circular dependencies from one module to another and back to itself (A uses B uses C uses D uses A!). This will create an unmaintainable mess. I hope, MagicDraw will also reject such a chain of modules. You need at least MD Standard Edition to work with modules. You can check them into your version control system and maintain it there together with your source code. This makes tagging and release management easier. Divide your model into modules such that separate people work on separate modules. Use the andromda-profile module in each module. Use commonly used modules inside the other modules. And so on... :-) Matthias -- Matthias Bohlen "Consulting that helps project teams to succeed..." Internet: http://www.andromda.com [EMAIL PROTECTED] _________________________________________________________ Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=245#245 Posting to http://forum.andromda.org/ is preferred over posting to the mailing list! ------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click _______________________________________________ Andromda-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/andromda-user
