Ücretsiz Kullanmaya Başla

Conclusions Knowledge-Based Study

TOGAF · Architecture Content · Foundation · Architectural Artifacts

Foundation topic explanations on Conclusions.

Study notes

  1. Overview of Architectural Artifacts

    In the TOGAF Standard, 10th Edition, architecture content is organized to clearly differentiate between work products, artifacts, and building blocks. An artifact is an architectural work product that describes an aspect of the architecture. Artifacts are generally classified into three distinct categories:

    • Catalogs: Lists or tabular representations of core architectural elements without showing structural relationships (e.g., Application Portfolio Catalog, Principle Catalog).
    • Matrices: Two-dimensional grids showing relationships between distinct elements or across architectural domains (e.g., Business Interaction Matrix, Application to Technology Matrix).
    • Diagrams: Graphical representations that illustrate architectural components, topology, flows, or structural relationships to provide visual clarity for specific stakeholder viewpoints.

    Architectural artifacts are not standalone deliverables; instead, one or more artifacts are typically grouped together into formal deliverables, which are contractual, reviewable work products approved by stakeholders.

    Critical Conclusions Regarding Architectural Artifacts

    Understanding how artifacts function within the Architecture Development Method (ADM) requires several key conclusions regarding their lifecycle, purpose, and governance:

    • Fit-for-Purpose Generation: Artifacts should never be generated merely for compliance or completeness. Each artifact must address specific stakeholder concerns and support informed decision-making. If an artifact does not help evaluate trade-offs, clarify requirements, or validate implementation, it represents unnecessary overhead.
    • Separation of Content and Presentation: Artifacts are views of underlying architecture models. While the underlying repository maintains the single source of truth (the Architecture Landscape consisting of Building Blocks), catalogs, matrices, and diagrams present tailored viewpoints for specific target audiences.
    • Traceability Across Architecture Domains: Matrices play a pivotal role in maintaining end-to-end traceability from business drivers down to technology components. Catalogs ensure inventory completeness, while diagrams facilitate cross-domain communication.
    • Evolution and Change Control: Artifacts undergo state transitions throughout the ADM phases—moving from initial draft states during Architecture Vision and domain architecture development to baselined and governing assets in Phase G (Implementation Governance).

    Knowledge Check: Architectural Artifacts & Conclusions

    Test your understanding of the conclusions and principles governing TOGAF artifacts with the following practice questions.

    Question 1

    Which statement best represents a fundamental conclusion regarding the development and usage of architectural artifacts in the TOGAF Standard?

    • A. Every catalog, matrix, and diagram specified in the ADM must be produced in every cycle to guarantee conformance.
    • B. Artifacts must be selected and tailored to address specific stakeholder concerns and support decision-making, rather than produced unconditionally.
    • C. Artifacts represent final signed-off contractual outputs, whereas deliverables represent internal architecture working drafts.
    • D. Catalogs illustrate complex inter-domain behavioral flows, whereas diagrams list individual architectural building blocks.

    Correct Answer: B

    Explanation: The TOGAF Standard explicitly emphasizes that the ADM is iterative and adaptable. Artifacts are selected based on business context and stakeholder concerns. Producing all artifacts unconditionally leads to unnecessary overhead. Furthermore, deliverables are the formal, contractual work products, whereas artifacts are the constituent elements (catalogs, matrices, diagrams) that form them.


    Question 2

    How does the TOGAF Standard distinguish a matrix from a catalog?

    • A. A catalog is a graphical depiction of system topology, while a matrix is a raw textual narrative.
    • B. A catalog manages procurement agreements, while a matrix governs physical infrastructure inventory.
    • C. A catalog is an itemized list of architectural elements, while a matrix depicts relationships between two or more elements.
    • D. A catalog is created exclusively in Phase A, while a matrix is created exclusively in Phase E.

    Correct Answer: C

    Explanation: In the TOGAF Architecture Content Framework, catalogs provide ordered lists or inventories of architectural entities (such as actors, business services, or applications), while matrices are grids that capture and assess the relationships between entities across or within domains.