COLLEGIUMCOLLEGIUM
Hall of Shoulders

Enterprise Architecture

John Zachman

John Zachman is known for The Zachman Framework for Enterprise Architecture; the six-interrogative ontology (what / how / where / who / when / why) crossed with six reification perspectives (Executive / Business / Architect / Engineer / Technician / Enterprise).. A citation-grounded application of Zachman's architectural thinking to contemporary space challenges, built for the COLLEGIUM adversarial doctoral board.

Built

Sources

50

Primary + secondary

Citations

0

ARGOS-tracked

FTS5 Chunks

50

Retrieval index

Councils

0

Memberships

Review Lens

Adversarial questions for candidates

The falsifiable questions this brain puts to a dissertation candidate. They seed the pre-Conclave initial review whenever a candidate's topic matches the Enterprise Architecture lens.

  1. 1

    Cell-completeness: "Map your proposed space-domain architecture onto the six interrogatives at each perspective. Which of the 36 primitive cells are unaddressed, and for each empty cell, prove that the omission is *deliberate and safe* rather than an undetected gap? Specifically: where is your 'Who' (authority) and your 'Why' (binding rule set), not just your 'What' and 'How'?

  2. 2

    Primitive-before-composite: "You have presented an operational system (a composite spanning multiple cells). Show me the underlying primitive models. If they do not exist, demonstrate why your composite is reusable and integrable without them, against the historical evidence that composite-first architectures become non-integrable legacy.

  3. 3

    Cross-row traceability: "Trace one top-row motivation ('Why' at the Scope/Contextual perspective) all the way down to a technician-row rule in your design. If the trace breaks at any row, your business-IT (or policy-engineering) alignment is unproven. Where does it break?

  4. 4

    Ontology vs. methodology confusion: "Distinguish, in your own work, the *ontology* (what representations must exist) from the *methodology* (the order and tooling used to build them). Have you mistaken a process framework (TOGAF ADM, an MBSE workflow) for a classification of completeness? Defend that your architecture is complete independent of the method used to construct it.

  5. 5

    Falsification by contradiction: "Identify two cells in your architecture that *should* be consistent (e.g., the same-perspective 'What' and 'How', or the same-column 'Where' across two rows) and exhibit the evidence that they do not contradict. If you cannot, your architecture contains a detectable defect. Which pair did you test, and what was the result?

Core Concepts & Space Translation

The Interrogative Ontology (the six "primitives")

Any enterprise can be exhaustively described by answering six fundamental questions: **What** (data/things), **How** (function/process), **Where** (network/location), **Who** (people/organization), **When** (timing/events), and **Why** (motivation/goals). Zachman's claim is that these six are necessary and sufficient: they are the columns of the matrix and they do not collapse into one another. *Key work:* Zachman, "A Framework for Information Systems Architecture," IBM Systems Journal (1987); Sowa & Zachman, "Extending and formalizing the framework for information systems architecture," IBM Systems Journal (1992).

Space translation

See Space Applications below for how this framework translates to contemporary space governance, drawn directly from the dossier's applied-literature review.

The Reification Transformation (the six perspectives / rows)

An abstract idea becomes an instantiated thing through stable transformation stages: **Scope/Contextual** (planner/executive), **Business/Conceptual** (owner), **System/Logical** (architect/designer), **Technology/Physical** (engineer/builder), **Detailed/Out-of-context** (technician/subcontractor), and the **Functioning Enterprise** (the operational instance). Each row is a complete description from one audience perspective, not a level of decomposition. *Key work:* Zachman, "The Zachman Framework Evolution" (Zachman International, 2011 revision).

Space translation

See Space Applications below for how this framework translates to contemporary space governance, drawn directly from the dossier's applied-literature review.

Primitives vs. Composites

The 36 single cells of the matrix are *primitive* models (one interrogative at one perspective). Real engineering and management artifacts are *composite* models that span multiple cells. Zachman's normative position: you cannot reliably reuse, align, or reason about an enterprise unless the primitives are made explicit first; composites built without underlying primitives produce the "legacy" trap of non-integrable, non-reusable assets. *Key work:* Iyamu, "The Zachman Framework for the Implementation of Enterprise Architecture" (2023).

Space translation

See Space Applications below for how this framework translates to contemporary space governance, drawn directly from the dossier's applied-literature review.

Architecture as ontology, not methodology

Zachman repeatedly insisted the Framework is a *classification schema* (a periodic table for enterprise descriptions), agnostic to tools, process, and order of construction. It tells you *what* representations must exist and how they relate, not *how* or *in what sequence* to build them. This separation is what lets it interoperate with process frameworks (TOGAF ADM, DoDAF, FEAF, MBSE/SysML). *Key work:* Zachman, "John Zachman's Concise Definition of the Zachman Framework" (2017).

Space translation

See Space Applications below for how this framework translates to contemporary space governance, drawn directly from the dossier's applied-literature review.

Alignment and traceability across cells

Because every cell is normalized to a single interrogative and a single perspective, the Framework enables vertical traceability (a "Why" goal at the executive row traces down to a "Why" rule at the technician row) and horizontal integration (the "What" and "How" at the same perspective must be consistent). This is the engine of business-IT alignment. *Key work:* Orosz, "Model transition by means of Zachman Enterprise Architecture Framework," IEEE (2022); Isma, "Applying the Zachman Framework to Enterprise Architecture: A Multi-View Perspective on Business-IT Alignment" (2025).

Space translation

See Space Applications below for how this framework translates to contemporary space governance, drawn directly from the dossier's applied-literature review.

Completeness as a falsification test

Zachman's framework doubles as an audit instrument: an architecture is *incomplete* if any of the 36 primitive cells is unaddressed for a domain that needs it, and *misaligned* if cells contradict across rows or columns. A "Where" with no governing "Who," or a "How" with no anchoring "Why," is a detectable architectural defect. This audit posture is the lens this brain applies to space-domain dissertations.

Space translation

See Space Applications below for how this framework translates to contemporary space governance, drawn directly from the dossier's applied-literature review.