all presentation material copyright eurostep group ab ® using systems engineering data standards...

All Presentation Material Copyright Eurostep Group AB

®

Using Systems Engineering Data

Standards with DoDAF

Ian Bailey (Eurostep)Fatma Dandashi (Mitre Corp)

Dwayne Hardy (American Systems Corp)David Price (Eurostep)

®


Disclaimers

• Most of the following is from the co-authors of a white paper on this subject– Ian Bailey, Eurostep– Dwayne Hardy, American Systems Corp– Fatma Dandashi and Huei-Wan Ang, Mitre– and, based on a Dwayne Hardy quote,

“Hundreds of like minded individuals who are contributing to the vision of model-driven SE championed by the INCOSE MDSD WG”

– including your own Sandy Friedenthal and others

®


Standards and SE data

• DoDAF - DoD Architecture Framework– Defines standardized views of systems information

• International Council on Systems Engineering (INCOSE) and Model-Driven System Design– Model-Driven SE Semantic Dictionary and Concept Model– Group work results in SysML/AP233 and alignment activity

• SysML - from Object Management Group– Provide a standard modelling language and notation for

systems engineers

• AP233 Systems Engineering - ISO 10303-233– Defines a neutral information model for complex systems

engineering structures

®


Why DoDAF?Military

Capabilitiesexpressed as •Concepts•Means•Behavior•Outcomes

DoD’s framework for defining mission capabilities

and related system-of-systems architectures

SoS and System

Componentsexpressed as •Components•Functions•Interfaces•Interactions

®


The DoDAF Views

OperationalView (OV)

OperationalView (OV)

SystemsView (SV)

TechnicalStandardsView (TV)

operationalrequirements

capability &supportabilityinformation

functional,organizational

& interfacerequirements

systemdesigns to

support process

standards governing systems interoperability

verification ofcapabilityagainst

standards

Prescribes technical standards

Organizations, activities, information flow requirements

System structure, interfacing, data models, etc.

®


Operational

Systems

Technical

Operational Concept Description (OV-1)

Node Connectivity Description (OV-2)

X YXZ

XY

Y

Systems InterfaceDescription (SV-1)

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

© Mitre Corp

Summary of DoDAF Views

®


Operational Activity Models (OV-5)

Node C

Node A

Node B

Activity 2

External Activity 1

Activity 1

Flow1

Flow 2

External Activity 2

Node D

Activity 3

Flow 3

Flow 4

Conducts

Conducts

ConductsConducts

Conducts

© Mitre Corp

®


Interface 2

Node A

System 1

System 5

Node B

System 1

System 3

Node C

System 1

System 4Node1

External Connection

Sys Func LSys Func M Interface 1

Interface 4

Sys Func N

Sys Func LSys Func M

Sys Func HSys Func ISys Func J

Interface 5

Key Interface 3

Systems Interface Description (SV-1)

© Mitre Corp

®


SysML

• System Modeling Language being standardized in OMG– “a general-purpose systems modeling language”– “supports the specification, analysis, design, verification and

validation of a broad range of complex systems”– “systems may include hardware, software, data, personnel,

procedures, and facilities”

• Based on UML 2.0 with extensions (i.e. a UML Profile):– To define engineering semantics for existing UML concepts– To add requirements and parametric capabilities

• AP233 and SysML based on the common Concept Model from INCOSE which defines their scope

®


SysML Diagram TypesSysML Diagram

StructureDiagram

BehaviorDiagram

Use CaseDiagram

ActivityDiagram

AssemblyDiagram

SequenceDiagram

InteractionOverviewDiagram

State MachineDiagram

TimingDiagram

ParametricDiagram

RequirementDiagram

ClassDiagram

Modified from UML 2

New diagram type

© SysML Partners (Submission to OMG)

®


SysML – System Structure

Example © SysML Partners (Submission to OMG)

®


SysML – Requirements


®


SysML – Continuous Behaviour


®


SysML – State Machines


®


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

®


How Does AP233 Help?

• Defines a reliable, automated way to move data between SE software tools– Eliminates the need for data re-entry

• Provides a system-independent format for archiving data

• Can be specified in a contract• Unlocks data stored in uncompetitive systems• Allows movement of data along the design process

– e.g. requirements->systems->budgeting->design

• Introduces functionality never before possible– All systems engineering data can be integrated together– Allows whole-system, whole-lifecycle design and analysis

®


Using Them Together• One obvious scenario

– Use DoDAF to specify requirements for the different views of a system

– Use SysML to model the system– Use AP233 to exchange data between SysML, legacy SE

tools and other DoDAF views

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

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

SV4 OV2

OV7 TV2

AP233

SysML

• --------

--------

--------

--------

--------

--------

--------

--------

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

DoDAF

®


How Well do They Fit ?

• AP233 and SysML are being aligned by the development teams

• Initial analysis indicates good coverage of the relevant DoDAF views with SysML

• AP233 aligned with SysML scope but can also exchange the DoDAF Technical Views– AP233 is independent of modelling technique or

representation and so can exchange data between non-SysML tools also

®


Proof-of-concept

1. AP233 Demonstrator2. SysML Assembly/AP233 project3. DoDAF CADM/AP233 project

®


1. AP233 Demonstrator

• Initial work sponsored by NASA JPL– further development sponsored by UK MOD and

Eurostep

• Intended to:– showcase AP233 functionality– enable creation of test data and to test AP233

functionality– provide target/source for vendor i/f

implementations

• Uses High Level API– native format is AP233 STEP ASCII File– High Level API has also been used for DOORS,

Cradle and Requisite Pro interfaces

®


AP233 Demonstrator

®


AP233 Demonstrator Interfaces

DOORS (Telelogic)

Core (Vitech)

Slate (EDS)

SysML (Poseidon UML)

Cradle (3SL)

Also:• Requisite Pro• MS Word• MS Excel• MS Visio• MS Project

®


2. SysML Assembly/AP233 project

• For John Deere research– SysML team member

• Define a mapping from SysML Assembly to STEP AP233/SysEng Structures

• Implement mapping using an early UML 2/SysML tool

• Import resulting data into “AP233 Demonstrator” to show what’s possible

®


The SysML Assembly Test Case Input

A Part in an Assembly

A Port in an Assembly

The Part Definitions

A Connector

A Second Level Assembly

®


SysML Meta-model example

• Data structures like this support the diagram notation of SysML, SE’s never see thisPort concept defined

®


AP233 Structure/Interfaces example

• Portions of AP233 EXPRESS model translated to UML, SE’s never see this either

Assembly/Port Link concept defined

®


Exchanged Part/Port in Assembly Output

Capacitor Part in Assembly

Output Port in Assembly

Low-pass filter Assembly

®


3. DoDAF CADM/AP233 project

• For DoD/American Systems Corporation– SysML team member

• Project currently underway– First demonstration planned for joint

INCOSE/OMG conference early November 2004

• Define mapping from several DoDAF Views to AP233

• Implement two-way mapping between DoDAF CADM XML format and AP233 XML format

®


Example AP233 & DODAF Scenario

CADMXML AP233

XML

SystemsEngineering

Tools

CASE/RAD Tools

e.g. System Architect

e.g. Rational Rose

etc.

e.g. DOORS

e.g. Slate

etc.

DARS PDM/PLCS

DataConverter

®


Conclusions

• DoDAF, SysML and AP233– Improve the systems engineering of Systems of Systems– Support related analyses and project management

decisions– Have different roles in the systems engineering process

• DoDAF provides larger context/framework for SE• SysML is tool for SEs enabling consistency across DoDAF and

other architectures/processes• AP233 for SE system integrators supporting a broad scope

– enables SysML/other SE modeling paradigm exchange and legacy data extraction

– opens up possibility of standardized shared data environments based on SysML and DoDAF

– Proof-of-concepts show that they do work together

®


More Information

• AP233– [email protected]– NASA AP233 Page at http://step.jpl.nasa.gov/AP233/– Eurostep AP233 Page at http://ap233.eurostep.com

• DoDAF– [email protected]– DoD NII Archive at http://www.defenselink.mil/nii/doc

• SysML– [email protected]– SysML Partners Page at http://www.sysml.org– OMG SysEng SIG at http://syseng.omg.org/

• The International Council on Systems Engineering– INCOSE at http://www.incose.org

all presentation material copyright eurostep group ab ® using systems engineering data standards...

Documents