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 .

2 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. 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.

3 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.

4 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. 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.

5 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.

6 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 .. 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.

7 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.

8 6-2 DARS Configuration .. 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.

9 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 ).

10 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.