Ücretsiz Kullanmaya Başla

Overview Knowledge-Based Study

TOGAF · Architecture Content · Foundation · TOGAF Content Framework and Enterprise Metamodel

Foundation topic explanations on Overview.

Study notes

  1. Purpose and Context

    The TOGAF Standard separates the process of developing an enterprise architecture from the work products produced during that process. While the Architecture Development Method (ADM) defines what to do, the TOGAF Content Framework provides a structured model defining what is produced.

    Key benefits of utilizing a structured Content Framework include:

    • Consistency and Rigor: Establishes a standardized vocabulary and taxonomy across different architecture projects.
    • Traceability: Allows architectural elements to be linked across business, data, application, and technology layers.
    • Tool Interoperability: Facilitates exchanging and managing architecture models across specialized Enterprise Architecture (EA) tools and repositories.
    • Completeness: Ensures that all necessary concerns and stakeholder perspectives are addressed without leaving critical architectural gaps.

    Classification of Architectural Work Products

    The Content Framework organizes the structural outputs of the architecture process into three major categories:

    • Deliverables: A work product that is formally specified, reviewed, agreed upon, and signed off by stakeholders. Deliverables typically represent the output of an ADM phase or project milestone (such as an Architecture Definition Document or Architecture Vision).
    • Artifacts: Architectural work products describing an architecture from a specific viewpoint. Artifacts are sub-components of deliverables and are categorized into three distinct varieties:
      • Catalogs: Lists or tables of architecture elements (e.g., Application Portfolio Catalog, Principle Catalog).
      • Matrices: Grids showing relationships between two or more elements (e.g., Business Interaction Matrix, Application to Data Matrix).
      • Diagrams: Graphical depictions of architectural concepts and relationships (e.g., Application Communication Diagram).
    • Building Blocks: Reusable components of business, IT, or architectural capability. These are divided into Architecture Building Blocks (ABBs), which define required functionality, and Solution Building Blocks (SBBs), which define concrete implementations.

    Process Meets Content

    The relationship between the ADM and the Content Framework is complementary:

    • ADM as the Engine: Drives the iterative lifecycle, governance, and stakeholder alignment.
    • Content Framework as the Blueprint: Dictates the structural composition and metamodel entities populated during each ADM phase.

    Throughout the phases of the ADM, architects capture requirements and model architectures by instantiating artifacts and building blocks. These outputs are subsequently packaged into formal deliverables governed under contractual agreements.

    Understanding the Enterprise Metamodel

    At the foundation of the Content Framework lies the Enterprise Metamodel. A metamodel is a "model of models" that defines:

    • Core Entities: Formal concepts representing architectural constructs, such as Actor, Business Capability, Application Component, and Technology Service.
    • Attributes: Specific characteristics and metadata associated with each entity (e.g., lifecycle status, criticality, ownership).
    • Relationships: Explicit associations connecting entities across domains (e.g., an Application Component realizes a Business Service; a Data Entity resides in a Logical Technology Component).

    By enforcing a coherent metamodel, organizations ensure that architecture repositories can execute rigorous impact analyses, dependency mapping, and gap analyses.