DoDAF Overview – What You Need to Know

This section provides an overview of DoDAF (DoD Architecture Framework), the industry-standard Enterprise Architecture Framework for defense and aerospace applications. DoDAF defines how to organize the specification of enterprise architectures for U.S. Department of Defense (DoD) applications. Please contact us about additions and corrections.

Overview

DoD Architecture Framework (DoDAF)
Description:
The DoD Architecture Framework (DoDAF) is the industry-standard Enterprise Architecture Framework for defense and aerospace applications. DoDAF defines how to organize the specification of enterprise architectures for U.S. Department of Defense (DoD) applications. All major DoD weapons and information technology system procurements are required to document their enterprise architectures using the view products prescribed by the DoDAF. DoDAF is well suited to large systems and systems-of-systems (SoSs) with complex integration and interoperability issues. Although DoDAF is primarily focused on defense applications, it can also be applied to commercial systems.
Framework Classification:
Model-Based Enterprise Architecture Framework/
Compatible with multiple Architecture Description Languages

General purpose?
Open standard?
Rigorous semantics?
Well-defined Views/Viewpoints?
Integrated Method?
Certifiable compliance?

Views/Viewpoints

  • Terminology Compatibility: Current version (v. 2.0) compatible with ISO/IEC 42010 Viewpoints; previous versions compatible with ANSI/IEEE 1471-2000 Views.
  • Viewpoints Specified: All; Capability; Data and Information; Operational; Project; Services; Standards; and Systems.
  • ADL Compatibility: UML, SysML, IDEF, etc.; Mixed-language usage appears encouraged by examples

Usage:
  • Primary Users: Defense industry, Aerospace industry, ...
  • Other Users: N/A
Estimated Number of Users: N/A
Size/Complexity:
  • Size = Large (5 Viewpoints and 42 work products)
  • Complexity = High (substantial Viewpoint and work product variation and semantic overlap)
  • Semantic integrity mappings across Viewpoints and work products is poorly specified, and largely ignored by modeling tool implementers.
Variations:
  • MODAF (UK Ministry of Defense Architecture Framework), DNDAF (Canadian Department of National Defence Architecture Framework), NAF (NATO Architecture Framework), ...
Origin/Derivation:
DoDAF evolved from the USA DoD C4ISR Architecture Framework 1.0 and 2.0 specifications, which were specified by the USA DoD during the late 1990s. DoDAF 1.0 was published in 2003, followed by DoDAF 1.5 in 2007, and DoDAF 2.0 in 2009.
Framework Design Style:
Compliance/Conformance/
  • Design-by-Committee anti-pattern manifested in DoDAF 1.0 became progressively worse in the DoDAF 1.5 minor revision and the DoDAF 2.0 major revision. The Enterprise Architecture Framework is bloated with gratuitous work products, ambiguities, and inconsistencies.
  • Editor Design Ratings: DoDAF 1.0: C+; DoDAF 1.5: C; DoDAF 2.0: C-

Standardization

DoD Architecture Framework (DoDAF)
Current Maintainer:
U.S. Department of Defense (since 2003)
Current Version:
Specification Rigor/Style:
Level of Rigor: Informal
  • Views/Viewpoints: Informally specified via a combination of natural language and examples.
  • Work Products: Informally specified via a combination of natural language and examples.
  • Semantic integrity rules: Inadequate and ambiguous.
  • Metamodel: Research ontology.
  • Formal lexicon: Sparse and poorly defined.

Editor Specification Rating: C-
Compliance/Conformance/ Certification:
  • Compliance/Conformance: DoD states that "DoDAF conformance" is achieved when architecture data conforms with DM2 metamodel constructs, and be interchanged via the Physical Exchange Specification (PES). Standards conformance may be claimed by tool vendors; no compliance test suites are available.
  • Tool Certification: N/A
  • User Certification: N/A