Print Friendly, PDF & Email

DoDAF Training

DoDAF training covers the concepts, background, requirements, tools, and techniques of DoDAF. Students will learn how to apply and implement DoDAF through practical exercises, labs, and hands-on activities.

6G for DoD

What is DoDAF?

DoDAF is the Department of Defense Architecture Framework for integrated architecture. DoDAF was initiated to support many features of the DOD, and was planned apply even when just the components of the framework that relate to a certain purpose or project are executed. An integrated architecture that includes the elements of an organization, system, or enterprise operates as a standardized model that can be evaluated to demonstrate the connections between components in the real world.

The DoDAF is the Enterprise Architecture framework that the Department of Defense (DOD) uses for capability development and acquisition. Its origin goes back to C4ISR Architecture Framework, named as DoDAF 1.0, and even further back to Zachman’s more general work on the same topic. However, its governmental foundation comes from the Clinger-Cohen Act, with exclusive guidance in the US Office of Budget and Management Circular (OMB) A-130.

The main purpose of using DoDAF and other similar integrated architecture frameworks is rigorous and consistent linkage of complex information.

DoDAF includes three versions being developed over time:

  • DoDAF version 1.0
    • A system of four “views” or classes of architecture data presentation products from the C4ISR Architecture Framework, along with the Core Architecture Data Model (CADM)
  • DoDAF version 1.5
    • Offered modifications designed to emphasize on the decoupling of technology, such as the use of services, and a simplification of the data model
  • DoDAF version 2.0
    • Provided supplemental reductions in clarifying requirements with a focus on a data-centric method and minimalist rendering of the data on views. It also got rid of the CADM against the DODAF Conceptual Data Model (CDM), which accomplishes integration through the specification of physical data transfer instead of specifying a data model planned to be used as a common repository

DoDAF Components

  • All Viewpoint (required) (AV)
  • Capability Viewpoint (CV)
  • Data and Information Viewpoint (DIV)
  • Operation Viewpoint (OV)
  • Project Viewpoint (PV)
  • Services Viewpoint (SvcV)
  • Standards Viewpoint (STDV)
  • Systems Viewpoint (SV)
  • Models

DoDAF Viewpoints and Models

DoDAF is invented to provide the exclusive business and operational demands of the DoD. It demonstrates an enterprise architecture that allows stakeholders to concentrate on details in the enterprise, whereas keeping the big picture in mind. To help managers make effective decisions, DoDAF offers the tolls of summarizing vital information from the fundamental complexity and demonstrating it in coherent and consistent way.

Each viewpoint has a specific purpose, and normally covers one or combinations of the following:

  • Extensive overview of information about the entire enterprise
  • Carefully concentrated information for a particular purpose
  • Information about how features of the enterprise are linked

DoDAF classifies the DoDAF‐described models into the following viewpoints:

  • The All Viewpoint explains the main features of architecture context that associates with all viewpoints.
  • The Capability Viewpoint discusses the capability requirements, the delivery timing, and the deployed capability.
  • The Data and Information Viewpoint discusses the data relationships and alignment structures in the content of architecture for the ability and functional criteria, system engineering procedures, and systems and services.
  • The Operational Viewpoint contains the operational situations, activities, and requirements that help capabilities.
  • The Project Viewpoint explains how operational and capability requirements are related.
  • The Project Viewpoint also outlines in details all dependencies between capability and operational requirements, system engineering processes, systems design, and services design inside the Defense Acquisition System process.
  • The Services Viewpoint is the design for resolutions that discuss the performers, activities, services, and their exchanges, by offering operational and capability functions.
  • The Standards Viewpoint expresses the valid functional, business, technical, and industry strategies, standards, guidance, constraints, and forecasts that use to capability and operational requirements, system engineering processes, and systems and services.
  • The Systems Viewpoint is the design for solutions articulating the systems, their configuration, interconnectivity, and context offering for or supporting operational and capability functions.

Capability-Based Approach

  • Push “jointness” from the top-down, strengthening joint war-fighting abilities
  • Connects strategic guidelines to strategic investment decision making and acquisition strategy
  • Allows a more receptive acquisition system
  • Incorporates materiel and non-materiel solutions to capability gaps and shortages
  • Shapes discussions of options using common language of metrics
  • Offers an engine for force transformation

Capability-Based Analysis

  • A capability is described by Operational Activity Model + DOTMLPF Attributes + Operational Activity Sequence and Timing Descriptions
  • New SV-5 Matrix relates Operational Activities to System Functions, Operational Activities (in an operational thread) to Capabilities, and Capabilities to Systems

Benefits of Architecture Meta-Data Standardization

  • Reusing data
  • Reliability that enables integration
  • Flexibility in dividing data from different points of view
  • Capability to apply automatic architecture and modeling methods interchangeably
  • Greater support for analysis and decision-making

DoDAF Development Process

  • Determine intended use of architecture
  • Determine scope of architecture
  • Determine data required to support architecture development
  • Collect, organize, correlate, & store architectural data
  • Conduct analyses in support of architecture objectives
  • Document results in accordance with decision-maker needs

Learn About

  • SE definition
  • SE terminology
  • SE goals and applications
  • System architecture
  • System model, Modeling, and Simulation,
  • Optimization
  • System dynamics
  • Systems analysis and design
  • System requirements engineering
  • Decision making
  • Architectural features
  • Viewpoints of DoDAF 2
  • How to create views
  • “Fit-for-Purpose” views
  • DoDAF v1.5 products migration to DoDAF 2.02
  • DoDAF System View (SV) and Services Viewpoints (SvcV)
  • DoDAF Version 2.02 viewpoint
  • Principles applied to complete, executable architectures
  • V-Diagram

For more details click HERE


  • System engineers
  • System architects
  • Software engineers
  • Software architects
  • Enterprise architects
  • Executives and leaders
  • Managers
  • CIO’s managers
  • Senior IT managers
  • IT engineers
  • Data scientists
  • Business and systems analysts
  • Senior analysts
  • Project managers
  • Vendors and developers

DoDAF Training

Request More Information

  • Please complete the following form and a Tonex Training Specialist will contact you as soon as is possible.

    * Indicates required fields

  • This field is for validation purposes and should be left unchanged.