4+1 View Model Deliverable Templates
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.
Linked.Archi
Software Architecture Document (4+1)
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.
1. Introduction & Architectural Goals
Purpose of the document, scope of the system, architectural goals and constraints, and references to requirements driving the architecture.
2. Architectural Scenarios
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
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
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
Software organization — modules, packages, layers, subsystems, build structure, and team ownership. Component diagrams, package diagrams, or repository/service boundaries.
6. Physical View
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
Cross-cutting quality attribute requirements, key architectural decisions with rationale, and known trade-offs. References to ADRs and quality attribute scenarios.