The purpose of the Software Qualification Test Process is to ensure that the integrated software is tested to provide evidence for compliance with the software requirements.

The sequential nature of the process defined by ASPICE can seem simplistic at first sight. In theory, if the V-model is adhered to, then the requirements will never change, each phase will follow in sequence, and tests will never throw up a problem.

Consider what happens if there is a code change in response to a failed integration test, or where there is a change in a customer requirement. Such scenarios can quickly lead to situations where the traceability between the products of software development falls down if the integrity of each development phase and the artefacts generated by them are not maintained. A sequence of similar issues can ultimately lead to a situation where the completed project does not fulfil functional, functional safety, or cybersecurity requirements.

For that reason, ASPICE incorporates the principle of bidirectional traceability, requiring ongoing maintenance and integrity of the artefacts generated by each phase of the development lifecycle. Adherence to this principle ensures not only that the delivered system accurately reflects the requirements of the stakeholders as confirmed during the software qualification test phase, but also confirms that there is no superfluous code within the system – important from both a safety and security perspective.

The double headed arrows in Figure 1 represent bidirectional traceability, confirming that each software “production” phase on the right side of the V accurately and completely reflects the “design” phase that specified it on the left. Figure 2 illustrates its automation.

SWE.6 Software Qualification Test