Submit Material

The EABOK accepts web page contributions on an ongoing basis. If you are interested in contributing a new page or updating an existing page, please follow the instructions below. We will email you when your submission is received and will update you during the review process. If a submission is accepted, it typically takes 30 days to post once the review is complete.

Instructions: Each web page should address a single topic. If the topic you wish to write about does not exist, please feel free to propose a new one. When writing, please consider the knowledge type descriptions below. The intended audience of this material ranges from new practitioners, to academics, to seasoned Enterprise Architectures (EAs). Please make your page concise and easily readable, while providing substantive content.

Web page content should include the following:

• An introductory paragraph describing the overall focus of the page
• Content of up to 5,000 words
• URLs to relevant websites (please summarize, but do not re-write existing material)
• References in alphabetical order by author, using American Psychological Association style
• For further reading, identify books, websites, or other materials for the reader’s consideration

Let’s get started! When your submission is ready:

Download and complete these forms:

• Submission table – This form contains the information that we need in order to review and categorize the material.
• Author certification form – The EABOK is a community-developed website that is hosted by The MITRE Corporation. Authors retain their rights to copyright for all contributions to the EABOK and should include their copyright information on their submissions. Legal requirements require us to confirm that you are authorized to publish the submitted content on the EABOK website by affirming that your submission will not violate or infringe on any copyright. This authorization is confirmed by reviewing the form that you submit with your package (see the three form types below). By completing this form, you certify that you hold the copyright to the submitted material and that you are authorized to publish it. This meets MITRE’s legal requirements for copyright infringement protection. Contact us if you need assistance with completing the forms. The forms are complex, and we will be happy to help you with them.
• Form A – For U.S. authors who are not U.S. government employees
• Form B – For U.S. authors who are government employees
• Form C – For non-U.S. citizens

Email the completed forms with your proposed content. Additional information is available in our FAQ section

Knowledge Type Descriptions

The following knowledge types are provided as suggestions for the types of material suitable for the EABOK:

Synthesis
Systemic review and distillation of an EA topic—an overall picture of what is known about the topic, containing a review of the literature and best practices in the topic area.

Analysis
A 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.

Method
A general systematic procedure, process, or technique for developing or evaluating a specific EA 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.

Pattern
A common, reusable solution that is applied and tailored to specific EA situations. Examples can include architecture building blocks; reference architectures; 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, the revision of accepted theories or laws in the light of new facts, or the practical application of such new or revised theories or laws [based on Merriam-Webster.com].

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

Comparisons and distinctions
Pattern and method: Patterns are distinguished from methods in the EABOK: 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.