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 UMLReview: What Is Architecture: The “4+1 View” ModelReview: What Is Architecture: The “4+1 View” ModelLogical ViewImplementation ViewAnalysts/DesignersStructureEnd-userFunctionalityUse-Case ViewProgrammersSoftware managementSystem integratorsPerformanceScalabilityThroughputProcess ViewDeployment ViewSystem engineeringSystem topologyDelivery, installationcommunicationMastering Object Oriented Analysis and Design with UMLCopyright © 2003 Rational Software, all rights reserved 6The above diagram describes the model Rational uses to describe the softwarearchitecture. This is the recommended way to represent a software architecture.There may be other “precursor” architectures that are not in this format. The goal isto mature those architectural representations into the 4+1 view representation.In Architectural Analysis, you will concentrate on the Logical View. The other viewswill be addressed in later architecture modules:• The Logical View will be refined in the Identify Design Mechanisms, IdentifyDesign modules.• The Process View will be discussed in the Describe Run-time Architecturemodule.• The Deployment View will be discussed in the Describe Distribution module.• The Implementation View is developed during Implementation and is thusconsidered out of scope for this Analysis and Design course.5 - 6
Module 5 - Architectural AnalysisReview: What Is a Package?Review: What Is a Package?• A package is a general-purpose mechanismfor organizing elements into groups.• It is a model element that can contain othermodel elements.UniversityArtifacts• A package can be used• To organize the model under development.• As a unit of configuration management.Mastering Object Oriented Analysis and Design with UMLCopyright © 2003 Rational Software, all rights reserved 7Packages were first introduced in the Introduction to Object Orientation module.The slide is repeated here for review purposes.Packages can be used to group any model elements. However, in this module, wewill be concentrating on how they are used within the Design Model.5 - 7
- Page 122 and 123: DEV475 Mastering Object-Oriented An
- Page 124 and 125: DEV475 Mastering Object-Oriented An
- 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 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 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
<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>Review: What Is Architecture: The “4+1 View” ModelReview: What Is Architecture: The “4+1 View” ModelLogical ViewImplementation ViewAnalysts/<strong>Design</strong>ersStructureEnd-userFunctionalityUse-Case ViewProgrammersSoftware managementSystem integratorsPerformanceScalabilityThroughputProcess ViewDeployment ViewSystem engineeringSystem topologyDelivery, installationcommunication<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 6The above diagram describes the model Rational uses to describe the softwarearchitecture. This is the recommended way to represent a software architecture.There may be other “precursor” architectures that are not in this format. The goal isto mature those architectural representations into the 4+1 view representation.In Architectural <strong>Analysis</strong>, you will concentrate on the Logical View. The other viewswill be addressed in later architecture modules:• The Logical View will be refined in the Identify <strong>Design</strong> Mechanisms, Identify<strong>Design</strong> modules.• The Process View will be discussed in the Describe Run-time Architecturemodule.• The Deployment View will be discussed in the Describe Distribution module.• The Implementation View is developed during Implementation <strong>and</strong> is thusconsidered out of scope for this <strong>Analysis</strong> <strong>and</strong> <strong>Design</strong> course.5 - 6