Coverage

The Coverage block evaluates whether testing has been comprehensive enough to provide reliable safety evidence on a CCAM system under test. It examines test results from multiple perspectives and derives a combined coverage outcome to determine if the testing adequately covers the system’s operational boundaries and requirements. The main coverage levels examined, are as follows:
- Coverage of the combined scenario set:
- Operational Design Domain (ODD) Coverage: Checks if the combined set of scenarios sufficiently explores the operational boundary within which the system is expected to operate safely, including the identification of possible gaps.
- Requirements Coverage: Verifies that the combined set of scenarios addresses all specified system requirements.
- Behavior Coverage: Confirms that relevant system behaviors are tested across the combined set of scenarios.
- Coverage of the individual scenarios:
- Parameter Coverage: Analyzes how concrete parameter values cover the logical parameter ranges within individual scenarios, including the identification of possible gaps.
Depending on the analysis outcomes, the Coverage block might trigger an iterative process that derives new concrete scenarios within logical scenario parameter ranges to identify failure conditions (for example parameter combinations leading to system failure). This feedback loop for continuous testing improvement, is indicated by the red arrow in the image above.
The Coverage block ultimately provides essential input to the Safety Argument block, which combines information from the Coverage block with that of the Test Evaluate block, to generate safety evidence for the CCAM system under test.
SAF Application Guidelines for 'Coverage'
In the list below, “D” stands for Deliverable. All deliverables of the SUNRISE project can be found here.
- Review ODD coverage (D5.3 section 5.5.1):
- Assess Tag Coverage (D5.3 section 5.5.1.1):
- Review how scenarios are categorised and tagged
- Check that all important driving situations are represented
- Verify each tag appears across different scenario types
- Look for missing or underrepresented driving conditions
- Assess Time Coverage (D5.3 section 5.5.1.2):
- Check that scenarios cover different time periods adequately
- Identify any time gaps where no scenarios exist
- Review scenarios that happen at the same time
- Document any uncovered time periods
- Assess Actor Coverage (D5.3 section 5.5.1.3):
- Review which vehicles and road users are included in scenarios
- Check coverage at different distances from the test vehicle
- Verify that vehicles in critical positions are well represented
- Assess if important actors are missing
- Assess Actor-Time Coverage (D5.3 section 5.5.1.4):
- Check that important actors appear throughout relevant time periods
- Verify actors stay covered during their entire critical presence
- Assess Tag Coverage (D5.3 section 5.5.1.1):
- Review parameter space coverage (D5.3 section 5.5.2):
- Review how selected parameter values are analysed for completeness
- Check that statistical assumptions are properly verified
- Identify areas with insufficient parameter coverage
- Verify that synthetic scenarios fill identified gaps
- Check SAF integration (D5.3 section 3 introduction):
- Verify that coverage analysis supports scenario selection
- Check that coverage results inform the safety argumentation
- Ensure that coverage metrics support completeness arguments
- Final verification (D5.3 sections 5.5 and 6.5):
- Confirm all coverage metrics meet acceptable levels
- Validate that coverage gaps are properly addressed
- Ensure synthetic scenarios appropriately fill coverage gaps
- Cross-check results with implementation examples
