Frank asks:
Do you create a UCR for each potential flow thru the UC? That is, do you have a UCR for the main flow, another UCR for an alternative flow (perhaps an error condition), etc... This would also give multiple UCRs per UC. Your approach still seems to handle this nicely. Todd Answers: No. You are describing a scenario, not a use case realization. A single use case realization includes the documentation for the entire collection of scenarios that the actors can perform while executing the use case. The total documentation for a UCR commonly will include: - One (or more!) object interaction diagrams that illustrate how the system internals interact during each scenario - A (single!) class diagram, what we call the View of Participating Classes (VOPC) diagram, that shows the relationships between ALL the classes that are involved in ANY of the scenarios. Well, this might actually be taking the concept too far. If I am using subsystem-based development, I most likely would stop at the subsystem boundaries. That is, the UCR interaction diagrams wouldn't go deeper than the subsystem interfaces, and the VOPC wouldn't show the classes that implement the interface operations. The VOPC is a very powerful diagram. In our approach to iterative systems development, we commonly determine the functionality to be implemented during an iteration by: - Identifying the risks we wish to retire during that iteration, then - Identifying the use cases that will make us face those risks when we implement them. Let's say that a risk is architectural in nature. We select a use case that WE THINK will force us to design and implement that piece of the architecture. During system design, we can use the VOPC to confirm that we are, indeed, touching the pieces of the system's innards that we expected, or we can see that we AREN'T. If we catch this faux pas early enough, we might still have time to touch our risky piece of the system by revisiting the project plan and implementing a different use case. ******************************************************** R a t i o n a l the software development company(tm) Todd Dunnavant Technical Lead, IBM Global Account Team Office Phone #: (281) 431-8751 Fax Phone #: (281) 431-8791 E-mail address: [EMAIL PROTECTED] < mailto:[EMAIL PROTECTED]> Rational's Mission: "To ensure the success of Customers who depend on software development and deployment." ******************************************************** -----Original Message----- From: Frank J. Lagattuta [mailto:[EMAIL PROTECTED]] Sent: Tuesday, August 13, 2002 5:52 PM To: 'Dunnavant, Todd'; [EMAIL PROTECTED] Subject: RE: (ROSE) From Use Case to Use Case Realiztion Good info, thanks. One question below... > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]] On Behalf Of Dunnavant, Todd > Sent: Tuesday, August 13, 2002 3:30 PM > To: [EMAIL PROTECTED] > Subject: RE: (ROSE) From Use Case to Use Case Realiztion > > The use case realizations are captured in the Logical View. > I commonly organize the packages for a simple system as follows: > > Logical View > Design Model > Use Case Realizations > Separate package for each UCR. > > Under each UCR package, I have a use case stereotyped as a > UCR. The activity diagrams, sequence diagrams, and View of > Participating Classes diagram are attached to the UCR icon. > > Under each UCR package, I also have a use case diagram (or a > class diagram, if I use a RoseScript to generate the UCR > hierarchy). This diagram shows the UCR icon, the icon for > the UC it realizes, and realize relations from the UCR to the UC. > > Here is a question -- what do you do if you have MULTIPLE > UCRs realizing the same UC? This can occur if a design team > needs to work with multiple design concepts. Do you create a UCR for each potential flow thru the UC? That is, do you have a UCR for the main flow, another UCR for an alternative flow (perhaps an error condition), etc... This would also give multiple UCRs per UC. Your approach still seems to handle this nicely. -Frank ************************************************************************ * Rose Forum is a public venue for ideas and discussions. * For technical support, visit http://www.rational.com/support * * Post or Reply to: [EMAIL PROTECTED] * 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 *************************************************************************
