Post on 27-Mar-2015
October 27, 2004 DoD Architecture FrameworkOverview
1
Understanding the DoD Architecture Framework
Products
Mason Myers
October 27, 2004 DoD Architecture FrameworkOverview
2
• 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”
Federal Policy/Guidance on Architectures
October 27, 2004 DoD Architecture FrameworkOverview
3
DoD Policy on Using Architectures
• DoDD 8000.1, Management of DoD Information Resources and Information Technology
• DoDD 8100.01, Global Information Grid Overarching Policy
• DoDD 5000.1, The Defense Acquisition System, (12May2003)
• DoDI 5000.2, Operation of the Defense Acquisition System, (12May2003)
• CJCSI 3170.01C, Joint Capabilities Integration and Development System
• CJCSI 6212.01C, Interoperability and Supportability of National Security Systems and Information Technology Systems
• DoDD 4630.5, Interoperability and Supportability of Information and National Security Systems
• DoDI 4630.8, 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
October 27, 2004 DoD Architecture FrameworkOverview
4
DoDD 5000.1 and .2 Oversight & ReviewDoDD 5000.1 and .2 Oversight & ReviewACAT ID/IAM ProgramsACAT ID/IAM Programs**
DoDD 5000.1 and .2 Oversight & ReviewDoDD 5000.1 and .2 Oversight & ReviewACAT ID/IAM ProgramsACAT ID/IAM Programs**
Defense AcquisitionBoard
Defense AcquisitionBoard
C3I OverarchingIntegrated Product
Team (OIPT)
C3I OverarchingIntegrated Product
Team (OIPT)
C3ISR Systems
OverarchingIntegrated Product
Teams (OIPT)
OverarchingIntegrated Product
Teams (OIPT)
Weapon Systems
Defense AcquisitionExecutive
Chief Information
Officer
IT AcquisitionBoard
IT AcquisitionBoard
Major AIS
*Note: Space Programs have been delegated to the Air Force and most missile defense programs to the Missile Defense Agency
October 27, 2004 DoD Architecture FrameworkOverview
5
• 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 610.12
“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 1471-2000
Architecture Definition
ArchitectureStructure of Components
RelationshipsPrinciples &Guidelines
= + +
October 27, 2004 DoD Architecture FrameworkOverview
6
• 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 (DoDAF) Purpose
October 27, 2004 DoD Architecture FrameworkOverview
7
DoD ArchitectureCoordination
Council
History of DoD Architecture Framework
Prior CommunityExperiences
C4ISR ITF Integrated
ArchitecturesPanel
C4ISR ArchitectureFrameworkVersion 1.0
C4ISR ArchitectureFrameworkVersion 2.0
C4ISR Architecture
Working Group
ArchitectureFramework
Working Group
DoD ArchitectureFrameworkVersion 2.0
June 1996
Dec 1997
2003
October 27, 2004 DoD Architecture FrameworkOverview
8
• 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
October 27, 2004 DoD Architecture FrameworkOverview
9
• 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
http://www.aitcnet.org/dodfw/
DoD Architecture Framework
October 27, 2004 DoD Architecture FrameworkOverview
10
• 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
October 27, 2004 DoD Architecture FrameworkOverview
11
• 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
DoDAF Operational View
October 27, 2004 DoD Architecture FrameworkOverview
12
• 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
DoDAF Systems View
October 27, 2004 DoD Architecture FrameworkOverview
13
• 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
DoDAF Technical View
October 27, 2004 DoD Architecture FrameworkOverview
14
OperationalView
Identifies WarfighterRelationships and Information Needs
SystemsView
Relates Capabilities and Characteristicsto Operational Requirements
TechnicalView
Prescribes Standards andConventions
Specific CapabilitiesIdentified to SatisfyInformation-ExchangeLevels and OtherOperational Requirements
Technical Criteria GoverningInteroperable Implementation/Procurement of the SelectedSystem Capabilities
One Architecture, multiple views or perspectives
Relationship Between DODAF Views
October 27, 2004 DoD Architecture FrameworkOverview
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
All Views AV-2 Integrated Dictionary Essential
Operational OV-1 High-Level Operational Concept Graphic Essential
Operational OV-2 Operational Node Connectivity Description Essential
Operational OV-3 Operational Information Exchange Matrix Essential
Operational OV-4 Command Relationships Chart Supporting
Operational OV-5 Activity Model Supporting
Operational OV-6a Operational Rules Model Supporting
Operational OV-6b Operational State Transition Description Supporting
Operational OV-6c Operational Event/Trace Description Supporting
Operational OV-7 Logical Data Model Supporting
October 27, 2004 DoD Architecture FrameworkOverview
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
October 27, 2004 DoD Architecture FrameworkOverview
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.
October 27, 2004 DoD Architecture FrameworkOverview
18
Overview and Summary Information Product (AV-1) for BCSS
1. Identification – The BCSS is to be developed for the Department of Homeland Security to meet the BCSS mission roles.
2. 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.
3. 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.
October 27, 2004 DoD Architecture FrameworkOverview
19
Overview and Summary Information Product (AV-1) for BCSS
4. 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.
5. 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.
October 27, 2004 DoD Architecture FrameworkOverview
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
October 27, 2004 DoD Architecture FrameworkOverview
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.
October 27, 2004 DoD Architecture FrameworkOverview
22
High-Level Concept Graphic Product (OV-1) for BCSS
NIMA
INTEL COMMS GPS
BCSSMissionPlanning
BCSSGroundStation
AirTrafficControl
OtherAircraft
BCSSAircraft
October 27, 2004 DoD Architecture FrameworkOverview
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.
October 27, 2004 DoD Architecture FrameworkOverview
24
System-of-Systems Operational Node Connectivity Product (OV-2) for BCSS
GPSSatellite
Node
BCSSAircraftNode
OtherAircraftNode
NIMANode
BCSS MissionPlanning
Node
BCSS GroundStationNode
Air TrafficControlNode
- Broadcast Position & Time
- Satellite position & time- Constellation data
- A/C ID & position
- Flight control- Mission track- Surveillance- Status reporting- A/C deconfliction
- ATC commands
- Airspace deconfliction
- Control commands- A/C status- Contact reports- Mission updates
- A/C deconfliction
- A/C monitoring- Mission monitoring- Contact reporting- Contingency handling
- Mission plans- Mission updates
- Route planning- Mission validation
- Database production
- DTED/DPPDB data
October 27, 2004 DoD Architecture FrameworkOverview
25
System-Level Operational Node Connectivity Product (OV-2) for BCSS
BCSSAircraftNode
BCSS GroundStationNode
BCSSSupport
Node
- Flight control- Mission track- Surveillance- Status reporting- A/C deconfliction- Subsystems diagnostics
- Diagnostic commands- Diagnostic status- Power-up/power-down sequencing commands
- A/C maintenance- Ground station maintenance- Operator training
- Control commands- A/C status- Contact reports- Mission updates
- A/C monitoring- Mission monitoring- Contact reporting- Contingency handling
BCSSSimulation
Node
- A/C status- Ground station status
- Training scenario commands
- A/C simulation
- Control commands- A/C status- Contact reports- Mission updates
BCSS MissionPlanningNode
- Route Planning- Mission Validation
- Mission Plans- Mission Updates
October 27, 2004 DoD Architecture FrameworkOverview
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
October 27, 2004 DoD Architecture FrameworkOverview
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
October 27, 2004 DoD Architecture FrameworkOverview
28
DoDAF Products – Systems ViewApplicable
Architecture View
Product Reference
DoDAF Product Essential or Supporting
Systems SV-1 System Interface Description Essential
Systems SV-2 Systems Communication Description Supporting
Systems SV-3 Systems2 Matrix Supporting
Systems SV-4 Systems Functionality Description Supporting
Systems SV-5 Operational Activity to System Function Traceability Matrix
Supporting
Systems SV-6 System Information Exchange Matrix Supporting
Systems SV-7 System Performance Parameters Matrix Supporting
Systems SV-8 System Evolution Description Supporting
Systems SV-9 System Technology Forecast Supporting
Systems SV-10a System Rules Model Supporting
Systems SV-10b Systems State Transition Description Supporting
Systems SV-10c Systems Event/Trace Description Supporting
Systems SV-11 Physical Data Model Supporting
October 27, 2004 DoD Architecture FrameworkOverview
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
October 27, 2004 DoD Architecture FrameworkOverview
30
System-of-Systems Interface Description Product (SV-1) for BCSS
GPSSatellite
Node
BCSSAircraftNode
OtherAircraftNode
NIMANode
BCSS MissionPlanning
Node BCSS GroundStationNode
Air TrafficControlNode
- Broadcast Position & Time
- RF communication
- LOS communications
- Communications- Flight control- Mission track- Surveillance- Status reporting- A/C deconfliction
- LOS & satellite communications
- Communications- Airspace deconfliction
- LOS & satellite communications
- Communications- A/C deconfliction
- Communications - A/C monitoring- Mission monitoring- Contact reporting- Contingency handling
- Media for ission plans and updates
- Route planning- Mission validation- Mission distribution
- Database production- Media production
- Media containing DTED/DPPDB
October 27, 2004 DoD Architecture FrameworkOverview
31
System-Level Interface Description Product (SV-1) for BCSS
BCSSAircraftNode
BCSS GroundStationNode
BCSSSupportNode
- Flight control- Navigation- Mission track- Propulsion- Surveillance- Status reporting- A/C deconfliction- Subsystems diagnostics- Communications
- RF communication- Umbilical communication
- A/C maintenance- Ground station maintenance- Operator training
- LOS communications- Satellite communications
- Communications- A/C monitoring- Mission monitoring- Contact reporting- Contingency handling
BCSSSimulation
Node
- Wire communications
- Wire communications
- A/C simulation- Communications
- LOS communications- Satellite communications
BCSS MissionPlanning
Node
- Route Planning- Mission Validation- Mission Distribution
- Files for mission plans and updates
October 27, 2004 DoD Architecture FrameworkOverview
32
DoDAF Products – Technical Standards View
Applicable Architecture
View
Product Reference
DoDAF Product Essential or Supporting
Technical TV-1 Technical Standards Profile Essential
Technical TV-2 Standards Technology Forecast Supporting
October 27, 2004 DoD Architecture FrameworkOverview
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
October 27, 2004 DoD Architecture FrameworkOverview
34
Technical Standards Profile (TV-1) Template Example
JTA Service Area
Service JTA Standard and Source Document
Information Processing
Higher Order Languages
Geospatial Data Interchange Motion Imagery Data Exchange – Video Information Transfer
Data Flow Network
Command and Control Information Network
Network Interface File Transfer Standards Network Time Synchronization Standards Info Security and Infrastructure Standards
Password Security
Virtual Private Network Service Intrusion Detection Service Human-Computer Interface Security
Standards
October 27, 2004 DoD Architecture FrameworkOverview
35
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 withdeveloping and using the DoDAF products