Transcript DoDAF CADM ISO AP233 OMG UML Converter Interim Report

®
Integrating System Architecture
& Engineering Applications Using
Open Systems
David Price
OSJTF SoS Architecture Modeling Meeting
September 22, 2005
System-of-Systems Architecture
Increasingly, architectures are used as basis for programmatic decisions
This increases importance of their consistency, precision and scalability
SoSs typical characteristics:
Individual
Focus
• Not
managed orSystem
funded under
a singular
System-of-Systems Focus
authority
Boundary
•
•
•
•
•
•
Interactions
Composed of complex systems that
provide independent functionality
Hard to bound
Distributed over time and space
Dynamically assembled, ‘on-the-fly’ by
operational commanders
Compete with other SoSs for the same
resources
Relatively short lifecycle, compared to
traditional systems
Modules
Interfaces
®
Boundaries
Collaborative System-of-Systems Engineering
System B
System A
Boundary
Boundaries
Modules
Interfaces
Modules
Interfaces
System-of-systems engineering requires:
Request
Systemfor describing systems architectures
• Use of robust modeling
techniques
Model
Response
• And, Greater collaboration and tool interoperability
®
Our Focus is on SE Standards
•System-of-systems engineering requires
Request
System
•Greater collaboration and tool interoperability,
and …
Model
Response
•Using robust modeling techniques for describing
systems architectures
• Enable communication between SEs and the tools
they use
– Approach described in white paper : Using Systems
Engineering Standards In an Architecture Framework
– Influenced by DoD, INCOSE, ISO STEP and OMG
communities
®
AP233 Systems Engineering
•System-of-systems engineering requires
Request
System
•Greater collaboration and tool interoperability,
and …
Model
Response
•Using robust modeling techniques for describing
systems architectures
• AP233 = ISO standard specifying communications pipeline between
Systems Engineering tools and databases
• Designed to be neutral vs DODAF, MODAF, SysML, UML, IDEF, other SE
tools, … which are more specific
• As part of ISO STEP series, AP233 links to standards with a vast scope
– AP stands for “Application Protocol”
• APs are very formal and strict – intended to prevent ambiguity in data exchange
• APs define the types of data to be exchanged and the structure of that data
– There are 40+ STEP Application Protocols
– AP233, like all new modular APs, is built from reusable information model
“modules” for compatibility across application domains
®
DoDAF CADM/AP233 Project
• 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
• Phase 1 and 1a Scope
– SV-1, SV-2, SV-3, SV-4, SV-10b, OV-5, OV-6b, TV-1 subset
– Delivered via www.exff.org/ap233 Web site
• Phase 2 includes all remaining products
– Plus AP233 High Level API
– Plus Extras such as:
• SysML/AP233 State Machine translation specification
• SysML Requirement/Systems Allocation demo
®
ISO STEP-enabled
Downstream Tool
Operational
DODAF
specifies requirements for
Any SE Tool
Request
System
Model
Response
DOD CADM
DoD Architecture
Repository System
®
Demo : Executable Architectures
Create Activity
Breakdown in
MindMap Tool
OV-5
Operational
Activity Model
(UML)
Transfer to UML
Tool Thru AP233
Pipeline
Request
System
Model
Response
Simulation
Tool
(SVM)
Transfer to Simulator
Thru AP233 Pipeline
®
OV-6b
Build State
Machine
(UML)
Contact Information
• David Price
– [email protected]
– +44 20 7221 7307
– exff Systems Engineering
• http://www.exff.org/ap233
• AP233
– NASA AP233 Page at http://step.jpl.nasa.gov/AP233/
• DoDAF
– DoD NII Archive at http://www.defenselink.mil/nii/doc
• SysML
– 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
®