(ROSE) Rose Modelling Steps to follow...

[Martin Paul]

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