Study guide

8.2 Architecture Building Blocks (ABBs) vs Solution Building Blocks (SBBs)

TOGAF Enterprise Architecture Study Guide Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Introduction to TOGAF & Enterprise Architecture Concepts

1.1 Overview of TOGAF Standard 10th Edition & Enterprise Architecture Concepts 1.2 The Structure of the TOGAF Standard (Easily Navigated Body of Knowledge) 1.3 Core Concepts: Enterprise, Architecture, Deliverables, Artifacts, and Building Blocks 1.4 TOGAF Certification Paths & the OGEA-101 Exam Plan

2 Chapter 2: ADM Foundation & Preliminary Phase

2.1 The Architecture Development Method (ADM) Cycle & Requirements Management 2.2 Preliminary Phase: Scope, Principles, and Architecture Capability Setup 2.3 Tailoring the ADM & Applying Iteration / Architecture Levels 2.4 Applying the ADM: The TOGAF Library, Purpose-Based Architecture Projects & the Digital Enterprise

3 Chapter 3: ADM Architecture Vision & Business Architecture

3.1 Phase A: Architecture Vision, Stakeholder Management & Value Proposition 3.2 Business Architecture Scope, Strategy & Capability Mapping 3.3 Phase B: Business Architecture Inputs, Steps, Outputs & Artifacts 3.4 Business Scenarios & Value Stream Modeling

4 Chapter 4: ADM Information Systems Architectures (Phase C)

4.1 Information Systems Architectures Overview & Phase C Strategy 4.2 Phase C Data Architecture: Principles, Data Models & Governance 4.3 Phase C Application Architecture: Logical Components, Services & Interfaces 4.4 Data and Application Integration, Migration & Interoperability

5 Chapter 5: ADM Technology Architecture & Solution Realization (Phases D, E, F)

5.1 Phase D: Technology Architecture, Platform Services & Infrastructure 5.2 Phase E: Opportunities and Solutions & Initial Implementation Strategy 5.3 Phase F: Migration Planning, Roadmap Development & Portfolio Prioritization 5.4 Transition Architectures & Implementation Dependencies

6 Chapter 6: ADM Governance, Change & Requirements Management (Phases G, H)

6.1 Phase G: Implementation Governance & Architecture Compliance 6.2 Phase H: Architecture Change Management & Driver Monitoring 6.3 Requirements Management: Central Flow, Impact Analysis & Traceability 6.4 Architecture Contracts, Dispensations & Compliance Reviews

7 Chapter 7: BDAT Architecture Domains Deep-Dive

7.1 Business Architecture Domain: Functions, Processes & Value Streams 7.2 Data Architecture Domain: Data Entities, Storage & Data Management 7.3 Application Architecture Domain: Application Services, Systems & Integration Patterns 7.4 Technology Architecture Domain: Hardware, Software, Cloud & Network Platforms

8 Chapter 8: Architecture Content — Content Framework, Enterprise Metamodel & Artifacts

8.1 Architecture Content Framework Overview & Deliverables vs Artifacts vs Building Blocks 8.2 Architecture Building Blocks (ABBs) vs Solution Building Blocks (SBBs) 8.3 The Enterprise Metamodel: Core Concepts, Entities & Attributes 8.4 Architecture Catalogs, Matrices & Diagrams (Visual Representation) 8.5 Stakeholders, Concerns, Architecture Views & Viewpoints

9 Chapter 9: Architecture Governance, Capability & Maturity

9.1 Architecture Governance Framework & The Role of the Architecture Board 9.2 Establishing an Architecture Capability & Organizational Structure 9.3 Architecture Skills Framework, Roles & Competency Levels 9.4 Architecture Maturity Models & Capability Assessments

10 Chapter 10: Enterprise Continuum, Reference Models & Key Techniques

10.1 Enterprise Continuum, Architecture Repository & Landscape Partitioning 10.2 Technical Reference Model (TRM) & Integrated Information Infrastructure Reference Model (III-RM) 10.3 Core EA Techniques: Gap Analysis, Interoperability, Risk, Capability-Based Planning & Architecture Patterns

8.2 Architecture Building Blocks (ABBs) vs Solution Building Blocks (SBBs)

Key Takeaways Explain This Topic AI

Architecture Building Blocks (ABBs) capture architecture requirements, business goals, and capability specifications in a vendor-agnostic format during ADM Phases A through D.

Solution Building Blocks (SBBs) represent the physical realization and candidate products, technologies, or custom developments selected in ADM Phase E to satisfy ABBs.

The relationship between ABBs and SBBs can be one-to-one, one-to-many, or many-to-one depending on component granularity and solution design.

Building blocks undergo a continuous lifecycle, progressing from initial specification in the Architecture Repository to candidate solution selection and eventual operational deployment.

Maintaining vendor independence in ABBs preserves architectural flexibility and prevents early vendor lock-in prior to formal solution procurement.

Last updated: November 2026

Architecture Building Blocks (ABBs) vs Solution Building Blocks (SBBs)

A core strength of TOGAF is its modular, component-based approach to enterprise architecture. Central to this approach is the concept of Building Blocks . A building block is a package of functionality defined to meet business needs across an enterprise. TOGAF makes a fundamental distinction between two types of building blocks throughout the Architecture Development Method (ADM) lifecycle: Architecture Building Blocks (ABBs) and Solution Building Blocks (SBBs) .

Understanding the distinction between specification (ABBs) and realization (SBBs) prevents organizations from locking into specific vendor products prematurely, ensuring that business requirements drive technical solutions rather than technology constraints dictating business capability.

Architecture Building Blocks (ABBs): Specification of Requirement

Architecture Building Blocks (ABBs) represent the abstract specification of architecture requirements, business capabilities, application services, and technology boundaries. ABBs define what functionality is needed without specifying how that functionality will be physically implemented or which vendor product will be purchased.

Key Characteristics of ABBs:

Vendor-Agnostic : Free from proprietary vendor dependencies, specific software brands, or hardware models.

Requirement-Driven : Capture business requirements, directional strategy, interoperability rules, and functional interfaces.

Logical Granularity : Define logical entities such as "Customer Relationship Management System", "Enterprise Service Bus", or "Relational Database Management System".

Phase Origin : ABBs are identified, defined, and refined during the early architectural definition phases of the ADM:

Phase A (Architecture Vision) : Initial high-level candidate ABBs.

Phase B (Business Architecture) : Business function, service, and capability ABBs.

Phase C (Information Systems Architectures) : Data entity, logical application component, and application service ABBs.

Phase D (Technology Architecture) : Logical technology components and infrastructure service ABBs.

What an ABB Specification Includes:

An ABB specification typically documents functional capability requirements, required interfaces, security parameters, performance metrics, data schema requirements, and interoperability standards.

Solution Building Blocks (SBBs): Realization of Solution

Solution Building Blocks (SBBs) represent the physical realization of ABBs. They are the concrete components, commercial off-the-shelf (COTS) software packages, custom-developed software modules, cloud infrastructure services, or hardware assets selected to satisfy the requirements defined by one or more ABBs.

Key Characteristics of SBBs:

Vendor and Product-Specific : Tied to specific commercial products, open-source projects, or custom software releases (e.g., Salesforce Enterprise Edition , Apache Kafka 3.4 , AWS Aurora PostgreSQL ).

Implementation-Focused : Define physical deployment configurations, operational boundaries, licensing constraints, and technical build specifications.

Concrete Assets : Represent real software binaries, hardware units, microservices, or platform services that can be procured, installed, or deployed.

Phase Origin : SBBs are evaluated, candidate-selected, and finalized primarily in Phase E (Opportunities & Solutions) , where candidate solutions are matched against baseline and target ABBs, and subsequently implemented in Phase F and Phase G.

What an SBB Specification Includes:

An SBB specification documents product vendor details, exact software build versions, licensing models, physical deployment architecture, operational SLA capabilities, hardware hosting specifications, and implementation cost metrics.

Mappings & Relationships Between ABBs and SBBs

The mapping between abstract specifications (ABBs) and physical realizations (SBBs) is flexible and depends on system architecture granularity: 1-to-1 Mapping: [ ABB: Relational Database ] ----> [ SBB: PostgreSQL 15 ]

  • 1-to-Many Mapping: [ ABB: Identity & Access ] ----> +-- [ SBB: Okta (SSO) ]
  • +-- [ SBB: CyberArk (PAM) ]
  • +-- [ SBB: PingFederate ]
  • Many-to-One Mapping: +-- [ ABB: API Gateway ] ----+
  • +-- [ ABB: Rate Limiter ] ---+---> [ SBB: Kong Enterprise ]
  • +-- [ ABB: Auth Proxy ] -----+

One-to-One (1:1) : A single logical ABB maps directly to a single physical SBB.

Example : An Enterprise RDBMS ABB is satisfied directly by a PostgreSQL 15 instance.

One-to-Many (1:N) : A single logical ABB requires multiple specialized SBBs working in tandem to fulfill all specification requirements.

Example : An Identity and Access Management ABB requires Okta (for Single Sign-On), CyberArk (for Privileged Access Management), and PingFederate (for external federation).

Many-to-One (N:1) : A single consolidated commercial software product or platform SBB satisfies multiple discrete ABBs simultaneously.

Example : An enterprise installs Kong Enterprise , a single product SBB that simultaneously fulfills three separate ABBs: API Gateway ABB , Rate Limiter ABB , and OAuth Token Validation ABB .

Life Cycle of Building Blocks in the Architecture Repository

Building blocks are not static; they evolve through an ongoing lifecycle across ADM iterations and are stored in the enterprise Architecture Repository :

Identification : Business requirements drive the identification of candidate ABBs during ADM Phases A–D.

Specification : Candidate ABBs are formalized with interfaces and standards in the Architecture Definition Document.

Evaluation : In Phase E, architecture teams conduct market analysis and Request for Proposal (RFP) evaluations to identify candidate SBBs that satisfy target ABBs.

Selection & Procurement : Candidate SBBs are chosen, procured, and pilot-tested.

Deployment : Selected SBBs are implemented (Phase G) and become part of the enterprise's operational baseline architecture.

Re-use & Governance : Deployed SBBs are recorded in the Architecture Repository's Solutions Landscape , reusable ABBs and patterns go to the Reference Library , and building blocks the enterprise mandates are listed in the Standards Library , so future ADM initiatives can reuse them.

Comparison Summary: ABBs vs SBBs

  • Attribute Architecture Building Block (ABB) Solution Building Block (SBB)
  • Primary Concept Specification of requirement ( What ) Realization of solution ( How )
  • Vendor Stance Vendor-agnostic, open specification Vendor-specific, product implementation
  • Primary ADM Phases Phases A, B, C, D (Architecture Definition) Phase E (Opportunities & Solutions), F, G
  • Focus Business capabilities, logical boundaries Commercial software, hardware, cloud services
  • Granularity Logical application components, service specs Executable packages, server instances, microservices
  • Examples Customer Master ABB, Message Broker ABB Salesforce CRM, RabbitMQ v3.11, AWS S3

By maintaining a clear division between ABBs and SBBs, enterprise architects ensure that architectural design remains resilient to vendor changes, flexible across cloud environments, and strictly aligned with business goals.