Upload
others
View
12
Download
2
Embed Size (px)
Citation preview
3.0… the new and the core features
Bernd HindelMethod Park Consulting31st May 2016, Rochester
Agenda
Background & History
Basics & Abstractions
Assessments & Learning
Organizations & References
The core features
Migration to Automotive SPICE® 3.0
Summary
© www.methodpark.com 2015 - Automotive SPICE® 2 of 118
Maturity Models
Objective: Improvement of Product Quality
Hypothesis:Product Quality ßà Quality of the Development Process
are defined by:§ Capability Levels § Best Practices§ Measurement Framework
Examples:§ CMM § SPICE
© www.methodpark.com 2015 - Automotive SPICE® 3 of 118
History & Background
SEI EU ISO HIS VDA AK13
1990 CMMBootstrap
SPICE
1995CMMi
ISO15504 TR
2000Decision
for SPICE
2005 ISO15504 ASPICE 1.0
2010 ASPICE 2.5
2015 ISO330xx ASPICE 3.0
© www.methodpark.com 2015 - Automotive SPICE® 4 of 118
Agenda
Background & History
Basics & Abstractions
Assessments & Learning
Organizations & References
The core features
Migration to Automotive SPICE® 3.0
Summary
© www.methodpark.com 2015 - Automotive SPICE® 5 of 118
Basics & Abstractions
… ASPICE focuses on …
© www.methodpark.com 2015 - Automotive SPICE® 6 of 118
Basics & Abstractions
© www.methodpark.com 2015 - Automotive SPICE® 7 of 118
Basics & Abstractions
© www.methodpark.com 2015 - Automotive SPICE® 8 of 118
Basics & Abstractions
© www.methodpark.com 2015 - Automotive SPICE® 9 of 118
Basics & Abstractions
© www.methodpark.com 2015 - Automotive SPICE® 10 of 118
Basics & Abstractions
© www.methodpark.com 2015 - Automotive SPICE® 11 of 118
Basics & Abstractions
Plan – Do - Check – Act
1. Objectives 2. Strategy to achieve the objectives3. Detailed Planning4. Implementation of the Plan5. Monitoring / Reporting6. Corrective Actions / Escalation
© www.methodpark.com 2015 - Automotive SPICE® 12 of 118
Agenda
Background & History
Basics & Abstractions
Assessments & Learning
Organizations & References
The core features
Migration to Automotive SPICE® 3.0
Summary
© www.methodpark.com 2015 - Automotive SPICE® 13 of 118
Basics of Assessments
Assessments compare used practices with recommended practices from standards
Assessments compare used practices with practices given by a process definition
Assessments should be of a consulting nature, assigning a maturity level is secondary
Assessments should be based on discussions and experiences, not on interviews and judgments
Assessments are baseline mechanismsof a learning organization
© www.methodpark.com 2015 - Automotive SPICE® 14 of 118
When to assess?
at Milestones or Quality Gates
long enough before releases, such that corrective actions can be implemented before the release date
at least after 1/3 of the planed project duration and before 2/3 of the planed project life time is over
© www.methodpark.com 2015 - Automotive SPICE® 15 of 118
Benefits gained from Automotive SPICE® 3.0
List of corrective actions
Harmonization of TermsAwareness of PracticesProcess AcceptanceKnow where you areKnow what to improve nextBecome a Learning Organization
© www.methodpark.com 2015 - Automotive SPICE® 16 of 118
Learning Organization
estimate, measure and act
define processes, tailor and feedback
define templates, checklists and review
© www.methodpark.com 2015 - Automotive SPICE® 17 of 118
ISO/IEC 330xx = ASPICE 3.0
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 Quantitative AnalysisPA.4.2 Quantitative Control
Level 5 InnovatingPA.5.1 Process Innovation ImplementationPA.5.2 Process Innovation
Level 0 IncompleteIncompleteChaotic processes
PerformedProcesses are intuitively performed, incoming and outgoing work products exist
PredictableMetrics for the measurement and control of process performance and outcomes are applied
OptimizingQuantitativ measures are implemented to continously improve the process
EstablishedDefined processes are tailored to specific projects, resources are managed
ManagedProcesses and work products are managed, responsibilities are identified
define and review
tailor and feedback
estimate and measure
© www.methodpark.com 2015 - Automotive SPICE® 18 of 118
Agi
le
Objectives: become a Learning Organization!„O
rgan
izat
iona
l“ L
evel
„Pro
ject
“ Le
vel
Tailoring
Tailoring Criteria
V M
odel
Set Of Standard Processes
Pro
ject
A
Pro
ject
B
Pro
ject
C
…
MeasurementRepository
Improvement Requests for Processes
FeedbackSessions
AssessmentResults
© www.methodpark.com 2015 - Automotive SPICE® 19 of 118
learning managed by of
© www.methodpark.com 2015 - Automotive SPICE® 21 of 118
Compliance Workbench
© www.methodpark.com 2015 - Automotive SPICE® 22 of 118
Agenda
Background & History
Basics & Abstractions
Assessments & Learning
Organizations & References
The core features
Migration to Automotive SPICE® 3.0
Summary
© www.methodpark.com 2015 - Automotive SPICE® 23 of 118
How it got started
Hersteller Initiative Software
Innovation in modern vehicles is to a great extent realised by software in electronic control units. Therefore vehicle manufacturers must extend their competence in the basics and methods of software design and quality assurance for microprocessor based control units. This has motivated the vehicle manufacturers Audi, BMW, Daimler, Porsche, and Volkswagen to bundle their activities for standard software modules, process maturity levels, software test, software tools and programming of control units. The common goal is to achieve and use joint standards source: http://www.automotive-his.de
© www.methodpark.com 2015 - Automotive SPICE® 24 of 118
Automotive Special Interest Group
ISO/IEC 15504 permits to define industry specific process assessments models compliant to the ISO standard
Due to the demand for a standard adapted to the automotive industry, the largest European car manufacturers started the “Automotive SPICE” initiative (1st version published ~2005)
Automotive SPICE is based upon the ISO/IEC 15504(www.automotivespice.com)
© www.methodpark.com 2015 - Automotive SPICE® 25 of 118
References to Automotive SPICE®
source: http://www.automotivespice.com
© www.methodpark.com 2015 - Automotive SPICE® 26 of 118
Stakeholders of Automotive SPICE®
SPICE
§ Requirements, Rules, Guidelines and Instructions for Trainings, Certifiers and Assessors
§ Working groups§ Support of Domains (e.g. Automotive)§ Verification of compliance (e.g. of Assessments)
Automotive SPICE®
§ Common steering committee of German Car manufacturers
§ Working groups for definition of unique Standards for the Automotive Domain
§ Certification of SPICE-Assessors§ Events for SPICE (e.g. SPICE Days)§ GATE4SPICE
§ Certification of Automotive SPICE®-Assessors
§ further development of Automotive SPICE® by VDA Working Group 13
§ Trainings provider for SPICE and Automotive SPICE®, e.g.
§ Competence network (Meetings, Workshops, etc.) of the Community§ Working groups i.e. GATE4SPICE
© www.methodpark.com 2015 - Automotive SPICE® 27 of 118
Key Users of Automotive SPICE®
Quelle: intacs.info, Gate4SPICE Meeting 19.09.2012
© www.methodpark.com 2015 - Automotive SPICE® 28 of 118
Key Users of Automotive SPICE®
© www.methodpark.com 2015 - Automotive SPICE® 29 of 118
Key Users of Automotive SPICE®
© www.methodpark.com 2015 - Automotive SPICE® 30 of 118
Key Users of Automotive SPICE®
© www.methodpark.com 2015 - Automotive SPICE® 31 of 118
Key Users of Automotive SPICE®
© www.methodpark.com 2015 - Automotive SPICE® 32 of 118
Key Users of Automotive SPICE®
© www.methodpark.com 2015 - Automotive SPICE® 33 of 118
Key Users of Automotive SPICE®
© www.methodpark.com 2015 - Automotive SPICE® 34 of 118
Key Users of Automotive SPICE®
© www.methodpark.com 2015 - Automotive SPICE® 35 of 118
Agenda
Background & History
Basics & Abstractions
Assessments & Learning
Organizations & References
The core features
Migration to Automotive SPICE® 3.0
Summary
© www.methodpark.com 2015 - Automotive SPICE® 36 of 118
Level 1: Why do we need a Traceability?
Advantages:• Analysis of coverage (completeness)
• Information for queries (status of requirements)
• Support of test activities
• Support for the problem resolution (change and configuration management)
• Support for the impact analysis ofchange requests
Realization:• Links (in Tools)
• References, Hyperlinks, Naming conventions
• Traceability matrices
© www.methodpark.com 2015 - Automotive SPICE® 37 of 118
Level 1: Traceability
© www.methodpark.com 2015 - Automotive SPICE® 38 of 118
Level1: What is a Traceability concept?
1. Purpose§ Extent and granularity of traceability must balance value
and maintenance effort
2. Coverage§ 100% Traceability coverage often is unrealistic
§ Consider taking a risk-based approach, e.g.§ Local increase of change requests§ Complexity§ New technology
§ Document this as a strategy§ Prove risk-based approach through metrics
3. Tooling§ Currently there is still no integrated
tool solution
© www.methodpark.com 2015 - Automotive SPICE® 39 of 118
Level1: Plan – Do – Check – Act… as part of Quality Assurance
Objectives & Strategy
Planning & Implementation
Monitoring & Reporting
Corrective Actions & Escalation
© www.methodpark.com 2015 - Automotive SPICE® 40 of 118
Level2: Plan – Do – Check – Act
GP 2.1.1 Identify the objectives for the performance of the process.GP 2.1.2 Plan and monitor the performance of the process to fulfill
the identified objectives.GP 2.1.3 Adjust the performance of the process.GP 2.1.4 Define responsibilities and authorities for performing the process.GP 2.1.5 Identify and make available resources to perform the process
according to plan.GP 2.1.6 Manage the interfaces between involved parties.
Generic Practices
• It’s a measure of the extent to which the performance of the process is managed.
Definition PA 2.1 Performance management
© www.methodpark.com 2015 - Automotive SPICE® 41 of 118
Level2: Plan – Do – Check – Act
GP 2.1.1 Objectives GP 2.1.2 Strategy to achieve the objectivesGP 2.1.2 Detailed PlanningGP 2.1.2 Implementation of the PlanGP 2.1.2 Monitoring / ReportingGP 2.1.3 Corrective Actions / Escalation
© www.methodpark.com 2015 - Automotive SPICE® 42 of 118
Level 2: Templates, Checklists, Configuration Management, Review Techniques
GP 2.2.1 Define the requirements for the work products.GP 2.2.2 Define the requirements for documentation and control
of the work products.GP 2.2.3 Identify, document and control the work products.GP 2.2.4 Review and adjust work products to meet the defined requirements.
Generic Practices
• It’s a measure of the extent to which the work products produced by the process are appropriately managed.
Definition PA 2.2 Work product management
© www.methodpark.com 2015 - Automotive SPICE® 43 of 118
Relationships inside Automotive SPICE®
MAN.3 has influence on PA2.1 for all other processes, esp.§ GP 2.1.2 Plan and monitor the performance of the
process to fulfill the identified objectives.§ GP 2.1.3 Adjust the performance of the process.§ GP 2.1.4 Define responsibilities and authorities for
performing the process.§ GP 2.1.5 Identify and make available resources to perform
the process according to plan.
SUP.8 has influence on PA2.2 for all other processes, esp§ GP 2.2.3 Identify, document and control the work products
SUP.1 has influence on PA2.2 for all other processes, esp.§ GP 2.2.1 Define the requirements for the work products.§ GP 2.2.4 Review and adjust work products to
meet the defined requirements.
FAQ
© www.methodpark.com 2015 - Automotive SPICE® 44 of 118
Level 3: Standard Process
GP 3.1.1 Define the standard process that will support the deployment of the defined process.
GP 3.1.2 Determine the sequence and interaction between processes so that they work as an integrated system of processes.
GP 3.1.3 Identify the roles and competencies for performing the standard process.GP 3.1.4 Identify the required infrastructure and work environment for
performing the standard process.GP 3.1.5 Determine suitable methods to monitor the effectiveness and suitability of
the standard process.
Generic Practices
• It’s a measure of the extent to which a standard process is maintained to support the deployment of the defined process.
Definition PA 3.1 Process definition
© www.methodpark.com 2015 - Automotive SPICE® 45 of 118
Level 3: Defined Process
GP 3.2.1 Deploy a defined process that satisfies the context specific requirements of the use of the standard process.
GP 3.2.2 Assign and communicate roles, responsibilities and authorities for performing the defined process.
GP 3.2.3 Ensure necessary competencies for performing the defined process.GP 3.2.4 Provide resources and information to support the performance of the
defined process.GP 3.2.5 Provide adequate process infrastructure to support the performance of
the defined process.GP 3.2.6 Collect and analyze data about performance of the process
to demonstrate its suitability and effectiveness..
Generic Practices
• It’s a measure f the extent to which the standard process is effectively deployed as a defined process to achieve its process outcomes.
Definition PA 3.2 Process deployment
© www.methodpark.com 2015 - Automotive SPICE® 46 of 118
Relationships inside Automotive SPICE®
MAN.3(Project Management)
SUP.1(Quality Assurance)
SUP.8(Configuration Management)
CL 1 CL2 CL3Base Practices
Output Work Products
(All Eng. Processes)ENG.2ENG.3
…ENG.10
…
PerformanceManagement
Generic Practices (valid for all processes, i.e. ENG)
ProcessDefinition
ProcessDeployment
Work ProductManagement
© www.methodpark.com 2015 - Automotive SPICE® 47 of 118
Agenda
Background & History
Basics & Abstractions
Assessments & Learning
Organizations & References
The core features
Migration to Automotive SPICE® 3.0
Summary
© www.methodpark.com 2015 - Automotive SPICE® 48 of 118
Current Status (April 2015)Withdrawn by ISO 03/03/2015
Withdrawn by ISO 03/03/2015
Published by ISO as IS 27/02/2015
Published by ISO as TR 19/11/2013
© www.methodpark.com 2015 - Automotive SPICE®
ISO/IEC 33020:2015
Measurement framework for the assessment of process capabilityand organizational maturity
Changes:§ PA 4.1 Quantitative analysis process attribute *1
§ PA 4.2 Quantitative control process attribute *1
§ PA 5.1 Process innovation process attribute *1
§ PA 5.2 Process innovation implementation process attribute *1
*1 including revised process attribute outcomes
§ Optional refinement of the ordinal scale *2
§ Three different rating methods *2
§ Different aggregation methods *2
*2 depending on the class of the assessment
Former4.1 Process measurement4.2 Process control5.1 Process innovation5.2 Process optimization
© www.methodpark.com 2015 - Automotive SPICE® 50 of 118
ISO/IEC 33020:2015Optional refinement of ordinal scale
Source: ISO/IEC 33020:2015
© www.methodpark.com 2015 - Automotive SPICE® 51 of 118
Automotive SPICE® Process Reference ModelThe Symmetry in the “V” Model
Probably new HIS Scope, but not confirmed yet Source: Automotive SPICE® PAM v3.0, July 16th, 2015, © VDA QMC
© www.methodpark.com 2015 - Automotive SPICE® 52 of 118
The “Plug-In” Concept
= developed by VDA, part of Automotive SPICE® 3.0
= not developed by VDA, not part of Automotive SPICE® 3.0(but by intacs™ Working Groups)
Source: Automotive SPICE® PAM v3.0, July 16th, 2015, © VDA QMC
© www.methodpark.com 2015 - Automotive SPICE® 53 of 118
Consistent Usage of Terms –“Element”, “Component”, “Unit” and “Item”
Source: Automotive SPICE® PAM v3.0, July 16th, 2015, © VDA QMC
© www.methodpark.com 2015 - Automotive SPICE® 54 of 118
Consistent Usage of Terms –“Agree” and “Summarize and Communicate”
Source: Automotive SPICE® PAM v3.0, July 16th, 2015, © VDA QMC
© www.methodpark.com 2015 - Automotive SPICE® 55 of 118
Consistent Usage of Terms –“Strategy” and “Plan”
Affected Processes:SYS.4 System Integration and Integration TestSYS.5 System Qualification TestSWE.4 Software Unit VerificationSWE.5 Software Integration and Integration TestSWE.6 Software Qualification TestSUP.1 Quality AssuranceSUP.8 Configuration ManagementSUP.9 Problem Resolution ManagementSUP.10 Change Request Management
Source: Automotive SPICE® PAM v3.0, July 16th, 2015, © VDA QMC
© www.methodpark.com 2015 - Automotive SPICE® 56 of 118
“Bidirectional Traceability” and “Consistency”
Source: Automotive SPICE® PAM v3.0, July 16th, 2015, © VDA QMC
© www.methodpark.com 2015 - Automotive SPICE® 57 of 118
“Evaluation”, “Verification Criteria”, “Compliance” and “Test”
Source: Automotive SPICE® PAM v3.0, July 16th, 2015, © VDA QMC
© www.methodpark.com 2015 - Automotive SPICE® 58 of 118
Who is affected?
Project Teams and Companies/Organisations- New structure of engineering processes- Textual changes in all process descriptions- Compliance to PAM(s)- Sponsor decision
Assessors and Instructors- Knowledge update- Assessment competence- Evaluation and mapping of evidences- Training updates and timeline
© www.methodpark.com 2015 - Automotive SPICE® 59 of 118
2015 Jan Apr Jul Okt Jan2016
Apr Jul Okt Jan2017
Apr Jul Okt 2017
Today
EndofTransitionPeriod30/9/2017
VDABlue-Gold-BookwithPAMGuidelines
30/9/2016
AutomotiveSPICE(R)PAMv3.0Release16/7/2015
intacsPAMv3.0UpgradeCourse
1/10/2016- 31/12/2017
UpdatedintacsAssessorCourses
1/10/2016- 31/12/2017
AssessmentswithPAMV2.xacceptedbyVDA-QMC
1/1/2015- 30/9/2017
AssessmentswithPAMv3.0acceptedbyVDA-QMC
17/7/2015- 31/12/2017
Timeline for Certification and Qualification
© www.methodpark.com 2015 - Automotive SPICE® 60 of 118
Agenda
Background & History
Basics & Abstractions
Assessments & Learning
Organizations & References
The core features
Migration to Automotive SPICE® 3.0
Summary
© www.methodpark.com 2015 - Automotive SPICE® 61 of 118
Objectives of Automotive SPICE®
Developing products, which are § traceable tested and which are§ managing the complex linkage of mechanic design, hardware and software
( = „Systems“)
Processes which are § really used and which are § based upon best practices shared within the whole organization
( = „Learning Organization“)
A product developing organization which is § achieving measurable performance objectives and § can react early on deviations
An optimized management of complex system releases.
Stable and faultless products which operate well.
Systematic and professional system and software engineering organization!
© www.methodpark.com 2015 - Automotive SPICE® 62 of 118
The SPICE Experience
PA.1.1Process Performance
PA.3.2Process Deployment
PA.3.1Process Definition
PA.2.2Work Product Management
PA.2.1Performance Management Objectives
are identifiedPerformance is planned
and monitoredPerformanceis adjusted
Responsibilities andauthorities are assigned
Resources are identifiedand made available
Interfacesare managed
Requirements for work products are defined
Requirements for documentationand control are defined
Review and adjustwork products
Work products are identified,documented and controlled
Leve
l 3Le
vel 2
Leve
l 1
Standardprocess definition
Sequence andinteraction
Identify rolesand competencies
Infrastructure andwork environment
Methods to monitorthe process
Deploy astandard
Assign and communicate roles,responsibilities and authorities
Ensure necessarycompetencies
Resources andinformation
Processinfrastructure
Collect and analyzeprocess performance data
Activities are performed
(A set of base practices isdefined for each process.)
Work products exist
(A set of outcomes isdefined for each process.) B
ase
Pra
ctic
esG
ener
ic P
ract
ices
Estimate, Plan, Schedule, Monitor, Status Reports, Resource Management,Improvement Objectives, Project Metrics
Configuration Management (CM-Plan, Naming Conventions, …),Templates, Checklists, Reviews
Standard Process, Process Feedback Sessions, Process Metrics
Process Tailoring, Process Management , Skill Management (incl. Trainings),Resource Management (incl. Skills and Competencies), Applied Process Metrics
Mindset to improve the project results
Mindset to remember and reuse whatever was good
TraceabilityCraftsmanshipin Software Engineering
© www.methodpark.com 2015 - Automotive SPICE® 63 of 118