Integrating System Architecture

1
Integrating System Architecture Engineering
Applications Using Open Systems

• David Price
• OSJTF SoS Architecture Modeling Meeting
• September 22, 2005

2
System-of-Systems Architecture
Increasingly, architectures are used as basis for
programmatic decisionsThis increases importance
of their consistency, precision and scalability

• SoSs typical characteristics
• Not managed or funded under a singular authority
• 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

3
Collaborative System-of-Systems Engineering

• System-of-systems engineering requires
• Use of robust modeling techniques for describing
  systems architectures
• And, Greater collaboration and tool
  interoperability

4
Our Focus is on SE Standards

• 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

5
Standards and SE data

• DoDAF - DoD Architecture Framework
• Defines standardized views of systems information
  
• CADM Core Architecture Data Model
• INCOSE - International Council on Systems
  Engineering
• Model-Driven System Design Working Group
• 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

6
DoDAF
DoDAF tells SEs what kinds of models to
create DoDAF does not require a specific tool or
notation IDEF, UML, etc. all OK Some SE tools
are tailored for DoDAF support Is a US DOD
standard
7
SysML
SysML is OMG standard language and notation for
SEs to use SE tools will implement and conform
to SysML SEs will understand SysML concepts and
terminology SysML can be used by SEs to create
systems architectures following DODAF
8
AP233 Systems Engineering

• 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

9
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

10
AP233 Scope
requirements
breakdowns
PDM
product structure
config control
static structure
system sub-system
text-based
person org
functional breakdown
WBS
security
property-based
behaviour
analysis
rules
state-based
verification validation
model presentation
function-based
risk
measurement
Legend
future work
completed
11
Proving this path
12
Context Diagram for Systems Engineering Standards
DoDAF

• This shows only one thread through these
  standards, others are necessary as well.

CADM
13
(No Transcript)
14
Demo Executable Architectures
Create Activity Breakdown in MindMap Tool
OV-6b Build State Machine (UML)
15
Contact Information

• David Price
• david.price_at_eurostep.com
• 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

16
SysML-ISO AP233 Converter Demo

• Eurostep David Price and Phil Spiby
• ARTiSAN Alan Moore
• INCOSE International Symposium
• July 2005

17
Agenda

• Brief overview of SysML concepts
• Brief overview of AP233 concepts
• The demo

18
Why the demo?

• This is a proof-of-concept demo
• Not trying to test any of the in-process STEP
  capability
• Two purposes
• show that some SysML/AP233 use cases are already
  supported
• show that converters can be easy and cheap to
  build

19
System
Requirement
System Decomposition
Requirement Decomposition
System Satisfies Requirement
Requirement Derivation
20
ISO Requirements concepts
Requirement
Requirement
Requirement
21
ISO Requirements Assignment
System Satisfies Requirement
22
ISO Requirements relations
Requirement Decomposition
Requirement Derivation
23
On implementation

• Using only UML and XML representations of STEP
• For STEP experts demo uses ARM and external
  taxonomy
• Not everyone likes this approach?
• Currently implemented as XSLT
• APIs to come, which will speed development even
  more
• Prototype translator development can be a matter
  of days (lt 2 for demo)
• Though we admit to being experts at this stuff ?

24
The Exported XMI File
25
The Translated AP233 XML File
26
In AP233 Demonstrator
27
Conclusions

• ISO STEP already supports
• Core SysML Requirements concepts
• Core SysML System concepts
• AP233-specific extensions should broaden SysML
  coverage
• SysML/AP233 translator implementation can support
  industry needs, yet be simple and inexpensive if
  we
• stay out of the weeds in STEP-land
• use widespread technology

28
CADM and AP233

• David Price
• September 2005

29
CADM/AP233 Project

• Delivered on publicly available, not password
  protected Web site
• Defines AP233 in terms of UML and XML rather than
  niche STEP/EXPRESS terms
• Defined a mapping from DODAF Products
  perspective for the supporting CADM XML
  structures
• Implements proof-of-concept converters between
  CADM and AP233
• Implements other converters in order to do
  demonstrations (e.g. UML to AP233 to CADM)

30
Approach

• Use the simplest part of AP233, technically
  called the Application Reference Model
• Use a related Taxonomy and the AP233 built-in
  capability to classify most things in the
  information model
• E.g. Most types of requirement implemented as
• Requirement lt- Classification -gt Class of
  requirement
• Some parts of the Taxonomy need to be
  standardized as part of AP233
• Other parts do not and are a specialization of
  the use of AP233 for a particular industry or
  agreement
• This works in a similar way to a UML Profile,
  like SysML

31
Profiles of AP233
AP233 Standard Taxonomy
Adds semantics to
UML2/SysML Standard Taxonomy
Adds semantics to
CADM Standard Taxonomy