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 UMLCheckpoints: Use-Case RealizationsCheckpoints: Use-Case Realizations• Have all the main and/or sub-flowsbeen handled, including exceptionalcases?• Have all the required objects beenfound?• Has all behavior been unambiguouslydistributed to the participating objects?• Has behavior been distributed to theright objects?• Where there are several Interactiondiagrams, are their relationships clearand consistent?Mastering Object Oriented Analysis and Design with UMLCopyright © 2003 Rational Software, all rights reserved 62The above checkpoints for the Use-Case Realizations might be useful.Note: All checkpoints should be evaluated with regards to the use cases beingdeveloped for the current iteration.The objects participating in a Use-Case Realization should be able to perform all ofthe behavior of the use case.If there are several Interaction diagrams for the Use-Case Realization, it is importantthat it is easy to understand which Interaction diagrams relate to which flow ofevents. Make sure that it is clear from the flow of events description how thediagrams are related to each other.6 - 62

Module 6 - Use-Case AnalysisReviewReview: Use-Case Analysis• What is the purpose of Use-Case Analysis?• What is an analysis class? Name anddescribe the three analysis stereotypes.• What is a Use-Case Realization?• Describe some considerationswhen allocating responsibilitiesto analysis classes.• How many Interaction diagramsshould be produced duringUse-Case Analysis?Mastering Object Oriented Analysis and Design with UMLCopyright © 2003 Rational Software, all rights reserved 636 - 63

<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>Checkpoints: Use-Case RealizationsCheckpoints: Use-Case Realizations• Have all the main <strong>and</strong>/or sub-flowsbeen h<strong>and</strong>led, including exceptionalcases?• Have all the required objects beenfound?• Has all behavior been unambiguouslydistributed to the participating objects?• Has behavior been distributed to theright objects?• Where there are several Interactiondiagrams, are their relationships clear<strong>and</strong> consistent?<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 62The above checkpoints for the Use-Case Realizations might be useful.Note: All checkpoints should be evaluated <strong>with</strong> regards to the use cases beingdeveloped for the current iteration.The objects participating in a Use-Case Realization should be able to perform all ofthe behavior of the use case.If there are several Interaction diagrams for the Use-Case Realization, it is importantthat it is easy to underst<strong>and</strong> which Interaction diagrams relate to which flow ofevents. Make sure that it is clear from the flow of events description how thediagrams are related to each other.6 - 62

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

Saved successfully!

Ooh no, something went wrong!