4+1 View Model Viewpoints
Viewpoint definitions for the 4+1 Architectural View Model. These are language-agnostic viewpoints — they specify concerns and stakeholders but do not prescribe which modeling language to use. A custom metamodel attaches concrete element types via arch:includesConcept.
Linked.Archi
4+1 Viewpoint Catalog
The five viewpoints from Kruchten's 4+1 model, defined as arch:Viewpoint individuals. Language-agnostic — attach concrete element types from your chosen modeling language via arch:includesConcept.
End User
Users of the system whose functional needs drive the Logical View.
Software Architect
Responsible for overall system structure and quality attribute trade-offs.
Developer
Builds and maintains the software modules.
System Engineer
Responsible for deployment topology, infrastructure, and operations.
Project Manager
Manages scope, schedule, and team allocation.
Functionality
What services the system provides to its users.
Performance & Concurrency
Runtime behavior, throughput, latency, scalability, and fault tolerance.
Software Management
Module organization, build structure, reuse, team allocation, and development tooling.
Deployment & Operations
Mapping software to hardware, topology, availability, and installation.
Validation & Consistency
Ensuring the four views are consistent and the architecture satisfies key scenarios.
Logical Viewpoint
Specifies the functional decomposition of the system — key abstractions, their responsibilities, and relationships. Answers: what does the system do and how is it structured logically?
Populate arch:includesConcept with your metamodel's structural elements — e.g., UML Class/Interface/Package, ArchiMate ApplicationComponent/ ApplicationService/DataObject, or custom domain classes.
Process Viewpoint
Specifies the runtime behavior — processes, threads, communication, synchronization, and how the system handles concurrency and distribution. Answers: how does the system behave at runtime?
Populate arch:includesConcept with behavioral elements — e.g., UML Activity/StateMachine/Interaction, BPMN Process/Gateway/Event, ArchiMate ApplicationProcess/ApplicationEvent, or custom flow elements.
Development Viewpoint
Specifies the organization of the software in its development environment — modules, packages, layers, subsystems, build structure, and team ownership. Answers: how is the codebase organized?
Populate arch:includesConcept with packaging/module elements — e.g., UML Component/Package, C4 Container/Component, Backstage Component/System, or custom module types.
Physical Viewpoint
Specifies the mapping of software to hardware — nodes, networks, deployment topology, and resource allocation. Answers: where does the software run?
Populate arch:includesConcept with infrastructure elements — e.g., UML Node/Artifact, ArchiMate Node/Device/SystemSoftware/CommunicationNetwork, C4 DeploymentNode/InfrastructureNode, or custom infra types.
Scenarios Viewpoint (+1)
The unifying viewpoint — key use cases or scenarios that trace through all four views, validating that the architecture supports the most important user goals. Answers: does the architecture work end-to-end?
Populate arch:includesConcept with scenario/use-case elements — e.g., UML UseCase/Actor, ArchiMate Stakeholder/Goal/Requirement, or custom scenario types. Scenarios should reference elements from all other four viewpoints.