Automotive SPICE® 3.

1
Software Development
Processes

Overview VDA
Automotive SPICE®
Guideline

Kugler Maag Cie GmbH

© KUGLER MAAG CIE GmbH

Page 1
 Agenda
• Structure of the VDA Guideline

• Understanding the purpose of rating rules and recommendations

• Understanding the terminology of rating rules and recommendations

• Understanding the concept of dependencies within the PAM

Page 2
 Structure of the VDA Guideline

Page 3
 Structure of the VDA Guidelines
The VDA Guidelines consist of two major elements:

• Part 1: “Interpretation and rating guidelines”

• Chapter 1: Application of interpretation and rating guidelines
• Chapter 2: Key concepts and overall guidelines
• Chapter 3: Rating guidelines on process performance (level 1)
• Chapter 4: Rating guidelines on process capability level 2
• Chapter 5: Rating guidelines on process capability level 3

• Part 2: “Guidelines for performing the assessment”

• Chapter 6: Documented assessment process
• Chapter 7: Improvement process
• Chapter 8: Recommendations for performing an assessment
• Chapter 9: Requirements relating to assessor qualification

Page 4
 Understanding purpose and
terminology of rating rules and
recommendations

Page 5
 Objectives for rules and recommendations

• Experiences from past assessments have shown, that there is a certain inconsistency
is observed in ratings of process attributes.

• The VDA Automotive SPICE® Guidelines are intended to reduce this inconsistency.

Page 6
 Definition of Rules and Recommendations
Rules
• A rule shall be followed for the rating in an assessment.
• It might be necessary to not follow a rule to provide an objective and adequate
rating.
• In case of an infringement of a rule for the rating, a justification shall be documented
to the assessment sponsor.

Recommendation
• A recommendation should be followed for the rating in an assessment.
• It might be reasonable for an assessor to decide to NOT follow a recommendation.
• In case of not following a recommendation, no documentation of this is needed.

Page 7
 Terminology of Rules (1/2)
Eight different formulations for a rule with different meanings.

… be rated F (1)

… be rated N/P/L (2)

dependency

… must not … … be rated higher (5)

… be downrated (3)
dependency

… be used to downrate (8)

positive

negative (refer to 1.4.2.1, page 28)

Page 8
 Terminology of Rules (2/2)
Eight different formulations for a rule with different meanings.

If … (4)

If A is downrated, B …
… shall be downrated
(6)
dependency

If A is downrated due
to, B … (7)

positive

negative (refer to 1.4.2.1, page 28)

Page 9
 Terminology of Recommendations (1/3)
Ten different formulations for a recommendations with different meanings.
Recommendations 1 – 8 are counterparts of rules:

Rule Recommendation

… must not … … should not …

… shall be downrated … … should be downrated …

(refer to 1.4.2.2, page 29)

Page 10
 Terminology of Recommendatinos (2/2)
Ten different formulations for a recommendations with different meanings.

… should have no influence

If A is downrated … (9) on …

If A is downrated due to … (10) … should be inline with …

positive

negative (refer to 1.4.2.2, page 29)

Page 11
 Understanding the concept of
dependencies within the PAM

Page 12
 Consistency of PA Ratings
• The Automotive SPICE® PAM includes various dependencies between the different
elements.

• To ensure a consistent rating of process attributes, these dependencies should be

considered during the rating process.

• The VDA Automotive SPICE® Guideline focuses on a dedicated set of dependencies

with the following criteria:
• The processes of the VDA scope
• The capability levels 1 to 3
• The dependencies having a significant impact on the process attribute rating

Page 13
 Types of Dependencies: Explicit
Three different explicit dependencies.

In-process (A)

Explicit by specific
out-of-process (B)
wording

in-level (C)

Within one
element
Across
elements (refer to 1.4.3, page 31)

Page 14
 Types of Dependencies: Implicit
Four different implicit dependencies.

CL to process (D)

Logical process
workflow (E)
Implicit
Quality of input (F)

Quantity of input (G)

Within one
element
Across
elements (refer to 1.4.3, page 31)

Page 15
 How to read Dependencies in Rules and Recommendations
In-process (A,E) or in-level (C) dependencies
(blue arrow to blue box)

BP BP GP GP
Rules:

BP BP GP GP
Recommendation:

Out-of-process (B,F) or out-of-level (D) dependencies

(green arrow to green box)

BP BP/PA GP BP/GP
Rules:

BP BP/PA GP BP/GP
Recommendation:

(refer to 1.4.3, page 33)

Page 16
 Your Questions

Seite 17