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