Learn architecture documentation vocabulary: 4+1 view model, logical vs. physical architecture, ADRs, arc42 template, deployment diagrams — the language of professional architecture documentation.
0 / 5 completed
1 / 5
The architect says: 'We follow the 4+1 view model for our architecture documentation.' What is the '4+1 view model'?
The 4+1 view model, introduced by Philippe Kruchten, describes software architecture through five views: Logical (functionality), Process (dynamic behaviour), Development (code organisation), Physical (deployment), and Scenarios (+1 use cases that tie the other views together). It is widely used in enterprise architecture documentation.
2 / 5
The tech lead explains: 'The logical architecture shows the components and their relationships, while the physical architecture shows where they run.' What is the key difference?
Logical architecture focuses on the conceptual structure — components, layers, modules, and their relationships — independent of infrastructure. Physical architecture (also called deployment architecture) shows where components actually run: which servers, containers, cloud regions, and networks. Both views are necessary for a complete architectural picture.
3 / 5
A developer says: 'The architecture is documented in the ADR for this decision.' What is an ADR?
ADR stands for Architecture Decision Record. An ADR is a short document that captures a significant architectural decision, its context, the options considered, the chosen solution, and the rationale. ADRs are stored in the repository alongside the code (often in /docs/adr/) and provide a historical record of why the architecture looks the way it does.
4 / 5
The architect recommends: 'We use the arc42 template for documenting our system.' What is arc42?
arc42 is a pragmatic, structured template for documenting software architectures. It organises documentation into 12 sections, including system context, constraints, solution strategy, building block view, runtime view, deployment view, and architectural decisions. It is widely adopted in German-speaking countries and increasingly used internationally.
5 / 5
During a review, the engineer says: 'The deployment diagram shows we have two app servers behind a load balancer with a shared database.' What does a deployment diagram show?
A deployment diagram (a UML artefact, also Level 4 in C4 model terms) shows the physical or virtual infrastructure: nodes (servers, VMs, containers, devices), communication paths (networks, protocols), and which software components are deployed on which nodes. It is essential for understanding availability, scaling, and infrastructure dependencies.