Price: $3,999.90

Length: 4 Days
Print Friendly, PDF & Email

MBSE Training Crash Course

Model-Based Systems Engineering (MBSE) isn’t a one-size-fits-all solution or the end all be all of systems design.

MBSE is, however, an incredibly powerful tool that can probably help many organizations more than they might believe.

While MBSE is particularly popular in the aerospace industry, it’s a valuable tool for basically anyone. MBSE can work for federal organizations, corporations, and pretty much any entity interested in building any kind of software or system.

Additionally, MBSE can help model any kind of application – all the way from an airplane navigational system down to a mobile app to remind you to call someone.

Model-Based Systems Engineering (MBSE) is the practice of developing a set of related system models that help define, design, and document a system under development.

These models provide an efficient way to explore, update, and communicate system aspects to stakeholders, while significantly reducing or eliminating dependence on traditional documents.

MBSE is the application of modeling systems as a cost-effective way to explore and document system characteristics. By testing and validating system characteristics early, models facilitate timely learning of properties and behaviors, enabling fast feedback on requirements and design decisions.

MBSE is an important application that allows engineers to develop, analyze, and test complex systems. MBSE is also important because it provides a means to coordinate system design activity, satisfies stakeholder requirements and provides a significant return on investment.

While systems and software engineers find value in MBSE practices, surveys show that the customer is also finding value in MBSE practices.

In fact, multiple surveys demonstrate that MBSE practices are spreading beyond traditional Defense and Space domains. Most MBSE practitioners are finding MBSE is most useful in the early project phases of conceptualization, requirements analysis, and systems architecting.

Analysts report that benefits to using MBSE include:

  • Helping coordinate system design activities
  • Satisfying stakeholder requirements
  • Providing significant return on investment

Another part of the systems engineers’ job is to work with the customers and end-users who are paying for the product. They have “operational requirements” that must be satisfied so that they can meet their business needs. Otherwise they will no longer have a business.

MBSE tools can help analyze those requirements and manage them to ensure they are met at the end of the product development. Consequently, the systems engineer becomes the translator from the electrical engineers to the mechanical engineers to the computer scientists to the operator of the system to the maintainer of the system to the buyer of the system.

Each speaks a different language. The idea of using models was a means to provide this communications in a simple, graphical form.

MBSE Training Crash Course by Tonex

MBSE Training Crash Course covers all the principals, theories, and techniques associated with Model-based Systems Engineering (MBSE).

MBSE Training Crash Course

Model-based systems engineering (MBSE) is the formal use of modeling to provide system requirements, design, analysis, and verification and validation activities. Such activities initiate in the conceptual design stage and continue throughout development and later life cycle phases.

A model often provides various perspectives to serve different purposes.

MBSE Goals

  • Improved communications
  • With stakeholders
  • Within the engineering project teams
  • Across spoken language barriers
  • Improved quality
  • Early identification of requirements issues
  • Enhanced system design integrity
  • Improved specification of allocated requirements to hardware and software
  • Fewer errors during integration and testing
  • More rigorous requirements traceability
  • Consistent documentation
  • Increased productivity
  • Improved impact analysis of requirements changes
  • Improved interaction across a multi discipline team
  • Reuse of existing models to support design and technology evolution
  • Auto-generation of documentation
  • Reduced risk
  • Improved cost estimates
  • Early, and on-going, requirements validation and design verification

MBSE Techniques and Tools

  • Structured analysis and design
  • Data flow diagramming
  • State transition diagramming
  • Behavioral modeling
  • Entity relationship modeling
  • Finite element modeling
  • Environment virtualization
  • Computer Aided Design (CAD)
  • Analytical modeling
  • Process modeling

System Model

  • Requirements
  • Behavior
  • Structure
  • Properties
  • Interconnections

Audience

MBSE training crash course is a 4-day training designed for:

  • Product manager
  • Project director
  • R and D manager
  • Engineering manager
  • Systems engineer
  • Capability developer
  • Business analyst
  • Systems analyst
  • System architect
  • Enterprise architect
  • Software systems engineer
  • Software engineer
  • Design engineer
  • Hardware engineer
  • Project engineer
  • LSA specialist
  • Industrial engineer

Training Objectives

Upon completion of MBSE training crash course, the attendees are able to:

  • Comprehend the general principals of systems engineering
  • Discuss the main characteristic of a system
  • Understand the overall process factors, and their relationships, which together establish the bases of systems engineering
  • Relate the roles of developer as supplier, developer as creator and developer as acquirer, and to position their own roles, and those of their customers (internal and external) and suppliers (internal and external) within this framework
  • Perform the fundamentals of some of the more important techniques of system requirements analysis, development of physical solution, development of logical solution, evaluation of solution alternatives (trade-off studies) and design iteration
  • Discuss the principles and major techniques of engineering management in a systems project context
  • Demonstrate the fundamental skills to adjust the use of the systems engineering concepts and methods to different application scenarios
  • Explain the concepts and rational behind MBSE, and how it compares to traditional SE
  • Describe overall benefits of MBSE
  • Explain the application of MBSE in the industry
  • Comprehend SysML and that how it supports MBSE
  • Explain how MBSE methods are used to specify and design systems
  • Explain how an organization can transition to MBSE?

Course Outline

Overview

  • What is a system
  • Systems thinking
  • Applying systems thinking to systems design
  • What is systems engineering?
  • Multidisciplinary technique
  • Problem classes
  • The design space: three systems
  • The design space: boundaries
  • The process
  • Domains
  • Communication

The System Life Cycle and Solution Development

  • The solution domain: key concepts, relationships, information types and work products, MBSE
  • OCD/CONOPS/OSD/ADD issues
  • Architectural frameworks
  • Impact of problem definition and stakeholder satisfaction
  • Systems of systems engineering
  • Waterfall, incremental, evolutionary and spiral developments
  • Agile, lean and concurrent/simultaneous engineering

Systems Engineering Processes: Principles, Concepts and Components

  • System concepts
  • SE process principles & components
  • Requirements assessment
  • Development of physical solution description
  • Development of logical solution description MBSE
  • Effectiveness evaluation and decision
  • System elements – specification writing
  • System integration
  • Verification and validation
  • Engineering management

Requirements Analysis

  • What are requirements?
  • Various types of requirements, and how they relate to analysis, specification & design
  • Requirements quality qualities
  • Requirements languages: operational, formal
  • Requirements analysis (RA) – how to do it
  • MBSE in the problem domain
  • Requirements quality measures
  • Lean concepts in functional analysis for the product-oriented enterprise
  • ERA analysis, rest-of scenario analysis, out-of-range analysis, other constraints search, stakeholder value analysis
  • The Operational Concept Description (OCD)/CONUSE
  • Managing RA
  • Requirements analysis and management software tools

Development of the System Physical Solution Description (Synthesis)

  • Technology and innovation in solution development
  • Configuration items
  • Standards for selecting configuration items

Development of the System Logical Solution (MBSE in Design)

  • Rational representation classification
  • Functional analysis in design
  • Architecture process
  • Implementation risks
  • SysML, LML and other systems modeling languages
  • n-squared charts, behavior modeling, and other functional notations
  • Assessment and design software tools

What is A Model?

  • Components of a model
  • Characteristics of a model
  • Language: the systems model is language-based language of behavior
  • Managing complexity with language
  • Structure: the model expresses system relationships
  • Argument: the model is used to “prove” the concept of the design
  • Presentation: the model must be “viewable”

Model-Based Systems Engineering

  • Requirements for a systems engineering processes
  • MBSE model and system definition language developing layer 1 of our solution
  • Proceeding with layer 2
  • Architecture design at layer n
  • Verification and validation

MBSE Definitions & Advantages

  • International council on systems engineering (incose) definition & advantages
  • Model-Based Systems Engineering (MBSE) definition
  • Advantage to using MBSE
  • Sysml forum mbse definition & advantage
  • SysML forum MBSE definition
  • SysML forum MBSE advantage

INCOSE Systems Engineering Vision 2020

  • Vision 2020 integrating framework
  • Systems engineering vision
  • Role of MBSE within systems engineering vision 2020

MBSE Methodologies

  • INCOSE Object-Oriented Systems Engineering Method (OOSEM)
  • IBM rational telelogic harmony-se
  • IBM rational unified process for systems engineering (RUP-SE)
  • JPL State Analysis (Sa)
  • VITECH MBSE methodology
  • Dori Object-Process Methodology (OPM)
  • Weilkiens Systems Modeling Process (SYSMOD)
  • Fernandez ISE & Process Pipelines in OO Architectures (ISE&PPOOA)

MBSE Modeling Language Standards

  • SysML
  • UML

MBSE Software Tools

  • MBSE tools and relevance of other “de-facto” MBSE visual modeling standards
  • SAE Architecture Analysis and Designing Language (AADL)
  • Vitech Core
  • MagicDraw
  • Phoenix integration
  • IBM® RATIONAL® RHAPSODY®
  • Eclipse
  • ISIGHT & the SIMULIA execution engine

Lean Engineering

  • Lean Implementation Develops From TPS
  • Differences From TPS
  • Lean goals and strategy
  • Steps to achieve lean systems
  • How Can Lean Connect With MBSE

Hands-On activities

  • Labs
  • Individual/small group activities
  • Hands-on workshops

TONEX MBSE Hands-On Workshop Sample

  • Defining the problem
  • Studying the system and its components
  • Figuring out the relationship between the components and the entire system
  • Discussing the characteristics of the system
  • Modeling the system

MBSE Training Crash Course

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.