# arc42 section 7: Deployment View

Checks for section 7 (Deployment View) of an arc42 document.

Technical infrastructure and mapping of building blocks to it

- A small set of scenarios or use cases illustrates the architecture as a fifth view. → [4+1 View Model](https://arc.fuet.ch/concepts/documentation/4-1-view-model.md)
- If the software runs as a distributed system, the document includes a deployment view of the technical infrastructure. → [Additional Architecture Viewpoints (Security, Information, Operational, Development, Process, Evolution)](https://arc.fuet.ch/concepts/documentation/additional-architecture-views-and-perspectives.md)
- Operation, administration and support in production are described. → [Additional Architecture Viewpoints (Security, Information, Operational, Development, Process, Evolution)](https://arc.fuet.ch/concepts/documentation/additional-architecture-views-and-perspectives.md)
- The building block view is present and shows the static decomposition of the system. → [Architectural View](https://arc.fuet.ch/concepts/documentation/purpose-of-views.md)
- If 4+1 is used, a small set of scenarios is included to illustrate the architecture. → [Architecture View Model](https://arc.fuet.ch/concepts/documentation/architecture-view-model.md)
- Quality perspectives are applied to views, not treated as views of their own. → [Architecture Viewpoint](https://arc.fuet.ch/concepts/documentation/architecture-viewpoint.md)
- The document maps building blocks onto hardware. → [Deployment View](https://arc.fuet.ch/concepts/documentation/distribution-view.md)
- If the system runs in several environments, each relevant environment is documented. → [Deployment View](https://arc.fuet.ch/concepts/documentation/distribution-view.md)
- The deployment view uses a UML deployment diagram. → [Deployment View](https://arc.fuet.ch/concepts/documentation/distribution-view.md)
- Where readable Git diffs matter, the team uses plain .drawio files instead of .drawio.png. → [Diagram Metadata in PNG (drawio.png)](https://arc.fuet.ch/concepts/documentation/diagram-metadata-in-png-drawio-png.md)
- The deployment view documents which building blocks run on which hardware or infrastructure. → [Distribution View Antipatterns](https://arc.fuet.ch/concepts/documentation/distribution-view-antipatterns.md)
- All relevant environments are documented. → [Distribution View Antipatterns](https://arc.fuet.ch/concepts/documentation/distribution-view-antipatterns.md)
- Each deployment diagram covers a single environment, such as production or staging. → [Distribution View Antipatterns](https://arc.fuet.ch/concepts/documentation/distribution-view-antipatterns.md)
- The documentation states whether diagrams are rendered with the free public Kroki service or a self-managed instance. → [Kroki](https://arc.fuet.ch/concepts/documentation/kroki.md)
- If POST with plain text is used, the output format is chosen with the Accept header. → [Kroki](https://arc.fuet.ch/concepts/documentation/kroki.md)
- The conventions for each view type (viewpoint) are defined apart from the views themselves. → [Model vs. View](https://arc.fuet.ch/concepts/documentation/model-vs-view.md)
- High-level and low-level views are drawn as separate diagrams, not combined in one. → [Unclear Level of Abstraction Antipattern](https://arc.fuet.ch/concepts/documentation/unclear-level-of-abstraction-antipattern.md)
- Applications are mapped to technology platforms. → [Application Architecture Artifacts](https://arc.fuet.ch/concepts/enterprise-architecture/application-architecture-artifacts.md)
- Business objects can be traced through data objects to the artifacts that realize them. → [Enterprise Architecture Layers](https://arc.fuet.ch/concepts/enterprise-architecture/enterprise-architecture-structure-business-and-it-architecture.md)
- Each technology has a lifecycle status such as adopt, tolerate, invest, or retire. → [IT Component Catalogue](https://arc.fuet.ch/concepts/enterprise-architecture/it-component-catalogue.md)
- Every relevant environment is documented, not just production. → [Technology Architecture](https://arc.fuet.ch/concepts/enterprise-architecture/technology-architecture.md)
- The document states how partial failure of a service or server is handled. → [Connectors and Distribution](https://arc.fuet.ch/concepts/fundamentals/connectors-and-distribution.md)
- Every deployment targets a node, and only artifacts (or artifact instances) are deployed onto it. → [Deployment Diagram Modeling Mistake](https://arc.fuet.ch/concepts/modeling-uml/deployment-diagram-modeling-mistakes.md)
- Physical hardware nodes are marked «device». Software hosts such as an application server or JVM are marked «executionEnvironment». → [Deployment Diagram Modeling Mistake](https://arc.fuet.ch/concepts/modeling-uml/deployment-diagram-modeling-mistakes.md)
- Each connection between nodes is labeled with its protocol, such as JDBC, REST or RMI. → [Deployment Diagram Modeling Mistake](https://arc.fuet.ch/concepts/modeling-uml/deployment-diagram-modeling-mistakes.md)
- The deployment view shows infrastructure nodes and channels, whether in a UML deployment diagram or another notation. → [Matching Diagram Type to System Aspect](https://arc.fuet.ch/concepts/modeling-uml/matching-diagram-type-to-system-aspect.md)
- Diagrams that show flow of control and data are treated as interaction diagrams, a subset of behavior diagrams. → [UML 2.5 Diagram Taxonomy](https://arc.fuet.ch/concepts/modeling-uml/uml-diagram-taxonomy.md)
- Artifacts are drawn as rectangles inside the box of the node they are allocated to. → [UML Deployment Diagram](https://arc.fuet.ch/concepts/modeling-uml/deployment-diagram.md)
- Complex infrastructure is documented with nested diagrams or nested nodes. → [UML Deployment Diagram](https://arc.fuet.ch/concepts/modeling-uml/deployment-diagram.md)
- Each environment that needs it (development, test, production) has its own deployment documentation. → [UML Deployment Diagram](https://arc.fuet.ch/concepts/modeling-uml/deployment-diagram.md)
- Every relationship line is labeled, and the label matches its direction and intent. → [UML Modeling Anti-Pattern](https://arc.fuet.ch/concepts/modeling-uml/uml-modeling-anti-patterns.md)
- Deeper levels zoom into selected building blocks of the level above. → [UML Structure Diagram](https://arc.fuet.ch/concepts/modeling-uml/structure-diagram.md)
- The documentation does not claim that using UML by itself improves the architecture. → [Why Use UML in Architecture Documentation](https://arc.fuet.ch/concepts/modeling-uml/why-use-uml-in-architecture-documentation.md)
- The availability calculation includes external services that affect critical flows. → [Availability](https://arc.fuet.ch/concepts/quality-attributes/availability.md)
- Installability goals cover both installing and uninstalling, not installing alone. → [Installability](https://arc.fuet.ch/concepts/quality-attributes/installability.md)
- Recovery targets are defined per incident (RTO) and for acceptable data loss (RPO). → [Recoverability](https://arc.fuet.ch/concepts/quality-attributes/recoverability.md)
- The document describes the failover logic and split-brain prevention, and says how they are exercised. → [Active Redundancy](https://arc.fuet.ch/concepts/tactics/active-redundancy.md)
- Traffic is encrypted in transit, for example with TLS. → [Encrypt Data](https://arc.fuet.ch/concepts/tactics/encrypt-data.md)
- The document states how a failed release is rolled back to an earlier version. → [Integrability, Deployability, Testability and Reliability Tactics](https://arc.fuet.ch/concepts/tactics/integrability-deployability-and-testability-tactics.md)
- The document states whether the balancer works at Layer 4 or Layer 7 and why. → [Load Balancer](https://arc.fuet.ch/concepts/tactics/load-balancer.md)
- Timeouts and failure thresholds are configured so transient failures such as network delays do not trigger unnecessary actions. → [Ping/Echo](https://arc.fuet.ch/concepts/tactics/ping-echo.md)
- The document describes how failures are detected (for example heartbeat, ping/echo, or voting) and any grace period used. → [Redundant Spare](https://arc.fuet.ch/concepts/tactics/redundant-spare.md)