DoDAF V2.0 is the overarching, comprehensive framework and conceptual model enabling the development of architectures to facilitate DoD managers at all levels to make key decisions more effectively through organized information sharing across Department, Joint Capability Areas (JCAs), Component, and Program boundaries. DoDAF V2.0 focuses on architectural data as information required by key DoD decision makers, rather than on developing individual products. The DoDAF-described Models described in this volume and Volume 2 are used to obtain and visualize data requirements. The framework also enables architecture content to be built that is “Fit-for-Purpose”, as defined and described in Section 1.4. DoDAF is one of the principal pillars supporting the responsibilities Department of Defense Chief Information Officer (DoD CIO) in exercise of his responsibilities for development and maintenance of architectures required under the Clinger-Cohen Act. DoDAF also explains guidance from OMB Circular A- 130 and other appropriate DoD directives and instructions; this version of the Framework also provides guidance on the development of architectures supporting the development of Netcentric services within the Department. DoDAF also serves as the principal guide for development of integrated architectures, as defined in DoD Instruction 4630.82, which states: “An architecture consisting of multiple views or perspectives facilitating integration and promoting interoperability across capabilities and among integrated architectures”. The term integrated means that data utilized in more than one instance in the architectural views is commonly understood across those views.
Defines standard
Replaced/Superseded by document(s)
Cancelled by
Amended by
| File | MIME type | Size (KB) | Language | Download | |
|---|---|---|---|---|---|
| DoD Architecture Framework Vol. I Introduction, Overview, and Concepts.pdf | application/pdf | 3.44 MB | English | DOWNLOAD! |
Provides definitions
Cover images
Summary
The Department of Defense Architecture Framework (DoDAF), Version 2.0 serves as the overarching, comprehensive framework and conceptual model enabling the development of architectures to facilitate the ability of Department of Defense (DoD) managers at all levels to make key decisions more effectively through organized information sharing across the Department, Joint Capability Areas (JCAs), Mission, Component, and Program boundaries. The DoDAF serves as one of the principal pillars supporting the DoD Chief Information Officer (CIO) in his responsibilities for development and maintenance of architectures required under the Clinger-Cohen Act. It also reflects guidance from the Office of Management and Budget (OMB) Circular A-130, and other Departmental directives and instructions. This version of the Framework provides extensive guidance on the development of architectures supporting the adoption and execution of Net-centric services within the Department. DoD managers, as process owners, specify the requirements and control the development of architectures, as described in this volume, within their areas of authority and responsibility. In that role, they select an architect and an architecture development team to create the architecture in accordance with the requirements defined by the process owner. As described in Volume 1, architecture concentrates on those data that correspond to architecture requirements. The duties of the architect and the architecture team that create the architecture are further described in more technical language in Volume 2 of DoDAF. The architect supervises development of the architecture, and ensures that the requirements and visual representations of the architecture meet process owner requirements and ensures that conformance requirements described in this volume and in Volume 2 are met DoD Components are expected to conform to DoDAF in development of architectures within the Department. Conformance ensures that reuse of information, architecture artifacts, models, and viewpoints can be shared with common understanding.