8.4 Architecture Catalogs, Matrices & Diagrams (Visual Representation)

Architecture Catalogs, Matrices & Diagrams (Visual Representation)

Architectural artifacts are the primary visual and structured outputs produced during the execution of the TOGAF ADM. Under the TOGAF Architecture Content Framework, every artifact produced to describe an architectural view falls into one of three structural representation types: Catalogs, Matrices, or Diagrams.

Each artifact representation type serves a distinct purpose in capturing, analyzing, and communicating architectural information to stakeholders. Understanding when to use a Catalog, Matrix, or Diagram ensures that enterprise architects select the most effective format for stakeholder communication, gap analysis, and governance.

---

1. Catalogs: Tabular Inventories & Registries

A Catalog is a plain list, inventory, or registry of building blocks of a specific entity type, structured in tabular format. Catalogs form the foundational raw data of the Architecture Repository. Before architects can construct complex relationship matrices or draw architectural diagrams, they must first build accurate catalogs to audit baseline assets.

Key Characteristics of Catalogs:

• Domain-Specific Inventories: Capture all instances of a single metamodel entity type across the enterprise.
• Tabular Structure: Organized with columns representing entity attributes (e.g., ID, Name, Description, Owner, Lifecycle State).
• Baseline & Target Scope: Provide authoritative registries for both current-state (baseline) and future-state (target) assets.

Standard TOGAF Catalogs by Domain:

• Business Architecture Catalogs:
  • Organization/Actor Catalog: Complete listing of all business units, internal departments, external partners, and individual actors.
  • Role Catalog: Registry of defined business roles and permissions.
  • Business Service / Function Catalog: Inventory of business capabilities, functions, and services offered.
  • Value Stream Catalog: Registry of primary enterprise value streams.
• Data Architecture Catalogs:
  • Data Entity / Data Component Catalog: Comprehensive listing of logical data entities, data classifications, and physical data stores.
• Application Architecture Catalogs:
  • Application Portfolio Catalog: Master list of all software applications, microservices, COTS products, and legacy systems.
  • Interface Catalog: Detailed registry of application-to-application integration endpoints, APIs, and data contracts.
• Technology Architecture Catalogs:
  • Technology Standards Catalog: Approved technology standards, frameworks, and programming language versions.
  • Technology Portfolio Catalog: Inventory of physical hardware servers, operating systems, cloud services, and network appliances.

---

2. Matrices: Relationship & Dependency Grids

A Matrix is a two-dimensional grid that maps the relationship between two different metamodel entity types (or between entities of the same type). Matrices are the primary tool used by enterprise architects to perform gap analysis, trace cross-domain alignment, discover missing capabilities, and identify legacy redundancies.

Key Characteristics of Matrices:

• Cross-Domain Mapping: Placed with Entity Type A on the vertical axis and Entity Type B on the horizontal axis.
• Relationship Cells: Intersection cells show relationship status (e.g., CRUD operations, direct dependencies, read/write permissions, or structural alignment).
• Gap & Overlap Analysis: Highlights missing interfaces (gaps) or instances where multiple applications serve the exact same business unit (redundancies).

Standard TOGAF Matrices by Domain:

• Business Function / Data Entity Matrix (CRUD Matrix): Maps business functions against data entities to show which functions Create, Read, Update, or Delete specific data.
• Application / Organization Matrix: Maps application software against organization units to identify which departments use which applications and highlight application sprawl.
• Application / Function Matrix: Maps applications against business functions to verify that every business function has application support.
• Application / Data Matrix: Maps applications against logical data entities to show data ownership and data flow boundaries.
• System / Technology Matrix: Maps physical applications against physical technology components to evaluate platform hosting dependencies.

---

3. Diagrams: Visual Graphical Views

A Diagram is a visual, graphical representation of an architectural view. Diagrams depict topology, interaction flows, structural relationships, physical deployments, and conceptual models. They are the most effective artifact type for communicating complex architectural concepts to non-technical stakeholders and executive sponsors.

Key Characteristics of Diagrams:

• Visual Syntax: Use standardized shapes, colors, connectors, and boundaries (often using ArchiMate or UML notation).
• Stakeholder Viewpoint-Driven: Tailored to answer specific stakeholder concerns (e.g., security topology for CISOs, deployment flows for DevOps engineers).
• Abstraction Levels: Range from high-level contextual views (Business Footprint) to low-level engineering specs.

Standard TOGAF Diagrams by Domain:

• Business Architecture Diagrams:
  • Business Footprint Diagram: Illustrates business goals, organization units, business functions, and supporting technical infrastructure on a single executive map.
  • Value Stream Map: Visualizes end-to-end customer value creation streams.
  • Business Process Diagram: High-level activity flow modeling business operations.
• Data Architecture Diagrams:
  • Data Dissemination Diagram: Depicts how data entities move between applications, databases, and external partners.
  • Data Security Diagram: Highlights data encryption boundaries, access zones, and compliance privacy limits.
• Application Architecture Diagrams:
  • Application Communication Diagram: Shows inter-application message flows, API calls, and protocol bindings.
  • Application Migration Diagram: Visualizes phased transition states during application modernization.
• Technology Architecture Diagrams:
  • Technology Infrastructure Diagram: Shows hardware servers, cloud virtual networks, load balancers, and physical site locations.
  • Processing Diagram: Depicts how data processing workloads are distributed across cluster nodes.

---

Selecting the Right Artifact Representation

+-----------------------+-------------------------------------------------------------+
| Artifact Type        | Primary Use Case & Selection Rationale                      |
+-----------------------+-------------------------------------------------------------+
| Catalog (List)        | 'I need an audited inventory of what assets exist.'          |
| Matrix (Grid)         | 'I need to analyze dependencies, gaps, or redundancies.'   |
| Diagram (Visual)      | 'I need to communicate topology or flow to stakeholders.'   |
+-----------------------+-------------------------------------------------------------+

By systematically building Catalogs first, constructing Matrices to evaluate relationships, and drawing Diagrams to communicate solutions, architects ensure complete coverage across all ADM phases.