Ücretsiz Kullanmaya Başla

Architectural Artifacts by ADM Phase Knowledge-Based Study

TOGAF · Architecture Content · Foundation · Architectural Artifacts

Foundation topic explanations on Architectural Artifacts by ADM Phase.

Study notes

  1. Architecture Content and Artifact Categories

    In the TOGAF Standard, an artifact is an architectural work product that describes an aspect of the architecture. Artifacts are classified into three core types:

    • Catalogs: Lists of architectural building blocks, assets, or elements of a specific type (for example, lists of business goals, applications, or technology standards).
    • Matrices: Tabular grids showing relationships, mappings, or cross-dependencies between two or more elements (such as showing which business services access which data entities).
    • Diagrams: Graphical representations that depict the structure, connectivity, decomposition, or operational flow among architectural elements.

    Each phase of the Architecture Development Method (ADM) develops, consumes, or refines specific artifacts to provide structured, repeatable views tailored to stakeholder concerns.

    Scoping and Initiating Architectural Work

    During the early stages of the ADM, artifacts focus on foundational governance, stakeholder alignment, and establishing high-level intent.

    Preliminary Phase Artifacts

    The Preliminary Phase establishes the enterprise architecture capability and governance framework:

    • Principles Catalog: Captures enduring qualitative statements of intent that guide architecture development and decision-making across the enterprise.

    Phase A: Architecture Vision Artifacts

    Phase A defines the scope, baseline context, and strategic buy-in for the architecture cycle:

    • Stakeholder Map Matrix: Identifies stakeholders, their roles, communication needs, influence, and levels of engagement.
    • Value Stream/Capability Matrix: Aligns identified business capabilities against the stages of enterprise value streams.
    • Solution Concept Diagram: Provides a high-level representation of the intended solution, giving executive sponsors a clear visual summary of proposed transformation changes.

    Structuring Business Strategy, Operations, and Capabilities

    Phase B develops the Business Architecture to align business objectives with operating models, services, and organizational roles.

    Phase B Catalogs

    • Organization/Actor Catalog: Enumerates organizational units, departments, external parties, and roles.
    • Driver/Goal/Objective Catalog: Outlines strategic drivers, qualitative goals, and quantitative objectives that govern business direction.
    • Business Capability Catalog: Defines the complete inventory of abilities that the enterprise possesses or requires to execute its strategy.
    • Value Stream Catalog: Lists end-to-end value-creating flows across the organization.
    • Business Service/Function Catalog: Details the business functions and externally consumed services.

    Phase B Matrices and Diagrams

    • Business Interaction Matrix: Maps functional or organizational interactions, depicting dependencies between business units.
    • Actor/Role Matrix: Correlates human or system actors with the specific business roles they perform.
    • Business Capability Map: Visually decomposes capabilities into structured hierarchies.
    • Value Stream Map: Graphically represents stages of value delivery alongside stakeholders and enabling capabilities.
    • Organization Map: Displays organizational structures and reporting relationships.

    Modeling Data and Application Assets

    Phase C defines the Information Systems Architecture, separated into Data Architecture and Application Architecture.

    Phase C: Data Architecture Artifacts

    • Data Entity/Data Component Catalog: Lists all major logical data entities and physical data stores across the organization.
    • Data Entity/Business Function Matrix: Maps which business functions create, read, update, or delete (CRUD) specific data entities.
    • System/Data Matrix: Defines which software systems store, consume, or maintain given data entities.
    • Conceptual and Logical Data Diagrams: Visually describe data structures, semantic relationships, and entity constraints.
    • Data Dissemination Diagram: Depicts the flow and distribution of data between systems and across physical locations.

    Phase C: Application Architecture Artifacts

    • Application Portfolio Catalog: Catalogs all enterprise applications, including their lifecycle status, business criticality, and ownership.
    • Interface Catalog: Details system-to-system interfaces, payloads, and communication protocols.
    • Application/Function Matrix: Maps software applications directly to the business functions they automate or support.
    • Application Interaction Matrix: Documents explicit interface dependencies between pairs of applications.
    • Application Communication Diagram: Illustrates application components and the messaging or integration channels connecting them.

    Infrastructure, Transition, and Continuous Requirements

    The downstream ADM phases transition logical designs into technical platforms and sequenced roadmaps, supported by rigorous requirements tracking.

    Phase D: Technology Architecture Artifacts

    • Technology Standards Catalog: Lists approved infrastructure standards, platforms, middleware, and technology conventions.
    • Technology Portfolio Catalog: Inventories physical and virtual technology assets currently deployed or planned.
    • System/Technology Matrix: Maps applications and databases to the specific supporting infrastructure and platforms.
    • Environments and Locations Diagram: Illustrates deployment environments (such as development, staging, production) across geographical or cloud locations.
    • Networked Computing/Hardware Diagram: Visualizes physical network topology, server clusters, and hardware interconnectivity.

    Phase E: Opportunities and Solutions Artifacts

    • Project Context Diagram: Maps the scope, boundaries, and dependencies of proposed implementation projects.
    • Benefits Diagram: Illustrates the causal relationships between delivered architectural building blocks, intermediate outcomes, and final business benefits.

    Requirements Management Artifacts

    • Requirements Catalog: Centrally captures, tracks, and manages prioritized functional and non-functional architecture requirements throughout all ADM phases.

    Applying Artifact Knowledge

    Understanding which artifact belongs to each phase and distinguishing between catalogs, matrices, and diagrams is essential for effective TOGAF practice.

    Common Conceptual Distinctions to Remember:

    • Catalog vs. Matrix: An Application Portfolio Catalog merely lists applications and their attributes; an Application/Function Matrix demonstrates cross-domain relationships by mapping applications to business functions.
    • Phase B vs. Phase C: Business Capabilities and Value Streams belong strictly to Phase B (Business Architecture), whereas Application Portfolios and Data Entities belong to Phase C (Information Systems Architectures).
    • Requirements Tracking: The Requirements Catalog is not owned exclusively by an individual phase; rather, it is maintained and updated dynamically within the ongoing Requirements Management process.