Merge pull request #420 from eclipse-score/pahmann/verification-standard-linking

Add missing requirements link for verification process

Author: masc2023

process/process_areas/verification/guidance/verification_guideline.rst

@@ -134,3 +134,26 @@ Verification types and methods are described in the :need:`gd_meth__verification
 derivation techniques in :need:`gd_meth__verification_derivation`. The detailed method guideline
 helps to get an understanding what the different methods and derivation techniques mean and how to
 create test cases using the same.
+
+Tailoring
+=========
+
+.. gd_guidl:: Verification Requirements Tailored
+   :id: gd_guidl__verification_req_tailored
+   :status: valid
+   :complies: std_req__iso26262__software_945,
+              std_req__iso26262__software_1045, std_req__iso26262__software_1046, std_req__iso26262__software_1047,
+              std_req__iso26262__software_1141, std_req__iso26262__software_1142, std_req__iso26262__software_1143, std_req__iso26262__software_1144
+
+   This part of the guideline links to all the requirements which are not fulfilled by the
+   verification process. Make sure these are tailored out in the safety/security/quality plans
+   for your project (documented in the PMP). Reasoning given below must be confirmed there.
+
+   The reasoning is:
+
+   - For SW requirement 945 & 1047 tests are executed in target environment regarding code and hardware architecture.
+     An integrator of the software can re-execute them on source or unmodified binary in the product environnment.
+   - For SW requirement 1045 "Function and call coverage" are not considered explicitly due to lower target safety integrity level (ASIL_B).
+   - For SW requirement 1046 the software is not a production release, but work for the system integrator or distributor with a production release.
+   - For SW requirement 1141, 1143, 1144 the SW only points to AoUs, but will not be executed on the final product environment as part of the project scope.
+   - For SW requirement 1142 there will be :need:`wp__verification_platform_int_test` available for re-use, but they are not supposed to deliver full coverage.

process/process_areas/verification/guidance/verification_methods.rst

@@ -26,6 +26,7 @@ Methods
 .. gd_method:: Verification Methods
    :id: gd_meth__verification_methods
    :status: valid
+   :complies: std_req__iso26262__software_942, std_req__iso26262__software_944
 
    Following methods are explained
 
@@ -139,6 +140,7 @@ Derivation Techniques
 .. gd_method:: Verification Derivation Technique
    :id: gd_meth__verification_derivation
    :status: valid
+   :complies: std_req__iso26262__software_943, std_req__iso26262__software_1043
 
    Following derivation techniques are explained
 

process/process_areas/verification/guidance/verification_report_template.rst

@@ -20,7 +20,8 @@ Verification Report Templates
 .. gd_temp:: Module Verification Report Template
     :id: gd_temp__mod_ver_report
     :status: valid
-    :complies: std_req__iso26262__software_942, std_req__iso26262__software_1042, std_req__iso26262__software_1043,
+    :complies: std_req__iso26262__software_942, std_req__iso26262__software_943, std_req__iso26262__software_944,
+      std_req__iso26262__software_1042, std_req__iso26262__software_1043,
       std_req__iso26262__support_9431, std_req__iso26262__support_9432, std_req__iso26262__support_9433, std_req__iso26262__support_9434,
       std_req__iso26262__support_12422, std_req__iso26262__support_12423, std_req__iso26262__support_12424, std_req__iso26262__support_12425,
       std_req__iso26262__support_1243,
@@ -96,7 +97,7 @@ Verification Report Templates
 .. gd_temp:: Platform Verification Report Template
     :id: gd_temp__platform_ver_report
     :status: valid
-    :complies: std_req__iso26262__software_1042,
+    :complies: std_req__iso26262__software_1042, std_req__iso26262__software_1044,
       std_req__iso26262__support_9431, std_req__iso26262__support_9432, std_req__iso26262__support_9433, std_req__iso26262__support_9434,
       std_req__iso26262__analysis_749, std_req__iso26262__analysis_848
 

process/process_areas/verification/guidance/verification_specification.rst

@@ -18,7 +18,9 @@ Test Specification Guideline
 .. gd_guidl:: Test Specification Guideline
    :id: gd_guidl__verification_specification
    :status: valid
-   :complies: std_req__iso26262__support_9421, std_req__iso26262__support_9422, std_req__iso26262__support_9423, std_req__iso26262__support_9424
+   :complies: std_req__iso26262__software_942, std_req__iso26262__software_943,
+              std_req__iso26262__support_9421, std_req__iso26262__support_9422,
+              std_req__iso26262__support_9423, std_req__iso26262__support_9424
 
 Test specification
 ------------------

process/process_areas/verification/verification_workproducts.rst

@@ -142,6 +142,8 @@ Component
    Unit testing verifies detailed design (traced to).
    Respective tooling is defined in :need:`wp__platform_mgmt`, :need:`wp__verification_plan` and integrated in CI/Build.
    Unit testing is in responsible of the :need:`rl__contributor` providing the :need:`wp__sw_implementation`.
+   The compiled tests run against the actual source code compiled for the component or reference integration and their
+   targeted HW architecture (e.g. arm64 or x86).
 
 Inspection
 **********