Linked.Archi

4+1 View Model Viewpoints

Viewpoint Definitions

https://meta.linked.archi/4plus1/viewpoints#

v0.1.0 fourplus1vp: Linked.Archi Modified: 2026-05-06 License

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.

Contents

DevelopmentView

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?
Purpose: Designing
Concerns: DevelopmentView, Software Management
View type: Diagram

LogicalView

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?
Purpose: Designing
Concerns: LogicalView, Functionality
View type: Diagram

PhysicalView

Physical Viewpoint

Specifies the mapping of software to hardware — nodes, networks, deployment topology, and resource allocation. Answers: where does the software run?
Purpose: Designing
Concerns: PhysicalView, Deployment & Operations
View type: Diagram

ProcessView

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?
Purpose: Designing
Concerns: ProcessView, Performance & Concurrency
View type: Diagram

ScenariosView

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?
Purpose: Deciding
Concerns: ScenariosView, Validation & Consistency, Functionality
View type: Diagram
Source: linked-archi-meta • Linked.Archi