Study guide
11.4 Architecture Compliance
TOGAF Enterprise Architecture Foundation OGEA-101
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Enterprise Architecture & the TOGAF Standard
1.1 The Enterprise, the Purpose of EA & Its Benefits 1.2 Why the TOGAF Standard: Framework, Documentation Set & Certification 1.3 The Four Architecture Domains & Architecture Abstraction
2 Chapter 2: Enterprise Continuum, Architecture Repository, Content Framework & Capability
2.1 The Enterprise Continuum 2.2 The Architecture Repository 2.3 The TOGAF Content Framework & Enterprise Metamodel 2.4 Architecture Capability
3 Chapter 3: Key TOGAF Terminology
3.1 Terms for Architecture Domains, Levels, States & Capability 3.2 Terms for Work Products, Models, Requirements & Change
4 Chapter 4: ADM Fundamentals, Preliminary Phase & Phase A
4.1 The ADM Cycle, Its Phases & Information Flow 4.2 Draft vs. Approved Deliverables & the Iterative ADM 4.3 Governing EA, Scoping the Architecture & Alternatives 4.4 The Preliminary Phase 4.5 Phase A: Architecture Vision
5 Chapter 5: Architecture Definition — Phases B, C & D
5.1 Phase B: Business Architecture 5.2 Phase C: Information Systems Architectures — Data & Application 5.3 Phase D: Technology Architecture
6 Chapter 6: Opportunities, Migration Planning & Implementation Governance (Phases E, F & G)
6.1 Phase E: Opportunities & Solutions 6.2 Phase F: Migration Planning 6.3 Phase G: Implementation Governance
7 Chapter 7: Phase H, Requirements Management & Agile Delivery
7.1 Phase H: Architecture Change Management 7.2 Requirements Management 7.3 Supporting Agile Software Development with the ADM
8 Chapter 8: ADM Techniques I — Guidelines, Principles, Business Scenarios & Gap Analysis
8.1 ADM Guidelines & Techniques and Architecture Principles 8.2 Business Scenarios 8.3 Gap Analysis
9 Chapter 9: ADM Techniques II — Interoperability, Transformation Readiness & Risk
9.1 Interoperability 9.2 Business Transformation Readiness Assessment 9.3 Risk Management
10 Chapter 10: Applying the ADM
10.1 Guidance for Applying TOGAF, Iteration & Concurrent Phases 10.2 The Architecture Landscape: Strategic, Segment & Capability Levels 10.3 Architecture Partitioning 10.4 The Four Purposes of Architecture 10.5 Applying the TOGAF Standard in the Digital Enterprise
11 Chapter 11: Architecture Governance
11.1 Architecture Governance: Concept & Benefits 11.2 The Architecture Board 11.3 Architecture Contracts 11.4 Architecture Compliance
12 Chapter 12: Architecture Content
12.1 Stakeholders, Concerns, Views & Viewpoints 12.2 Building Blocks: ABBs & SBBs 12.3 ADM Deliverables I: Preliminary Phase and Architecture Vision 12.4 ADM Deliverables II: From Architecture Definition to Change
11.4 Architecture Compliance
Key Takeaways Explain This Topic AI
TOGAF's six levels of architecture conformance are Irrelevant, Consistent, Compliant, Conformant, Fully Conformant, and Non-conformant.
A Compliant implementation implements some specified features, and all features it implements are covered by and in accordance with the specification.
A Conformant implementation implements all specified features in accordance with the specification but also has extra features not in accordance with it.
Any implementation in which some specified features are implemented not in accordance with the specification is Non-conformant.
The first purpose of an Architecture Compliance review is to catch errors in the project architecture early, reducing the cost and risk of later changes.
Last updated: September 2026
11.4 Architecture Compliance
The Foundation syllabus asks you to briefly explain the need for Architecture Compliance . Compliance is how an organization checks that projects actually implement the Enterprise Architecture — and it is one of the most precisely worded areas of TOGAF, especially the six levels of conformance .
The Need for Architecture Compliance
Ensuring the compliance of individual projects with the Enterprise Architecture is an essential aspect of architecture governance. TOGAF describes two complementary processes:
The architecture function prepares project architectures — project-specific views of the Enterprise Architecture that illustrate how it affects each major project.
The IT governance function defines a formal Architecture Compliance review process for reviewing the compliance of projects with the Enterprise Architecture.
The Six Levels of Conformance
TOGAF defines conformance by comparing the features in the architecture specification with the features in the implementation :
Level Definition
Irrelevant The implementation has no features in common with the architecture specification, so the question of conformance does not arise
Consistent The implementation has some features in common with the specification, and those common features are implemented in accordance with it. However, some specified features are not implemented, and the implementation has other features not covered by the specification
Compliant Some features in the specification are not implemented, but all features implemented are covered by the specification , and in accordance with it
Conformant All the features in the specification are implemented in accordance with it, but some more features are implemented that are not in accordance with it
Fully Conformant There is full correspondence between specification and implementation: all specified features are implemented in accordance with the specification, and there are no features implemented that are not covered by it
Non-conformant Any of the above in which some features in the specification are implemented not in accordance with the specification
How to Tell Them Apart
- Question Irrelevant Consistent Compliant Conformant Fully Conformant
- Are all specified features implemented? No common features No No Yes Yes
- Are all implemented features covered by the specification? — No Yes No Yes
If any specified feature is implemented incorrectly , the result is Non-conformant , whatever else is true.
Purpose of Architecture Compliance Reviews
A compliance review is a scrutiny of the compliance of a specific project against established architectural criteria, spirit, and business objectives. TOGAF lists purposes such as:
First and foremost, catch errors in the project architecture early , reducing the cost and risk of changes later in the lifecycle
- Ensure the application of best practices to architecture work
- Identify where the standards themselves may require modification
Identify services that are currently application-specific but might be provided as part of the enterprise infrastructure
- Document strategies for collaboration, resource sharing, and other synergy across teams
- Take advantage of advances in technology
- Communicate the status of technical readiness of a project to management
- Identify key criteria for procurement activities
- Identify and communicate significant architectural gaps to product and service providers
- The Compliance Review Process
Typical steps include:
- Request an architecture review
- Identify the responsible part of the organization and relevant project principals
- Identify the lead enterprise architect and other architects
- Determine the scope of the review
- Tailor checklists
- Schedule the architecture review meeting
- Interview project principals
- Analyze completed checklists
- Prepare the Architecture Compliance review report
- Present the review findings
- Accept the review and sign off
- Send the assessment report or summary to the architecture review coordinator
Roles typically include the Architecture Board , the project leader (or project board), the customer , the lead enterprise architect , other architects , and the project principals . Checklists usually cover areas such as hardware and operating systems, software services and middleware, applications, information management, security, system management, system engineering, and methods and tools.
The output recorded in the ADM is a Compliance Assessment (Phase G).
Dispensations
When a compliance assessment is rejected because a subject area is not compliant, the subject area can either be adjusted or realigned to meet the compliance requirements or request a dispensation . Dispensations provide an alternate route to interim conformance: they are granted for a given time period and set of identified services and operational parameters that must be enforced. When the dispensation expires, the subject area must go through the compliance assessment process again.
Scenario: Classifying a Review Result
An architecture specification for a customer portal defines five features: single sign-on, the standard API gateway, encrypted data at rest, audit logging, and accessibility compliance. The delivered portal implements all five correctly and adds an unapproved chat widget that sends data to an external service outside the specification. Because every specified feature is implemented in accordance with the specification but an extra feature is not in accordance, the result is Conformant , not Fully Conformant. If the audit logging had been implemented incorrectly, the result would be Non-conformant .
Common Exam Pitfalls
Assuming "Compliant" is better than "Conformant." Compliant means only some specified features are implemented (all implemented ones covered); Conformant means all specified features are implemented, plus some extra.
Defining Consistent as "similar in spirit." Consistent has a precise meaning: some common features implemented correctly, some specified features missing, and some features not covered.
Forgetting Non-conformant overrides. Any incorrectly implemented specified feature makes the result Non-conformant.
Treating dispensations as permanent. They are granted for a given period and parameters, then re-assessed.