Zachman Framework

The Zachman Framework for Enterprise Architecture

1. Overview: The Zachman Framework, the progenitor of Enterprise Architecture (EA)

    flowchart LR
    A["Fragmented system design"] -- "Establishing an enterprise-wide classification scheme" --> B["Zachman Framework"]

Definition: A taxonomy in the form of a 6x6 matrix, composed of six perspectives (Rows) and six fundamental questions (Columns), for viewing and classifying an organization’s complex information infrastructure from multiple angles.

Characteristics: (Classification scheme) Not a methodology but a 6×6 classification schema that structures architecture deliverables exhaustively, without omission. (Cell uniqueness) Each cell has a unique, mutually exclusive set of properties, guaranteeing complete classification without overlap. (Multi-perspective representation) Cross-references six questions — What, How, Where, Who, When, Why — with six stakeholder perspectives to represent architecture three-dimensionally.

2. Structure and Matrix Composition of the Zachman Framework

A. The 6x6 Matrix Architecture Model

    flowchart TD
    subgraph Columns["6 Fundamental Questions (Columns)"]
        direction LR
        W1["What<br/>(Data)"]
        W2["How<br/>(Function)"]
        W3["Where<br/>(Network)"]
        W4["Who<br/>(People)"]
        W5["When<br/>(Time)"]
        W6["Why<br/>(Motivation)"]
    end
    
    subgraph Rows["6 Participant Perspectives (Rows)"]
        direction TB
        R1["Planner (Scope)"]
        R2["Owner (Business)"]
        R3["Designer (System)"]
        R4["Builder (Technology)"]
        R5["Sub-contractor (Specification)"]
        R6["User (Actual asset)"]
    end

    Columns <-->|"A classification scheme of 36 cells"| Rows

    style Columns fill:#f9f9f9,stroke:#333,stroke-dasharray: 5 5
    style Rows fill:#f9f9f9,stroke:#333,stroke-dasharray: 5 5

Category	Question (Columns)	Description
What	Data	The key entities and information used by the business (Entity)
How	Function	Business processes and service activities (Process)
Where	Network	The geographic locations and connectivity where business is conducted (Node)
Who	People	The business actors and organizational roles/responsibilities (Agent)
When	Time	The timing and sequence of business events (Time)
Why	Motivation	Business goals, strategy, and business rules (Rule)

B. Detailed Architecture Levels per Perspective (Rows)

    flowchart TD
  ROOT["Zachman Perspectives"]
  R1["Planner (Scope)"]
  R2["Owner (Business)"]
  R3["Designer (System)"]
  R4["Builder (Technology)"]
  R5["Sub-contractor (Detail)"]
  R6["User (Actual operation)"]

  ROOT --> R1
  ROOT --> R2
  ROOT --> R3
  ROOT --> R4
  ROOT --> R5
  ROOT --> R6

  R1 --> D1["Business background and strategic context"]
  R2 --> D2["Conceptual business entities and processes"]
  R3 --> D3["Logical system architecture and data design"]
  R4 --> D4["Physical technology specifications and implementation environment"]
  R5 --> D5["Detailed specifications of individual components and modules"]
  R6 --> D6["The final operating system and actual business environment"]

  style ROOT fill:#1E3A5F,color:#fff

3. Expected Benefits and Application of the Zachman Framework

Category	Key Expected Benefit	Application and Practical Use
Standardization	Systematic classification of enterprise assets	Used as an enterprise-wide communication standard to maintain EA information consistency
Completeness	Prevents architecture omissions	Use the 6x6 matrix to identify gaps when building EA
Flexibility	Technology-independent architecture	Separates business logic from implementation technology for flexible response to change

TOGAF