TOGAF EA Foundation · Plain-English terminology

TOGAF Foundation Terminology That Confuses Beginners

TOGAF becomes much easier when you stop treating every unfamiliar word as a separate fact to memorise. Many Foundation terms come in related pairs or groups. The real task is to understand the relationship between them.

The Open Group describes shared terminology as one of the core competencies of TOGAF Enterprise Architecture Foundation. That makes vocabulary important, but the useful skill is not reciting a glossary. It is knowing why two similar terms are not interchangeable.[1]

Use this rule

Learn confusing terms as contrasts, not isolated definitions.

If you can explain the difference between two nearby concepts in plain English, you are much less likely to be distracted by similar-looking answer options.

The quick-reference version

Scroll sideways to compare all three columns.

TermsPlain-English distinctionMemory cue
ADM / phaseThe ADM is the overall method. A phase is one part of that method.Method → stages
View / viewpointA viewpoint defines how to construct a particular kind of view. The view is the resulting representation.Viewpoint = rules; view = result
Deliverable / artefact / building blockA deliverable is a formal work product. An artefact describes an aspect of the architecture. A building block represents a reusable package of capability or solution content.Package / description / reusable element
ABB / SBBAn Architecture Building Block describes required capability at the architecture level. A Solution Building Block describes how that capability is realised in a solution.What is needed / how it is implemented
Baseline / Target / TransitionBaseline is where you are. Target is where you want to be. A Transition Architecture is an intermediate state on the way there.Now / later / in between
Architecture Repository / Enterprise ContinuumThe Repository stores architecture assets. The Enterprise Continuum provides a way to classify and understand architecture and solution assets from generic to organisation-specific.Store / classify
Architecture / Architecture CapabilityThe architecture describes the enterprise and its intended change. Architecture Capability is the organisation's ability to perform architecture work.The work / ability to do the work

1. ADM vs an ADM phase

ADM means Architecture Development Method. It is the overall TOGAF method for developing and governing Enterprise Architecture. The phases are the parts of that method.

Phase A, for example, is Architecture Vision. Phase B covers Business Architecture. They are not separate methods. They are stages within the ADM.

A useful mental model is a journey and its stages: ADM = the whole route; phases = the stages along it.

Where beginners get caught

It is easy to memorise the ADM diagram as a sequence of letters and miss what the diagram represents. Foundation questions become easier when you connect each phase to its purpose rather than treating the phase name as a label.

2. View vs viewpoint

This pair sounds almost identical, but the relationship is straightforward.

A viewpoint defines the conventions for a particular kind of architecture view: what concerns it addresses, what information is relevant, and how that information should be represented. A view is the representation created using that viewpoint.

Think of the viewpoint as the specification and the view as the instance produced from it.

Simple example

A stakeholder wants to understand application dependencies. The viewpoint defines how an application-dependency view should be constructed. The actual diagram showing this organisation's applications and dependencies is the view.

3. Deliverable vs artefact vs building block

These three terms are close because all of them relate to architecture content.

A deliverable is a formal work product that is contractually specified and reviewed or signed off. It can contain several pieces of architecture content.

An artefact describes an aspect of the architecture. Catalogues, matrices and diagrams are common forms of artefact.

A building block is a potentially reusable package of functionality or capability used in defining or realising an architecture.

Keep the levels separate

A deliverable can contain artefacts. Artefacts can describe building blocks. The three terms therefore relate to one another, but they describe different things.

4. Architecture Building Block vs Solution Building Block

An Architecture Building Block (ABB) describes what capability is required at the architecture level. A Solution Building Block (SBB) describes how that capability will be realised in the implemented solution.

For example, an architecture may require secure customer authentication. That requirement can be expressed at the ABB level without choosing a particular product. The eventual SBB could identify the specific identity service, product or implementation used to provide it.

The distinction is therefore not “conceptual thing versus technical thing”. It is closer to required capability versus solution realisation.

5. Baseline vs Target vs Transition Architecture

Baseline Architecture describes the relevant current state. Target Architecture describes the desired future state.

A Transition Architecture describes an intermediate state when the organisation cannot move directly from Baseline to Target in one step.

If a company is replacing several legacy applications over three years, the final intended landscape is the Target Architecture. A stable intermediate landscape after year one may be represented as a Transition Architecture.

The easiest memory cue is: Baseline = now, Target = destination, Transition = a meaningful stop on the way.

6. Architecture Repository vs Enterprise Continuum

This is one of the more abstract Foundation distinctions.

The Architecture Repository is the concept used to organise and store architecture-related outputs and reusable assets. The Enterprise Continuum provides a way to classify architecture and solution assets in context, including movement from generic material toward organisation-specific material.

The 10th Edition ADM guidance describes the practical implementation of the Enterprise Continuum as typically taking the form of an Architecture Repository containing reusable reference architectures, models, patterns and previous architecture work.[2]

For Foundation study, a useful simplification is: Repository = where assets are managed; Continuum = how you think about and classify their context and specificity.

7. Architecture vs Architecture Capability

Enterprise Architecture is concerned with the structures, relationships and changes needed to support the enterprise.

Architecture Capability is the organisation's ability to do architecture work effectively. That includes roles, responsibilities, governance, processes, skills and supporting structures.

If an organisation defines a target application landscape, that is architecture work. If it decides who its architects are, how architecture decisions are governed and how the practice operates, that is part of establishing the Architecture Capability.

Two terminology traps that are not really TOGAF concepts

“TOGAF 10 Foundation”

You will see this phrase online, but it is not the current formal certification name. The standard is the TOGAF Standard, 10th Edition. The certification is TOGAF Enterprise Architecture Foundation. The Open Group deliberately separated certification names from the edition number.[3]

TOGAF vs ArchiMate

TOGAF is not a modelling notation. The TOGAF Standard provides a method, structure and governance approach for Enterprise Architecture. The ArchiMate language is a separate standard used to model and communicate architecture visually. They can be used together, but they are not the same framework under two names.[4]

How to study terminology without drowning in definitions

Do not build a glossary with one isolated definition per line. Build a contrast list.

This works particularly well for Foundation because the official exam is designed to assess knowledge and understanding of core concepts, terminology, ADM, governance and architecture content.[5]

The useful test

Can you explain the difference without quoting the glossary?

If you can explain “view versus viewpoint” or “deliverable versus artefact” to someone who has never read TOGAF, you probably understand the distinction well enough to recognise it in a question.

Official sources

  1. The Open Group — Competency-to-Role Mapping: TOGAF Enterprise Architecture Foundation
  2. The Open Group — TOGAF Standard, 10th Edition, Architecture Development Method guidance on the Enterprise Continuum and Architecture Repository
  3. The Open Group — Why there is no “TOGAF 10 Foundation” or “TOGAF 10 Practitioner”
  4. The Open Group — How the ArchiMate Language and the TOGAF Standard complement each other
  5. The Open Group — OGEA-101 exam plan

Need a structure for the rest of Foundation?

Use the beginner study plan to put these terms into the ADM, governance and architecture-content topics they belong to.

Open the Foundation study plan