TOGAF Enterprise Metamodel Attributes Knowledge-Based Study

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

Foundation topic explanations on TOGAF Enterprise Metamodel Attributes.

Study notes

  1. In the TOGAF Standard, 10th Edition, the Content Framework and Enterprise Metamodel define the structural components that make up an Enterprise Architecture. While metamodel entities (such as Business Services, Application Components, and Data Entities) define the foundational building blocks, metamodel attributes provide the granular metadata required to specify, quantify, evaluate, and manage those entities effectively.

    Purpose and Role of Metamodel Attributes

    Attributes serve several critical architectural functions within the Enterprise Metamodel:

    • Unambiguous Identification: Distinguishing each architectural artifact uniquely within the architecture repository.
    • Characterization: Describing the functional, technical, qualitative, and operational traits of an entity.
    • Governance and Lifecycle Tracking: Recording ownership, change history, readiness, and alignment with organizational standards.
    • Analysis and Trade-Off Evaluation: Providing measurable criteria (such as cost, service level, critical path, or security classification) to support architectural decision-making.

    The TOGAF metamodel designates a set of universal attributes shared across almost all architectural entities. These common attributes maintain consistency across business, data, application, and technology domains.

    Key Universal Attributes

    • ID (Unique Identifier): A globally unique token or code used to reference the entity unambiguously across repositories and viewpoints.
    • Name: A clear, concise, and business-meaningful title for the architectural element.
    • Description: A narrative statement detailing the scope, purpose, and role of the entity within the enterprise.
    • Category / Tag: A user-defined classification allowing grouping, filtering, and cross-domain portfolio reporting.
    • Source / Origin: Identifies the project, standard, stakeholder, or external authority that introduced or defined the entity.
    • Owner: The named stakeholder, organizational role, or governance body accountable for the entity's ongoing accuracy and lifecycle management.

    Beyond the universal attributes, each architectural domain defines specialized attributes tailored to specific modeling requirements and concerns.

    Core Domain Attribute Categories

    • Business Architecture Attributes: Applied to entities such as Business Services and Processes. Typical attributes include Service Quality, Criticality, Standard Duration, and Business Value.
    • Data Architecture Attributes: Characterize Data Entities and Logical Data Components. These include Confidentiality Level, Integrity Rating, Retention Period, and Volumetrics.
    • Application Architecture Attributes: Applied to Application Components and Interfaces. Key attributes include Lifecycle Status (e.g., Proposed, Active, Deprecated, Retired), Vendor, Version, and Hosting Model.
    • Technology Architecture Attributes: Describe Technology Services and Nodes. Examples include Standardization Status (e.g., Strategic, Contained, Prohibited), Deployment Platform, and Capacity Limits.
    • Motivation and Strategy Attributes: Used with Goals, Objectives, and Requirements. Attributes include Target Completion Date, Metric / KPI, Acceptance Criteria, and Priority.

    Enterprise architects frequently tailor the TOGAF Enterprise Metamodel by adding custom attributes to meet specific governance, regulatory, or tooling requirements. However, standard TOGAF attributes should remain the baseline to ensure cross-team semantic consistency and repository interoperability.

    Knowledge Check Question

    Question: Within the TOGAF Content Framework, which of the following represents a universal (standard) attribute common to almost all enterprise metamodel entities, rather than a domain-specific operational attribute?

    1. Option A: Standard Duration
    2. Option B: Retention Period
    3. Option C: Description
    4. Option D: Hosting Model

    Explanation of the Answer

    Correct Answer: Option C (Description)

    Explanation: In the TOGAF Content Framework and Enterprise Metamodel, Description (alongside ID, Name, Category, and Owner) is a universal attribute defined across all core metamodel entities regardless of domain. In contrast:

    • Option A (Standard Duration) is a domain-specific attribute typically associated with Process or Event entities in the Business Architecture domain.
    • Option B (Retention Period) is a specialized data management attribute associated with Data Entities.
    • Option D (Hosting Model) is an operational attribute specific to Application Components or Technology Nodes.