Embraer’s Vision on Systems Engineering

Embraer’s Vision on

Systems Engineering

Presentation for theMeeting for INCOSE BRAZIL Chapter Creation

6-jun-2011 - André MayoralINCOSE member since 2008

Systems Engineering Challenges

• Propagate engineering information throughout the entire product life cycle

• Integrate knowledge from all internal stakeholders into the product development

• Increase the product maturity level at delivery time

• Increase the level of automation for mechanical, repetitive activities

• Anticipate defect detection during development

The nature of the challenges

TheEscalating

Cost of Errors

INCOSE Systems Engineering Handbook v. 3.2, 2010, from Defense Acquisition University.

Systems Engineering Revitalization: an Industry Perspective, DSP Conference, 8 March 2005,John B. Noblin

The Nature of our Approach

Facilitators:• Model-Based Systems Engineering Approach

• Simulation Tools

• Virtual Systems Integration and tests

• Test automation• Reuse

• Competencies

Time

Ra

te o

f D

efe

ct

dis

co

ve

ry

Releas

e to

field

Requir

emen

ts

Design

& b

uild

Releas

e to

test

Source: Safford, Software Technology Conference, 2000

Early Defect Identification and Correction

Defect Prevention

Our vision relies on models

Not only Model-based design, but Model-Based Development:

• Requirements specification / validation

• Design specification / verification

• Software development (requirements, design and V&V)

• Testing (enforcing test automation)

• Safety assessment

• Integration with CAE/CAD design

Continuous Verification and Validation

Component Test- at supplier -

Equipment Test- at a/c manufacturer -

- a/c ground test -

System Test- HIL rig test -

Aircraft

integration- Flight Test -

Component

requirements

Implementation

Model

Integrated

Model

Integrated

Model

Model

Verification

Req

Validation

Model

Verification

Req

Validation

Model

Verification

Req

Validation

Model

Integrated

Model

Model

Verification

Req

Validation

Model

Verification

Req

Validation

Model

Model

Verification

Req

ValidationAircraft

requirements

System

requirements

Equipment

requirements

Time

Defe

ct

rate

of

dis

co

very

Releas

e to f

ield

Requir

emen

ts

Design

& bu

ild

Releas

e to t

est

Model Simulation Models, to Simulation Models, to

anticipate:anticipate:

Analyses, verificationsAnalyses, verifications

• Propagates engineering info

• Integrates knowledge

• Product maturity

• Automation

• Early defect detection

Automatic Code

Generation

Addition of V to Y Transition

Time reduction

Larger initial effort due to

Model-based Design and

Model-based Testing

• Automation • Early defect detection

Maturity level that can be achieved

Rig testing

Desktop testing0 5 10 15 20

-0.5

0

0.5

1

1.5

2

2.5

3

obtained

expected

0 5 10 15 20278

280

282

284

286

288

290

gro

und s

peed [

kt]

obtained

expected

0 5 10 15 20-0.3

-0.2

-0.1

0

0.1

0.2

0.3

0.4

0.5

0.6

q [

deg/s

]

obtained

expected

0 5 10 15 201

1.5

2

2.5

3

3.5

4

4.5

obtained

expected

0 5 10 15 201

1.005

1.01

1.015

1.02

1.025x 10

4

- Z

dis

t [f

t]

obtained

expected

0 5 10 15 200

2000

4000

6000

8000

10000

Xdis

t [f

t]

obtained

expected

Functional and Geometric models integration

-6

-5

-4

-3

-2

-1

0

1

2

3

4

150 160 170 180 190 200 210 220 230 240 250 260 270 280 290 300 310 320 330 340 350 360 370 380 W101

W102

W104

MultipleMultiple FailureFailure ConditionsConditions to to bebe simulatedsimulated


• knowledge Integration


• Automation


Automation ofknowledge work

(mechanical and repetitive)

Systems and SW Development Processes

VERIFICATION & VALIDATIONVERIFICATION & VALIDATION

REQUIREMENTS, DESIGN, INTEGRATIONREQUIREMENTS, DESIGN, INTEGRATION

PROCESS DESCRIPTIONPROCESS DESCRIPTION

CHECKLISTSCHECKLISTS TEMPLATESTEMPLATES

GUIDELINESGUIDELINES

Sys/SWSys/SW Eng Eng ProcessProcess::

•• bestbest practicespractices,,

•• StdsStds::

•• ARP4754ARP4754

•• DODO--178B/C178B/C


• knowledge Integration



Process Maturity Construction Strategy

Process Development

ExercisesFeedback

Analysis

Prototype # 3

Prototype # 2

Prototype # 1

Product Maturity

comes from

Process Maturity

A Road of Continuous Improvement...

Time

De

fec

tra

te o

f d

isc

ove

ry

Releas

e to

field

Requir

emen

ts

Design

& b

uild

Releas

e to

test

Source: Safford, Software Technology Conference, 2000

Thank you

Obrigado,

Thanks!

Documents

Embraer’s Vision on Systems Engineering