4 1 architectural view model

The 4 1 views of software architecture model is a widely used model of the views of a software system that was developed by Philippe Kruchten for " description of the architecture of a software - intensive system on the basis of several competing views ."

These views are used to describe the system from the perspective of the various stakeholders, such as end-user, developer, or project manager. The four views of the model are logical, development, process and physical view ( context, component, distribution and runtime views). In addition, use cases or scenarios can be included to better illustrate the architecture, which is intended to express the " 1". It was known to the UML tool Rational Rose.

The 4 1 views are:

  • Logical view: The "logical view" deals with the system for the end-user functionality. Various UML diagrams are used to represent, among the class diagram, communication chart sequence diagram.
  • Development view: The development perspective (also Implementation View) describes the system from the standpoint of a developer and is engaged in the software management. It is represented as a UML component diagram or package diagram.
  • Process view: The "process view" deals with the dynamic aspects of the system. It clarifies the processes of the system and how they communicate with respect to the runtime behavior. It is intended to describe concurrency, distribution, integration, performance and scalability. The corresponding UML diagrams include, for example, the activity diagram.
  • Physical view: The "physical view" (or deployment view) describes the system from the point of view of the system architect. He (ie the assignment of these hardware parts ) deals with the distribution of software components at the physical level and the communication between these components. The corresponding UML diagram is the distribution diagram.
  • Scenarios: The fifth view is to show important use cases or application scenarios. These describe processes between components or processes and should help to identify architectural elements, to illustrate and verify the architecture. They also serve as a starting point for initial testing or implementation architecture designs. As a UML diagram, the use case diagram is used.
Rational Software#Second-generation products Deployment diagram Digital Object Identifier
360
de