4 1 architectural view model - significado y definición. Qué es 4 1 architectural view model
Diclib.com
Diccionario en línea

Qué (quién) es 4 1 architectural view model - definición

VIEW MODEL IN SOFTWARE ARCHITECTURE
4+1; 4+1 View Model; 4+1 Architectural View Model
  • Illustration of the 4+1 Architectural View Model.

Discovery Aviation Model 201         
1992 UTILITY AIRCRAFT MODEL BY AVIA LTD.
Discovery 201
The Discovery Aviation Model 201 aka Avia Accord 201 is a light utility aircraft that was re-introduced in 2013.
Ikarbus IK-201         
  • IK-201 of Lasta Beograd.
  • IK-201 of JGSP Novi Sad.
  • IK-201 of Lastra Lazarevac.
MOTOR VEHICLE
IK-201
Ikarbus IK-201 is an articulated city bus built by the Serbian bus manufacturer Ikarbus from 1993 until 2006.
OSE class A.201         
  • Class A.201 locomotive as it was before the modifications. Here is A.204 at the Rentis Depot in 2007
CLASS OF 10 GREEK DIESEL-ELECTRIC LOCOMOTIVE
User:Μητσίκας/OSE class A.201; Draft:OSE class A.201; User:JTE Dimandix/OSE class A.201
The OSE class A.201, also known as the Διακοσαράκι (Diakosaraki, Little two-hundred) or Πλούτο (Pluto), after the well known cartoon, due to the generally not accepted aesthetic result of the reconstruction completed in 2010, is, along with the class A.

Wikipedia

4+1 architectural view model

4+1 is a view model used for "describing the architecture of software-intensive systems, based on the use of multiple, concurrent views". The views are used to describe the system from the viewpoint of different stakeholders, such as end-users, developers, system engineers, and project managers. The four views of the model are logical, development, process and physical view. In addition, selected use cases or scenarios are used to illustrate the architecture serving as the 'plus one' view. Hence, the model contains 4+1 views:

  • Logical view: The logical view is concerned with the functionality that the system provides to end-users. UML diagrams are used to represent the logical view, and include class diagrams, and state diagrams.
  • Process view: The process view deals with the dynamic aspects of the system, explains the system processes and how they communicate, and focuses on the run time behavior of the system. The process view addresses concurrency, distribution, integrator, performance, and scalability, etc. UML diagrams to represent process view include the sequence diagram, communication diagram, activity diagram.
  • Development view: The development view illustrates a system from a programmer's perspective and is concerned with software management. This view is also known as the implementation view. UML Diagrams used to represent the development view include the Package diagram and the Component diagram.
  • Physical view: The physical view (aka the deployment view) depicts the system from a system engineer's point of view. It is concerned with the topology of software components on the physical layer as well as the physical connections between these components. UML diagrams used to represent the physical view include the deployment diagram.
  • Scenarios: The description of an architecture is illustrated using a small set of use cases, or scenarios, which become a fifth view. The scenarios describe sequences of interactions between objects and between processes. They are used to identify architectural elements and to illustrate and validate the architecture design. They also serve as a starting point for tests of an architecture prototype. This view is also known as the use case view.

The 4+1 view model is generic and is not restricted to any notation, tool or design method. Quoting Kruchten,

The “4+1” view model is rather “generic”: other notations and tools can be used, other design methods can be used, especially for the logical and process decompositions, but we have indicated the ones we have used with success.