Ücretsiz Kullanmaya Başla

Overview Knowledge-Based Study

TOGAF · Architecture Content · Foundation · Building Blocks

Foundation topic explanations on Overview.

Study notes

  1. Overview of Building Blocks

    In the TOGAF Standard, 10th Edition, a building block is defined as a package of functionality defined to meet business needs across an organization. Building blocks represent reusable components of business, IT, or architectural capability that can be combined with other building blocks to deliver architectures and solutions.

    Key characteristics of building blocks include:

    • Reusability: Designed to be reused across different systems, business units, or architecture domains.
    • Interoperability: Capable of interoperation with other building blocks through well-defined interfaces and boundaries.
    • Separation of Specification from Implementation: Clear distinction between the requirements/functionality needed and the specific technology or product used to realize it.

    The Two Primary Types of Building Blocks

    The TOGAF Standard categorizes building blocks into two fundamental types based on their level of abstraction and lifecycle stage:

    1. Architecture Building Blocks (ABBs)

    Architecture Building Blocks (ABBs) capture architecture requirements and define the required functionality. They are typically technology-agnostic and conceptual.

    • Describe capability and functional requirements (e.g., "Customer Identity and Access Management Service").
    • Define the boundaries, interfaces, and interoperability criteria required by the business.
    • Guide the development and selection of Solution Building Blocks.

    2. Solution Building Blocks (SBBs)

    Solution Building Blocks (SBBs) represent concrete implementations and realizations of the functionality defined by ABBs.

    • Identify specific products, components, services, or software packages (e.g., "Okta Workforce Identity Cloud v2024").
    • Define physical interfaces, operational parameters, and deployment specifications.
    • Directly satisfy the functional and non-functional requirements specified in one or more ABBs.

    Lifecycle of Building Blocks across ADM Phases

    Building blocks evolve progressively as an enterprise architecture project advances through the Architecture Development Method (ADM) cycle:

    1. Early Phases (Phases A through D): The architecture team identifies business needs and defines conceptual and logical Architecture Building Blocks (ABBs) to address those needs across Business, Data, Application, and Technology domains.
    2. Opportunities and Solutions (Phase E): The focus shifts from requirements to implementation strategies. ABBs are mapped to candidate and existing Solution Building Blocks (SBBs), evaluating potential commercial off-the-shelf (COTS) software, shared services, and custom developments.
    3. Migration Planning and Governance (Phases F and G): Selected SBBs are procured, developed, configured, and deployed, ensuring continuous alignment with the defining ABBs.

    This progressive refinement ensures that architectural decisions remain anchored to business capabilities rather than prematurely dictated by vendor products.