automotive spice general understanding and an insight into … · 2020-03-20 · definition of vda...

© tecmata GmbH© tecmata GmbH© tecmata GmbH

EMBEDDED ENGINEERING. FUNCTIONAL SAFETY. QUALITY!

Automotive SPICE®–

general understandingand an insight into version 3.0

Ingolstadt

21. September 2017


Embedded Software

Engineering and Test

Requirements-Engineering

Software Architectur /

Design

Implemen-tation

Modultest

Integrations-

test

Systemtest

Core Competencies

Functional Safety Process Management


Welcome

ASQF Section Automotive Bayern-Süd

Guest Speaker: Vera Gebhardt

Company: tecmata GmbH

ASQF Leader of safety+security section

SPICE - Software Process Improvement and Capability dEtermination

3


Automotive SPICEGeneral understanding

4


SPICE - Software Process Improvement and Capability dEtermination

5

Standard

is an international standard for performing a validation

of business processes focused on software development

Provides

SPICE provides a procedure for process assessments

Maturity

SPICE is now also been used for assessments of system

processes and organizational maturity


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

6


Complexity of systems

7

e.g. approximately 62 ECU`s E-Class

controllability of the complexity of electronic systems and the software

a particular challenge for vehicle manufacturers and suppliers


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

8


Scope

Assessment

9

Internal AssessmentFindings for SW-Process Improvement

External AssessmentRates the capability of a project

Supplier

ProcessProfile

Assess

ment

Process

Improvement

Supplier

Customer

Level 1,2,3,4,5

ServiceProvider

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


ISO 15504 Part 2 + exemplar PAM in Part 5

Assessment Process

Process Reference ModelPRM

PAMProcess Assessment Model

MeasurementFramework

Roles and Responsibilities

Improvement

Initial Input

Organisation/

Project

Part 2 normative elements - performing an assessment

Output

Rating & improvement successions

10

V2.5V

3.0/3.1

ISO/IEC 15504-5:2006 anexemplar PAM


Choose your processes?

A – Automotive SPICEH – HIS Scope

Management Process Group (MAN)Management Process Group (MAN)MAN.1 Organizational alignmentMAN.2 Organizational management

A H MAN.3 Project managementMAN.4 Quality management

A MAN.5 Risk managementA MAN.6 Measurement

Process Improvement Process Group (PIM)Process Improvement Process Group (PIM)PIM.1 Process establishmentPIM.2 Process assessment

A PIM.3 Process improvement

Organizational Life Cycle Processes

Resource and Infrastructure Process Group (RIN)Resource and Infrastructure Process Group (RIN)RIN.1 Human resource managementRIN.2 TrainingRIN.3 Knowledge managementRIN.4 Infrastructure

Reuse Process Group (REU)Reuse Process Group (REU)REU.1 Asset management

A REU.2 Reuse program managementREU.3 Domain engineering

Supply Process Group (SPL)Supply Process Group (SPL)A SPL.1 Supplier tenderingA SPL.2 Product release

SPL.3 Product acceptance support

Acquisition Process Group (ACQ)Acquisition Process Group (ACQ)ACQ.1 Acquisition preparationACQ.2 Supplier selection

A ACQ.3 Contract agreementA H ACQ.4 Supplier monitoring

ACQ.5 Customer acceptanceA ACQ.11 Technical requirementsA ACQ.12 Legal and administrative requirementsA ACQ.13 Project requirementsA ACQ.14 Request for proposalsA ACQ.15 Supplier qualification

Primary Life Cycle Processes

Engineering Process Group (ENG)Engineering Process Group (ENG)A ENG.1 Requirements elicitationA H ENG.2 System requirements analysisA H ENG.3 System architectural designA H ENG.4 Software requirements analysisA H ENG.5 Software designA H ENG.6 Software constructionA H ENG.7 Software integrationA H ENG.8 Software testingA H ENG.9 System integrationA H ENG.10 System testing

ENG.11 Software installationENG.12 Software and system maintenance

Operation Process Group (OPE)Operation Process Group (OPE)OPE.1 Operational useOPE.2 Customer support

Support Process Group (SUP)Support Process Group (SUP)A H SUP.1 Quality assurance A SUP.2 Verification

SUP.3 Validation A SUP.4 Joint review

SUP.5 AuditSUP.6 Product evaluation

A SUP.7 DocumentationA H SUP.8 Configuration managementA H SUP.9 Problem resolution managementA H SUP.10 Change request management

11

Supporting Life Cycle Processes


ORGANIZATIONAL Life Cycle Processes

Management Process Group (MAN)

MAN.3 Project management

HIS Scope

Engineering Process Group (ENG)

ENG.2 System requirements analysis

ENG.3 System architectural design

ENG.4 Software requirements analysis

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

PRIMARY Life Cycle Processes

Acquisition Process Group (ACQ)

ACQ.4 Supplier monitoring

HIS (Herstellerinitiative Software)

Scope refers those 15 processes requiredby OEMs

Without subcontractors: <>Elimination ofACQ.4 Supplier Monitoring

12


Automotive SPICE 3.0

13

Process Reference Model


Processes

Proceeding/Methods

Execution

Only 3 Steps

14


Process can be understood at three levels of abstraction

“Do it“- Plan, tailor, implement – compliant to the process model -generate input/output, measure results

15

“Hands on“

“Best Practice Guidance“


Method based development

16


PAM Insight

Outcomes of the

process

Purpose of the process

Base Practices

(Best Practices)

17


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 customerrequirements into a set of desired system technical requirements that will guide the design of the system

18


Tailoring means

Deviation of a project specific version

of the adequate standard process

using the instructions and the projects context

19


Tailoring on project level

Mandatory standard processes

Project processes Customer processes

Processes ajusted to the specific project conditions

20


6 Levels

Level 1 PerformedPA.1.1 Process Performance

Level 2 ManagedPA.2.1 Performance ManagementPA.2.2 Work Product Management

Level 3 EstablishedPA.3.1 Process DefinitionPA.3.2 Process Deployment

Level 4 PredictablePA.4.1 Process MeasurementPA.4.2 Process Control

Level 5 OptimizingPA.5.1 Process InnovationPA.5.2 Process Optimization

Level 0 Incomplete Incomplete Not structured processes / processes which not fulfill Automotive SPICE requirements

PredictableMetrics for the measurement and control of process performance and outcomes are applied

OptimizingQuantitative measures are implemented to continuously improve the process

EstablishedDefined processes are tailored to specific projects, resources are managed

PerformedProcesses are intuitively performed, incoming and outgoing work products exist

ManagedProcesses and work products are managed, responsibilities are identified

21


ASPICE Rating Scale

22

F Fully achieved>85%

There`s evidence of a complete and systematic approach, fullachivement of the defined process attribute – no significantweaknesses related to this process attribute exist in the assessedprocess

L Largely achived>50%L+ >67,5-85%L- >50-67,5%

There`s evidence of a systematic approach and significantachievement of the defined process attribute – Some weaknessesrelated to this process attribute may exist in the assessedprocess.

P Partially achieved>15%P+ >32,5-50%P- > 15-32,5%

There`s some evidence of an approach and some achievement ofthe defined process attributeSome aspects of achievement of the process attribute may beunpredictable

N Not achieved There`s little or no evidence of achievement of the definedprocess attribute

P- Many aspects of achievement of the process may be unpredictable

L- Many weaknesses related to this process attribute may exist…


Traceability

Traceability to MAN processes and vertical-horizontal traceability in Engineering

23


Traceability and Consistency APICE 3.0

24



25

The authors believe that, with the publication of the Automotive SPICE® Process Assessment Model, there is now more specific guidance available for the basis of process design and assessment in the Automotive Industry.


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)

26


Deployment and timeline

� Automotive SPICE 2.3 is still the version whichis 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

27


Timeline

ASPICE 3.0Published July 2015

Q3/ 2017

Yellow Book 2017 draft published Feb 2017Full draft AS 3.0 distributed for review, solved 592 external comments for yellow print�Transition phase to blue-gold print in 2018

28

Feb 2017

Minor Changes

Guideline Automotive SPICE

Review, Approval, Publication

ASPICE3.0

Draft Review

ASPICE3.1

Review, Publication blue/gold print is nearly done

Will bepublishedwith blue-gold print


3.0 Purpose

29

The Automotive SPICE® Process Assessment Model will be used to perform conformant assessments of the software process capability in the development of automotive systems in accordance with the requirements of ISO/IEC 33002.

The results of assessment are used for the identification of process improvements, for identifying risks in quality of a specific product release as well as a criterion for supplier selection.


� 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 themeasurment framework of ISO/IEC 33020 (ISO 15504 Harmonisation)

� Refinement of rating scale according to ISO/IEC 33020

Information to the Standard

30

© tecmata GmbH© tecmata GmbH© tecmata GmbH 31

� Definition of VDA Scope

� Interpretation / application guideline for assessors

� Detailed rating guideline (Level 1-3)

� Documented assessment process ASPICE

� Recommendations for performing an assessment

� Recommendations for reporting an assessment

� Requirements for assessor qualification

� Annex: Template for assessment scope definition for

different use cases

Content of the Automotive SPICE guideline


ISO/IEC 33004:2015

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

�process reference models,

�process assessment models, and

�maturity models

32


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/normativemodels 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 frameworksto 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 andthe extent to which a maturity model can be constructedusing elements from different process assessment models

33


Process assessment model relationship

34

Process performance indicators [BP, WP], which apply exclusively to capability Level 1. They provide an indication of the extent of fulfillment of the process outcomes.

Process capability [GP`s, GR`s], they provide an indication of the extent of fulfillment of the process attribute achievements.

Source: Automotive SPICE® PAM v3.0, July 16th, 2015, © VDA QMC


ISO/IEC 33020:2015

ISO/IEC 33020:2015 defines a process measurement frameworkthat supports the assessment of process capability,in accordance with the requirements of ISO/IEC 33003

The process measurement framework provides a schemathat 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

35


Process needs to meet defined goals

In the context of this and related standards, process capability is a process quality characteristicrelated 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

36



What`s new?

Some answers!

37


Plug in concept

= no HIS scope

38



Automotive SPICE 3.0 is now fully compliant to the requirements of the newISO/IEC 330XX series of standards.

The new version contains new key conceptswhich are explained in a separate annex, several clarifications regarding Level 1 base practices and a completely revised introduction.

39



All these changes have been made focussing onthe continuity of process assessments within the automotive domain

� regarding effort spent in an assessment,

� validity of assessment results and

� the fundamental understanding of the model

which is present in the community.

40


Some structural changes

ASPICE 2.5 ASPICE 3.0

ENG (Engineering processes) SYS (System Engineering), SWE (Software Engineering) acronymchanged

Unit construction and unitverification are one process

Unit construction process+ Unit verification process

No integration of HW andMechanical processes

Plug in concept allows integration ofHW/Mechanical processes

Known process names The name of some processes havechanged, but not their intention

Known reference standards,Traceability diagram Annex E

Updated references,Traceability diagram Annex D(will be shown on page 9)

41


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 aspossible verification criteria (interesting e.g. at architectural design)

42


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

Test Processes

Quality Assurance

Is simplified in general –Independence is still requiredObjectivity is added (because review ofwork products can`t be performedindependently)

Some examples of changed content

Dynamic behavior has to be explicitly addressed Evaluation of alternative solutions,according to defined criteriaRecorded evaluation result includes rational for the selection

Architectural Design

43

The process SWE.3 “Software Detailed Design and Unit Construction“ isseparated from the process SWE.4 “Software Unit Verification"

SW Detailed Design


Requirements for system qualification test

Explicit relationship between system quality test strategy and:

� regression test strategy� consistent with the project plan and with the release plan

New: test cases included in the system qualification test specification areselected according to the system qualification test strategy and theRelease plan [Outcome 3 of SYS.5]

New: test specification is suitable to provide evidence for compliance withsystem requirements (v.2_5: …that demonstrates compliance with SysRequ)

44


Traceability and consistency now splitted into twoBase Practices for all traceability of each process.

Refers:� of references or� links between work products

Supports:� coverage analysis, � impact analysis, � Status tracking of requirements

implementationConsistency:� nothing is missing (references/links)� References/links are correct� Proven by technical review

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

Traceability

45


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

46


Thank you for your attention!Questions?

Engineering Know How

Quality-Know How

ProcessKnow How

tecmata GmbHHagenauerstr. 57D-65203 Wiesbadenwww.tecmata.de

Vera GebhardtMain Branch Manager

� +49.611.971318-11 [email protected]

Product-Know How

47

automotive spice general understanding and an insight into … · 2020-03-20 · definition of vda...

Documents