EA_MetaModel
Enterprise Architecture Reference Frameworks
- Enterprise Architecture Reference Frameworks
- DoDAF - Department of Defense Architecture Framework (US)
- MODAF - British Ministry of Defense Architecture Framework (UK)
- NAF V4 $\rightarrow$ UAF
- FEAF - Federal Enterprise Architecture Framework
- TOGAF - The Open Group Architecture Framework
- Zachman Enterprise Architecture Framework
- The $EA^3$ Cube Approach
DoDAF - Department of Defense Architecture Framework (US)
URL: https://dodcio.defense.gov/library/dod-architecture-framework/
The detail framework 2.02 is here: https://dodcio.defense.gov/DODAF/
DoDAF Meta Model: https://dodcio.defense.gov/Library/DoD-Architecture-Framework/dodaf20_dm2/
Based on DoD Architeture Framework Version 2.02, here is the viewpoint:
The DoDAF Meta Model (DM2) defines three levels:
| DM2 Level | Name | Full Name | Content | Schema Files | Definitions and Aliases | Description Documents |
|---|---|---|---|---|---|---|
| DIV-1 | CDM | Conceptual Data Model | Concepts and concept relationships | N/A | Conceptual Data Model (CDM) Description, Manager and Core Process Stakeholder’s Guide to DM2 | |
| DIV-2 | LDM | Logical Data Model | Reified and Formailized Relationships | UML and XMI files employing IDEAS Profile | MS Excel file | Logical Data Model (LDM) Description, Architect’s Guide |
| DIV-3 | PES | Physical Exchange Schema | XML encoding of LDM | XML Schema Description (XSD) | Physical Exchange Specification (PES), Integrator, Data Analyst, and Developer’s Guide |
MODAF - British Ministry of Defense Architecture Framework (UK)
MODAF - The MOD Architecture Framework - is a set of rules that support UK Government’s defense planning and change management activities.
URL: https://www.gov.uk/guidance/mod-architecture-framework
The guidance was withdrawn on 15 January 2021, it had been replaced with the NATO Architecture Framework (NAF) V4.
The simplified overview of the MODAF Meta Model (M3) is here:
As the framework had been withdrawn, here are the MODAF documents downloaded from above website and list for reference (and archiving):
MODAF Guidance:
Viewpoints and Views:
- Views Summary Documents:
- All Views ViewPoint: AV Viewpoint
- Strategic View Viewpoint: StV Viewpoint
- Operational View Viewpoint:
- System View Viewpoint: SV Viewpoint
- Technical Standards View Viewpoint: TV Viewpoint
- Acquisition View Viewpoint: AcV Viewpoint
- Service Oriented View Viewpoint: SOV Viewpoint
MODAF Meta Model and MODAF Ontological Data Exchange Mechanism:
- MODAF Meta Model 3
- MODAF Ontological Data Exchange Mechanism: MODAF MODEM
Use and Examples of MODAF:
- Uses and Examples:
- The MODAF Architecturing Process
- MODAF Support to Analysis of Capability Integration in the Context of Defense Lines of Development (DLODs)
- MODAF Support to User Requirements Definition
- MODAF Support to System Requirements Definition
- MODAF Support to Dependency Analysis
- MODAF Support to Gap Analysis
- Creating Capability Architectures with MODAF
Frequently Asked Questions:
- Ontologies and Their Use in MODAF
- MODAF Glossary
- Comparison of MODAF with Other Frameworks
- How MODAF can Reflect Security Concerns
- Unified Modeling Language (UML) Relation to MODAF
- Coherency across Models with MODAF
- Sharing Architecture Data
- Other Frequently Asked Questions
Other MODAF Reference:
NAF V4 $\rightarrow$ UAF
URL: https://www.nato.int/en/about-us/organization/nato-structure/digital-policy-committee-dpc/nato-architecture-framework-version
Current version is V4.1 as of March 2026.
You can find the downloaded documents here: NAF V4.1
NAFv4_Meta-Model can be found here: https://nafdocs.github.io/modem/
Below shows the NATO’s roadmap to Unified Architecture Framework:
FEAF - Federal Enterprise Architecture Framework
FEAF - Federal Enterprise Architecture Framework - is developed by the Federal Government of the United States and is the industry standard for government enterprise architecture frameworks.
It’s archived here https://obamawhitehouse.archives.gov/omb/e-gov/fea till 2013.
The Consolidated Reference Model (CRM) of the FEAF equips OMB (Office of Management and Budget) and Federal agencies with a common language and framework to describe and analyze investments. It contains a set of interrelated “reference models” designed to facilitate cross-agency analysis and the identification of duplicative investments, gaps and opportunities for collaboration within and across agencies.
| RM | RM-FullName | Description | Content | Artefacts |
|---|---|---|---|---|
| PRM | Performance Reference Model | links agency strategy, internal business components, and investments, providing a means to measure the impact of those investments on strategic outcomes. | - Cross-Agency and Inter-Agency Goals and Objectives - Uniquely tailored performance indicators |
- Goals - Meas. Area - Meas. Category |
| BRM | Business Reference Model | describes an organization through a taxonomy of common mission and support service areas instead of through a stove-piped organizational view, thereby promoting inter- and inter-agency collaboration. | - Intra- and inter-agency shared services - Agencies, customers, partners, providers. |
- Mission Sector - Business Function - Service |
| DRM | Data Reference Model | facilitates discovery of existing data holdings residing in “silos” and enables understanding the meaning of the data, how to access it, and how to leverage it to support performance results. | - Business-focused data standardization - Cross-agency information exchanges |
- Domain - Subject - Topic |
| ARM | Application Reference Model | categorizes the system- and application-related standards and technologies that support the delivery of service capabilities, allowing agencies to share and reuse common solutions and benefit from economies of scale. | - Software providing functionality - Enterprise service bus |
- System - Application Component - Interface |
| IRM | Infrastructure Reference Model | categorizes the network/cloud related standards and technologies to support and enable the delivery of voice, data, video, and mobile service components and capabilities. | - Hardware providing functionality - Hosting, data centers, cloud, virtualization |
- Platform - Network - Facility |
| SRM | Security Reference Model | provides a common language and methodology for discussing security and privacy in the context of federal agencies’ business and performance goals. | - Risk-adjusted security/privacy protection - Security control design / implementation |
- Purpose - Risk - Control |
Consolidated Reference Model Relationship Diagram is as below:
TOGAF - The Open Group Architecture Framework
URL: https://www.opengroup.org/togaf
TOGAF 9.1 Simplified Meta Model:
Here is TOGAF 9 to Essential Meta Model Concept Mapping
Zachman Enterprise Architecture Framework
The Zachman framework provided a fresh perspective of looking at and developing enterprise architecture. It asks the questions of What, How, When, Who, Where, and Why–and the integration and answers to these questions that enable the comprehensive, composite overview of complex ideas used to plan, implement, process and evaluate an organization’s enterprise structure.
Here is a comparison between Zachman vs TOGAF:
The $EA^3$ Cube Approach
Enterprise Architecture = Strategy + Business + Technology
(EA = S + B + T)
