Merge pull request #471 from eclipse-score/pahmann/verification-tailoring

Correct tailoring for verification process

Author: masc2023

process/process_areas/release_management/guidance/release_guideline.rst

@@ -18,7 +18,7 @@ Guideline
 .. gd_guidl:: Release Management Guideline
    :id: gd_guidl__rel_management
    :status: valid
-   :complies: std_req__iso26262__management_64131, std_req__iso26262__management_64132, std_req__iso26262__management_64133, std_req__iso26262__management_64134, std_req__iso26262__management_64135
+   :complies: std_req__iso26262__software_1041, std_req__iso26262__management_64131, std_req__iso26262__management_64132, std_req__iso26262__management_64133, std_req__iso26262__management_64134, std_req__iso26262__management_64135
 
 .. _workflow_release:
 
@@ -85,6 +85,7 @@ Platform Release
    * Prepare platform release notes summarizing the updates from all integrated software modules.
    * Check if all planned configuration items are in correct state (i.e. work products are valid, external libraries/tools are used in the correct released version).
    * Ensure the relevant safety packages are available and complete.
+   * Create/Maintain Platform Handbook for the release.
    * Tag the platform release in the repository.
 
 5. **Release Execution**:
@@ -109,11 +110,34 @@ Tracking and Communication
    * Hold periodic meetings to discuss progress, issues, and dependencies within the project lead circle.
    * meeting definition and schedule is defined in the projects's platform management plan, as defined in :need:`gd_guidl__platform_mgmt_plan`.
 
+Release Handbook
+----------------
+
+.. gd_guidl:: Release Handbook
+   :id: gd_guidl__rel_handbook
+   :status: valid
+   :complies: std_req__iso26262__software_1041
+
+   The release handbook incorporates an overview including a tutorial to explain the usage of the released software.
+   It extends as a decent documentation for users and contributors beyond the pure release notes created according to the template :need:`gd_temp__rel_plat_rel_note`.
+
+   It is intended to contain:
+
+   * Overview of the technologies used within the project
+   * Software architecture overview
+   * Module structure overview
+   * Integration process
+   * Getting started guide
+   * Contribution guide
+
+   By this the software integration approach becomes clear and reflects the dependencies and functional unit integration of the various modules.
+   It also describes how to build and run the software for the various target systems such as simulation, hardware architectures, and operating system(s).
+
 
 Templates
 =========
 
-For the release note a template has been created for module level and for platform level
+For the release note a template has been created for module level and for platform level.
 
 .. list-table:: Overview
    :header-rows: 1

process/process_areas/release_management/release_workflow.rst

@@ -77,7 +77,7 @@ For a detailed explanation of workflows and their role within the process model,
    :approved_by: rl__project_lead
    :input: wp__platform_safety_package, wp__platform_sw_release_plan, wp__verification_platform_ver_report
    :output: wp__platform_handbook
-   :contains:
+   :contains: gd_guidl__rel_handbook
    :has: doc_concept__rel_process, doc_getstrt__release_process
 
    The platform handbook is prepared and approved by the project lead circle.

process/process_areas/verification/guidance/verification_guideline.rst

@@ -142,7 +142,7 @@ Tailoring
    :id: gd_guidl__verification_req_tailored
    :status: valid
    :complies: std_req__iso26262__software_945,
-              std_req__iso26262__software_1041, std_req__iso26262__software_1045, std_req__iso26262__software_1046, std_req__iso26262__software_1047,
+              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

process/process_areas/verification/guidance/verification_report_template.rst

@@ -21,7 +21,7 @@ Verification Report Templates
     :id: gd_temp__mod_ver_report
     :status: valid
     :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__software_1041, 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,
@@ -97,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, std_req__iso26262__software_1044,
+    :complies: std_req__iso26262__software_1041, 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