Joint Mission Thread JMT Do DAF MetaModel DM

Joint Mission Thread (JMT) Do. DAF Meta-Model (DM 2) Mapping and Measures Use Case Dr. David Dryer Mr. Johnny Yohman JFCOM J 84 dryerd@visense. net 757 -966 -5780 1

DRAFT JMT DM 2 Key Data Groups/Relationships DRAFT 2

IDEAS Foundation Category Legend • Individual. Type DM 2 Definition: The Power. Type of Individual. • SA examples- BPM: Operational Activity IDEF: ICOM Arrow: Mechanism Couple. Type DM 2 Definition: The Tuple. Type that is the Power. Type of Couple. • SA examples- BPM: Association BPM: Sequence Flow Triple. Type Not Defined in DM 2 • SAExamples- IDEF: ICOM Arrow (with conditions) 3

Enterprise Architect (EA) to DM 2 Mapping EA->DM 2 Mappings for JMT OV-2 Organization. Type uml: Class: Operational. Node Activity uml: Activity activity. Performed. By. Performer uml: Activity, uml: Class: Operational. Node Activity. Resource. Overlap uml: activity, uml: Class: Information EA->DM 2 Mappings for JMT OV-5 b DM 2 JMT Data Objects DM 2 JMT Data Type Activity uml: Interruptible. Activity. Region Activity (2) uml: Activity (3) uml: State. Node Activity (4) uml: Synchronization Activity (5) uml: Decision Before. After. Type Control. Flow EA->DM 2 Mappings for JMT OV-6 c DM 2 JMT Data Objects DM 2 JMT Data Type Performer uml: Class: Operational. Node Activity Sequence* activity. Resoure. Overlap Sequence* activity. Performed. By. Performer Sequence*, uml: Class: Operational. Node Before. After. Type Sequence* Information uml: Class: Information. Element EA->DM 2 Mappings for JMT SV-1 DM 2 JMT Data Objects DM 2 JMT Data Type System uml: Class: Systems. Node Activity uml: Activity: System. Function activity. Performed. By. Performer uml: Activity: System. Function, uml: Class: Systems. Node activity. Resource. Overlap uml: Organization. Type uml: Class: Operational. Node Whole. Part. Type uml: Class: Operational. Node, uml: Activity: System. Function *Generated information pertaining to Sequence element, but not present in EA XML structure 4

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

EA – DM 2 JMT Translation Process EA XMI Data EA Project EA XM po I Ex rt Vis e Tra nse nsl XM ato L r DM 2 XML Data 6

DM-2 Translation Service Implementation EA XML Schema Visense Translation Web Service um l: O pe rat ion al. A cti Vi vit Str sense y ea X mi ML ng Alg Pack ori et thm DM vit Vis y e Str nse ea mi XML ng Alg Pack ori et thm Vi ID EF : O pe r SA XML Schema at io s na St en re s l. A am e X ct ivi in M g. A LP ty lgo ac rit ket hm 2: A cti DM 2 PES Schema 7

Activity Before. After Type OV-5 b 8

EA OV-5 b to DM 2 Mapping • Most EA OV-5 b elements get mapped to activity in DM 2, including – uml: Activity – uml: Synchronization – uml: Decision – uml: Interruptible. Activity. Region – uml: State. Node • Control. Flow connections mapped to Before. After. Type 9

SA Business Process Model (BPM) 10

SA BPM to DM 2 Mapping BPM Elements DM 2 Elements Data Object Data Process Activity Event Gateway Mapped To Association Couple. Type Sequence Flow Before. After. Type 11

Organization Type Information activity. Resource Overlap activity. Performed By. Performer Activity OV-212

EA OV-2 to DM 2 Mapping • EA element mappings – uml: Class: Operational. Node->Organization. Type – uml: Activity->Activity • EA connector, relationship mappings – activity. Performed. By. Performer – activity. Resource. Overlap 13

Integration Definition for Function Modeling (IDEF 0) 14

System Architect (SA) IDEF 0 to DM 2 Mapping IDEF 0 Elements ICOM Arrow: Control ICOM Arrow* DM 2 Elements Information Mapped To ICOM Arrow: Mechanism Performer Operational Activity ICOM Arrow Activity. Resource. Overlap Sequence Flow 15

activity. Performed By. Performer Organization Type Activity activity. Resource Overlap Before. After. Type OV-6 c 16

EA OV-6 c to DM 2 Mapping • EA elements mapped directly from EA XMI: – uml: Class: Operational. Node to DM 2 Organization. Type – uml: Class: Information mapped to DM 2 Information • EA elements mapped based on implications in diagram (based on sequence connectors): – Activity, activity. Resource. Overlap, Before. After. Type, Activity. Performed. By. Performer 17

System activity. Performed By. Performer Organization Type activity. Resource Overlap Information Activity Whole. Part. Type SV-118

EA SV-1 to DM 2 Mapping • EA element mappings – uml: Class: Systems. Node=>System – uml: Activity: System. Function=>Activity – uml: Class: Operational. Node=>Organization. Type – uml: Class: Data. Element=>Data • EA connector, relationship mappings – System Organizaton. Type with Whole. Part. Type – activity. Performed. By. Performer – activity. Resource. Overlap 19

JMT DM 2 Mapping Feedback • ‘Activity’ data element in DM 2 accommodates a broad range of UML structures – uml: Decision, uml: Synchronization, etc as seen in OV 5 b • Activity. Type data element introduced for distinction between UML structures • Extensive of Type class to type other classes (e. g. , – Typing various Couple. Type relationships – Typing Architecture. Descriptions 20

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

Key Input Elements Output Elements Element Already There Relationships 22

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

NECM DM 2 Native Activity (OV-5 b to 6 c) Traceability Check Activity 1 activity. Performable Under. Condition Start/End Boundary. Type activity. Performable Under. Conditionc Activity: OSpec 2 24

NECM DM 2 Measure Composition Measure named. By type. Instance Name Overlap. Type Couple. Type Measure. Type Rule Measure. Of Desire super. Sub. Type Overlap. Type Measure. Type (scale) DM 2 Object DM 2 Values Object Values Content 25

NECM DM 2 Evaluation View (OV-5 b to Measures) Traceability Check Activity Measure. Of Desire Couple. Type Performance Measure 3 Condition activity. Performabl e. Under. Condition Measure. Type measure. Of. Type activity. Performabl e. Under. Condition type. Instance super. Sub. Type Measure. Type (scale) 26

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

NECM DM 2 Performance Measure Example (SN 7. 8. 1 M 1: Operational Timeliness) Activity : Op. Activity 1 Start Boundary. Type Activity: OSpec 1 activity. Performable Under. Condition End Boundary. Type Activity: Op. Activity 2 Activity: OSpec 2 Temporal Measure (event time) Overlap. Type measure. Of. Type Condition Temporal Measure (event time) Performance Measure Rule Couple. Type Measure. Of Desire 28

OV-5 b Example Activity: OSpec 1 Start Time: ti Start Boundary. Type Temporal Measure Activity Performable Under. Condition measure. Of. Type Condition Overlap. Type ti tf Condition Activity Performable Under. Condition Overlap. Type measure. Of. Type Condition Rule Overlap. Type Performance Measure Temporal Measure End Boundary. Type Activity: OSpec 4 End Time: tf *assuming all 4 Activities are Performable. Under. Condition 29

JMT DM 2 Measures Mapping Feedback • Direct association between Activity (or activity. Type) and Measure, so not necessary to go through the Condition just to get to the measure. • Measure unit (scale) as a Rule, not Measure. Type • More specific measure associations? Currently using: – Generic Overlap. Type to go from the Temporal. Measure to Rule (to be able to perform the duration calculation) – Rule to the Performance. Measure (the actual calculation) – Actual measure Performance. Measure relating to Measure. Of. Desire with a generic Couple. Type 30

Influence of DM 2 • Requirement of DM 2 compliance has influenced J 8 JMT modeling process – No “PRO” relationship (Performer. Resource. Overlap) – Impact: Activities from OV-5 b mapped into OV-2 System Functions (Activities in DM 2)included in SV-1 31