Art, If I understand you correctly you do not want to lose any of the information that you had in iteration #1 when working on iteration #2 - correct? If so then you need to employ some kind of version control to save iteration #1 in it's entirety before editing it again. You can get that through the use of ClearCase, SourceSafe, etc. or, primitively by physically copying the .mdl file to a new directory and working on it there. Controlled units may help you as well. This can reduce the number/size of packages you need to worry about versioning. You can put each controlled unit into source control for maximum flexibility. You can create issues with missing or "hanging" associations if you're not careful about how you delete classes from the model. You can use Show Access Violations and Check Model to help resolve those issues. Jordan R. Janis Director of Product Development Sorceron, Inc. T: 212-620-0021 F: 212-620-7986 E: [EMAIL PROTECTED] URL: www.sorceron.com ***************************************NOTE********************************* ********** The information contained in this email message is intended only for use of the individual or entity named above. If the reader of this message is not the intended recipient, or the employee or agent responsible to deliver it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please immediately notify us by telephone (212-620-0021). Thank you. **************************************************************************** ************* -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of [EMAIL PROTECTED] Sent: Wednesday, November 08, 2000 1:35 PM To: [EMAIL PROTECTED] Subject: (ROSE) versioning models Afternoon Folks, I've got my Rose model appropriately packaged off by business domains and I'm merrily going along doing OOA with my domain experts. As we're going thru numerous iterations refining a class model adding more classes, associations, etc. as we learn more about the business requirements, I've been doing a copy-and-paste from version 1 to a new version 2 of a model to segregate what we learn from one iteration to the next. I've just realised that I'm accumulating a pile of junk!! Classes, attributes and/or associations which were good in iteration #1 stay around as I keep adding new things to the model. I'm guessing I'm not using the versioning facility of Rose2000 correctly. Can anyone recommend how I can manage in a fast iterating environment? Thanks Art Roberts Manager - Business Systems & Methodology SoftChoice Corp [EMAIL PROTECTED] 1-416-588-9002 x2321 ************************************************************************ * Rose Forum is a public venue for ideas and discussions. * For technical support, visit http://www.rational.com/support * * Admin.Subscription Requests: [EMAIL PROTECTED] * Archive of messages: http://www.rational.com/products/rose/usergroups/rose_forum.jtmpl * Other Requests: [EMAIL PROTECTED] * * To unsubscribe from the list, please send email * * To: [EMAIL PROTECTED] * Subject:<BLANK> * Body: unsubscribe rose_forum * ************************************************************************* ************************************************************************ * Rose Forum is a public venue for ideas and discussions. * For technical support, visit http://www.rational.com/support * * Admin.Subscription Requests: [EMAIL PROTECTED] * Archive of messages: http://www.rational.com/products/rose/usergroups/rose_forum.jtmpl * Other Requests: [EMAIL PROTECTED] * * To unsubscribe from the list, please send email * * To: [EMAIL PROTECTED] * Subject:<BLANK> * Body: unsubscribe rose_forum * *************************************************************************
