Architecture Building Blocks (ABBs)

Architecture Building Blocks (ABBs) in TOGAF 10 Foundation - Complete Guide

Understanding Architecture Building Blocks (ABBs)

Architecture Building Blocks are fundamental components in the TOGAF framework that represent the key logical and physical components of an enterprise architecture. They serve as the foundation for designing, planning, and implementing enterprise solutions.

Why Architecture Building Blocks Are Important

ABBs are critical for several reasons:

• Standardization: They provide standardized components that ensure consistency across the enterprise architecture
• Reusability: ABBs can be reused across multiple projects and solutions, reducing development time and costs
• Modularity: They enable architects to break down complex systems into manageable, independent components
• Communication: ABBs provide a common language for stakeholders to understand architectural components
• Governance: They facilitate architecture governance by establishing approved building blocks
• Risk Reduction: Using proven building blocks reduces technical and implementation risks

What Are Architecture Building Blocks?

Definition: Architecture Building Blocks (ABBs) are the building blocks that represent fundamental units of the enterprise architecture. They encompass both logical and physical components required to deliver the enterprise solution.

Key Characteristics of ABBs:

• Logical Components: Represent business functions, processes, and services independent of implementation
• Physical Components: Represent actual technologies, systems, and infrastructure used to implement solutions
• Abstraction Level: Operate at a higher abstraction level than Solution Building Blocks (SBBs)
• Enterprise-Wide Scope: Designed to support multiple solutions and business capabilities
• Technology Neutral (for Logical ABBs): Logical ABBs describe what needs to be done without specifying how

How Architecture Building Blocks Work

Relationship Between ABBs and SBBs:

Architecture Building Blocks work in conjunction with Solution Building Blocks. ABBs define what logical and physical components should exist in the architecture, while SBBs represent the specific implementations and instantiations of those ABBs in particular solutions.

ABB Development Process:

1. Identification: Identify required building blocks based on business requirements and architecture principles
2. Specification: Define detailed specifications including interfaces, dependencies, and standards
3. Classification: Categorize building blocks by type (application, technology, infrastructure, etc.)
4. Documentation: Document each ABB with clear descriptions, characteristics, and usage guidelines
5. Approval: Obtain governance approval for use across the enterprise
6. Deployment: Make ABBs available in architecture repositories or catalogs
7. Governance: Monitor and manage the lifecycle of ABBs throughout the enterprise

ABB Types and Categories:

• Application Building Blocks: Business applications and services that support enterprise functions
• Technology Building Blocks: Technology components such as databases, middleware, and platforms
• Infrastructure Building Blocks: Physical infrastructure components like servers, networks, and storage
• Organization Building Blocks: Organizational units and roles responsible for managing components

ABBs in the Architecture Development Method (ADM)

Where ABBs Appear in ADM:

• Phase B (Business Architecture): Define business-oriented building blocks
• Phase C (Information Systems Architecture): Develop application and data building blocks
• Phase D (Technology Architecture): Define technology and infrastructure building blocks
• Phase E (Opportunities and Solutions): Combine ABBs to create solution architecture

Iterative Refinement: ABBs are continuously refined and updated as the architecture evolves through iterations of the ADM.

Key Concepts and Definitions

Architecture Repository: A central location where all approved ABBs are stored and managed for enterprise-wide access

Building Block Catalog: A structured list of available ABBs organized by category and type

Interfaces and Dependencies: ABBs define clear interfaces and document dependencies with other building blocks

Standards and Compliance: ABBs must comply with enterprise architecture standards and principles

Versioning: ABBs are versioned to track changes and maintain backward compatibility

Exam Tips: Answering Questions on Architecture Building Blocks (ABBs)

1. Understand the ABB vs. SBB Distinction

• Remember: ABBs are enterprise-level, reusable components; SBBs are specific implementations in particular solutions
• ABBs answer "what should exist," while SBBs answer "what specifically exists in this solution"
• Be ready to differentiate when exam questions present scenarios involving both types

2. Know the Four Categories

• Master the four main types: Application, Data, Technology, and Infrastructure building blocks
• Be able to classify examples correctly - this is a common exam question type
• Understand which ADM phase primarily deals with each type

3. Remember the ABB Lifecycle

• Be familiar with the complete lifecycle: Identification → Specification → Classification → Documentation → Approval → Deployment → Governance
• Questions may ask about best practices for managing ABBs throughout their lifecycle
• Understand governance and approval processes for new or modified ABBs

4. Key Relationships to Remember

• ABBs and Architecture Principles: ABBs must align with enterprise architecture principles
• ABBs and Architecture Repository: ABBs are stored, managed, and accessed through the architecture repository
• ABBs and ADM Phases: Know which phases primarily create and refine ABBs
• ABBs and Solutions: Solutions combine multiple ABBs to deliver business value

5. Common Exam Question Patterns

• Pattern 1: "Which of the following best represents an ABB?" - Look for enterprise-level, reusable components, not specific implementations
• Pattern 2: "What is the primary purpose of ABBs?" - Focus on reusability, standardization, and governance
• Pattern 3: "In which phase are Application Building Blocks primarily defined?" - Phase C (Information Systems Architecture)
• Pattern 4: "ABBs should be documented with..." - Include interfaces, dependencies, standards, and versioning information
• Pattern 5: "The relationship between an ABB and an SBB is..." - ABBs are architectural patterns; SBBs are concrete implementations of those patterns

6. What Examiners Are Testing

• Conceptual Understanding: Can you define and explain ABBs correctly?
• Practical Application: Can you identify and classify ABBs in architectural scenarios?
• Process Knowledge: Do you understand how ABBs are created, managed, and governed?
• Integration: Can you relate ABBs to other TOGAF concepts like the repository, ADM, and principles?

7. Answering Strategy for ABB Questions

• Step 1: Determine if the question is about ABB definition, types, lifecycle, or relationships
• Step 2: If it's a classification question, check if the item is enterprise-level (ABB) or solution-specific (SBB)
• Step 3: For scenario-based questions, map the building blocks to the appropriate ADM phase
• Step 4: Eliminate answers that confuse ABBs with solutions, components, or architecture principles
• Step 5: Choose answers that emphasize reusability, standardization, and enterprise-wide applicability

8. Red Herrings to Avoid

• Don't confuse ABBs with Solution Building Blocks - ABBs are abstract; SBBs are concrete
• Don't think ABBs are only about Technology - they encompass business, application, data, and infrastructure
• Don't believe ABBs are unique to each project - their power is in reusability across projects
• Don't assume ABBs are implemented directly - they must be adapted to create SBBs for specific solutions
• Don't overlook governance requirements - ABBs must be approved and managed through architecture governance

9. Key Phrases to Look For in Questions

• "Reusable across" - Indicator of ABB discussion
• "Enterprise standard" - ABBs establish enterprise standards
• "Specific implementation" - Indicator of SBB, not ABB
• "Architecture repository" - ABBs are managed and stored here
• "Multiple solutions" - ABBs serve multiple solutions; SBBs serve single solutions

10. Practice Question Examples

Example 1: "An organization needs to standardize its customer data management approach. Which building block type should be used?"
Answer: Data Building Block (a type of ABB) - This is enterprise-level and will be reused across solutions

Example 2: "What is the primary difference between an ABB and an SBB?"
Answer: ABBs are enterprise-level, reusable architectural components, while SBBs are specific implementations of ABBs in particular solutions

Example 3: "In which ADM phase are Technology Building Blocks primarily developed?"
Answer: Phase D (Technology Architecture)

Example 4: "ABBs must comply with which of the following?"
Answer: Enterprise architecture standards and principles (plus correct answer may include governance requirements)

Summary

Architecture Building Blocks are essential components of the TOGAF framework that enable organizations to standardize, reuse, and govern their architectural components. Understanding ABBs—their definition, types, lifecycle, and relationships—is critical for TOGAF Foundation exam success. Focus on the distinction between ABBs and SBBs, master the four categories, understand the ADM phases where each type is developed, and remember that ABBs emphasize reusability and enterprise-wide standardization. By recognizing common question patterns and avoiding red herrings, you'll be well-prepared to answer ABB-related questions confidently on your exam.