RE: (ROSE) Rose Modelling Steps to follow...

[Sekhar, Chandra (Melbourne)]

Hi,   As you have usecases, actors identified, it will be better to draw a Business Domain Model (BDM), this process involves identifying raw business classes/objects (Bank, Financial Institution, Account, Customer etc...), then draw a sequence diagram between these objects to derive at different scenarios defined in usecases (take complex scenarios for simplicity).  This sequence diagram will help in identifying more well defined objects/classes.  This will link usecases and high level design and helps to track back whether all requirements are understood.  Also BDM helps in identifying Entities at a later point of design.  This is my perspective of going ahead.   Rgds, Always AKNR AKNR Chandra Sekhar ANZ IT, CMM Level 5 Company * [EMAIL PROTECTED] ( +61(03) 9658 1151 This e-mail and any attachments to it (the "Communication") is confidential and is for the use only of the intended recipient. The Communication may contain copyright material of Australia and New Zealand Banking Group Limited ABN 11 005 357 522 ("ANZ"), or any of its related entities or of third parties. If you are not the intended recipient of the Communication, please notify the sender immediately by return e-mail, delete the Communication, and do not read, copy, print, retransmit, store or act in reliance on the Communication. Any views expressed in the Communication are those of the individual sender only, unless expressly stated to be those of ANZ. ANZ does not guarantee the integrity of the Communication, or that it is free from errors, viruses or interference. -----Original Message----- From: Martin Paul [mailto:[EMAIL PROTECTED]] Sent: Saturday, 1 February 2003 4:23 PM To: [EMAIL PROTECTED] Subject: (ROSE) Rose Modelling Steps to follow... Hi all,    I have my usecase document like vision and other usecasedocuments ready and usecase diagrams with all relations with actors ready. We also know how to map them to requistpro features and related. What do we do next? 1)Do we startoff with sequence/colaboration diagrams and activity diagrams.  Do we include them in usecase view or Logical View? Should not classes be identified before sequence digram.? 2)How are the usecases identfied maps to usecase realizations in logical view?   How do we link the different Views in the model?   What all diagrams/artifacts has to included in which all views.   3)Which all diagrams have effects on code generation. While designing classes keeping in mind Com+ Vb ? How and why should i make use of interface inheritance? Can anyone  provide with hints and tips on steps to be followed.! Our application is a COM+ backoffice financial application using VB/SQL. We have clearcase and testing tools being used efficently here. but regarding rose we have some idea on datamodelling and usecasemodelling. but round trip engineering is not happening rather we used to use rose as a documentation tool.I did be gratefull if u do help me regarding this? No helps could be rose modelling steps to be followed is found anywhere.   Martin