Presentation is loading. Please wait.

Presentation is loading. Please wait.

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

Similar presentations


Presentation on theme: "October 27, 2004 DoD Architecture Framework Overview 1 Understanding the DoD Architecture Framework Products Mason Myers."— Presentation transcript:

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

2 October 27, 2004 DoD Architecture Framework Overview 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

3 October 27, 2004 DoD Architecture Framework Overview 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

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

5 October 27, 2004 DoD Architecture Framework Overview 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 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 Definition Architecture Structure of Components Relationships Principles & Guidelines = ++

6 October 27, 2004 DoD Architecture Framework Overview 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

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

8 October 27, 2004 DoD Architecture Framework Overview 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

9 October 27, 2004 DoD Architecture Framework Overview 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 DoD Architecture Framework

10 October 27, 2004 DoD Architecture Framework Overview 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

11 October 27, 2004 DoD Architecture Framework Overview 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

12 October 27, 2004 DoD Architecture Framework Overview 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

13 October 27, 2004 DoD Architecture Framework Overview 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

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

15 October 27, 2004 DoD Architecture Framework Overview 15 DoDAF Products – All Views and Operational View Applicable Architecture View Product Reference DoDAF ProductEssential or Supporting All ViewsAV-1Overview and Summary InformationEssential All ViewsAV-2Integrated DictionaryEssential OperationalOV-1High-Level Operational Concept GraphicEssential OperationalOV-2Operational Node Connectivity DescriptionEssential OperationalOV-3Operational Information Exchange MatrixEssential OperationalOV-4Command Relationships ChartSupporting OperationalOV-5Activity ModelSupporting OperationalOV-6aOperational Rules ModelSupporting OperationalOV-6bOperational State Transition DescriptionSupporting OperationalOV-6cOperational Event/Trace DescriptionSupporting OperationalOV-7Logical Data ModelSupporting

16 October 27, 2004 DoD Architecture Framework Overview 16 C 4 ISR 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

17 October 27, 2004 DoD Architecture Framework Overview 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.

18 October 27, 2004 DoD Architecture Framework Overview 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.

19 October 27, 2004 DoD Architecture Framework Overview 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.

20 October 27, 2004 DoD Architecture Framework Overview 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

21 October 27, 2004 DoD Architecture Framework Overview 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 systems role as an element of the encompassing system-of-systems.

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

23 October 27, 2004 DoD Architecture Framework Overview 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 systems role as an element of the encompassing system-of-systems OV-2 is frequently done at both the system-of-systems and system levels.

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

25 October 27, 2004 DoD Architecture Framework Overview 25 System-Level Operational Node Connectivity Product (OV-2) for BCSS BCSS Aircraft Node BCSS Ground Station Node BCSS Support 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 BCSS Simulation Node - A/C status - Ground station status - Training scenario commands - A/C simulation - Control commands - A/C status - Contact reports - Mission updates BCSS Mission Planning Node - Route Planning - Mission Validation - Mission Plans - Mission Updates

26 October 27, 2004 DoD Architecture Framework Overview 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

27 October 27, 2004 DoD Architecture Framework Overview 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

28 October 27, 2004 DoD Architecture Framework Overview 28 DoDAF Products – Systems View Applicable Architecture View Product Reference DoDAF ProductEssential or Supporting SystemsSV-1System Interface DescriptionEssential SystemsSV-2Systems Communication DescriptionSupporting SystemsSV-3Systems 2 MatrixSupporting SystemsSV-4Systems Functionality DescriptionSupporting SystemsSV-5Operational Activity to System Function Traceability Matrix Supporting SystemsSV-6System Information Exchange MatrixSupporting SystemsSV-7System Performance Parameters MatrixSupporting SystemsSV-8System Evolution DescriptionSupporting SystemsSV-9System Technology ForecastSupporting SystemsSV-10aSystem Rules ModelSupporting SystemsSV-10bSystems State Transition DescriptionSupporting SystemsSV-10cSystems Event/Trace DescriptionSupporting SystemsSV-11Physical Data ModelSupporting

29 October 27, 2004 DoD Architecture Framework Overview 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

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

31 October 27, 2004 DoD Architecture Framework Overview 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

32 October 27, 2004 DoD Architecture Framework Overview 32 DoDAF Products – Technical Standards View Applicable Architecture View Product Reference DoDAF ProductEssential or Supporting TechnicalTV-1Technical Standards ProfileEssential TechnicalTV-2Standards Technology ForecastSupporting

33 October 27, 2004 DoD Architecture Framework Overview 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

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

35 October 27, 2004 DoD Architecture Framework Overview 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 with developing and using the DoDAF products


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

Similar presentations


Ads by Google