Developing an EA
Methodologies and Processes
An EA development methodology is a body of methods, rules and postulates used to structure, plan, and implement the process of developing an EA. A methodology usually specifies a set number of development phases, each with its own defined inputs and outputs. The goal is to enable the EA to be developed in a consistent and systematic manner.
A process is a series of defined actions or operations to be followed to achieve some result. A methodology may define one or more processes to be followed, or it may define a set of actions and outcomes without prescribing the sequence of the actions. A variety of EA development methodologies have evolved over the years, giving the EA team the opportunity to select the best match to their needs. Prominent EA methodologies include The Open Group Architecture Framework (TOGAF) Architecture Development Method (ADM), the Federal Enterprise Architecture (FEA) methodology, and the Gartner EA practice.
This topic area includes guidance, research, case studies, sample artifacts, and other references that will help the EA practitioner select and apply the most appropriate methodologies to apply to an EA effort.
- Cane, S., Martinez, C.E., (2012) Organizationally-Agnostic Business Modeling: A Case Study, MITRE Corporation
- Martinez, C.E, Cane, S.A. (2012) Organizationally-Agnostic Business Modeling: How to Make Business Architecture Adaptable to Organization Change, MITRE Corporation
- Gianni, D., (2015) Data Policy Definition and Verification of System of Systems Governance, in L. Rainey, A. Tolk (eds.) Modeling and Support for System of Systems, 99-130
EABOK® Knowledge Areas
Organizational Scope and Structure of EA
Developing an EA
- Business Requirements and Value Proposition
- Methodologies and Processes
- Architecture Frameworks
- Data and Information Management
- Project Management
- Change Management
- Testing and Evaluation
- Modeling and Simulation
- Role of Reference Architectures
- How to Build a Reference Architecture
- Coordinating the Creation of a Reference Architecture
Management of EA
EA in Practice
Perspectives on EA
EABOK is an evolving knowledge base and more information will be released as available.
In addition to the EABOK Board members, the content is also contributed by the following MITRE employees:
- Carla Kendrick
- Brenda Yu
- Eddie Wang
- Rose Tykinski
- Wakar Khan
- Mike Russell
This website is managed by the EABOK Consortium and hosted by MITRE to enable stakeholder collaboration within the EA community.
EABOK and the EABOK logo are trademarks of MITRE and are used by The EABOK Consortium with permission.
All other trademarks are the property of their respective owners. All rights reserved.