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 UMLSoftware Architecture: The “4+1 View” ModelSoftware 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 10The above diagram shows the model Rational uses to describe the softwarearchitecture.Architecture is many things to many different interested parties. On a particularproject, there are usually multiple stakeholders, each with their own concerns andview of the system to be developed. The goal is to provide each of these stakeholderswith a view of the system that addresses their concerns, and suppresses the otherdetails.To address these different needs, Rational has defined the “4+1 view” architecturemodel. An architectural view is a simplified description (an abstraction) of a systemfrom a particular perspective or vantage point, covering particular concerns, andomitting entities that are not relevant to this perspective. Views are “slices” of models.Not all systems require all views (for example, single processor: drop DeploymentView; single process: drop Process View; small program: drop Implementation View,and so forth). A project may document all of these views or additional views. Thenumber of views is dependent on the system you are building.Each of these views, and the UML notation used to represent them, will be discussedin subsequent modules.4 - 10
Module 4 - Analysis and Design OverviewAnalysis and Design WorkflowAnalysis & Design Overview Topics• Key Concepts• Analysis and Design WorkflowMastering Object Oriented Analysis and Design with UMLCopyright © 2003 Rational Software, all rights reserved 11Because we have a common vocabulary, we can now briefly discuss the activities ofAnalysis and Design and how they work together.4 - 11
- Page 106 and 107: DEV475 Mastering Object-Oriented An
- Page 108 and 109: DEV475 Mastering Object-Oriented An
- Page 110 and 111: DEV475 Mastering Object-Oriented An
- Page 112 and 113: DEV475 Mastering Object-Oriented An
- Page 114 and 115: DEV475 Mastering Object-Oriented An
- Page 116 and 117: DEV475 Mastering Object-Oriented An
- Page 118 and 119: DEV475 Mastering Object-Oriented An
- Page 120 and 121: DEV475 Mastering Object-Oriented An
- 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 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 204 and 205: DEV475 Mastering Object-Oriented An
Module 4 - <strong>Analysis</strong> <strong>and</strong> <strong>Design</strong> Overview<strong>Analysis</strong> <strong>and</strong> <strong>Design</strong> Workflow<strong>Analysis</strong> & <strong>Design</strong> Overview Topics• Key Concepts• <strong>Analysis</strong> <strong>and</strong> <strong>Design</strong> Workflow<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 11Because we have a common vocabulary, we can now briefly discuss the activities of<strong>Analysis</strong> <strong>and</strong> <strong>Design</strong> <strong>and</strong> how they work together.4 - 11