For our design efforts we are wanting to maintain the Analysis & Design
versions of classes in the same model. For us, this makes it easier to
show the evolution from Analysis to Design.
In cases where there is a direct 1:1 relationship between an analysis
version and design version of the same class, how did you handle namespace
collisions? Or did you?
How do you handle concurrency, where multiple modelers need to modify the
design version of the same class at the same time.
One way I've seen this done to handle namespace between the analysis and
design versions of a class is:
Customer_A // Analysis Version
Customer_D // Design Version
What are your thoughts?
Eric Manley
Enterprise Rent-A-Car
Rental Application Development
Phone: 314.512.5321
Email: [EMAIL PROTECTED]
************************************************************************
* Rose Forum is a public venue for ideas and discussions.
* For technical support, visit http://www.rational.com/support
*
* Post or Reply to: [EMAIL PROTECTED]
* Subscription Requests: [EMAIL PROTECTED]
* Archive of messages:
* http://www.rational.com/support/usergroups/rose/rose_forum.jsp
* Other Requests: [EMAIL PROTECTED]
*
* To unsubscribe from the list, please send email
* To: [EMAIL PROTECTED]
* Subject: <BLANK>
* Body: unsubscribe rose_forum
*************************************************************************
