5 Test that traces to no requirement
Tests are derived from requirements, and the trace runs both ways: every result should link back to a requirement it verifies. This test links to no requirement in the paste, or names only an ID the paste does not hold. It may verify a requirement in another module, be left over from an earlier version, or be a test with no requirement behind it.
- the test
- a test or verification in the results that no requirement links and that names no requirement in the paste; where the results carry a test type, regression, exploratory, infrastructure, robustness, qualification and smoke tests are shown apart by type and never raise it
- the question
- Which requirement does this test verify? If none, is it still needed, and if the requirement sits in another export, where?
- asked of
- the verification lead
- columns it reads
- the results: Requirements, Verified By and the results: Type
Where the results carry a test type, regression, exploratory, infrastructure, robustness, qualification and smoke tests with no requirement are listed apart by type and never raise this finding. With no type column, every such test is asked about.
The clauses behind it, by standard
each shown when you tick its standard- ISO 26262: Part 8, 9.4.2
- Automotive SPICE: SYS.5.BP4 and SWE.6.BP4
- DO-178C: A-6.1
The clause text
The verification specification selects and specifies the methods, test cases with inputs, conditions and expected results, the equipment and environment, and the criteria, derived from the requirements and the design. Requirement text not held.
Held text: ISO 26262:2018, our statement of the clause, not the instrument verbatim.
what an assessor asks to see Verification specification with test cases and expected results
where it usually breaks Tests run without specified expected results
Normal-range requirements-based tests on the executable object code show it satisfies the high-level requirements, with trace data between requirements, test cases, procedures and results. Table A-6 objective 1, described in 6.4.a; applies at levels A, B, C, D, no independence required; activities 6.4.2, 6.4.2.1, 6.4.3, 6.5; outputs: Trace Data, Software Verification Results, and Software Verification Cases and Procedures. All tests, normal and robustness, are requirements-based; the purpose of verification trace data (6.5, new) is requirements coverage analysis and proof that every procedure ran.
Applies at software level A, B, C, D: a line at another level does not carry it.
Held text: DO-178C / ED-12C, our statement of the clause, not the instrument verbatim.
what an assessor asks to see Requirements-based test cases, procedures and results for high-level requirements, traced
where it usually breaks Tests not derived from requirements
Make sure the verification measures agree with the system requirements and link the two in both directions; likewise link each verification result back and forth with the measure that produced it.
Held text: Automotive SPICE v4.1, our statement of the clause, not the instrument verbatim.
what an assessor asks to see Consistency evidence (13-51), such as a trace matrix, linking each system requirement to its verification measures and each result to the measure run
where it usually breaks System requirements with no linked system test identified only at the final gate; System test results not traceable to the test case version run
Make sure the verification measures agree with the software requirements and link the two in both directions; likewise link each verification result back and forth with the measure that produced it.
Held text: Automotive SPICE v4.1, our statement of the clause, not the instrument verbatim.
what an assessor asks to see 15-52 Verification Results; 08-58 Verification Measure Selection Set; 03-50 Verification Measure Data; 08-60 Verification Measure
where it usually breaks Software requirements with no linked qualification test, discovered only at release review; Test results cannot be traced to the test specification version used