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 UMLDefine the High-Level Organization of SubsystemsArchitectural Analysis Steps• Key Concepts• Define the High-Level Organization ofSubsystems• Identify Analysis mechanisms• Identify Key Abstractions• Create Use-Case Realizations• CheckpointsMastering Object Oriented Analysis and Design with UMLCopyright © 2003 Rational Software, all rights reserved 10Early in the software development lifecycle, it is important to define the modelingconventions that everyone on the project should use. The modeling conventionsensure that the representation of the architecture and design are consistent acrossteams and iterations.5 - 10
Module 5 - Architectural AnalysisPatterns and FrameworksPatterns and Frameworks• Pattern• Provides a common solution to a common problemin a context• Analysis/Design pattern• Provides a solution to a narrowly-scoped technicalproblem• Provides a fragment of a solution, or a piece of thepuzzle• Framework• Defines the general approach to solving theproblem• Provides a skeletal solution, whosedetails may be Analysis/Design patternsMastering Object Oriented Analysis and Design with UMLCopyright © 2003 Rational Software, all rights reserved 11The selection of the upper-level layers may be affected by the choice of anarchitectural pattern or framework. Thus, it is important to define what these termsmean.A pattern codifies specific knowledge collected from experience. Patterns provideexamples of how good modeling solves real problems, whether you come up with thepattern yourself or you reuse someone else’s. Design patterns are discussed in moredetail on the next slide.Frameworks differ from Analysis and Design patterns in their scale and scope.Frameworks describe a skeletal solution to a particular problem that may lack manyof the details, and that may be filled in by applying various Analysis and Designpatterns.A framework is a micro-architecture that provides an incomplete template forapplications within a specific domain. Architectural frameworks provide the contextin which the components run. They provide the infrastructure (plumbing, if you will)that allows the components to co-exist and perform in predictable ways. Theseframeworks may provide communication mechanisms, distribution mechanisms,error processing capabilities, transaction support, and so forth.Frameworks may range in scope from persistence frameworks that describe theworkings of a fairly complex but fragmentary part of an application to domain-specificframeworks that are intended to be customized (such as Peoplesoft, SanFransisco,Infinity, and SAP). For example, SAP is a framework for manufacturing and finance.5 - 11
- Page 126 and 127: DEV475 Mastering Object-Oriented An
- Page 128 and 129: DEV475 Mastering Object-Oriented An
- Page 130 and 131: DEV475 Mastering Object-Oriented An
- Page 132 and 133: DEV475 Mastering Object-Oriented An
- Page 134 and 135: DEV475 Mastering Object-Oriented An
- Page 136 and 137: DEV475 Mastering Object-Oriented An
- Page 138 and 139: DEV475 Mastering Object-Oriented An
- Page 140 and 141: DEV475 Mastering Object-Oriented An
- Page 142 and 143: DEV475 Mastering Object-Oriented An
- Page 144 and 145: DEV475 Mastering Object-Oriented An
- Page 146 and 147: DEV475 Mastering Object-Oriented An
- Page 148 and 149: DEV475 Mastering Object-Oriented An
- Page 150 and 151: DEV475 Mastering Object-Oriented An
- Page 152 and 153: DEV475 Mastering Object-Oriented An
- 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 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 204 and 205: 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
<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>Define the High-Level Organization of SubsystemsArchitectural <strong>Analysis</strong> Steps• Key Concepts• Define the High-Level Organization ofSubsystems• Identify <strong>Analysis</strong> mechanisms• Identify Key Abstractions• Create Use-Case Realizations• Checkpoints<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 10Early in the software development lifecycle, it is important to define the modelingconventions that everyone on the project should use. The modeling conventionsensure that the representation of the architecture <strong>and</strong> design are consistent acrossteams <strong>and</strong> iterations.5 - 10