▪ This session will be recorded

▪ Please use the Q&A tab for questions

▪ The event starts at 15.00hr CET

Model-Based Systems Engineering

Practical Use and Applications

Stephan van Beek Sebastien Dupertuis Michiel Schipper

Principal Application Engineer Senior Application Engineer Account Manager

Becky Petteys Danielle Li

Systems Engineering System Composer & Stateflow
Segment Manager Product Marketing Manager

© 2021 The MathWorks, Inc.

1
 Typical System Engineering Workflow
Stakeholder Requirements &
Requirements &
Needs Use Cases Use Cases
Highly Iterative
Respond to changes Highly Collaborative

Architecture:
Structure & Behavior

Optimize Communicate
Deliverables:
• Specifications
System • ICDs
Multiple Viewpoints
Characteristics • Reports
• Code
• More….

2
Polling time!

3
 Challenges in a System Engineering Workflow
Stakeholder Requirements &
Needs Use Cases

Difficulty responding to change

Hard to use
Steep learning curve Not Synchronized
Architecture:
Structure & Behavior

Not Analyzable Hard to use

Not Executable Steep learning curve Deliverables:
• Specifications
System • ICDs
Multiple Viewpoints
Characteristics • Reports
• Code
• More….

4
What is in System Composer?

Be Intuitive Tackle Complexity Facilitate Analysis Enable Implementation

5
Process used: Stakeholder Use Case
▪ (R)equirement
Needs Diagram WHY
▪ (F)unctional
▪ (L)ogical
▪ (P)hysical

Functional Functional
Requirements Architecture WHAT

System Logical
Requirements Architecture
WHO

Hardware Physical
Requirements Architecture WHERE
Requirement link
Allocation link 6
(1) Stakeholder Use Case
Stakeholder Req’s
Use-Cases Needs Diagram

Functional Functional
Requirements Architecture (3)
Software Architectures
(2) Deployment
Traceability Analysis
Functional layer
Logical layer System Logical Software
Physical layer
Requirements Architecture Architecture
Interfaces
Stereotypes
Analysis (static/simulation)
Allocation

Hardware Physical Physical

Requirements Architecture Architecture

Requirement link Allocation link Component reference 7

Case Study: Machine & Cooling System

▪ Design a system architecture for a production machine, its cooling system and
software architectures
– Machine needs to have a certain production throughput
– Operate needs to operate within a certain temperature range

8
(1) Stakeholder Use Case
Stakeholder Req’s
Use-Cases Needs Diagram

Functional Functional
Requirements Architecture (3)
Software Architectures
(2) Deployment
Traceability Analysis
Functional layer
Logical layer System Logical Software
Physical layer
Requirements Architecture Architecture
Interfaces
Stereotypes
Analysis (static/simulation)
Allocation

Hardware Physical Physical

Requirements Architecture Architecture

Requirement link Allocation link Component reference 9

Follow the Digital Thread from Stakeholder to Detailed Requirements
Traceability diagram
Use-case behavior
Detailed ‘refined’
Sequence requirement
Diagram
Statechart

Stakeholder

Stakeholder ‘needed’
requirement 10
 Validate and Understand Use-Case Behaviors through Simulation
Integrate Test Harness

Understand requirement
Integrated test through simulation

Test harness
harness

Explore behavior
with different
parameter inputs

11
(1) Stakeholder Use Case
Stakeholder Req’s
Use-Cases Needs Diagram

Functional Functional
Requirements Architecture (3)
Software Architectures
(2) Deployment
Traceability Analysis
Functional layer
Logical layer System Logical Software
Physical layer
Requirements Architecture Architecture
Interfaces
Stereotypes
Analysis (static/simulation)
Allocation

Hardware Physical Physical

Requirements Architecture Architecture

Requirement link Allocation link Component reference 12

 Function Decomposition and Requirements Traceability
Functional Architecture Implementation and
verification status

Import requirements
using ReqIF

System
Requirements Bi-directional
traceability
High-Level
Requirements

ReqIF

13
 Simulation to Validate Interfaces and Understand System Behavior
Logical Architecture
Integrate with Simulink,
Simscape and Stateflow

Enable models with simulation

to understand system behavior Validate interfaces
between components

Define interfaces and re-use

between models

14
Extend Modeling Language with Domain Specific Elements
Stereotype Properties and Profiles

Properties
with units and
checking
Extend graphical
language with domain
specific elements
15
 Calculate Fluid-flow Throughput
MATLAB-based analysis

30% Consumption rate A: 0.8 m^3/sec

30%
Consumption rate B: 0.5 m^3/sec Validate whether
requirements are met
through static analysis

Fluid A – 1.5 m^3/sec 40%

Fluid B – 2.2 m^3/sec 20%

Consumption rate margin =
Consumption rate -
(Throughput x Fluid rate)
30%
50%
16
Interactive Analysis and Assess Results in the Analysis Viewer

Stereotype Properties

Model Instance Hierarchy

(incl Ports, Connectors)

17
 Analysis as part of your Testing Framework (Test Manager)

Use custom parameters in

requirements to specify
threshold values

MATLAB unit tests to

programatically run the
analysis function

18
Describe Physical Platform in Architecture Diagrams
Physical Architecture

19
Model-to-Model Allocations Allocation between functional, logical and
physical architecture models

Autogenerated via MATLAB Report Generator® 20

(1) Stakeholder Use Case
Stakeholder Req’s
Use-Cases Needs Diagram

Functional Functional
Requirements Architecture (3)
Software Architectures
(2) Deployment
Traceability Analysis
Functional layer
Logical layer System Logical Software
Physical layer
Requirements Architecture Architecture
Interfaces
Stereotypes
Analysis (static/simulation)
Allocation

Hardware Physical Physical

Requirements Architecture Architecture

Requirement link Allocation link Component reference 21

Software Architecture Design

Control scheduling order for

simulation and implementation

Integrate with software

components in Simulink

Define and share interfaces

with system model

22
Use Stereotypes and Custom Views to Manage System Complexity

Views filtered by software

status as a class diagram

Stereotypes to specify custom

properties

23
Manage and Use Variants in System Architecture and Design Models

Active software variant

24
Test and Verify Software Components before Implementation

Integrated test
harness

Analyze simulation results

Enable models with simulation

to verify software components

25
Generate Traceable C/C++ Code

Generate C/C++ code

Model-to-Code
Code-to-Model
Traceability

26
Allocation and Analysis Software Components on Deployment Platforms
Memory need
Allocate software components
on physical platforms

2 deployment
strategies Analyze deployment impact
on memory

Core 1-4
Memory Memory not
Memory availability overloaded overloaded 27
Polling time!

28
Summary

1
▪ System Composer seamless integrates MBSE with 1
2
Requirements & Model-Based Design 2
3
1 4
▪ System Composer can be used in many existing 4
2
MBSE processes (e.g. RFLP) 5 5
3

▪ System Composer uses MATLAB Analytics 1

and Simulation to Analyze architectures 4 “Goals of System Composer are to
make system modeling easy, flexible,
and scalable; and to ease the transition to
3 the design environment. The features
▪ And ..... System Composer is easy to use ..... and constructs of System Composer reflect
5
the prioritization of these goals.”

29
Gulfstream Using System Composer to Model Electronic System
Architecture

“Goals of System Composer are to make

system modeling easy, flexible, and
scalable; and to ease the transition to the
design environment. The features and
constructs of System Composer reflect the
prioritization of these goals.”

PDF
Video

30
Training: System Composer for Architecture Modeling

After this 1-day training you will be able to:

▪ Identify the role of architectural modeling in System Composer

Model-Based Design Stereotypes

▪ Create functional, logical, and physical System

architectures Architecture

▪ Associate and tracking non-functional properties Views & Analysis &

Allocations Trade Studies
in architecture elements
▪ Analyze architecture models for early
requirement validation
▪ Generate architecture visualizations Design Manufacturing

Operations Testing

31
 Roles

Embedded Model-Based System

Proficiency Engineer Design Engineer Architect
Embedded Coder for
Production Code Generation
(2 days)
Advanced
System Composer for Architecture Modelling (1 day)

Simulink Model Management and Architecture (2 days)

Stateflow Fundamentals (2 days)

Fundamentals
Simulink Fundamentals (2 days)

Highlights MATLAB, Simulink, and Stateflow On-ramp (2 Hours each - FREE)

32
Q&A

33
Additional Resources

34
System Engineering: From Requirements to Architecture to Simulation

https://nl.mathworks.com/campaigns/offers/model-based-system-engineering.html
35
Systems Engineering introduction by Brian Douglas

https://www.youtube.com/playlist?list=PLn8PRpmsu08owzDpgnQr7vo2O-FUQm_fL 36
 System Composer Customer Adoption

Robert Bosch: Rolls Royce: Mercedes Benz:

System Architectural Design Our Journey Towards System Architecture Creation
According to Automotive SPICE Model-Based Product Lines Using System Composer
Using the MathWorks Toolchain

37