1. Joint Mission Thread (JMT) DoDAF Meta-Model (DM2) Mapping and Measures Use Case
Dr. David Dryer
Mr. Johnny Yohman
JFCOM J84

2. JMT DM2 Key Data Groups/Relationships
DRAFT
JMT DM2 Key Data Groups/Relationships
DRAFT

3. IDEAS Foundation Category Legend
DM2 Definition: The PowerType of Individual.
SA examples- BPM:Operational Activity
IDEF:ICOM Arrow:Mechanism
DM2 Definition: The TupleType that is the PowerType of Couple.
SA examples- BPM:Association
BPM:Sequence Flow
Not Defined in DM2
SAExamples- IDEF:ICOM Arrow (with conditions)
IndividualType
CoupleType
TripleType

4. Enterprise Architect (EA) to DM2 Mapping
EA->DM2 Mappings for JMT OV-5b
DM2 JMT Data Objects
DM2 JMT Data Type
Activity
uml:InterruptibleActivityRegion
Activity (2)
uml:Activity
Activity (3)
uml:StateNode
Activity (4)
uml:Synchronization
Activity (5)
uml:Decision
BeforeAfterType
ControlFlow
EA->DM2 Mappings for JMT OV-2
OrganizationType
uml:Class:OperationalNode
Activity
uml:Activity
activityPerformedByPerformer
uml:Activity, uml:Class:OperationalNode
ActivityResourceOverlap
uml:activity, uml:Class:Information
EA->DM2 Mappings for JMT OV-6c
DM2 JMT Data Objects
DM2 JMT Data Type
Performer
uml:Class:OperationalNode
Activity
Sequence*
activityResoureOverlap
activityPerformedByPerformer
Sequence*, uml:Class:OperationalNode
BeforeAfterType
Information
uml:Class:InformationElement
EA->DM2 Mappings for JMT SV-1
DM2 JMT Data Objects
DM2 JMT Data Type
System
uml:Class:SystemsNode
Activity
uml:Activity:SystemFunction
activityPerformedByPerformer
uml:Activity:SystemFunction, uml:Class:SystemsNode
activityResourceOverlap
uml:
OrganizationType
uml:Class:OperationalNode
WholePartType
uml:Class:OperationalNode, uml:Activity:SystemFunction
*Generated information pertaining to Sequence element, but not present in EA XML structure

5. EA JMT Element Type Naming Convention
Elements
xmi:type:stereotype
Connectors
ea_type:stereotype
Stereotype only included when needed for distinction
OV-5b Activity = uml:Activity
OV-2 Performer = uml:Class:OperationalNode
SV-1 System = uml:Class:SystemsNode

6. Visense XML Translator
EA – DM2 JMT Translation Process
EA XMI Data
EA Project
EA XMI Export
Visense XML Translator
DM2 XML Data

7. DM-2 Translation Service Implementation
EA XML Schema
Visense Translation Web Service
uml:OperationalActivity
Visense XML Packet Streaming Algorithm
DM2:Activity
Visense XML Packet Streaming Algorithm
SA XML Schema
IDEF:Operational Activity
Visense XML Packet Streaming Algorithm
DM2 PES Schema

8. Activity
BeforeAfterType
OV-5b

9. Most EA OV-5b elements get mapped to activity in DM2, including
EA OV-5b to DM2 Mapping
Most EA OV-5b elements get mapped to activity in DM2, including
uml:Activity
uml:Synchronization
uml:Decision
uml:InterruptibleActivityRegion
uml:StateNode
ControlFlow connections mapped to BeforeAfterType

10. SA Business Process Model (BPM)

11. SA BPM to DM2 Mapping Data Object Process Event Gateway Association
BPM Elements
DM2 Elements
Data Object
Process
Event
Gateway
Association
Sequence Flow
Data
Activity
CoupleType
BeforeAfterType
Mapped To

12. OrganizationType Information Activity OV-2 activityResourceOverlap
activityPerformedByPerformer
Activity
OV-2

13. EA connector, relationship mappings
EA OV-2 to DM2 Mapping
EA element mappings
uml:Class:OperationalNode->OrganizationType
uml:Activity->Activity
EA connector, relationship mappings
activityPerformedByPerformer
activityResourceOverlap

14. Integration Definition for Function Modeling (IDEF0)

15. System Architect (SA) IDEF0 to DM2 Mapping
IDEF0 Elements
DM2 Elements
ICOM Arrow:Control
ICOM Arrow*
ICOM Arrow:Mechanism
Operational Activity
ICOM Arrow
Sequence Flow
Information
Performer
Activity
ActivityResourceOverlap
Mapped To

16. OrganizationType Activity OV-6c activityPerformedByPerformer
activityResourceOverlap
BeforeAfterType
OV-6c

17. EA elements mapped directly from EA XMI:
EA OV-6c to DM2 Mapping
EA elements mapped directly from EA XMI:
uml:Class:OperationalNode to DM2 OrganizationType
uml:Class:Information mapped to DM2 Information
EA elements mapped based on implications in diagram (based on sequence connectors):
Activity, activityResourceOverlap, BeforeAfterType, ActivityPerformedByPerformer

18. System OrganizationType Information Activity SV-1
activityPerformedByPerformer
OrganizationType
Information
activityResourceOverlap
Activity
WholePartType
SV-1

19. EA connector, relationship mappings
EA SV-1 to DM2 Mapping
EA element mappings
uml:Class:SystemsNode=>System
uml:Activity:SystemFunction=>Activity
uml:Class:OperationalNode=>OrganizationType
uml:Class:DataElement=>Data
EA connector, relationship mappings
System OrganizatonType with WholePartType
activityPerformedByPerformer
activityResourceOverlap

20. JMT DM2 Mapping Feedback
‘Activity’ data element in DM2 accommodates a broad range of UML structures
uml:Decision, uml:Synchronization, etc as seen in OV-5b
ActivityType data element introduced for distinction between UML structures
Extensive of Type class to type other classes (e.g.,
Typing various CoupleType relationships
Typing ArchitectureDescriptions

21. Dr. David Dryer Mr. Johnny Yohman Mr. Walter Pierce
Measures Use Case
Dr. David Dryer
Mr. Johnny Yohman
Mr. Walter Pierce

22. Key
Input Elements
Output Elements
Element Already There
Relationships

23. Evaluation View Inputs
Key NECM Client
Evaluation View Inputs
Activity
Activity:Ospec
(Op Event)
Performer (Op Node)
Information
MeasureOf
Desire
Condition
System Function
Activity:Ospec
(Sys/Service event)
joint
threat
environment
System
Data

24. NECM DM2 Native Activity (OV-5b to 6c) Traceability Check1
activityPerformableUnderCondition
Condition
Start/End BoundaryType
activityPerformableUnderConditionc
Activity:OSpec 2

25. NECM DM2 Measure Composition
namedBy
typeInstance
OverlapType
CoupleType
Name
MeasureType
Rule
MeasureOf
Desire
superSubType
OverlapType
DM2 Object Values
MeasureType
(scale)
DM2 Object Values
DM2 Object Content

26. NECM DM2 Evaluation View (OV-5b to Measures) Traceability Check
Condition
Activity 3
activityPerformableUnderCondition
MeasureOf Desire
MeasureType
CoupleType
measureOfType
activityPerformableUnderCondition
superSubType
Performance
Measure
typeInstance
MeasureType
(scale)

27. JMT DM2 Measures Pipeline
MeasureOf Effect
Activity
Temporal Measure
(Mission Level)
Activity:
OSpec
Spatial Measure
Performance Measure
Rule (calculation)
(Task Level)
Condition
Performance Measure
joint
threat
environment
(Function Level)
Information
Rule (math/logic operator)
Rule (math/logic operator)
Rule (math/logic operator)
Data
Information Content
MeasureOf Desire
Data Content

28. NECM DM2 Performance Measure Example
(SN M1: Operational Timeliness)
Activity : OpActivity1
Start BoundaryType
Activity: OSpec1
Temporal Measure
(event time)
OverlapType
activityPerformableUnderCondition
measureOfType Condition
Performance Measure
Condition
OverlapType
Rule
CoupleType
activityPerformableUnderCondition
measureOfType Condition
End BoundaryType
Activity: OSpec2
Temporal Measure
(event time)
MeasureOf
Desire
Activity: OpActivity2

29. OV-5b Example Start Time: ti tf - ti End Time: tf
Activity: OSpec1
Start Time: ti
Start BoundaryType
Temporal Measure
Activity
Performable
UnderCondition
measureOfTypeCondition
OverlapType
OverlapType
tf - ti
Condition
Rule
Performance Measure
Activity
Performable
UnderCondition
measureOfTypeCondition
OverlapType
Temporal Measure
End BoundaryType
End Time: tf
*assuming all 4 Activities are PerformableUnderCondition
Activity: OSpec4

30. JMT DM2 Measures Mapping Feedback
Direct association between Activity (or activityType) and Measure, so not necessary to go through the Condition just to get to the measure.
Measure unit (scale) as a Rule, not MeasureType
More specific measure associations? Currently using:
Generic OverlapType to go from the TemporalMeasure to Rule (to be able to perform the duration calculation)
Rule to the PerformanceMeasure (the actual calculation)
Actual measure PerformanceMeasure relating to MeasureOfDesire with a generic CoupleType

31. Requirement of DM2 compliance has influenced J8 JMT modeling process
Influence of DM2
Requirement of DM2 compliance has influenced J8 JMT modeling process
No “PRO” relationship (PerformerResourceOverlap)
Impact: Activities from OV-5b mapped into OV-2
System Functions (Activities in DM2)included in SV-1