Verification Report#

Note

Document header

[Your Module Name] Verification Report
status: draft
security: NO
safety: ASIL_B
tags: template
realizes: wp__verification_module_ver_report
doc__module_name_verification_report
Generic Document

Attention

The above directive must be updated according to your Module.

  • Modify Your Module Name to be your Module Name

  • Modify id to be your Module Name in upper snake case preceded by doc_ and succeeded by verification_report

  • Adjust status to be valid

  • Adjust safety and tags according to your needs

This verification report is based on the Platform Verification Plan .... It covers all the components of the above stated module.

Verification Report contains:

Note

Schema synchronization contract

The following fields define the canonical section keys and descriptions used for machine-readable verification report schema synchronization.

Table 75 Verification report section contract fields#

section_index

section_key

section_description

1

verification_coverage

Coverage on requirements, architecture, and detailed design including test and inspection results.

2

dfa_report

Report of component DFA results including verdict and open mitigations.

3

safety_analysis_report

Report of component safety analysis results including verdict and open mitigations.

4

unit_verification

Unit-level verification coverage including structural coverage, static analysis, and manual inspection.

5

software_component_qualification

Verification results for qualification of pre-developed software components.

6

test_results

Per-testcase execution result status.

7

test_logs

Per-testcase execution logs with pass/fail/not_run status context.

1. Verification Coverage

1.1. on Requirements

  • Lists of component requirements (incl. AoU satisfied by the component) tested by which test case, passed/failed and completeness verdict (this shall be generated by tools and accompanied by progress charts to be usable also for project steering)

  • For external component Assumptions of Use: coverage by platform safety manual or feature/components incl. test case, passed/failed and completeness verdict

  • This is split in a list of QM requirements tested and a separate list of tests for ASIL rated requirements.

  • List of component requirements (ASIL rated) linked to inspection checklist and verdict (derived from PR export)

1.2. on Architecture

  • List of component architecture tags tested by which test case, passed/failed and completeness verdict (this shall be generated by tools and accompanied by progress charts to be usable also for project steering)

  • This is split in a list of QM components tested and a separate list of tests for ASIL rated components.

  • List of component architecture tags (ASIL rated) linked to inspection checklist and verdict (derived from PR export)

1.3. on Detailed Design

  • List of detailed design tags tested by which test case, passed/failed and completeness verdict (this shall be generated by tools and accompanied by progress charts to be usable also for project steering)

  • This is split in a list of QM components tested and a separate list of tests for ASIL rated components.

  • List of detailed design tags (ASIL rated) linked to inspection checklist and verdict (derived from PR export)

  • The lists may also contain other verification methods like “Analysis” - process tbd

2. DFA Report

  • List of the performed component DFA, pass/fail with open mitigations

3. Safety Analysis Report

  • List of the performed component Safety Analysis, pass/fail with open mitigations

4. Unit Verification Coverage

4.1. Structural Coverage

  • List of the units with C0(line) and C1(branch) coverage absolute and percentage (this shall be generated by tools and accompanied by progress charts to be usable also for project steering)

  • List includes a column for the safety rating of each unit.

4.2. Static Code Analysis

  • List of the units with compiler warning numbers and coding rule violation numbers (this shall be generated by tools and accompanied by progress charts to be usable also for project steering)

  • List includes a column for the safety rating of each unit.

4.3. Manual Code Inspection

  • List of components (ASIL rated) linked to inspection checklist and verdict (derived from PR export)

5. Software component qualification verification report

  • Contains the needed verification results if for some components a qualification of pre-developed SW is performed.

6. Test results

  • Test result per test case with status passed/failed/not_run

7. Test logs

  • Test log per test case with status passed/failed/not_run

Note1: The verification report is valid for the module version tagged together with the report

Note2: All the above lists are generated automatically