Enterprise Architecture Body of Knowledge
Open-knowledge reference entry

The Enterprise Architecture Body of Knowledge (EABOK) is a guide to Enterprise Architecture produced by MITRE's Center for Innovative Computing and Informatics, and is substantially funded by US government agencies. It provides a critical review of enterprise architecture issues in the context of the needs of an organization. Because it provides a "big picture" view of needs and methods, some enterprise architecture practitioners recommend it as starting point for a business establishing an enterprise architecture unit.
Overview
The Guide to the Enterprise Architecture Body of Knowledge (EABOK) organizes and characterizes the knowledge content of the Enterprise Architecture (EA) discipline. This organization and characterization promotes a consistent view of EA, establishes the scope and bounds of the EA discipline, and places the discipline in the context of related disciplines. The EABOK subdivides EA into knowledge areas and topics within each area, presents an overview of the topic, and provides the reader references for further information. The EABOK is a guide to EA, not the body of knowledge itself.
The current printable version is marked DRAFT, dated 06-Feb-2004, and edited by Dr Paula J Hagan. It has been approved for public release; distribution unlimited. No updates have been made to any publicly released version of this document since 2004, and the project appears to have been abandoned.
This brief starts where responsible research should: with the source description of “Enterprise Architecture Body of Knowledge” as open-knowledge reference entry. Everything that follows is an evidence route, not borrowed authority.
Why this record matters
The subject matters to the general reference register because the source frames it as open-knowledge reference entry. Its deeper value depends on whether names, dates, institutions and citations support that framing.
Vocabulary and entity names are the principal evidence signals here, because they determine the precision of every later search. The source revision retrieved here is dated Jan 23, 2026. The linked authority identifier is Q5380284. None of the 0 selected statements returned an explicit reference. The first chronological checks are 2004.
A concise general-reference account can conceal disagreements about scope, terminology or the weight assigned to individual sources. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “Enterprise Architecture Body of Knowledge”, its source revision and the description used here.
- Expand the search: follow Enterprise Architecture Body of Knowledge primary sources, Enterprise Architecture Body of Knowledge archive and Enterprise research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Enterprise Architecture Body of Knowledge”?
- Which institution is responsible for the underlying evidence?
- Which cited source is closest to the event, object or claim?
Search terms from this dossier
This entry incorporates text from “Enterprise Architecture Body of Knowledge” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.