DoDAF 2.0 Data Model
Conceptual Data Model Version 0.1
Tool Vendor Day
28 March 2008
1
Outline
 DoDAF 2.0 Data Model Development Process
 International Defence Enterprise Architecture Specification
(IDEAS) Relevance to DoDAF 2.0 Data Model
 Overview of Conceptual Data Model version 0.1
Top-Down / Bottom-Up Development
DoD Core Process Information Requirements Collection
UCORE
COI1
COI
Coordination
JCIDS Process
Information
Requirements
Ops Planning
Process
Information
Requirements
SE Process
Information
Requirements
PPBE Process
Information
Requirements
DAS Process
Information
Requirements
CPfm Process
Information
Requirements
DoDAF 2.0:
 Conceptual Data
Model (Vol I)
Data Model
Development
COIn
Existing / Emerging Schema, Models, and Databases
 Logical Data
Model (Vol II)
 Physical
Exchange Model
(Vol III)
Models

VOLUME I, DoDAF Conceptual Data Model (CDM)
– Core concepts, definitions (with examples, sources, aliases)
– Relationships (with some typing)

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.
Conceptual Data Model Version 0.1 Process
1. Overviews of Models
3. Make a pass on the
“Core” Terms
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
4
3
2
1
5. Group
related terms
4. Gather authoritative
definitions for “Core” terms
6. Proposed
definitions
(+rationale,
examples,
and aliases)
7. Relationships
8. Relationship Types
Ontology
Relationship
Types
Meronymic
Influence
Dependency
Case
Temporal
Spatial
12/3
Strawman – list of
important or recurring
“core”
words/terms/concepts
with source definition(s)
1/3
Partial Draft –
2/3
Interim Draft – Initial
3/3
CDM version 0.1
proposed definitions, some
harmonization (e.g., via
super/subtyping,
determining aliases)
relationships (e.g.,
"performs", "part-of",
...)
1. Concepts (defined)
2. Relationships (some
typing, e.g., super/sub,
cardinality)
Classification
Sources
a.
b.
c.
d.
e.
f.
g.
h.
i.
j.
k.
l.
m.
n.
o.
p.
q.
r.
s.
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
1.
2.
3.
4.
5.
6.
7.
8.
IEEE
ISO
W3C
OMG
EIA
DODD & DODI
JCS Pubs, especially CJCSI's
Models in the
Source_Candidates_071115.p
pt
9. DoDAF
10. Other frameworks: Zachman,
MODAF, TOGAF, NAF, ...
11. FEA
12. BMM
13. Worknet
14. Wikipedia
15. English dictionaries
16. DoDAF Glossary
Definition Phase Example 1
Category
Capability
Technical Term
Capability
Proposed
Definition
Capability: (n) 1. The ability to execute a specified course of action. (JP 1-02) 2. The ability to achieve a
desired effect under specified standards and conditions through combinations of means and ways to perform
a set of tasks. (JCIDS)
Potentially
Related
Terms or
Aliases
Source/Current
Definition
(source)
definition
(JCIDS): The ability to achieve a desired effect under specified standards and conditions through
combinations of means and ways to perform a set of tasks.
(DoDAF/CADM): An ability to achieve an objective. (DDDS Counter (333/1)(A))
(JC3IEDM): The potential ability to do work, perform a function or mission, achieve an objective, or provide
a service.
(NAF): The ability of one or more resources to deliver a specified type of effect or a specified course of
action. (GEN TERM)
(NAF): A high level specification of the enterprise's ability. (MM)
(JCS 1-02): The ability to execute a specified course of action. (A capability may or may not be
accompanied by an intention.)
(Webster's): 1. The quality of being capable; ability. 2. A talent or ability that has potential for development
or use. 3. The capacity to be used, treated, or developed for a specific purpose.
Examples
"The soldier shall be able to load and fire his individual weapon." (JP 1-02) "The soldier shall be able to load
and fire his individual weapon from (positions) on a trainfire range, in (weather) to achieve a minimum score
of "Marksman" on the Army Marksm
Definition
Rationale
Authority: "The Secretary of Defense, by DOD Directive 5025.12, 23 August 1989, Standardization of Military
and Associated Terminology, has directed the use of JP 1-02 throughout the Department of Defense to
ensure standardization of military and associated terminology.
Leveraging the IDEAS Project

IDEAS is “different” from traditional CADM modeling:
– 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 realworld 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
US and UK are coordinating the employment of IDEAS for DoDAF 2.0 Data
Model and UK MODEM (successor to M3)
IDEAS Foundation Top Level

Everything’s a
Thing:
– Individuals that
have spatiotemporal extent
– Types that are
sets of Things
– Tuples that
relate Things in
a specified
manner
(tuplePlaces)
http://en.wikipedia.org/wiki/IDEAS_Group
Foundation: Key Objects in the
Common Patterns for DoDAF 2.0
class IDEAS Foundation Key Obj ects
 Can be thought of as the
way to say set
membership, i.e., aÎ{A}
 A special type of
membership where a set
is an element of a some
other set (or class, to be
more precise), e.g.,
Key Foundation Objects
A diagram summarising the key objects and patterns in the IDEAS Foundation
«Type»
Thing
 one tuplePlace points to
the element
tuplePlace1 tuplePlace2 tuplePlace3 tuplePlace4 tuplePlace5
«superSubtype»
«place1Type» «place2Type» «place3Type» «place4Type» «place5Type»
 the other tuplePlace
points to the set
«TupleType»
tuple
instance
«superSubtype»
«place2Type»
«superSubtype»
– The set of
Government workers
is an element of the
set of worker types
«superSubtype»
«TupleType»
couple
«superSubtype»
«Type»
Type
«TupleType»
typeInstance
type
«place1Type»
 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)
«superSubtype»
«superSubtype»
«TupleType»
pow ertypeInstance
powertype
«place2Type»
supertype
«place1Type»
«superSubtype»
«TupleType»
superSubType
subtype
«place2Type»
part
«Type»
Indiv idual
«place2Type»
whole
«place1Type»
«TupleType»
w holePart
 Means the 4D spatiotemporal extent of the
Part is contained within
the 4D spatio-temporal
extent of the Whole
Sample EA Domain Patterns:
Specialize from the Foundation
class Information Element Whole-Part
class OV-2
Information Element Whole-Part
OV-2 Operational Node
AgentRole is a state of an agent when the agent is performing one or more tasks. In military architectures, there are often
operational nodes, which represent states of agents that perform operational activities.
«Type»
IDEAS Foundation::Indiv idual
«powertypeInstance»
...
«Type»
Pow er Types Lev els::Indiv idualType
part
«TupleType»
IDEAS Foundation::w holePart
«superSubtype»
«NameType»
Name Space Extensions::M3Names
«Type»
Agent::AgentState
«place2Type»
whole
«place1Type»
«superSubtype»
«superSubtype»
«nameTypeInstance»
«superSubtype»
«Name»
M3Node
«Type»
OperationalNodeType
«superSubtype»
«namedBy»
«superSubtype»
«Type»
OperationalNodeInstance
«Type»
InformationElementState
«superSubtype»
«Type»
Agent::AgentRole
«Type»
IDEAS Foundation::
Indiv idual
«powertypeInstance»
tags
exemplarText = Node
«Name»
DoDAFOpNode
«namedBy»
tags
exemplarText = Operational Node
«nameTypeInstance»
«NameType»
Name Space Extensions::DoDAFNames
«TupleType»
informationElementWholePart
whole
«place1Type»
«superSubtype»
«TupleType»
InformationElementWholeAndPart
part
«place2Type»
«Type»
InformationElement
«Type»
Foundation::Thing
tuplePlace1
tuplePlace2
tuplePlace3
tuplePlace4tuplePlace5
«place1Type»
«place2Type»
«place3Type»
«place4Type»
«place5Type»
«superSubtype»
«superSubtype»
«superSubtype»
«TupleType»
Foundation::tuple
«superSubtype»
«Type»
Foundation::Type
«Type»
Foundation::
Indiv idual
«TupleType»
Foundation::couple
0..*
«superSubtype»
0..*
«TupleType»
Foundation::superSubType
«superSubtype»
«place1Type» supertype
«place2Type»
subtype
0..*
whole
«TupleType»
Foundation::w holePart
0..*
«place1Type»
part
«place2Type»
«superSubtype»
«TupleType»
CommonPatterns::ov erlapPart
Measure
«superSubtype»
AbstractFeature
GeoFeature
Rule
Vision
Capability
0..*
CommonPatterns::InterfaceType
0..*
before
0..*
CommonPatterns::TemporalType
CommonPatterns::
Interface
«TupleType»
CommonPatterns::beforeAfter
0..*
«place1Type»
after
«place2Type»
Activ ity
FunctionalDependency
ExchangeObj ect
RealProperty
Skill
Ev ent
AbstractTimeGeometricPrimitive
UCORE Temporal::TimePeriod
PerformerState
Proj ect
Plan
CapabilityConfiguration
Condition
Netw ork
AbstractTimeGeometricPrimitive
Performer
Goal
Effect
Obj ectiv e
UCORE Temporal::TimeInstant
IDEAS
Foundation
Linkage to
DoDAF
Domain
Sample Views
couple
Thing
«TupleType»
Foundation::
superSubType
0..*
«Type»
Foundation::Type
0..*
0..*
couple
«TupleType»
Foundation::
w holePart
0..*
couple
0..*
0..*
«TupleType»
CommonPatterns::
beforeAfter
CommonPatterns::TemporalType
Baseline::Task
InterfaceType
applies-to
0..*
Capabilities
and Metrics
0..*
Baseline::Activ ity
Baseline::RealProperty
Performer
0..*
Baseline::Organization
Performer
is-a-part-of
0..*
Baseline::
PersonType(Personnel)
Baseline::Skill
0..*
is-a-part-of
is-a-part-of
0..*
ExchangeObject
is-a-part-of
Baseline::Materiel
is-a-part-of
0..*
is-a-part-of
results-in
Baseline::CapabilityConfiguration
realizes
is-performedunder
1..*
Baseline::Condition
Baseline::Capability
0..*
is-part-of
0..*
Baseline::Measure
1..*
Baseline::
Timeliness
Baseline::
Accuracy
Baseline::
Dependability
Baseline::Rate
Baseline::
Capacity
Name:
Author:
Version:
Created:
Updated:
Baseline::Effect
CapabilitiesMetrics
1.0
2/26/2008 1:29:55 PM
3/2/2008 9:23:23 AM
couple
«TupleType»
Foundation::
w holePart
0..*
Thing
«Type»
Foundation::Type
0..*
0..*
couple
«TupleType»
Foundation::
superSubType
0..*
0..*
CommonPatterns::TemporalType
0..*
couple
Vision
«TupleType»
CommonPatterns::
beforeAfter
0..*
is-realized-by
Goal
1..*
0..*
isrealizedby
is-part-of
1..*
Obj ectiv e
Proj ect
Rule
0..*
Means
directs
directs
Measure
Cost
Plan
0..*
Name:
Author:
Version:
Created:
Updated:
Project
guyc
1.0
2/1/2008 11:30:31 AM
3/2/2008 3:33:26 PM
InterfaceType
Activ ity
initiatesstimulates
1..*
Ev ent
Condition
state-change
0..*
Trigger
0..*
Project
couple
0..*
«TupleType»
Foundation::
superSubType
Thing
couple
0..*
«TupleType»
Foundation::
w holePart
«Type»
Foundation::Type
0..*
0..*
couple
«TupleType»
CommonPatterns::
beforeAfter
0..*
0..*
overlapPart
CommonPatterns::
InterfaceType
CommonPatterns::TemporalType
0..*
0..*
CommonPatterns::
Interface
Goals
Name:
Author:
Version:
Created:
Updated:
Rule
0..*
Vision
Goals
1.0
3/1/2008 12:42:50 PM
3/2/2008 3:01:04 PM
constrains
0..*
is-realized-by
0..*
directs
Goal
0..*
0..*
results-in
0..*
0..*
Activ ity
0..*
0..*
initiates-stimulates
Effect
0..*
seeksChangeTo
directs
1..*
changes
Ev ent
is-part-of
1..*
PerformerState
1..*
1..*
seeksChangeTo
1..*
0..*
0..*
Obj ectiv e
class Process
couple
«TupleType»
Foundation::superSubType
couple
«TupleType»
CommonPatterns::
beforeAfter
Baseline::
Measure
Thing
0..*
0..*
0..*
couple
«Type»
0..*
Foundation::Type
0..*
0..* CommonPatterns::
TemporalType
«TupleType»
Foundation::w holePart
Name:
Author:
Version:
Created:
Updated:
Process
guyc
1.0
2/1/2008 11:29:35 AM
3/2/2008 9:44:19 AM
InterfaceType
appliesto
0..*
0..*
Baseline::Activ ity
initiatesstimulates
1..*
Baseline::Ev ent
Baseline::
FunctionalDependency
Baseline::Condition
Activity
class Performer
0..*
couple
«TupleType»
Foundation::
superSubType
Thing
«Type»
Foundation::Type
0..*
0..*
0..*
couple
«TupleType»
Foundation::
w holePart
0..*
0..*
couple
0..*
CommonPatterns::
TemporalType
overlapPart
CommonPatterns::
Interface
CommonPatterns::
InterfaceType
0..*
«TupleType»
CommonPatterns::
beforeAfter
PerformerState
Name:
Author:
Version:
Created:
Updated:
Performer
2..*
Performer
1.0
2/1/2008 11:21:58 AM
3/2/2008 3:23:19 PM
0..*
performs
according-to
Performers
is-performedby
is-part-of
Serv ice
1..*
System
Activ ity
Rule
Standard
Netw ork
Organization
Softw areServ ice
ExchangeObject
Materiel
PersonType(Personnel)
is-a-partof
Skill
(inc Systems,
Services, and
Applications)
couple
«TupleType»
Foundation::
superSubType
Name:
Author:
Version:
Created:
Updated:
0..*
couple
0..*
Thing
0..*
«TupleType»
Foundation::
w holePart
«Type»
0..*
Foundation::Type
Systems
Baseline::
Measure
CommonPatterns::
TemporalType
«TupleType»
CommonPatterns::
beforeAfter
0..*
Baseline::Activ ity
0..*
1..*
Baseline::
Condition
Systems,
Services,
and
Applications
InterfaceType
applies-to
0..*
couple
0..*
1.0
2/26/2008 1:33:13 PM
3/2/2008 9:44:17 AM
initiatesstimulates
according-to
is-performed-by
performs
1..*
Baseline::
FunctionalDependency
0..*
Baseline::Ev ent
Rule
PerformerState
Baseline::Performer
Baseline::System
Baseline::Serv ice
Baseline::
Softw areServ ice
ExchangeObject
Baseline::Materiel
Baseline::
Standard
couple
0..*
«TupleType»
Foundation::
superSubType
0..*
overlapPart
0..*
CommonPatterns::
Interface
couple
Thing 0..*
«Type»
Foundation::Type
«TupleType»
Foundation::
w holePart
0..*
0..*
CommonPatterns::
InterfaceType
CommonPatterns::
TemporalType
0..*
0..*
couple
«TupleType»
CommonPatterns::
beforeAfter
Baseline::Activ ity
Interfaces
1..*
is-performedby
performs
0..*
PerformerState
Baseline::Performer
Rule
according-to
Baseline::Standard
Baseline::System
Baseline::Serv ice
Baseline::Softw areServ ice
Baseline::
PersonType(Personnel)
Name:
Author:
Version:
Created:
Updated:
Interfaces
1.0
2/26/2008 1:34:12 PM
3/2/2008 9:44:16 AM
class ExhangeObj ectFlow
couple
0..*
«TupleType»
Foundation::
superSubType
overlapPart
CommonPatterns::
Interface
«Type»
Foundation::Type
0..*
0..*
couple
Thing 0..*
«TupleType»
Foundation::
w holePart
0..*
couple
0..*
CommonPatterns::
TemporalType
CommonPatterns::
InterfaceType
0..*
0..*
«TupleType»
CommonPatterns::
beforeAfter
Baseline::Activ ity
1..*
is-performedby
0..*
performs
is-consumedby
0..*
0..*
0..*
is-producedby
Name:
Author:
Version:
Created:
Updated:
ExhangeObjectFlow
1.0
2/1/2008 11:21:15 AM
3/2/2008 9:44:23 AM
0..*
PerformerState
Baseline::ExchangeObj ect
Baseline::Performer
according-to
Baseline::Materiel
Rule
Baseline::Standard
Baseline::Data
is-a-partof
Baseline::Information
Exchange
Object
Flow
class Infrastructure
couple
«TupleType»
Foundation::
superSubType
0..*
couple
Thing
0..*
«TupleType»
Foundation::
w holePart
«Type»
Foundation::Type
0..*
0..*
0..*
couple
«TupleType»
CommonPatterns::
beforeAfter
0..*
CommonPatterns::
TemporalType
0..*
overlapPart
CommonPatterns::
InterfaceType
CommonPatterns::
Interface
0..*
Baseline::Netw ork
Baseline::
Measure
applies-to
0..*
Infrastructure
Baseline::Activ ity
0..*
1..*
according-to
is-part-of
is-performed-by
Baseline::
Condition
Baseline::
FunctionalDependency
performs
2..*
0..*
Rule
PerformerState
Baseline::Performer
Baseline::System
Baseline::Serv ice
Name:
Author:
Version:
Created:
Updated:
Infrastructure
1.0
2/26/2008 1:34:23 PM
3/2/2008 9:44:20 AM
Baseline::
Softw areServ ice
ExchangeObject
Baseline::Materiel
Baseline::
Standard
class Rule
couple
«TupleType»
Foundation::
w holePart
Name:
Author:
Version:
Created:
Updated:
0..*
0..*
Thing
«Type»
Foundation::Type
couple
0..*
«TupleType»
Foundation::
superSubType
0..*
TemporalType
Rule
Condition
1.0
2/1/2008 11:21:30 AM
3/2/2008 3:26:53 PM
0..*
is-validunder
1..*
Rule
Rule
Agreement
Means
Standard
Guidance
Constraint
UCORE IC-ISM-v 2::
SecurityAttributesGroup
FunctionalStandard
TechnicalStandard
Standards
class Standards
couple
0..*
«TupleType»
Foundation::
w holePart
0..*
InterfaceType
TemporalType
Baseline::Activ ity
0..*
Thing
«Type»
Foundation::Type
0..*
«TupleType»
Foundation::
superSubType
0..*
Name:
Author:
Version:
Created:
Updated:
constrains
0..*
couple
Baseline::Rule
Standards
1.0
2/26/2008 1:34:37 PM
3/2/2008 9:44:14 AM
1..*
is-performed-by
according-to
performs
Baseline::
Standard
0..*
PerformerState
Baseline::Performer
Baseline::
TechnicalStandard
Baseline::
FunctionalStandard
Next
 Refinement and completion
 Coordination and feedback from other TWG’s
 Spiral II Comments
 Attributes
 Trace to Core Process requirements