Insight · Frameworks

TOGAF vs Zachman Framework: Which Architecture Framework for Your EA Program?

By Sparx Services · January 26, 2026 · 7 min read

TOGAF and Zachman are not rivals — they answer different questions. TOGAF is a process framework: it tells you how to do enterprise architecture, through the Architecture Development Method (ADM), governance structures, and a content metamodel. Zachman is a classification framework: it tells you how to organize architecture artifacts across six perspectives and six interrogatives. Most organizations run TOGAF as their process, ArchiMate as their notation, and reach for Zachman thinking only when they need to design an artifact taxonomy. Starting a program today? TOGAF is the anchor. Zachman earns its place in large, formal artifact libraries.

The split that resolves the whole debate

The "versus" in the title is misleading. These two frameworks operate on different axes — one is about activity, the other about taxonomy — and seeing that distinction clearly is what lets you stop choosing and start combining.

TOGAF — a process for doing EA

What it gives you: the ADM — a cyclical, phase-based method that takes you from architecture vision through the business, information, application, and technology domains to migration and governance.
Core question answered: what do I do, and in what order?
Strength: comprehensive, certifiable, and supported by a vast tooling and consulting ecosystem.
Weakness: abstract. It tells you to produce an Application Architecture; it does not tell you how to model one.
Maturity: now in version 10 (2022), modularized so you can adopt only the parts you need.

Zachman — a scheme for organizing artifacts

What it gives you: a 6×6 ontology — six perspectives (Executive to Enterprise) crossed with six interrogatives (What, How, Where, Who, When, Why) — defining 36 artifact cells.
Core question answered: where does this artifact belong, and is anything missing?
Strength: intellectually complete. Every artifact has exactly one home; nothing falls through a gap.
Weakness: operationally heavy. Classifying before modeling drains energy, and almost no program fills all 36 cells.
Maturity: created by John Zachman in 1987; still actively developed and widely taught.

What TOGAF actually contains

The Open Group Architecture Framework is the most widely adopted EA framework in the world, with well over 100,000 certified architects. Three pieces carry most of the value:

The Architecture Development Method (ADM) is a cyclical, phase-based process — Preliminary, phases A through H, and Requirements Management — that walks architects from establishing EA capability, through architecture vision and the four architecture domains, into migration planning, implementation governance, and change management.

The Architecture Content Framework is a metamodel of work products: the deliverables, artifacts, and building blocks an EA program produces.

The Architecture Capability Framework supplies the structures for standing up an EA function — the Architecture Review Board, the Architecture Repository, and the governance processes around them.

TOGAF's strength is breadth and shared understanding. Its limitation is abstraction: it specifies that you create an Application Architecture but stays silent on how to model it. That is where Sparx EA and ArchiMate come in.

What Zachman actually contains

The Zachman Framework for Enterprise Architecture, created by John Zachman in 1987, is one of the earliest EA frameworks and a two-dimensional ontology that classifies artifacts across:

Six perspectives (rows): Executive (Contextual) — scope and strategy; Business Management (Conceptual) — business owner models and processes; Architect (Logical) — logical system design; Engineer (Physical) — physical specifications; Technician (Detailed) — real implementation components; Enterprise (Operational) — the deployed enterprise itself.

Six interrogatives (columns): What (Data), How (Function), Where (Network), Who (People), When (Time), Why (Motivation).

The resulting 6×6 matrix defines 36 cells, each a specific artifact type seen from a specific perspective. An entity-relationship diagram lives in the Architect row, What column; a business process flow lives in the Business Management row, How column.

The Zachman matrix in practice

Zachman's appeal is completeness — every conceivable artifact has a place, and nothing slips through. The operational challenge is consistency: teams that adopt the matrix as their primary operating model burn significant effort on classification before they have modeled anything, and the 36-cell structure implies a coverage level almost no organization reaches.

In real programs, Zachman thinking tends to surface in three ways:

Artifact taxonomy design. Large organizations building an artifact library use the perspectives and interrogatives as a completeness check — "do we have anything in the Executive/Why cell? What is our Technician/What artifact?"
Academic and research contexts. Zachman is widely taught and remains a reference framework for EA ontology research.
Audit and compliance. Some government and defense architectures use Zachman-style classification for artifact compliance checking.

Why TOGAF won the market

TOGAF achieved dominant adoption for pragmatic reasons.

It is a process, not just a taxonomy. Architects needed to know what to do on Monday morning. The ADM answered that. Zachman told them which artifacts existed, but not how to produce them or in what sequence.

It is certifiable. TOGAF Foundation and Architect certifications created a global talent pool and organizational demand for TOGAF-aligned practice.

It is vendor-supported. Consulting firms, tool vendors (Sparx Systems among them), and training providers built ecosystems around it. ArchiMate — also from The Open Group — was designed to complement TOGAF, giving it a modeling notation Zachman never had.

It evolved. TOGAF 10 (2022) modularized the framework, letting teams adopt relevant components without committing to the full ADM. That adaptability kept it current.

How Sparx EA supports both frameworks

Sparx EA supports both through its MDG Technology extension mechanism.

TOGAF. Sparx EA ships with TOGAF support, including the Content Metamodel element types (Principle, Requirement, Gap, Work Package, Plateau, and more) and TOGAF-specific diagrams. The ADM phases map to a recommended package structure within the repository.

Zachman. The Zachman MDG extension maps the 36 cells to stereotyped packages and elements. Most teams that use it do so for classification tagging — applying a tagged value indicating which Zachman cell an artifact belongs to — rather than treating the grid as their primary model structure.

The pattern that works in most implementations: ArchiMate as the primary notation, a custom organizational MDG for governance on top, and optional Zachman classification tags applied to artifacts for taxonomy and reporting. See why Sparx EA handles multi-framework programs in one repository.

When Zachman earns its place

Despite the operational overhead, Zachman is worth fluency in specific situations:

Large-organization artifact taxonomy. Designing an artifact library across multiple EA teams? Map your planned artifacts to the matrix and let the gaps reveal themselves.
Stakeholder communication. The perspectives (Executive, Business Management, Architect, Engineer, Technician) are a useful vocabulary for explaining why different views exist and who each is for.
Framework design. Building a custom methodology rather than adopting TOGAF? Zachman gives you a principled structure for deciding what to cover.
Academic and government contexts. Architects presenting to academics, or working inside frameworks that reference Zachman, benefit from the fluency.

The practical recommendation

For an organization starting or maturing an EA program:

Anchor on TOGAF process

Use TOGAF (or a TOGAF-informed approach) as your EA process. You do not need every ADM phase — adopt what is relevant and skip the rest.

Model in ArchiMate

Use ArchiMate as your primary notation in Sparx EA. It supplies the semantic precision TOGAF's content framework implies but never specifies.

Borrow Zachman for taxonomy

Draw on Zachman thinking when designing your artifact taxonomy — but do not try to run the 36-cell matrix as your primary operational structure.

Implement in Sparx EA

Use Sparx EA to carry whichever frameworks you adopt. It supports both, and the MDG mechanism lets you layer custom governance on top.

Frequently asked questions

Can I use TOGAF and Zachman together in the same program?

Yes, and it is fairly common. Run TOGAF as your process — the ADM phases guide what you do and when — and use Zachman classification as a taxonomy overlay on your artifact library, applying cell tags via tagged values in Sparx EA. The two address different concerns and do not conflict.

Is Zachman still relevant in 2026?

It remains conceptually relevant as an EA ontology and is widely cited in academic literature. Its operational adoption has declined relative to TOGAF, but it endures as a reference for artifact completeness and a teaching tool for EA concepts. John Zachman continues to actively develop the framework.

Does Sparx EA support TOGAF natively?

Yes. Sparx EA ships with a TOGAF MDG that includes the Content Metamodel element types, ADM phase diagrams, and the Architecture Repository structure. You can model all TOGAF deliverables directly, with no extra configuration. Sparx Services implements TOGAF support as part of the Configure the Solution engagement.

Which framework is better for government EA programs?

It depends on jurisdiction. US federal programs typically reference FEAF or DoDAF, both with Zachman influences. Australian federal programs lean toward TOGAF; UK government uses TOGAF-aligned approaches. In every case Sparx EA supports the relevant framework via MDG extensions, and Sparx Services can advise on the right choice for your jurisdiction.

Do I need TOGAF certification to use TOGAF?

No. Certification demonstrates knowledge but is not required to apply the framework. Many organizations run TOGAF-informed processes without formal certification, though having at least one certified architect helps ensure correct application. Sparx Services architects hold TOGAF certifications.

Is ArchiMate part of TOGAF?

They are separate frameworks, both from The Open Group, designed to complement each other. TOGAF defines the process and content; ArchiMate defines the modeling language. The ADM phases guide what work is done; ArchiMate provides the notation for the resulting models. Sparx EA implements ArchiMate natively and connects it to TOGAF content elements.

Choose the framework, then start building

Most teams need a guide to cut through the framework landscape and reach practical decisions. The Paralysis to a Plan engagement establishes your framework selection, tool configuration, and governance design — so you start building architecture instead of debating frameworks. For teams that already have a framework but need the governance infrastructure built, Configure the Solution delivers MDG governance, naming conventions, and artifact taxonomy in Sparx EA.

Still debating frameworks instead of building?

Talk to a practitioner about anchoring your EA program on the right framework — and standing it up in Sparx EA.

Book a call →

Keep reading