Scribd
Upload
69 views20 pages

Session 5 - 4+1 Views - Complete

The 4+1 View Model, introduced by Philippe Kruchten, provides a comprehensive framework for understanding complex software architecture through four essential views: logical, process, physical, and development, along with a scenario view. Each view offers a different perspective on the system, aiding in design and validation, and utilizes various UML diagrams for representation. The model serves as an architecture verification technique for documenting software design effectively.

Uploaded by

shanireal420
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
69 views20 pages

Session 5 - 4+1 Views - Complete

The 4+1 View Model, introduced by Philippe Kruchten, provides a comprehensive framework for understanding complex software architecture through four essential views: logical, process, physical, and development, along with a scenario view. Each view offers a different perspective on the system, aiding in design and validation, and utilizes various UML diagrams for representation. The model serves as an architecture verification technique for documenting software design effectively.

Uploaded by

shanireal420
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 20

4+1

Architectural
view

2/17/2025 1
Architecture View Models
• A model is a complete, simplified
description of a system from a
particular perspective or viewpoint.

• There is no single view that can


present all aspects of complex
software to stakeholders!!!

Users of a requirements document

2
The 4 +1 View Model
• The 4+1 view model was originally introduced by Philippe Kruchten
(Kruchten, 1995).

• The model provides four essential views:


• the logical view,
• the process view,
• the physical view, and
• the development view
• and fifth is the scenario view

3
The Scenario/User Interface View
• The scenario view describes the
functionality of the system, i.e., how the
user employs the system and how the
system provides services to the users.

• It helps designers to discover


architecture elements during the design
process and to validate the architecture
design afterward.

• UML use case diagram

4
The Logical or Conceptual View
• The logical view specifies system decomposition into
conceptual entities (such as objects) and connections
between them (such as associations).
• The logical view is typically supported by
• UML static diagrams including class/object diagrams

5
The Development/Implementation View

• The development view derives from the logical


view and describes the static organization of the
system modules.

• Modules such as namespaces, class library,


subsystem, or packages are building blocks that
group classes for further development and
implementation.

• UML diagrams such as package diagrams and


component diagrams are often used to support
this view.

6
The Process View
• The process view focuses on the dynamic
aspects of the system, i.e., its execution time
behavior.

• This view maps functions, activities, and


interactions onto runtime implementation.

• The process view takes care of the concurrency


and synchronization issues between subsystems.

• UML dynamic diagrams such as activity diagram,


sequence diagram, communication diagram, state
diagram.

7
The Physical/Deployment View
• The physical view describes installation, configuration, and deployment of the
software application.

• It concerns itself with how to deliver the deploy-able system.

• The physical view shows the mapping of software onto hardware.


• It is particularly of interest in distributed or parallel systems.

• The UML deployment diagrams


and other documentation are often used
to support this view.

8
2/17/2025 9
2/17/2025 10
4+1 view model - Advantage
The 4+1 view is an architecture verification technique
for studying and documenting software architecture
design.

11
Tools and SW

12
Visual paradigm

13
Lucid chart

14
Rationale rose

15
MS Visio

16
Edraw max

17
Smartdraw

18
Model-Io

19
Draw.io

20

You might also like