TOGAF has precise language — using the wrong word in the exam costs marks. Master the exact definitions, not paraphrases.
OGEA-101 tests whether you know the TOGAF-specific meaning of terms — not common English meanings. "View" and "Viewpoint" look similar but are completely different. "ABB" and "SBB" are often confused. Getting these right is free marks.
- ▸Exam options are designed with near-identical wording to trap paraphrasers
- ▸Many terms have counterintuitive TOGAF meanings (e.g. "Enterprise" ≠ large company)
- ▸Some terms come directly from ISO standards — the wording is legally precise
- ▸Target: know the one-line definition AND the exam trap for each key term
Use the explorer below. Filter by category, search by keyword, click any term card to reveal its full definition and exam tip:
The fundamental concepts or properties of a system in its environment embodied in its elements, relationships, and in the principles of its design and evolution.
The application of architecture disciplines to enable the development of a holistic view of the enterprise's strategy, information, processes, and IT assets.
A general rule and guideline intended to be enduring and seldom amended, that informs and supports how an organization fulfils its mission.
A foundational structure that defines a common approach and vocabulary for developing, describing, and communicating architectures.
An individual, team, organization, or class thereof having an interest or concern in the realization of the architecture.
A primary interest that pertains to system development, operation, or any other aspect that is important to one or more stakeholders.
The representation of a related set of concerns from the perspective of a stakeholder.
A specification of the conventions for constructing and using a view. A pattern or template from which to develop individual views.
A constituent of the architecture model that describes a single aspect of the overall model and defines WHAT functionality will be implemented.
A candidate physical solution or implementation component that fulfils the requirements defined by one or more Architecture Building Blocks.
A component of business, IT, or architectural capability that can be combined with other building blocks to deliver architectures and solutions.
A structure for storing and managing different classes of architectural output at different levels of abstraction.
A categorization mechanism for classifying architecture and solution artifacts, from generic (Foundation Architecture) to specific (Organization-Specific Architecture).
The architectural representation of assets in use, or planned to be in use, by the enterprise at a particular point in time.
A work product that is contractually specified and in turn formally reviewed, agreed, and signed off by the stakeholders.
An architectural work product that describes an aspect of the architecture. Artifacts are contained within deliverables.
A joint agreement between development partners and sponsors on the deliverables, quality, and fitness-for-purpose of an architecture.
The adherence of an implementation to the specifications defined in the architecture.
A cross-organizational group responsible for controlling the enterprise architecture and the architecture process, establishing and maintaining architecture governance.
A snapshot of the current state of the architecture at a point in time.
The description of a future state of the architecture to be developed for an organization.
A formal description of one state of the architecture at an architecturally significant point in time between the Baseline and Target Architecture.
A technique used to identify differences between two states — typically the Baseline Architecture and the Target Architecture — to understand what must be done to move from one to the other.
These two pairs generate the most wrong answers in OGEA-101. Master them with a simple anchor:
- ▸👁️ VIEW = the OUTPUT — the actual representation created for a stakeholder
- ▸📐 VIEWPOINT = the SPECIFICATION/TEMPLATE — the convention used to build a View
- ▸🧩 ABB (Architecture Building Block) = WHAT you NEED — defines functionality required
- ▸🔧 SBB (Solution Building Block) = WHAT you USE — the actual product/system that fulfills the ABB
- ▸Memory: "View is what you SEE; Viewpoint is how you LOOK. ABB is the need; SBB is the solution."
Two related but distinct concepts that are frequently swapped in exam options:
- ▸🗄️ ARCHITECTURE REPOSITORY = where you STORE architectural assets (the "warehouse")
- ▸🔢 ENTERPRISE CONTINUUM = how you CLASSIFY those assets from generic → specific (the "filing system")
- ▸The Repository contains the Continuum — they are not the same thing
- ▸Enterprise Continuum has two parts: Architecture Continuum + Solutions Continuum
TOGAF distinguishes three types of work products — each has a specific role:
- ▸📋 DELIVERABLE = formal output; contractually specified; formally signed off by stakeholders
- ▸🖼️ ARTIFACT = architectural work product inside a deliverable (catalogue, matrix, or diagram)
- ▸🧱 BUILDING BLOCK = reusable component (either ABB or SBB) that makes up the architecture
- ▸Hierarchy: Deliverable contains Artifacts; Artifacts describe Building Blocks