Skip to content
Contact
SYS_TIME [ 00 00 00 ]

SE322

4+1 VIEW MODEL MAP

Kruchten's 4+1 View Model, on one map

Every view with its stakeholders, concerns and UML diagrams, drawn around the scenarios that tie them together (Chapter 2, Lecture 3). Drag to move, scroll or pinch to zoom.

Mind map of the 4+1 View Model. The central User View (scenarios: use case diagrams) links to four views. Logical view: functional, what parts exist, for end users, designers and analysts, modelled with static class and object diagrams and dynamic sequence, communication, interaction, state and activity diagrams. Process view: non-functional, runtime behavior and concurrency, for developers and integrators, modelled with activity, state machine and interaction overview diagrams. Development view: how parts are organized as code, for project managers and programmers, modelled with package and component diagrams. Physical view: where the software runs on hardware nodes, for system engineers, installers and administrators, modelled with deployment diagrams.

The map, in text

Scenarios (+1)

User view

Functionality: discovers elements and validates the design by tracing a use case through the other four views.

Stakeholders
Everyone
Diagrams
Use Case, Scenarios
Watch the diagram videos

Logical View

WHAT parts exist

Functional requirements: specifies the entities and the connections between them.

Stakeholders
End users, designers, analysts
Diagrams
Static: Class, Object. Dynamic: Sequence, Communication, Interaction, State, Activity
Watch the diagram videos

Process View

How the system runs

Non-functional: runtime behavior, concurrency and synchronization; evaluated on scalability and performance.

Stakeholders
Developers, integrators
Diagrams
Activity (main), State Machine, Interaction Overview

Development View

HOW parts are organized as code

Static organization of packages, components, subsystems, libraries and source directories.

Stakeholders
Project managers, programmers
Diagrams
Package, Component
Watch the diagram videos

Physical View

WHERE the software runs

Deployment on hardware nodes, configuration and installation; evaluated on security, performance and availability.

Stakeholders
System engineers, installers, administrators
Diagrams
Deployment
Watch the diagram videos