RE: (ROSE) The best order to make a model

[Picarello, Anthony]

Rick,   Its a mix of what you suggested in your I.E. below... Are you using a software process that will tend to guide your team as to which artifacts to create, and when?  If not, get a process!!   One suggestion:  start with Use Cases and Scenarios.  After that, you have to satisfy the Use Cases by creating Class and Object diagrams, etc.  But it does not, and probably wont be, have to sequential activities.  You'll find yourself working different views of the model, simultaneously.   One thing I have seen in the past: some folks waste lots of time thinking of names for classes, attributes, and operations.   Just pick whatever seems right at that moment... you'll have time to go back an modify them before code generation. ------------------------------------------------- Tony Picarello Engineer Science Applications International Corp. Voice: 407-207-2791 Fax:    407-282-4530 Email: mailto:[EMAIL PROTECTED]     -----Original Message----- From: Rick [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 27, 2001 6:33 AM To: Rose Forum (E-mail) Subject: (ROSE) The best order to make a model Hi, Im making a model in Rose for a project, but this is the first time Im trying to do this exactly right...... (read: able to generate code from the model & make ALL Use Cases for complete documentation)   but to find all the best Classnames, Attributes & Operations.... is there a certain order to work ?   I.E.: First Brainstorming for classnames, then make the model in without attributes/operations .. then make use cases, then make scenarios ... in those scenarios you get to come up with the operations ... etc   how do you usually start a project ?   thnx in advance rick