Zachman Framework Primer & Classification Guide — Enterprise Architecture with Linked.Archi¶
This guide introduces the Zachman Framework as formalised in Linked.Archi, explains how its concepts map to semantic assets, and demonstrates practical classification through worked examples.
Disclaimer: This is a community semantic representation of the Zachman Framework for interoperability purposes. It is not produced by, endorsed by, or affiliated with Zachman International, Inc. "Zachman Framework" is a registered trademark of Zachman International, Inc.
Phase 1 — Understanding the Zachman Framework¶
What is the Zachman Framework?¶
The Zachman Framework for Enterprise Architecture, created by John Zachman in 1987, is a two-dimensional classification schema for organizing the descriptive representations of an enterprise. It is formed by the intersection of six primitive communication interrogatives and six reification transformations, producing a bounded 6×6 matrix of 36 cells.
The Zachman Framework is not a methodology — it does not prescribe a process for creating architecture, does not define a modeling notation, and does not tell you which artifacts to produce. It classifies the complete logical space of what could be described about an enterprise.
"The Zachman Framework is a schema — the intersection of two historical classifications that have been in use for literally thousands of years. The first is the fundamentals of communication found in the primitive interrogatives: What, How, When, Who, Where, and Why. The second is derived from reification, the transformation of an abstract idea into an instantiation." — John Zachman, The Concise Definition of The Zachman Framework
References: - Zachman, J.A. (1987). A Framework for Information Systems Architecture. IBM Systems Journal, 26(3). - Zachman, J.A. (2008). The Concise Definition of The Zachman Framework. Business Rules Community. - About the Zachman Framework — Zachman International / FEAC Institute - Zachman International
The Two Axes¶
Communication Interrogatives (Columns)¶
The six primitive questions that can be asked about any complex thing:
| Column | Interrogative | Abstraction Name | What it describes |
|---|---|---|---|
| 1 | What | Inventory | The things of the enterprise — material compositions, inventory sets |
| 2 | How | Process | The functioning of the enterprise — process transformations, process flows |
| 3 | Where | Distribution | The locations and connectivity — distribution networks, geographic topology |
| 4 | Who | Responsibility | The people and organizations — responsibility assignments, authority structures |
| 5 | When | Timing | The events, cycles, and schedules — timing cycles, temporal ordering |
| 6 | Why | Motivation | The goals, strategies, and rules — motivation intentions, ends and means |
Reification Transformations (Rows)¶
The six levels of progressive concretization from abstract identification to physical instantiation:
| Row | Transformation | Common Perspective | What it produces |
|---|---|---|---|
| 1 | Identification | Executive / Planner | Scope contexts — naming and bounding the enterprise |
| 2 | Definition | Business Management / Owner | Business concepts — defining in business terms |
| 3 | Representation | Architect / Designer | System logic — logical models independent of technology |
| 4 | Specification | Engineer / Builder | Technology physics — technology-constrained physical models |
| 5 | Configuration | Technician / Implementer | Tool components — tool-specific implementation details |
| 6 | Instantiation | Enterprise / Worker | Operations instances — the functioning enterprise |
The 36 Cells¶
Each cell is the intersection of one interrogative and one reification transformation. It represents a primitive descriptive representation — the most atomic type of enterprise description.
What How Where Who When Why
(Inventory) (Process) (Distrib.) (Respons.) (Timing) (Motivation)
┌────────────┬────────────┬────────────┬────────────┬────────────┬────────────┐
Identifi- │ Inventory │ Process │ Distrib. │ Respons. │ Timing │ Motivation │
cation │ Identif. │ Identif. │ Identif. │ Identif. │ Identif. │ Identif. │
(Planner) │ │ │ │ │ │ │
├────────────┼────────────┼────────────┼────────────┼────────────┼────────────┤
Definition │ Inventory │ Process │ Distrib. │ Respons. │ Timing │ Motivation │
(Owner) │ Definition │ Definition │ Definition │ Definition │ Definition │ Definition │
│ │ │ │ │ │ │
├────────────┼────────────┼────────────┼────────────┼────────────┼────────────┤
Represen- │ Inventory │ Process │ Distrib. │ Respons. │ Timing │ Motivation │
tation │ Represent. │ Represent. │ Represent. │ Represent. │ Represent. │ Represent. │
(Designer) │ │ │ │ │ │ │
├────────────┼────────────┼────────────┼────────────┼────────────┼────────────┤
Specifi- │ Inventory │ Process │ Distrib. │ Respons. │ Timing │ Motivation │
cation │ Specif. │ Specif. │ Specif. │ Specif. │ Specif. │ Specif. │
(Builder) │ │ │ │ │ │ │
├────────────┼────────────┼────────────┼────────────┼────────────┼────────────┤
Configu- │ Inventory │ Process │ Distrib. │ Respons. │ Timing │ Motivation │
ration │ Config. │ Config. │ Config. │ Config. │ Config. │ Config. │
(Implmtr) │ │ │ │ │ │ │
├────────────┼────────────┼────────────┼────────────┼────────────┼────────────┤
Instanti- │ Inventory │ Process │ Distrib. │ Respons. │ Timing │ Motivation │
ation │ Instant. │ Instant. │ Instant. │ Instant. │ Instant. │ Instant. │
(Enterpr.) │ │ │ │ │ │ │
└────────────┴────────────┴────────────┴────────────┴────────────┴────────────┘
Key Principles¶
-
Each cell is primitive. A cell represents one and only one intersection. Real-world artifacts are often composite — they combine descriptions from multiple cells.
-
Cells are classification slots, not deliverables. Architecture deliverables (Architecture Definition Documents, roadmaps, governance packages) are compositions that aggregate multiple artifacts/views, each of which may cover one or more cells.
-
Cells are not viewpoints. A Zachman cell may correspond to a viewpoint family, but it only becomes a proper ISO 42010 viewpoint if stakeholders, concerns, model kinds, notations, and construction rules are explicitly defined.
-
The framework is not a methodology. It does not prescribe which cells to fill, in what order, or how much architecture to create. It classifies what could exist, not what should exist.
-
Rows have a meaningful order. The reification transformations progress from abstract (Identification) to concrete (Instantiation). Columns have no inherent methodological order.
Phase 2 — The Linked.Archi Semantic Model¶
Namespace and Assets¶
| File | Namespace | Content |
|---|---|---|
zachman.ttl |
https://meta.linked.archi/zachman# |
SKOS taxonomy: 6 interrogatives, 6 transformations, 6 perspectives, 6 abstractions, 36 cells |
zachman-shapes.ttl |
https://meta.linked.archi/zachman/shapes# |
SHACL validation: completeness and consistency checks |
zachman-deliverable-templates.ttl |
https://meta.linked.archi/zachman/deliverable-templates# |
EA Artifact Coverage Report (5 sections) |
zachman-metamodel.ttl |
https://meta.linked.archi/zachman/metamodel# |
Metamodel manifest (entry point) |
Concept Scheme Structure¶
The Zachman taxonomy is a single skos:ConceptScheme with five top concepts:
zach:ZachmanConceptScheme
skos:hasTopConcept zach:Interrogative, # 6 columns
zach:Perspective, # 6 row stakeholders
zach:ReificationTransformation, # 6 row transformations
zach:ColumnAbstraction, # 6 abstraction names
zach:ZachmanCell . # 36 intersection cells
Classification Properties¶
Linked.Archi provides three properties for Zachman classification:
| Property | Purpose | Level |
|---|---|---|
arch:viewpointCoversAspect |
Links to a Zachman interrogative (column) | Axis-level |
arch:viewpointFromPerspective |
Links to a Zachman perspective (row) | Axis-level |
arch:classifiedByFrameworkCell |
Links directly to a Zachman cell | Cell-level |
Additionally, for deliverables that aggregate multiple artifacts:
| Property | Purpose | Level |
|---|---|---|
arch:coversFrameworkCell |
Summary/derived coverage of a deliverable | Deliverable-level |
Cell Properties¶
Each of the 36 cells carries four linking properties:
zach:InventoryRepresentation
a skos:Concept ;
skos:broader zach:ZachmanCell ;
skos:prefLabel "Inventory Representation"@en ;
skos:altLabel "Logical Data Model"@en ;
zach:hasInterrogative :What ;
zach:hasColumnAbstraction :Inventory ;
zach:hasPerspective :ArchitectPerspective ;
zach:hasReificationTransformation :Representation ;
zach:rowOrder 3 ;
zach:columnOrder 1 ;
.
Relationship to Other Linked.Archi Concepts¶
┌─────────────────────────────────────────────────────────────────┐
│ Architecture Deliverable │
│ (e.g., Architecture Definition Document) │
│ arch:coversFrameworkCell zach:ProcessDefinition, ... │
│ │
│ ┌──────────────────────────────────────────────────────────┐ │
│ │ Architecture Artifact / View │ │
│ │ (e.g., Business Process Model) │ │
│ │ arch:classifiedByFrameworkCell zach:ProcessDefinition │ │
│ │ arch:governedByViewpoint ex:BPMNProcessViewpoint │ │
│ └──────────────────────────────────────────────────────────┘ │
│ │
│ ┌──────────────────────────────────────────────────────────┐ │
│ │ Architecture Artifact / View │ │
│ │ (e.g., Logical Data Model) │ │
│ │ arch:classifiedByFrameworkCell zach:InventoryRepresen. │ │
│ │ arch:governedByViewpoint ex:DataModelViewpoint │ │
│ └──────────────────────────────────────────────────────────┘ │
└─────────────────────────────────────────────────────────────────┘
Phase 3 — Practical Classification¶
Example 1: Classifying individual artifacts¶
@prefix zach: <https://meta.linked.archi/zachman#> .
@prefix arch: <https://meta.linked.archi/core#> .
@prefix ex: <https://model.example.com/myea#> .
# A business capability map — classified by axis
ex:CapabilityMap a arch:Model ;
skos:prefLabel "Enterprise Capability Map"@en ;
arch:viewpointCoversAspect zach:What ;
arch:viewpointFromPerspective zach:BusinessManagementPerspective .
# A logical data model — classified by cell
ex:CustomerDataModel a arch:Model ;
skos:prefLabel "Customer Domain Logical Data Model"@en ;
arch:classifiedByFrameworkCell zach:InventoryRepresentation .
# A deployment diagram — classified by cell
ex:ProductionDeployment a arch:Diagram ;
skos:prefLabel "Production Deployment Architecture"@en ;
arch:classifiedByFrameworkCell zach:DistributionSpecification .
# A business process model — classified by both axis and cell
ex:OrderFulfillmentProcess a arch:Model ;
skos:prefLabel "Order Fulfillment Process Model"@en ;
arch:viewpointCoversAspect zach:How ;
arch:viewpointFromPerspective zach:BusinessManagementPerspective ;
arch:classifiedByFrameworkCell zach:ProcessDefinition .
Example 2: Deliverable aggregating artifacts¶
@prefix zach: <https://meta.linked.archi/zachman#> .
@prefix arch: <https://meta.linked.archi/core#> .
@prefix ex: <https://model.example.com/myea#> .
# Individual artifacts
ex:ProcessFlowView a arch:ArchitectureView ;
skos:prefLabel "Order Processing Flow"@en ;
arch:classifiedByFrameworkCell zach:ProcessDefinition .
ex:InformationModelView a arch:ArchitectureView ;
skos:prefLabel "Order Information Model"@en ;
arch:classifiedByFrameworkCell zach:InventoryDefinition .
ex:OrgResponsibilityView a arch:ArchitectureView ;
skos:prefLabel "Order Fulfillment Responsibilities"@en ;
arch:classifiedByFrameworkCell zach:ResponsibilityDefinition .
# Deliverable that aggregates them
ex:OrderDomainArchitecture a arch:ArchitectureDeliverable ;
skos:prefLabel "Order Domain Architecture Definition"@en ;
arch:containsArtifact ex:ProcessFlowView ;
arch:containsArtifact ex:InformationModelView ;
arch:containsArtifact ex:OrgResponsibilityView ;
# Derived coverage summary
arch:coversFrameworkCell zach:ProcessDefinition ;
arch:coversFrameworkCell zach:InventoryDefinition ;
arch:coversFrameworkCell zach:ResponsibilityDefinition .
Example 3: Dual classification with EA on a Page¶
@prefix eaop: <https://meta.linked.archi/eaonapage/onto#> .
@prefix zach: <https://meta.linked.archi/zachman#> .
@prefix arch: <https://meta.linked.archi/core#> .
@prefix ex: <https://model.example.com/myea#> .
# A technology reference model — classified by both frameworks
ex:TechRefModel a arch:Model, eaop:Standard ;
skos:prefLabel "Enterprise Technology Reference Model"@en ;
# EA on a Page classification
eaop:artifactScope "organization-wide" ;
eaop:artifactLifecycle "permanent" ;
eaop:artifactNature "rules" ;
eaop:artifactFocus "IT-focused" ;
# Zachman classification
arch:viewpointCoversAspect zach:How, zach:What ;
arch:viewpointFromPerspective zach:ArchitectPerspective .
Example 4: Coverage gap analysis¶
PREFIX zach: <https://meta.linked.archi/zachman#>
PREFIX arch: <https://meta.linked.archi/core#>
PREFIX skos: <http://www.w3.org/2004/02/skos/core#>
# Which Zachman cells have no artifacts?
SELECT ?cell ?cellLabel ?perspLabel ?intLabel WHERE {
?cell skos:broader zach:ZachmanCell ;
skos:prefLabel ?cellLabel ;
zach:hasPerspective ?perspective ;
zach:hasInterrogative ?interrogative ;
zach:rowOrder ?row ;
zach:columnOrder ?col .
?perspective skos:prefLabel ?perspLabel .
?interrogative skos:prefLabel ?intLabel .
FILTER NOT EXISTS {
{ ?artifact arch:viewpointCoversAspect ?interrogative ;
arch:viewpointFromPerspective ?perspective . }
UNION
{ ?artifact arch:classifiedByFrameworkCell ?cell . }
}
}
ORDER BY ?row ?col
Example 5: Query by reification level¶
PREFIX zach: <https://meta.linked.archi/zachman#>
PREFIX arch: <https://meta.linked.archi/core#>
PREFIX skos: <http://www.w3.org/2004/02/skos/core#>
# All artifacts at the Representation (logical/architect) level
SELECT ?artifact ?label ?interrogative ?intLabel WHERE {
?perspective zach:hasReificationTransformation zach:Representation .
{
?artifact arch:viewpointFromPerspective ?perspective ;
arch:viewpointCoversAspect ?interrogative ;
skos:prefLabel ?label .
} UNION {
?cell zach:hasPerspective ?perspective ;
zach:hasInterrogative ?interrogative .
?artifact arch:classifiedByFrameworkCell ?cell ;
skos:prefLabel ?label .
}
?interrogative skos:prefLabel ?intLabel .
}
SHACL Validation¶
The zachman-shapes.ttl file provides validation rules:
- Completeness: If an artifact has a perspective, it should also have an interrogative (and vice versa)
- Consistency: If an artifact is classified by a cell, any explicit axis-level classification must match the cell's row and column
- Valid values: Perspective and interrogative values must be from the Zachman vocabulary
Run validation:
Appendix A — Common Misconceptions¶
| Misconception | Reality |
|---|---|
| "Zachman is a methodology" | It is a classification schema. It does not prescribe process, sequence, or governance. |
| "Each cell is a deliverable" | Cells classify primitive descriptions. Deliverables are compositions of multiple artifacts/views. |
| "Each cell is a viewpoint" | Cells are classification slots. A viewpoint requires additional semantics (concerns, model kinds, notations). |
| "You must fill all 36 cells" | The framework classifies what could exist. Most organizations fill 10-20 cells in practice. |
| "Columns are Data/Function/Network/People/Time/Motivation" | Those are IT-centric aliases. The formal names are Inventory/Process/Distribution/Responsibility/Timing/Motivation. |
| "Rows are just stakeholder audiences" | Formally, rows are reification transformations (Identification→Instantiation). Stakeholder perspectives are associated labels. |
Appendix B — Mapping Common Artifacts to Cells¶
This mapping is heuristic — artifacts may legitimately span multiple cells depending on scope and abstraction level.
| Artifact | Primary Cell(s) | Rationale |
|---|---|---|
| Business Capability Map | Inventory Definition | Defines the things the business does, in business terms |
| Business Process Model (BPMN) | Process Definition | Defines how the business works, in business terms |
| Logical Data Model | Inventory Representation | Represents data entities as a logical model |
| Application Architecture | Process Representation | Represents system functions as a logical model |
| Network Topology Diagram | Distribution Specification | Specifies network in technology terms |
| Organization Chart | Responsibility Definition | Defines who is responsible, in business terms |
| Roadmap | Timing Identification | Identifies key events and milestones at scope level |
| Strategy Map | Motivation Identification | Identifies goals and strategies at scope level |
| Physical Data Model | Inventory Specification | Specifies data in technology-specific terms |
| Deployment Diagram | Distribution Specification | Specifies deployment in technology terms |
| Security Model | Responsibility Representation | Represents access and authority as a logical model |
| Business Rules | Motivation Representation | Represents constraints as a logical model |
| DDL / Schema | Inventory Configuration | Configures data in tool-specific terms |
| Source Code | Process Configuration | Configures processes in tool-specific terms |
Appendix C — Comparison Articles¶
For detailed comparisons of the Zachman Framework with other frameworks in Linked.Archi:
- Zachman Framework vs EA on a Page — Two classification lenses on the same artifacts
- EA Frameworks Compared — Broader comparison across TOGAF, Zachman, EA on a Page, and others
References¶
- Zachman, J.A. (1987). A Framework for Information Systems Architecture. IBM Systems Journal, 26(3).
- Zachman, J.A. (2008). The Concise Definition of The Zachman Framework. Business Rules Community.
- About the Zachman Framework — Zachman International / FEAC Institute
- Zachman International
- ISO/IEC/IEEE 42010:2022 — Architecture description
- Linked.Archi Zachman Taxonomy
- Linked.Archi Zachman Metamodel
- Linked.Archi Frameworks Guide