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 UMLReviewReview: Architectural Analysis• What is the purpose of Architectural Analysis?• What is a package?• What are analysis mechanisms? Give examples.• What key abstractions are identified duringArchitectural Analysis? Why are they identifiedhere?• What is a layered architecture? Give examples oftypical layers.Mastering Object Oriented Analysis and Design with UMLCopyright © 2003 Rational Software, all rights reserved 385 - 38

Module 5 - Architectural AnalysisExercise: Architectural AnalysisExercise: Architectural Analysis• Given the following:• Some results from the Requirementsdiscipline:• Problem statement• Use-Case Model main diagram• Glossary• Some architectural decisions:• (textually) The upper-levelarchitectural layers and theirdependencies(continued)Mastering Object Oriented Analysis and Design with UMLCopyright © 2003 Rational Software, all rights reserved 39The goal of this exercise is to jump-start analysis.References to givens:• Requirements Results: Payroll Requirements Document• Architectural Decisions: Payroll Architecture Handbook, Logical View,Architectural Analysis section.Note: This exercise has been tightly scoped to emphasize the Analysis and Designmodeling concepts and reduce the emphasis on architectural issues. Thus, much ofthe architecture has been provided to you, rather than asking you to provide it as partof the exercise. Remember, this is not an architecture course.5 - 39

Module 5 - Architectural <strong>Analysis</strong>Exercise: Architectural <strong>Analysis</strong>Exercise: Architectural <strong>Analysis</strong>• Given the following:• Some results from the Requirementsdiscipline:• Problem statement• Use-Case Model main diagram• Glossary• Some architectural decisions:• (textually) The upper-levelarchitectural layers <strong>and</strong> theirdependencies(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 39The goal of this exercise is to jump-start analysis.References to givens:• Requirements Results: Payroll Requirements Document• Architectural Decisions: Payroll Architecture H<strong>and</strong>book, Logical View,Architectural <strong>Analysis</strong> section.Note: This exercise has been tightly scoped to emphasize the <strong>Analysis</strong> <strong>and</strong> <strong>Design</strong>modeling concepts <strong>and</strong> reduce the emphasis on architectural issues. Thus, much ofthe architecture has been provided to you, rather than asking you to provide it as partof the exercise. Remember, this is not an architecture course.5 - 39

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

Saved successfully!

Ooh no, something went wrong!