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 UMLUse-Case Analysis OverviewUse-Case Analysis OverviewGlossaryProject SpecificGuidelinesSoftwareArchitectureDocumentUse-Case RealizationSupplementarySpecificationsUse-CaseAnalysisAnalysis ModelUse-Case ModelAnalysis ClassesMastering Object Oriented Analysis and Design with UMLCopyright © 2003 Rational Software, all rights reserved 4Use-Case Analysis is performed by the designer, once per iteration per Use-CaseRealization. What event flows, and therefore what Use-Case Realizations you aregoing to work on during the current iteration are defined prior to the start of Use-Case Analysis in Architectural Analysis.Purpose• To identify the classes that perform a use case’s flow of events• To distribute the use case behavior to those classes, using Use-Case Realizations• To identify the responsibilities, attributes and associations of the classes• To note the usage of architectural mechanismsInput Artifacts• Glossary• Supplementary Specifications• Use-Case• Use-Case Model• Use-Case Realization• Software Architecture Document• Analysis Class• Analysis Model• Project Specific GuidelinesResulting Artifacts• Analysis Classes• Analysis Model• Use-Case RealizationsNote: We will not be developing a separate Analysis Model in this course.6 - 4

Module 6 - Use-Case AnalysisUse-Case Analysis StepsUse-Case Analysis Steps• Supplement the Use-Case Description• 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 5The above are the major steps of the Use-Case Analysis activity.First we must review the use-case descriptions developed in the Requirementsdiscipline. Chances are, they will need some enhancements to include enough detailto begin developing a model.Next, we study the use-case flow of events, identify analysis classes, and allocate usecaseresponsibilities to the analysis classes. Based on these allocations, and theanalysis class collaborations, we can begin to model the relationships between theidentified analysis classes.Once the use case has been analyzed, we need to take a good look at the identifiedclasses, making sure they are thoroughly documented and identify which analysis andmechanisms they implement.Last, but not least, we need to make sure that our developed Analysis Model isconsistent.6 - 5

<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>Use-Case <strong>Analysis</strong> OverviewUse-Case <strong>Analysis</strong> OverviewGlossaryProject SpecificGuidelinesSoftwareArchitectureDocumentUse-Case RealizationSupplementarySpecificationsUse-Case<strong>Analysis</strong><strong>Analysis</strong> ModelUse-Case Model<strong>Analysis</strong> Classes<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 4Use-Case <strong>Analysis</strong> is performed by the designer, once per iteration per Use-CaseRealization. What event flows, <strong>and</strong> therefore what Use-Case Realizations you aregoing to work on during the current iteration are defined prior to the start of Use-Case <strong>Analysis</strong> in Architectural <strong>Analysis</strong>.Purpose• To identify the classes that perform a use case’s flow of events• To distribute the use case behavior to those classes, using Use-Case Realizations• To identify the responsibilities, attributes <strong>and</strong> associations of the classes• To note the usage of architectural mechanismsInput Artifacts• Glossary• Supplementary Specifications• Use-Case• Use-Case Model• Use-Case Realization• Software Architecture Document• <strong>Analysis</strong> Class• <strong>Analysis</strong> Model• Project Specific GuidelinesResulting Artifacts• <strong>Analysis</strong> Classes• <strong>Analysis</strong> Model• Use-Case RealizationsNote: We will not be developing a separate <strong>Analysis</strong> Model in this course.6 - 4

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!