Zachman Framework interactive infographic study manual β 6 rows, 6 columns, 36 cells, rules, and flash cards
ποΈ
Zachman Framework β Infographic Study Manual
An ontology for enterprise architecture Β· John A. Zachman, 1987 Β· The 6 Γ 6 matrix of interrogatives and perspectives Β· Not a methodology β a classification schema
The Zachman Framework is an ontology for enterprise architecture β not a methodology, not a process, not a set of tools. It is a two-dimensional classification schema that organises ALL the descriptive representations of an enterprise. Created by John A. Zachman in 1987, updated in 2011 (v3.0).
1987
Year created by John A. Zachman at IBM
36
Cells β intersections of 6 rows Γ 6 columns
v3.0
Current version β published 2011
β WHAT ZACHMAN IS
βA complete classification schema for all enterprise descriptive artefacts
βAn ontology β a taxonomy of what exists and how it relates
βA framework for organising architecture documentation
βA communication tool across all stakeholder perspectives
βTechnology-, industry-, and methodology-neutral
β WHAT ZACHMAN IS NOT
βNOT a methodology β it does not tell you HOW to do architecture
βNOT a process β there is no prescribed sequence of steps
βNOT a set of tools or templates
βNOT prescriptive about what to build first
βNOT an implementation framework
THE BUILDING ANALOGY β Zachman's own explanation
ποΈ
Owner's Perspective
"I need 3 bedrooms, open kitchen, garage"
π
Designer's Perspective
Architect's floor plans, elevations, sections
π§
Builder's Perspective
Contractor's working drawings and specs
Just as a building has multiple sets of drawings β floor plans, electrical diagrams, structural plans, plumbing β an enterprise has multiple perspectives and dimensions that must all be described. Zachman provides the framework to ensure every cell is addressed and every perspective is consistent.
EVOLUTION OF THE ZACHMAN FRAMEWORK
1987 β Original
John Zachman publishes "A Framework for Information Systems Architecture" in IBM Systems Journal. 3 rows, 3 columns initially β later expanded.
1992 β Expanded
Zachman and Sowa publish "Extending and Formalizing the Framework for Information Systems Architecture" β 6Γ6 matrix formalised with Who, When, Why columns added.
2011 β v3.0
Zachman International releases version 3.0 β renamed rows to reflect stakeholder perspectives rather than phases. Emphasis on ontology, not methodology. Current version.
The Zachman Framework is a 6Γ6 matrix β 6 stakeholder perspectives (rows) Γ 6 interrogatives (columns) = 36 cells, each representing a unique primitive model. Click any cell to explore what it contains. Each cell must be internally consistent and consistent with all cells in the same row and column.
ποΈ
Select a cell
PRIMITIVE MODEL
β
CONCRETE EXAMPLE
β
STAKEHOLDER QUESTION
β
Perspective
π¦ WHAT Data / Inventory
βοΈ HOW Function / Process
πΊοΈ WHERE Network / Location
π₯ WHO People / Responsibility
β±οΈ WHEN Time / Event
π― WHY Motivation / Strategy
Row 1 β Contextual (Executive)
Row 2 β Conceptual (Business)
Row 3 β Logical (Architect)
Row 4 β Physical (Engineer)
Row 5 β Detailed (Technician)
Row 6 β Functioning Enterprise
The 6 rows represent different stakeholder perspectives β each asking the same 6 questions from a different level of abstraction. Row 1 is the most abstract (contextual); Row 6 is the most concrete (the actual functioning enterprise). Click any row to see its full detail.
The 6 columns represent the 6 fundamental interrogatives β the questions every stakeholder asks about the enterprise from their perspective. Every cell in the matrix is the answer to one interrogative from one perspective. Together, the 6 columns give a complete description of any complex object.
All 6 begin with W (in English) β "What How Where Who When Why". These are the same questions a journalist asks about any event. Applied to the enterprise, they yield a complete description.
Zachman defined explicit rules for the framework β these rules distinguish it from a simple classification table and make it a true ontology. Understanding the rules is essential for correct application and for exam questions.
Zachman and TOGAF are complementary, not competing. Zachman provides the classification schema (what to describe); TOGAF provides the method (how to develop the architecture). Many organisations use both together.
Dimension
Zachman Framework
TOGAF (any version)
Type
Ontology / classification schema
Methodology / process framework
Purpose
Organises and classifies ALL architecture descriptions
Guides HOW to develop and govern enterprise architecture
Primary output
A complete set of 36 primitive models describing the enterprise
Technology-neutral in principles; technology-aware in practice
Used together?
Yes β TOGAF ADM produces artefacts that are classified using Zachman cells. Many EA teams map TOGAF deliverables to Zachman cells.
HOW THEY WORK TOGETHER β TOGAF + ZACHMAN
TOGAF ADM Phase B β Zachman Row 2
The Business Architecture produced in TOGAF Phase B maps to Row 2 (Business / Conceptual perspective) across all 6 Zachman columns β Business Entity Model (What), Business Process Model (How), Business Logistics Model (Where), Work Model (Who), Master Schedule (When), Business Plan (Why).
TOGAF Phase D β Zachman Row 4
The Technology Architecture produced in TOGAF Phase D maps to Row 4 (Physical / Engineer perspective) β Physical Data Model (What), Physical Process Design (How), Physical Network Architecture (Where), Physical Organisation Design (Who), Physical Event Schedule (When), Physical Rules (Why).
30 flash cards covering all key Zachman Framework concepts β rows, columns, rules, cell content, and comparison with TOGAF. Filter by category to focus on specific areas.
Card 1 of 30
QUESTION
Loading...
Tap to reveal the answer
ANSWER
Essential Zachman Framework definitions β understand these precisely for any architecture exam, interview, or professional application.