THIS IS YOUR PRESENTATION TITLE - es.mathworks.com · automation here. There is a big confusion...

25
Systems Engineering Requires a Paradigm Shift YOGANANDA JEPPU

Transcript of THIS IS YOUR PRESENTATION TITLE - es.mathworks.com · automation here. There is a big confusion...

Page 1: THIS IS YOUR PRESENTATION TITLE - es.mathworks.com · automation here. There is a big confusion here on how to write requirements!! Remember: Models ARE NOT requirements!! THIS IS

Systems Engineering Requires a Paradigm Shift

YOGANANDA JEPPU

Page 2: THIS IS YOUR PRESENTATION TITLE - es.mathworks.com · automation here. There is a big confusion here on how to write requirements!! Remember: Models ARE NOT requirements!! THIS IS

SYSTEMS

ENGINEERINGA peep into history

Page 3: THIS IS YOUR PRESENTATION TITLE - es.mathworks.com · automation here. There is a big confusion here on how to write requirements!! Remember: Models ARE NOT requirements!! THIS IS

SYSTEMS

ENGINEERING

IS NOT NEW!

3

Aristotle – Metaphysica 330 BC

Page 4: THIS IS YOUR PRESENTATION TITLE - es.mathworks.com · automation here. There is a big confusion here on how to write requirements!! Remember: Models ARE NOT requirements!! THIS IS

4

PONT DU

GARD IN

FRANCE

(19 BC)

Page 5: THIS IS YOUR PRESENTATION TITLE - es.mathworks.com · automation here. There is a big confusion here on how to write requirements!! Remember: Models ARE NOT requirements!! THIS IS

THE TERM

SYSTEMS

ENGINEERING

CAN BE

TRACED TO

BELL

TELEPHONE

LABORATORIES

▸First attempt to

teach systems

engineering as

we know it today

came in 1950 at

MIT by Mr.

Gilman, Director

of Systems

Engineering at

Bell.

5

“today's systems may embed themselves

in history” - Ludwig von Bertalanffy

Page 6: THIS IS YOUR PRESENTATION TITLE - es.mathworks.com · automation here. There is a big confusion here on how to write requirements!! Remember: Models ARE NOT requirements!! THIS IS

SYSTEMS

ENGINEERING

PROJECTS OF

YORE

▸SAGE - Semi

Automatic

Ground

Environment air-

defense system

was defined and

managed by MIT

(1951 –1980)

6

Page 7: THIS IS YOUR PRESENTATION TITLE - es.mathworks.com · automation here. There is a big confusion here on how to write requirements!! Remember: Models ARE NOT requirements!! THIS IS

SYSTEMS HAVE

BECOME

COMPLICATED

OVER THE

YEARS

The earlier

Northrop XB-35

of the 1940s had

mechanical

controls. The B-2

of today has fly-

by-wire controls a

combination of

mechanical

electronics and

software.

7

Page 8: THIS IS YOUR PRESENTATION TITLE - es.mathworks.com · automation here. There is a big confusion here on how to write requirements!! Remember: Models ARE NOT requirements!! THIS IS

FAILURES HAVE

HAPPENEDSystems Engineering has failed us for some time now

Page 9: THIS IS YOUR PRESENTATION TITLE - es.mathworks.com · automation here. There is a big confusion here on how to write requirements!! Remember: Models ARE NOT requirements!! THIS IS

AS THE

SYSTEMS HAVE

BECOME

COMPLICATED

ACCIDENTS

HAVE

INCREASED

▸ The first error in 19629

Page 10: THIS IS YOUR PRESENTATION TITLE - es.mathworks.com · automation here. There is a big confusion here on how to write requirements!! Remember: Models ARE NOT requirements!! THIS IS

FAA

DIRECTIVE

TO

RESTART

BOEING 787

ENGINES TO

AVOID

OVERFLOW

ERROR

10

2015

Page 11: THIS IS YOUR PRESENTATION TITLE - es.mathworks.com · automation here. There is a big confusion here on how to write requirements!! Remember: Models ARE NOT requirements!! THIS IS

AIRBUS

A400M

CRASHES

DUE TO

ENGINE

FAILURE

11

2015

Four crew dead!!

Page 12: THIS IS YOUR PRESENTATION TITLE - es.mathworks.com · automation here. There is a big confusion here on how to write requirements!! Remember: Models ARE NOT requirements!! THIS IS

12

F-35 LIST OF

BUGS

PUBLISHED

IN REPORT

2016

Page 13: THIS IS YOUR PRESENTATION TITLE - es.mathworks.com · automation here. There is a big confusion here on how to write requirements!! Remember: Models ARE NOT requirements!! THIS IS

THERE HAVE

BEEN

FAILURES IN

OTHER FIELDS

TOO

13

Page 14: THIS IS YOUR PRESENTATION TITLE - es.mathworks.com · automation here. There is a big confusion here on how to write requirements!! Remember: Models ARE NOT requirements!! THIS IS

WE REQUIRE

SOMETHING Different

Page 15: THIS IS YOUR PRESENTATION TITLE - es.mathworks.com · automation here. There is a big confusion here on how to write requirements!! Remember: Models ARE NOT requirements!! THIS IS

“The world as we have

created it is a process of

our thinking. It cannot be

changed without changing

our thinking

-Albert Einstein”

15

Page 16: THIS IS YOUR PRESENTATION TITLE - es.mathworks.com · automation here. There is a big confusion here on how to write requirements!! Remember: Models ARE NOT requirements!! THIS IS

16

EFFORT

DISTRIBUTION

IN SYSTEM

DEVELOPMENT

Page 18: THIS IS YOUR PRESENTATION TITLE - es.mathworks.com · automation here. There is a big confusion here on how to write requirements!! Remember: Models ARE NOT requirements!! THIS IS

18

AN

INTERESTING

METRIC ON

THE PROCESS

TODAY

Cost of Fixing

Type Errors Found

Effort Spent/

Where errors found

Page 19: THIS IS YOUR PRESENTATION TITLE - es.mathworks.com · automation here. There is a big confusion here on how to write requirements!! Remember: Models ARE NOT requirements!! THIS IS

19

WE REQUIRE A

PARADIGM

SHIFT !

Page 21: THIS IS YOUR PRESENTATION TITLE - es.mathworks.com · automation here. There is a big confusion here on how to write requirements!! Remember: Models ARE NOT requirements!! THIS IS

MATHEMATIZE

THE LEFT

▸Model based representation

▸Property based requirements

▸Formal proof of correctness

of behavior

▸Validated control system in

the presence of noise,

modeling inaccuracy, data

ambiguity, faults

21

Page 22: THIS IS YOUR PRESENTATION TITLE - es.mathworks.com · automation here. There is a big confusion here on how to write requirements!! Remember: Models ARE NOT requirements!! THIS IS

AUTOMATE

THE RIGHT

▸Model based testing

▸Generate random test cases

▸Generate test cases using

Orthogonal arrays

▸Generate test cases using

formal methods

▸Generate test cases from

Mutants

▸Always measure coverage

22

Page 23: THIS IS YOUR PRESENTATION TITLE - es.mathworks.com · automation here. There is a big confusion here on how to write requirements!! Remember: Models ARE NOT requirements!! THIS IS

23

Requirements

Models

C/Ada

Make use of

Simulink

Blocks

Use

autocode

Requirement

based tests

Structural

Autotests

There is a little bit

of test case

automation here.

There is a big

confusion here

on how to write

requirements!!

Remember: Models

ARE NOT

requirements!!

THIS IS WHAT

WE DO TODAY

Page 24: THIS IS YOUR PRESENTATION TITLE - es.mathworks.com · automation here. There is a big confusion here on how to write requirements!! Remember: Models ARE NOT requirements!! THIS IS

24

THIS IS WHAT

WE NEED TO

DO NOW

Properties

Models

C/Ada

Use Simulink

blocks or any

other models

Definitely use

autocode

Property Based

Autotests

Structural

AutotestsContinue with

your

automated

testing

Bring in Property

Based

Requirements

Bring in Property

Based Testing

Page 25: THIS IS YOUR PRESENTATION TITLE - es.mathworks.com · automation here. There is a big confusion here on how to write requirements!! Remember: Models ARE NOT requirements!! THIS IS

25

Thank youAny questions?

You can find me at

[email protected]

Our system is only as good as the test cases we

have designed to prove it correct