Kruchten’s 4+1 views for solution architecture

4+1 is a view model designed by Philippe Kruchten describing the architecture of IT systems, based on the use of multiple, concurrent views.

Figure: 4+1 views

The 4+1 views describe a solution from the viewpoint of different stakeholders. The model contains the following views:

  • Logical view - this describes the functionality that the system provides to end users
  • Development / implementation view - this describes the system from a programmer's perspective and is concerned with software management
  • Process view - this describes the dynamic aspects of the system, explains the system processes and how they communicate, and focuses on the runtime behavior of the system. The process view addresses issues like concurrency, distribution, integrators, performance and scalability
  • Physical / deployment view - this describes 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 communication between these components.
  • Use cases - this describes a small set of use cases, or scenarios, the fifth view. They are used to identify architectural elements and to illustrate and validate the architecture design. 

Apart from software architecture, the 4+1 view descriptions can be used in infrastructure architecture as well. The 4+1 views define what should be documented and how (4+1 prefers using UML for this). It does not contain a process on how to create the documentation, like the SEI stack does.


This entry was posted on Friday 05 July 2013

Earlier articles

Cloud computing and Infrastructure

What is IT architecture?

Infrastructure as Code pipelines

Quantum computing

VS kan nog steeds Europese data Microsoft opeisen ondanks nieuwe regels

Data Nederlandse studenten in cloud niet grootschalig toegankelijk voor bedrijven VS

Passend Europees cloudinitiatief nog ver weg

Security bij cloudproviders wordt niet beter door overheidsregulering

The cloud is as insecure as its configuration

Infrastructure as code

DevOps for infrastructure

Infrastructure as a Service (IaaS)

(Hyper) Converged Infrastructure

Object storage

Software Defined Networking (SDN) and Network Function Virtualization (NFV)

Software Defined Storage (SDS)

What's the point of using Docker containers?

Identity and Access Management

Using user profiles to determine infrastructure load

Public wireless networks

Stakeholder management

Archivering data - more than backup

Desktop virtualization

Supercomputer architecture

x86 platform architecture

Midrange systems architecture

Mainframe Architecture

Software Defined Data Center - SDDC

The Virtualization Model

Sjaak Laan

What are concurrent users?

Performance and availability monitoring in levels

UX/UI has no business rules

Technical debt: a time related issue

Solution shaping workshops

Architecture life cycle

Project managers and architects

Using ArchiMate for describing infrastructures

Kruchten’s 4+1 views for solution architecture

The SEI stack of solution architecture frameworks

TOGAF and infrastructure architecture

How to handle a Distributed Denial of Service (DDoS) attack

The Zachman framework

An introduction to architecture frameworks

Architecture Principles

Views and viewpoints explained

Stakeholders and their concerns

Skills of a solution architect architect

Solution architects versus enterprise architects

Definition of IT Architecture

Purchasing of IT infrastructure technologies and services

IP Protocol (IPv4) classes and subnets

My Book

What is Cloud computing and IaaS?

What is Big Data?

How to make your IT "Greener"

IDS/IPS systems

Introduction to Bring Your Own Device (BYOD)

IT Infrastructure Architecture model

Fire prevention in the datacenter

Where to build your datacenter

Availability - Fall-back, hot site, warm site

Reliabilty of infrastructure components

Human factors in availability of systems

Business Continuity Management (BCM) and Disaster Recovery Plan (DRP)

Performance - Design for use

Performance concepts - Load balancing

Performance concepts - Scaling

Performance concept - Caching

Perceived performance

Ethical hacking

Computer crime

Introduction to Cryptography

Introduction to Risk management

Engelse woorden in het Nederlands

The history of UNIX and Linux

The history of Microsoft Windows

Infosecurity beurs 2010

The history of Storage

The history of Networking

The first computers

Cloud: waar staat mijn data?

Tips voor het behalen van uw ITAC / Open CA certificaat

Ervaringen met het bestuderen van TOGAF

De beveiliging van uw data in de cloud

Proof of concept

Measuring Enterprise Architecture Maturity

The Long Tail

Open group ITAC /Open CA Certification

Google outage

Een consistente back-up? Nergens voor nodig.

Human factors in security

TOGAF 9 - wat is veranderd?

Landelijk Architectuur Congres LAC 2008

De Mythe van de Man-Maand

InfoSecurity beurs 2008

Spam is big business

SAS 70

De zeven eigenschappen van effectief leiderschap

Een ontmoeting met John Zachman

Persoonlijk Informatie Eigendom


Recommended links

Genootschap voor Informatie Architecten
Ruth Malan
Gaudi site
XR Magazine
Esther Barthel's site on virtualization
Eltjo Poort's site on architecture


Feeds

 
XML: RSS Feed 
XML: Atom Feed 


Disclaimer

The postings on this site are my opinions and do not necessarily represent CGI’s strategies, views or opinions.

 

Copyright Sjaak Laan