DoDAF Version 2.03 Update 05 Jan 2012 DoDAF Team 1 1

Outline CM Plan (CMP) Changes for 2.03 Formal coordination review plan Why DoDAF is under CM CMP Organizational Roles CMP Processes CMP Business Rules Changes for 2.03 Formal coordination review plan

DoDAF CM Improvements, error correction, emerging requirements Stability for governance developers, users, vendors 2.0 2.01 2.02 2.03 5/2009 2/2010 8/2010 8/2012

CMP Organizational Roles

CMP Processes

CMP Business Rules

DoDAF-DM2 WG Status: Change Request Status

Packaging for Formal CM CM Requiring Formal Coordination Associated DoDAF Conformance Level* Vol. I DM2 Conceptual Model Level 1 DoDAF Viewpoints & Models Vol. II DM2 Logical DM Level 2 DoDAF Model Specs DoDAF Glossary Vol. III DM2 Physical DM: PES Level 3 SparxEA .EAP DM2 Level 4 SparxEA .EAP IDEAS Foundation Moved to DoDAF Journal historical material tutorials architecture methods modeling methods presentation methods DoDAF best practices DoDAF examples DM2 applications DoD guidance DoD component guidance FAC guidance DoDAF procedures DoDAF DM2 procedures DoDAF DM2 WG procedures BORO materials IDEAS materials ontology methods DB schemas OWL file * See next slide

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 DM2 Description of Rules and Desired Effect Information resource flow Capability made a subtype of Property

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

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

TECHEDIT Example Name: One-Liner: Narrative: Diagram: Other names: Notes:

Criteria for an Architectural Description to be Conformant with DoDAF-DM2* Level 1 -- Conceptually conformant Level 2 -- Logically conformant Level 3 -- Physically conformant Level 4 -- Semantically conformant * Info brief at FAC Nov 2010 13

Criteria for an Architectural Description to be Conformant with DoDAF-DM2* Level 1 -- Conceptually conformant Uses DoDAF terms and aliases (from DM2 CDM) to categorize its concepts DoDAF views (AV-1 thru DIV-3) have correct information according to “monster matrix”).  For example: An OV-2 with radios would be non-conformant An OV-4 with Tank parts would be non-conformant Fit-For-Purpose (FFP) would have to be conformant with whatever the FFP model creator(s) specified, e.g., a “xV-1" view for which the creator(s) specified the model as Services mapping to Capabilities should have Services and Capabilities and the relationship but shouldn't have unrelated info 14

Criteria for an Architectural Description to be Conformant with DoDAF-DM2* Level 2 -- Logically conformant Level 1 + adheres to terms and relationships from DM2 LDM and aliases Level 3 -- Physically conformant Level 2 + expressed as DoDAF – DM2 PES that can be consumed by others Level 4 -- Semantically conformant Level 3 + IDEAS semantics are correct * Info brief at FAC Nov 2010 15

DoDAF v2.03 Release Plan

Questions?