4+1 View Model Deliverable Templates
type: Ontology
imports: core#
license: http://creativecommons.org/licenses/by/4.0/
preferred namespace prefix: fourplus1dt
description: Deliverable templates for the 4+1 Architectural View Model. Defines a Software Architecture Document (SAD) structured around the five views, following the template pattern from Kruchten's original paper and the RUP SAD template.
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

Software Architecture Document (4+1)
type: DeliverableTemplate
definition: A software architecture document structured around the 4+1 views. Each section corresponds to one of Kruchten's five views, providing a complete architecture description from multiple perspectives. Based on the RUP Software Architecture Document template.
template requires viewpoint: LogicalViewpoint
template requires viewpoint: ProcessViewpoint
template requires viewpoint: DevelopmentViewpoint
template requires viewpoint: PhysicalViewpoint
template requires viewpoint: ScenariosViewpoint
template has section: 1. Introduction & Architectural Goals
template has section: 2. Architectural Scenarios
template has section: 3. Logical View
template has section: 4. Process View
template has section: 5. Development View
template has section: 6. Physical View
template has section: 7. Quality & Architectural Decisions
template targets purpose: Designing
template targets purpose: Informing
template has format: MarkdownFormat
template has format: HTMLFormat

1. Introduction & Architectural Goals
type: TemplateSection
section order: 1
definition: Purpose of the document, scope of the system, architectural goals and constraints, and references to requirements driving the architecture.

2. Architectural Scenarios
type: TemplateSection
section order: 2
section viewpoint: ScenariosViewpoint
definition: Key use cases and scenarios that drive and validate the architecture. Each scenario traces through the other four views, demonstrating how the architecture supports the most important user goals.

3. Logical View
type: TemplateSection
section order: 3
section viewpoint: LogicalViewpoint
definition: Functional decomposition — key abstractions, their responsibilities, and relationships. Class diagrams, domain models, service interfaces, or equivalent representations from the chosen modeling language.

4. Process View
type: TemplateSection
section order: 4
section viewpoint: ProcessViewpoint
definition: Runtime behavior — processes, threads, communication mechanisms, synchronization, and concurrency patterns. Activity diagrams, sequence diagrams, or process models showing how the system handles load and failure.

5. Development View
type: TemplateSection
section order: 5
section viewpoint: DevelopmentViewpoint
definition: Software organization — modules, packages, layers, subsystems, build structure, and team ownership. Component diagrams, package diagrams, or repository/service boundaries.

6. Physical View
type: TemplateSection
section order: 6
section viewpoint: PhysicalViewpoint
definition: Deployment topology — mapping of software to hardware, nodes, networks, availability zones, and resource allocation. Deployment diagrams or infrastructure-as-code references.

7. Quality & Architectural Decisions
type: TemplateSection
section order: 7
definition: Cross-cutting quality attribute requirements, key architectural decisions with rationale, and known trade-offs. References to ADRs and quality attribute scenarios.