Study guide

10.3 Architecture Compliance Reviews: Conformance Levels, Process, Timing, and Checklists

TOGAF Enterprise Architecture Practitioner OGEA-103

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Exam Mechanics & Foundation Overview

1.1 OGEA-103 Exam Structure, Gradient Scoring & Open-Book Strategy 1.2 The TOGAF Standard 10th Edition Structure & Core Concepts 1.3 Enterprise Architecture in Practice: Context, Scope, and Architecture Domains 1.4 The Context for Enterprise Architecture: Purpose, Capability, Security, and the Digital Enterprise

2 Chapter 2: Preliminary Phase & Establishing the EA Capability

2.1 Preliminary Phase Objectives, Inputs, and Activities 2.2 Scope of the Enterprise and Defining the Architecture Footprint 2.3 Establishing Architecture Governance, Frameworks, and Tools

3 Chapter 3: Architecture Vision & Stakeholder Management (Phase A)

3.1 Phase A Objectives, Request for Architecture Work, and Scope Definition 3.2 Stakeholder Management: Identification, Classification, the Power/Interest Grid, and the Stakeholder Map 3.3 Business Scenarios Technique for Problem Definition and Requirements Elicitation 3.4 Architecture Vision, Communications Plan, and Statement of Architecture Work Approval

4 Chapter 4: Business Architecture (Phase B)

4.1 Phase B Objectives, Steps, and Business Modeling Approaches 4.2 Business Capabilities, Capability Mapping, and Assessment 4.3 Value Streams, Value Stream Mapping, and Capability Cross-Mapping 4.4 Business Architecture Artifacts, Gap Analysis, and Architecture Definition Document Updates

5 Chapter 5: Information Systems Architectures — Data Architecture (Phase C)

5.1 Phase C Data Architecture Objectives, Approach, and Data Principles 5.2 Conceptual, Logical, and Physical Data Models and Data Management 5.3 Data Entity/Business Function Matrix, Data Architecture Gap Analysis, and Interoperability Requirements

6 Chapter 6: Information Systems Architectures — Application Architecture (Phase C)

6.1 Phase C Application Architecture Objectives, Approach, and Baseline vs. Target First 6.2 Application Portfolio Rationalization, Component Modeling, and Application Integration 6.3 Application/Organization Matrix, Application Gap Analysis, and Boundary Definitions

7 Chapter 7: Technology Architecture (Phase D)

7.1 Phase D Objectives, Cloud & Modern Platforms, and Technology Principles 7.2 Technology Standards, the Standards Library, Platform Services, and Infrastructure Modeling 7.3 Technology Gap Analysis, Non-Functional Requirements, and Reference Models

8 Chapter 8: Opportunities and Solutions (Phase E)

8.1 Phase E Objectives, Consolidated Gap Analysis, and Work Package Formulation 8.2 Architecture Building Blocks (ABBs) to Solution Building Blocks (SBBs) Transition 8.3 Transition Architectures, Incremental Delivery, and Dependency Analysis 8.4 Architecture Roadmap Development and Trade-Off Analysis 8.5 Business Transformation Readiness Assessment and Risk Management

9 Chapter 9: Migration Planning (Phase F)

9.1 Phase F Objectives, Stakeholder Collaboration, and Governance Alignment 9.2 Business Value Assessment, Cost-Benefit Analysis, and Risk/Feasibility Scoring 9.3 Implementation and Migration Plan Deliverable, Resource Allocation, and Transition Roadmaps

10 Chapter 10: Implementation Governance (Phase G)

10.1 Phase G Objectives, Implementation Governance Structure, and Project Architecture Hand-off 10.2 Architecture Contracts: Purpose, Types, Timing, and Stakeholder Commitments 10.3 Architecture Compliance Reviews: Conformance Levels, Process, Timing, and Checklists

11 Chapter 11: Architecture Change Management (Phase H) & Requirements Management

11.1 Phase H Objectives, Drivers of Architecture Change, and Value Monitoring 11.2 Change Classification: Simplification, Incremental, and Re-Architecting Changes 11.3 Ongoing Governance, Retirement of Solutions, and Maintenance vs. New ADM Cycle 11.4 Requirements Management: Central Role, Traceability, Mid-Phase Discovery, and Scope Conflict

12 Chapter 12: Architecture Governance, Boards, and Dispensations

12.1 Architecture Governance Framework, Organizational Roles, and RACI Matrix 12.2 Architecture Board Structure, Federation, Responsibilities, and Meeting Operations 12.3 Compliance Assessment, Dispensation Process, Expiration, and Remediation Tracking 12.4 Architecture Principles, the Decision Log, and Resolving Principle Conflicts

13 Chapter 13: Architecture Content Framework & Architecture Repository

13.1 The TOGAF Content Framework and Enterprise Metamodel 13.2 Deliverables, Artifacts (Catalogs, Matrices, Diagrams), and Building Blocks (ABBs vs SBBs) 13.3 Architectural Views, Viewpoints, Stakeholder Concerns, and ISO/IEC/IEEE 42010 13.4 The Enterprise Continuum and the TOGAF 10 Architecture Repository

14 Chapter 14: EA Capability, Tailoring, and Iteration

14.1 Tailoring the ADM: Enterprise Context, Process Weight, and Agile Integration 14.2 ADM Iteration Cycles, Levels, and Classes of Architecture Engagement 14.3 Architecture Maturity Models, Capability Assessment, and EA Performance Measures 14.4 Supporting the ADM Work: The TOGAF Library, Series Guides, Patterns, and Security

10.3 Architecture Compliance Reviews: Conformance Levels, Process, Timing, and Checklists

Key Takeaways Explain This Topic AI

An Architecture Compliance review scrutinizes a specific project against established architectural criteria, spirit, and business objectives; its first goal is to catch errors early.

TOGAF's conformance levels are Irrelevant, Consistent, Compliant, Conformant, Fully Conformant, and Non-conformant, defined by comparing the features in the specification with those implemented.

Compliant means some specified features are missing but everything implemented is covered by and in accordance with the specification; Conformant means all specified features are implemented, plus some extra features that are not in accordance.

TOGAF's twelve-step review process ends with the Architecture Board and Customer accepting and signing off the review; an Architecture Review Co-ordinator administers it.

Reviews are timed at project initiation, initial design, major design changes, and ad hoc, and the checklists are tailored rather than used in full.

Last updated: October 2026

10.3 Architecture Compliance Reviews: Conformance Levels, Process, Timing, and Checklists

The TOGAF Standard describes an Architecture Compliance review as a scrutiny of the compliance of a specific project against established architectural criteria, spirit, and business objectives. A formal review process normally forms the core of an enterprise's Architecture Compliance strategy. Phase G's step "Perform Enterprise Architecture Compliance reviews" applies it to each implementation project, and the resulting Compliance Assessments are a Phase G output held in the Governance Repository. A compliance strategy is one of three elements of an effective governance strategy, together with an Architecture Board and Architecture Principles.

Why Compliance Reviews Are Held

TOGAF lists the goals of a review. First and foremost is to catch errors in the project architecture early , reducing the cost and risk of change later and shortening the project. Other goals include:

Ensure best practices are applied to architecture work.

Give an overview of the architecture's compliance with mandated enterprise standards.

Identify where the standards themselves may need 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 synergies across architecture teams.

Take advantage of advances in technology.

Communicate the status of business and technical readiness to management.

Identify key criteria for procurement, such as RFI and RFP content for COTS products.

Identify and communicate significant architectural gaps to product and service providers.

TOGAF also notes more political benefits. A review can help decide between architectural alternatives, because business decision-makers in the review favor what is best for the business. It produces one of the few measurable deliverables for executives. It gives the architecture function a way to engage projects that might otherwise bypass it.

Non-compliance is not only a failure signal. It highlights areas to realign and areas to consider for integration into the architecture . Dispensations register such changes and start a process for assessing them.

The Six Levels of Architecture Conformance

TOGAF defines conformance by comparing the features in the architecture specification with the features in the implementation . Memorize the levels in these terms:

Level What the comparison shows

Irrelevant The implementation has no features in common with the architecture specification, so the specification is irrelevant to it.

Consistent Some features are common and implemented in accordance with the specification, but some specified features are not implemented, and the implementation has other features not covered by the specification.

Compliant Some specified features are not implemented, but every feature that is implemented is covered by the specification and in accordance with it .

Conformant All specified features are implemented in accordance with the specification, but some additional features are implemented that are not in accordance with it.

Fully Conformant Full correspondence: all specified features are implemented in accordance with the specification, and nothing is implemented that the specification does not cover.

Non-conformant Any of the above in which some specified features are implemented not in accordance with the specification .

TOGAF explains that "in accordance with" means the implementation supports the stated strategy and future direction, adheres to the stated standards (including syntax and semantic rules), provides the stated functionality, and adheres to the stated principles, such as being open where appropriate and reusing building blocks.

Quick test: check whether anything specified was implemented wrongly (Non-conformant). Then check whether everything specified was implemented. Finally, check whether anything unspecified was added. A project that implements only part of the specification but adds nothing outside it is Compliant . A project that implements all of it but adds non-conforming extras is Conformant .

When to Review

TOGAF separates checkpoints for the development of the architecture itself ( ADM compliance ) from checkpoints for its implementation ( architecture compliance ). Project timings for assessments include:

  • Project initiation
  • Initial design
  • Major design changes
  • Ad hoc reviews

The review is typically targeted at a point when business requirements and the Enterprise Architecture are reasonably firm and the project architecture is taking shape, well before completion , while there is still time to correct major errors. Normally the CIO or Architecture Board mandates reviews for all major projects, with subsequent annual reviews.

Who Runs the Review

TOGAF describes three scenarios. A small project may review itself using the checklists. A project with no practicing architect may have the review led by the EA function, with business domain experts involved. Most commonly, in larger projects (the typical TOGAF scenario), the Lead Enterprise Architect coordinates the review with a team of business and technical domain experts, or a representative of the Architecture Board leads it.

Roles and the Twelve-Step Process

Roles: Architecture Board; Project Leader (or Project Board); Architecture Review Co-ordinator , who administers the process and is more likely business-oriented than technology-oriented; Lead Enterprise Architect; Architect; Customer; Business Domain Expert; and Project Principals.

Steps:

Request architecture review (anyone with an interest in the business area may request it, as mandated by governance policies)

  • Identify the responsible part of the organization and the relevant project principals (Review Co-ordinator)
  • Identify the Lead Enterprise Architect and other architects (Review Co-ordinator)
  • Determine the scope of the review (Review Co-ordinator)
  • Tailor the checklists to address the business requirements (Lead Enterprise Architect)
  • Schedule the Architecture Review Meeting (Review Co-ordinator with the Lead Enterprise Architect)

Interview project principals, using the checklists (Lead Enterprise Architect and/or Architect, Project Leader, and Customers)

Analyze completed checklists against corporate standards and determine recommendations (Lead Enterprise Architect)

  • Prepare the Architecture Compliance review report (Lead Enterprise Architect)
  • Present review findings to the Customer and the Architecture Board (Lead Enterprise Architect)
  • Accept the review and sign off (Architecture Board and Customer)
  • Send the assessment report or summary to the Review Co-ordinator (Lead Enterprise Architect)

TOGAF also mentions a model-based alternative. Solution architects trace their elements to the Enterprise Architecture model through "drill-down" diagrams, so tools can partly automate conformance checks.

The Compliance Review Checklists

TOGAF provides example checklists covering:

  • Hardware and Operating System
  • Software Services and Middleware
  • Applications (infrastructure and business-specific)
  • Information Management
  • Security
  • System Management
  • System Engineering/Overall Architecture
  • System Engineering/Methods and Tools

The checklists deliberately contain too many questions for any single review . They are meant to be tailored to the project, typically by subject matter experts, and updated annually by interest groups. They are designed for individual projects; a review across several processes or projects would use different categories.

After the Review

The Architecture Board and the customer accept and sign off the review. Where an implementation is not compliant, TOGAF's governance framework gives two routes: adjust or realign the design to meet the requirements, or request a dispensation . Dispensations are granted for a given time period with identified service and operational criteria that must be enforced while they last, and their time-bound nature makes them a trigger in the compliance cycle (Section 12.3). Compliance assessments are recorded in the Governance Repository.

Common Exam Traps

Using informal "mandatory versus optional" definitions. TOGAF's levels compare specified features with implemented features. Decide on that basis.

Reviewing only at go-live. TOGAF targets reviews well before completion, while errors can still be fixed.

Using every checklist question. The checklists are meant to be tailored.

Treating a dispensation as permanent. Dispensations are time-bound and trigger later compliance activity.

Loading diagram... TOGAF Architecture Compliance Review Process