Embed Size (px)
Citation preview
SPICE auf der Überholspur
Vergleich von ISO (TR) 15504 und Automotive SPICE
Historie
� SPICE wird als Projekt der ISO zur Entwicklung eines Technical Reports gestartet (Fast Track).
� Technical Report fertig 1998/99 (ISO/IEC TR 15504:1998, Teil 1-4 und 6-9, Teil 5 ist von 1999)
� ISO/IEC TR 15504 muss umgeschrieben werden, da nicht kompatibel zu ISO/IEC 12207 (1995)
� ISO/IEC 15504 Teil 1-4 werden veröffentlicht 2003/2004
� Automotive SPICE wird veröffentlicht Q3/2005
� ISO/IEC 15504 Teil 5 wird veröffentlicht Q1/2006
1997
1995
1998
2000
ISO 15504Draft
2001
ISO 15504TR
1994
2003
2005
2006
Veröffentl.ISO 15504
Software Process Improvement and Capability dEtermination
AutomotiveSPICE
Measurement Framework
CapabilityScale
5
4
3
2
1
PM KM QM SWTest
SWDesign
Base Practices (BP)
Generic Practices (GP)
Process Reference Model
ISO 12207Automotive
SPICEPRM
ProcessAssessmentModel
(PAM)
ISO 15504Part 5
AutomotiveSPICEPAM
Automotive SPICE
ISO/IEC 15504
Process Capability Determination
AssessmentProcedure
process reference model
forsystems engineering
ISO/IEC 15288
additional process reference models can
be applied(e.g. SPICE 4 SPACE)
additional PRMs
process reference model for
software engineering
ISO/IEC 12207
process reference model
for automotive software
engineering
Automotive SPICE
standard of the European Space Agency
SPICE 4 SPACE
� Positionierung Automotive SPICE
Indikatoren der Prozessdimension
� Unterschiede zu ISO TR 15504
� Es bei gibt bei Automotive SPICE nur noch Output Work ProductsHinweis: ISO/IEC 15504-5 unterscheidet auch weiterhin zwischen Input und Output Work Products
� Überarbeitete Base Practices� Neue Practices
� Eindeutigere Formulierung
� Vereinheitlichung des Satzbaus
� Zuordnung von� Process Outcomes zu Base Practices
� Process Outcomes zu Work Products
Indikatoren der Reifegraddimension
� ISO TR 15504: � Management Practices
(practice performance characteristics, resource and infrastructure characteristics)
� ISO/IEC 15504:� Generic Practices
� Generic Work Products
� Generic Resources
� Automotive SPICE PAM:� Generic Practices
� Generic Resources
HIS Scope Vergleich
SUP.3 Quality Assurance Process
ENG.1.6 Software testing process
MAN.3 Project managementMAN.2 Project Management Process
SUP.9 Problem resolution managementSUP.8 Problem Resolution Process
SUP.8 Configuration managementSUP.2 Configuration Management Process
SUP.10 Change request management
SUP.1 Quality assurance
ENG.10 System testing
ENG.9 System integration (test)ENG.1.7 System integration and testingprocess
ENG.8 Software testing
ENG.7 Software integration (test)ENG.1.5 Software integration process
ENG.6 Software constructionENG.1.4 Software construction process
ENG.5 Software designENG.1.3 Software design process
ENG.4 Software requirements analysisENG.1.2 Software requirements analysisprocess
ENG.3 System architectural design
ENG.2 System requirements analysisENG.1.1 System requirements analysis and design process
ISO/IEC 15504/Automotive SPICEISO/IEC TR 15504
Key concept - System
System
Hardware
Software
Software-Component
Software Unit
1..*
1..*
1..*
1..*
1
1
1
1..*
Specifiesrequirements for
1
1
Software Integration
Is i
nte
gra
ted
to
1..*
Software Testing
verifies
verificationcriteria
Are derived from
uses
Software requirements
Mechanics
System Integration
verificationcriteria
uses
System Testing
verifiesSystem functional-and non-functional
requirements
Customerrequirements
Are derived from
1..*
1..*
System architectural
design
1..*
1..*
Are allocated to
Hardwarerequirements
Mechanicsrequirements
specify
specify
Are al lo-cated to
Are al lo-cated to
Software design
1..*
1..*
1..*
1..*1..*
1..*
11
11
specify
work product of a process
System
System Integration
System
System Integration
Explanation:
Software-item
Is i
nte
gra
ted
to
Requirementselicitation
integrates
integrates
integrates
elicits
elicits
elicits
Acceptance Testing
validates
Validates SW-only systems
Vergleich: Software Design
BP10: Ensure consistency and bilateral traceability to
software architectural design.
BP9: Ensure consistency and bilateral traceability to
software requirements.
BP8: Verify Software Design.
BP7: Develop Test Criteria.
BP6: Develop detailed design.
BP5: Ensure consistency.
BP4: Analyze the design fortestability.
BP3: Develop detailed design.
BP2: Define interfaces.
BP1: Describe software architecture.
15504 ENG.5
BP5: Define resource consumptionobjectives.
BP5 : Establish Traceability
BP4: Describe dynamic behaviour.BP4 : Develop detailed design
BP3: Define interfaces.BP3 : Verify the software design
BP2: Allocate software requirements.
BP2 : Design interfaces
BP1: Develop software architecturaldesign.
BP1 : Develop software architectural design
Automotive SPICE ENG.5TR 15504 ENG.1.3
new
new
new
new
Vergleich: Qualitätssicherung
BP10: Implement an escalation mechanism.
BP9: Ensure resolution on non-conformances.
BP8: Report quality assurance activities and results.
BP7: Track and record quality assurance activities and report results.
BP7: Handle deviations.
BP6: Assure quality of process activities.BP6: Report quality results.
BP5: Act on non-conformances.
BP4: Identify and record problems and non-conformance.
BP3: Assure the quality of project process activities and project work products.
BP2: Define quality records.
BP1: Develop a strategy for product and process quality assurance.
15504 SUP.1
BP5: Assure quality of work products.BP5: Assure quality of work products.
BP4: Maintain evidence of quality assuranceBP4: Assure quality of process activities.
BP3: Develop and implement a plan for project quality assurance based on a quality assurance strategy.
BP3: Define quality records.
BP2: Develop and maintain an organisation structure which ensures that quality assurance is carried out and report independently.
BP2: Establish quality standards.
BP1 : Develop project quality assurance strategy
BP1: Develop quality assurance strategy.
Automotive SPICE SUP.1TR 15504 SUP.3
new
new
Konsequenzen für Qualitätssicherung
� Organisation:� Qualitätsbeauftragte weisungsunabhängig zur Projektleitung!
-> Querschnittsabteilung notwendig
� Berichtswege:� Qualitätsbeauftragte berichten Projekt-übergeordneten Stellen
� Eskalationsstufen über Standard-Berichtsweg hinaus müssen definiert sein!
� Dokumentation:� Qualitätssicherungsplan explizit gefordert!
� Eskalationsstufen und -wege definiert
� Kooperation mit Qualitätssicherung des Kunden definiert
� Konsistenz mit organisationsweiter Qualitätssicherungsstrategie muss sichergestellt sein
� Dokumentation aller Qualitätssicherungsmaßnahmen und Berichte
Configuration Management
BP 11: Manage the backup, storage, archiving, handlingand delivery of configuration items
BP10: Verify the information about configured items
BP9: Report configuration status
BP8: Maintain configuration items history
BP7: Control modification and releases
BP6: Maintain configuration item description
BP5: Establish baselines
BP4: Establish branch management strategy
BP3: Establish configuration management system
BP2: Identify configuration items
BP1: Develop configuration mangement strategy
Automotive SPICE SUP.8
BP9 : Manage the release and delivery of configuration items
BP8 : Report configuration status
BP7 : Maintain configuration items history
BP6 : Manage product releases
BP5 : Manage Changes
BP4 : Maintain configuration itemsdescription
BP3 : Identify configuration items
BP2 : Establish configurationmanagement system
BP1 : Develop configuration managementstrategy
TR 15504 SUP.2
new
new
new
new
Work Products im Automotive SPICE
� “Process Outcomes” für Configuration Management:
As a result of successful implementation of this process:
1) A configuration management strategy is developed;
2) all items generated by a process or project are identified, definedand base lined according to the Configuration management strategy;
3) modifications and releases of the items are controlled;
4) modifications and releases are made available to affected parties;
5) the status of the items and modification requests are recorded andreported;
6) the completeness and consistency of the items is ensured; and
7) storage, handling and delivery of the items are controlled.
Notes
� In den Notes der Base Pratices sind Neuerungen enthalten! BeispielConfiguration Management:
� NOTE 11: The description should identify:
� its decomposition into lower level configuration components;
� who is responsible for each item; and
� when it is placed under configuration management.
� NOTE 5: Items requiring configuration control may also includework products of hardware (layouts, drawings, circuit boards, bills of material, etc.) and mechanical development.
Change Request Management
BP12: Change requests are tracked until closure. [OC: 7,8]
BP11: Review the implemented change. [OC: 7,8]
BP10: Schedule and allocate the change request. [OC: 5,7]
BP9: Identify and plan the verification and validation activities to beperformed for implemented changes. [OC: 4,5,6]
BP8: Approve change requests before implementation. [OC: 6]
BP7: Analyze and prioritize change requests. [OC: 4,5]
BP6: Assess the impact of the change. [OC: 4,5]
BP5: Establish the dependencies and relationships to other changerequests. [OC: 3]
BP4: Record the status of change requests. [OC: 8]
BP3: Identify and record the change request. [OC: 2,3]
BP2: Establish a consistent change request management proceeding [OC:1]
BP1: Develop a change request management strategy. [OC:1]
Automotive SPICE SUP.8
BP5 : Manage Changes
TR 15504 SUP.2
Bi-lateral Traceability
Schwerpunkt Traceability
� Automotive SPICE legt mehr Gewicht auf die bidirektionale Traceability, alsder TR-15504-Standard� Mehr Base Practices zum Thema Tracing
� � Rating verändert sich im Vergleich zu SPICE TR-15504
BP7 : Ensure consistency and bilateral traceability to test specification
BP6 : Ensure consistency and bilateral traceability to detailed design
BP5 : Ensure consistency and bilateral traceability to software requirements
BP4 : Verify the software units
BP3: Develop software units.
BP2: Develop unit verification criteria.
BP1: Define a unit verification strategy.
Automotive SPICE ENG.6
BP4 : Establish traceability
BP3 : Verify the software units
BP2 : Develop unit verificationprocedures
BP1 : Develop software units
TR 15504 ENG.1.4
AndereGewichtung!
Generic versus Management Practices
� Level 1:� TR: PA 1.1 Process performance attribute
� MP 1.1.1 Identify input and output work products
� MP 1.1.2 Ensure that the scope of work is identified
� MP 1.1.3 Ensure that the base practices are implemented
� Automotive: PA 1.1 Process performance attribute� GP 1.1.1 Achieve the process outcomes
Generic versus Management Practices
� Level 2� TR: PA 2.1 Performance Management Attribute
� MP 2.1.1 Identify the objectives for the performance of the process (for example, time-scale, cycle time and resource usage).
� MP 2.1.2 Plan the performance of the process according to the identified objectives byidentifying the activities of the process, the expected time schedule and allocation of resources for each activity.
� Automotive: PA 2.1 Performance Management Attribute� 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 versus Management Practices
� Level 2� TR: PA 2.2 Work Product Management Attribute
� MP 2.2.1 Identify the requirements for the work products, including both functional and non-functional aspects.
� MP 2.2.2 Manage the documentation, configuration management and change control of the work products.
� MP 2.2.3 Identify and define any work product dependencies.
� MP 2.2.4 Manage the quality of work products to ensure that they meet their functionaland non-functional requirements.
� Automotive: PA 2.2 Work product management attribute� 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.
SPI Vorgehen
Pilot procedures
Design procedures
Analysis
Setup & Kick off
Rolloutprocess
Workshops
Process &project analysis
Feedback
SPI Project management
Planpilot
Planrollout
Plan
Pilot
Training
Perform training
Gap analysis
Reviews for each process area
Coaching
Define trainingconcept
Implementtraining
Überprüfung der Compliance
Prozessmodell
AutomotiveSPICE
ISO 15504Part 5
IEC 61508Referenzmodell
Unternehmens-standard
Abbildung
� Abbildung schaffen zwischen� Prozessmodell und
� Anforderungen aus Referenzmodell
� Auswertung der Compliance auf Knopfdruck� Gap-Analyse
Reference Compliance Workbench
