From 494cd36c262653f5a30dcc7516ef7925a1a1a62e Mon Sep 17 00:00:00 2001 From: Philipp Ahmann Date: Mon, 22 Dec 2025 19:51:12 +0100 Subject: [PATCH 1/2] Align verification plan template to PMP implementation - Enhance verification plan template with detailed design, architectural design, and requirements coverage sections as well as Independence argument. - Content is taken from the most recent verification plan within S-CORE main repo. Resolves: #405 Signed-off-by: Philipp Ahmann --- .../guidance/verification_plan_template.rst | 39 +++++++++++++++++++ 1 file changed, 39 insertions(+) diff --git a/process/process_areas/verification/guidance/verification_plan_template.rst b/process/process_areas/verification/guidance/verification_plan_template.rst index 6e019a0943..c71c0cb487 100644 --- a/process/process_areas/verification/guidance/verification_plan_template.rst +++ b/process/process_areas/verification/guidance/verification_plan_template.rst @@ -131,6 +131,36 @@ Verification Plan Template These criteria might include code coverage metrics, defect density, or other relevant measures. The criteria should be defined with quantifiable goals for different ASIL levels. + The strategy on how to achieve the defined coverage goals is described in the below sub-sections. + + Coverage of detailed design + ^^^^^^^^^^^^^^^^^^^^^^^^^^^ + + Beside :need:`wp__verification_comp_int_test` and :need:`wp__verification_sw_unit_test` the + following aspects define the coverage of detailed design. + + - Statement/Branch/Path coverage as defined by their specific thresholds + - Static analysis and Linting + - :need:`wp__sw_implementation_inspection` for safety-critical implementation + + Coverage of architectural design + ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + + Beside :need:`wp__verification_comp_int_test` and :need:`wp__verification_feat_int_test` the + following aspects define the coverage of the architectural design. + + - :need:`wp__sw_arch_verification` - done by walkthrough (QM) or inspection (safety-critical parts) + - :need:`wp__sw_component_fmea` and :need:`wp__sw_component_dfa` for safety-critical parts + - :need:`wp__feature_fmea` and :need:`wp__feature_dfa` for safety-critical parts + + Each architectural element has at least one test case linked with attribute `FullyVerified` or + multiple test cases with attribute `PartiallyVerified`. + + Coverage of software requirements specifications + ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + + For a release all `valid` requirements need to have a complete test coverage of linked test cases. + Test Development ---------------- @@ -180,6 +210,15 @@ Verification Plan Template verification process. It can refer and should be based on the definition in the verification process :ref:`verification_roles`. + Independence of verification + ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + + As there are no separated roles for a software developer and test developer with :need:`rl__contributor` and + :need:`rl__committer` it is important to achieve independence. This is done by having different + people responsible for the test implementation and the actual code which gets tested. + + This section describes how independence is achieved in the project. + Tools ----- From 4e80454538fcffe4832bc6a95326904fcd2a1684 Mon Sep 17 00:00:00 2001 From: Philipp Ahmann Date: Mon, 5 Jan 2026 15:18:20 +0100 Subject: [PATCH 2/2] update coverage section of verification plan template Fixes review comment on #485 Signed-off-by: Philipp Ahmann --- .../guidance/verification_plan_template.rst | 38 +++++++++++-------- 1 file changed, 23 insertions(+), 15 deletions(-) diff --git a/process/process_areas/verification/guidance/verification_plan_template.rst b/process/process_areas/verification/guidance/verification_plan_template.rst index c71c0cb487..c2d19e5935 100644 --- a/process/process_areas/verification/guidance/verification_plan_template.rst +++ b/process/process_areas/verification/guidance/verification_plan_template.rst @@ -136,30 +136,38 @@ Verification Plan Template Coverage of detailed design ^^^^^^^^^^^^^^^^^^^^^^^^^^^ - Beside :need:`wp__verification_comp_int_test` and :need:`wp__verification_sw_unit_test` the - following aspects define the coverage of detailed design. + This section defines how coverage of the detailed design is measured and achieved. - - Statement/Branch/Path coverage as defined by their specific thresholds - - Static analysis and Linting - - :need:`wp__sw_implementation_inspection` for safety-critical implementation + Coverage metrics with defined thresholds should be e.g. based on: + - Structural code coverage (e.g. by statement, branch, path coverage) + - Code quality metrics (e.g. by linting and static analysis) + - Traceability coverage (e.g. by a 100% requirements coverage by test cases) + + The section further documents the selected verification methods appropriate to achieve the defined + coverage goals (e.g. by :need:`wp__verification_sw_unit_test`, :need:`wp__verification_comp_int_test`, and + :need:`wp__sw_implementation_inspection`). Coverage of architectural design ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - Beside :need:`wp__verification_comp_int_test` and :need:`wp__verification_feat_int_test` the - following aspects define the coverage of the architectural design. + This section defines how coverage of the architectural design is measured and achieved. + It describes the metrics used to ensure completeness and quality of the architecture + and the verification methods applied to achieve the defined coverage goals + (e.g. by :need:`wp__verification_comp_int_test`, :need:`wp__verification_feat_int_test`, and + :need:`wp__sw_arch_verification`). - - :need:`wp__sw_arch_verification` - done by walkthrough (QM) or inspection (safety-critical parts) - - :need:`wp__sw_component_fmea` and :need:`wp__sw_component_dfa` for safety-critical parts - - :need:`wp__feature_fmea` and :need:`wp__feature_dfa` for safety-critical parts + Each valid traceable element shall have at least one test case linked with attribute `FullyVerified` or + multiple test cases with attribute `PartiallyVerified` to achieve a 100% requirement coverage metric. - Each architectural element has at least one test case linked with attribute `FullyVerified` or - multiple test cases with attribute `PartiallyVerified`. + The confirmation or any deviation of the coverage percentage value is documented in this section. Coverage of software requirements specifications ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - For a release all `valid` requirements need to have a complete test coverage of linked test cases. + For a release all `valid` requirements need to have a complete test coverage of linked test cases + leading to a 100% requirement coverage. + + The confirmation or any deviation of the coverage percentage value is documented in this section. Test Development ---------------- @@ -213,12 +221,12 @@ Verification Plan Template Independence of verification ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + This section describes how independence is achieved in the project. + As there are no separated roles for a software developer and test developer with :need:`rl__contributor` and :need:`rl__committer` it is important to achieve independence. This is done by having different people responsible for the test implementation and the actual code which gets tested. - This section describes how independence is achieved in the project. - Tools -----