Model Based Systems
Engineering Tool Review –
Comparison of Tools
Phil Simpkins, Senoir Systems Engineer
Philip.simpkins@kihomac.com
(201) 267-1152
Agenda
o
INCOSE Symposium 2011
o
Introduction to MBSE
o
Compare MBSE Methodologies
o
Systems Engineering





Requirements Analysis
Behavior Analysis
Architecture Synthesis
Validation and Verification
Documentation
The objectives for this session are to familiarize the user with key concepts of
Model-Based Systems Engineering (MBSE) and compare tools
October 2011
INCOSE Chapter Awards
Bronze Circle
3
Where is the Chapter
INCOSE Regions and Chapters
4
Member Resources
 INCOSE.org


On-line renewal
SE Products – (e.g. Handbook, CSEP, SEBoK)
 Insight
 INCOSE Journal
 INCOSE connect at https://connect.incose.org
5
SE Products
o
o
o
o
INCOSE Handbook (Hard Copy)
Systems Engineering Book of Knowledge
(SEBoK) - Portions can be purchased
SE Certification – CSEP (885)
Measurement Use Guidebook for SE
Practitioners
o
Requirements Categorization Guidance
o
Requirements Engineering Guidebook (TBD)
o
Past Symposium Proceedings
6
Working Groups
o
Listed on www.incose.org




Requirements
Risk Management
Complex Systems
Model Based Systems Engineering


Workshop meeting
www.omgwiki.org/MBSE/doku.php
 Lean Systems Engineering
 PMI Interfacing
Future International Workshop
o
January 21-24, 2012 and 2013
o
Jacksonville, Florida
Future Symposia
• INCOSE 2012 in Rome, Italy
July 09-12, 2012
• INCOSE 2013 - Philadelphia
9
Board of Directors Change
Board of Directors
Member Board
Board of Directors Change
Board of Directors
10 %
Asian and Pacific
Chapters
8 Chapters
60 %
30 %
European
Chapters
13 Chapters
North American &
South American
Chapters
46 Chapters
The Systems Engineer’s Dilemma:
Integration and Synchronization
graph 1
graph 2
extracted
requirements
Source
Documents
Data
function
list
graph 3
data
items
traceability
list
physical
components
graph
text
open
action
items
analyses
& trade
studies
engineering
note book
interface
definitions
Systems Engineer’s Desktop
October 2011
Printed
Reports,
Models, &
Specifications
Data
Any change will affect
something else
The Common SE “Tool Suite” Architecture
Requirements
Management
Requirements
Database
Word Processors
Spreadsheets
Behavioral
Analysis
Behavior
Database
Drawing Packages
Spreadsheets
Simulation Packages
Architecture
Synthesis
Verification
Physical
Architecture
Database
Verification
Database
Drawing Packages
Spreadsheets
Testing Packages
Spreadsheets
Multiple products utilizing independent databases forces extraordinary
data management – and complicates the original SE effort
October 2011
The Preferred SE Tool Architecture
Requirements
Management
Behavioral
Analysis
Architecture
Synthesis
Verification
Data
Data
Data
Data
Source Data
Material
Design
Specifications
Data
Integrated, consistent analysis: complete specifications, project documentation,
queries and models
October 2011
The Enterprise Team
Program
Management
Customer
Configuration
Management
Chief Engineer
System Engineer / Architect
Publications
Hardware
Training & Personnel
Software
Environmental
Safety
Operations
System Definition Repository
Reliability,
Availability,
Maintainability
Maintenance
Logistics
Manufacturability
Test
Security
Facilitate domain expert collaboration by leveraging a common repository
October 2011
Comparison of MBSE Methodologies
o
o
o
Telelogic Harmony-SE
INCOSE Object-Oriented Systems Engineering Method
(OOSEM)
IBM Rational Unified Process for Systems Engineering
(RUP SE) for Model-Driven Systems Development (MDSD)
o
Vitech - CORE
o
State Analysis (SA) is a JPL-developed MBSE methodology
October 2011
Telelogic Harmony-SE
Harmony® Integrated Systems and Software Development Process
October 2011
Telelogic Harmony-SE
Harmony® Integrated Systems and Software Development Proce
Harmony-SE Process Elements
October 2011
INCOSE Object-Oriented Systems Engineering
Method (OOSEM)
OOSEM Activities in the Context of the System Development Process
October 2011
INCOSE Object-Oriented Systems Engineering
Method (OOSEM)
OOSEM Activities and Modeling Artifacts
October 2011
IBM Rational Unified Process for Systems
Engineering (RUP SE)
The RUP SE architecture framework
October 2011
IBM Rational Unified Process for Systems
Engineering (RUP SE)
RUP SE Requirements Allocation/Derivation Method
October 2011
Vitech CORE
Behavior Domain
Source Requirements Domain
Data
Originating requirements
trace to behavior
Data
verified by
V&V Domain
Data
CORE
System
Definition
Repository
Behavior is allocated to
physical components
Architecture Domain
Data
Data
verified by
verified by
Originating requirements trace to physical components
Utilizing a layered approach to progressively clarify and elaborate all four
domains concurrently to ensure consistency and completeness
October 2011
Vitech CORE
Vitech MBSE "Onion Model"
October 2011
State Analysis (SA)
Model- and State-Based Control Architecture ("Control Diamond")
October 2011
State Analysis (SA)
Integrated Approach to Design for Safety
October 2011
Comparison of MBSE Methodologies
Tool /
Methodology
Process
Framework
Functional
Analysis
Tool Support
SysML
Simulation
Integration
Harmony SE
•No framework
•No Third Party
Yes
Yes
Yes
Yes, other
software
available
Manually
initiated &
Manually
corrected
OOSEM –
Methodology
only
•No framework
•COTS Tool
applied
Yes, Manual, if
no tool used
No
No
No
No
IBM Rational UP
SE
Yes, Plug-In
available
Yes
Yes, Plug-In
available;
services
recommended
Yes, Third party
Yes, Plug-In
available
No
CORE
•No framework
•No Third Party
•DoDAF Schema
optional
Yes
Yes
Yes
Yes
Yes,
automatic
State Analysis
(SA)
•No framework
•No Third Party
Yes
Yes
No
No
No
October 2011
Tool Comparison at INCOSE 2011
Tool
Company
Name
Req
Tool
Drawing
package
Functional Exchange Data Simulation Doors or other tool
CORE
Vitech
Yes
Yes
Yes
Cradle
3SL
Yes
Yes
Yes
Magic
Draw
No Magic No
Rhapsody IBM
Team
Center
Unified
October 2011
Siemens
Not
really
Yes
Yes – only No – but
a drawing they intend
package
to build an
add-on
Yes
Yes
Yes
One way ( upload or
download not
integrated)
One Way
One Way
Bi-directional but
not really integrated
Not Yet, but One way, but really
intend to.
prefer you use their
tool
Tool Comparison at INCOSE 2011
Tool
Company
Name
Cognitive Cognitive?
Canopy
Req
Tool
Yes
Drawing
package
Functional
Simulation
Yes, some No
Exchange Data
Doors or other
tool
One way
Yes, but
Maybe
not
integrated
Arkitect Knowledge No
Yes
Inside
Windchill PTC
No
Yes
No – High
end Cad
Bi-directional not
integrated
No
One way
No
One way
MD
Sodius
Workben
ch
Yes
Bi directional.
Needs manual start
and verification
Requim
October 2011
Dissault
Yes
Yes