Clarifying Definitions in TOGAF 9 Architecture Compliance

To understand the compliance definition in full clarity, it is better to draw the separation between Architecture Specification and Architecture Implementation and then  lift off from the existing Venn diagram (TOGAF 9 - chapter 48) the Features as a new dimension, as indicated as S (specification) and I (implementation) in the following Vend diagram:

For the new dimension mentioned, we use S to represent feature Specified and I to represent feature Implemented, so that we can now apply the "IN ACCORDANCE WITH" test on their relevancy.

In effect, we can also see clearly that the barrier for the promotion from the architecture "Compliant" level to the architecture "Conformant" level, and that happens when you have  FULL ACCORDANCE COVERAGE of the entire scope of Architecture Specification, regardless  of the fact that you may have one or more orphan implemented features (features that are NOT specified in the Architecture scope).

Definition of Non-conformant is now Better Understood

Then bringing the meaning of non-conformant to light is much easier and simply by identifying relevant architecture implementation features that are NOT IN ACCORDANCE with the corresponding Specification within the architecture scope.

Here to shed light on Non-conformant,  = is used to represent "Implementation is In Accordance with Specification" and != is used to represent "Implementation is NOT IN ACCORDANCE with specification"

So the threshold for determining non-conformant is when you have at least one relevant feature that fails to be "IN ACCORDANCE" between the implementation and the specification.

Before I wrote my TOGAF 9 exam, I had a hard time understanding the associated description for "non-conformant" in this TOGAF 9 Section in charpter 48.  since the description is a bit flat.  I hope this clarity for Conformant versus Non-conformant definition by adding the Feature dimension will help members who are about to write the TOGAF 9 exams.

TOGAF Architecture Compliance Model in Pure UML

Based on the analysis using the Venn diagram, we can express the TOGAF Architecture Compliance Model in pure UML as follow: