International Defence Enterprise Architecture Specification (IDEAS) and DoDAF 2.0 Data Model

1. OMG Systems Engineering Domain Special Interest Group (SE DSIG) Mr. David McDaniel Silver Bullet Solutions, Inc. under contract to OASD (NII) / DoD CIO 11 March 2008 International Defence Enterprise Architecture Specification (IDEAS)andDoDAF 2.0 Data Model

2. Outline DoDAF 2.0 Data Model Development Process IDEAS Role Overview of Conceptual Data Model version 0.1

3. Top-Down / Bottom-Up Development DoD Core Process Information Requirements Collection JCIDS Process Information Requirements PPBE Process Information Requirements Ops Planning Process Information Requirements DAS Process Information Requirements CPfm Process Information Requirements SE Process Information Requirements DoDAF 2.0: • Conceptual Data Model (Vol I) • Logical Data Model (Vol II) • Physical Exchange Model (Vol III) UCORE Data Model Development COI Coordination COI1 COIn Existing / Emerging Schema, Models, and Databases

4. 3. Make a pass on the “Core” Terms 5 4 3 2 1 1. Overviews of Models 2. Collect the terms 1 = Core, critical to process or very common in architectures 2 = Derived or less common 3 = TBD 4 = TBD 5 = TBD 5. Group related terms 4. Gather authoritative definitions for “Core” terms 7. Relationships 6. Proposed definitions (+rationale, examples, and aliases) 8. Relationship Types 12/3 Strawman – list of important or recurring “core” words/terms/concepts with source definition(s) 1/3 Partial Draft – proposed definitions, some harmonization (e.g., via super/subtyping, determining aliases) 2/3 Interim Draft – Initial relationships (e.g., "performs", "part-of", ...) • 3/3 • CDM version 0.1 • Concepts (defined) • Relationships (some typing, e.g., super/sub, cardinality)

5. Logical and Physical Exchange Models VOLUME II, DoDAF Logical Data Model (LDM) The DoDAF Logical Data Model (LDM) is the Conceptual Data Model described in Volume I with attributes, specializations, and association reifications added VOLUME III 1. DoDAF Physical Data Exchange Model Physical Data Exchange Model is the Logical Data Model with general data types specified and implementation attributes (e.g., source, date) added and then generated as a set of XSD’s, one schema per product/view type described in Volume II. The full model is also available on DARS for customized product/view, topics, or other needs. The DoDAF Physical Data Exchange Model (PDEM) is TBS.

6. Sources Models CADM 1.5 IDEAS UPDM BMM Hay/Zachman ASM CRIS Conceptual CADM in DoDAF 1.0 / prototype CADM 2.0 M3 NAF Meta Model DoI Meta Model JC3IEDM GML UCORE 1.1 GEIA 927 AP233 SUMO and ISO 15926 (via IDEAS) FEA Reference Models JFCOM JACAE Definitions IEEE ISO W3C OMG EIA DODD & DODI JCS Pubs, especially CJCSI's Models in the Source_Candidates_071115.ppt DoDAF Other frameworks: Zachman, MODAF, TOGAF, NAF, ... FEA BMM Worknet Wikipedia English dictionaries DoDAF Glossary

7. Definition Phase Example 1

8. International Defence Enterprise Architecture Specification (IDEAS) Relevance to DoDAF 2.0 Data Model

9. What Makes IDEAS Different ? Foundation Layers Foundation based on Set Theory Traditional data modelling is generally not founded in mathematic principles IDEAS uses formal set theoretic tools to accurately represent the structure of real-world concepts Next – common patterns based on the foundation Next – domain patterns that specialize the common patterns BORO Methodology Relies on the only thing that is irrefutable, the physical extent of something All analysis is rooted in 4D spatio-temporal “individuals” that are instances-of Types Naming Pattern Allows separation of linguistics from semantics

10. Foundation Top Level Everything’s a Thing: Individuals that have spatio-temporal extent Types that are sets of Things Tuples that relate Things in a specified manner (tuplePlaces)

11. Foundation: Key Objects in the Common Patterns for DoDAF 2.0 Means the 4D spatio-temporal extent of the Part is contained within the 4D spatio-temporal extent of the Whole • A special type of membership where a set is an element of a some other set (or class, to be more precise), e.g., • The set of Government workers is an element of the set of worker types • Can be thought of as the way to say set membership, i.e., aÎ{A} • one tuplePlace points to the element • the other tuplePlace points to the set • Can be thought of a subset, e.g., • F-18 (type) is a subset of the set of Fighter (type) is a subset of the set of Aircraft (type)

12. DoDAF 2.0 Conceptual Data Model version 0.1 Foundation and Sample Diagrams

13. Foundation Top-Level Foundation Elements: Thing, similar to other model’s “object” Individual, a “thing” that has spatio-temporal extent. Type, a set of individuals or classes of other sets or classes Tuple, ordered places of “things” Common (Reuse) Patterns: Composition (or whole-part) Super/Sub Type (or generalization / specialization) Before / After, for “things” that have temporal relationships in their Type Interface, for “things” that can exchange other things that are parts of themselves

14. Foundation Linkage to Domain

15. Capabilities and Metrics

16. Interfaces

17. Exchange Object Flow

18. Standards

19. Project

20. Next Refinement and completion Coordination and feedback from other TWG’s Spiral II Comments Attributes Trace to Core Process requirements

21. Backups

22. Sample EA Domain Patterns:Specialize from the Foundation

23. Rule

24. Activity

25. Performers (inc Systems, Services, and Applications)

26. Systems, Services, and Applications

27. Infrastructure

28. Goals