TOGAF® Standard, 10th Edition · OGEA-101 Foundation · Quick revision
Architecture Principle
Official definition — learn word for word
“A qualitative statement of intent that should be met by the architecture.”
Principles in general are “general rules and guidelines, intended to be enduring and seldom amended, that inform and support the way in which an organization sets about fulfilling its mission” (TECH §2.1).
Source: CC §4.19 (§4.61 “Principle” refers to §4.19) · TECH §2.1
Memory aid
Template = N-S-R-I. Good set = U-R-C-C-S.
N-S-R-I: Name · Statement · Rationale · Implications
U-R-C-C-S: Understandable · Robust · Complete · Consistent · Stable
Memory aid — not TOGAF wording.
In plain words
A short rule everyone agrees to follow when making architecture decisions — written down with why it matters and what it will cost to follow.
Plain-English summary — not TOGAF wording.
Worked example
Name: Single Student Record. Statement: every DUK system uses the one authoritative student record. Rationale: fewer errors, one update everywhere. Implications: the legacy exam system must be integrated or retired, and data migration needs a budget.
Illustrative example (Digital University Kerala) — not from the Standard.
01Mind map — related concepts
Architecture Principle
TEMPLATE (TABLE 2-1)
Name · Statement · Rationale · Implications
5 QUALITIES
Understandable · Robust · Complete · Consistent · Stable
HIERARCHY
Informed & constrained by Enterprise Principles
WHO
Developed by Enterprise Architects; Board approves
WHEN
Established Preliminary; confirmed in Phase A
NOT TO CONFUSE WITH
Enterprise Principles (broader, decision-making)
Source: TECH §2.1–2.4.1 · CC §3.8 · ADM §2.3.4, §3.3.7
02Enterprise Principles vs Architecture Principles
| Aspect | Enterprise Principles | Architecture Principles |
|---|---|---|
| Relate to | Decision-making throughout the enterprise | Architecture work |
| Purpose | Inform how the organization fulfils its mission; harmonize decision-making | Govern the architecture process — development, maintenance and use of the EA |
| Position | Top of the hierarchy; subsidiary principles (e.g. IT, HR) sit within them | Informed and constrained by enterprise principles; cannot overstep them |
| Link to governance | A key element in a successful Architecture Governance strategy | Critical in setting the foundation for Architecture Governance (Preliminary 2.3.4) |
Source: TECH §2.1 · CC §3.8 · ADM §2.3.4
03How principles are developed and used
Influencesmission & plans · strategic initiatives · external constraints · current systems · industry trends
shape
Developedby Enterprise Architects with key stakeholders
then
Approvedby the Architecture Board
Preliminary step 2.3.4
EstablishedIdentify and Establish Architecture Principles
Phase A step 3.3.7
ConfirmedConfirm and Elaborate Architecture Principles
Source: TECH §2.4 · ADM §2.3.4, §3.3.7
04Where it appears in the ADM
Preliminary · Step 2.3.4
Identify and Establish Architecture Principles — based on business principles; critical in setting the foundation for Architecture Governance.
ADM §2.3.4
Phase A · Step 3.3.7
Confirm and Elaborate Architecture Principles, including Business Principles — ensure definitions are current; clarify ambiguity.
ADM §3.3.7
Preliminary · Artifact
Principles Catalog is the Preliminary Phase artifact.
AC §3.6.1
05Exam traps
“A principle's name can mention a specific technology platform” → Specific technology platforms should not be mentioned in the name or statement
“Principles are first created in Phase A” → Established in Preliminary (2.3.4); confirmed and elaborated in Phase A (3.3.7)
“Architecture Principles can override enterprise principles” → They are informed and constrained by enterprise principles and cannot overstep them
“A principle is a statement only” → Template: Name, Statement, Rationale, Implications
“Principles are approved by the CIO alone” → Typically developed by Enterprise Architects with stakeholders and approved by the Architecture Board
“A good set of principles should be as large as possible” → Principles should be few in number, future-oriented, and endorsed by senior management
06Self-test — tap to reveal
Q1Define an Architecture Principle.
A qualitative statement of intent that should be met by the architecture.
Q2Name the four parts of the principle template.
Name, Statement, Rationale, Implications.
Q3Which part highlights business benefits?
Rationale.
Q4Which part answers “How does this affect me?”
Implications.
Q5Name the five qualities of a good set of principles.
Understandable, Robust, Complete, Consistent, Stable.
Q6Who approves Architecture Principles?
The Architecture Board.
Q7Which Preliminary step establishes them?
Step 2.3.4 — Identify and Establish Architecture Principles.
Q8Which Phase A step confirms them?
Step 3.3.7.