Mastering SysML and MagicGrid

for Systems Engineering

Constantin Neacsu, Brian Pepper, Bill Bentley

Dassault Systemes
 Instructor
Constantin Neacsu
CATIA CYBER SYSTEMS Industry Process Senior Specialist
Specializing in MBSE and CATIA Magic solutions
Extensive experience in SE in A&D sector
© Dassault Systèmes | 5/1/2024

Masters degree in Aeronautical & Aerospace Engineering

Live in London, UK

3
 Objectives
 Learn the modeling workflow defined by the MagicGrid
 Learn what SysML elements and views to use in each step of the workflow
 Learn how to organize the system model
 Get introduced to CATIA Magic software for model-base systems engineering
© Dassault Systèmes | 5/1/2024

(MBSE)

4
 Agenda (8:30 AM – 5:00PM)
1. Introduction 10. Solution Domain: Sub-System
2. MagicGrid overview Architecture
3. Problem Domain: Black Box 11. Practical Assignment #4
4. Practical Assignment #1 12. Solution Domain: Configuration
© Dassault Systèmes | 5/1/2024

5. Problem Domain: White Box 13. Practical Assignment #5

6. Practical Assignment #2 14. Wrap-up
7. Traceability 15. Q/A
8. Practical Assignment #3
9. Solution Domain: Logical System
Architecture

5
 Breaks
1. Coffee Break
2. Lunch Break (12:00 – 13:30)
3. Coffee Break
© Dassault Systèmes | 5/1/2024

6
 MBSE in the Context of the SE Lifecycle
 MBSE do not change the processes and activities of system development life cycle defined
by INCOSE
 They provide an approach to perform the activities and produce the SE Artifacts – the
conceptual and logical architecture of the system – using a tool and a semi-formal
language applied with a proper methodology.
© Dassault Systèmes | 5/1/2024

SysML models and artifacts

are generally developed as
part of the left side “leg” of
the SE “V” Model.
7
 © Dassault Systèmes | 5/1/2024

8
MBSE Enablers

CATIA Magic
 Motivation – Why Method?
 SysML is a language only
 Itprovides neither guidelines nor recommendations
© Dassault Systèmes | Confidential Information | 5/1/2024 | ref.: 3DS_Document_2020

for the modeling process

 MBSE method is necessary to address
the following questions:
 What is the modeling workflow?
 How to establish a coherent model structure?
 What views to build?
 What model artifacts to deliver?
 What roles are involved and what responsibilities
they take?
9
 © Dassault Systèmes | 5/1/2024

10
MagicGrid
 Explaining MagicGrid Layout
Pillar
Requirements Structure Behavior Parameters Safety & Reliability
White Box Black Box

Measures of Conceptual and

System Context Use Cases
View Specification Effectiveness Functional FMEA
© Dassault Systèmes | 5/1/2024

Problem

Stakeholder
Needs
Conceptual Conceptual
Functional Analysis MoEs for Subsystems
Subsystems Subsystems FMEA
Domain

System
System Structure System Behavior System Parameters System S&R
Requirements
Solution

Subsystem
Subsystem Structure Subsystem Behavior Subsystem Parameters Subsystem S&R
Requirements
Component
Component Structure Component Behavior Component Parameters Component S&R
Requirements
Impleme

Implementation
ntation

11
Requirements
 Related SysML Diagrams
Pillar
Requirements Structure Behavior Parameters Safety & Reliability
Black Box

Stakeholder System Context: Use Cases: Measures of Effectiveness Conceptual and

Needs: •Internal Block diagram (ibd) 1.Use Case diagram (MoEs): Functional FMEA:
Problem

•Requirements diagram 2.Activity diagram •Block Definition diagram (bdd) •FMEA table
•Requirements table
Conceptual Subsystems: Functional Analysis: MoEs for Subsystems: Conceptual Subsystems
© Dassault Systèmes | 5/1/2024

White

•bdd •Activity diagram •bdd FMEA:

Box

•ibd •FMEA table

System System Structure: System Behavior: System Parameters: System S&R:

Domain

Requirements: •bdd •State Machine diagram 1.bdd •bdd, ibd

•Requirements diagram •ibd •Activity diagram 2.Parametric diagram •State Machine, Activity, and
•Requirements table •Sequence diagram Sequence diagrams
•Parametric diagram
Solution

Subsystem Subsystem Structure: Subsystem Behavior: Subsystem Parameters: Subsystem S&R:

Requirements: •SA •SA •SA •SA
•SA

Component Component Structure: Component Behavior: Component Parameters: Component S&R:

Requirements: •SA •SA •SA •SA
•SA
SA = same as above
Implementation
Impleme
ntation

12 Requirements:
•SA
 Pillar
Requirements Structure Behavior Parameters Safety & Reliability

White Box Black Box Conceptual and

System Context Use Cases Measures of Effectiveness
Functional FMEA

Conceptual Architecture
Problem

Stakeholder
Needs
Conceptual Subsystems
Conceptual Subsystems Functional Analysis MoEs for Subsystems
FMEA
Domain

System
© Dassault Systèmes | 5/1/2024

System Structure System Behavior System Parameters System S&R

Requirements

Logical Architecture
Solution

Subsystem
Subsystem Structure Subsystem Behavior Subsystem Parameters Subsystem S&R
Requirements
Component
Component Structure Component Behavior Component Parameters Component S&R
Requirements
Implementation

Implementation
Requirements Physical Architecture
13
 Modeling Workflow
Pillar

Requirements Structure Behavior Parameters Safety & Reliability

White Box Black Box

Measures of Conceptual and

System Context Use Cases
Effectiveness Functional FMEA
Problem

Stakeholder
© Dassault Systèmes | 5/1/2024

Needs
Conceptual MoEs for Conceptual
Functional Analysis
Subsystems Subsystems Subsystems FMEA
Domain

System
System Structure System Behavior System Parameters System S&R
Requirements
Solution

Subsystem
Subsystem Structure Subsystem Behavior Subsystem Parameters Subsystem S&R
Requirements
Component
Component Structure Component Behavior Component Parameters Component S&R
Requirements
Impleme

Implementation
ntation

14
Requirements
 MagicGrid in SE Life Cycle

SoS Architecture System Architecture

(Conceptual to Logical)
© Dassault Systèmes | 5/1/2024

Business/Mission
Analysis
MagicGrid
Stakeholder Needs
and Requirements
System
Requirements
Architecture High Level
Design
Detail
Design
Implementation Integration Test Sustainment

System Design
(Logical to Physical)
15
 MagicGrid Templates and Samples
© Dassault Systèmes | 5/1/2024

16
 MagicGrid Book of Knowledge Ed.2
© Dassault Systèmes | 5/1/2024

https://discover.3ds.com/magicgrid-book-of-knowledge

17
 © Dassault Systèmes | 5/1/2024

18
Clients
 Sample SOI: Search Drone
© Dassault Systèmes | Confidential Information | 5/1/2024 | ref.: 3DS_Document_2020

19 Almalki, Faris & Othman, Soufiene. (2022). Modifying Hata-Davidson Propagation Model for Remote Sensing in Complex Environments Using a Multifactional Drone. Sensors.
 Pillar
Requirements Structure Behavior Parameters Safety & Reliability

White Box Black Box Conceptual and

System Context Use Cases Measures of Effectiveness
Functional FMEA

Conceptual Architecture
Problem

Stakeholder
Needs
Conceptual Subsystems
Conceptual Subsystems Functional Analysis MoEs for Subsystems
FMEA
Domain

System
© Dassault Systèmes | 5/1/2024

System Structure System Behavior System Parameters System S&R

Requirements
Solution

Subsystem
Subsystem Structure Subsystem Behavior Subsystem Parameters Subsystem S&R
Requirements
Component
Component Structure Component Behavior Component Parameters Component S&R
Requirements
Implementation

Implementation
Requirements

20
 Pillar
Requirements Structure Behavior Parameters Safety & Reliability

White Box Black Box Conceptual and

System Context Use Cases Measures of Effectiveness
Functional FMEA
Problem

Stakeholder
Needs
Conceptual Subsystems
Conceptual Subsystems Functional Analysis MoEs for Subsystems
FMEA
Domain

System
© Dassault Systèmes | 5/1/2024

System Structure System Behavior System Parameters System S&R

Requirements
Solution

Subsystem
Subsystem Structure Subsystem Behavior Subsystem Parameters Subsystem S&R
Requirements
Component
Component Structure Component Behavior Component Parameters Component S&R
Requirements
Implementation

Implementation
Requirements

21
 Problem Domain → Black-Box Analysis
 Aka operational analysis
 System of interest (SOI) is considered a black box
 Main goal – to define what the SOI shall do to fullfil the stakeholders expectations, that
is:
© Dassault Systèmes | 5/1/2024

 Interactionsbetween the SOI and its

environment (other systems, humans)
 Inputs and outputs of the SOI
 Black-box functions of the SOI
 Non-functional characteristics of the SOI

22
 Pillar
Requirements Structure Behavior Parameters Safety & Reliability

White Box Black Box Conceptual and

System Context Use Cases Measures of Effectiveness
Functional FMEA
Problem

Stakeholder
Needs
Conceptual Subsystems
Conceptual Subsystems Functional Analysis MoEs for Subsystems
FMEA
Domain

System
© Dassault Systèmes | 5/1/2024

System Structure System Behavior System Parameters System S&R

Requirements
Solution

Subsystem
Subsystem Structure Subsystem Behavior Subsystem Parameters Subsystem S&R
Requirements
Component
Component Structure Component Behavior Component Parameters Component S&R
Requirements
Implementation

Implementation
Requirements

23
 Stakeholder Needs
 User needs, regulations, policies, principles, and internal guidelines
to develop a system
 Interviews, questionnaires, discussions,
documents of various formats
© Dassault Systèmes | 5/1/2024

 Raw information:
Doesn’t need to be re-written!
Needs to be refined!!!

24
 Stakeholder Needs
Stakeholder needs can be captured directly in the SysML
model or retrieved from other digital sources
© Dassault Systèmes | 5/1/2024

Import/export

Each stakeholder need

 Have unique IDs ? via

 Can be grouped by source

 Can be categorized into functional and non-functional

25
 © Dassault Systèmes | Confidential Information | 5/1/2024 | ref.: 3DS_Document_2020

26
Stakeholder Needs – Sample

26
 Pillar
Requirements Structure Behavior Parameters Safety & Reliability

White Box Black Box Conceptual and

System Context Use Cases Measures of Effectiveness
Functional FMEA
Problem

Stakeholder
Needs
Conceptual Subsystems
Conceptual Subsystems Functional Analysis MoEs for Subsystems
FMEA
Domain

System
© Dassault Systèmes | 5/1/2024

System Structure System Behavior System Parameters System S&R

Requirements
Solution

Subsystem
Subsystem Structure Subsystem Behavior Subsystem Parameters Subsystem S&R
Requirements
Component
Component Structure Component Behavior Component Parameters Component S&R
Requirements
Implementation

Implementation
Requirements

27
 System Context
 A system context captures a unique operating environment which determines
an external view of the SOI, e.g., Coffee Machine in Airport or Vehicle in Use
 Context diagram (in form of SysML ibd) shows how the SOI interacts with
its environment (other systems, humans – SysML actors), to exchange data,
© Dassault Systèmes | 5/1/2024

matter, or energy
 In other words, this diagram captures inputs and outputs of the SOI
 Later on system contexts are used to group
use cases

28
 © Dassault Systèmes | Confidential Information | 5/1/2024 | ref.: 3DS_Document_2020

29
Interactions
System Context – Sample
 Pillar
Requirements Structure Behavior Parameters Safety & Reliability

White Box Black Box Conceptual and

System Context Use Cases Measures of Effectiveness
Functional FMEA
Problem

Stakeholder
Needs
Conceptual Subsystems
Conceptual Subsystems Functional Analysis MoEs for Subsystems
FMEA
Domain

System
© Dassault Systèmes | 5/1/2024

System Structure System Behavior System Parameters System S&R

Requirements
Solution

Subsystem
Subsystem Structure Subsystem Behavior Subsystem Parameters Subsystem S&R
Requirements
Component
Component Structure Component Behavior Component Parameters Component S&R
Requirements
Implementation

Implementation
Requirements

30
 Use Cases
 A use case captures the functional goal of the SOI that provides a certain value
for the stakeholder, e.g., Perform Mission, Provide Comfortable Temperature, Brew
Coffee
 Use cases refine functional stakeholder needs
© Dassault Systèmes | 5/1/2024

 A use case goes with a use case scenario in the form of SysML activity or
sequence diagram
 Each step of the scenario should be performed by one or another participant of the
related system context; participants are represented as swimlanes or lifelines
 Steps of performed by the SOI, are refered as black-box functions

31
 © Dassault Systèmes | Confidential Information | 5/1/2024 | ref.: 3DS_Document_2020

32
Use Cases – Sample
Participants of the system context

Interactions
 Pillar
Requirements Structure Behavior Parameters Safety & Reliability

White Box Black Box Conceptual and

System Context Use Cases Measures of Effectiveness
Functional FMEA
Problem

Stakeholder
Needs
Conceptual Subsystems
Conceptual Subsystems Functional Analysis MoEs for Subsystems
FMEA
Domain

System
© Dassault Systèmes | 5/1/2024

System Structure System Behavior System Parameters System S&R

Requirements
Solution

Subsystem
Subsystem Structure Subsystem Behavior Subsystem Parameters Subsystem S&R
Requirements
Component
Component Structure Component Behavior Component Parameters Component S&R
Requirements
Implementation

Implementation
Requirements

33
 Measures of Effectiveness
 A measure of effectiveness (MoE) captures a quantitative goal of the SOI,
expressed in the numerical format, e.g., total mass, stopping distance, noise level
 MoEs refine non-functional quantitative stakeholder needs and may refine some
functional stakeholder needs
© Dassault Systèmes | 5/1/2024

 MoEs are captured as value properties of the SOI block

 SysML bdd can be used to display them

34
 © Dassault Systèmes | Confidential Information | 5/1/2024 | ref.: 3DS_Document_2020

35
MoEs – Sample
 Pillar
Requirements Structure Behavior Parameters Safety & Reliability

White Box Black Box Conceptual and

System Context Use Cases Measures of Effectiveness
Functional FMEA
Problem

Stakeholder
Needs
Conceptual Subsystems
Conceptual Subsystems Functional Analysis MoEs for Subsystems
FMEA
Domain

System
© Dassault Systèmes | 5/1/2024

System Structure System Behavior System Parameters System S&R

Requirements
Solution

Subsystem
Subsystem Structure Subsystem Behavior Subsystem Parameters Subsystem S&R
Requirements
Component
Component Structure Component Behavior Component Parameters Component S&R
Requirements
Implementation

Implementation
Requirements

36
 Conceptual and Functional FMEA
 Failure Modes and Effect Analysis (FMEA) examines possible failures in your
systems
 Identifies conceptual and functional risks & failures for SOI and introduces
mitigations
© Dassault Systèmes | 5/1/2024

 Can start from Safety & Reliability Needs and functional risks and conclude with the
issuing of brand new mitigation needs/requirements
 New Safety Needs/Requirements are addressed through another iteration of the
black-box layer or additions to the white-box analysis

37
 © Dassault Systèmes | Confidential Information | 5/1/2024 | ref.: 3DS_Document_2020

38
Conceptual and Functional FMEA – Sample
 Practical Assignment #1
Given the stakeholder needs for the S&R Drone system:
a) Identify which of them are functional, which are not.
b) Identify the System Context and its components (SOI and actors)
c) Identify at least one (1) use case and decompose one (1) of them into black-box functions.
© Dassault Systèmes | 5/1/2024

d) OPTIONAL: Identify at least three (3) measures of effectiveness.

39
 Pillar
Requirements Structure Behavior Parameters Safety & Reliability

White Box Black Box Conceptual and

System Context Use Cases Measures of Effectiveness
Functional FMEA
Problem

Stakeholder
Needs
Conceptual Subsystems
Conceptual Subsystems Functional Analysis MoEs for Subsystems
FMEA
Domain

System
© Dassault Systèmes | 5/1/2024

System Structure System Behavior System Parameters System S&R

Requirements
Solution

Subsystem
Subsystem Structure Subsystem Behavior Subsystem Parameters Subsystem S&R
Requirements
Component
Component Structure Component Behavior Component Parameters Component S&R
Requirements
Implementation

Implementation
Requirements

40
 Problem Domain → White-Box Analysis
 Aka functional analysis
 SOI is considered a white box
 The main goal – to understand and define in detail what the SOI is expected to do, that is:
 Internal behavior of the SOI
© Dassault Systèmes | 5/1/2024

 Conceptual subsystems (aka functional blocks) and how they interoperate

with each other
 Inputs and outputs of each subsystem (they are delegated from the SOI)

 Results of the white-box analysis are actually system

requirements specification

41
 Pillar
Requirements Structure Behavior Parameters Safety & Reliability

White Box Black Box Conceptual and

System Context Use Cases Measures of Effectiveness
Functional FMEA
Problem

Stakeholder
Needs
Conceptual Subsystems
Conceptual Subsystems Functional Analysis MoEs for Subsystems
FMEA
Domain

System
© Dassault Systèmes | 5/1/2024

System Structure System Behavior System Parameters System S&R

Requirements
Solution

Subsystem
Subsystem Structure Subsystem Behavior Subsystem Parameters Subsystem S&R
Requirements
Component
Component Structure Component Behavior Component Parameters Component S&R
Requirements
Implementation

Implementation
Requirements

42
 Functional Analysis
 Continuation of use case analysis with focus on internal functions of SOI
(aka white-box functions)

 Enables to identify conceptual subsystems (aka functional blocks)

© Dassault Systèmes | 5/1/2024

responsible for different groups of functions

 Modeling tool can generate the functional

breakdown map

43
 © Dassault Systèmes | Confidential Information | 5/1/2024 | ref.: 3DS_Document_2020

44
Sample
Functional Analysis –
 Functional Decompsition Map – Sample
© Dassault Systèmes | Confidential Information | 5/1/2024 | ref.: 3DS_Document_2020

Use Case Scenario Black-box functions of System White-box functions of SOI

45
Context
 Pillar
Requirements Structure Behavior Parameters Safety & Reliability

White Box Black Box Conceptual and

System Context Use Cases Measures of Effectiveness
Functional FMEA
Problem

Stakeholder
Needs
Conceptual Subsystems
Conceptual Subsystems Functional Analysis MoEs for Subsystems
FMEA
Domain

System
© Dassault Systèmes | 5/1/2024

System Structure System Behavior System Parameters System S&R

Requirements
Solution

Subsystem
Subsystem Structure Subsystem Behavior Subsystem Parameters Subsystem S&R
Requirements
Component
Component Structure Component Behavior Component Parameters Component S&R
Requirements
Implementation

Implementation
Requirements

46
 Conceptual Subsystems (2/3)
 Conceptual subsystems, each responsible for some group of internal
functions captured in the functional analysis model, are identified
 Conceptual interfaces are identified and defined
 Communication between these subsystems is specified to define what data,
© Dassault Systèmes | 5/1/2024

matter, or energy they exchange

 Internal functions of the SOI are allocated to the conceptual structure of
the SOI, that is, grouped by functional blocks
 Further decomposition of functions and structure can
be performed

47
 © Dassault Systèmes | Confidential Information | 5/1/2024 | ref.: 3DS_Document_2020

48
Interfaces
Conceptual Subsystems – Sample
Subsystems
 © Dassault Systèmes | Confidential Information | 5/1/2024 | ref.: 3DS_Document_2020

49
Subsystems
Interactions
Conceptual Subsystems Communication – Sample
 Pillar
Requirements Structure Behavior Parameters Safety & Reliability

White Box Black Box Conceptual and

System Context Use Cases Measures of Effectiveness
Functional FMEA
Problem

Stakeholder
Needs
Conceptual Subsystems
Conceptual Subsystems Functional Analysis MoEs for Subsystems
FMEA
Domain

System
© Dassault Systèmes | 5/1/2024

System Structure System Behavior System Parameters System S&R

Requirements
Solution

Subsystem
Subsystem Structure Subsystem Behavior Subsystem Parameters Subsystem S&R
Requirements
Component
Component Structure Component Behavior Component Parameters Component S&R
Requirements
Implementation

Implementation
Requirements

50
 Allocating Behaviour to Structure
 Synchronise behaviour to structure, similar to Black-Box analysis, in reverse
 Add Swimlanes to SOI White-box Functional Decomposition
 Match Swimlanes to Conceptual Subsystems
© Dassault Systèmes | 5/1/2024

 SOI White Box Functions are allocated to SOI Conceptual Subsystems

51
 © Dassault Systèmes | Confidential Information | 5/1/2024 | ref.: 3DS_Document_2020

52
Interactions
Allocating Behavior to Structure – Sample
 © Dassault Systèmes | Confidential Information | 5/1/2024 | ref.: 3DS_Document_2020

53
Consistency of Behavior and Structure Models
 Pillar
Requirements Structure Behavior Parameters Safety & Reliability

White Box Black Box Conceptual and

System Context Use Cases Measures of Effectiveness
Functional FMEA
Problem

Stakeholder
Needs
Conceptual Subsystems
Conceptual Subsystems Functional Analysis MoEs for Subsystems
FMEA
Domain

System
© Dassault Systèmes | 5/1/2024

System Structure System Behavior System Parameters System S&R

Requirements
Solution

Subsystem
Subsystem Structure Subsystem Behavior Subsystem Parameters Subsystem S&R
Requirements
Component
Component Structure Component Behavior Component Parameters Component S&R
Requirements
Implementation

Implementation
Requirements

54
 Pillar
Requirements Structure Behavior Parameters Safety & Reliability

White Box Black Box Conceptual and

System Context Use Cases Measures of Effectiveness
Functional FMEA
Problem

Stakeholder
Needs
Conceptual Subsystems
Conceptual Subsystems Functional Analysis MoEs for Subsystems
FMEA
Domain

System
© Dassault Systèmes | 5/1/2024

System Structure System Behavior System Parameters System S&R

Requirements
Solution

Subsystem
Subsystem Structure Subsystem Behavior Subsystem Parameters Subsystem S&R
Requirements
Component
Component Structure Component Behavior Component Parameters Component S&R
Requirements
Implementation

Implementation
Requirements

55
 Conceptual Subsystems FMEA
 Identifies conceptual and functional risks & failures for SOI sub-systems and
introduces mitigations
 Can start from black-box resultant safety mitigations and concludes with the issuing
of brand new mitigation needs/requirements
© Dassault Systèmes | 5/1/2024

 New Safety Needs/Requirements are addressed through another iteration of the

white-box layer or additions to the logical solution analysis

56
 Practical Assignment #2

a) Take one of the black-box functions identified in previous practical assignment and
decompose it into the white-box functions.
© Dassault Systèmes | 5/1/2024

b) Identify conceptual subsystems (functional blocks) of the S&R Drone system and allocate
the white-box functions to them.

57
 Pillar
Requirements Structure Behavior Parameters Safety & Reliability

White Box Black Box Conceptual and

System Context Use Cases Measures of Effectiveness
Functional FMEA
Problem

Stakeholder
Needs
Refine
Conceptual Subsystems
Conceptual Subsystems Functional Analysis MoEs for Subsystems
FMEA
Domain

System
© Dassault Systèmes | 5/1/2024

System Structure System Behavior System Parameters System S&R

Requirements
Solution

Subsystem
Subsystem Structure Subsystem Behavior Subsystem Parameters Subsystem S&R
Requirements
Component
Component Structure Component Behavior Component Parameters Component S&R
Requirements
Implementation

Implementation
Requirements

58
 © Dassault Systèmes | Confidential Information | 5/1/2024 | ref.: 3DS_Document_2020

59
Sample
Traceability from PD > WB to Stakeholder Needs –
 Practical Assignment #3
Specify which white-box functions, conceptual subsystems (functional blocks), and MoEs you
have identified previously, refine each stakeholder need.
© Dassault Systèmes | 5/1/2024

60
 Pillar
Requirements Structure Behavior Parameters Safety & Reliability

White Box Black Box Conceptual and

System Context Use Cases Measures of Effectiveness
Functional FMEA
Problem

Stakeholder
Needs
Conceptual Subsystems
Conceptual Subsystems Functional Analysis MoEs for Subsystems
FMEA
Domain

System
© Dassault Systèmes | 5/1/2024

System Structure System Behavior System Parameters System S&R

Requirements

Logical Architecture
Solution

Subsystem
Subsystem Structure Subsystem Behavior Subsystem Parameters Subsystem S&R
Requirements
Component
Component Structure Component Behavior Component Parameters Component S&R
Requirements
Implementation

Implementation
Requirements

61
 Solution Domain
 A precise model of the logical (cross-
discipline) architecture and high-level
design of the system

 Provides one or more solutions for the

© Dassault Systèmes | 5/1/2024

problem domain definition

 Having several solutions, a trade-off

analysis can be performed to choose
the optimal one for implementing the
system

62
 Organizing Solution Domain Model
© Dassault Systèmes | 5/1/2024

63
 System Level Solution Domain Model
Pillar
Requirements Structure Behavior Parameters Safety & Reliability
White Box Black Box

Conceptual and
System Context Use Cases Measures of Effectiveness
Functional FMEA
Problem

Stakeholder
© Dassault Systèmes | 5/1/2024

Needs
MoEs for Subsystems Conceptual Subsystems
Conceptual Subsystems Functional Analysis
FMEA
Domain

System
System Structure System Behavior System Parameters System S&R
Requirements
Solution

Subsystem
Subsystem Structure Subsystem Behavior Subsystem Parameters Subsystem S&R
Requirements
Component
Component Structure Component Behavior Component Parameters Component S&R
Requirements
Implementation

Implementation
Requirements

64
 Pillar
Requirements Structure Behavior Parameters Safety & Reliability

White Box Black Box Conceptual and

System Context Use Cases Measures of Effectiveness
Functional FMEA
Problem

Stakeholder
Needs
Conceptual Subsystems
Conceptual Subsystems Functional Analysis MoEs for Subsystems
FMEA
Domain

System
© Dassault Systèmes | 5/1/2024

System Structure System Behavior System Parameters System S&R

Requirements
Solution

Subsystem
Subsystem Structure Subsystem Behavior Subsystem Parameters Subsystem S&R
Requirements
Component
Component Structure Component Behavior Component Parameters Component S&R
Requirements
Implementation

Implementation
Requirements

65
 System Requirements
 Results of the problem domain analysis are actually the system requirements
specification captured as SysML model
 They can serve as an input for producing the textual system requirements
specification
© Dassault Systèmes | 5/1/2024

 Just like stakeholder needs, system requirements

 Have unique IDs (different from stakeholder needs)
 Can be grouped by feature
 Can be categorized

System requirements refine problem domain and are derived from stakeholder
needs

66
 Pillar
Requirements Structure Behavior Parameters Safety & Reliability

White Box Black Box Conceptual and

System Context Use Cases Measures of Effectiveness
Functional FMEA
Problem

Stakeholder
Needs Refine
Conceptual Subsystems
Conceptual Subsystems Functional Analysis MoEs for Subsystems
Derive FMEA
Domain

System
© Dassault Systèmes | 5/1/2024

System Structure System Behavior System Parameters System S&R

Requirements
Solution

Subsystem
Subsystem Structure Subsystem Behavior Subsystem Parameters Subsystem S&R
Requirements
Component
Component Structure Component Behavior Component Parameters Component S&R
Requirements
Implementation

Implementation
Requirements

67
 © Dassault Systèmes | Confidential Information | 5/1/2024 | ref.: 3DS_Document_2020

68
System Requirements – Sample
 Pillar
Requirements Structure Behavior Parameters Safety & Reliability

White Box Black Box Conceptual and

System Context Use Cases Measures of Effectiveness
Functional FMEA
Problem

Stakeholder
Needs
Conceptual Subsystems
Conceptual Subsystems Functional Analysis MoEs for Subsystems
FMEA
Domain

System
© Dassault Systèmes | 5/1/2024

System Structure System Behavior System Parameters System S&R

Requirements
Solution

Subsystem
Subsystem Structure Subsystem Behavior Subsystem Parameters Subsystem S&R
Requirements
Component
Component Structure Component Behavior Component Parameters Component S&R
Requirements
Implementation

Implementation
Requirements

69
 System Structure: Logical System Architecture
 LSA model specifies all the
subsystems in a single-level hierarchy

 Purpose of LSA model – identify work

© Dassault Systèmes | 5/1/2024

packages and allocate them to

separate engineering teams

 Having the LSA model, the system

requirements can be updated

70
 © Dassault Systèmes | Confidential Information | 5/1/2024 | ref.: 3DS_Document_2020

71
Work packages
Work Packages and Traceability to PD – Sample
 Interfaces in LSA Model
 Interfaces are specified for each subsystem
 Purpose – determine how subsystems communicate with one
another and what data, energy, or matter they exchange. This is to
ensure consistency between proposed solutions at lower levels
© Dassault Systèmes | 5/1/2024

 Exchange items are also specified

72
 Pillar
Requirements Structure Behavior Parameters Safety & Reliability

White Box Black Box Conceptual and

System Context Use Cases Measures of Effectiveness
Functional FMEA
Problem

Stakeholder
Needs
Conceptual Subsystems
Conceptual Subsystems Functional Analysis MoEs for Subsystems
FMEA
Domain

System
© Dassault Systèmes | 5/1/2024

System Structure System Behavior System Parameters System S&R

Requirements
Solution

Subsystem
Subsystem Structure Subsystem Behavior Subsystem
We don’t usually define Parameters
system Subsystem S&R
Requirements
behavior in LSA
Component
Component Structure Component Behavior Component Parameters Component S&R
Requirements
Implementation

Implementation
Requirements

73
 Pillar
Requirements Structure Behavior Parameters Safety & Reliability

White Box Black Box Conceptual and

System Context Use Cases Measures of Effectiveness
Functional FMEA
Problem

Stakeholder
Needs
Conceptual Subsystems
Conceptual Subsystems Functional Analysis MoEs for Subsystems
FMEA
Domain

System
© Dassault Systèmes | 5/1/2024

System Structure System Behavior System Parameters System S&R

Requirements
Solution

Subsystem
Subsystem Structure Subsystem Behavior Subsystem Parameters Subsystem S&R
Requirements
Component
Component Structure Component Behavior Component Parameters Component S&R
Requirements
Implementation

Implementation
Requirements

74
 System Parameters
 System parameters capture quantitative characteristics of the SOI that
can be measured
 They are used to calculate MoEs identified during the problem domain
analysis
© Dassault Systèmes | 5/1/2024

 Mathematical expressions which define the derivation rules, can be

specified in the model

75
 © Dassault Systèmes | Confidential Information | 5/1/2024 | ref.: 3DS_Document_2020

76
System Parameters – Sample
 Pillar
Requirements Structure Behavior Parameters Safety & Reliability

White Box Black Box Conceptual and

System Context Use Cases Measures of Effectiveness
Functional FMEA
Problem

Stakeholder
Needs
Conceptual Subsystems
Conceptual Subsystems Functional Analysis MoEs for Subsystems
FMEA
Domain

System
© Dassault Systèmes | 5/1/2024

System Structure System Behavior System Parameters System S&R

Requirements
Solution

Subsystem
Subsystem Structure Subsystem Behavior Subsystem Parameters Subsystem S&R
Requirements
Component
Component Structure Component Behavior Component Parameters Component S&R
Requirements
Implementation

Implementation
Requirements

77
 System S&R
 Identifies risks, hazards and failures for SOI solution and introduces mitigations

 Can be in the shape of FMEA, HARA or FTA

 New Safety Requirements are addressed through another iteration of the current
layer or additions to other layers of the solution domain
© Dassault Systèmes | 5/1/2024

78
 © Dassault Systèmes | 5/1/2024

79
HARA – UAV Sample
 Pillar
Requirements Structure Behavior Parameters Safety & Reliability

White Box Black Box Conceptual and

System Context Use Cases Measures of Effectiveness
Functional FMEA
Problem

Stakeholder
Needs
Conceptual Subsystems
Conceptual Subsystems Functional Analysis MoEs for Subsystems
FMEA
Satisfy
Domain

System
© Dassault Systèmes | 5/1/2024

System Structure System Behavior System Parameters System S&R

Requirements
Solution

Subsystem
Subsystem Structure Subsystem Behavior Subsystem Parameters Subsystem S&R
Requirements
Component
Component Structure Component Behavior Component Parameters Component S&R
Requirements
Implementation

Implementation
Requirements

80
 Subsystem Level Solution Domain Model
Pillar
Requirements Structure Behavior Parameters Safety & Reliability
White Box Black Box

Conceptual and
System Context Use Cases Measures of Effectiveness
Functional FMEA
Problem

Stakeholder
© Dassault Systèmes | 5/1/2024

Needs
MoEs for Subsystems Conceptual Subsystems
Conceptual Subsystems Functional Analysis
FMEA
Domain

System
System Structure System Behavior System Parameters System S&R
Requirements
Solution

Subsystem
Subsystem Structure Subsystem Behavior Subsystem Parameters Subsystem S&R
Requirements
Component
Component Structure Component Behavior Component Parameters Component S&R
Requirements
Implementation

Implementation
Requirements

81
 Pillar
Requirements Structure Behavior Parameters Safety & Reliability

White Box Black Box Conceptual and

System Context Use Cases Measures of Effectiveness
Functional FMEA
Problem

Stakeholder
Needs
Conceptual Subsystems
Conceptual Subsystems Functional Analysis MoEs for Subsystems
FMEA
Domain

System
© Dassault Systèmes | 5/1/2024

System Structure System Behavior System Parameters System S&R

Requirements
Solution

Subsystem
Subsystem Structure Subsystem Behavior Subsystem Parameters Subsystem S&R
Requirements
Component
Component Structure Component Behavior Component Parameters Component S&R
Requirements
Implementation

Implementation
Requirements

82
 Applying MagicGrid Recursively

MagicGrid at System Level

MagicGrid at Subsystem/Component Level

Subsystem 1 (Supplier 1)
© Dassault Systèmes | 5/1/2024

Subsystem 2 (Supplier 2)

Subsystem 3 (Supplier 3)

83
 Pillar
Requirements Structure Behavior Parameters Safety & Reliability

White Box Black Box Conceptual and

System Context Use Cases Measures of Effectiveness
Functional FMEA
Problem

Stakeholder
Needs
Conceptual Subsystems
Conceptual Subsystems Functional Analysis MoEs for Subsystems
FMEA
Domain

System
© Dassault Systèmes | 5/1/2024

System Structure System Behavior System Parameters System S&R

Requirements
Solution

Subsystem
Subsystem Structure Subsystem Behavior Subsystem Parameters Subsystem S&R
Requirements
Component
Component Structure Component Behavior Component Parameters Component S&R
Requirements
Implementation

Implementation
Requirements

84
 Subsystem Structure: Logical Subsystem Architecture
 Separate engineering teams work in
parallel on logical architectures of
different subsystems
 Logical architecture of a subsystem
© Dassault Systèmes | 5/1/2024

starts by defining the internal structure

of the subsystem and specifying how
its parts communicate
 Multiple logical architectures of the
subsystem can be modeled

85
 Subsystem Structure - Sample
System Level (LSA)
Read-only
© Dassault Systèmes | Confidential Information | 5/1/2024 | ref.: 3DS_Document_2020

Subsystem Level (LSSA)

Inherited ports
and interfaces
Components

86
 Pillar
Requirements Structure Behavior Parameters Safety & Reliability

White Box Black Box Conceptual and

System Context Use Cases Measures of Effectiveness
Functional FMEA
Problem

Stakeholder
Needs
Conceptual Subsystems
Conceptual Subsystems Functional Analysis MoEs for Subsystems
FMEA
Domain

System
© Dassault Systèmes | 5/1/2024

System Structure System Behavior System Parameters System S&R

Requirements
Solution

Subsystem
Subsystem Structure Subsystem Behavior Subsystem Parameters Subsystem S&R
Requirements
Component
Component Structure Component Behavior Component Parameters Component S&R
Requirements
Implementation

Implementation
Requirements

87
 Subsystem Behavior
 A detailed behavior in form of the state
machine usually combined with with
activities and sequences, is specified
 Signals to exchange between
subsystems are used from the LSA
© Dassault Systèmes | 5/1/2024

model
 Behavior is not specified FOR ALL
structural parts of the system
 After subsystems behavior is specified,
the system configuration model can be
used for verifying how these subsystems
communicate over the compatible ports

88
 Subsystem Behavior – Sample
© Dassault Systèmes | Confidential Information | 5/1/2024 | ref.: 3DS_Document_2020

Signals from
the outside

Signals within the

Signal to the subsystem
other subsystem
89
 Pillar
Requirements Structure Behavior Parameters Safety & Reliability

White Box Black Box Conceptual and

System Context Use Cases Measures of Effectiveness
Functional FMEA
Problem

Stakeholder
Needs
Conceptual Subsystems
Conceptual Subsystems Functional Analysis MoEs for Subsystems
FMEA
Domain

System
© Dassault Systèmes | 5/1/2024

System Structure System Behavior System Parameters System S&R

Requirements
Solution

Subsystem
Subsystem Structure Subsystem Behavior Subsystem Parameters Subsystem S&R
Requirements
Component
Component Structure Component Behavior Component Parameters Component S&R
Requirements
Implementation

Implementation
Requirements

90
 Pillar
Requirements Structure Behavior Parameters Safety & Reliability

White Box Black Box Conceptual and

System Context Use Cases Measures of Effectiveness
Functional FMEA
Problem

Stakeholder
Needs
Conceptual Subsystems
Conceptual Subsystems Functional Analysis MoEs for Subsystems
FMEA
Domain

System
© Dassault Systèmes | 5/1/2024

System Structure System Behavior System Parameters System S&R

Requirements
Solution

Subsystem
Subsystem Structure Subsystem Behavior Subsystem Parameters Subsystem S&R
Requirements
Component
Component Structure Component Behavior Component Parameters Component S&R
Requirements
Implementation

Implementation
Requirements

91
 Subsystem S&R
 S&R requirements derived from the problem domain model, must be addressed in
the solution domain model
© Dassault Systèmes | Confidential Information | 5/1/2024 | ref.: 3DS_Document_2020

S&R requirement

S&R requirement

92
 Pillar
Requirements Structure Behavior Parameters Safety & Reliability

White Box Black Box Conceptual and

System Context Use Cases Measures of Effectiveness
Functional FMEA
Problem

Stakeholder
Needs
Conceptual Subsystems
Conceptual Subsystems Functional Analysis MoEs for Subsystems
FMEA
Domain

System
© Dassault Systèmes | 5/1/2024

System Structure System Behavior System Parameters System S&R

Requirements
Satisfy
Solution

Subsystem
Subsystem Structure Subsystem Behavior Subsystem Parameters Subsystem S&R
Requirements
Component
Component Structure Component Behavior Component Parameters Component S&R
Requirements
Implementation

Implementation
Requirements

93
 Pillar
Requirements Structure Behavior Parameters Safety & Reliability

White Box Black Box Conceptual and

System Context Use Cases Measures of Effectiveness
Functional FMEA
Problem

Stakeholder
Needs
Conceptual Subsystems
Conceptual Subsystems Functional Analysis MoEs for Subsystems
FMEA
Domain

System
© Dassault Systèmes | 5/1/2024

System Structure System Behavior System Parameters System S&R

Requirements
Solution

Subsystem
Subsystem Structure Subsystem Behavior Subsystem Parameters Subsystem S&R
Requirements
Component
Component Structure Component Behavior Component Parameters Component S&R
Requirements
Implementation

Implementation
Requirements

94
 Practical Assignment #4
• Create a State Machine to describe the behaviour of the Power Supply System.
• Create the necessary signals, activities and structural elements in the owning block.
© Dassault Systèmes | 5/1/2024

95
 System Level Configuration Model of the Solution Domain
Pillar
Requirements Structure Behavior Parameters Safety & Reliability
Black Box

Conceptual and
System Context Use Cases Measures of Effectiveness
Functional FMEA
Problem

Stakeholder
Needs
© Dassault Systèmes | 5/1/2024

White Box

MoEs for Subsystems Conceptual Subsystems

Conceptual Subsystems Functional Analysis
FMEA
Domain

System
System StructureConfig System BehaviorConfig System ParametersConfig System S&RConfig
Requirements
Solution

Subsystem
Subsystem Structure Subsystem Behavior Subsystem Parameters Subsystem S&R
Requirements
Component
Component Structure Component Behavior Component Parameters Component S&R
Requirements
Implementation

Implementation
Requirements

96
 Pillar
Requirements Structure Behavior Parameters Safety & Reliability

White Box Black Box Conceptual and

System Context Use Cases Measures of Effectiveness
Functional FMEA
Problem

Stakeholder
Needs
Conceptual Subsystems
Conceptual Subsystems Functional Analysis MoEs for Subsystems
FMEA
Domain

System
© Dassault Systèmes | 5/1/2024

System StructureConfig System BehaviorConfig System ParametersConfig System S&RConfig

Requirements
Solution

Subsystem
Subsystem Structure Subsystem Behavior Subsystem Parameters Subsystem S&R
Requirements
Component
Component Structure Component Behavior Component Parameters Component S&R
Requirements
Implementation

Implementation
Requirements

97
 System Configuration Structure
 System architect/integrator integrates the
models produced by different engineering
teams into the whole system configuration
model
 Multiple system configurations can be produced
© Dassault Systèmes | 5/1/2024

 Trade-off analysis is the mean to choose for the

optimal solution for implementation
 System model integrity can be verified by
executing it (simulation capabilities of the
modeling tool)
 Traceability to system requirements enables to
verify if all requirements are covered
 Knowing how to calculate MoEs values enables
early system verification against system
requirements (using the simulation capability of the
modeling tool)
98
 System Configuration Structure – Sample
System Level (LSA) Read-only
© Dassault Systèmes | Confidential Information | 5/1/2024 | ref.: 3DS_Document_2020

System Level (System Configuration) Inherited

information

Read-only Read-only Read-only

Subsystems Level (LSSAs)

99
 Pillar
Requirements Structure Behavior Parameters Safety & Reliability

White Box Black Box Conceptual and

System Context Use Cases Measures of Effectiveness
Functional FMEA
Problem

Stakeholder
Needs
Conceptual Subsystems
Conceptual Subsystems Functional Analysis MoEs for Subsystems
FMEA
Domain

System
© Dassault Systèmes | 5/1/2024

System StructureConfig System BehaviorConfig System ParametersConfig System S&RConfig

Requirements
Solution

Subsystem
Subsystem Structure Subsystem Behavior Subsystem Parameters Subsystem S&R
Requirements
Component
Component Structure Component Behavior Component Parameters Component S&R
Requirements
Implementation

Implementation
Requirements

100
 © Dassault Systèmes | Confidential Information | 5/1/2024 | ref.: 3DS_Document_2020

101
System Configuration Behavior – Sample
 Pillar
Requirements Structure Behavior Parameters Safety & Reliability

White Box Black Box Conceptual and

System Context Use Cases Measures of Effectiveness
Functional FMEA
Problem

Stakeholder
Needs
Conceptual Subsystems
Conceptual Subsystems Functional Analysis MoEs for Subsystems
FMEA
Domain

System
© Dassault Systèmes | 5/1/2024

System StructureConfig System BehaviorConfig System ParametersConfig System S&RConfig

Requirements
Solution

Subsystem
Subsystem Structure Subsystem Behavior Subsystem Parameters Subsystem S&R
Requirements
Component
Component Structure Component Behavior Component Parameters Component S&R
Requirements
Implementation

Implementation
Requirements

102
 © Dassault Systèmes | Confidential Information | 5/1/2024 | ref.: 3DS_Document_2020

103
System Configuration: System Parameters - Sample
 Pillar
Requirements Structure Behavior Parameters Safety & Reliability

White Box Black Box Conceptual and

System Context Use Cases Measures of Effectiveness
Functional FMEA
Problem

Stakeholder
Needs
Conceptual Subsystems
Conceptual Subsystems Functional Analysis MoEs for Subsystems
FMEA
Domain

System
© Dassault Systèmes | 5/1/2024

System StructureConfig System BehaviorConfig System ParametersConfig System S&RConfig

Requirements
Solution

Subsystem
Subsystem Structure Subsystem Behavior Subsystem Parameters Subsystem S&R
Requirements
Component
Component Structure Component Behavior Component Parameters Component S&R
Requirements
Implementation

Implementation
Requirements

104
 System Configuration S&R
 Identifies risks, hazards and failures for SOI solution configuration and introduces
mitigations
 Can be in the shape of FMEA, HARA or FTA

 New Safety Requirements are addressed through additions to individual solutions

© Dassault Systèmes | 5/1/2024

part of the configuration, or the overall configuration itself

105
 © Dassault Systèmes | 5/1/2024

106
FTA – UAV Sample
 Pillar
Requirements Structure Behavior Parameters Safety & Reliability

White Box Black Box Conceptual and

System Context Use Cases Measures of Effectiveness
Functional FMEA
Problem

Stakeholder
Needs
Conceptual Subsystems
Conceptual Subsystems Functional Analysis MoEs for Subsystems
FMEA
Domain

System
© Dassault Systèmes | 5/1/2024

System StructureConfig System BehaviorConfig System ParametersConfig System S&RConfig

Requirements Logical System
Architecture
Solution

Subsystem
Subsystem Structure Subsystem Behavior Subsystem Parameters Subsystem S&R
Requirements
Component Logical
Component
Trade-off Structure Component
Component Behavior Component Parameters Component S&R
Requirements Analysis
Models
Implementation

Integrated
Implementation System
Model(s)
Requirements

107
 Practical Assignment #5
• Create mass value properties and constraint for the S&R Drone and its Sub-Systems.
• Create a Satisfy relationship between the Mass Requirement and constraint.
• Create a parametric diagram to determine the Total Mass of the S&R Drone from its sub-
systems and simulate the diagram to verify requirement compliance.
© Dassault Systèmes | 5/1/2024

108
 Benefits of MagicGrid
 Gives user a clear idea what needs to be done and when
 Separates problem definition from solution architecture
 Clearly separates behavior model from structure model
© Dassault Systèmes | 5/1/2024

 Controls granularity of the model

 Provides both qualitative and quantitative views to the problem and solution
 Clarifies traces to be used among elements
 Can be applied partially – unnecessary cells can be skipped
 Can be applied recursively – starting from the subsystem level in the solution
domain model
109
 © Dassault Systèmes | 5/1/2024

110