Length: 5 Days
Print Friendly, PDF & Email

Hands-on MBSE and SysML Training Workshop with Modelio

Hands-on-MBSE

Business team on business meeting discussion new project

The goal of an organization, when adopting MBSE, is to move from a document-centric to a data-centric practice of Systems Engineering (SE).

The idea behind this transformation is to realize the real intent of MBSE which is to develop, maintain, and manage a data and information model of the system being developed along with a model of all the system life cycle process activities, resulting artifacts, and their underlying data and information.

Most analysts will tell you that MBSE is not really about any particular type of model or visualization of data and information – whether that be a model, diagram, report, document, sets of needs, or sets of requirements – but is about the underlying data and information model that enables consistency across the data and information that represents the various models and visualizations.

Systems Modeling Language (SysML) is a general-purpose system architecture modeling language for systems engineering applications, commonly used in conjunction with MBSE. In fact, after a decade of pragmatic experience applying SysML to tough Systems Engineering problems, SysML has emerged as the de facto Model-Based Language choice for MBSE projects.

SysML supports the specification, analysis, design, verification, and validation of a broad range of systems and systems-of-systems.

These systems may include hardware, software, information, processes, personnel, and facilities.

Model Based Systems Engineering (MBSE) is well-known for improving quality, reducing risk and addressing complexity by enabling a system model to be viewed from multiple perspectives, and to analyze the impact of changes.

Complexity is often the root cause of systems engineering challenges. By using MBSE’s visual representation of the system, relationships between different parts of the system are easier to see and manage.

A common misconception about MBSE is that it replaces traditional systems engineering. It does not. It’s more like MBSE formalizes part of systems engineering. MBSE combines traditional methods and best practices with rigorous modeling techniques.

Formal systems models offer these benefits because they introduce additional consistency and continuity, and because they are understandable to both humans and computers, and logically verifiable.

It’s important to understand that when it comes to MBSE, one size doesn’t fit all. Experts in this area believe organizations need to assess their needs and produce an MBSE solution that best fits its domain, product line (degree of complexity), and culture.

At the very least, organizations turning to MBSE need to establish a capability to define and manage needs, requirements, verification, and validation across the system lifecycle.  These capabilities will allow the organization to build a data and information model of their products and systems engineering process activities and artifacts.

Based on these needs and desired capabilities, the organization can choose the appropriate SE toolset, update their processes, and train their people in these tools and processes.

Hands-on MBSE and SysML Training Workshop with Modelio

Hands-on MBSE and SysML Training Workshop with Modelio is a 5-day comprehensive training provides a solid foundation in MBSE project processes and how to build system models using SysML notation and diagrams. participants will learn how to use MBSE process and approach to create and build SysML diagrams to cover modern and agile systems engineering process steps including ConOps, Use Cases, Requirements, System Architecture and Design, Verification and Validation.

Modelio is the open source modeling environment to create SysML diagrams. An open source SysML modeling tool, Modelio SysML Architect, or Model-Based Systems Engineering (MBSE) applications.

The 5-day MBSE/SysML course teaches you how to implement essential MBSE and SysML modeling concepts through case studies, hands-on sessions and exercises with Modelio tool supporting Systems Modeling Language (SysML) modeling functional requirements, structural model, low level design model, behavioral model, parametrics & simulation.

Hands-on MBSE and SysML Training Workshop with Modelio: System Architecture and systems engineering. Create models with Modelio open source  to manage complex systems and system of systems (SoS)

Who Should Attend?

This course is designed for software and system engineers, scientists, analysts’ managers, technicians, and anyone else who wants to learn MBSE and SysML.

WHAT WILL YOU LEARN?

  • Explain the goals of Systems Engineering using Model Based System Applying MBSE approach to your project
  • Modern system engineering approach with SysML model constructs
  • Models in a Modelio SysML tool creating standard SysML diagrams
  • Engineering (MBSE) Approach
  • Learn the four pillars of MBSE: Requirements to Structure to Behavior to Parametrics
  • Learn how to create SysML diagrams
  • Explain SysML Diagram Taxonomy
  • Create with Requirement Diagram
  • Crate Behavioral Diagram: Use Case Diagram, Activity Diagram, Sequence Diagram, State Machine Diagram
  • Creating Structural Diagrams: Package Diagram, Block Definition Diagram, and Internal Block Diagram
  • Describe how to structure system models for testing, validation and requirements

Agenda/Modules

Overview of MBSE (Model Based Systems Engineering)

  • Principles of Modern Systems Engineering Principles
  • What is Model Based System Engineering (MBSE)
  • Principles of Systems Modeling Language (SysML)
  • SysML and MBSE
  • Systems modeling with MBSE and SysML systems diagrams

SysML Diagram Taxonomy

  • Behavioral Diagram
  • Activity Diagram
  • Sequence Diagram
  • State Machine Diagram
  • Use Case Diagram
  • Requirement Diagram
  • Structural Diagram
  • Block Definition Diagram
  • Internal Block Diagram
  • Package Diagram

Working with SysML

  • Structure: Definition and Use
  • Behavior: Interaction, State Machine, and activity/functions
  • Requirements
  • Parametrics
  • SysML Diagram Frames
  • Package Diagram
  • Internal Block Diagram
  • Allocations
  • Basic Structural elements

Creating Systems Modeling Language (SysML) Models

  • SysML Behavior Diagram
  • SysML Use Case Diagram
  • SysML Activity Diagram
  • SysML Sequence Diagram
  • SysML State Machine Diagram
  • SysML Requirements Diagram
  • SysML Parametric Diagram
  • Deploying MBSE and Models

Workshop (Hands-on Project with Modelio Tool)

  • Working with a critical system modeling example and functional analysis using MBSE and SysML
  • General Modeling Elements
  • Discipline-Specific Elements
  • Extended Requirement
  • Systems and Subsystems
  • Creating Structure and Concepts
  • Creating System Stakeholders (Actors)
  • The Use Case Diagram
  • Actor Categories
  • The Activity Diagram
  • The State Machine Diagram
  • Interaction Diagrams
  • The Requirement Diagram
  • Allocation
  • Block Diagrams
  • The Parametric Diagram
  • System Context Elements
  • System Processes
    • Model with Packages
    • Structure with Blocks
    • Constraints with Parametrics
    • Flow-Based Behavior with Activities
    • Message-Based Behavior with Interactions
    • Event-Based Behavior with State Machines
    • Functionality with Use Cases
    • Cross-Cutting Relationships with Allocations
  • Essential Activity
  • Domain Block
  • Weighted Requirement Relationships
  • Continuous and Secondary Use Cases

 

Hands-on MBSE and SysML Training Workshop with Modelio

Request More Information

Please enter contact information followed by your questions, comments and/or request(s):
  • Please complete the following form and a Tonex Training Specialist will contact you as soon as is possible.

    * Indicates required fields

  • This field is for validation purposes and should be left unchanged.

Request More Information

  • Please complete the following form and a Tonex Training Specialist will contact you as soon as is possible.

    * Indicates required fields

  • This field is for validation purposes and should be left unchanged.