Integrating DoDAF into Systems Engineering Process

1. - INCOSE PRESENTATION - Integrating DoDAF into Systems Engineering Process Linda Davis/Lisa Meacham Northrop Grumman

2. - INCOSE PRESENTION - Agenda • DoD Architecture Framework (DoDAF) Overview • Integrate DoDAF into Systems Engineering (SE) Process • Benefits of Integrating DoDAF into SE Process • Leveraging Traceability to integrate DoDAF and Requirements • Summary • Tools • Q&A/Open Discussion

3. - INCOSE PRESENTATION - DoDAF Overview • What is Department of Defense Architecture Framework (DoDAF)? • Defines a common approach for describing and presenting architectures • A graphical, textual and tabular representation of anarchitecture Architecture Modeling

4. - INCOSE PRESENTATION - DoDAF Overview • Rules and guidelines presented in two volumes and a deskbook (Version 1.0, August 2003) • Volume I: provides definitions and guidelines • Volume II: describes each architecture product • Deskbook: provides supplementary information • Documentation can be found at: http://aitc.aitcnet.org/dodfw/ The U.S. Department of Defense mandates the use of DoDAF for all architectures developed by and for all organizational entities within the DoD. (refer to DoD promulgation memo found at http://aitc.aitcnet.org/dodfw/)

5. - INCOSE PRESENTATION - DoDAF Overview - Views • DoDAF architectures are described in terms of 4 views • Operational Views (OV) • System Views (SV) • Technical Standards Views (TV) • All Views (AV) • Each main view conveys different aspects of the architecture Operational Elements, Tasks/Activities, Information Exchanges Systems supporting Operational Elements, System Interfaces Current Technical Standards, Future Technical Standards Fundamental Linkages Among Views From “DoD Architecture Framework v. 1.0 (Vol I, 15 August 2003)

6. - INCOSE PRESENTATION - DoDAF Overview - Products • Each view is represented by products • Each product conveys different aspects of the architecture view All Views • Produce the minimum required products. • Add additional products based on intended use of your DoDAF architecture. Operational Views System Views Technical Views

7. - INCOSE PRESENTATION - DoDAF Overview – Product Examples Common definitions/terms used across products OV-5, Operational Activity Model ActivityA - 1 ActivityB - 1 ActivityA-2 ActivityB-2 Flow1 ActivityA-1 OpNodeA - OpNodeB Flow2 (Info ExchangeA ) OpNode OpNode A B ActivityB-1 ActivityB-2 Flow3 OpNodeB - OpNodeC Flow4 (Info ExchangeB OpNodeA - OpNodeC (InfoExchangeC) ActivityC-1 OpNode C ActivityC - 1 OpNodeB ActivityC-2 OV-2, Operational Node Connectivity Diagram OpNodeA System 2 Interface1 Interface3 System 1 OpNodeB System 4 Interface2 System 3 OV-3, Information Exchange Matrix SV-1, System Interface Description Information/Symbols Represents Architecture Capabilities/Requirements

8. · Operational activities map to operational nodes OV - 5 · Flows map to needlines · Operational Nodes map to System Nodes · Operational Needlines map to System OV - 2 Interfaces · Operational activities are SV - 1 supported by systems · Flows map to operational information exchanges · Information Exchanges are detailed in the OV-3 OV - 3 - INCOSE PRESENTATION - DoDAF Overview – Fundamental Linkages Example Products have relationships to other products.

9. - INCOSE PRESENTATION - DoDAF Overview – Uses for DoDAF • Examples of how DoDAF can be used • To describe the baseline architecture, the current capabilities/requirements (i.e., “As-Is”) • To describe future views of the architecture, future capabilities/requirements (i.e., “To-Be”, “Objective”) • For budgeting and planning purposes • For gap analysis • Identify requirements As-IS To-Be ....ArchitectureEvolution....

10. - INCOSE PRESENTATION - DoDAF Overview – Example of DoDAF Sources Baseline Interface Specifications Future Technical Standards Future Concept of Operations Baseline/Met Requirements Supported Technical Standards As-Is Architecture as base Baseline Concept of Operations Future Capabilities/ Requirements As-IS To-Be ....ArchitectureEvolution.... • Establish the To-Be Time Frame. • Use the To-Be for Gap Analysis, Budgeting and Planning. Gap Analysis/Budget/Planning

11. - INCOSE PRESENTATION - Integrate DoDAF into Systems Engineering Process Systems Engineering Lifecycle Concept Definition System Requirements Analysis & Design S/W Requirements Analysis & Design Integration & Test

12. Sys Arch Def Sys Reqmts Components External I/F Use Cases Use Case Models Prototyping & Code Analysis - INCOSE PRESENTATION - Benefits of Integrating DoDAF into SE Process DoDAF Views Segments S/W Reqmts Internal I/F Low Level Infrastructure Concept Definition System Reqmts Analysis System Design S/W Reqmts Analysis Software Design Develop Test Procedures Lower Level Use Case Models * Key is Multiple Iterations and Checks and Balance Integration & Test

13. Parent 3.2.1.1 The System shall… 3.7.2.1.4 The Sub-system shall… Child - INCOSE PRESENTATION - Leveraging Traceability to Integrate DoDAF and Requirements • Traceability – a link or definable relationship between two entities • Requirement to Requirement Traceability Parent-to-child traceability ensures that all source requirements have been addressed Child-to-Parent traceability ensures that the source of a requirement is documented.

14. DoDAF Views 3.2.1.1 The System shall… 3.7.2.1.4 The Sub-system shall… Use Cases - INCOSE PRESENTATION - Leveraging Traceability to Integrate DoDAF and Requirements, Cont. • Requirements to Models (DoDAF Views) Traceability Customer provides CONOPS Systems Engineer Develops Systems Architect develops Collaboration between Systems Architect and Systems Engineer - Check and Balance is the Key -

15. - INCOSE PRESENTATION - Summary • Today, suppliers of defense solutions must describe their offering in terms of an architecture framework • Integrate DoDAF into SE Process • Traceability helps to integrate DoDAF and Requirements • It is the Intelligent Implementation of theProcess that will lead to the successful development of a system

16. - INCOSE PRESENTATION - Tools and Open Discussion/Q&A • Tools • Open Discussion/Q&A