1. Understanding the DoD Architecture Framework Products
Mason Myers
DoD Architecture Framework
Overview
October 27, 2004

2. Federal Policy/Guidance on Architectures DoD Architecture Framework
Information Technology Management Reform Act (1996) mandates that Chief Information Officers of Executive Agencies are responsible for “developing, maintaining, and facilitating implementation of sound and integrated information technology architecture for the executive agency”
OMB Circular A-130 defines Enterprise Architecture as “the explicit description and documentation of the current and desired relationships among business and management processes and information technology”
DoD Architecture Framework
Overview
October 27, 2004

3. DoD Policy on Using Architectures
DoDD , Management of DoD Information Resources and Information Technology
DoDD , Global Information Grid Overarching Policy
DoDD , The Defense Acquisition System, (12May2003)
DoDI , Operation of the Defense Acquisition System, (12May2003)
CJCSI C, Joint Capabilities Integration and Development System
CJCSI C, Interoperability and Supportability of National Security Systems and Information Technology Systems
DoDD , Interoperability and Supportability of Information and National Security Systems
DoDI , Procedures for Interoperability and Supportability of Information Technology and National Security Systems
Recent DoD policy highlights use of architectures for:
Understanding the DoD as an enterprise
Identification of operational requirements
Rationalization of IT investment decisions
Improvements to interoperability among various systems
DoD Architecture Framework
Overview
October 27, 2004

4. DoD Architecture Framework
DoDD and .2 Oversight & Review ACAT ID/IAM Programs*
Defense Acquisition
Executive
Chief Information
Officer
Defense Acquisition
Board
IT Acquisition
Board
Weapon Systems
C3ISR Systems
Major AIS
Overarching
Integrated Product
Teams (OIPT)
C3I Overarching
Integrated Product
Team (OIPT)
*Note: Space Programs have been delegated to the Air Force and most missile defense programs to the Missile Defense Agency
DoD Architecture Framework
Overview
October 27, 2004

5. Architecture Definition
Architecture “The structure of components, their relationships, and the principles and guidelines governing their design and evolution over time.” DoD Integrated Architecture Panel, 1995, based on IEEE STD “An architecture is the fundamental organization of a system embodied in its components, their relationships to each other, and to the environment, and the principles guiding its design and evolution.” IEEE STD
Architecture =
Structure of Components
Relationships
Principles & Guidelines + +
DoD Architecture Framework
Overview
October 27, 2004

6. DoD Architecture Framework (DoDAF) Purpose DoD Architecture Framework
An architecture framework is a tool
It should describe a method for designing an information system in terms of a set of building blocks and for showing how the building blocks fit together.
It should contain a set of tools and provide a common vocabulary.
It should also include a list of recommended standards and compliant products that can be used to implement the building blocks.
DoD Architecture Framework
Overview
October 27, 2004

7. History of DoD Architecture Framework
DoD Architecture Framework Version 2.0
2003
C4ISR Architecture Framework Version 2.0
Architecture Framework Working Group
DoD Architecture Coordination Council
C4ISR Architecture Working Group
Dec 1997
C4ISR Architecture Framework Version 1.0
C4ISR ITF Integrated Architectures Panel
Prior Community Experiences
June 1996
DoD Architecture Framework
Overview
October 27, 2004

8. DoD Architecture Framework DoD Architecture Framework
DoDAF provides guidance on describing architectures in order to standardize this method of description
Standardized architecture description approaches improve possibilities for architecture consistency and reuse
An architecture description is a representation of:
a current or future point in time,
a defined “domain” in terms of its component parts,
what those parts do,
how the parts relate to each other, and
the rules and constraints under which the parts function
DoD Architecture Framework
Overview
October 27, 2004

9. DoD Architecture Framework DoD Architecture Framework
DoD Architecture Framework is partitioned into two volumes and a deskbook
Volume I provides definitions, guidelines, and related background material
Volume II contains descriptions and examples/templates for each of the 26 products
The Deskbook provides supplementary information to Framework users
All three available on Internet at
DoD Architecture Framework
Overview
October 27, 2004

10. DoD Architecture Framework DoD Architecture Framework
DoDAF supports development of interoperating and interacting architectures
DoDAF defines three related views of an architecture and products describing each of these views
Operational View
Systems View
Technical Standards View
DoD Architecture Framework
Overview
October 27, 2004

11. DoDAF Operational View DoD Architecture Framework
Operational View (OV) is description of tasks and activities, operational elements, and information exchanges required to accomplish DoD missions
OV contains graphical and textual products that comprise an identification of the operational nodes and elements, assigned tasks and activities, and information flows required between nodes
OV defines types of information exchanged, frequency of exchange, which tasks and activities are supported by the information exchanges, and nature of information exchanges
DoD Architecture Framework
Overview
October 27, 2004

12. DoD Architecture Framework
DoDAF Systems View
Systems View (SV) is set of graphical and textual products that describes systems and interconnections providing for, or supporting, DoD functions
SV associates systems resources to the Operational View
These system resources support operational activities and facilitate exchange of information among operational nodes
DoD Architecture Framework
Overview
October 27, 2004

13. DoD Architecture Framework
DoDAF Technical View
Technical View (TV) is minimal set of rules governing arrangement, interaction, and interdependence of system parts or elements
TV provides technical systems implementation guidelines upon which engineering specifications are based, common building blocks are established, and product lines are developed
TV includes collection of technical standards, implementation conventions, standards options, rules, and criteria organized into profiles that govern systems and systems elements for a given architecture
DoD Architecture Framework
Overview
October 27, 2004

14. Relationship Between DODAF Views
One Architecture, multiple views or perspectives
DoD Architecture Framework
Overview
October 27, 2004

15. DoDAF Products – All Views and Operational View
Applicable Architecture View
Product Reference
DoDAF Product
Essential or Supporting
All Views
AV-1
Overview and Summary Information
Essential
AV-2
Integrated Dictionary
Operational
OV-1
High-Level Operational Concept Graphic
OV-2
Operational Node Connectivity Description
OV-3
Operational Information Exchange Matrix
OV-4
Command Relationships Chart
Supporting
OV-5
Activity Model
OV-6a
Operational Rules Model
OV-6b
Operational State Transition Description
OV-6c
Operational Event/Trace Description
OV-7
Logical Data Model
DoD Architecture Framework
Overview
October 27, 2004

16. C4ISR Architecture Framework Example
In order to demonstrate examples of the contents of some of the DoD Architecture Framework products, assume that we will analyze the application domain for a Border and Coastline Surveillance System (BCSS) that should provide aerial coastline and border surveillance and reporting for the United States Border Patrol and Drug Enforcement Agency
DoD Architecture Framework
Overview
October 27, 2004

17. Overview and Summary Information Product (AV-1)
The Overview and Summary Information Product (AV-1) of the DoD Architecture Framework is used to document the Identification, Purpose, Scope, Intended Users, and Context of the system or system-of-systems that is being described.
DoD Architecture Framework
Overview
October 27, 2004

18. Overview and Summary Information Product (AV-1) for BCSS
Identification – The BCSS is to be developed for the Department of Homeland Security to meet the BCSS mission roles.
Purpose – The BCSS will employ autonomous, long-endurance drone aircraft to patrol both land and water border regions in order to detect unauthorized incursions and notify ground personnel.
Scope – The BCSS development project will develop, demonstrate, integrate, deliver, and maintain the air vehicle, ground station, mission planning, and logistics functionalities that comprise BCSS.
DoD Architecture Framework
Overview
October 27, 2004

19. Overview and Summary Information Product (AV-1) for BCSS
Intended Users – BCSS will be used by the U.S. Border Patrol and the Drug Enforcement Agency to monitor the borders and coastal waters to detect possible unauthorized incursions into the United States and to notify authorities to investigate these incursions.
Context – BCSS is to be a system that employs an autonomous, long-endurance drone aircraft capable of integration into civilian airspace and of sharing surveillance data with other aircraft as well as with its mission monitoring station.
DoD Architecture Framework
Overview
October 27, 2004

20. Integrated Dictionary Product (AV-2)
The Integrated Dictionary Product (AV-2) of the DoD Architecture Framework is to define terms used in the given architecture
AV-2 consists of textual descriptions in form of glossary, repository of architecture data, their taxonomies, and their metadata (data about architecture data)
AV-2 enables set of architecture products to stand alone, allowing them to be read and understood with minimal reference to outside resources
DoD Architecture Framework
Overview
October 27, 2004

21. High-Level Concept Graphic Product (OV-1)
The High-Level Concept Graphic Product (OV-1) of the DoD Architecture Framework is used to depict a high-level graphical description of the proposed system and its internal and external interdependencies.
OV-1 serves as a facilitating diagram for explaining the system elements and interfaces and for showing the system’s role as an element of the encompassing system-of-systems.
DoD Architecture Framework
Overview
October 27, 2004

22. High-Level Concept Graphic Product (OV-1) for BCSS
DoD Architecture Framework
Overview
October 27, 2004

23. Operational Node Connectivity Description Product (OV-2)
The Operational Node Connectivity Description Product (OV-2) of the DoD Architecture Framework is used to depict the operational nodes and elements of the architecture, the needlines between them, and the characteristics of the information exchanged.
OV-2 serves as a facilitating diagram for further defining the interfaces and information to be exchanged and for showing the system’s role as an element of the encompassing system-of-systems
OV-2 is frequently done at both the system-of-systems and system levels.
DoD Architecture Framework
Overview
October 27, 2004

24. DoD Architecture Framework
System-of-Systems Operational Node Connectivity Product (OV-2) for BCSS
DoD Architecture Framework
Overview
October 27, 2004

25. System-Level Operational Node Connectivity Product (OV-2) for BCSS
- Flight control
- Mission track
BCSS
- Surveillance
- Status reporting
Aircraft
BCSS Mission
Planning
Node
- A/C deconfliction
Route Planning
Mission Validation
Node
- Subsystems
- Control commands
diagnostics
- A/C status
- Diagnostic commands
- Contact reports
- Diagnostic status
Mission Plans
Mission Updates
- Mission updates
- Power-up/power-down
sequencing commands
- A/C monitoring
BCSS Ground
BCSS
- A/C maintenance
- Mission monitoring
- Ground station
Station
Support
- Contact reporting
maintenance
- Contingency handling
Node
Node
- Operator training
- A/C status
- Ground
station status
- Training scenario
- Control commands
commands
- A/C status
- Contact reports
- Mission updates
BCSS
Simulation
Node
- A/C simulation
DoD Architecture Framework
Overview
October 27, 2004

26. Operational Information Exchange Matrix (OV-3)
The Operational Information Exchange Matrix (OV-3) of the DoD Architecture Framework details information exchanges and identifies who exchanges what information, with whom, why the information is necessary, and how the information exchange must occur
OV-3 identifies information elements and relevant attributes of information exchange and associates the exchange to the producing and consuming operational nodes and activities and to the needline that the exchange satisfies
DoD Architecture Framework
Overview
October 27, 2004

27. Operational Information Exchange Matrix (OV-3)
OV-3 contains the information in the following categories for each Information Element:
Information Element Description
Producer and Consumer Identification
Nature of Transaction
Performance Attributes
Information Assurance
Security
DoD Architecture Framework
Overview
October 27, 2004

28. DoDAF Products – Systems View
Applicable Architecture View
Product Reference
DoDAF Product
Essential or Supporting
Systems
SV-1
System Interface Description
Essential
SV-2
Systems Communication Description
Supporting
SV-3
Systems2 Matrix
SV-4
Systems Functionality Description
SV-5
Operational Activity to System Function Traceability Matrix
SV-6
System Information Exchange Matrix
SV-7
System Performance Parameters Matrix
SV-8
System Evolution Description
SV-9
System Technology Forecast
SV-10a
System Rules Model
SV-10b
Systems State Transition Description
SV-10c
Systems Event/Trace Description
SV-11
Physical Data Model
DoD Architecture Framework
Overview
October 27, 2004

29. System Interface Description Product (SV-1)
The System Interface Description Product (SV-1) of the DoD Architecture Framework is used to depict the assignments of systems and their interfaces to the nodes and needlines identified in the OV-2 diagram
SV-1 serves to specify which interfaces correspond to which systems and contributes to the identification of other systems with which coordination must be established
SV-1 is frequently done at both the system-of-systems and system levels
DoD Architecture Framework
Overview
October 27, 2004

30. System-of-Systems Interface Description Product (SV-1) for BCSS
DoD Architecture Framework
Overview
October 27, 2004

31. System-Level Interface Description Product (SV-1) for BCSS
BCSS Mission
Planning
Node
Route Planning
Mission Validation
Mission Distribution
Files for mission plans and updates
DoD Architecture Framework
Overview
October 27, 2004

32. DoDAF Products – Technical Standards View
Applicable Architecture View
Product Reference
DoDAF Product
Essential or Supporting
Technical
TV-1
Technical Standards Profile
Essential
TV-2
Standards Technology Forecast
Supporting
DoD Architecture Framework
Overview
October 27, 2004

33. Technical Standards Profile (TV-1)
The Technical Standards Profile (TV-1) of the DoD Architecture Framework provides technical systems implementation standards upon which engineering specifications are based, common building block are established, and product lines are developed
TV-1 consists of set of systems standards rules that govern system implementation and operation of that architecture including what hardware and software may be implemented and what system data formats may be used
DoD Architecture Framework
Overview
October 27, 2004

34. Technical Standards Profile (TV-1) Template Example
DoD Architecture Framework
Overview
October 27, 2004

35. DoD Architecture Framework
Conclusion
Our DoD customers are being instructed to describe their system architectures for milestone review meetings using DoDAF products
Some Boeing programs are using DoDAF products in their documentation
J-UCAS has an Architecture Description Document that uses DoDAF products to capture their system architecture
Boeing systems engineers need to become familiar with developing and using the DoDAF products
DoD Architecture Framework
Overview
October 27, 2004