< Previous | Contents | Next >
Traceability and consistency are addressed by two separate base practices in the Automotive SPICE
3.1 PAM. Traceability refers to the existence of references or links between work products thereby further supporting coverage, impact analysis, requirements implementation status tracking etc. In contrast, consistency addresses content and semantics.
Furthermore, bidirectional traceability has been explicitly defined between
test cases and test results, and
change requests and work products affected by these change requests.
Stakeholder
requirements
bidirectional traceability
consistency
SYS.2 BP6 SYS.2 BP7
SYS.5 BP5 SYS.5 BP6
System qualification
test specification
System requirements
Test cases
SYS.5 BP5 System qualification
test results
SYS.3 BP6 SYS.3 BP7
SYS.4 BP7
SYS.4 BP8
System architecture
System integration
test specification
SYS.4 BP7
Test cases
SWE.1 BP6 SWE.1 BP7
System integration
test results
SWE.1 BP6 SWE.1 BP7
SWE.6 BP5 SWE.6 BP6
Software requirements
Software qualification
test specification
Test cases SWE.6 BP5
SWE.2 BP7 SWE.2 BP8
Software qualification
test results
SWE.5.BP7 SWE.5 BP8
Software architecture
Software integration
test specification
SWE.5 BP7
Test cases
SWE.3.BP5 SWE.3 BP6
Software integration
test results
SWE.3 BP5 SWE.3 BP6
SWE.3 BP5 SWE.3 BP6
Software detailed
design
SWE.4 BP5 SWE.4 BP6
Unit test specification
SWE.4 BP5
Unit test results
Software units
SWE.4 BP5
Static verification
results
An overview of bidirectional traceability and consistency is depicted in the following figure.
To affected work products
SUP.10 BP8
Change requests