DEV475 Mastering Object-Oriented Analysis and Design with UML ...

Module 6 - Use-Case AnalysisDistribute Use-Case Behavior to ClassesDistribute Use-Case Behavior to Classes• For each use-case flow of events:• Identify analysis classes• Allocate use-case responsibilities to analysisclasses• Model analysis class interactions in InteractiondiagramsSequence DiagramsCollaboration DiagramsUse CaseUse-Case RealizationMastering Object Oriented Analysis and Design with UMLCopyright © 2003 Rational Software, all rights reserved 27You can identify analysis classes responsible for the required behavior by steppingthrough the flow of events of the use case. In the previous step, we outlined someclasses. Now it is time to see exactly where they are applied in the use-case flow ofevents.In addition to the identified analysis classes, the Interaction diagram should showinteractions of the system with its actors. The interactions should begin with an actor,since an actor always invokes the use case. If you have several actor instances in thesame diagram, try keeping them in the periphery of that diagram.Interactions between actors should not be modeled. By definition, actors are external,and are out of scope of the system being developed. Thus, you do not includeinteractions between actors in your system model. If you need to model interactionsbetween entities that are external to the system that you are developing (for example,the interactions between a customer and an order agent for an order-processingsystem), those interactions are best included in a Business Model that drives theSystem Model.Guidelines for how to distribute behavior to classes are described on the next slide.6 - 27