Hi Stefan,
I am planning to do exactly what you mention below. Have one model and different team
members work on different parts of the model. After discussions with some Andromda
experts (Chad and Walter) and also based on input from MagicDraw engineers, my
conclusion was that you can use Magic Draw's import/export module capability to split
up the model. Each module can then be modified independently by different team
members. In this case you don't need the Team Server component of MagicDraw. I think
you would need the Team Server component only if different people wanted to modify the
same part of the model simultaneously. That may not be a good practice anyway.
But I must add that I have not yet implemented this process myself. When I do I can
publish my experiences.
Regards,
Sunondo
-----Original Message-----
From: Stefan Scheidt [mailto:[EMAIL PROTECTED]
Sent: Tue 9/7/2004 10:10 PM
To: [EMAIL PROTECTED]
Cc:
Subject: [Andromda-user] Teamwork Best Practices
Hi,
can anyone give some best practices on how to work with AndroMDA in teams,
especially regarding the modelling part? How can and should one splitt the model into
peaces? Any experiences using MagicDraw teamserver? Or can you recommend any other UML
tool that works fine with AndroMDA and has good team support?
Any infos on this topic would be very helpful!
Thanks in advance,
Stefan.
_______________________________________________________
WEB.DE Video-Mail - Sagen Sie mehr mit bewegten Bildern
Informationen unter: http://freemail.web.de/?mc=021199
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
_______________________________________________
Andromda-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/andromda-user
N¬HS^µéX¬²š'²ŠÞu¼žnZ ‰Å®K!¢‘QBZ½¡'µêé®+ 'auëÞŠ^®Ú(–Á·*.úÞyÊ)ÊÁžlº
‰Å®K!¢Ÿ5¶‡ZÊm§ÿÚvÊ,vw(›ö‰
