DoDAF Maintenance Update (v2.03) 05 Jan 2012 DoDAF Team 1 1

Outline Recap of the DoDAF Configuration Management Process CM Plan (CMP) ASRG, FAC, and DoDAF-DM2 WG CM Processes Overview CM “Business” Rules Changes for 2.03 Formal coordination review plan 2

DoD Architecture Framework Evolution and CM C4ISR F/W’s Joint Interoperability DoDAF 1.0 JCIDS, applicability beyond C4ISR DoDAF 1.5 Net-centricity and SoA DoDAF 2.0 Fit-for-purpose, data-centric architecture, improved models of systems, services, capabilities, rules, measures CM phase: High-priority improvements, error correction, emerging requirements Stability for governance developers, users, vendors

DoDAF is under formal CM CONFIGURATION IDENTIFICATION ORGANIZATIONAL ROLES, RESPONSIBILITIES, AND INTERACTIONS DODAF-DM2 CM PROCESSES AND PROCEDURES DODAF-DM2 CM BUSINESS RULES CONFIGURATION STATUS ACCOUNTING

Configuration Identification DoDAF Viewpoint Definitions. Conventions for the construction, interpretation and use of architecture views and associated architecture models. DoDAF Model Specifications. Specifications from which architecture views representing a architecture are composed. Glossary. Defines all non-demotic terms used in DoDAF and the DoDAF Meta Model. DM2. Consists of a Conceptual Data Model (CDM) diagram and narrative description, a Logical Data Model (LDM) in an UML file adapted to IDEAS and a narrative description, and Physical Exchange Specification (PES) XML Schema Descriptions. NOTE that introductory, tutorial, document outlining, and web navigation documentation is considered under control of the DoDAF Journal editorial team and not subject to formal CM in scope of this plan.

CM Organizational Roles CONFIGURATION STATUS ACCOUNTING CR Tracker (CRT) CSAR VDD 6

CMP Processes CR Processing and Configuration Status Reporting Baseline Process 7

CMP Business Rules Terms and Definitions Aliases Core Process Requirement Aggregation Rule Subtype Rule Typed Relationships Attributes and Properties DoDAF model specification Information Pedigree Security classification marking Terms and Definitions All model and alias terms proposed for inclusion in the data dictionary shall be researched for multiple source definitions. DoD definitions shall be included. Other Federal Government, industry and academic and common definitions should also be included. The WG shall formulate a baseline definition based on the multiple sources, core process requirements, and model structural meaning. The source definitions and the rationale for the baseline definition shall be maintained in the data dictionary as well. Aliases Terms representing concepts that are represented in a semantically equivalent way by other terms and concepts in the model shall be maintained as aliases and shall not be introduced into the model. Multiple source definitions shall be maintained as with other model terms and a consensus definition shall be derived from the sources. Core Process Requirement All concepts included in the DM2 shall be necessary to support the information requirements of one or more core processes (PPBE, DAS, JCIDS, CPM, SE, OPS). All DoDAF models shall be applicable to one or more core processes. Core process information requirements shall be as explicitly or implicitly specified in current or planned DoD governance. All model terms and concepts not necessary for core process support with architectures shall be removed. All core process information requirements for architectural descriptions shall be modeled and contained in one or more DoDAF models. Aggregation Rule If a term representing a concept differs structurally from some other term representing some concept only in level of aggregation, it shall not be included in the model. Whole-part relationships cover the need without different names for different types of wholes and parts. The term may be included as an alias. Subtype Rule If a term representing a subtype concept has no structural difference from its supertype, it shall not be included in the model. Super-subtype relationships cover the need without different names for different types of supertypes and subtypes. The term may be included as an alias. Typed Relationships All relationships shall be typed, ultimately up to IDEAS foundation. The typing shall be determined using BORO analysis of spatio-temporal examples. Attributes and Properties All attribute and property relationships shall be explicit, that is, by an association class that is typed according to the Typed Relationships rule. The only exceptions are for representational exemplars. DoDAF model specification All DoDAF models shall be specified using terms from the data dictionary. Aliases may be used. If new terms are required, they shall undergo the process for new term inclusion in the data dictionary as described by the Terms and Definitions and Aliases rules. All DoDAF models shall be mapped to the DM2 classes (base and associative) that represent the information contained in the view the model specifies. Information Pedigree There shall be a provision to provide pedigree (and provenance) for every piece of data IAW NCDS Security classification marking There shall be a provision to provide a classification marking for every piece of data and for DM2 PES XML documents overall IAW NCDS 8

DoDAF-DM2 WG Status: Change Request Status 9

Packaging for Formal CM Vol. I DM2 Conceptual Model DoDAF Viewpoints & Models Vol. II DM2 Logical DM DoDAF Model Specs DoDAF Glossary SparxEA .EAP DM2 Vol. III DM2 Physical DM: PES SparxEA .EAP IDEAS Foundation 10

Changes for v2.03 TECHEDITS Normative parts separated from informative parts Normative parts subject to formal coordination with DoD Components Informative parts moved to DoDAF Journal Document + Webpages Major DM2 CR’s: Rules and Desired Effects: Their Descriptions are produced by rule and goal-setting authorities They are consumed by Activities (ala Controls in IDEF0 Conforming Activities are subtypes Information resource flow was simplified into flatter type structure so it would be logically correct and consistent with other Resource Flows, e.g., Aircraft 123 on my scope Î {all reports on A/C 123} Ì {TADIL-J 3.2 msg} Capability made a subtype of Property so that it is the set of Tasks performed under Conditions that meet certain performance standards (Measures) Makes Capability comparison and dependencies more direct (simple set operations) Distinguished that Guidance influences Activity from Rules that control Activity Added SoA Joint Action concept Continued work on distinguishing Roles (within scope of EA) from types of Persons (outside scope of EA) exists spatio-temporally a set usable in, e.g., SV-6 11

Marine Corps - Led TECHEDIT Team Marine Corps commented on many incorrect, ambiguous, and inconsistent statements After working on this for several meetings, the WG requested a rewrite rather than line-by-line fixes SPAWAR noted many undefined and inconsistent terms in the DoDAF model A long-standing CR asked for a DM2 diagram for each DoDAF model as in DoDAF 1.x documents 12

TECHEDIT Team Rules Must follow DoDAF-DM2 WG rules (per CM Plan) Structure of each model specification: Name. The twenty-four revised names agreed to by the WG under CR #579 shall be used. One Sentence Description. The twenty-four revised “one-liners” agreed to by the WG under CR #579 shall be used. Narrative Description (one page maximum). DoDAF Glossary terms (in DM2 or aliases) shall be used per DoDAF-DM2 CM Business Rule #8. Meta-model diagram (one-half to one page). Other Names for this artifact (one-quarter page). 13

OV-2 As-Is Text is lengthy… but doesn’t actually ever get around to unambiguously specifying content for an OV-2 model…

TECHEDIT Example Name: One-Liner: Narrative: Diagram: Other names: Notes: SHALLS & MAYS 15

SV-1 Issues Identified by DoDAF WG Name: Systems Interface Description One liner: The identification of systems, system items, and their interconnections. Description: composition and interaction of Systems links together the operational and systems architecture models -- a SV-1 may represent the realization of a requirement specified in an OV-2 there may be many alternative SV models that could realize the operational requirement. in an “As-Is” architecture, the OV-2 may simply be a simplified, logical representation of the SV-1 to allow communication of key Resource Flows to non-technical stakeholders. A System Resource Flow is a simplified representation of a pathway or network pattern, Note that Resource Flows between Systems may be further specified in detail in SV-2 Systems Resource Flow Description and SV-6 Systems Resource Flow Matrix. Sub-System assemblies SV-1 may also identify the Physical Assets (e.g., Platforms) at which Resources are deployed optionally overlay Operational Activities and Locations In many cases, an operational activity and locations depicted in an OV-2 may well be the logical representation of the resource that is shown in SV-1. The SV-1 is used in two complementary ways: Describe the Resource Flows exchanged between resources in the architecture. Describe a solution, or solution option, in terms of the components of capability and their physical integration on platforms and other facilities. Detailed Description: Systems and sub-systems The real benefit of a SV-1 is its ability to show the human aspects of an architecture, and how these interact with Systems. Capability and Performers which is used to gather together systems, assets and people into a configuration, which can meet a specific capability. A primary purpose of a SV-1 DoDAF-described Model is to show resource structure, i.e., identify the primary sub-systems, performer and activities (functions) and their interactions. SV-1 contributes to user understanding of the structural characteristics of the capability. The physical resources contributing to a capability are either an organizational resource or a physical asset, i.e., a system cannot contribute alone (it must be hosted on a physical asset used by an organizational resource of both). Organizational aspects can now be shown on SV-1 (e.g., who uses System). Resource structures may be identified in SV-1 DoDAF does not specifically use terms such as, sub-System and component as these terms often denote a position relative to a structural hierarchy. Any System may combine hardware and software or these can be treated as separate (sub) Systems. DoDAF V2.0 includes human factors (as Personnel Types and a type of Performer). Should an architect wish to describe a System which has human elements, then Systems, Personnel Types and Performers should be used to wrap the human and system elements together. optionally be annotated with Operational Activities, Capabilities, and/or Locations originally specified in OV-2 Every phrase analyzed contains problematic terms or expressions that are: not defined used mysteriously inconsistent within this description or across the document ambiguous vague suggest content exists elsewhere that does not exist logically, operationally, or technically wrong The SV-1 addresses the composition and interaction of Systems. For DoDAF V2.0, the SV-1 incorporates the human elements as types of Performers - Organizations and Personnel Types. Resources are defined in Section 2.2.1 The SV-1 links together the operational and systems architecture models by depicting how Resources are structured and interact to realize the logical architecture specified in an OV-2 Operational Resource Flow Description. A SV-1 may represent the realization of a requirement specified in an OV-2 Operational Resource Flow Description (i.e., in a “To-Be” architecture), and so there may be many alternative SV models that could realize the operational requirement. Alternatively, in an “As-Is” architecture, the OV-2 Operational Resource Flow Description may simply be a simplified, logical representation of the SV-1 to allow communication of key Resource Flows to non-technical stakeholders. A System Resource Flow is a simplified representation of a pathway or network pattern, usually depicted graphically as a connector (i.e., a line with possible amplifying information). The SV-1 depicts all System Resource Flows between Systems that are of interest. Note that Resource Flows between Systems may be further specified in detail in SV-2 Systems Resource Flow Description and SV-6 Systems Resource Flow Matrix. Sub-System assemblies may be identified in SV-1 to any level (i.e., depth) of decomposition the architect sees fit. SV-1 may also identify the Physical Assets (e.g., Platforms) at which Resources are deployed, and optionally overlay Operational Activities and Locations that utilize those Resources. In many cases, an operational activity and locations depicted in an OV-2 Operational Resource Flow Description model may well be the logical representation of the resource that is shown in SV-1. The intended usage of the SV-1 includes: Definition of System concepts. Definition of System options. System Resource Flow requirements capture. Capability integration planning. System integration management. Operational planning (capability and performer definition). The SV-1 is used in two complementary ways: Describe the Resource Flows exchanged between resources in the architecture. Describe a solution, or solution option, in terms of the components of capability and their physical integration on platforms and other facilities. Detailed Description: A SV-1 can be used simply to depict Systems and sub-systems and identify the Resource Flows between them. The real benefit of a SV-1 is its ability to show the human aspects of an architecture, and how these interact with Systems. In addition, DoDAF has the concept of Capability and Performers (see Capability Meta-model group in Section 2) which is used to gather together systems, assets and people into a configuration, which can meet a specific capability. A primary purpose of a SV-1 DoDAF-described Model is to show resource structure, i.e., identify the primary sub-systems, performer and activities (functions) and their interactions. SV-1 contributes to user understanding of the structural characteristics of the capability. The physical resources contributing to a capability are either an organizational resource or a physical asset, i.e., a system cannot contribute alone (it must be hosted on a physical asset used by an organizational resource of both). Organizational aspects can now be shown on SV-1 (e.g., who uses System). Resource structures may be identified in SV-1 to any level (i.e., depth) of decomposition the architect sees fit. DoDAF does not specifically use terms such as, sub-System and component as these terms often denote a position relative to a structural hierarchy. Any System may combine hardware and software or these can be treated as separate (sub) Systems. DoDAF V2.0 includes human factors (as Personnel Types and a type of Performer). Should an architect wish to describe a System which has human elements, then Systems, Personnel Types and Performers should be used to wrap the human and system elements together. A SV-1 can optionally be annotated with Operational Activities, Capabilities, and/or Locations originally specified in OV-2 Operational Resource Flow Description model. In this way, traceability can be established from the logical OV structure to the physical System Viewpoint structure. If possible, a SV-1 shows Systems, Physical Assets and System interfaces for the entire Architectural Description on the same diagram. If a single SV-1 is not possible, the resource of interest should be decomposed into multiple SV-1 models. Functions (Activities): Some Resources can carry out System Functions (Activities) as described in SV-4 Systems Functionality Description model and these functions can optionally be overlaid on a SV-1. In a sense, the SV-1 and the SV-4 Systems Functionality Description model provide complementary representations (structure and function). Either could be modeled first, but usually an iterative approach is used to model these together gradually building up the level of detail in the System description. Note that the same type (class) of resource may be used in different contexts in a given SV-1. For this reason, the tracing of functions to resources is specified in context of their usage (see DM2 for details). Resource Flows in SV-1: In addition to depicting Systems (Performers) and their structure, the SV-1 addresses Resource Flows. A Resource Flow, as depicted in SV-1, is an indicator that resources pass between one System and the other. In the case of Systems, this can be expanded into further detail in SV-2 Systems Resource Flow Description. Interactions are only possible between Systems and Services. System Resource Flows provide a specification for how the operational Resource Flows Exchanges specified in Needlines (in the OV-2 Operational Resource Flow Description model) are realized with Systems. A single Needline shown in the OV-2 Operational Resource Flow Description model may translate into multiple System Resource Flows. The actual implementation of a System Resource Flow may take more than one form (e.g., multiple physical links). Details of the physical pathways or network patterns that implement the interfaces are documented in SV-2 Systems Resource Flow Description. System Resource Flows are summarized in a SV-3b Systems-Systems Matrix. The functions performed by the resources are specified in a SV-4 System Functionality Description, but may optionally be overlaid on the Resources in a SV-1. An Operational Viewpoint (OV) suite may specify a set of requirements – either as a specific operational plan, or a scenario for procurement. As OV-2 Operational Resource Flow Description, OV-5a Operational Activity Decomposition Tree, and OV-5b Operational Activity Model specify the logical structure and behavior, SV-1 and SV-4 Systems Functionality Description specify the physical structure and behavior (to the level of detail required by the architectural stakeholders). This separation of logical and physical presents an opportunity for carrying out architectural trade studies based on the architectural content in the DoDAF-described Models. The structural and behavioral models in the OVs and SVs allow architects and stakeholders to quickly ascertain which functions are carried out by humans and which by Systems for each alternative specification and so carry out trade analysis based on risk, cost, reliability, etc. Spotlight on synopsis prepared by DoDAF WG. Highlighted words were found to be problematic.

SV-1 Content Guidance for Template and Descriptions Several distinct pieces are currently described. They should be refactored: SV-1a Interface Description. The SV-1a shows interfaces (Resource Flows) between Systems, Services, and/or Person Types. SV-1b Perfomer Configuration Diagram. Interface Description plus composition (whole-parts) of Resources involved. If Locations are involved in the configuration, relationships to Resources. SV-1c Functional Allocation. Activities (System Functions) performed by Systems, Services, and Person Types. SV-1d Organizational Resources. Shows Resources that are part of (whole-part) Organizations. SV-1e Organizational Dependencies. Shows Organizations whose Activities are reified by System Functions (Activities) performed by Performer Configurations. All views should show traceability to higher-order reifications, other views that constitute requirements, and/or other non-view requirements. This should be restated for just about every model. Systems relationship to Capabilities – already in SV-5. The SV-1 addresses the composition and interaction of Systems. For DoDAF V2.0, the SV-1 incorporates the human elements as types of Performers - Organizations and Personnel Types. Resources are defined in Section 2.2.1 The SV-1 links together the operational and systems architecture models by depicting how Resources are structured and interact to realize the logical architecture specified in an OV-2 Operational Resource Flow Description. A SV-1 may represent the realization of a requirement specified in an OV-2 Operational Resource Flow Description (i.e., in a “To-Be” architecture), and so there may be many alternative SV models that could realize the operational requirement. Alternatively, in an “As-Is” architecture, the OV-2 Operational Resource Flow Description may simply be a simplified, logical representation of the SV-1 to allow communication of key Resource Flows to non-technical stakeholders. A System Resource Flow is a simplified representation of a pathway or network pattern, usually depicted graphically as a connector (i.e., a line with possible amplifying information). The SV-1 depicts all System Resource Flows between Systems that are of interest. Note that Resource Flows between Systems may be further specified in detail in SV-2 Systems Resource Flow Description and SV-6 Systems Resource Flow Matrix. Sub-System assemblies may be identified in SV-1 to any level (i.e., depth) of decomposition the architect sees fit. SV-1 may also identify the Physical Assets (e.g., Platforms) at which Resources are deployed, and optionally overlay Operational Activities and Locations that utilize those Resources. In many cases, an operational activity and locations depicted in an OV-2 Operational Resource Flow Description model may well be the logical representation of the resource that is shown in SV-1. The intended usage of the SV-1 includes: Definition of System concepts. Definition of System options. System Resource Flow requirements capture. Capability integration planning. System integration management. Operational planning (capability and performer definition). The SV-1 is used in two complementary ways: Describe the Resource Flows exchanged between resources in the architecture. Describe a solution, or solution option, in terms of the components of capability and their physical integration on platforms and other facilities. Detailed Description: A SV-1 can be used simply to depict Systems and sub-systems and identify the Resource Flows between them. The real benefit of a SV-1 is its ability to show the human aspects of an architecture, and how these interact with Systems. In addition, DoDAF has the concept of Capability and Performers (see Capability Meta-model group in Section 2) which is used to gather together systems, assets and people into a configuration, which can meet a specific capability. A primary purpose of a SV-1 DoDAF-described Model is to show resource structure, i.e., identify the primary sub-systems, performer and activities (functions) and their interactions. SV-1 contributes to user understanding of the structural characteristics of the capability. The physical resources contributing to a capability are either an organizational resource or a physical asset, i.e., a system cannot contribute alone (it must be hosted on a physical asset used by an organizational resource of both). Organizational aspects can now be shown on SV-1 (e.g., who uses System). Resource structures may be identified in SV-1 to any level (i.e., depth) of decomposition the architect sees fit. DoDAF does not specifically use terms such as, sub-System and component as these terms often denote a position relative to a structural hierarchy. Any System may combine hardware and software or these can be treated as separate (sub) Systems. DoDAF V2.0 includes human factors (as Personnel Types and a type of Performer). Should an architect wish to describe a System which has human elements, then Systems, Personnel Types and Performers should be used to wrap the human and system elements together. A SV-1 can optionally be annotated with Operational Activities, Capabilities, and/or Locations originally specified in OV-2 Operational Resource Flow Description model. In this way, traceability can be established from the logical OV structure to the physical System Viewpoint structure. If possible, a SV-1 shows Systems, Physical Assets and System interfaces for the entire Architectural Description on the same diagram. If a single SV-1 is not possible, the resource of interest should be decomposed into multiple SV-1 models. Functions (Activities): Some Resources can carry out System Functions (Activities) as described in SV-4 Systems Functionality Description model and these functions can optionally be overlaid on a SV-1. In a sense, the SV-1 and the SV-4 Systems Functionality Description model provide complementary representations (structure and function). Either could be modeled first, but usually an iterative approach is used to model these together gradually building up the level of detail in the System description. Note that the same type (class) of resource may be used in different contexts in a given SV-1. For this reason, the tracing of functions to resources is specified in context of their usage (see DM2 for details). Resource Flows in SV-1: In addition to depicting Systems (Performers) and their structure, the SV-1 addresses Resource Flows. A Resource Flow, as depicted in SV-1, is an indicator that resources pass between one System and the other. In the case of Systems, this can be expanded into further detail in SV-2 Systems Resource Flow Description. Interactions are only possible between Systems and Services. System Resource Flows provide a specification for how the operational Resource Flows Exchanges specified in Needlines (in the OV-2 Operational Resource Flow Description model) are realized with Systems. A single Needline shown in the OV-2 Operational Resource Flow Description model may translate into multiple System Resource Flows. The actual implementation of a System Resource Flow may take more than one form (e.g., multiple physical links). Details of the physical pathways or network patterns that implement the interfaces are documented in SV-2 Systems Resource Flow Description. System Resource Flows are summarized in a SV-3b Systems-Systems Matrix. The functions performed by the resources are specified in a SV-4 System Functionality Description, but may optionally be overlaid on the Resources in a SV-1. An Operational Viewpoint (OV) suite may specify a set of requirements – either as a specific operational plan, or a scenario for procurement. As OV-2 Operational Resource Flow Description, OV-5a Operational Activity Decomposition Tree, and OV-5b Operational Activity Model specify the logical structure and behavior, SV-1 and SV-4 Systems Functionality Description specify the physical structure and behavior (to the level of detail required by the architectural stakeholders). This separation of logical and physical presents an opportunity for carrying out architectural trade studies based on the architectural content in the DoDAF-described Models. The structural and behavioral models in the OVs and SVs allow architects and stakeholders to quickly ascertain which functions are carried out by humans and which by Systems for each alternative specification and so carry out trade analysis based on risk, cost, reliability, etc.

To-Be SV-1a Refocused to be a model of system interfaces (SV-1a)

DoDAF v2.03 Release Plan 19

Next: Systems Engineering and Architecture Harmonization and Efficiency AV RD CBA System O & M DoDAF Viewpoints All (AV) Capabilities (CV) Operational (OV) Data / Information (DIV) Systems (SV) Services (SvcV) Standards (StdV) Validation & VAL Acquisition Model Decisions & Milestones CV MS-C TEMPcapabilities MSA System Validation CPD Capabilities Based Assessment (CBA) Material Solutions Analysis (MSA) Verification Technology Development (TD) MS-A OV DIV1 SVR JCIDS Documents Initial Capabilities Doc (ICD) Capabilities Design Doc (CDD) Capabilities Production Doc (CPD) Information Support Plan (ISP) ICD TEMPoperational Engineering & Manufacturing Development (E&MD) Prototyping System Verification REQM SRR VER SRD System Engineering Technical Reviews System Requirements Reviews (SRR) System Functional Reviews (SFR) Preliminary Design Reviews (PDR) Critical Design Reviews (CDR) Test Readiness Review (TRR) System Verification Review (SVR) SV SvcV DIV2 StdV TRR TEMPsystem SFR System Design Subsystem Verification Typical Systems Engineering Work Products System Requirements Document (SRD) / Technical Requirements Document (TRD) / System Segment Specification (SSS) System Design Document (SDD) / System Segment Design Document (SSDD) Software Requirements Specification (SwRS) Software Design Document (SwDD) Interface Requirements Specification (IRS) Interface Control Document (ICD) / Interface Design Document (IDD) Data Base Design Document (DBDD) Test and Evaluation Master Plan (TEMP) SDD CDDprelim; ISPprelim MS-B SV SvcV DIV2 StdV Component Design Component Verification PDR CDDfinal; ISPfinal SwRS; IRS CMMI Process Areas Requirements Development (RD) Requirements Management (REQM Technical Solution (TS) Product Integration (PI) Verification (VER) Validation (VAL) CDR DIV3 SwDD; IDD; DBDD TS PI Build Unit Test Notional Systems Development “V”

Questions? 21