Verification Report#

[Module Name] Verification Report
status: draft
security: NO
safety: ASIL_B
tags: template
version: 1

Verification report for the [Module Name] module. This report is generated based on the module verification plan and the module verification work product (wp__verification_module_ver_report), and covers all components of the module.

Attention

The verification report is automatically generated by a tool based on the code block above (see module_verification_report.need). It contains all information required for module verification, is based on the module verification plan and the module verification work product (wp__verification_module_ver_report), and covers all components of the module.

When this template is used in a module, replace the placeholder directive above with a module-specific directive. The following example shows the required structure; adapt its values to your module as described below.

  • Modify module pretty name to be your Module Name

  • Modify module formal name to be your Module Name in lower case

  • Adjust status to be valid

  • Adjust safety and tags according to your needs

.. document:: {module pretty name} Module Verification Report
   :id: doc__{module formal name = same as in ..mod}_verification_report
   :post_template: module_verification_report
   :status: valid
   :safety: QM
   :security: NO
   :realizes: wp__verification_module_ver_report
   :version: 1

Note

An possible example for a generated verification report is shown below and might contain the following parts, which are described in the following sections and is based on the gd_temp__verification_plan. This description can be deleted in a real module, but is kept here in the module template for documentation purposes.

**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" - for example
         by :need:`doc__mod_temp_component_name_impl_inspection`

**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