Reference · Automotive SPICE 4.1
Process cards: the VDA Scope and the flex processes the course uses
The base five, the software and system plug-ins, and the flex processes the course uses, each with its purpose in brief; the base five, SYS.1, SWE.1 and SPL.2 also list their base practice headers, and the engineering cards name their traceability BP. Read the PAM page for the full wording.
MAN.3 Project Management · p. 89
Identify and control the project's activities and resources.
BP1 scope of work · BP2 lifecycle · BP3 feasibility · BP4 work packages · BP5 estimates and resources · BP6 skills · BP7 interfaces and commitments · BP8 schedule · BP9 consistency · BP10 review and report progress
SUP.1 Quality Assurance · p. 79
Independent, objective assurance that work products and processes meet the criteria; non-conformances resolved.
BP1 independence · BP2 criteria · BP3 assure work products · BP4 assure process activities · BP5 summarise and communicate · BP6 resolve non-conformances · BP7 escalate
SUP.8 Configuration Management · p. 81
Integrity of configuration items and baselines, available to all affected parties.
BP1 identify configuration items · BP2 configuration item properties · BP3 establish CM (incl. branch and merge) · BP4 control modifications · BP5 baselines · BP6 communicate status · BP7 completeness and consistency · BP8 backup and recovery
SUP.9 Problem Resolution Management · p. 83
Problems identified, recorded, analysed, and resolution managed.
BP1 identify and record · BP2 causes and impacts · BP3 authorise urgent actions · BP4 alert notifications · BP5 initiate resolution · BP6 track to closure · BP7 report status and trends
SUP.10 Change Request Management · p. 85
Change requests recorded, analysed, tracked, approved and implemented.
BP1 identify and record · BP2 analyse and assess · BP3 approve before implementation · BP4 bidirectional traceability · BP5 confirm implementation · BP6 track to closure
SWE.1 Software Requirements Analysis · p. 44
Structured, analysed software requirements consistent with system requirements and architecture.
BP1 specify · BP2 structure and prioritise · BP3 analyse · BP4 impact on operating environment · BP5 consistency and traceability · BP6 communicate
SWE.2 Software Architectural Design · p. 46
Analysed architecture, static and dynamic, consistent with the software requirements. Traceability BP: BP4.
SWE.3 Software Detailed Design and Unit Construction · p. 48
Detailed design consistent with the architecture; units consistent with the design. Traceability BP: BP4.
SWE.4 Software Unit Verification · p. 50
Units verified against the detailed design. Traceability BP: BP4.
SWE.5 Software Component Verification and Integration Verification · p. 52
Components verified against the architecture; elements integrated and the integration verified. Traceability BP: BP6.
SWE.6 Software Verification · p. 55
Integrated software verified against the software requirements. Traceability BP: BP4.
SYS.1 Requirements Elicitation (flex) · p. 33
Gather, analyse and track stakeholder needs into a set of agreed stakeholder requirements.
BP1 identify stakeholders and obtain expectations · BP2 agree the requirements · BP3 analyse changes · BP4 communicate status
SYS.2 System Requirements Analysis · p. 35
Structured, analysed system requirements consistent with the stakeholder requirements. Traceability BP: BP5.
SYS.3 System Architectural Design · p. 37
Analysed system architecture, static and dynamic, consistent with the system requirements; special characteristics derived. Traceability BP: BP4.
SYS.4 System Integration and Integration Verification · p. 39
System elements integrated, and the integration verified against the system architecture. Traceability BP: BP4.
SYS.5 System Verification · p. 42
Integrated system verified against the system requirements. Traceability BP: BP4.
VAL.1 Validation (flex) · p. 58
Evidence that the end product, with direct end-user interaction, meets its intended use in its operational environment. Not for pure embedded software or ECUs. Traceability BP: BP4.
SPL.2 Product Release (flex) · p. 30
Control the release of a product to the intended customer.
BP1 content and release criteria · BP2 release package · BP3 unique identification · BP4 build from controlled items · BP5 approval before delivery · BP6 release note · BP7 support terms · BP8 deliver
Flex processes
ACQ.4 Supplier Monitoring · MAN.5 Risk Management · MAN.6 Measurement · SYS.1 Requirements Elicitation · VAL.1 Validation · SPL.2 Product Release · PIM.3 Process Improvement · REU.2 Management of Products for Reuse. Recommended scope: Guidelines Fig. 1-1, p. 29.
The traceability chain
