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.

Further Reading

1. Cane, S., Martinez, C.E., (2012) Organizationally-Agnostic Business Modeling: A Case Study, MITRE Corporation
2. Martinez, C.E, Cane, S.A. (2012) Organizationally-Agnostic Business Modeling: How to Make Business Architecture Adaptable to Organization Change, MITRE Corporation
3. 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