# arc42 section 2: Architecture Constraints

Checks for section 2 (Architecture Constraints) of an arc42 document.

Technical, organizational and regulatory constraints

- For each open data source, the document states its license, or that it is in the public domain. → [Use of external and open data](https://arc.fuet.ch/concepts/data-architecture/use-of-external-and-open-data.md)
- The building block view is a hierarchy of black boxes and white boxes, with level 1 as the white box of the whole system. → [arc42 Architecture Documentation Template](https://arc.fuet.ch/concepts/documentation/arc42-documentation-template.md)
- The document lists constraints in one place, with an explanation or background for each. → [arc42 Constraints](https://arc.fuet.ch/concepts/documentation/arc42-constraints.md)
- Constraints are grouped into technical, organizational/political and conventions where the list is long. → [arc42 Constraints](https://arc.fuet.ch/concepts/documentation/arc42-constraints.md)
- Organizational constraints such as budget, time or processes are recorded. → [arc42 Constraints](https://arc.fuet.ch/concepts/documentation/arc42-constraints.md)
- Data principles and architecture reference materials are identified as guidance for the Data Architecture. → [Data Architecture Inputs](https://arc.fuet.ch/concepts/enterprise-architecture/data-architecture-inputs.md)
- Data administration responsibilities are clearly assigned. → [Data Architecture Principle](https://arc.fuet.ch/concepts/enterprise-architecture/data-architecture-principle.md)
- The document states which business vision or strategy the enterprise-level architecture supports. → [Enterprise Architecture](https://arc.fuet.ch/concepts/enterprise-architecture/enterprise-architecture-management.md)
- The chosen level of process integration and standardization is stated explicitly. → [Foundation for Execution](https://arc.fuet.ch/concepts/enterprise-architecture/foundation-for-execution.md)
- Each catalogued component shows a standardization status (standard, approval needed, or not permitted). → [IT Component Catalogue](https://arc.fuet.ch/concepts/enterprise-architecture/it-component-catalogue.md)
- Constraints that originate in enterprise-wide standards, such as mandated technologies, are listed as constraints. → [Relationship between Enterprise Architecture and Application Architecture](https://arc.fuet.ch/concepts/enterprise-architecture/relationship-between-enterprise-architecture-and-application-architecture.md)
- The deployment view shows the infrastructure elements relevant to the software. → [Technology Architecture](https://arc.fuet.ch/concepts/enterprise-architecture/technology-architecture.md)
- The document lists its constraints in one place, so architects can see where they are free and where they must comply. → [Architectural Constraint](https://arc.fuet.ch/concepts/forces-decisions/requirements-versus-constraints.md)
- The decision record lists the forces and concerns that drove each decision, for example in a Decision Drivers section. → [Architectural Force](https://arc.fuet.ch/concepts/forces-decisions/architectural-forces.md)
- The document states where the architects are free and where they are bound by constraints. → [Architectural Force](https://arc.fuet.ch/concepts/forces-decisions/architectural-forces.md)
- Constraints are listed, and the document notes which ones may be negotiable and which apply organization-wide. → [Architecture Challenges at Project Start](https://arc.fuet.ch/concepts/forces-decisions/architecture-challenges-at-project-start.md)
- The document states that early decisions may be revisited and corrected. → [Architecture Challenges at Project Start](https://arc.fuet.ch/concepts/forces-decisions/architecture-challenges-at-project-start.md)
- Each important decision is documented with its motivation and reasoning. → [Architecture Decision Documentation and Requirements Management](https://arc.fuet.ch/concepts/forces-decisions/decision-documentation-and-requirements-management.md)
- The context of a decision covers technical, political, social and project aspects. → [Architecture Decision Documentation and Requirements Management](https://arc.fuet.ch/concepts/forces-decisions/decision-documentation-and-requirements-management.md)
- Use cases are backed by functional requirements that itemize specific software behavior. → [Requirement Types and Documents (Wiegers/Beatty)](https://arc.fuet.ch/concepts/functional-requirements/requirement-types-and-documents.md)
- The document lists constraints and shows where the architect is free to decide. → [Requirements and Means Influence Architecture](https://arc.fuet.ch/concepts/fundamentals/requirements-and-means-influence-architecture.md)
- The document notes which constraints come from the wider organization rather than from this system alone. → [Software Architecture in Its Context](https://arc.fuet.ch/concepts/fundamentals/software-architecture-in-its-context.md)
- The document names the BPMN modeling tool the team uses and whether it runs as a desktop app or a web app. → [BPMN Modeling Tool](https://arc.fuet.ch/concepts/modeling-bpmn/bpmn-modeling-tools.md)
- The principles reflect what the organization values when it must compromise, not generic statements. → [Architecture Principle](https://arc.fuet.ch/concepts/principles/architecture-principle.md)
- Encryption at rest and in transit is chosen based on the confidentiality level of the data. → [Confidentiality](https://arc.fuet.ch/concepts/quality-attributes/confidentiality.md)
- The document names lock-in risks and says which other products could be used in place of the present one. → [Replaceability](https://arc.fuet.ch/concepts/quality-attributes/replaceability.md)
- The costs of the chosen style are stated next to its benefits, such as operational complexity or network latency. → [Architecture Style](https://arc.fuet.ch/concepts/styles-patterns/architectural-style.md)