Automotive SPICE®

Basic`s and
Overview v. 3.0

tecmata GmbH
Sulzbach, 09.05.2017

© tecmata
© tecmata GmbH
GmbH
 Core Competencies
Systemtest

Requirements- Integrations-
Engineering test

Embedded
Software
Functional Safety Engineering Process Management
and Test
Software
Architectur / Modultest
Design

Implemen-
tation

© tecmata
© tecmata GmbH
GmbH
 Agenda

SPICE - Software Process Improvement and

Capability dEtermination

Speaker: Vera Gebhardt

Company: tecmata GmbH

© tecmata
© tecmata GmbH
GmbH 3
 SPICE - Software Process Improvement and
Capability dEtermination

is an international standard for performing a validation

of business processes focused on software development

SPICE is now also been used for assessments of system

processes and organizational maturity

SPICE provides a procedure for process assessments

© tecmata
© tecmata GmbH
GmbH 4
 SPICE ?!?

SPICE is no product standard

SPICE specifies no procedure model

No methods or tools are specified or favored

The results may not be used in common (just in

context)

SPICE is not automatically a process improvement, but

it can be a basis for it

© tecmata
© tecmata GmbH
GmbH 5
 Complexity of systems

Source: with courtesy of method park AG

© tecmata
© tecmata GmbH
GmbH 6
 Motivation – YOUR Motivation?

Process
Assessment

leads to leads to
influence

Process
Process
Maturity
Improvement
?
Motivation

© tecmata
© tecmata GmbH
GmbH 7
 Important to understand

Process Assessment / Review Scope

Overall Results + Results for each Process

Proceeding with Level xy (0-5 Level)

General Remarks

An assessment is a snap shot in time based on samples

The rating of the Automotive SPICE processes

is NO rating for the adherence to the internally defined processes

Presentation contains only the most important aspects for improvement

© tecmata
© tecmata GmbH
GmbH 8
 Scope

Internal Assessment External Assessment

Findings for SW-Process Improvement Rates the capability of a project

Supplier
Supplier Level 1,2,3,4,5

Assessment
Assess
ment

Process
Process
Profile Improve Customer Service
ment
Provider

Automotive SPICE® is a registered trademark of VDA e.V.

© tecmata
© tecmata GmbH
GmbH 9
 ISO 15504 Part 2

Process Reference Model Measurement

PRM Framework

PAM
Process Assessment Model

Initial Input Output

Organisation/ Assessment Process Rating & improvement
successions
Project

Roles and Responsibilities

Improvement
Normative elements - performing an assessment
© tecmata
© tecmata GmbH
GmbH 10
 Choose your processes?
Primary Life Cycle Processes
Acquisition Process Group (ACQ) Support Process Group (SUP)
ACQ.1 Acquisition preparation A H SUP.1 Quality assurance
ACQ.2 Supplier selection A SUP.2 Verification
A ACQ.3 Contract agreement SUP.3 Validation
A H ACQ.4 Supplier monitoring A SUP.4 Joint review
ACQ.5 Customer acceptance SUP.5 Audit
A ACQ.11 Technical requirements SUP.6 Product evaluation
A ACQ.12 Legal and administrative requirements A SUP.7 Documentation
A ACQ.13 Project requirements A H SUP.8 Configuration management
A ACQ.14 Request for proposals A H SUP.9 Problem resolution management
A ACQ.15 Supplier qualification A H SUP.10 Change request management

Supply Process Group (SPL)

A SPL.1 Supplier tendering
Organizational Life Cycle Processes
A SPL.2 Product release Management Process Group (MAN)
SPL.3 Product acceptance support MAN.1 Organizational alignment
MAN.2 Organizational management
Engineering Process Group (ENG) A H MAN.3 Project management
A ENG.1 Requirements elicitation MAN.4 Quality management
A H ENG.2 System requirements analysis A MAN.5 Risk management
A H ENG.3 System architectural design A MAN.6 Measurement
A H ENG.4 Software requirements analysis
A H ENG.5 Software design Process Improvement Process Group (PIM)
A H ENG.6 Software construction PIM.1 Process establishment
A H ENG.7 Software integration PIM.2 Process assessment
A H ENG.8 Software testing A PIM.3 Process improvement
A H ENG.9 System integration
A H ENG.10 System testing Resource and Infrastructure Process Group (RIN)
ENG.11 Software installation RIN.1 Human resource management
ENG.12 Software and system maintenance RIN.2 Training
RIN.3 Knowledge management
Operation Process Group (OPE) RIN.4 Infrastructure
OPE.1 Operational use Reuse Process Group (REU)
OPE.2 Customer support REU.1 Asset management
A REU.2 Reuse program management
REU.3 Domain engineering
A – Automotive SPICE
© H – HIS
tecmata GmbHScope
© tecmata GmbH 11
 HIS Scope

PRIMARY Life Cycle Processes ORGANIZATIONAL Life Cycle

Acquisition Process Group (ACQ)

Processes HIS (Herstellerinitiative Software)
ACQ.4 Supplier monitoring
Management Process Group (MAN) Scope refers those 15 processes required
Engineering Process Group (ENG)
MAN.3 Project management
by OEMs
ENG.2 System requirements analysis

ENG.3 System architectural design

Without subcontractors: <>Elimination of
ENG.4 Software requirements
analysis ACQ.4 Supplier Monitoring
ENG.5 Software design

ENG.6 Software construction

ENG.7 Software integration test

ENG.8 Software testing

ENG.9 System integration test

ENG.10 System testing

SUPPORTING Life Cycle Processes

Support Process Group (SUP)

SUP.1 Quality Assurance

SUP.8 Configuration Management

SUP.9 Problem Resolution Management

SUP.10 Change Management

© tecmata
© tecmata GmbH
GmbH 12
 Only 3 Steps

Processes

Proceeding / Methods

Execution

Project

© tecmata
© tecmata GmbH
GmbH 13
 Manage Projects
“What“
Experience Follow the defined system and
software development principles and
observe the organizational culture
change. Maturity Models support to
understand „WHY“ and in which way
there is a professional context

Experience
“Hands on - Guidance“
Tools, Templates, Methods, Metrics,
“Best Practice Guidance“, Roles +
Skills, Tailoring Rules integrate in the
temporale relationships

“Do it“
Tailoring, Planning und Project
Risks
Implementation compliant to the
Project Costs
process model, generate measurements
results

© tecmata
© tecmata GmbH
GmbH 14
 Method based development

© tecmata
© tecmata GmbH
GmbH 15
 PAM Insight
Purpose of
the process

Outcomes
of the
process

Base
Practices
(Best
Practices)

© tecmata
© tecmata GmbH
GmbH 16
 Purpose of a process

e.g. MAN.3: General purpose is to identify, establish,

plan, coordinate and monitor the
activities, tasks, and resources in the context of
the project’s requirements and constraints

e.g. ENG.2: Purpose is to transform the defined customer

requirements into a set of desired system technical
requirements that will guide the design of the system

© tecmata
© tecmata GmbH
GmbH 17
 Tailoring means

Deviation of a project specific version

of the adequate standard process

using the instructions and the projects context

© tecmata
© tecmata GmbH
GmbH 18
 Tailoring on project level

Mandatory standard processes

Project processes Customer processes

Processes ajusted to the specific project conditions

© tecmata
© tecmata GmbH
GmbH 19
 6 Levels
Optimizing Level 5 Optimizing
Quantitative measures are implemented to PA.5.1 Process Innovation
continuously improve the process PA.5.2 Process Optimization

Predictable Level 4 Predictable

Metrics for the measurement and control of PA.4.1 Process Measurement
process performance and outcomes are applied PA.4.2 Process Control

Established Level 3 Established

Defined processes are tailored to PA.3.1 Process Definition
specific projects, resources are PA.3.2 Process Deployment
managed

Level 2 Managed Managed

Processes and work products are
PA.2.1 Performance Management
managed, responsibilities are identified
PA.2.2 Work Product Management

Level 1 Performed Performed

PA.1.1 Process Performance Processes are intuitively performed, incoming and
outgoing work products exist

Level 0 Incomplete Incomplete Not structured processes / processes which

not fulfill Automotive SPICE requirements
© tecmata
© tecmata GmbH
GmbH 20
 ASPICE in common

All processes according to V-Model

Mandatory to fulfill processes purpose

Create their outcomes work products…

… as result for fulfillment

Represent recommended activities for each process (BP`s)

© tecmata
© tecmata GmbH
GmbH 21
 Traceability

Traceability to MAN processes and vertical-horizontal traceability in Engineering

© tecmata
© tecmata GmbH
GmbH 22
 ASPICE some changes

Automotive SPICE 3.0

© tecmata
© tecmata GmbH
GmbH 23
 Timeline

Period 1 Period 2 Period 3

Transition Period

ASPICE 3.0 April 2017 Mid 2018

Published July 2015

Automotive SPICE 3.0 may be used for

assessments in agreement with the sponsor

© tecmata
© tecmata GmbH
GmbH 24
 3.0 Who`s working on it?

• Created by the Working Group 13 of the

Quality Management Center (QMC) within the (VDA)
• Represents members of the Automotive Special Interest Group (SIG) –
review only, and with the agreement of The SPICE User Group.
• This agreement is based on a validation of the Automotive SPICE 3.0
version - regarding any ISO copyright infringement and the statements
given from VDA QMC to the SPICE User Group

© tecmata
© tecmata GmbH
GmbH 25
 Deployment and timeline

Automotive SPICE 2.3 is still the version which

is considered mandatory by the VDA

Automotive SPICE versions 2.3 or 2.5 may still be used

Mandatory rules for the Automotive SPICE 3.0 transition are

decided by the VDA Quality Management Board with the
release of the new Blue/Gold Volume by VDA

© tecmata
© tecmata GmbH
GmbH 26
 Information to the Standard

ASPICE 3.0 comprises PRM and PAM on one single document/

(replaces PAM 2.5 and PRM 4.5)

Automotive SPICE 3.0 is yet not mandatory

ASPICE is no longer using ISO/IEC 12207 as guidance

Process CL and attributes adapted to the

measurment framework of ISO/IEC 33020
(ISO 15504 Harmonisation)

© tecmata
© tecmata GmbH
GmbH 27
 ISO/IEC 33004:2015

ISO/IEC 33004:2015 sets out the requirements for:

process reference models,

process assessment models, and

maturity models

© tecmata
© tecmata GmbH
GmbH 28
 ISO/IEC 33004:2015

The requirements defined in this International Standard form a structure

which specifies:

a) the relationship between the classes of process model

associated with the performance of process assessment,
b) the relationship between process reference models and prescriptive/normative
models of process performance, as constituted by, for example, the activities
and tasks defined in ISO/IEC 12207 and ISO/IEC 15288,
c) the integration of process reference models and process measurement frameworks
to establish process assessment models,
d) the use of common sets of assessment indicators of process performance and
process quality in process assessment models,
e) the relationship between maturity models and process assessment models and
the extent to which a maturity model can be constructed
using elements from different process assessment models

© tecmata
© tecmata GmbH
GmbH 29
 ISO/IEC 33020:2015

ISO/IEC 33020:2015 defines a process measurement framework

that supports the assessment of process capability,
in accordance with the requirements of ISO/IEC 33003

The process measurement framework provides a schema

that can be used to construct a process assessment model
conformant with ISO/IEC 33004 – which can be used
in the performance of assessment of process capability
according to the requirements of ISO/IEC 33002

© tecmata
© tecmata GmbH
GmbH 30
 Process needs to meet defined goals

In the context of this and related standards,

process capability is a process quality characteristic
related to the ability of a process to consistently meet
current or projected business goals.

The process measurement frameworks

defined in ISO/IEC 33020:2015 form a structure which:

a) facilitates self-assessment,
b) provides a basis for use in process improvement and
process quality determination,
c) is applicable across all application domains and sizes of organization,
d) produces a set of process (capability) attribute ratings (process profile),
e) derives a process capability level

© tecmata
© tecmata GmbH
GmbH 31
 Automotive SPICE 3.0

What`s new?

Some answers!

© tecmata
© tecmata GmbH
GmbH 32
 Plug in concept

= no HIS scope

© tecmata
© tecmata GmbH
GmbH 33
 Some structural changes
ASPICE 2.5 ASPICE 3.0
ENG (Engineering processes) SYS (System Engineering), SWE
(Software Engineering) acronym
changed
Unit construction and unit Unit construction process
verification are one process +
Unit verification process
No integration of HW and Plug in concept allows integration of
Mechanical processes HW/Mechanical processes

Known process names The name of some processes have

changed, but not their intention
Known reference standards, Updated references,
Traceability diagram Annex E Traceability diagram Annex D
(will be shown on page 9)

© tecmata
© tecmata GmbH
GmbH 34
Some examples of main changes

No planning aspects at Level 1 (of course not in MAN.3)

–> were available in 2.5 moved to Level 2

Proceeding is part of the strategy/plan

Qualification is explicit required (GP2.1.6)

Modifications on work product characteristics

Simulation is explicit mentioned as

possible verification criteria
(interesting e.g. at architectural design)

© tecmata
© tecmata GmbH
GmbH 35
 Some examples of changed content

Architectural Design Quality Assurance

Dynamic behavior has to be explicitly
addressed Is simplified in general –
Evaluation of alternative solutions, Independence is still required
according to defined criteria Objectivity is added (because review of
Recorded evaluation result includes work products can`t be performed
rational for the selection independently)

Test Processes
SYS.4, SYS.5, SWE.5, SWE.6 require, that
the selection of test cases is based on the
test strategy for the relevant test steps

© tecmata
© tecmata GmbH
GmbH 36
 Traceability
Traceability and consistency now splitted into two
Base Practices for all traceability of each process.
Refers: Supports:
of references or coverage analysis,
links between work products impact analysis,
Status tracking of requirements
Consistency: implementation
nothing is missing (references/links)
References/links are correct
Proven by technical review

New tracability requirements:

Traceability between test cases and results
Between change requests and wp`s (affected by these changes)

© tecmata
© tecmata GmbH
GmbH 37
 Automotive SPICE Objectives

Development of products which

– can be tested traceable and
– manage the complex line between mechanical design, hardware and
software ( = manage „systems“)

Processes which
– really can be used by and within the whole organisation and
– based on best practices
( = „Learning Organization“)

A development organisation which

– meets defined (performance) targets - measurable
– can respond quickly to deviations

An optimal management of complex system releases

Stable, functional and bug free mature products

© tecmata
© tecmata GmbH
GmbH 38
 Thank you for your attention!
Questions?
Ingenieur
Know How

Qualitäts- Prozess
Know How Know How

Produkt-
Know How

tecmata GmbH
Hagenauerstr. 57 Vera Gebhardt
D-65203 Wiesbaden Hauptniederlassungsleiterin
www.tecmata.de +49.611.971318-11
vera.gebhardt@tecmata.de

Thanks to methodpark for the slide support!

© tecmata
© tecmata GmbH
GmbH 39