Zachman Framework

framework · governance and compliance · organizing-schema

Enterprise architecture taxonomy intersecting six perspectives with six abstractions (what, how, where, who, when, why).

John Zachman's framework, introduced in his 1987 IBM Systems Journal paper and progressively elaborated since, is a fundamental ontological taxonomy for enterprise architecture: a 6×6 matrix in which rows represent perspectives (Executive/Scope, Business Management, Architect, Engineer, Technician, and the operational Enterprise) and columns represent the basic interrogatives What (data), How (function), Where (network), Who (people), When (time), and Why (motivation). Each cell describes the artifacts a given perspective produces about a given aspect, treated as primitives that combine into composite views rather than as steps in a process. The framework is explicitly a taxonomy, not a methodology — it tells you how to classify architectural descriptions but not how to develop them, distinguishing it from process-oriented frameworks like TOGAF.

Originators

John A. Zachman high

Year / Decade

1987 (initial paper); subsequent elaboration into 6x6 matrix high

Primary sources

Zachman, J.A. (1987). 'A Framework for Information Systems Architecture', IBM Systems Journal, 26(3), Zachman International. The Zachman Framework for Enterprise Architecture (ongoing publications) high

Core components

Six perspectives (Executive Perspective/Scope
Business Management/Conceptual
Architect/Logical
Engineer/Physical
Technician/Out-of-Context
Enterprise/Operational)
Six interrogatives (What/data
How/function
Where/network
Who/people
When/time
Why/motivation)
Cell artifacts as primitives
Classification rather than methodology

Primary use case

Classifying and organizing enterprise architecture artifacts and descriptions; conceptual scaffolding for understanding what an EA practice should produce.

Common criticisms

Pure taxonomy with no how-to guidance limits operational utility
cell semantics ambiguous in practice
rarely fully populated in real engagements (most organizations use only a few cells)
abstraction makes adoption challenging
framework's prescriptive primitive/composite distinction sometimes ignored.

Lineage

Siblings: TOGAF