Joint Mission Thread (JMT)DoDAF Meta-Model (DM2)

Mapping and Measures Use Case

Dr. David DryerMr. Johnny Yohman

JFCOM J84dryerd@visense.net

757-966-5780

1

JMT DM2 Key Data Groups/Relationships

DRAFT

DRAFT

2

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

3

EA->DM2 Mappings for JMT OV-2OrganizationType uml:Class:OperationalNodeActivity uml:ActivityactivityPerformedByPerformer uml:Activity,

uml:Class:OperationalNodeActivityResourceOverlap uml:activity, uml:Class:Information

Enterprise Architect (EA) to DM2 MappingEA->DM2 Mappings for JMT OV-5b

DM2 JMT Data Objects DM2 JMT Data Type

Activityuml:InterruptibleActivityRegion

Activity (2) uml:ActivityActivity (3) uml:StateNodeActivity (4) uml:SynchronizationActivity (5) uml:DecisionBeforeAfterType ControlFlow

EA->DM2 Mappings for JMT OV-6cDM2 JMT Data Objects DM2 JMT Data TypePerformer uml:Class:OperationalNodeActivity Sequence*activityResoureOverlap Sequence*activityPerformedByPerformer Sequence*, uml:Class:OperationalNodeBeforeAfterType Sequence*Information uml:Class:InformationElement

EA->DM2 Mappings for JMT SV-1DM2 JMT Data Objects DM2 JMT Data TypeSystem uml:Class:SystemsNodeActivity uml:Activity:SystemFunctionactivityPerformedByPerformer uml:Activity:SystemFunction, uml:Class:SystemsNodeactivityResourceOverlap uml:OrganizationType uml:Class:OperationalNodeWholePartType uml:Class:OperationalNode, uml:Activity:SystemFunction

*Generated information pertaining to Sequence element, but not present in EA XML structure 4

• 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

EA JMT Element Type Naming Convention

5

Visense XML

Translator

EA XMI Export

EA Project

EA XMI Data

DM2 XML Data

EA – DM2 JMT Translation Process

6

DM-2 Translation Service Implementation EA XML Schema

SA XML Schema

Visense Translation Web Service

DM2 PES Schema

Visense XML Packet

Streaming Algorithm

Visense XML Packet

Streaming Algorithm

Visense

XML Packe

t

Streaming A

lgorit

hm

uml:OperationalActivity

IDEF:Operational A

ctivit

y

DM2:Activity

7

ActivityBeforeAfter

Type

OV-5b8

• 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

EA OV-5b to DM2 Mapping

9

SA Business Process Model (BPM)

10

SA BPM to DM2 Mapping

Data Object

Process

Event

Gateway

Association

Sequence Flow

Data

Activity

CoupleType

BeforeAfterType

BPM Elements DM2 Elements

Mapped To

11

OV-2

OrganizationType

Activity

Information

activityResourceOverlap

activityPerformedByPerformer

12

EA OV-2 to DM2 Mapping

• EA element mappings– uml:Class:OperationalNode->OrganizationType– uml:Activity->Activity

• EA connector, relationship mappings– activityPerformedByPerformer– activityResourceOverlap

13

Integration Definition for Function Modeling (IDEF0)

14

ICOM Arrow:Control

ICOM Arrow*

ICOM Arrow:Mechanism

Operational Activity

ICOM Arrow

Sequence Flow

Information

Performer

Activity

ActivityResourceOverlap

IDEF0 Elements DM2 Elements

System Architect (SA) IDEF0 to DM2 Mapping

Mapped To

15

Activity

activityResourceOverlap

OV-6c

OrganizationType

activityPerformedByPerformer

BeforeAfterType

16

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

17

SV-1

System

WholePartType

Activity

Information

OrganizationType

activityResourceOverlap

activityPerformedByPerformer

18

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

19

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

20

Dr. David DryerMr. Johnny Yohman

Mr. Walter Pierce

21

Measures Use Case

Input Elements

Relationships

Output Elements

Element Already There

22

Key

Activity Activity:Ospec(Op Event)

Condition

MeasureOfDesire

Data

Information

System

Performer (Op Node)

System Function

Activity:Ospec(Sys/Service event) •joint

•threat•environment

23

Key NECM Client Evaluation View Inputs

Activity

Condition

Activity:OSpec

activityPerformableUnderConditionc

1

2

activityPerformableUnderCondition

Start/End BoundaryType

24

NECM DM2 Native Activity (OV-5b to 6c) Traceability Check

DM2 Object Values

DM2 Object Values

Measure

Name

namedBy

MeasureType

typeInstance

Rule

OverlapType

OverlapType

CoupleType

MeasureOfDesire

DM2 Object Content

superSubType

MeasureType(scale)

25

NECM DM2 Measure Composition

Activity Condition

activityPerformableUnderCondition

PerformanceMeasure

measureOfTypeactivityPerformableUnderCondition

3

MeasureOf Desire

MeasureType

typeInstance

superSubType

MeasureType(scale)

CoupleType

26

NECM DM2 Evaluation View (OV-5b to Measures) Traceability Check

Rule (math/logic operator)Rule (math/logic

operator)

Activity

Activity:OSpec

Information

Data

Temporal Measure

Spatial Measure

Information Content

Data Content

Condition

Rule (calculation)

Rule (math/logic operator)

MeasureOf Desire

Performance Measure

(Task Level)

Performance Measure

(Function Level)

MeasureOf Effect

(Mission Level)

•joint•threat•environment

27

JMT DM2 Measures Pipeline

Activity: OSpec2

Activity: OSpec1

measureOfType Condition

measureOfType Condition

Temporal Measure (event time)

Temporal Measure (event time)

RuleOverlapType

OverlapType

Performance Measure

MeasureOfDesire

Condition

CoupleType

Activity: OpActivity2

Activity : OpActivity1

End BoundaryType

Start BoundaryType

activityPerformableUnderCondition

activityPerformableUnderCondition

28

NECM DM2 Performance Measure Example (SN 7.8.1 M1: Operational Timeliness)

Activity: OSpec1

Activity: OSpec4

ActivityPerformable

UnderCondition

Start BoundaryType

End BoundaryType

ActivityPerformable

UnderCondition

Condition

Temporal Measure

measureOfTypeCondition

measureOfTypeCondition

Temporal Measure

OverlapType

OverlapType

Rule

Performance Measure

OverlapType

Start Time: ti

End Time: tf

t f - t i

*assuming all 4 Activities are PerformableUnderCondition

29

OV-5b Example

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

30

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-2System Functions (Activities in DM2)included in SV-1

31