3. The ASPICE-Processes (VDA Scope)
3.18 Verification criteria in Automotive SPICE
What are verification criteria?
Verification criteria give directions on how to verify a requirement. They are required in the system and software requirements processes.
Verification criteria are based typically on the expertise of the subject matter experts specifying the requirements. They give hints on what needs to be observed in developing the system tests (SYS.5) and software tests (SWE.6) to verify a requirement successfully. They are the basis for the development of the tests on the right side of the V cycle.
Verification criteria need to cover all requirements and can be defined for a single requirement or for groups of requirements. Verification criteria have the following characteristics:
They can be unambiguously assigned to a requirement.
The requirement is thus verifiable or can be evaluated.
Verification criteria define the qualitative and quantitative criteria for determining a requirement has been implemented successfully.
They cover conditions under which a requirement can be tested.
Verification criteria show that a requirement can be verified under agreed boundary conditions.
Example of verification criteria for requirements:
- Requirement: Corrupt content in the EEPROM can be found.
- Verification criterion: corrupt content in the EEPROM can be found by a checksum calculation by the diagnostic service “readCheckSumStatus”.
- Requirement: Display a red dashboard indicator when airbag system detects a failure that will prevent it from firing upon a collision.
- Verification criteria: Check wavelengths of allowable red light for indicator is between 680 and 700 nm. Failures required to indicate are loss of communication with satellite sensors or satellite pretensioners or airbags. Use fault injection to check this.
Creating verification criteria
Verification criteria are created by subject matter experts during requirements development time, e.g., as a results of the requirements analysis. Specifying the criteria later in the right branch of the V cycle in the test processes is too late and leads to downratings in the assessment. However, if the tests are already developed on the left side of the V cycle (“test-driven development”), these tests are often accepted as verification criteria in assessments.
If you wish to continue to the next chapter click here: