1. Model Based Systems Engineering Tool Review – Comparison of Tools
Phil Simpkins, Senoir Systems Engineer
(201)

2. Agenda INCOSE Symposium 2011 Introduction to MBSE
Compare MBSE Methodologies
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

3. INCOSE Chapter Awards
Bronze Circle

4. INCOSE Regions and Chapters
Where is the Chapter
INCOSE Regions and Chapters

5. Member Resources INCOSE.org On-line renewal
SE Products – (e.g. Handbook, CSEP, SEBoK)
Insight
INCOSE Journal
INCOSE connect at

6. SE Products INCOSE Handbook (Hard Copy)
Systems Engineering Book of Knowledge (SEBoK) - Portions can be purchased
SE Certification – CSEP (885)
Measurement Use Guidebook for SE Practitioners
Requirements Categorization Guidance
Requirements Engineering Guidebook (TBD)
Past Symposium Proceedings

7. Working Groups Requirements Risk Management Complex Systems
Listed on
Requirements
Risk Management
Complex Systems
Model Based Systems Engineering
Workshop meeting
Lean Systems Engineering
PMI Interfacing

8. Future International Workshop
January 21-24, and 2013
Jacksonville, Florida

9. Future Symposia INCOSE 2012 in Rome, Italy July 09-12, 2012
INCOSE Philadelphia
Radiological Control Department to certify the waste.
(Procedures defined and accomplished by operation of the facility are not defined in the requirements section).

10. Board of Directors Change
Member Board

11. Board of Directors Change
60 %
10 %
30 %
North American & South American Chapters
Asian and Pacific Chapters
European Chapters
8 Chapters
13 Chapters
46 Chapters

12. The Systems Engineer’s Dilemma: Integration and Synchronization
graph 1
extracted
requirements
graph 2
graph
text
Printed Reports, Models, & Specifications
graph 3
Source Documents
open
action
items
Data
Data
function
list
analyses
& trade
studies
data
items
engineering
note book
traceability
list
interface
definitions
physical
components
Any change will affect something else
Systems Engineer’s Desktop
October 2011

13. The Common SE “Tool Suite” Architecture
Verification
Database
Physical
Architecture
Requirements Management
Behavioral Analysis
Architecture Synthesis
Requirements
Behavior
Word Processors
Spreadsheets
Drawing Packages
Simulation Packages
Testing Packages
Multiple products utilizing independent databases forces extraordinary
data management – and complicates the original SE effort
October 2011

14. The Preferred SE Tool Architecture
Requirements Management
Behavioral Analysis
Architecture Synthesis
Verification
Data
Data
Data
Data
Design Specifications
Source Material
Data
Data
Integrated, consistent analysis: complete specifications, project documentation, queries and models
October 2011

15. System Definition Repository
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

16. Comparison of MBSE Methodologies
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)
Vitech - CORE
State Analysis (SA) is a JPL-developed MBSE methodology
October 2011

17. Harmony® Integrated Systems and Software Development Process
Telelogic Harmony-SE
Harmony® Integrated Systems and Software Development Process
October 2011

18. Harmony-SE Process Elements
Telelogic Harmony-SE
Harmony® Integrated Systems and Software Development Process
Harmony-SE Process Elements
October 2011

19. INCOSE Object-Oriented Systems Engineering Method (OOSEM)
OOSEM Activities in the Context of the System Development Process
October 2011

20. INCOSE Object-Oriented Systems Engineering Method (OOSEM)
OOSEM Activities and Modeling Artifacts
October 2011

21. IBM Rational Unified Process for Systems Engineering (RUP SE)
The RUP SE architecture framework
October 2011

22. IBM Rational Unified Process for Systems Engineering (RUP SE)
RUP SE Requirements Allocation/Derivation Method
October 2011

23. Vitech CORE CORE System Definition Repository October 2011
Behavior Domain
Source Requirements Domain
Originating requirements
trace to behavior
Data
Data
CORE System Definition Repository
verified by
Behavior is allocated to
physical components
V&V Domain
Architecture Domain
Data
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

24. Vitech MBSE "Onion Model"
Vitech CORE
Vitech MBSE "Onion Model"
October 2011

25. Model- and State-Based Control Architecture ("Control Diamond")
State Analysis (SA)
Model- and State-Based Control Architecture ("Control Diamond")
October 2011

26. Integrated Approach to Design for Safety
State Analysis (SA)
Integrated Approach to Design for Safety
October 2011

27. Comparison of MBSE Methodologies
Tool / Methodology
Process Framework
Functional Analysis
Tool Support
SysML
Simulation
Integration
Harmony SE
No framework
No Third Party
Yes
Yes, other software available
Manually initiated & Manually corrected
OOSEM – Methodology only
COTS Tool applied
Yes, Manual, if no tool used No
IBM Rational UP SE
Yes, Plug-In available
Yes, Plug-In available; services recommended
Yes, Third party
CORE
DoDAF Schema optional
Yes, automatic
State Analysis (SA)
October 2011

28. Tool Comparison at INCOSE 2011
Company
Name
Req
Drawing package
Functional
Simulation
Exchange Data -
Doors or other tool
CORE
Vitech
Yes
One way ( upload or download not integrated)
Cradle
3SL
One Way
Magic Draw
No Magic No
Yes – only a drawing package
No – but they intend to build an add-on
Rhapsody
IBM
Not really
Bi-directional but not really integrated
Team Center Unified
Siemens
Not Yet, but intend to.
One way, but really prefer you use their tool
October 2011

29. Tool Comparison at INCOSE 2011
Company
Name
Req
Drawing package
Functional
Simulation
Exchange Data
Doors or other tool
Cognitive Canopy
Cognitive?
Yes
Yes, some No
One way
Requim
Dissault
Yes, but not integrated
Maybe
No – High end Cad
Bi-directional not integrated
Arkitect
Knowledge Inside
Windchill
PTC
MD Workbench
Sodius
Bi directional. Needs manual start and verification
October 2011