TL;DR
Architecture Compliance ensures that implementation projects understand and follow the target enterprise architecture. TOGAF distinguishes the architecture function of compliance from the formal enterprise and IT governance compliance review process.
What it is
Architecture Compliance is a governance concept used to ensure that projects and changes conform to the target enterprise architecture.
It is also called:
- enterprise architecture compliance
- architecture compliance
- compliance
The goal is to make sure implementation work moves the enterprise toward the target architecture.
Two compliance functions
TOGAF distinguishes between two related compliance functions.
Architecture function
The architecture function of compliance provides implementation projects with information about how the enterprise architecture impacts them.
For example, the architecture function may specify participation in:
- technology selection
- external service provision
- product purchases
- solution design decisions
- implementation planning
This helps projects understand the constraints, standards, and architecture requirements they must follow.
Enterprise and IT governance function
The enterprise and IT governance function defines a formal architecture compliance review process.
This process reviews whether projects comply with the target enterprise architecture.
It is more formal than everyday architecture guidance.
It connects architecture governance with broader enterprise and IT governance.
Compliance during implementation
Compliance becomes especially important during implementation because project teams are making real changes to the enterprise.
Without compliance governance, projects may:
- diverge from the target architecture
- create unnecessary redundancy
- ignore architecture standards
- increase technical debt
- weaken reuse
- create inconsistent sub-architectures
Compliance reviews and assessments help detect and manage these issues.
Relationship to Phase G
Phase G: Implementation Governance uses architecture governance to oversee implementation projects.
During Phase G, architecture compliance is supported through:
- Architecture Contracts
- compliance reviews and assessments
- architecture requirements
- implementation constraints
- checklists
- dispensations where appropriate
Relationship to the Architecture Board
The Architecture Board plays an important role in compliance governance.
It may:
- enforce architecture compliance
- grant dispensations
- review non-compliance
- resolve conflicts
- provide escalation
- approve governance processes and checklists
However, final decision rights about the target architecture remain with the stakeholders.
Exam note
- Architecture Compliance ensures implementation projects conform to the target architecture.
- TOGAF distinguishes the architecture function of compliance from the enterprise and IT governance compliance review function.
- The architecture function informs projects how enterprise architecture affects them.
- The enterprise and IT governance function defines a formal compliance review process.
- Compliance is especially important during implementation.
- Phase G uses contracts, reviews, assessments, requirements, constraints, and checklists to support compliance.
- The Architecture Board supports compliance governance and may grant dispensations.