supplying value. s p i r i t spirt i s. sv c rs np4 klaus heimerl jan-04 why process impr....
TRANSCRIPT
Supplying value.
S P I R I TSS PP II RR TT I I SS
SV C RS NP4Klaus Heimerl Jan-04
Why Process Impr.
Introduction
Requirements Eng.
Test Process
Project Management
Quality Assurance
Process Visualisation
Overview
Why Process Improvement?
Introduction
Requirements Engineering
Test Process
Project Management
Quality Assurance
Process Visualisation
SV C RS NP4Klaus Heimerl Jan-04
Why Process Impr.
Introduction
Requirements Eng.
Test Process
Project Management
Quality Assurance
Process Visualisation
Process Improvement at Restraint SystemsS P I R I T
Why Process Improvement ?
SV C RS NP4Klaus Heimerl Jan-04
Why Process Impr.
Introduction
Requirements Eng.
Test Process
Project Management
Quality Assurance
Process Visualisation
Why Process Improvement
Software
Hardware
Algorithm
Mechanic
ECU
ECU- development
SAT- development
RO- development
… - development
ECU+
SAT+
RO+…
Comparison of development – past and future
Past development for restraint systems required the synchronize 4 process
variants.
Actual and future restraint systems consist of higher
functionality; therefore synchronization of several independent development
process has to be considered.
To handle higher system complexity Process Improvement was conducted.
Why Process Impr.
Introduction
Requirements Eng.
Test Process
Project Management
Quality Assurance
Process VisualisationA/B ECU
g-Sat
Bat.
g-Sat
Sidebag Front (Thorax)
Front A/B
Belt Pretensioner(front)
Co
ckpit-In
strum
ent
Cockpit-Instrument (inc. Warning Lamps…)
Why Process Improvement
a past Restraint System in a car …
Why Process Impr.
Introduction
Requirements Eng.
Test Process
Project Management
Quality Assurance
Process Visualisation
Cockpit-Instrument (inc. Warning
lamps …)
A/B ECU
ECS
ECS
p-Sat
g-Sat
OC
Seat-Slide
Bat.
g-Sat
Buckle SwitchFront A/B (dual-stage)
Belt Pretensioner (rear)
Belt Pretensioner + Belt Force Limiter
(front)
AWS
ECU
Co
ckpit-
Instru
men
t
ISOFIX
Occupant Detection(OC)
FOSE
Weight Sensing
RO
S
Rollover Satellite
FOSElectronic
(PP)
Fiber OpticalSensor(FOS)
Actuator Pedestrian
Protection (PP)
p-Sat
p-Sat
PP ECU
Sidebag Front (Thorax)
Curtairbag Front (Head)
Sidebag Rear(Thorax)
Pedestrian Protection
ECU
p-Sat
CA
KC
AK
Seat-Slide
Crash activeheadrest
(front)
Why Process Improvement
an actual/ future Restraint System in a car …
SV C RS NP4Klaus Heimerl Jan-04
Why Process Impr.
Introduction
Requirements Eng.
Test Process
Project Management
Quality Assurance
Process Visualisation
Why Process Improvement
Comparison of development – the increasing importance of Software
Lines of Code- all systems in a car
1,0E+001,0E+011,0E+021,0E+031,0E+041,0E+051,0E+061,0E+071,0E+081,0E+09
1965 1970 1975 1980 1985 1990 1995 2000 2005
year
lin
es o
f co
de
The contribution of software to the electronical systems of a car will increase tremendously within the next years. To cope this challenge,
Software development must follow a defined process.
SV C RS NP4Klaus Heimerl Jan-04
Why Process Impr.
Introduction
Requirements Eng.
Test Process
Project Management
Quality Assurance
Process Visualisation
Process Improvement at Restraint SystemsS P I R I T
Introduction
SV C RS NP4Klaus Heimerl Jan-04
Why Process Impr.
Introduction
Requirements Eng.
Test Process
Project Management
Quality Assurance
Process Visualisation
Introduction
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, …
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.
SV C RS NP4Klaus Heimerl Jan-04
Why Process Impr.
Introduction
Requirements Eng.
Test Process
Project Management
Quality Assurance
Process Visualisation
Introduction
Component
Discipline
Product
System
Siemens Restraint System has identified 4 Levels of Development.
These development levels are very important for process improvement:
The Levels of Development
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.
SV C RS NP4Klaus Heimerl Jan-04
Why Process Impr.
Introduction
Requirements Eng.
Test Process
Project Management
Quality Assurance
Process Visualisation
Introduction
The Milestone Model:
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 M3a M3a
M3 M4 M5
The Milestone Model covers the phases between Opportunity
Selection and Production Ramp up. It is the base for all SV C RS
development processes covered by the process improvement SPIRIT.
SV C RS NP4Klaus Heimerl Jan-04
Why Process Impr.
Introduction
Requirements Eng.
Test Process
Project Management
Quality Assurance
Process Visualisation
Introduction
Development Source:
Customer SpecsStandards
Lessons LearnedWeak Point AnalysisTop System = Vehicle
. . .
Development and Testing
according to
Result:
RobustDesign
With a Robust Design, SiemensVDO Restraint System
is focused in achieving a zero defect product.
SV C RS NP4Klaus Heimerl Jan-04
Why Process Impr.
Introduction
Requirements Eng.
Test Process
Project Management
Quality Assurance
Process Visualisation
Process Improvement at Restraint SystemsS P I R I T
Requirements Engineering
SV C RS NP4Klaus Heimerl Jan-04
Why Process Impr.
Introduction
Requirements Eng.
Test Process
Project Management
Quality Assurance
Process Visualisation
How Customer explained his ideas
Project Manager understood:
Architecture results:
Implementation approach:
Consultant advice:
User Documentation:
Sample Delivery:
What Customer really needed:
Requirements Engineering
SV C RS NP4Klaus Heimerl Jan-04
Why Process Impr.
Introduction
Requirements Eng.
Test Process
Project Management
Quality Assurance
Process Visualisation
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
SV C RS NP4Klaus Heimerl Jan-04
Why Process Impr.
Introduction
Requirements Eng.
Test Process
Project Management
Quality Assurance
Process Visualisation
Process Improvement at Restraint SystemsS P I R I T
Test Process
SV C RS NP4Klaus Heimerl Jan-04
Why Process Impr.
Introduction
Requirements Eng.
Test Process
Project Management
Quality Assurance
Process Visualisation
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
SV C RS NP4Klaus Heimerl Jan-04
Why Process Impr.
Introduction
Requirements Eng.
Test Process
Project Management
Quality Assurance
Process Visualisation
Test Process
The Test Process defines also the sequence for documents and tests
System TestPlan
Product TestPlan
SW/HWTest Plan
M1 M2 M3ax M3bx M3cU
pdat
eP
lan
Upd
ate
Pla
nU
pdat
eP
lan Module
TestSpec
ModuleTests
Prod. Integr.Test Spec
Prod. Integr.Tests
Prod. Val.Test Spec
Prod. Val.Tests
Syst. Integr.Test Spec
Syst. Integr.Tests
con
tin
ued
Upd
ate
Pla
nU
pdat
eP
lan
Upd
ate
Pla
nSyst. Valid.Test Spec
Syst. Valid.Tests
SV C RS NP4Klaus Heimerl Jan-04
Why Process Impr.
Introduction
Requirements Eng.
Test Process
Project Management
Quality Assurance
Process Visualisation
Process Improvement at Restraint SystemsS P I R I T
Project Management
SV C RS NP4Klaus Heimerl Jan-04
Why Process Impr.
Introduction
Requirements Eng.
Test Process
Project Management
Quality Assurance
Process Visualisation
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
Project
Mgmt.
Project
Mgmt.
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 M3a M3a
M3 M4 M5
SV C RS NP4Klaus Heimerl Jan-04
Why Process Impr.
Introduction
Requirements Eng.
Test Process
Project Management
Quality Assurance
Process Visualisation
Process Improvement at Restraint SystemsS P I R I T
Design Quality Assurance
SV C RS NP4Klaus Heimerl Jan-04
Why Process Impr.
Introduction
Requirements Eng.
Test Process
Project Management
Quality Assurance
Process Visualisation
Design 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 M3a M3a
M3 M4 M5
SV C RS NP4Klaus Heimerl Jan-04
Why Process Impr.
Introduction
Requirements Eng.
Test Process
Project Management
Quality Assurance
Process Visualisation
Process Improvement at Restraint SystemsS P I R I T
Configuration Management
SV C RS NP4Klaus Heimerl Jan-04
Why Process Impr.
Introduction
Requirements Eng.
Test Process
Project Management
Quality Assurance
Process Visualisation
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.
SV C RS NP4Klaus Heimerl Jan-04
Why Process Impr.
Introduction
Requirements Eng.
Test Process
Project Management
Quality Assurance
Process Visualisation
Process Improvement at Restraint SystemsS P I R I T
Process Visualisation
SV C RS NP4Klaus Heimerl Jan-04
Why Process Impr.
Introduction
Requirements Eng.
Test Process
Project Management
Quality Assurance
Process Visualisation
Process Visualisation
Process Visualisation
provides a web based repository of processes
and is easy to use for the engineers
SV C RS NP4Klaus Heimerl Jan-04
Why Process Impr.
Introduction
Requirements Eng.
Test Process
Project Management
Quality Assurance
Process Visualisation
T H A N K Y O U .
SS PP II RR TT I I SS