Presentation is loading. Please wait.

Presentation is loading. Please wait.

Model Based Systems Engineering Tool Review – Comparison of Tools (201) 267-1152 Phil Simpkins, Senoir Systems Engineer

Similar presentations


Presentation on theme: "Model Based Systems Engineering Tool Review – Comparison of Tools (201) 267-1152 Phil Simpkins, Senoir Systems Engineer"— Presentation transcript:

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

2 October 2011 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

3 3 INCOSE Chapter Awards Bronze Circle

4 4 Where is the Chapter INCOSE Regions and Chapters

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

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

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

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

9 9 INCOSE 2012 in Rome, Italy July 09-12, 2012 INCOSE Philadelphia Future Symposia

10 Board of Directors Change Member Board Board of Directors

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

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

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

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

15 October 2011 System Engineer / Architect Program Management Configuration Management Publications Environmental Operations The Enterprise Team System Definition Repository Customer Chief Engineer Hardware Software Safety Reliability, Availability, Maintainability Manufacturability Security Test Logistics Maintenance Training & Personnel Facilitate domain expert collaboration by leveraging a common repository

16 Comparison of MBSE Methodologies o Telelogic Harmony-SE o INCOSE Object-Oriented Systems Engineering Method (OOSEM) o 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

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

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

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

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

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

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

23 October 2011 Vitech CORE Data verified by Source Requirements Domain Architecture Domain Behavior Domain V&V Domain verified by Originating requirements trace to behavior Originating requirements trace to physical components Behavior is allocated to physical components verified by Data Utilizing a layered approach to progressively clarify and elaborate all four domains concurrently to ensure consistency and completeness CORE System Definition Repository

24 Vitech CORE October 2011 Vitech MBSE "Onion Model"

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

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

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

28 Tool Comparison at INCOSE 2011 October 2011 ToolCompany Name Req Tool Drawing package Functional Simulation Exchange Data - Doors or other tool COREVitechYes One way ( upload or download not integrated) Cradle3SLYes One Way Magic Draw No MagicNoYes – only a drawing package No – but they intend to build an add-on One Way RhapsodyIBMNot really Yes Bi-directional but not really integrated Team Center Unified SiemensYes Not Yet, but intend to. One way, but really prefer you use their tool

29 Tool Comparison at INCOSE 2011 October 2011 ToolCompany Name Req Tool Drawing package Functional Simulation Exchange Data Doors or other tool Cognitive Canopy Cognitive?YesYes, someNoOne way RequimDissaultYes, but not integrated MaybeNo – High end Cad Bi-directional not integrated ArkitectKnowledge Inside NoYesNoOne way WindchillPTCNoYesNoOne way MD Workben ch SodiusYes Bi directional. Needs manual start and verification


Download ppt "Model Based Systems Engineering Tool Review – Comparison of Tools (201) 267-1152 Phil Simpkins, Senoir Systems Engineer"

Similar presentations


Ads by Google