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 UMLCheckpointsCheckpoints• General• Is the package partitioning andlayering done in a logicallyconsistent way?• Have the necessary analysismechanisms been identified?• Packages• Have we provided a comprehensivepicture of the services of thepackages in upper-level layers?(continued)Mastering Object Oriented Analysis and Design with UMLCopyright © 2003 Rational Software, all rights reserved 36The next few slides contains the key things a designer would look for when assessingthe results of Architectural Analysis. An architect would have a more detailed list.A well-structured architecture encompasses a set of classes, typically organized intomultiple hierarchiesNote: At this point, some of the packages/layers may not contain any classes, and thatis okay. More classes will be identified over time, starting in the next activity, Use-Case Analysis.5 - 36

Module 5 - Architectural AnalysisCheckpoints (cont.)Checkpoints (cont.)• Classes• Have the key entity classes andtheir relationships been identifiedand accurately modeled?• Does the name of each class clearlyreflect the role it plays?• Are the key abstractions/classesand their relationships consistentwith the Business Model, DomainModel, Requirements, Glossary,etc.?Mastering Object Oriented Analysis and Design with UMLCopyright © 2003 Rational Software, all rights reserved 37A well-structured class provides a crisp abstraction of something drawn from thevocabulary of the problem domain or the solution domain.5 - 37

<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>CheckpointsCheckpoints• General• Is the package partitioning <strong>and</strong>layering done in a logicallyconsistent way?• Have the necessary analysismechanisms been identified?• Packages• Have we provided a comprehensivepicture of the services of thepackages in upper-level layers?(continued)<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 36The next few slides contains the key things a designer would look for when assessingthe results of Architectural <strong>Analysis</strong>. An architect would have a more detailed list.A well-structured architecture encompasses a set of classes, typically organized intomultiple hierarchiesNote: At this point, some of the packages/layers may not contain any classes, <strong>and</strong> thatis okay. More classes will be identified over time, starting in the next activity, Use-Case <strong>Analysis</strong>.5 - 36

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!