Download Interent ExplorerDownload Apple SafariDownload OperaDownload FirefoxDownload Google Chrome

DoDAF 2.0 Training – Hands-on Project Based DoDAF Training

DoDAF 2.0 Training – Hands-on Project Based DoDAF Training

DoDAF 2.0 Training – Hands-on Project-Based DoDAF Training:

DoDAF 2.0 Training Course – Hands-on

DoDAF 2.0 Training, DoD Architecture Framework Version 2.0, advanced course and workshop focuses on creating and building DoDAF 2.0 viewpoints based on a selected project. DoDAF 2.0 Training also focuses on teaching the students how to create and model architecture data. Through the selected projects, data will be collected, organized, and stored by a wide range of architecture tools developed by sources and organized using the DoDAF Meta-model (DM2). ENO Advanced DoDAF 2.0 training will help the students to create their own viewpoints based on a common denominator across their domain and boundaries. This is 100% hands-on and project-based.

DoDAF 2.0 Training Workshop

After extensively covering architecture development with DoDAF, the DoDAF Training will focus on DoDAF 2.0 viewpoints and models. After briefly introducing the attendees to each model, the students will master how to create viewpoints and views using a real project (Scenario based) through various roles such as operators, PM and EA.

DoDAF’s six-step process is recommended as best practice by the enterprise architecture team. There are collaborative efforts were undertaken between:

  • Program Management Team
  • Enterprise Architecture Team
  • Operational Team
  • System and Engineering Team
  • Compliance Team

Using DoDAF Six-Step Development Process, the attendees will create DoDAF 2.0 Viewpoints.

DoDAF Six-Step Development Process

  • Determine Intended Use of architecture
  • Determine the Scope of architecture
  • Determine Data Required to support architecture development
  • Collect, Organize, Correlate, & Store architectural data
  • Conduct Analyses in support of architectural objectives
  • Document Results in accordance with decision-maker needs

The purpose of DoDAF is to define concepts and models usable in DoD’s six core processes:

  • Capabilities Integration and Development (JCIDS)
  • Planning, Programming, Budgeting, and Execution (PPBE)
  • Acquisition System (DAS)
  • Systems Engineering (SE)
  • Operations Planning
  • Capabilities Portfolio Management (CPM)

DoDAF 2.0 Viewpoints

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

Working with DoDAF Meta-Model (DM2)

The DM2 defines architectural data elements and enables the integration and federation of Architectural Descriptions. It establishes a basis for semantic (i.e., understanding) consistency within and across Architectural Descriptions. In this manner, the DM2 supports the exchange and reuse of architectural information among JCAs, Components, and Federal and Coalition partners, thus facilitating the understanding and implementation of interoperability of processes and systems.

  • What should be modeled?
  • What degree of detail?
  • What is your purpose?

Multiple model types allow data modelers or data analysts to work with the models best suited for their needs. The following model types are defined in DoDAf 2.0:

  • The Conceptual Data Model (CDM)
  • The Logical Data Model (LDM) a
  • The Physical Exchange Specification (PES)

Why use DoDAF Meta-Model (DM2)

  • To establish and define the constrained vocabulary for description and discourse about DoDAF models (formerly “products”) and their usage in the 6 core processes
  • To specify the semantics and format for federated EA data exchange between architecture development and analysis tools and architecture databases across the DoD Enterprise Architecture (EA) Community of Interest (COI) and with other authoritative data sources
  • To provide a basis for semantic precision in architectural descriptions to support heterogeneous architectural description integration and analysis in support of core process decision making.

DoDAF 2.0 Defined by Chief Information Officer, U.S. Department of Defense

DoDAF 2.0 by DoDAF organizes the DoDAF-described Models into the following viewpoints:

  • The All Viewpoint describes the overarching aspects of architecture context that relate to all viewpoints.
  • The articulates the capability requirements, the delivery timing, and the deployed capability.
  • The Data and Information Viewpoint articulates the data relationships and alignment structures in the architecture content for the capability and operational requirements, system engineering processes, and systems and services.
  • The Operational Viewpoint includes the operational scenarios, activities, and requirements that support capabilities.
  • TheProject Viewpoint describes the relationships between operational and capability requirements and the various projects being implemented. The Project Viewpoint also details dependencies among capability and operational requirements, system engineering processes, systems design, and services design within the Defense Acquisition System process. An example is the Vcharts in Chapter 4 of the Defense Acquisition Guide.
  • The Services Viewpoint is the design for solutions articulating the Performers, Activities, Services, and their Exchanges, providing for or supporting operational and capability functions.
  • The Standards Viewpoint articulates the applicable operational, business, technical, and industry policies, standards, guidance, constraints, and forecasts that apply to capability and operational requirements, system engineering processes, and systems and services.
  • The Systems Viewpoint, for Legacy support, is the design for solutions articulating the systems, their composition, interconnectivity, and context providing for or supporting operational and capability functions.

What’s Included?

  • 3 days of DoDAF Training with an expert instructor
  • DoDAF Training Electronic Course Guide
  • Certificate of Completion
  • 100% Satisfaction Guarantee


Related Courses4

Customize It:

  • If you are familiar with some aspects of the DoDAF 2.0 Training – Hands-on Project-Based DoDAF Training course, we can omit or shorten their discussion.
  • We can adjust the emphasis placed on the various topics or build the DoDAF 2.0 Training – Hands-on Project-Based DoDAF Training course around the mix of technologies of interest to you (including technologies other than those included in this outline).
  • If your background is nontechnical, we can exclude the more technical topics, include the topics that may be of special interest to you (e.g., as a manager or policy-maker), and present the DoDAF 2.0 Training – Hands-on Project-Based DoDAF Training course in manner understandable to lay audiences.

Audience / Target Group:

The target audience for this DoDAF 2.0 Training – Hands-on Project-Based DoDAF Training course is defined here:

  • DoDAF Program Management Team Members
  • DoDAF Enterprise Architecture Team Members
  • DoDAF Operational Team Members
  • DoDAF System and Engineering Team Members
  • DoDAF Compliance Team Members


Upon completing this DoDAF 2.0 Training course, learners will be able to meet these objectives:

  • Create DoDAF Version 2.0 Architecture Data and Viewpoints
  • Understand DoDAF Version 2.0 Meta-model Physical Exchange Specification
  • Work with advanced DoDAF 2.0 concepts

Course Syllabus:

Architecture Development with DoDAF 2.0

  • 6-Step Architecture Development Process
  • Learning Architecture Development 6-Step Process
  • Determine Intended Use of Architecture
  • Determine Scope of Architecture
  • Determine Data Required to Support Architecture Development
  • Collect, Organize, Correlate, and Store Architectural Data
  • Conduct Analyses in Support of Architecture Objectives
  • Document Results in Accordance with Decision-Maker Needs
  • DoDAF 2.0 Development Organizational Structure
  • DoDAF 2.0 Planned Approach

DoDAF 2.0 Applied

  • DoDAF 2.0 applied to Joint Capability Areas (JCAs)
  • Modeling net-centric/GIG viewpoints for your operations
  • Applying DODAF 2.0 to SoS
  • DoDAF and SOA /GIG alignment and implementation
  • Apply DoDAF 2.0 Viewpoints to CPIC, JCIDs, DISR, JITC, and ISA
  • Looking at databases implementing:
  • Automatic Storage Management (ASM)
  • UML Profile for DoDAF/Ministry of Defense Architecture Framework (MODAF) (UPDM)
  • Integrated Database and Extended Analysis System (IDEAS)
  • Joint Command and Control (JC2) Architecture and Capability
  • Assessment Enterprise (JACAE)
  • Joint Forces Command (JFCOM)
  • Current Research Information System (CRIS)
  • Transportation Command (USTC)
  • Basic Audit and Reporting Tool (BART)
  • Business Transformation Agency (BTA)’s BEA
  • Goal Oriented Business Model
  • Architecture and Standards Review Group (ASRG)
  • IDEAS Group
  • DARS
  • DoD MDR

Defining, Creating and Building DODAF 2.0 VIEWPOINTS – Project based

  • Defining your Project
  • Defining Selected Viewpoints
    • All Viewpoint
    • Capability Viewpoint.
    • Data and Information View
    • Operational Viewpoint
    • Project Viewpoint
    • Services Viewpoint
    • Standards Viewpoint
    • Systems Model Viewpoint

Creating DoDAF Meta-model Groups Support of Viewpoints

  • Working with Meta-Model Data Groups`
  • Performers
  • Resource Flows
  • Information and Data
  • Activities
  • Training / Skill / Education
  • Capability
  • Services
  • Project
  • Goals
  • Rules
  • Measures
  • Locations

DoDAF 2.0 Viewpoints– Building the DoDAF 2.0 Viewpoints and Specification

  • Overview of the Problem Domain
  • Mapping the requirements to DoDAF 2.0 Viewpoints
  • Working with Viewpoints
  • Creating and Refining DoDAF 2.0 Viewpoints
  • Understanding and working with Business Processes
  • TONEX’s Process for Developing all the Necessary Viewpoints
  • Structure for a Specific Stakeholder Concern through Viewpoints Organized by Various Views
  • Process to Identify and Interview the stakeholders
  • Techniques to Understand the Needs and Concerns of Stakeholders
  • Map Stakeholder’s Need and Requirements to Selected DoDAF 2.0 Viewpoints
  • AV-1 Overview and Summary Information av1
  • AV-2 Integrated Dictionary av2
  • CV-1 Vision CV1
  • CV-2 Capability Taxonomy CV2
  • CV-3 Capability Phasing CV3
  • CV-4 Capability Dependencies CV4
  • CV-5 Capability to organizational Development Mapping CV5
  • CV-6 Capability to Operational Activities Mapping CV6
  • CV-7 Capability to Services Mapping CV7
  • DIV-1 Conceptual Data Model DIV1
  • DIV-2 Logical Data Model DIV2
  • DIV-3 Physical Data Model DIV3
  • OV-2 Operational Connectivity Description ov2
  • OV-3 Operational Information Exchange Matrix ov3
  • OV-4 Organizational Relationships Chart ov4
  • OV-5 Operational Activity Model ov5
  • OV-6a Operational Rules Model ov6a
  • OV-6b State Transition Description ov6b
  • OV-6c Event-Trace Description ov6c
  • PV-1 Project Portfolio Relationships PV1
  • PV-2 Project Timelines PV2
  • PV-3 Project to Capability Mapping PV3
  • StdV-1 Standards Profile StdV1
  • StdV-2 Standards Forecast StdV2
  • SvcV-1 Services Interface Description SvcV1
  • SvcV-2 Services Communication Description SvcV2
  • SvcV-3a, Systems-Services Matrix SvcV3
  • SvcV-3b, Services-Services Matrix SvcV3
  • SvcV-4 Services Functionality Description SvcV4
  • SvcV-5 Operational Activity to Services Traceability Matrix SvcV5
  • SvcV-6 Services Data Exchange Matrix SvcV6
  • SvcV-7 Services performance parameters Matrix SvcV7SvcV-8 Services Evolution Description SvcV8
  • SvcV-9 Services Technology Forecast SvcV9
  • SvcV-10a, Services Rules Model SvcV10a
  • SvcV-10b, Services State Transition Description SvcV10b
  • SvcV-10c, Services Event-Trace Description SvcV10c
  • SV-1 Systems Interface Description SV1
  • SV-2 Systems Communications Description SV2
  • SV-3 Systems-Systems matrix SV3
  • SV-4 Systems Functionality Description SV4
  • SV-5a Operational Activity to Systems Function Traceability Matrix
  • SV5.xsd, SV-5b Operational Activity to Systems traceability Matrix SV5
  • SV-6 Systems Data Exchange Matrix SV6
  • SV-7 Systems Performance Parameters Matrix SV7
  • SV-8 Systems Evolution Description SV8
  • SV-9 Systems Technology Forecast SV9
  • SV-10a Systems Rules Model SV10a
  • SV-10b Systems State Transition Description SV10b
  • SV-10c Systems Event-Trace Description SV10c

Creating Viewpoints for Specific Project

  • All Viewpoint (AV)
    • AV-1
    • AV-2
  • Capability Viewpoint (CV)
    • CV-1
    • CV-2
    • CV-3
    • CV-4
    • Cv-5
    • CV-6
    • CV-7
  • Operational Viewpoint (OV)
    • OV-1
    • OV-2
    • OV-3
    • OV-4
    • OV-5
    • OV-6a/6b/6c
  • Services Viewpoint (SvcV)
    • SvcV-1
    • SvcV-2
    • SvcV-3a
    • SvcV-4
    • SvcV-5
    • SvcV-6
  • Standard Viewpoint (StdV)
    • StdV-1
    • Stdv-2
  • Systems Viewpoint (SV)
    • SV-1
    • SV-2
    • SV-3
    • SV-4
    • SV-5
    • SV-6
    • SV-7
  • Data and Information Viewpoint (DIV)
    • DIV-1
    • DIV-2
    • DIV-3

UML and DoDAF 2.0 Integration Workshop

  • Elements of UML
  • Building blocks
  • Architectural views: use case, design, implementation, process and deployment
  • Levels of detail: visualization, specification and construction
  • Modeling the Structure of a System
  • Specifying classes
  • Use Case diagrams
  • Class diagrams
  • Sequence diagrams
  • Requirements and Analysis
  • UML 2 and DoDAF 2.0
  • The Unified Profile for DoDAF/MODAF (UPDM)
  • UML Profile for DoDAF
  • Working with DoDAF 2.0 View Products using Class, Activity and
  • Sequence diagrams
  • Building a Weapon system using DoDAF 2.0 Viewpoints
  • Working with Joint Interoperability Test Command (JITC) Projects

Applying DoDAF 2.0 and UML to your Project

  • Defense Agencies Initiative (DAI)
  • Global Command and Control System-Joint (GCCS-J)
  • Global Transportation Network 21 (GTN 21)
  • Joint Distributed Test Network Operations Center (JNOC)
  • Joint Explosive Ordinance Disposal Decision Support System (JEOD-DSS)
  • Net-Centric Enterprise Services (NCES)

Building DoDAF Meta Model (DM2)

  • Define concepts and models usable in DoD’s six core processes
  • Capabilities Integration and Development (JCIDS)
  • Planning, Programming, Budgeting, and Execution (PPBE)
  • Acquisition System (DAS)
  • Systems Engineering (SE)
  • Operations Planning
  • Capabilities Portfolio Management (CPM)

Architecture Development- Addressing Security in DoDAF 2.0

  • Addressing Security Issues in DoDAF
  • Conformant Architecture Development
  • Security as a critical concern within the DoD
  • Physical, procedural, communications security (COMSEC)
  • Transient Electromagnetic Pulse Emanation Standard (TEMPEST)
  • Information Security (INFOSEC)
  • DM2 and the Intelligence Community Information Security Marking (IC ISM) standard
  • How Does DoDAF Represent Security?
  • Mapping Capabilities to a variety of threats to the integrity, availability, and confidentiality of their operation
  • Physical
  • Communication Security (COMSEC)
  • Transient Electromagnetic Pulse Emanation Standard (TEMPEST)
  • DoDAF Viewpoints and Concept Mapped to Security Characteristics and Protective Measures


Dr. Eric Honour, CSEP, INCOSE Fellow, has been in international leadership of the engineering of systems for nearly two decades, part of a 40-year career of complex systems development and operation. His energetic and informative presentation style actively involves class participants. He is a former President of the International Council on Systems Engineering (INCOSE). He was selected in 2000 for Who’s Who in Science and Technology and in 2004 as an INCOSE Founder. He has been a systems engineer, engineering manager, and program manager at Harris, E-Systems, and Link, and was a Navy pilot. He has contributed to the development of 17 major systems, including Air Combat Maneuvering Instrumentation, Battle Group Passive Horizon Extension System, and National Crime Information Center. BSSE (Systems Engineering) from US Naval Academy and MSEE from Naval Postgraduate School, PhD University of South Australia based on his ground-breaking work into the quantified value of systems engineering

Whether you are looking for general information or have a specific question, we want to help!

Request More Information

    Time frame: