DoD Architecture Framework Working Group DoD …

1 Wreath stars Text DoD Architecture Framework Working Group DoD Architecture Framework Version Te s em ch t nic Sys al Operational Volume I: Definitions and Guidelines 9 February 2004. TABLE OF CONTENTS. SECTION PAGE. EXECUTIVE SUMMARY .. ES-1. 1 1-1. PURPOS E AND 1-1. Architecture DESCRIPTIONS .. 1-2. DEFINITIONS OF VIEWS .. 1-2. Definition of the Operational 1-2. Definition of the Systems View .. 1-2. Definition of the Technical Standards 1-3. Architectural Aspects that Concern All Views .. 1-3. DEFINITIONS OF 1-3. DEFINITION OF AN INTEGRATED Architecture .. 1-5. HISTORY OF THE Framework .. 1-5. ORGANIZATION OF THIS 1-6. 2 RELATED GOVERNMENT POLICY AND LEGISLATION .. 2-1. FEDERAL 2-1. Clinger-Cohen Act of 1996 .. 2-1. OMB Circular A-130 .. 2-1. Federal Enterprise Architecture Reference 2-2. DOD POLICY .. 2-4. DoDD 2-4. DoDI .. 2-5. DoDD 2-5. DoDI .. 2-5. DoDD 2-6. DoDD 2-6. JOINT STAFF POLICY .. 2-6. CJCSI .. 2-7. CJCSM .. 2-7. CJCSI 2-7. ORGANIZATION-SPECIFIC 2-7.

2 I TABLE OF CONTENTS (Cont). SECTION PAGE. 3 Architecture USES .. 3-1. REPRESENTATIVE USES OF THE THREE VIEWS .. 3-2. Use of the Operational 3-2. Use of the Systems View .. 3-3. Use of the Technical Standards 3-4. LINKAGES AMONG THE VIEWS .. 3-4. RELATIONSHIPS AMONG PRODUCTS .. 3-5. USES OF INTEGRATED ARCHITECTURES .. 3-5. THE VALUE OF ARCHITECTURES DIFFERENT USES FOR. DIFFERENT 3-6. PRODUCTS ACCORDING TO 3-8. Products Required for an Integrated Architecture .. 3-10. Planning, Programming, Budgeting, and Execution 3-14. Joint Capabilities Integration and Development 3-16. Acquisition 3-20. Operations .. 3-24. 4 TECHNIQUES FOR USING Architecture INFORMATION .. 4-1. CAPABILITY-BASED 4-1. The Situation .. 4-1. Capability Reports .. 4-1. MISSION CAPABILITY PACKAGES .. 4-1. The Situation .. 4-1. The MCP 4-2. KEY INTERFACE PROFILES .. 4-3. The Situation .. 4-3. The Key Interface Profile 4-3. HUMAN FACTORS .. 4-4. The Situation .. 4-4. Including Human Factors .. 4-4. Architecture 4-5.

3 Ii TABLE OF CONTENTS (Cont). SECTION PAGE. 5 Architecture GUIDELINES, DESCRIPTION PROCESS, AND. INTEGRATION .. 5-1. Architecture GUIDELINES .. 5-1. Guiding Principles .. 5-1. Framework Compliance Guidance .. 5-2. THE GENERIC SIX-STEP Architecture DESCRIPTION. PROCESS .. 5-4. Architecture INTEGRATION .. 5-6. Two Types of Architecture Integrations .. 5-6. Scope of Cross- Architecture Integration .. 5-7. The Value of Integration .. 5-9. 6 Architecture DATA MODEL, REPOSITORY, AND 6-1. 6-1. Architecture DATA .. 6-1. BENEFITS OF STANDARDS-BASED REPOSITORY-BASED. ARCHITECTURES .. 6-1. CADM AS A SPECIFICATION OF Architecture DATA .. 6-2. DARS AS A REPOSITORY FOR Architecture 6-3. Architecture TOOLS .. 6-6. 7 Architecture Framework EVOLUTION .. 7-1. EVOLUTION OF THE Framework .. 7-1. NET-CENTRIC OPERATIONS AND 7-1. EXECUTABLE ARCHITECTURES .. 7-1. OTHER EVOLUTION 7-2. ANNEX. A A-1. B DICTIONARY OF B-1. C REFERENCES .. C-1. iii LIST OF FIGURES. FIGURE PAGE. ES-1 Linkages Among Views.

4 ES-1. 2-1 Products Keyed to OMB Circular 2-2. 2-2 Federal Enterprise Architecture Reference 2-3. 2-3 Federal Enterprise Architecture Business Reference Model Version .. 2-4. 3-1 Operational Architecture Granularity Required for Systems Analyses .. 3-3. 3-2 Fundamental Linkages Among the Views .. 3-4. 3-3 Relationships Among Products .. 3-5. 3-4 Architectures Related to the Requirements, Acquisition, and Budgeting Processes .. 3-6. 3-5 Illustrative Architecture Value to Different Communities of Interest .. 3-8. 3-6 Using Architectures to View DoD In an Integrated Manner and to Support DoD 3-9. 3-7 Architecture Products by 3-12. 3-8 Acquisition Process and Architecture -Based Analysis .. 3-20. 3-9 Architecture -Based Metrics .. 3-22. 4-1 Using Architectures and Analysis to Influence POM Decisions .. 4-2. 4-2 Cross-View Linkages and Measurements .. 4-5. 5-1 The Six-Step Process of Building an Architecture 5-5. 5-2 Four Levels of Architecture 5-8. 6-1 CADM 6-3. 6-2 DARS Configuration.

5 6-4. TABLE. TABLE PAGE. 1-1 Architecture 1-4. iv EXECUTIVE SUMMARY. 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 The Department of Defense (DoD) Architecture Framework (DoDAF), Version , defines a common approach for DoD Architecture description development, presentation, and integration for both warfighting operations and business operations and processes. The Framework is intended to ensure that Architecture descriptions can be compared and related across organizational boundaries, including Joint and multinational boundaries. This document applies to architectures developed by and for the Office of the Secretary of Defense (OSD), the Military Departments, the Chairman of the Joint Chiefs of Staff (CJCS), the Combatant Commands, the Office of the Inspector General of the Department of Defense, the Defense Agencies, DoD Field Activities, and all other organizational entities within the Department of Defense (hereafter referred to collectively as the DoD Components ).

6 The Framework supports the development of interoperating and interacting architectures as referenced in DoD issuances. It defines three related views of Architecture : Operational View (OV), Systems View (SV), and Technical Standards View (TV) as depicted in Figure ES-1. Each view is composed of sets of Architecture data elements that are depicted via graphic, tabular, or textual products. The All- DoD Core Architecture Data Model (CADM) defines the entities and relationships for Architecture data elements. The Framework is partitioned into two volumes and a deskbook: Volume I provides definitions, guidelines, and related background material. Volume II contains descriptions for each product. The DoDAF Deskbook provides supplementary information to Framework users. Operational View Identifies What Needs to be an Accomplished and Who Does It Op d C. era ap ne Do tio abi na litie ire on It Be s lR s It D ge ne qu ati es to et han eq o Re orm Do eds uir o G xc . em Inf o Ne dt E.

7 B. en as por chni Wh hat xc d ort Su ew T bilitie ic T tab cal ts Cap W. n E an upp p es N a ec ility ng atio ities at S.. hn ha olo orm tiv th e s gy Inf Ac ms the ste Sy . Systems Specific System Capabilities Technical Standards View Required to Satisfy View Information Exchanges Relates Systems and Characteristics Prescribes Standards and to Operational Needs Technical Standards Criteria Conventions Governing Interoperable Implementation/Procurement of the Selected System Capabilities Figure ES-1. Linkages Among Views ES-1. Version of the DoDAF is an evolution of the Command, Control, Communications, Computers, Intelligence, Surveillance, and Reconnaissance (C4 ISR) Architecture Framework , Version , dated 18 December 1997, and supercedes it. This evolution reflects and leverages the experience that the DoD Components have gained in developing and using Architecture descriptions. The most significant changes in this version of the Framework include guidelines on determining Architecture content based on intended use; focus on using architectures in support of DoD's Programming, Budgeting, and Execution (PPBE) process; Joint Capabilities Integration and Development System (JCIDS); and the Defense Acquisition System; and increasing emphasis on the Architecture data elements.

8 Changes from the preceding C4 ISR. Architecture Framework , Version , are outlined on page ES-3. As DoD moves toward Net-Centric Operations and Warfare (NCOW), architectures continue to provide a critical mechanism for understanding operational concepts and their relation to capabilities, anticipating changes in operational concepts or changes in automated capabilities, and acquiring both materiel and non-materiel assets. The DoD Components have made significant progress in using architectures. Examples of using architectures to support budgeting, identification of capability gaps, acquisition, and operations include the Air Force Task Force capability-based analysis, Navy's Mission Capability Package analysis approach, and OSD/Joint Staff concept of improving interoperability through focusing on key interfaces. Descriptions of the analytical techniques developed by each of these efforts are included in the Deskbook portion of the Framework . The DoDAF, Version , was developed under the auspices of the DoDAF Working Group (AFWG), with review and comments from a broad spectrum of DoD Components.

9 The Architecture and Interoperability Directorate of the Deputy Assistant Secretary of Defense (Chief Information Officer), under the Assistant Secretary of Defense for Networks and Information Integration1 facilitated the coordinated development and evolution of the C4 ISR. Architecture Framework , Version , to the DoDAF, Version 1 The Assistant Secretary of Defense for Command, Control, Communications, and Intelligence has been re- designated as the Assistant Secretary of Defense for Networks and Information Integration. ES-2. What's New in the DoD Architecture Framework , Version Changes in the DoD Architecture Framework from its predecessor C4 ISR Architecture Framework , Version Changes are based on recommendations from the AFWG and community feedback on the C4 ISR Architecture Framework , Version 1. Document is restructured, with key guidance in Volume I, product descriptions in Volume II, and supplementary information in the Deskbook. 2. Guidelines are provided for product selection based on the intended use of the Architecture .

10 A minimum set of products necessary to comply with DoD instructions on integrated architectures is specified. 3. Document moves toward a repository-based approach by placing greater emphasis on Architecture data elements comprising the products, not just Architecture products. The following are provided: An overview of the CADM. For each product, a table of Architecture data elements associated with the product including attributes and definitions For each product, an entity-relationship diagram of corresponding CADM entities An introduction to the DoD Architecture Repository System General information on automated tools 4. The Technical View has been retitled the Technical Standards View to provide a better description of the intent and content of the view. The acronym remains TV. 5. Product descriptions and graphics in Volume II have been refined for clarity and are provided in the following structured format: Definition Purpose Detailed Description Narrative, including definitions of Architecture data elements One or more generic templates, and/or examples Equivalent representation using the Unified Modeling Language (UML).