Ücretsiz Kullanmaya Başla

Content Framework and the TOGAF ADM Knowledge-Based Study

TOGAF · Architecture Content · Foundation · Introduction

Foundation topic explanations on Content Framework and the TOGAF ADM.

Study notes

  1. Process Meets Content

    The TOGAF Standard separates the process of developing an enterprise architecture from the products generated during that development.

    • The Architecture Development Method (ADM): Acts as the process engine. It defines a dynamic, iterative sequence of phases (from Phase A through Phase H) outlining how to execute an architecture project, engage stakeholders, and manage transitions.
    • The Architecture Content Framework: Defines the structural model for outputs. It specifies what architectural work products should be created, collected, and managed throughout the ADM lifecycle.

    Without a structured content model, architecture teams risk producing inconsistent documentation that cannot be easily integrated, queried, or reused across subsequent ADM cycles.

    Deliverables, Artifacts, and Building Blocks

    The Content Framework categorizes the outputs produced by the ADM into three distinct structural concepts:

    • Deliverables: Formally reviewed, agreed, and signed off work products. Deliverables represent contractual outputs of an ADM phase and typically combine multiple artifacts into a consolidated document or presentation package (e.g., an Architecture Definition Document).
    • Artifacts: More granular architectural work products that describe an aspect of the architecture. Artifacts are classified into three types:
      • Catalogs: Lists of architectural elements (e.g., Application Portfolio Catalog, Principle Catalog).
      • Matrices: Tables showing relationships between two or more elements (e.g., Business Interaction Matrix, Application/Organization Matrix).
      • Diagrams: Graphical representations depicting architectural relationships and topologies.
    • Building Blocks: Reusable operational and functional components. The ADM refines requirements into Architecture Building Blocks (ABBs) representing architecture capability, which are later realized as Solution Building Blocks (SBBs) representing candidate solutions and components.

    Structuring Architecture Consistency

    At the core of the Architecture Content Framework is the Content Metamodel, which defines the formal ontology of concepts (such as Actor, Business Service, Logical Application Component, and Physical Technology Component) and their allowable relationships.

    The interaction between the Content Framework and the ADM ensures three core capabilities:

    1. Traceability: Architecture entities defined in early phases (such as Goals and Requirements in the Preliminary Phase and Phase A) remain directly linked to implementations defined in Phase D and Phase E.
    2. Consistency Across Domains: Business, Data, Application, and Technology architectures use a common semantic taxonomy, eliminating ambiguity across stakeholder viewpoints.
    3. Separation of Concerns: The content model enables architects to isolate detailed technical specifications from high-level contractual deliverables, ensuring appropriate detail reaches the intended audience.