DoDAF CADM ISO AP233 OMG UML Converter Interim Report

®

Eurostep.ESUKPC20.000049v0.1©Copyright Eurostep Limited

DoDAF CADM ISO AP233 Converter Project Final

Presentation

David PriceFebruary 2005

®


Agenda

• Who am I and what is Eurostep?• Project Focus• Project Technical Summary• Walkthrough of Mapping Documentation• Demonstration of Software• Recommendations for Further Activities

®


Who am I?

• David Price– ~20 years at IBM as Senior Software Engineer

• Mechanical CAD support, Corporate Design Practices• IBM Consulting, IBM Enterprise Integration• Assignee to PDES, Inc. consortium developing ISO STEP

stds

– ~4 years at Eurostep Limited as Senior Consultant• Oil and Gas data warehouse standards/implementation• Ship Classification data exchange UML/XML Schema

project• ISO AP239/PLCS Semantic Approach to Taxonomies for

data exchange for UK MoD• Open-source Web site www.exff.org dedicated to data

exchange and modeling language interoperability

®


What is Eurostep?

• Eurostep Limited– Consulting company based in UK, part of Eurostep Group

operating in UK, Sweden, Finland and USA• Eurostep Sweden commercial product Web-enabled PLM system

– Typical Customers : BAE SYSTEMS, UK MoD, Volvo, NASA/JPL, Boeing, FMV, AstraZeneca, John Deere

– Decades of experience in ISO STEP and OMG standards– Decades of industrial experience in Aerospace, Ship

Classification, Logistics Support, PLM, Mechanical Engineering, …

– Related projects• SEDRES 2• PLCS Consortium Project and Technical Coordination• ISO STEP AP239/PLCS and AP233/SysEng modeling• SysML submission team member

®


Project Focus

• Based on white paper describing DoDAF, SysML and AP233 standards for System-of-systems and Systems Engineering– Using Systems Engineering Standards In an

Architecture Framework by Ian Bailey, Eurostep, Fatma Dandashi and Huei-Wan Ang, Mitre Corp, and Dwayne Hardy, American Systems Corp

• Influenced by INCOSE, ISO STEP and OMG communities

®


Future Big Picture?

SV4

AP233

OMG SysMLOther SE Views

Operational

Systems

Technical

DODAF

AP2xx

Detailed Design,Manufacturing,Life Cycle Support,…

ISO 10303STEP Standards

specifies requirements for

AP233

DARS

CADM

CA

DM

CADM = Core Architecture Data ModelDARS = DoD Architecture Repository System

®


Walkthrough of Mapping Documentation

• Document as a Web site in the style of a programmers guide– Audience

• Audience is software developers• No previous knowledge of AP233 is required• UML diagrams and XML Schemas used to explain how

to write a converter

– Approach• Develop standalone AP233 document that is

independent of DoDAF/CADM mapping• Develop document for each DoDAF View and “link” into

the AP233 document• Makes the AP233 documentation reusable for a similar

project on SysML, MoDAF, etc.

®


The Mapping Documentation

®


ActivityHierarchy

(Mindmap)

OperationalUse Case(UML)

SystemsInterfaces

(UML)

AP233

CADM

AP233 AP233

Demonstration Scenario

SimpleCADMBrowser

12

34

5

®


Resulting Tool Interoperability

• CADM-AP233 interoperability creates a new path into DoDAF for:– UML/SysML tool vendors– Non-UML tool vendors– Other military AFs

• UK MoDAF Enterprise Reference Model

• CADM-AP233 interoperability creates a capability to feed DoDAF data down the systems life cycle via other STEP APs– e.g. AP239/Product Life Cycle Support for Support

Engineering, Maintenance, Logistics, etc.

®


Recommended Next Steps

• Release current software and documentation as open source– With DoD approval, Eurostep will post results as open-

source project to which anyone can contribute

• Evaluate possibility of validating results in CADM testing forum

• Consider expanding CADM-AP233 to cover additional views– Suggest priority aligned with SysML to build on

momentum

• SysML 1.0 release planned for June 05, consider doing a similar project for SysML-AP233– SysML partners have prototyping plans

®


From SysML Submission

®


From SysML Submission

®


Where might we go from here?

• Interoperability can be provided through an open-source set of software tools reducing barriers for everyone– The XML community has been very successful at

this

• Ideas for the information technology– High Level API specified as UML and delivered in

multiple programming languages (e.g. Java, C++, C#)

– Direct converters for other standard formats (e.g. XMI)

– Web services and interoperability hubs on Web

®


AP233 approach

• Standardize flexible, extensible information model in ISO– Independent of any tool or modelling approach

• Can represent UML, IDEF and non-standard tool languages

– Extension via a “classification by external class” concept within the information model itself

• makes AP233 suitable as a neutral data exchange standard for Systems Engineering data

• leaves room for communities or organizations to tailor AP233 use for specific needs

– Designed for data exchange, not for operational system or repository Fewer semantics and rules written into the information model

• Breaks concepts down to relatively fine level of detail to support a variety of tools/disciplines

®


AP233 Requirements

ISO Information Model External Classes (aka Taxonomy)

®


DoDAF/CADM External Classes

®


AP233 is modular

• AP233 is one of the new suite of STEP modular APs– A STEP module is a small, reusable information

model from which the larger Application Protocols are created

– So, if AP233 doesn’t quite cover something it can be extended by incorporating or creating other small STEP information models

®


DoDAF Uses

®


AP233 Systems Engineering

• AP233 is the Systems Engineering part of the new suite of ISO 10303 STEP Application Protocols built from modules– Shared constructs guarantee interoperability between disciplines

such as Systems Engineering, Product Life Cycle Support and Configuration Controlled Design

• Defines a formal, strict information model– intended to prevent ambiguity when used for exchange between

engineering systems

• As part of STEP, AP233 links to standards with a vast scope

®


AP233 Scoperequirements

text-based

property-based

breakdownsstatic

structure

PDM

analysis rulesbehaviour

productstructure

systemsub-system

functionalbreakdown

WBS

verification &validation

state-based

function-basedmodel presentation

configcontrol

security

risk measurement

person &org

completed

future work

Legend

®


Project Overview

• Deliverables– Interim report and CADM/AP233 converter

• Demonstration at OMG/INCOSE conference

– Final report, CADM/AP233 converter and demonstration

• DoDAF Views In-scopeSV1 – System Interface DescriptionSV2 – Systems Communications DescriptionSV3 – Systems-Systems MatrixSV4 – Systems Functionality DescriptionOV5 – Operational Activity ModelTV1 – Technical Standards Profile

®


SysML UML 1.5 MoD AFERM

Non-UMLTools

AP233

CADM

AP233 AP233 AP233

Possibilities

SimpleCADMBrowser

®


Project Technical Summary

• Scope– SV-1, SV-2, SV-3, SV-4, OV-5, TV-1 subset

• Purpose– Evaluate feasibility of system architecture data exchange

using emerging ISO AP233 Systems Engineering standard• Not a fully validated design effort

– Provide a body of work that future efforts can build upon

• Deliverables– Documented mapping between DoDAF CADM XML format

and the ISO AP233 XML format• Delivered as a Web site• Audience is software developers writing CADM-AP233

translators– Software that coverts between CADM XML and AP233 XML

• Upon permission from DoD, intended release as open-source project

®


Operational

Systems

Technical

Operational Concept Description (OV-1)

Node Connectivity Description (OV-2)

X YXZ

XY

Y

Systems InterfaceDescription (SV-1)

Operational Activity Model (OV-5)

Information Exchange Matrix

(OV-3)

Activity to System Function (SV-5)

System Functionality Description (SV-4)

Organizational Relationships Chart (OV-4)

Systems Data Exchange Matrix (SV-6)

Operational Activity Sequence and Timing

Description (OV-6 a/b/c)

NODE A

Local Area Net

System 1 System 2

System 3 System 4

System 5

EXTERNALCONNECTION(OUTSIDE THENODES OF INTEREST)

CONNECTIONTO NODE B

CONNECTIONTO NODE B

CONNECTIONTO NODE C

Two-WayCommunicationsLinks

One-WayCommunicationsLink

Systems Communications Description (SV-2)

System - System Matrix (SV-3)

Systems Technology Forecast (SV-9)

Standards Technology Forecast (TV-2)

Technical Architecture Profile (TV-1)

Systems Performance Parameters Matrix (SV-7)

• ----------------------------------------------------------------

• .....• .....• .....

Logical Data Model (OV-7)

Systems Functionality Sequence and Timing

Description (SV-10 a/b/c)

Systems Evolution Description (SV-8)

Physical SchemaSV-11

A B C

T1T2T3

NODESTIME

A B C

T1T2T3

NODESTIME

DoDAF Views

®


A0--GENERATE TACTICAL RECONNAISSANCE PLAN

A1--DEVELOP TACTICAL RECONNAISSANCE PLAN

A2--COORDINATE ORGANIC SENSOR EMPLOYMENT

A3--COORNDINATE AT JOINT LEVELTACTICAL RECONNAISSANCE PLAN

A1.1--ASSESS INTIAL TR NEEDS FOR MISSIONS AND PLANS

A1.2--UPDATE TR NEEDS

A1.3--ISSUE TRP FOR COORDINATIONA2.1--EVALUATE NEW TR NEEDS

A2.2--ASSESS CURRENT TR CAPABILITIES

A2.3--FINALIZE ARMY TRP

A3.1--ASSESS JOINT TR CAPABILITIES

A3.2--PRIORITIZE TR NEEDS

AIP Sample Data (1)

®


NODE: NO.:A0 TITLE: TRP GENERATION

A1

DEVELOP TACTICALRECONNAISSANCE

PLAN

A2

COORDINATEORGANIC SENSOR

EMPLOYMENT

A3

COORNDINATE ATJOINT

LEVELTACTICALRECONNAISSANCE

PLAN

INTEL REPORTS

MISSIONS AND PLANS

CURRENT SITREPS

ARMY DIRECTIVES

ARMY DOCTRINE

DoD DIRECTIVES

ANALYSTS

SENSORINVENTORY

DB

JOINT OPERATIONSDOCTRINE

DRAFT TRP

UPDATED TRP

FINALIZED TRP

TR DEFICIENCIES LIST

UNSUPPORTEDARMY TR NEEDS

AIP Sample Data (2)

®


Scenario 1

®


Activity and I/O Flows

®


Activity Breakdown

®


Nodes, Systems and Interfaces

®


Conclusions

• Core DoDAF Views/CADM and AP233 can be mapped– Provides additional path for creating CADM data for tool

vendors

• SysML 0.9 out for review and alignment with AP233 is underway– AP233 Structure done– AP233 Requirements done– AP233 Behaviour still in-work

• Confirmed white paper conclusions on SysML, AP233 and DoDAF each being useful

• Deliverables can be reused as the basis for future work– e.g. CADM-AP233 documentation can be basis for adding

SysML-AP233 structure mapping