Terminology: The Meaning of Architecture Compliance Knowledge-Based Study

Study notes

1. Overview of Architecture Compliance

   Architecture compliance is a core mechanism within enterprise architecture governance. It ensures that business transformation projects, procurement decisions, and solution implementations align with established architectural standards, principles, and target models.

   A critical responsibility of an Architecture Review Board (ARB) is conducting formal compliance reviews. To evaluate solutions objectively and avoid arbitrary decisions, the TOGAF standard establishes precise terminology defining different degrees of adherence to an architecture specification.

   The Defined Compliance Terminology

   The TOGAF Standard categorizes adherence into distinct levels ranging from total separation to absolute one-to-one fidelity:

   • Irrelevant: The implementation has no features in common with the architecture specification (the specification does not apply to this implementation).
   • Consistent: The implementation has features in common with the architecture specification, but also distinct features that differ without direct contradiction, showing general harmony of direction.
   • Compliant: Some features from the specification may be omitted, but all implemented features adhere strictly to the specification.
   • Conformant: All features in the architecture specification are implemented, but the implementation may also include additional features not covered by the specification.
   • Fully Conformant: The implementation adheres strictly to the specification with no omissions and no additional features (an exact one-to-one correspondence).
   • Non-conformant: Features in the implementation do not adhere to the architecture specification where they overlap, resulting in direct conflict or deviation.

   Comparing Degrees of Adherence

   Understanding the precise mathematical and logical relationships between the target specification and the actual implementation helps eliminate common governance misconceptions:

   • Compliant vs. Conformant: A compliant implementation may omit certain specification items but never violates the ones it adopts. A conformant implementation implements everything specified, plus potentially extra elements.
   • Conformant vs. Fully Conformant: A fully conformant solution neither adds nor omits any feature; it matches the specification exactly. A conformant solution guarantees that all required specifications are met but permits scope additions.
   • Consistent vs. Compliant: A consistent state reflects common ground and compatibility in philosophy or design, whereas compliance requires rigorous, verified adherence for every implemented element.
   • Irrelevant vs. Non-conformant: An irrelevant solution simply falls outside the scope of the architecture standard, whereas a non-conformant solution falls within scope but actively violates or fails the requirements.

   Applying Terminology in Governance

   During an Architecture Compliance Review, identifying the exact compliance level determines the governance outcome and required remedial actions:

   • Acceptance and Dispensation: If an implementation is compliant (with omissions) or conformant (with extensions), the ARB evaluates whether a formal architecture dispensation is warranted or if the architecture roadmap should be updated.
   • Escalation and Remediation: When a solution is evaluated as non-conformant, remediation plans, redesigns, or contractual adjustments must be triggered prior to production deployment.
   • Continuous Improvement: Regularly assessing compliance levels provides visibility into technical debt, architecture gaps, and opportunities to evolve standards based on emerging project patterns.