Documente Academic
Documente Profesional
Documente Cultură
ZF confidential
Agenda
1. Motivation / Importance
2. ASPICE 3.1
3. ASPICE ratings and assessments
4. Process examples
© ZF Friedrichshafen AG
ZF confidential
Automotive SPICE Basic Training
1. Motivation / Importance
ZF confidential 3
What enabled that journey?
Complex network of electronic systems inside and around your vehicle
More lines of code than a fighter plane (SEI 2015):
F35 fighter plane – 35M LoC
Luxury car – 100M LoC
Where is all this code?
Powertrain – engine, gearbox, after-treatment
Chassis – Steering, ABS, ESC
Safety – airbag(s) and seat-belt systems
Driver Assistance – radar and cameras
Convenience - remote locking, keyless start, Smartphone integration 92 ECUs; 8Km wiring; 100M lines of code
© ZF Friedrichshafen AG
ZF confidential
Motivation - control complexity
Large international teams are needed for Product development
… ZF confidential
© ZF Friedrichshafen AG
5
The challenge of quality ...
Decisions we make today affect millions of vehicles in use for decades to come.
© ZF Friedrichshafen AG
ZF confidential
Motivation – Quality & product liability
Property damage
Environmental damage Warranty cost
ZF confidential
© ZF Friedrichshafen AG
7
7
Motivation – Continuous Process Improvement
ZF confidential
© ZF Friedrichshafen AG
8
8
Motivation – Reduce corrections / loss through
waste
The later changes (due to bugs or request) are done in the development life cycle, the more costly
and time-consuming the become.
cost
factor
© ZF Friedrichshafen AG
ZF confidential 9
Motivation – customer expectation & future business
OEMs define the Requirement that their electronic and software supplier
© ZF Friedrichshafen AG
ZF confidential 10
Motivation - Why are we using ASPICE?
Control complexity
Increasing lines of code and number of ECU in modern cars
International teams, interfaces need to be managed, team of expert groups
Achieve higher product liability
Avoid warranty efforts and
Damages due to your products
Reduce correction cost
Meet customer expectations and future business
OEMs define the Requirement that their Electronic and Software supplier have to attain Automotive SPICE Level 3
(minimum VDA scope). Automotive SPICE Level 2 or 3 are assumed meanwhile by OEMs.
Does the supplier fail these objective they are called to improve their development and engineering processes.
In case of identified risks (low attained capability levels), the supplier will get a business hold (C-Supplier rating)
and will be accounted with contractual penalties!
Continues improvement
Standardisation
© ZF Friedrichshafen AG
ZF confidential 11
Automotive SPICE Basic Training
2. ASPICE 3.1
ZF confidential 12
What is SPICE / Automotive SPICE
SPICE = Software Process Improvement and Capability Determination (SPICE (ISO
IEC 330XX family) international standard)
http://automotivespice.com/
VDA Band Automotive SPICE Deutsch
Only the english version is binding
© ZF Friedrichshafen AG
ZF confidential 13
Automotive SPICE – IS/ IS NOT
A Certification
A Product line or company capability determination (only applicable for Process execution in projects)
© ZF Friedrichshafen AG
ZF confidential
ASPICE V3.1 Process Map
© ZF Friedrichshafen AG
ZF confidential 15
ASPICE V3.1 Plug-in concept
© ZF Friedrichshafen AG
ZF confidential 16
Automotive SPICE Basic Training
3. ASPICE ratings and assessments
ZF confidential 17
Capability Level – the definition of SPICE level
Optimizing
Level 5 Optimizing
Systematic continuous improvements are executed, process data PA.5.1 Process Innovation
are measured that show the ‚Best practices‘ (Innovations). PA.5.2 Process Optimization
© ZF Friedrichshafen AG
ZF confidential
SPICE – two dimensional process scoring
© ZF Friedrichshafen AG
ZF confidential
Evaluation of Capability – Process capability level
SPICE Rating
A SPICE Level is achieved, once the PA is rated at least “L”.
The next Level can only be achieved, if all previous Levels are rated “F”
Capability level 1 2 3 4 5
Process attribute PA PA PA PA PA PA PA PA PA
Process 1.1 2.1 2.2 3.1 3.2 4.1 4.2 5.1 5.2
SYS.1 Requirements Elicitation F L L 2
SYS.2 System Requirements Analysis F F F L F 3
SYS.3 System Architectural Design F F F F L 3
SWE.1 Software Requirements Analysis P 0
SWE.2 Software Architectural Design L 1
SWE.3 SW Detailed Design & Unit Const. F F L 2
SWE.6 Software Qualification Test N 0
MAN.3 Project Management F N P 1
SUP.8 Configuration Management P 0
SUP.1 Quality Assurance P 0
ACQ.4 Supplier Monitoring F L F 2
F = Fully achieved L = Largely achieved P = Partially achieved N = Not achieved
© ZF Friedrichshafen AG
ZF confidential
What is a SPICE Assessment?
Assessment
© ZF Friedrichshafen AG
ZF confidential
Process Assessment approach
© ZF Friedrichshafen AG
ZF confidential 23
How does ASPICE affect our Work?
Consistency is Key!
© ZF Friedrichshafen AG
ZF confidential 24
ASPICE - Assessor Certification
iNTACS is an abbreviation for “International Assessor Certification Scheme”
and its primary objective is the standardization of assessor education and
certification. It is an independent and legally registered not-for-profit
organization
© ZF Friedrichshafen AG
ZF confidential
Automotive SPICE Basic Training
Process examples
ZF confidential 26
© ZF Friedrichshafen AG
4/22/2019 Engineering Quality Assurance, Process Handling ZF confidential
GEE Process Dimension in STAGES
Stages
© ZF Friedrichshafen AG
ZF confidential
MAN.3 Project Management
ZF confidential 29
MAN.3 Project Management
Process purpose:
The purpose of the Project Management Process is to identify, establish, and control the activities and
resources necessary for a project to produce a product, in the context of the project’s requirements
and constraints.
Process Outcomes:
1) the scope of the work for the project is defined;
2) the feasibility of achieving the goals of the project with available resources and constraints is
evaluated;
3) the activities and resources necessary to complete the work are sized and estimated;
4) interfaces within the project, and with other projects and organizational units, are identified and
monitored;
5) plans for the execution of the project are developed, implemented and maintained;
6) progress of the project is monitored and reported; and
7) corrective action is taken when project goals are not achieved, and recurrence of problems identified
in the project is prevented.
© ZF Friedrichshafen AG
ZF confidential
MAN.3 BP1 - Define the scope of work.
© ZF Friedrichshafen AG
ZF confidential
MAN.3.BP1 - Define the scope of work.
© ZF Friedrichshafen AG
ZF confidential 32