ow systems engineering with sysml helps in complex systems … · 2019. 1. 2. · logical...

How Systems Engineering With SysML

Helps in Complex Systems Design?

Dr. Saulius Pavalkis

3DS (No Magic, Inc.)

Topics

1. What Drives Complexity Of New Systems Design?

2. Systems Engineering To Manage Complexity

3. Systems Engineering Framework And Method

4. Case Study

2

WHAT DRIVES COMPLEXITY OF NEW

SYSTEMS DESIGN?

3

New Systems Challenges: What Drives Complexity?

• Cyber Components (Electrical, Software, Mechanical)

• Software Centric

4


• Short Time to Market

5


• Limited Resources

6

A selection of the 23 cameras on NASA's 2020

Mars rover (Credit: NASA/JPL-Caltech)

NASA’s Curiosity rover

landed on Mars in 2012,

in part to analyze rocks to

see whether the Red

Planet was ever

habitable (or inhabited)

SYSTEMS ENGINEERING TO MANAGE

COMPLEXITY

7

“The formalized application of

modeling to support system

requirements, design analysis,

verification and validation

activities beginning in the

conceptual phase and continuing

throughout development and

later lifecycle phases.”

From the INCOSE SE Handbook Version 4

8

What is Model Based Systems Engineering (MBSE)?

What Makes MBSE Different

• It helps avoid catastrophic mistakes by enhancing and significantly lowering the costs of feasibility studies, tradeoff analysis, and impact analysis

• The entire specification set about the system that the model captures is an interconnected network of information

• As opposed to being spread out in non-searchable and non-navigable set of documents that require dedicated staff to manage

9

Today: Standalone models related

through documents

Future: Shared system model with multiple

views, and connected to discipline models

How do you do MBSE?

A modeling tool

A modeling method

A modeling language

MBSE is a combination of a

modeling language(s), a

methodology, a modeling tool,

and people that using

infrastructure apply Model

Driven Development in the

context of a particular

organization.

10

SysML Language

• Systems Modeling Language (SysML) is a graphical modeling language

for specification, analysis, design, verification and validation of

systems.

• Developed by OMG and INCOSE / Adopted by OMG in May 2006

• ISO Standard

• Cover the latest SysML version 1.5, active work is done on 2.0

11

UML 2 SysML

Not

required by

SysML

UML reused

by SysML

(UML4SysML)

SysML’s

extensions

to UML

Tutorial, specifications, papers, and

vendor info can be found on the

OMG SysML Website at

http://www.omgsysml.org/

System Model as an Integration Framework

12

© 2012-2014 by Sanford Friedenthal

12

An Interconnected Network of Information

13

SYSTEMS ENGINEERING FRAMEWORK AND

METHOD

14

System engineering process (V process)

Credits: Pawel Chadzynski & Michael Pfenning - MBSE and the Business of Engineering

15

Systems Engineering Activity

16

Synthesize

Physical

Architecture

Analyze

System

Requirements

Define

Logical

Architecture

Optimize &

Evaluate

Alternatives

Support

Validation &

Verification

Analyze

Stakeholder

Needs

Major SE Development Activities

Common Sub-activities (Automatic with MBSE)

•Critical parameters•Trade studies & analysis

•Test cases•Test procedures

•Causal analysis•Mission use cases/Scenario•Domain model

•System context•System use case/scenarios

•Logical decomposition•Logical scenarios•Logical subsystem interconnection

•HW/SW/Data architecture•Physical interconnection•System deployment

Manage

Requirements

Traceability

•Requirements Trace•Impact Analysis

System

Specificatio

n

MBSE Focus SE Activities

17

Tower. James. 2013. “ Model Based Systems Engineering ‘The State of the Nation’” INCOSE UK

ASEC 2013

MagicGrid

1818

Pillar

La

ye

ro

f A

bstr

actio

n

Requirements Behavior Structure Parametrics

Sp

ecific

atio

n

Co

nce

pt

Stakeholder NeedsUse

Cases

System

Context

Measurements of

Effectiveness

Pro

ble

m

System

RequirementsFunctional Analysis

Logical Subsystems

Communication

De

sig

n

So

lutio

n

Component

Requirements

Component

Behavior

Component

Structure

Component

Parameters

CASE STUDY

20

Case Study of CAR Climate Control

• The CAR Climate Control case study follows the MagicGrid

approach to describe the concept, problem, and Solution

• The model of the case study is based on SysML 1.4 and

created with MagicDraw CASE tool

2121

Stakeholder Needs

2222

Pillar

La

ye

ro

f A

bstr

actio

n


Co

nce

pt C1

Stakeholder

Needs

C2

Use Cases

C3

System Context

C4-P4 Measurements

of Effectiveness

Pro

ble

m

P1

System

Requirements

P2

Functional Analysis

P3

Logical Subsystems

Communication

So

lutio

n

S1 Component

Requirements

S2

Component Behavior

S3

Component

Structure

S4

Component

Parameters

Stakeholder Needs

• The cell represents information gathered from all the

stakeholders of the system

• It includes primary user requirements, government

regulations, policies, procedures, etc.

• The later refinements in the model make these

stakeholder needs structured and formalized

2323

Use Cases

2424

Pillar

La

ye

ro

f A

bstr

actio

n


Co

nce

pt C1

Stakeholder

Needs

C2

Use Cases

C3

System Context

C4-P4 Measurements

of Effectiveness

Pro

ble

m

P1

System

Requirements

P2

Functional Analysis

P3

Logical Subsystems

Communication

So

lutio

n

S1 Component

Requirements

S2

Component Behavior

S3

Component

Structure

S4

Component

Parameters

Use Cases

2626

System Context

2727

Pillar

La

ye

ro

f A

bstr

actio

n


Co

nce

pt C1

Stakeholder

Needs

C2

Use Cases

C3

System Context

C4-P4 Measurements

of Effectiveness

Pro

ble

m

P1

System

Requirements

P2

Functional Analysis

P3

Logical Subsystems

Communication

So

lutio

n

S1 Component

Requirements

S2

Component Behavior

S3

Component

Structure

S4

Component

Parameters

© 2016 No Magic, Inc. Exclusively for No Magic Use

System Context

2929

Measurements of Effectiveness (MoEs)

3030

Pillar

La

ye

ro

f A

bstr

actio

n


Co

nce

pt C1

Stakeholder

Needs

C2

Use Cases

C3

System Context

C4-P4 Measurements

of Effectiveness

Pro

ble

m

P1

System

Requirements

P2

Functional Analysis

P3

Logical Subsystems

Communication

So

lutio

n

S1 Component

Requirements

S2

Component Behavior

S3

Component

Structure

S4

Component

Parameters

Measurements of Effectiveness (MoEs)

3232

Pillar

La

ye

ro

f A

bstr

actio

n


Co

nce

pt C1

Stakeholder

Needs

C2

Use Cases

C3

System Context

C4-P4 Measurements

of Effectiveness

Pro

ble

m

P1

System

Requirements

P2

Functional Analysis

P3

Logical Subsystems

Communication

So

lutio

n

S1 Component

Requirements

S2

Component Behavior

S3

Component

Structure

S4

Component

Parameters

System Requirements

3333

System Requirements

3535

Pillar

La

ye

ro

f A

bstr

actio

n


Co

nce

pt C1

Stakeholder

Needs

C2

Use Cases

C3

System Context

C4-P4 Measurements

of Effectiveness

Pro

ble

m

P1

System

Requirements

P2

Functional Analysis

P3

Logical Subsystems

Communication

So

lutio

n

S1 Component

Requirements

S2

Component Behavior

S3

Component

Structure

S4

Component

Parameters

Functional Analysis

3636

Functional Analysis

3838

Functional Analysis

39

Pillar

La

ye

ro

f A

bstr

actio

n


Co

nce

pt C1

Stakeholder

Needs

C2

Use Cases

C3

System Context

C4-P4 Measurements

of Effectiveness

Pro

ble

m

P1

System

Requirements

P2

Functional Analysis

P3

Logical Subsystems

Communication

So

lutio

n

S1 Component

Requirements

S2

Component Behavior

S3

Component

Structure

S4

Component

Parameters

Logical Subsystems Communication

4040

Structure – Product Tree

42

Interfaces

43

Logical Subsystems Communication

4444

Pillar

La

ye

ro

f A

bstr

actio

n


Co

nce

pt

C1

Stakeholder

Needs

C2

Use Cases

C3

System Context

C4-P4 Measurements

of Effectiveness

Pro

ble

m

P1

Goals & Objectives

P2

Functional Analysis

P3

Logical Subsystems

Communication

So

lutio

n

S1 Component

Requirements

S2

Component Behavior

S3

Component

Assembly

S4

Component

Parameters

Component Assembly

4545

Component Assembly

4747

MagicGrid

4848

Pillar

La

ye

ro

f A

bstr

actio

n


Sp

ecific

atio

n

Co

nce

pt

Stakeholder NeedsUse

Cases

System

Context

Pro

ble

m

Goals & Objectives Functional Analysis Logical Subsystems

De

sig

n

So

lutio

n

Component

Requirements

Component

Behavior

Component

Assembly

Component

Parameters

Enable Traceability – Digital Thread

49

Conclusions

• Systems engineering support complex multidisciplinary systems design.

• Because of formalization and transparency MBSE with SysML and

method / framework support complex systems design automation and

integration.

• Requirements are no longer abstract text paragraphs. Now they are

formalized with models which allows efficient traceability and

optimization between stakeholder needs to electrical, software and

mechanical components even at the most complex systems.

5050

THANK YOU!

[email protected]

51

ow systems engineering with sysml helps in complex systems … · 2019. 1. 2. · logical...

Documents