Merge pull request #467 from eclipse-score/pahmann/verification-analysis

Add artifacts for requirements analysis

Author: masc2023

process/folder_templates/features/feature_name/requirements/chklst_req_inspection.rst

@@ -131,7 +131,13 @@ Requirement Inspection Checklist
         -
       * - REQ_08_01
         - Is the requirement *verifiable*?
-        - If at the time of the inspection already tests are created for the requirement, the answer is yes. This can be checked via traces, but also :need:`gd_req__req_attr_test_covered` shows this. In case the requirement is not sufficiently traced to test cases already, a test expert is invited to the inspection to give his opinion whether the requirement is formulated in a way that supports test development and the available test infrastructure is sufficient to perform the test.
+        - If at the time of the inspection already tests are created for the requirement, the answer is yes. This can be checked via traces, but also :need:`gd_req__req_attr_test_covered` shows this. In case the requirement is not sufficiently traced to test cases already, a test expert is invited to the inspection to give their opinion whether the requirement is formulated in a way that supports test development and the available test infrastructure is sufficient to perform the test.
+        -
+        -
+        -
+      * - REQ_08_02
+        - Is the requirement verifiable by design or code review in case it is not feasibly testable?
+        - In very rare cases a requirement may not be verifiable by test cases, for example a specific non-functional requirement. In this case a requirement analysis verifies the requirement by design/code review. If such a requirement is in scope of this inspection, please check this here and link to the respective review record. A test expert is invited to the inspection to confirm their opinion that the requirement is not testable.
         -
         -
         -

process/folder_templates/modules/module_name/component_name/docs/requirements/chklst_req_inspection.rst

@@ -131,7 +131,13 @@ Requirement Inspection Checklist
         -
       * - REQ_08_01
         - Is the requirement *verifiable*?
-        - If at the time of the inspection already tests are created for the requirement, the answer is yes. This can be checked via traces, but also :need:`gd_req__req_attr_test_covered` shows this. In case the requirement is not sufficiently traced to test cases already, a test expert is invited to the inspection to give his opinion whether the requirement is formulated in a way that supports test development and the available test infrastructure is sufficient to perform the test.
+        - If at the time of the inspection already tests are created for the requirement, the answer is yes. This can be checked via traces, but also :need:`gd_req__req_attr_test_covered` shows this. In case the requirement is not sufficiently traced to test cases already, a test expert is invited to the inspection to give their opinion whether the requirement is formulated in a way that supports test development and the available test infrastructure is sufficient to perform the test.
+        -
+        -
+        -
+      * - REQ_08_02
+        - Is the requirement verifiable by design or code review in case it is not feasibly testable?
+        - In very rare cases a requirement may not be verifiable by test cases, for example a specific non-functional requirement. In this case a requirement analysis verifies the requirement by design/code review. If such a requirement is in scope of this inspection, please check this here and link to the respective review record. A test expert is invited to the inspection to confirm their opinion that the requirement is not testable.
         -
         -
         -

process/process_areas/verification/verification_concept.rst

@@ -167,8 +167,7 @@ stakeholder requirements as stakeholder requirements describe the platform behav
 
 Note that all the above tests shall only link to requirements of type "Functional" and "Interface".
 The verification of requirements of types "Process" and "Non-Functional" will be done via Analysis,
-which is a verification method still to be defined. ``[TODO: Link to Analysis process once available. See ticket #577]``
-
+which is part of the requirement inspection :need:`doc__feature_name_req_inspection` and :need:`doc__component_name_req_inspection`.
 Requirements always include Assumptions Of Use.
 
 A more detailed description of how to link code to requirements is available here: :need:`gd_req__verification_link_tests`