DEV475 Mastering Object-Oriented Analysis and Design with UML ...
Share Embed Flag
Download ePaper

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

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

crnarupa.singidunum.ac.rs
from crnarupa.singidunum.ac.rs More from this publisher
12.07.2015 Views

DEV475 Mastering Object-Oriented Analysis and Design with UMLDistribute Use-Case Behavior to ClassesUse-Case Analysis Steps• Supplement the Use-Case Descriptions• For each Use-Case Realization• Find Classes from Use-Case Behavior• Distribute Use-Case Behavior to Classes• For each resulting analysis class• Describe Responsibilities• Describe Attributes and Associations• Qualify Analysis Mechanisms• Unify Analysis Classes• CheckpointsMastering Object Oriented Analysis and Design with UMLCopyright © 2003 Rational Software, all rights reserved 26Now that we have identified the candidate analysis classes, we need to allocate theresponsibilities of the use case to the analysis classes and model this allocation bydescribing the way the class instances collaborate to perform the use case in Use-Case Realization.The purpose of “Distribute Use-Case Behavior to Classes” is to:• Express the use-case behavior in terms of collaborating analysis classes• Determine the responsibilities of analysis classes6 - 26

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

<strong>DEV475</strong> <strong>Mastering</strong> <strong>Object</strong>-<strong>Oriented</strong> <strong>Analysis</strong> <strong>and</strong> <strong>Design</strong> <strong>with</strong> <strong>UML</strong>Distribute Use-Case Behavior to ClassesUse-Case <strong>Analysis</strong> Steps• Supplement the Use-Case Descriptions• For each Use-Case Realization• Find Classes from Use-Case Behavior• Distribute Use-Case Behavior to Classes• For each resulting analysis class• Describe Responsibilities• Describe Attributes <strong>and</strong> Associations• Qualify <strong>Analysis</strong> Mechanisms• Unify <strong>Analysis</strong> Classes• Checkpoints<strong>Mastering</strong> <strong>Object</strong> <strong>Oriented</strong> <strong>Analysis</strong> <strong>and</strong> <strong>Design</strong> <strong>with</strong> <strong>UML</strong>Copyright © 2003 Rational Software, all rights reserved 26Now that we have identified the c<strong>and</strong>idate analysis classes, we need to allocate theresponsibilities of the use case to the analysis classes <strong>and</strong> model this allocation bydescribing the way the class instances collaborate to perform the use case in Use-Case Realization.The purpose of “Distribute Use-Case Behavior to Classes” is to:• Express the use-case behavior in terms of collaborating analysis classes• Determine the responsibilities of analysis classes6 - 26

logo

products

Resources

Company

Terms of service
Privacy policy
Cookie policy
Cookie settings
Imprint
Change language
Made with love in Switzerland
© 2024 Yumpu.com all rights reserved

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!