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 ...
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
- Page 154 and 155: DEV475 Mastering Object-Oriented An
- Page 156 and 157: DEV475 Mastering Object-Oriented An
- Page 158 and 159: DEV475 Mastering Object-Oriented An
- Page 160 and 161: DEV475 Mastering Object-Oriented An
- Page 162 and 163: DEV475 Mastering Object-Oriented An
- Page 164 and 165: DEV475 Mastering Object-Oriented An
- Page 166 and 167: DEV475 Mastering Object-Oriented An
- Page 168 and 169: DEV475 Mastering Object-Oriented An
- Page 170 and 171: DEV475 Mastering Object-Oriented An
- Page 172 and 173: DEV475 Mastering Object-Oriented An
- Page 174 and 175: DEV475 Mastering Object-Oriented An
- Page 176 and 177: DEV475 Mastering Object-Oriented An
- Page 178 and 179: DEV475 Mastering Object-Oriented An
- Page 180 and 181: DEV475 Mastering Object-Oriented An
- Page 182 and 183: DEV475 Mastering Object-Oriented An
- Page 184 and 185: DEV475 Mastering Object-Oriented An
- Page 186 and 187: DEV475 Mastering Object-Oriented An
- Page 188 and 189: DEV475 Mastering Object-Oriented An
- Page 190 and 191: DEV475 Mastering Object-Oriented An
- Page 192 and 193: DEV475 Mastering Object-Oriented An
- Page 194 and 195: DEV475 Mastering Object-Oriented An
- Page 196 and 197: DEV475 Mastering Object-Oriented An
- Page 198 and 199: DEV475 Mastering Object-Oriented An
- Page 200 and 201: DEV475 Mastering Object-Oriented An
- Page 202 and 203: DEV475 Mastering Object-Oriented An
- Page 206 and 207: DEV475 Mastering Object-Oriented An
- Page 208 and 209: DEV475 Mastering Object-Oriented An
- Page 210 and 211: DEV475 Mastering Object-Oriented An
- Page 212 and 213: DEV475 Mastering Object-Oriented An
- Page 214 and 215: DEV475 Mastering Object-Oriented An
- Page 216 and 217: DEV475 Mastering Object-Oriented An
- Page 218 and 219: DEV475 Mastering Object-Oriented An
- Page 220 and 221: DEV475 Mastering Object-Oriented An
- Page 222 and 223: DEV475 Mastering Object-Oriented An
- Page 224 and 225: DEV475 Mastering Object-Oriented An
- Page 226 and 227: DEV475 Mastering Object-Oriented An
- Page 228 and 229: DEV475 Mastering Object-Oriented An
- Page 230 and 231: DEV475 Mastering Object-Oriented An
- Page 232 and 233: DEV475 Mastering Object-Oriented An
- Page 234 and 235: DEV475 Mastering Object-Oriented An
- Page 236 and 237: DEV475 Mastering Object-Oriented An
- Page 238 and 239: DEV475 Mastering Object-Oriented An
- Page 240 and 241: DEV475 Mastering Object-Oriented An
- Page 242 and 243: DEV475 Mastering Object-Oriented An
- Page 244 and 245: DEV475 Mastering Object-Oriented An
- Page 246 and 247: DEV475 Mastering Object-Oriented An
- Page 248 and 249: DEV475 Mastering Object-Oriented An
- Page 250 and 251: DEV475 Mastering Object-Oriented An
- Page 252 and 253: DEV475 Mastering Object-Oriented An
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