Study guide

3.2 Terms for Work Products, Models, Requirements & Change

TOGAF Enterprise Architecture Foundation OGEA-101

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Enterprise Architecture & the TOGAF Standard

1.1 The Enterprise, the Purpose of EA & Its Benefits 1.2 Why the TOGAF Standard: Framework, Documentation Set & Certification 1.3 The Four Architecture Domains & Architecture Abstraction

2 Chapter 2: Enterprise Continuum, Architecture Repository, Content Framework & Capability

2.1 The Enterprise Continuum 2.2 The Architecture Repository 2.3 The TOGAF Content Framework & Enterprise Metamodel 2.4 Architecture Capability

3 Chapter 3: Key TOGAF Terminology

3.1 Terms for Architecture Domains, Levels, States & Capability 3.2 Terms for Work Products, Models, Requirements & Change

4 Chapter 4: ADM Fundamentals, Preliminary Phase & Phase A

4.1 The ADM Cycle, Its Phases & Information Flow 4.2 Draft vs. Approved Deliverables & the Iterative ADM 4.3 Governing EA, Scoping the Architecture & Alternatives 4.4 The Preliminary Phase 4.5 Phase A: Architecture Vision

5 Chapter 5: Architecture Definition — Phases B, C & D

5.1 Phase B: Business Architecture 5.2 Phase C: Information Systems Architectures — Data & Application 5.3 Phase D: Technology Architecture

6 Chapter 6: Opportunities, Migration Planning & Implementation Governance (Phases E, F & G)

6.1 Phase E: Opportunities & Solutions 6.2 Phase F: Migration Planning 6.3 Phase G: Implementation Governance

7 Chapter 7: Phase H, Requirements Management & Agile Delivery

7.1 Phase H: Architecture Change Management 7.2 Requirements Management 7.3 Supporting Agile Software Development with the ADM

8 Chapter 8: ADM Techniques I — Guidelines, Principles, Business Scenarios & Gap Analysis

8.1 ADM Guidelines & Techniques and Architecture Principles 8.2 Business Scenarios 8.3 Gap Analysis

9 Chapter 9: ADM Techniques II — Interoperability, Transformation Readiness & Risk

9.1 Interoperability 9.2 Business Transformation Readiness Assessment 9.3 Risk Management

10 Chapter 10: Applying the ADM

10.1 Guidance for Applying TOGAF, Iteration & Concurrent Phases 10.2 The Architecture Landscape: Strategic, Segment & Capability Levels 10.3 Architecture Partitioning 10.4 The Four Purposes of Architecture 10.5 Applying the TOGAF Standard in the Digital Enterprise

11 Chapter 11: Architecture Governance

11.1 Architecture Governance: Concept & Benefits 11.2 The Architecture Board 11.3 Architecture Contracts 11.4 Architecture Compliance

12 Chapter 12: Architecture Content

12.1 Stakeholders, Concerns, Views & Viewpoints 12.2 Building Blocks: ABBs & SBBs 12.3 ADM Deliverables I: Preliminary Phase and Architecture Vision 12.4 ADM Deliverables II: From Architecture Definition to Change

3.2 Terms for Work Products, Models, Requirements & Change

Key Takeaways Explain This Topic AI

TOGAF defines a Requirement as a statement of need that is unambiguous, testable or measurable, and necessary for acceptability.

A Metamodel is a model that describes the entities used in building an Architecture Description, their characteristics, and the key relationships between them.

A Work Package is a set of actions to achieve one or more business objectives and can be part of a project, a complete project, or a program.

A Gap is a statement of difference between two states, used in gap analysis to identify the difference between the Baseline and Target Architectures.

TOGAF defines a Stakeholder as an individual, team, organization, or class thereof, having an interest in a system.

Last updated: September 2026

3.2 Terms for Work Products, Models, Requirements & Change

This section completes the Learning Unit 2 terminology. It covers the words TOGAF uses for what architects produce (artifacts, deliverables, models), how they describe things (metamodel, modeling, business model), who and what they deal with (stakeholder, role, requirement), and how change is packaged (gap, work package).

Work Products

Term TOGAF definition Plain-language meaning

Deliverable An architectural work product that is contractually specified and in turn formally reviewed, agreed, and signed off by the stakeholders A formal, signed-off output, such as a Statement of Architecture Work or Architecture Definition Document

Artifact An architectural work product that describes an aspect of the architecture A catalog, matrix, or diagram describing part of the architecture

The note on Deliverable adds that deliverables represent the output of projects; documentation deliverables are typically archived at project completion or transitioned into an Architecture Repository as a reference model, standard, or snapshot of the Architecture Landscape.

Key distinction: every deliverable is formally agreed and signed off; an artifact may or may not be a deliverable, depending on the contractual specification, and a deliverable usually contains several artifacts.

Models and Modeling

Term TOGAF definition Plain-language meaning

Architecture Model A representation of a subject of interest. An architecture model provides a smaller scale, simplified, and/or abstract representation of the subject matter A simplified picture or structure that stands in for the real thing

Metamodel A model that describes the entities used in building an Architecture Description, their characteristics, and the key relationships between those entities A "model of the model" — which entity types and relationships are allowed

Modeling A technique through construction of models which enables a subject to be represented in a form that enables reasoning, insight, and clarity concerning the essence of the subject matter The act of building models so people can reason about something

Business Model A model describing the rationale for how an enterprise creates, delivers, and captures value How the enterprise makes or delivers value, for example as described with a Business Model Canvas

How These Fit Together

The metamodel says a model may contain entity types such as Actor, Role, Process, and Application Component, and how they may relate.

Modeling is the technique of building architecture models that use those entity types.

A business model is one particular kind of model — about value creation, delivery, and capture — used mainly in Business Architecture.

Related glossary terms: an Architecture View is a representation of a system from the perspective of a related set of concerns, and a Model Kind is the conventions for a type of modeling; a viewpoint references model kinds and a view incorporates models.

Stakeholders, Roles, and Requirements

Term TOGAF definition Plain-language meaning

Stakeholder An individual, team, organization, or class thereof, having an interest in a system Anyone with an interest in the system or the architecture

Role (1) The usual or expected behavior of an actor, or the part somebody or something plays in a particular process or event; an actor may have a number of roles. (2) The part an individual plays in an organization and the contribution they make through the application of their skills, knowledge, experience, and abilities A part played by an actor, not the actor itself

Requirement A statement of need, which is unambiguous, testable or measurable, and necessary for acceptability A need precise enough to test and important enough that the result is unacceptable without it

Actor Versus Role

The glossary defines an Actor as "a person, organization, or system that has one or more roles that initiates or interacts with activities." One actor can hold several roles: a single employee (actor) might play the roles of claims approver and fraud reviewer.

What Makes a Good Requirement

A TOGAF requirement has three qualities built into the definition:

  • Unambiguous — only one reasonable interpretation
  • Testable or measurable — you can verify whether it is met
  • Necessary for acceptability — without it, the solution would not be acceptable

Compare: "the portal should be fast" fails the test; "the portal shall return account balances within two seconds for 95% of requests" passes it.

Gaps and Work Packages

Term TOGAF definition Plain-language meaning

Gap A statement of difference between two states. Used in the context of gap analysis, where the difference between the Baseline and Target Architecture is identified What must change to get from one state to another

Work Package A set of actions identified to achieve one or more objectives for the business. A work package can be a part of a project, a complete project, or a program A bundle of change activity that closes gaps

Gaps are identified in Phases B, C, and D, consolidated in Phase E, and addressed by work packages , which are sequenced on the Architecture Roadmap and scheduled in the Implementation and Migration Plan. Note the flexibility in the Work Package definition: it can be part of a project, a complete project, or a program .

Worked Example: An Insurance Claims Initiative

  • Term Example in the initiative
  • Stakeholder Head of Claims, Chief Risk Officer, claims handlers, regulators
  • Role Claims Approver; Fraud Reviewer (both played by senior handlers)
  • Requirement "Claims under USD 1,000 shall be settled within 24 hours for 90% of cases"
  • Architecture Model A process model of the target claims journey

Metamodel The enterprise's rule that a Process is performed by a Role and supported by an Application Component

  • Business Model How the insurer creates value through faster, lower-cost claims handling
  • Artifact Application/Organization matrix showing which teams use which claims systems
  • Deliverable The signed-off Architecture Definition Document for claims
  • Gap Baseline has no automated fraud scoring; target does
  • Work Package "Automated fraud scoring," delivered as one project within the claims program
  • Common Exam Pitfalls

Calling an artifact a deliverable. Only work products that are contractually specified and signed off are deliverables.

Confusing Metamodel with Architecture Model. A metamodel describes the entities and relationships used to build architecture descriptions; an architecture model represents a subject of interest.

Treating a Role as a person. A role is the part an actor plays; the actor is the person, organization, or system.

Forgetting the three qualities of a Requirement. Unambiguous, testable or measurable, and necessary for acceptability.

Assuming a Work Package is always a single project. It can be part of a project, a whole project, or a program.

Loading diagram... How Key Terms Connect: From Stakeholders to Work Packages