OMG Presentation

Use of MDA in the SIAP Program

Presented at:

MDA Implementers’ Workshop:Succeeding with Model Driven Systems

May 17-20, 2004 – Orlando, FL

By:

Basil Krikeles and Robert Merenyi, ALPHATECH, Inc.John Brtis, The MITRE Corporation

©2004 – The MITRE Corporation

OMG Presentation

Agenda

• Single Integrated Air Picture (SIAP)

• The Integrated Architecture Behavioral Model (IABM) PIM

• From PIM to PSM – Procedure, Verification, Validation

• Issues

• Summary

OMG Presentation

Joint Engagement ZoneJoint Engagement Zone

MaritimeMaritimeGroundGround

AirAirOperational Problem:

• Engagements constrained by- Procedural controls- Target ID- Sensor limitations

• Lack of interoperability among- Weapon Systems- Sensors- C4I

Operational Problem:• Engagements constrained by

- Procedural controls- Target ID- Sensor limitations

• Lack of interoperability among- Weapon Systems- Sensors- C4I

Operational Elements:• Single Integrated Air Picture• Combat Identification• Integrated Fire Control• Automated Battle Management

Aids• Attack Operations• Passive Defense / Early Warning

Operational Elements:Operational Elements:• Single Integrated Air Picture• Combat Identification• Integrated Fire Control• Automated Battle Management

Aids• Attack Operations• Passive Defense / Early Warning

Problem Definition

OMG Presentation

Process Overview

• Integrated Architecture Behavior Model (IABM) requirements sourced from all Services

• JSSEO outputs test requirements for Joint Interoperability Test Command (JITC)

• JSSEO produces IABM for use by Services– PIM developed by industry, university, FFRDC and government team

– Distributed through Program Offices to primes

OMG Presentation

SIAP Consortium

ALPHATECH, Inc.

OMG Presentation

The SIAP Goal

• A federation of peers over the network implementing the same processing logic

– Each peer is a Platform-Specific Implementation (PSI) of the same IABM PIM– Peers are deployed on heterogeneous platforms

• Peers can share consistent information such as Combat ID– Common functionality implemented and maintained commonly

• Each peer can generate an improved, more complete, picture of the battlespace by utilizing information received from other peers

• Specifications for the shared behavior are expressed in a form that is not susceptible to human error or interpretation by the contractors

• Verification and validation of correct performance can be accomplished uniformly across all weapons systems

OMG Presentation

Using MDA to Implement SIAP

• Critical processing logic (business rules) captured in the IABM (PIM), guaranteed to be applied uniformly across all IABM Peers

• Requirements and specifications encapsulated in the IABM are precise and not subject to interpretation by prime contractors

• Potential n to 1 reduction in the maintenance cost of the core processing logic (n Weapon Systems, 1 IABM)

• Separates functionality and implementation– Provides design stability as implementation technologies evolve and improve

Integrated Architecture Behavior Model(IABM PIM in xUML developed by JSSEO)

Weapon System Instantiation a

Weapon System Instantiation b

Weapon System Instantiation n

…

OMG Presentation

Cost Implications of MDA

Testing Program Mgt

System A

System B d e f

Duplicate Effort

cba

cba d e f

Analysis/Design Coding Integration

Conventional Development Total Cost = Cost of System A + Cost of System B

System A(PSM)

System B(PSM)

d e f

d e f

Integration

cba

Common (shared) Effort

MDA Cost Savings over n Weapon Systems = n * (a + b + c)

The cost of both PIM development and maintenance is amortized across multiple systems.

Analysis/Design CodingProgram MgtTesting

IABM Development (PIM)

OMG Presentation

Overview of IABM Approach

Target HardwareTarget Hardware

WeaponsWeapons

SensorsSensors

CommsComms

Run-Time Interface Domain

AdaptationLayer

Sensor InterfaceComms Domain

User InterfaceDomain

HUD/HDDsHUD/HDDs

DisplaysDisplays

Other ToolsOther Tools

Target Execution Environment(Processors / Operating System / Language)

IABMCore

Isolates application from hardware devices and

data buses

Isolates application from hardware devices and

data buses

Isolates application from underlying execution

technologies

Isolates application from underlying execution

technologies

Core domains capture common

behaviour to ensure uniformly applied

processing rules in a net-centric environment

Core domains capture common

behaviour to ensure uniformly applied

processing rules in a net-centric environment

Isolates application from user interface

formats and devices

Isolates application from user interface

formats and devices

OMG Presentation

Notional PIM-to-PSI Transformation

IABM iniUML

TA-x(tool)

Requirements Development

Xform rulesin iUML

Transformation Development

iCCG(tool)

PSMCCompiler

(tool)

Platformlibraries

PlatformImplementationPlatform-Specific

Model Compiler

OMG Presentation

PSM Generation

CompilerGenerator

PlatformTranslation Rules

(Transformation model)

PSMC(exe)

g++

Platform-SpecificBuild Set (PSBS)

Model Compiler Framework

Compiler Meta Model

Creation of Customized Code Generator

Creation of Target Executable

Generated C++ (PSM)

Generated C++

Legacy headers& libraries

g++

Platform-Specific

Implementation(PSI)

Platform-Specific

Model Compiler(PSMC)

xUML Source code

Executable binary

Executable binary

OMG Presentation

PSI Verification and Validation

RTI / Middleware

IABM Peer(PSI)

IABM Peer(PSI)

Simulation Test Objectives• Does PSI behave as an expected instance of the IABM?

– Can be verified using stub interface code

• Does PSI behave as expected by weapon system platform?– Initial stub testing can reveal early performance numbers

– Final testing requires fully populated platform library code

TrackDisplayTrack

DisplaySensorFeeds

SensorFeeds

Test Harness

OMG Presentation

SIAP System Development Process

Yes

ServiceStart point

Ongoing JDEPValidation Testing(1x / 3-4 months)

1.5

JSSEO

IABM Dev

Generate PSM

3.4

IRC

PSM Dev.

Establish TestFacility

4.1

IRC

PSM Test

Testing

4.5

IRC

PSM Test

ResultsAcceptable?

Analyze, Review,Document Test

Results

4.6

IRC

PSM Test

Conformance Testing to:- JROC validated CRDs- MIL STDs- JROC Validated ORDs

JITC

JITC

Test Development

1.2

JSSEO

IABM Dev

Develop IABM(Core, Optional, &generic Adaptation

layers)1.1

JSSEO

IABM Dev

Time-box Testing(1x / Month)

1.3

JSSEO

IABM Dev

Develop HLA RTIPSM

1.4

JSSEO

IABM Dev

End-to-EndJDEP V&V

1.7

Joint

IABM Dev

Test Development

1.6

Joint

IABM Dev

Identify JITCRequirements

JSSEO

IABM Dev

Partition ExistingWS Program

2.5

SPO Prime

WS Analysis

Map WS / IABMFunctions to WS /

IABM PhysicalStructures

2.4

SPO Prime w/ IRC

WS Analysis

Map Functions ofIABM to WS

Platform

2.2

SPO w/ SPO Prime

WS Analysis

Existing WS SourceCode

Test Results

JSSEOStart point

Generate PSI

3.5

IRC

PSM Dev

g++ Compiler

Interfaces to Existing WSCode (Header Files)

Trouble Report orECP to IRC

Test Report

WS to IABM AlignmentDocument

Platform IABMInterface Spec.

- Operating System - Middleware - CPU Mapping - Ref. Implementation - Processor Dist Input

Customize ModelCompiler (Analysis,Design, Code, Test)

3.3

IRC

PSM Dev.

- TA-5 Adaptable - Operating System- Compiler Suite (g++)

USAF Requirements

JROC Validated ORDs(Combat Sys. Reqs)

MIL STDs

JROC Validated CRDs

Select IABMFunctionality in

Optional Layer anddefine BuildSet (incterminator bridges)

3.2

IRC

PSM Dev.

Platform SpeciificModel Compiler (PSMC)

PSM (Source Code)

Platform SpecifcBuild Set (PSBS)

IABM

PSI (binary)

JITC

IOC

Developmental T&Efor Integrated

Systems

6.3

SPO Prime w/ SPO

WS Test

Developmental T&Efor joint BMC2Functionality

6.4

SPO Prime w/ SPO

WS Test

Initial OperationalT&E &

Live Fire T&E

6.5

SPO Prime w/ SPO

WS Test

Follow-onOperational T&E

6.6

SPO Prime w/ SPO

WS Test

Pre-deploymentConformance

Testing

6.7

SPO Prime w/ SPO

WS Test6.1

SPO Primew/ SPO

WS Test

Dev

. & O

pera

tiona

l Tes

t Dev

elop

men

t

Stub Source Code

Establish TestFacility

5.1

SPO Prime

PSM Test

Testing

5.3

SPO Prime

PSM Test

Analyze, Review,Document Test

Results

5.4

SPO Prime

PSM Test

Test Results

Test Data

Test Plans &Procedures

Link PSI w/ ExistingWS Library

5.2

SPO Prime

PSM Test

g++ Compiler

Test Report

Existing WS PSI(.exe file)

ExistingWS Program

WS to IABM FunctionalMapping Document

WS Physical Structure

IABM

WS Adapter

Develop WSAdapter to the IABM

Adaptation Layer

3.1

IRC

PSM Dev

Platform IABMInterface Spec.

Config ’05 Document

Timebox Content &Schedule Document

InterfaceRequirements

WS FunctionalRequirements &Responsibilities

Develop USAFAnnex to Config ’05

(Multi-Phase)

2.1

SPO w/ SPO Prime

WS Analysis

Resolve WS / IABMFunctional Mapping

Issues

2.3

SPO, SPO Prime & JSSEO

WS Analysis

Link PSI w/ StubLibrary

4.3

IRC

PSM Test

SIAP Requirements & Functions

Test Harnesses

Develop Test Plan

4.4

IRC

PSM Test

TestEnvironment

Test Data

Test Plan &Procedures

Develop GenericTest Harnesses

4.2

IRC

PSM Test

Test Environment

Integration onto WSEquipment

6.2

SPO Prime w/ SPO

WS Test

WS Stub PSI(.exe)

Design & DevelopExisting WS Interface

(fan-in / fan-out,tanslate / transform)

2.6

SPO Prime

WS Analysis

SIAP Requirements& Functions

SIAP Requirements& Functions

OMG Presentation

Challenges

• Tools supporting MDA are still evolving– UML standards for interchange and transformations being

defined

• Configuration Management unique to the MDA process – See Wednesday’s “Practical MDA” sessions

• Horizontal acceptance– New government procurement paradigm

– Affects prime’s business model

OMG Presentation

Summary

• SIAP is an important goal of the DoD that is now being addressed using a novel approach both in terms of development as well as government procurement

• The Joint SIAP System Engineering Organization has adopted Model Driven Architecture with xUML as their development and deployment methodology

• Shared processing logic is captured in JSSEO’sIntegrated Architecture Behavior Model (IABM) – an xUML model can be deployed in multiple weapons systems