date, location

© C

opyrig

ht Melexis M

icroelectronic In

tegrated

Syste

ms. A

ll Righ

ts Re

serve

d

We Engineer The Sustainable Future

Deploying Systems Engineering Methods

The Swiss Society of Systems Engineering Day 2015September 8, Zürich

A Case Study in Automotive Sensors Development

Gaël Close, PhDSystem Architect | Melexis | Bevaix, Switzerland

2

Micro-Systems and Systems-on-Chip

A system is a construct or collection of different elements that together

produce results not obtainable by the elements alone [...]. The value added by

the system as a whole, beyond that contributed independently by the parts, is

primarily created by the relationship among the parts; that is, how they are

interconnected (Rechtin, 2000).

ref: cypress-semiconductor

System-on-chip,Micro-systems (MEMS),Embedded Systems, ...

“There is plenty of room at the bottom”

Richard P. Feynman (1959)

3

Deploying Systems Engineering: Itinerary Overview

4

Outline

Quick overview of Melexis products (= Melexis “systems”)

Driving forces for Systems Engineering in automotive

electronics

Melexis systems engineering vision

Cornerstone: requirements management

System architecture design

System analyses (and executable models)

Testing and traceability

Achievements and remaining gaps

Conclusions

5

Quick overview of Melexis products

Melexis Supplies Worldwide Average 77 ICs / Car

SensingSensingSpeedSpeed

PositionPosition

CurrentCurrent

PressurePressure

TemperatureTemperature

LightLight

ImageImage

DrivingDrivingBLDC/DC Motor DriversBLDC/DC Motor Drivers

Smart DriversSmart Drivers

CommunicatingCommunicatingWired SW CAN, SENT and LINWired SW CAN, SENT and LIN

Wireless RF & RFID/NFCWireless RF & RFID/NFCCombining into Combining into

SystemsSystems

The contents of this presentation are CONFIDENTIAL AND PROPRIETARY. All Rights Reserved.

HMI

Sense (6)ASICs (1)

More than 50 unique standard products and 2 ASICsfor Safety & Comfort

Car Access

ADAS

ComfortSafety

Sense (3) Drive (6) Communicate (5)

Sense (14)Drive (12)Communicate (6)ASICs (1)Sense (12)

Communicate (1)

Sense (8)Communicate (9)Drive (3)

The contents of this presentation are CONFIDENTIAL AND PROPRIETARY. All Rights Reserved.

FuelManagement

Thermal Management

Air Management

Electrification & PowerManagement

EmissionManagement

Sense (7) Drive (4)

Sense (10)Drive (4)ASICs (3)

Sense (10) Drive (4)Communicate (5)ASICs (2)

Sense (13)Drive (4)ASICs (2)

Sense (6)Drive (5)

More than 40 unique standard products and 7 ASICsin Powertrain systems

9

Systems Engineering Driving Forces in Automotive Electronics

ref: http://www.rdmcoe.nl/futuremobility

10

Technology Driver for SE – “This Car Runs on Code”

A modern car contains more lines of software code than a new

787 Airliner (ref: R. Charette “This Car Runs on Code”, IEEE Spectrum, Feb. 2009).

Methods and techniques to manage complexity developed

initially in the Aeronautics and in the Software engineering

communities are rapidly gaining grounds in Automotive.

This is especially true for smart sensor and actuators—where

the hardware, software and the mechanics are all at play.

11

Technology Drivers for SE – Miniaturization

12

“The Best Process is No Process” !?

A definite process is a must when dealing with remote (large) teams, different disciplines, contractors, suppliers, ...

Ref: Prof. Eric Sax

13

Why Formalizing the System Engineering (SE) Process ?

Having a more mature living SE process, across an organization, improves project success probability

(mostly because issues are tackled early)

https://resources.sei.cmu.edu/asset_files/SpecialReport/2003_003_001_14117.pdf

“Give me six hours to chop down a tree and I will spend the first four sharpening the axe.”- Abraham Lincoln

14

Melexis Systems Engineering Vision

15

Shortcomings of Current Document-Centric Approach

16

To-be: Formalized Systems Engineering Methods & Tools

Pillars of Systems Engineering

Project management Work breakdown,

planning, follow up

Requirement definition management

System arch. design description

System analysis Safety-oriented FMEA, FTA

Performance simulation Integration & testing

18

System Development Life Cycle at Melexis

19

Requirements Management Requirements ⇒ Engineering

20

Polarion – the Cornerstone of our System Engineering Process

Requirement Management

Test case Management

Centralized technical documentation

Handles reviews, version control

Collaborative editing

Intuitive Word-like web-based

interface

But built atop a database, keeping track of

work items and their traceability (==> TAM) Requirements, Test cases, Blocks, ...

Handle re-use from one project to another

21

Organizing Requirements

22

Requirements reuse across variants

23

System Architecture Design

24

SysML (“extra-light”) for Architecture Description

25

Requirements Flow Down throughout the Architecture

26

System Analyses (and Executable Models)

27

Conceptual and Executable Models: Foundations for Analyses

Models supports analyses on both sides of the “Vee”

28

Modeling hierarchy and Refinement of System Models

29

System Design FMEA – to be Anchored to Architecture

30

Testing and Traceability

31

Test Cases Specification and Traceability

Test cases in HDL / circuit simulators

Test cases specifications

Test cases results back

annotated in SE database

Testing status reflected in treacability

matrix

32

Achievements and Remaining Gaps

33

Systems Engineering Vision Implemented in Database(pilot-phase)

34

Gaps

Small-scale pilot for now

Test case management across platforms:

Models / prototypes

Circuit simulators

Engineering sample characterization

High-volume manufacturing

Connection between Systems Engineering & project

management milestones

Identitication of right

people:

“T-shaped” engineers

http://asmarterplanet.com/

35

Systems Engineer Roles and Activities

Focus is on avoiding issues by

anticipating corrective actions.

Work products tend to be “paper-based”. ==> Not for everyone.

Conclusions

Deploying Systems Engineering in a journey Tailoring “textbook” practices to company workflow

Covers methodology and tools aspects Need for a cohesive System Engineering eco-systems, built on top of

existing workflows

The System Engineers are key Not easy to identify internally

or hire off the shelf

Journey can be frustrating Preparation is key

Positive outlook: the early adopters are seeing the light at the end of the tunnel (in the pilot projects)

– triggering Systems Engineering vocations