DoD Architecture Framework v2.0
Information Enterprise Architecture v1.1
Walt Okon
Senior Architect Engineer
Director, Enterprise Architecture & Standards
Office of the DoD Deputy Chief Information Officer
(703) 607-0502
walt.okon@osd.mil
Enterprise Architecture Conference June 19, 2009
1
DoD Architecture Framework
DoDAF V2.0
What are we delivering?
2
DoDAF V2.0
What are we delivering?
Volume 1 – Manager’s Guide
– Guidance for Development, Use, and
Management of Architectures
Volume 2 – Architect’s Guide
– Describes construction of
Architectures, the DODAF Metamodel, Data Exchange Requirements,
and Development of the Architectural
Models in technical detail
Volume 3 – Developer’s Guide
– Introduces the DoDAF Meta-Model
Physical Exchange Specification
3
DoDAF V2.0
What are we delivering?
DoDAF Journal
(https://www.us.army.mil/suite/page/454707)
– On-line interface providing examples,
description of best practices, lessons
learned, and reference documents
supplementing the information in the
three volumes
Meta-Model Data Dictionary (Zip File)
– https://www.us.army.mil/suite/folder/17204298
Physical Exchange Specification XSDs
(Zip file)
– https://www.us.army.mil/suite/folder/17204298
4
DoDAF V2.0 Focus
Focus:
architecture DATA,
not Products
Results: Better
ANALYSIS and
Decisions.
DoDAF V2.0 provides an overarching set of architecture concepts,
guidance, best practices, and methods to enable and facilitate architecture
5
development.
Architecture Models + Data =
Architectural Description
Operational
Model
Example
Things
Individuals
Types or classes
of individuals or
things
Architecture
Architecture
Data + Metadata
Models
Fit-for-Purpose (FFP)
Architectural
Description
Fit-for-Purpose describes an architecture that is appropriately focused and
directly support customer needs or improve the overall process undergoing
change. The models provide choices, based upon the decision-maker needs.
6
Key Concepts
DoDAF is prescribed for the use and development of
Architectural Descriptions in the Department.
– Specific DoDAF-described Models for a particular purpose are
prescribed by process-owners.
– All the DoDAF-described Models do not have to be created.
DoDAF V2.0 is “Fit-for-Purpose”, based on the decision-maker
needs.
DoDAF V2.0 is data-centric and has shifted from the DoDAF
V1.5 focus on Products, consistent with the NCDS.
DoDAF V2.0 prescribes a discipline for Architecture
Development to determine the purpose and scope of the
architecture before the data and Viewpoints are selected.
Node has been decomposed into more concrete concepts.
Examples will appear in the DoDAF Journal.
7
Select the Viewpoints That Fit-thePurpose
Articulate operational scenarios,
processes, activities & requirements
Services Viewpoint
Articulate the performers, activities,
services, and their exchanges providing
for, or supporting, DoD functions
Systems Viewpoint
Articulate the legacy systems or
independent systems, their composition,
interconnectivity, and context providing for,
or supporting, DoD functions
Project Viewpoint
Operational Viewpoint
Describes the relationships between operational and capability
requirements and the various projects being implemented;
Details dependencies between capability management and the
Defense Acquisition System process.
Articulate the capability requirement,
delivery timing, and deployed capability
Standards Viewpoint
Articulate applicable Operational, Business, Technical, and
Industry policy, standards, guidance, constraints, and
forecasts
Data and Information Viewpoint
Articulate the data relationships and alignment structures in
the architecture content
All Viewpoint
Overarching aspects of architecture context that relate to all
models
Capability Viewpoint
Architecture viewpoints are composed of data that has been organized to
facilitate understanding.
8
DoDAF V2.0 Promulgation Memo
Version 2.0 is the prescribed framework
for all Department architectures and
represents a substantial shift in approach.
– Don’t redo current architecture
Architectures shall comply with Version
2.0 in their next major release.
– Update only in the next release
9
DoDAF V2.0 Conformance
The data in an architectural description is defined
according to the DoDAF Meta-model (DM2)
concepts, associations, and attributes.
– The information captured in an architecture
tool is consistent with the DM2 concepts,
association, and attributes.
– Architectural data should be stored in a
recognized commercial architecture tool that
conforms to industry standards. Powerpoint,
Visio, Excel, etc. can be used for the
PRESENTATION of architectural data, but it
must be based on DATA.
10
DoDAF V2.0 Conformance
The architecture data is capable of transfer in
accordance with the Physical Exchange
Specification (PES)
– Architectures that will exchange information
need to comply with DM2 PES (for the
appropriate architectural data)
11
DoDAF V2.0 Summary
DoDAF V2.0 provides an overarching set of
architecture concepts, guidance, best
practices, and methods to enable and
facilitate architecture development.
It is all about the decision-makers and the
data!
Fit-for-Purpose describes an architecture
that is appropriately focused and directly
support customer needs or improve the
overall process undergoing change. The
models provide choices, based upon the
decision-maker needs.
12
DoDAF V2.0 Summary
Adoption of DoDAF V2.0 benefits the
decision-maker and the architect with
the freedom of presenting the
architectural data in the terms for the
decision-makers.
DoDAF V2.0 is available at:
https://www.us.army.mil/suite/page/454707
13
Defense Information Enterprise
Architecture
(DIEA), V1.0
to
DoD IEA, Version 1.1
14
Background
Defense Information Enterprise Architecture (DIEA),
V1.0
Department-wide effort; Approved 11 April 2008
Purpose:
Unifies the concepts embedded in the DoD’s
net-centric strategies into common vision
Describes the integrated Defense Information
Enterprise and the rules for information
assets and resources that enable it
Fosters alignment of DoD architectures with
the enterprise net-centric vision
Recognized more work to be done
DoD CIO decision to merge NCOW Reference Model
with DIEA, V1.0
15
Background
The Immediate Task:
– DIEA, V1.0 evolution (page 27)
Merge related enterprise architecture guidance
(NCOW Reference Model)
Develop DIEA compliance guideline document using
NCOW RM compliance documentation
DoD IEA, Version 1.1
– DIEA, V 1.0
– Appendix D: Applying the DoD IEA
– Appendix E: Compliance with the DoD IEA
– Appendix F: Integrated View
– Integration of NCOW RM content
– Focused upon amplification of “Using and Applying
Principles and Business Rules” - customer set
identified in V1.0: It architects, PEOs and PMs, IRBs,
CPMs, CIOs (DIEA, v1.0, page 4/7)
Department-wide review and comment: EA Summit
Version 1.1 approved 27 May 2009
16
DoD IEA v1.1
- DoD IEA, V1.0 (original document with minor
editorial changes)
- Appendix D: Applying the DoD IEA
- Appendix E: Compliance with the DoD IEA
- Appendix F: Mapping of NCOW RM to the
DoD IEA
17
Way Ahead: DoD IEA v2.0
Refine existing products (Principles, Rules, Activities)
– Develop additional operational views – “particularly
process models”
– Embed DoD IEA in decision-making and investment
processes
– Further merge related net-centric information guidance
(NCOW RM, Net-Centric Checklist) into DoD IEA
– Evolve compliance guidelines
– Continue to align DoD IEA and other key DoD direction/
guidance/standards (JCSFL, “Blue Sheets,” GIG 2.0, GTG
) to support portfolio and program decision-making
– Institutionalize DoD IEA in architecture development and
maintenance and in support of CPM and PM compliance
with net-centric requirements
18
Way Ahead:
Enterprise Reference Architecture Cell
(ERAC)
Components have expressed the need for more detailed guidance
– Enterprise patterns and processes
– Army CIO/G-6 Comment on DoD IEA v1.1: “…establish a separate
DoD IEA Reference Architecture with sufficient granularity to
enable interoperability across the DOD IE/GIG. To foster such
interoperability, these reference architectures would need to
include processes, process patterns and service patterns, as well
as service interfaces and metrics.”
Purpose:
– Develop reference architecture artifacts
– Assist IT Decision Makers/Components/Programs/Solution
Architects as directed
Assist in the proper application of the DoD IEA, DoDAF and DARS
– Conduct architecture assessments as directed
Assess architecture compliance w/DoD IEA
Event Driven - Net Centric Reviews (ED-NCR)
JCIDS/DAS Milestone Reviews
19
http://www.defenselink.mil/cio-nii/sites/diea/
20
DoD Architecture Framework v2.0
Information Enterprise Architecture v1.1
Walt Okon
Senior Architect Engineer
Director, Enterprise Architecture & Standards
Office of the DoD Deputy Chief Information Officer
(703) 607-0502
walt.okon@osd.mil
21