4+1 View Model Taxonomy
type: Ontology
imports: core#
license: http://creativecommons.org/licenses/by/4.0/
preferred namespace prefix: fourplus1
description: SKOS taxonomy of the 4+1 Architectural View Model (Kruchten, 1995). Defines five viewpoint categories that can be used to classify viewpoints in any custom metamodel. The 4+1 model is language-agnostic — it describes what concerns each view addresses, not which notation to use.
created: 2026-05-06
modified: 2026-05-06
creator: Kalin Maldzhanski
publisher: Linked.Archi
publisher: linked.archi
version IRI: 0.1.0#
version info: 0.1.0
source: 220018231 The 41 View Model of Architecture

4+1 Architectural View Model
type: ConceptScheme
definition: Classification scheme based on Philippe Kruchten's 4+1 View Model (IEEE Software, 1995). Organizes architecture descriptions into four concurrent views (Logical, Process, Development, Physical) plus a unifying Scenarios view that validates and illustrates the others.
has top concept: Logical View
has top concept: Process View
has top concept: Development View
has top concept: Physical View
has top concept: Scenarios View
source: 220018231 The 41 View Model of Architecture

Logical View
type: Concept
type: Concern
in scheme: 4+1 Architectural View Model
top concept of: 4+1 Architectural View Model
alternative label: Design View
definition: Addresses the functional requirements — what the system provides to end users. Describes the key abstractions (objects, classes, packages) and their relationships. Concerned with decomposition, encapsulation, and interface design.
scope note: In UML: class diagrams, object diagrams, package diagrams. In ArchiMate: Application layer elements (ApplicationComponent, ApplicationService, ApplicationInterface, DataObject). In C4: Component diagrams.
example: Domain model, service interfaces, module decomposition

Process View
type: Concept
type: Concern
in scheme: 4+1 Architectural View Model
top concept of: 4+1 Architectural View Model
alternative label: Concurrency View
definition: Addresses non-functional requirements — concurrency, distribution, performance, scalability, fault tolerance. Describes the runtime behavior: processes, threads, synchronization, and communication mechanisms.
scope note: In UML: activity diagrams, sequence diagrams, state machine diagrams. In ArchiMate: Triggering and Flow relationships, ApplicationProcess, ApplicationEvent. In BPMN: full process models with gateways and events.
example: Message flows between services, event-driven choreography, thread pools

Development View
type: Concept
type: Concern
in scheme: 4+1 Architectural View Model
top concept of: 4+1 Architectural View Model
alternative label: Implementation View
definition: Addresses the organization of the software in its development environment. Describes modules, packages, layers, subsystems, and their dependencies. Concerned with build structure, team allocation, and reuse.
scope note: In UML: component diagrams, package diagrams. In C4: Container diagrams (deployable units and their technology choices). In Backstage: Component and System catalog entries with ownership.
example: Microservice boundaries, shared libraries, monorepo structure

Physical View
type: Concept
type: Concern
in scheme: 4+1 Architectural View Model
top concept of: 4+1 Architectural View Model
alternative label: Deployment View
definition: Addresses the mapping of software to hardware — topology, deployment, communication, and infrastructure. Describes nodes, networks, and the allocation of processes and components to physical or virtual resources.
scope note: In UML: deployment diagrams. In ArchiMate: Technology layer (Node, Device, SystemSoftware, CommunicationNetwork) with Assignment relationships. In C4: Deployment diagrams.
example: Kubernetes cluster topology, cloud region layout, network zones

Scenarios View
type: Concept
type: Concern
in scheme: 4+1 Architectural View Model
top concept of: 4+1 Architectural View Model
alternative label: +1 View
alternative label: Use Case View
definition: The unifying view — a set of key scenarios (use cases) that drive and validate the architecture. Each scenario traces through the other four views, showing how elements from the Logical, Process, Development, and Physical views collaborate to fulfill a user goal.
scope note: In UML: use case diagrams, sequence diagrams showing end-to-end scenarios. In ArchiMate: motivation elements (Stakeholder, Goal, Requirement) linked to application and business elements. In C4: System Context diagrams showing user interactions.
example: User places an order — traces from UI through services, queues, database, to deployment