S P I R I T

Supplying value.

S P I R I TSS PP II RR TT I I SS

SV C RS NP4Margit Schifferl

June 2005Page 2

Introduction

Focus Spirit II Project Management Requirement Eng Test Process Quality Assurance Configuration Mgt

Spirit III Activities

Process Visualisation

Customer Feedback

SPIRIT Base Training - Overview


June 2005Page 3

Introduction




Customer Feedback

Motivation / History

VW Assessment in June/2002 with the result: SPICE level 0 on some of the process areas (SPICE is

from 0 … 5) Supplier level C ( not accepted for further business)

Conclusion: Short-term all processes which were assessed on SPICE

Level 1 Midterm all processes which were assessed on CMMI

Level 2 Long-term all processes which were assessed on CMMI

Level 3

Improvement program SPIRIT was stablished


June 2005Page 4

Introduction




Customer Feedback

Spirit 1 Spice 1

2002 2003 2004 2005

1

5

Spirit 1Rollout

Spirit 2 CMMI Level 2

Spirit 3 CMMI Level 3

2 Spirit 2 Rollout

Spirit 3 Rollout

4

3

5

“SPIRIT”Kick off

1

Important SPICE processes realised2

3 CMMI Level 2processes defined

4CMMI Level 3

processes defined

5 Siemens Process Assessment

Roadmap on SV C RS Process Improvement

Level 2 Level 3


June 2005Page 5

Introduction




Customer Feedback

Process Influences and Sources

SV C RS Process ImprovementDomains: HW, SW, Algo, Mech, Q, MC M M I

Inte

rna

lP

roc

ed

ure

s

Le

ga

lS

tan

da

rds

Ca

r Ma

nu

f.

TU

MR

EQ

M

CT

SE

3S

up

po

rt

Sy

ste

m-

&

Fu

nc

tio

n D

ev

.

SW

I@S

V

FINAL GOAL:CMMI LEVEL 3

Sp

irit 1+

2S

V I

nit

iati

ve

s(P

M,

QA

,..)


June 2005Page 6

Introduction




Customer Feedback

Focus of SPIRIT II

Requirements Eng.Architecture

Rbg: D. BrasinTSR: D. Macra

Web: W. RochowiakTro: Scott Morell

Test Process

Rbg: Th. LangnerTSR: C. Mihaly

Web: R. NovotniTro: Scott Morell

Project Management

Rbg: L. PfauTSR: M. Weickhmann

Web: K. TretterTro: D. Talbot

Quality Assurance

Rbg: P. GruenTSR: L. Margineanu

Web: R. NovotniTro: A. Ali

Configuration Management

Rbg: R. HamperlTSR: Z. Pall

Web: M. SeitzTro: K. Koshorek

Supplier Management

Rbg: M. Kiening

Requirements Engineering

DocumentationManagement

SW QualityAssurance

Problem Resolution

Transition from Phase I to Phase II

SP

IRIT

I S

PIR

IT II


June 2005Page 7

Introduction




Customer Feedback

Levels of Development

What does SV RS deliver to the customer?What does SV RS develop?

System consisting of eg.SRS + SAT + Rollover + …

Single Products, such as1 SRS unit, 2 Satellites, LIDAR, BSD …

Software, Hardware,Algorithm, Mechanic

HW component,SW code, …

Depending on the customer, SV C RS delivers systems consisting out of SRS and peripheral units or single products, completing the restraint system of the vehicle.

The products consist of Software, Hardware, Algorithm and Mechanic.

Hardware + Mechanic consists out of components, Software + Algo out of .c/.h files.


June 2005Page 8

Introduction




Customer Feedback

Levels of Development

Component

Discipline

Product

System

Siemens Restraint System has identified 4 Levels of Development.

These development levels are very important for process improvement:

How are requirements handled from top to down and bottom to top.

Tests for each level must be defined in scope and delimited to upper and lower levels.

Project Management and Quality Assurance has to be defined for relevant levels.

Support processes (eg. configuration management) must be installed.


June 2005Page 9

Introduction




Customer Feedback

Example

I want to have a restraint system, with front

airbags, side airbags, rollover curtains. Also

low- g crashes shall be detected.

Eric Customer

FunctionalityMain ECU Rollover Unit Early Crash SensorSatellite

SYSTEM

HW SW ... HW SW .... HW SW Algo HW SW Algo Mech


June 2005Page 10

Introduction




Customer Feedback

Project Management

Level 3(Discipl.)

Level 2(Product)

Level 1(System)

The Project Management Process:

lists all project management relevant activities

shows them sorted in the milestone plan

with adaptations for easier use in the development levels

PMPM

OpportunitySelection

Acquisition/Quotation Concept

Sample Verification /Design Validation

SublevelPhase 3a

SublevelPhase 3b

SublevelPhase 3c

SublevelPhase 3end

Introductionto Production

andValidation

ProductionRamp up

M0 M1 M2

M3a.x M3b.x M3c

M3 M4 M5

Key Points:

• Clear structure of roles for project team members and clear responsibilities

• Effort estimation and scheduling procedure embedded

• One project-wide Risk Mgmt


June 2005Page 11

Introduction




Customer Feedback

Requirements Engineering

Level 0(Vehicle)

Level 1(System)

Level 2(Product)

Level 3(Discipl.)

Level 4(Comp.)

Level 4(Comp.)

Level 3(Discipl.)

Level 2(Product)

Level 1(System)

Level 0(Vehicle)

Requirement Engineering defines:

Developm

ent Process

Test

Pro

cess

how requirements are derived (Method)

the way of requirements during development

the tracing of requirements (tool support)

Customer Customer

V-Cycle

trace

trace

trace

trace


June 2005Page 12

Introduction




Customer Feedback

Test Process

Level 4(Comp.)

Level 3(Discipl.)

Level 2(Product)

Level 1(System)

Level 0(Vehicle)

The Test Process defines:

Test

Pro

cess

timing and content of

for all development levels.Customer

test plan, test spec, test report

TestPlan

TestSpec

TestReport


June 2005Page 13

Introduction




Customer Feedback

Quality Assurance

Level 3(Discipl.)

Level 2(Product)

Level 1(System)

The Design Quality Assurance Process:

lists all development relevant quality activities

shows them sorted in the milestone plan

with adaptations for easier use in the development levels

QAQA

OpportunitySelection

Acquisition/Quotation Concept

Sample Verification /Design Validation

SublevelPhase 3a

SublevelPhase 3b

SublevelPhase 3c

SublevelPhase 3end

Introductionto Production

andValidation

ProductionRamp up

M0 M1 M2

M3a.x M3b.x M3c

M3 M4 M5

Key Points:

• Similar Q process for all development levels, separated in independent roles

• Responsibilities: Planning and Tracking for QA activities (eg. reviews), checking for process compliancy


June 2005Page 14

Introduction




Customer Feedback

Configuration Management

Configuration Management:

administers work products (documents) of the development. CM for

example maintains the codes of SW development.

CM consists basically out of 3 sub- topics:

Document Management … shows where documents are stored

Change Management … shows how changes are handled

Release Procedure … shows documents that needs to be released

Configuration Management is also a typical support process.

Key Points:

• Transparent structure for documents and work results

• One common Change and Error Management

• Tasks are supported by PVCS tools


June 2005Page 15

Introduction




Customer Feedback

SPIRIT III Activities

01 Process Definition and Maintenance:

"Set up organisational administration of our

processes"

02 Training

"Develop organisational management of

competences and training"

03 Metrics and Repository

"Align process measurement and analysis activities"

04 Function Development

"Development of reusable objects"

05 Internal Process Reviews

"Measure process conformance of

projects at RS using SPICE "

06 Completion of M and Q Workflow

"Complete process definition of

manufacturing and quality"

07 Doors Introduction

"Provide tool to support requirement engineering"

08 Functional Safety (IEC

61508)

"Analyze gaps between SPIRIT processes and

IEC61508"

09 SPIRIT 2 Process

Maintenance

"Continue roll out of SPIRIT II processes"

Legend : Organisational Project Level Internal Issue


June 2005Page 16

Introduction




Customer Feedback

How to get to the RS Process Web

Siemens VDO Home RS Page Process Web


June 2005Page 17

Introduction




Customer Feedback

Web based repository of processes

SiemensReference

Process House

SV C RSProcessVariants


June 2005Page 18

Introduction




Customer Feedback

Phase Oriented

Phase-view Diagram:

Shows all tasks between two milestones (=yellow rhomb).

Related tasks have the samecolour (eg. one colour for allproject management tasks).


June 2005Page 19

Introduction




Customer Feedback

Workflow-view Diagram:

Shows all related tasks overall milestones.

Related tasks are similar asregards content.(eg. engineering tasks)

Workflow Oriented

continued


June 2005Page 20

Introduction




Customer Feedback

Task Descripion

Workflow and Phasewhere/ when is this

task relevant

Roleswho is involved?

who is responsible (in bold letters)?

Inputwhat documentsare necessary

to start this task? Outputwhat document

should be issued with this task?

(link to templates)

Goalwhat aims the task?

Action/ Descriptionwhat items are

necessary to be performed?

Auxiliarieshow should it be done?

(link to method descriptions)


June 2005Page 21

Introduction




Customer Feedback

Process Support

RS Page


June 2005Page 22

Introduction




Customer Feedback

Customer Feedback

02 / 04 Ford Q-Labs: Excellent feedback – All processes >=

Spice Level 1

03 / 04 Siemens Interim Profile: CMMI Level 2.5

08 /04 Positive statements on our RE-Methode from DC

12 / 04 VW assessment: Upgrade as A-Supplier All processes >= Spice Level 2


June 2005Page 23

Introduction




Customer Feedback

Growing from "C" to "A":

VW assessment in June 2002

C supplier:"not able to deliver quality"

A supplier:"able to deliver quality"

VW assessment in December 2004

Assessment:Nissan

Assessment:Ford

Assessment:DaimlerChrysler

Assessment:Siemens AG (SIP)

Assessment:Siemens AG (SPA)

Documents

S P I R I T