TOGAF® Standard, 10th Edition · OGEA-101 Foundation · Quick revision
Architecture Contract
No Chapter 4 definition — closest official wording
“Architecture Contracts are the joint agreements between development partners and sponsors on the deliverables, quality, and fitness-for-purpose of an architecture.”
Successful implementation of these agreements will be delivered through effective Architecture Governance.
Source: CG §5.1 · AC §4.2.2 — Chapter 4 has no “Architecture Contract” entry
Memory aid
Three contracts, three moments: SoAW (Phase A) → Partners (as work is contracted out) → Business stakeholders (end of Phase F).
Memory aid — not TOGAF wording.
In plain words
A signed agreement on what the architecture will deliver, to what quality, and how the parties will work together.
Plain-English summary — not TOGAF wording.
Worked example
Before build starts in Phase G, CDIPD and the PayFlask vendor sign a contract listing the target payment architecture, the conformance requirements and the review milestones.
Illustrative example (Digital University Kerala) — not from the Standard.
01Mind map — related concepts
Architecture Contract
BETWEEN
Development partners and sponsors
COVERS
Deliverables · quality · fitness-for-purpose
PHASE G
Documented and signed (output: signed contract)
MONITORED BY
The Architecture Board (monitoring and control)
PHASE H
Business stakeholder contract manages change
NOT TO CONFUSE WITH
A dispensation or a compliance review
Source: CG §4.2, §5.1–5.3 · ADM §11.3.3, §11.4
02The three kinds of Architecture Contract (CG §5.2)
| Kind | Between | When |
|---|---|---|
| Statement of Architecture Work | Architecting organization and the sponsor of the EA (or IT governance function) | Created as a deliverable of Phase A |
| Architecture Design and Development contract | The enterprise and partner organizations — systems integrators, application providers, service providers | At the ADM stage where work is contracted out; template defined in the Preliminary Phase |
| Contract with business stakeholders | The architecting function and the business stakeholders who will build and deploy the architected solutions | When the Implementation and Migration Plan is agreed (end of Phase F); also used to manage changes in Phase H |
Source: CG §5.1, §5.2.1–5.2.3
03The contract across the ADM
Preliminarycontract template normally defined (if not existing)
Phase A · 3.3.11Statement of Architecture Work — effectively a contract
End of Phase Fcontract with business stakeholders may be drawn up
Phase G · 11.3.3Document Architecture Contract; obtain signature from all developing and sponsoring organizations
Phase Hbusiness stakeholder contract used to manage changes
Source: CG §5.1, §5.2 · ADM §3.3.11, §11.3.3
04Where it appears in the ADM
Phase G · Step 11.3.3
Guide Development of Solutions Deployment — Document Architecture Contract; obtain signature from all developing organizations and sponsoring organization.
ADM §11.3.3
Phase G · Inputs / Outputs
Input: Architecture Contract (standard). Output: Architecture Contract (signed).
ADM §11.2.3, §11.4
Phase H · Inputs / Outputs
Architecture Contract (signed) is an input; the Architecture Contract is an output, updated if necessary.
ADM §12.2.3, §12.4
05Exam traps
“Architecture Contracts only exist in Phase G” → They may occur at various stages — the Phase A Statement of Architecture Work is effectively one
“The contract is only between the sponsor and the IS department” → That is the traditional form; increasingly it covers all parties, incl. integrators and service providers
“Only the Architecture Board signs the contract” → Phase G: obtain signature from all developing organizations and the sponsoring organization
“The business stakeholder contract is drawn up in Phase A” → When the Implementation and Migration Plan is agreed, at the end of Phase F
“Monitoring the contract is the project manager's job” → All aspects of monitoring and control of the contract are an Architecture Board responsibility
06Self-test — tap to reveal
Q1What are Architecture Contracts?
Joint agreements between development partners and sponsors on the deliverables, quality, and fitness-for-purpose of an architecture.
Q2Which Phase A deliverable is effectively a contract?
The Statement of Architecture Work.
Q3Name the three kinds of contract.
Statement of Architecture Work; Design and Development partners contract; contract with business stakeholders.
Q4When is the business stakeholder contract drawn up?
When the Implementation and Migration Plan is agreed (end of Phase F).
Q5Which Phase G step documents the contract?
Step 11.3.3.
Q6Who signs in Phase G?
All developing organizations and the sponsoring organization.
Q7Where is the contract template normally defined?
In the Preliminary Phase.
Q8Which body monitors and controls the contract?
The Architecture Board.