Enterprise Architecture Body of Knowledge


The EABOK relies on and welcomes contributions from members of the EA community to advance our profession. If our editorial review board approves your submission for publication on this site, we will promote you and your work to the EA community worldwide.

All submissions should be—

  • Either new material or previously published content. You may include links or citations to existing material in your work, e.g. websites, books, periodicals and other publications
  • Based on evidence or practice
  • Clear, concise and easily understandable
  • 1-12 pages long
  • Focused on the selected EA knowledge area and/or topic. If you wish to propose a new knowledge area and/or topic, please indicate that and include the rationale when completing the submission table
  • In an unlocked PDF or Microsoft Word format
  • In English
  • Free of spelling and grammar errors.

Please Note:

  • Material posted to this website is not an implicit or explicit endorsement by EABOK's sponsor, The MITRE Corporation.
  • Marketing materials about a specific software or tool, training, etc., will not be considered.
  • It's the author's responsibility to ensure content submissions don't contain proprietary or otherwise restricted information.

Questions? Send us an mail.


Submit Material

The EABOK considers new and previously published material on an ongoing basis. We will email you when your submission is received, and update you during the review. If a submission is accepted, it typically takes 30 days to post once the review is complete.

Let's get started! Complete these two forms for all submissions:

  • Submission table - This form has the information we need to review and categorize the material.
  • Author certification form - The form confirms you are authorized to publish the material on the EABOK website.

NEW material should include the following, if possible:

  • Abstract—Include an abstract describing the overall focus of the paper.
  • References—List all references at the end of the submission, preferably in alphabetical order by author using American Psychological Association style. Authors may reference longer work(s) or websites with a hyperlink.

PREVIOUSLY published material (paper, book, etc.) should be accessible to the general public via a publisher or a website. Please include a copy of the material (if allowed by copyright), or a pointer to the material, consisting of one or both of the following as appropriate:

  • Citation: Identify the reference citation of the material (authors, title, date, journal or publisher) using American Psychological Association style.
  • URL: Identify the website link (URL) to the material.

Click here to email the completed forms with your proposed content.

Quick Links:

Knowledge Type Descriptions

Systemic review and distillation of an EA topic, providing an overall picture of what is known about the topic; reflecting review of the literature and of best practice in the topic area.

Systematic investigation of an EA topic or a specific element within that topic, such as a specific method or framework, or a comparison of different elements.

Case study
An in-depth example of the application of EA practices, principles, and concepts that are based on real-life context.

General systematic procedure, process, or technique for developing or evaluating a specific enterprise architecture or related artifact. Examples can include architecture development methods, such as the TOGAF Architecture Development Method, architecture evaluation methods, modeling methods, enterprise analysis methods, etc.

A pattern in EA is a common reusable solution that is applied and tailored to specific EA situations. Examples can include architecture building blocks, reference architectures, and reference models such as the TOGAF Technical Reference Model, taxonomies such as the FEA Reference Models, domain architectures, domain models, common use cases, common organizational structures, and other reusable or standardized EA artifacts.

Research result
Emerging EA knowledge that is the outcome of investigation or experimentation aimed at the discovery and interpretation of facts, revision of accepted theories or laws in the light of new facts, or practical application of such new or revised theories or laws [based on Merriam-Webster.com].

Sample artifact
Model, collection of information, or document that describes one EA or some aspect of it, or describes an operation on it such as simulation or testing. Examples can include specific instances of enterprise architectures, architecture views, architecture or enterprise models, organization structures, etc.

Comparisons and Distinctions
Pattern and Method: Patterns are distinguished from Methods in the EABOK this way: A method is a general process for creating new specific solutions to specific situations, while a pattern is an accepted general solution that can be tailored to specific situations.

Pattern and Sample Artifact: A sample artifact is usually taken to mean one specific solution for one specific situation, while a pattern is a general solution that applies to multiple specific situations. A pattern is often the result of abstracting from and generalizing multiple sample artifacts.

Author Certification Form

The authors or their organizations will retain their rights to copyright, and should include their copyright information on their submissions. Authors must affirm their submission will not violate or infringe on any copyright by submitting one of the forms below with their package.

  • Form A - For U.S. authors (excludes U.S. government employees)
  • Form B - For U.S. authors who are government employees
  • Form C - For foreign nationals


Reviewer Guidelines

The EABOK's editorial review board follows the reviewer guidelines to determine if submissions meet the necessary criteria for publication on this website.
Quick Links: