Alfonso,
Your Design Model should be related to your Analysis Model in much the same way as Use Case to Analysis. Design artifacts should realise Analysis artifacts, e.g design classes realise analysis classes and the corresponding Design sequence diagrams should map from the Analysis sequence diagrams. The Design Model should also have a tracability diagram showing these realisation mappings. Thus, you should have tracability all the way through from requirements artifacts to design artifacts (via analysis artifacts). Just as you will go back and refine your Use Case diagrams (hopefully with the agreement of your client) based on decisions you make during analysis, you will also go back and refine your Analysis artifacts based on decisions you make during your design. However, don't make the mistake of having low level details in your Analysis artifacts. One abstract message on an analysis sequence will (usually) be mapped to a flow of messages on a design sequence - e.g. in analysis you might have a message between User <<actor>> and Login Frame <<boundary class>> like '1. Enter user details'. This message would map to a design sequence like <user to loginFrame> 1. Enter username; <loginFrame to loginController> 1.1 setUserName( username ); <loginController to userDB> 1.1.1 find( userTable, username) ... etc. So, keep your Analysis Model distinct from your Design model. And keep all models up to date - make sure the mapping from requirements to implementation is fully tracable. Regards, Stephen. > -----Original Message----- > From: Alfonso Moreno Rey [mailto:[EMAIL PROTECTED]] > Sent: 05 October 2001 09:51 > To: [EMAIL PROTECTED] > Subject: RE: Stephen (ROSE) realizing the use cases and Test model > > > > Hi all, > I undestand from Stephen�s explanation that use case > realisations first appear in the > logical view \ Analysis Model. > When evolving from Analysis to Design, do you think it is a > good idea to keep the use case realisations up to date with > all changes, ie replace analysis classes with design classes, > add new messages to the flows as operations are added to > design classes, etc... What would be the consequence of > finishing realisations refinements at the Analysis phase? > > If that is achieved and use case realisations are eventually > kept updated with regard to our latest design model, don�t > they just represent how we expect all Actors to behave when > running the application and how we expect every other > internal class to bahave? Therefore can we consider the > possibility of producing test cases directly from our various > scenarios (use case realisations)? > > Thanks in advance. > > Alfonso > > ************************************************************** > ********** > * 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/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 > * > ************************************************************** > *********** > ************************************************************************ * 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/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 * *************************************************************************
