Overview
Architecture Content is about what the ADM produces and how it is expressed. It starts with the vocabulary for communicating architecture to people. Stakeholders have concerns; a viewpoint defines how to construct a kind of view that frames certain concerns; a view is the representation, built to that viewpoint, that addresses them. These ideas come from ISO/IEC/IEEE 42010 and decide how architecture is presented to each audience.
The unit then covers building blocks, the reusable components that architectures are made of. Architecture Building Blocks capture requirements; Solution Building Blocks are the product-aware components that realize them. The largest outcome is the set of sixteen named deliverables, from the Request for Architecture Work and Statement of Architecture Work to the Architecture Contract, Compliance Assessment and Requirements Impact Assessment. For each, know its purpose and the phases that create and consume it.
How it's tested
Questions here are definition and placement items. A stem describes a document's purpose and asks which deliverable it is, names a deliverable and asks which phase produces it, or contrasts view and viewpoint or Architecture and Solution Building Blocks. The options are usually all real TOGAF deliverables or terms.
-
Deliverable from purpose
The stem describes what a document does, such as recording the impact of a requirements change, and you pick the deliverable. One word in the description, such as 'impact', 'scope' or 'quantitative', usually decides it.
-
Deliverable to phase
A deliverable is named and you choose the phase that creates or finalizes it, for example Implementation Governance Model in Phase F or Compliance Assessment in Phase G.
-
Pair distinction
Two related terms are contrasted, such as view versus viewpoint or ABB versus SBB, and you pick the statement that describes one of them correctly.
A stem asks which deliverable contains measurable criteria that must be met when implementing the architecture, such as performance targets and interface standards. The Architecture Definition Document is tempting because it is the main design document. But the ADD is qualitative and describes the architecture; the quantitative statements that implementation must meet belong in the Architecture Requirements Specification. The word 'measurable' is the clue.
Learning outcomes 3
Official learning outcomes from the The Open Group outline, in outline order.
7.1 Define stakeholders, concerns, views and viewpoints and the links between themWho cares, what they care about, and how architecture is shown to them.
- What it means
- A stakeholder is an individual, team, organization or class of these with interests in, or concerns about, the outcome of the architecture. A concern is an interest relevant to one or more stakeholders. A viewpoint is a specification of the conventions for constructing and using a kind of view to address particular concerns. A view is a representation of the system from the perspective of a related set of concerns, built according to a viewpoint.
- What to understand
- The links run: stakeholders have concerns; viewpoints frame concerns; views conform to viewpoints and address the stakeholders' concerns. A viewpoint is reusable, like a template; a view is the specific output for a specific architecture.
- How it shows up
- A stem asks which term describes the conventions and techniques used to build a particular kind of representation: viewpoint.
- Common confusion
- Swapping view and viewpoint; the viewpoint is where you look from and the rules, the view is what you see.
7.2 Explain what building blocks are and their use in the ADMReusable components: ABBs capture requirements, SBBs realize them.
- What it means
- A building block is a package of functionality defined to meet business needs, with a defined boundary and published interfaces, that can be reused and replaced and may interoperate with other building blocks. TOGAF distinguishes Architecture Building Blocks (ABBs), which capture architecture requirements and guide development, from Solution Building Blocks (SBBs), which are product- or vendor-aware components that implement them.
- What to understand
- ABBs are identified and refined in Phases A to D and sit in the Architecture Continuum. SBBs are identified from Phase E onwards, as solutions are chosen, and sit in the Solutions Continuum. One ABB may be realized by different SBBs over time.
- How it shows up
- A stem describes a component defined by required capability with no product named, and asks whether it is an ABB or an SBB: an ABB.
- Common confusion
- Thinking ABBs are smaller or simpler SBBs, rather than the requirement-level description that SBBs implement.
7.3 Describe the TOGAF deliverables created and consumed in different ADM phasesSixteen deliverables, each with a purpose and a place in the cycle.
- What it means
- The Foundation syllabus names sixteen deliverables: Architecture Contract, Architecture Definition Document, Architecture Principles, Architecture Requirements Specification, Architecture Roadmap, Architecture Vision, Business Principles, Business Goals and Business Drivers, Capability Assessment, Change Request, Communications Plan, Compliance Assessment, Implementation and Migration Plan, Implementation Governance Model, Request for Architecture Work, Requirements Impact Assessment and Statement of Architecture Work.
- What to understand
- Learn them in cycle order. The Request for Architecture Work and the business principles, goals and drivers come in at the start, and Architecture Principles come from the Preliminary Phase. Phase A produces the Statement of Architecture Work, Architecture Vision, Communications Plan and Capability Assessment. Phases B to D develop the Architecture Definition Document and Architecture Requirements Specification. Phases E and F produce the Architecture Roadmap and Implementation and Migration Plan, and F the Implementation Governance Model. Phase G uses Architecture Contracts and Compliance Assessments. Change Requests and Requirements Impact Assessments arise in Phase H and Requirements Management.
- How it shows up
- A stem asks which deliverable defines how the implementation of the architecture will be governed and is produced in Phase F: the Implementation Governance Model.
- Common confusion
- Assigning a deliverable to the phase that uses it rather than the phase that creates it, or confusing look-alike pairs such as the Roadmap and the Implementation and Migration Plan.
High-yield concepts
The terms, rules and formulas this domain turns into questions most often.
-
View vs. viewpoint
A viewpoint specifies the conventions for building a kind of view to frame certain concerns; a view is the actual representation of a system built to that viewpoint.
- Remember
- Viewpoint is the reusable template; the view is the specific output for one architecture.
- Tested as
- The most common pair-distinction question in this unit.
- Trap
- Saying a viewpoint is what the stakeholder sees.
-
Stakeholder and concern
A stakeholder has interests in the architecture's outcome, and those interests are expressed as concerns that views must address.
- Remember
- Concerns link stakeholders to the viewpoints and views chosen for them.
- Tested as
- Definition items in outcome 7.1.
- Trap
- Treating concerns as risks or issues logs.
-
Architecture Building Block
A building block that captures architecture requirements and directs the development of solutions without naming products.
- Remember
- Defined in Phases A to D; sits in the Architecture Continuum.
- Tested as
- ABB versus SBB questions.
- Trap
- Naming a vendor product as an ABB.
-
Solution Building Block
A product- or vendor-aware component that implements one or more ABBs.
- Remember
- Identified from Phase E onwards; sits in the Solutions Continuum.
- Tested as
- ABB versus SBB questions.
- Trap
- Thinking SBBs are defined before the architecture.
-
Statement of Architecture Work
The Phase A deliverable that defines the scope, approach and plan of the architecture effort and is approved by the sponsor.
- Remember
- It responds to the Request for Architecture Work and acts as a contract with the sponsor.
- Tested as
- Purpose and phase questions.
- Trap
- Confusing it with the Request for Architecture Work.
-
Architecture Definition Document vs. Architecture Requirements Specification
The Architecture Definition Document holds the qualitative description of baseline and target architectures; the Architecture Requirements Specification holds the quantitative statements implementation must meet.
- Remember
- Both are developed in Phases B to D.
- Tested as
- Classic look-alike pair.
- Trap
- Putting measurable criteria in the ADD.
-
Architecture Roadmap vs. Implementation and Migration Plan
The roadmap lists work packages and their timeline toward the target; the Implementation and Migration Plan gives the detailed schedule, resources and delivery approach.
- Remember
- Initial versions in Phase E, finalized in Phase F.
- Tested as
- Purpose and phase questions.
- Trap
- Treating them as one document.
-
Implementation Governance Model
A Phase F deliverable that sets out how implementation will be governed, including organization, roles and processes for oversight.
- Remember
- Created in F, used in G.
- Tested as
- Placement questions.
- Trap
- Placing it in Phase G because that is where governance happens.
-
Architecture Contract and Compliance Assessment
The contract records agreement on deliverables and quality with implementation partners; the assessment records the results of compliance reviews.
- Remember
- Both belong to Phase G.
- Tested as
- Placement and purpose questions.
- Trap
- Thinking the contract is a vendor purchase agreement.
-
Change Request vs. Requirements Impact Assessment
A Change Request asks for a change to the architecture; a Requirements Impact Assessment evaluates how a change to requirements affects the architecture and the phases.
- Remember
- Impact assessments come from Requirements Management and Phase H.
- Tested as
- Purpose-matching questions.
- Trap
- Choosing Change Request whenever the word 'change' appears.
-
Capability Assessment and Communications Plan
The Capability Assessment describes the baseline and target capability levels and readiness of the enterprise; the Communications Plan sets how architecture information reaches stakeholders.
- Remember
- Both are produced in Phase A.
- Tested as
- Phase A output questions.
- Trap
- Placing the Communications Plan in Phase G.
-
Request for Architecture Work
The document from the sponsoring organization that triggers an ADM cycle.
- Remember
- Input to the Preliminary Phase or Phase A; Phase H can produce a new one.
- Tested as
- Start-of-cycle questions.
- Trap
- Thinking architects produce it in Phase A.
Side by side
Concepts candidates mix up, compared on the point that decides the answer.
View vs. viewpoint
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Viewpoint | Conventions, techniques and model kinds for constructing a kind of view for given concerns | Reusable specification; where you look from | Describing it as the diagram itself |
| View | A representation of a specific system addressing a set of concerns | Concrete output built to a viewpoint; what you see | Describing it as the reusable template |
Architecture Building Block vs. Solution Building Block
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Architecture Building Block | Captures requirements and guides solution development | Product-independent; Phases A to D; Architecture Continuum | Naming products as ABBs |
| Solution Building Block | Product- or vendor-aware component that implements ABBs | Concrete; Phase E onwards; Solutions Continuum | Defining SBBs before ABBs |
Architecture Definition Document vs. Architecture Requirements Specification
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Architecture Definition Document | Qualitative description of the baseline and target architectures across domains | Describes the architecture | Adding measurable implementation criteria |
| Architecture Requirements Specification | Quantitative statements the implementation must meet to comply | Measurable criteria and requirements | Treating it as a narrative design document |
Architecture Roadmap vs. Implementation and Migration Plan
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Architecture Roadmap | Work packages and timeline from baseline to target, including Transition Architectures | What changes and in what order | Expecting resourcing detail here |
| Implementation and Migration Plan | Detailed schedule, resources, approach and dependencies for delivering the roadmap | How and when it will be delivered | Treating it as the same document as the roadmap |
Exam traps
Each trap is an answer that looks right. Learn the clue that should change your mind.
-
Viewpoint is what you see
- What candidates pick
- Viewpoint as the representation that addresses a stakeholder's concerns.
- Why it looks right
- In everyday language, a viewpoint is a perspective someone sees.
- Why it's wrong
- In TOGAF the viewpoint is the specification of conventions; the view is the actual representation built to it.
Clue to watch for 'Conventions', 'template' or 'how to construct' means viewpoint; 'representation of the system' means view.
-
Products as ABBs
- What candidates pick
- A named database product as an Architecture Building Block.
- Why it looks right
- It is a reusable component of the architecture.
- Why it's wrong
- Anything product- or vendor-specific is a Solution Building Block; ABBs describe required capability without naming products.
Clue to watch for A brand or product name always points to an SBB.
-
Measurable criteria in the ADD
- What candidates pick
- Architecture Definition Document for a list of quantitative requirements and interface standards.
- Why it looks right
- The ADD is the main architecture deliverable.
- Why it's wrong
- Quantitative, measurable criteria for implementation belong in the Architecture Requirements Specification.
Clue to watch for 'Measurable', 'quantitative' or 'criteria for compliance' means Architecture Requirements Specification.
-
Change Request for every change
- What candidates pick
- Change Request for a document that evaluates how a requirements change affects the architecture.
- Why it looks right
- The stem is about change.
- Why it's wrong
- Evaluating the effect of changed requirements is the Requirements Impact Assessment; a Change Request is the request itself.
Clue to watch for 'Assess the impact' points to the Requirements Impact Assessment.
-
Governance model in Phase G
- What candidates pick
- Phase G as the phase that creates the Implementation Governance Model.
- Why it looks right
- Phase G is Implementation Governance.
- Why it's wrong
- The model is prepared in Phase F so governance is ready when implementation starts; Phase G uses it.
Clue to watch for 'Created' or 'prepared' points to F; 'applied' or 'used' points to G.
-
Request versus Statement
- What candidates pick
- Request for Architecture Work as the Phase A output approved by the sponsor.
- Why it looks right
- Both start the architecture effort and have similar names.
- Why it's wrong
- The Request comes from the sponsor and triggers Phase A; the Statement of Architecture Work is produced in Phase A and approved.
Clue to watch for 'Triggers' or 'initiates' means Request; 'defines scope and approach' and 'approved' means Statement.
Answer framework
Use these steps to identify a deliverable or content term from its description.
- Decide whether the stem is about communicating architecture to people (stakeholders, concerns, views), reusable components (building blocks) or a named deliverable with a defined purpose.
- For communication terms, ask whether it is the reusable specification (viewpoint) or the concrete representation (view).
- For building blocks, check for product or vendor names: none means an Architecture Building Block, while a named product or vendor means a Solution Building Block.
- For deliverables, find the key word, such as triggers, scope, qualitative, measurable, work packages, schedule, governance, agreement, review results or impact.
- Confirm the phase that creates the deliverable, not just the one that later uses or refines it, before choosing the answer.
Practice question
Want more like this? The TOGAF EA Foundation practice test has questions for every domain.
Checklist
0 of 13
Tick each one you can do without notes. Your ticks stay in this browser.
Study strategy
Start with outcome 7.1, because the four terms are short and the links between them are easy to sketch: stakeholder, concern, viewpoint, view. Draw them as a chain and label each arrow with its relationship, such as 'has', 'frames', 'conforms to' and 'addresses'. Then learn building blocks, keeping one rule in mind: no product name means ABB, product name means SBB.
Spend most of your time on outcome 7.3, the deliverables, since it drives most of this unit's five questions. Do not learn them alphabetically. Lay them out in ADM cycle order, from the Request for Architecture Work through Phase A outputs, the B to D design documents, the E and F planning documents, and Phase G governance documents, to Phase H change documents. Write one purpose phrase for each.
The commonly underestimated areas are the look-alike pairs: ADD versus Architecture Requirements Specification, Roadmap versus Implementation and Migration Plan, Request versus Statement of Architecture Work, and Change Request versus Requirements Impact Assessment. Make a two-column table for each pair.
Afterwards, revisit the ADM unit and answer its 'which phase' questions using the deliverables as clues. Then practise purpose-to-deliverable questions until each takes under a minute.
FAQ
How many questions come from Architecture Content?
The official OGEA-101 exam plan allocates 5 of the 40 questions to this unit, which is 12.5% of the paper, drawn from just three learning outcomes.
What is the difference between a view and a viewpoint?
A viewpoint specifies the conventions for building a particular kind of view to address certain concerns. A view is the actual representation of a system built according to that viewpoint.
How do ABBs and SBBs differ?
Architecture Building Blocks describe required capability and guide development without naming products. Solution Building Blocks are the product- or vendor-aware components that implement them.
Do I need to know all sixteen deliverables?
Yes. Outcome 7.3 names all sixteen, so expect questions on the purpose of each and the phases that create and consume them.
What is the difference between the Architecture Roadmap and the Implementation and Migration Plan?
The roadmap lists the work packages and their sequence toward the target. The Implementation and Migration Plan adds the detailed schedule, resources and delivery approach. Both are started in Phase E and finalized in Phase F.
Where do the viewpoint and view concepts come from?
The TOGAF Standard aligns these terms with the international standard ISO/IEC/IEEE 42010 for architecture description.
How long should I study this unit?
As a planning estimate, about 4 to 6 hours of a 40-hour plan, most of it spent on the deliverables and their phases.
Other Enterprise Architecture & IT Governance certifications
Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.
Test your Domain 6 knowledge
You have just mapped views to viewpoints, ABBs to SBBs and each of the sixteen deliverables to its phase. Check that you can name a deliverable from a one-line description of its purpose.
Keep going
- Training Training Built on your Weak areas
- Practice test Questions by domain, with explanations
- Mock exam Full length, timed like the real exam
- Readiness test Find your weakest domain in minutes
- Cheat sheet Key terms and formulas on one page
- Ask the TOGAF EA Foundation AI tutor Get any concept explained your way