DoDAF 2.02 (DoD Architecture Framework Version 2.02)
Volume I: executive accountability, architecture types, fit-for-purpose use, the four conformance levels and the data-centric approach (Change 1, January 2015) – DoDAF 2.02 (DoD Architecture Framework Version 2.02)

DoDAF 2.02 (DoD Architecture Framework Version 2.02) DODAF-4.1: Architectural data and DM2 exchange

What does DODAF-4.1 require?

Architectural data should come from the DM2 set that is the minimum needed for departmental decisions, be expressed through the conceptual and logical data models, and be exchanged in a specified form such as the Physical Exchange Specification or DM2-OWL. Tools should use the DM2 specifications so data can be integrated, reused and exchanged across the Department and with partners.

Maintained by Gerard Blokdyk

Other controls in Volume I: executive accountability, architecture types, fit-for-purpose use, the four conformance levels and the data-centric approach (Change 1, January 2015) – DoDAF 2.02 (DoD Architecture Framework Version 2.02)

Query this from an agent

The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.

MCP endpointAll DoDAF 2.02 (DoD Architecture Framework Version 2.02) controls