TOGAF® Standard, 10th Edition · OGEA-101 Foundation · Quick revision

Solution Building Block (SBB)

5-minute sheet
Official definition — learn word for word
“A physical or implementation-specific component that realizes part or all of one or more logical Architecture Building Blocks (ABBs).”
There are business, application, and technology SBBs (§4.73 note). SBBs represent components that will be used to implement the required capability (§3.6).
Source: CC §4.73 · CC §3.6
Memory aid
S for Solution, S for Supplier: SBBs are product- or vendor-aware.
Memory aid — not TOGAF wording.

In plain words

The actual product or component chosen to deliver an ABB.
Plain-English summary — not TOGAF wording.

Worked example

PayFlask using a specific payment gateway implements the “Online payment service” ABB; a chosen single-sign-on product implements the “Identity service” ABB.
Illustrative example (Digital University Kerala) — not from the Standard.

01Mind map — related concepts

SBB
RELATES TO
Solutions Continuum
REALIZES
Part or all of one or more ABBs
OBTAINED BY
Procured or developed
THREE KINDS
Business · Application · Technology SBBs
HELD IN
Solutions Landscape (planned or deployed)
NOT TO CONFUSE WITH
ABB (logical, supplier-independent)
Source: CC §4.73 · AC §5.2.4, §7.1

02SBB vs ABB

AspectSBBABB
LevelPhysical or implementation-specificLogical or supplier-independent
ContinuumSolutions ContinuumArchitecture Continuum
CharacteristicsDefines products/components; defines the implementation; fulfils business requirements; product or vendor-awareCaptures architecture requirements; directs and guides SBBs
Repository componentSolutions LandscapeArchitecture Landscape
Source: CC §4.9, §4.73 · AC §5.2.3, §5.2.4, §7.1

03Where it appears in the ADM

Phases B, C, D
The selected set of ABBs is refined iteratively into SBBs, bought off-the-shelf or custom developed.
AC §5.3.2
Phase G · Step 11.3.3
Guide Development of Solutions Deployment — includes “Update Enterprise Continuum directory and repository for solutions”.
ADM §11.3.3

04Exam traps

“An SBB realizes exactly one ABB” → Part or all of one or more ABBs
“SBBs are always technology” → There are business, application, and technology SBBs
“SBBs are held in the Architecture Landscape” → The Solutions Landscape represents the SBBs supporting the Architecture Landscape
“SBBs relate to the Architecture Continuum” → Solutions Continuum
“SBBs must be custom-built” → They may be either procured or developed

05Self-test — tap to reveal

Q1Define an SBB.
A physical or implementation-specific component that realizes part or all of one or more logical ABBs.
Q2Name the three kinds of SBB.
Business, application, technology.
Q3Which continuum?
Solutions Continuum.
Q4How can SBBs be obtained?
Procured or developed.
Q5Which repository component represents SBBs?
The Solutions Landscape.
Q6Are SBBs vendor-aware?
Yes — product or vendor-aware.
Q7Which Phase G step updates the repository for solutions?
Step 11.3.3 — Guide Development of Solutions Deployment.
Q8Must an SBB specification show its relationship to ABBs?
Yes — “Relationships between SBBs and ABBs” is a minimum content item.
Checked against the TOGAF Standard, 10th Edition: Introduction & Core Concepts §3.6, §4.9, §4.73 · Architecture Content §5.2.3, §5.2.4, §5.3.2, §7.1 · ADM §11.3.3. Original study notes — not exam content.