Improvement: Quality Management, ML2 #65

process/process_areas/quality_management/guidance/quality_plan_guideline.rst

@@ -23,20 +23,20 @@ Guideline Quality Management Plan
    :complies: std_req__iso26262__management_5423, std_req__aspice_40__SUP-1-BP1, std_req__aspice_40__SUP-1-BP2, std_req__aspice_40__SUP-1-BP3, std_req__aspice_40__SUP-1-BP4, std_req__aspice_40__SUP-1-BP7, std_req__aspice_40__PIM-3-BP1, std_req__aspice_40__PIM-3-BP2, std_req__aspice_40__PIM-3-BP3, std_req__aspice_40__PIM-3-BP4, std_req__aspice_40__PIM-3-BP5, std_req__aspice_40__PIM-3-BP6, std_req__aspice_40__PIM-3-BP7, std_req__aspice_40__SUP-1-BP5, std_req__aspice_40__SUP-1-BP6, std_req__aspice_40__PIM-3-BP8
 
    | **Overall quality management:**
-   | Quality culture:
+   |
+   | **Quality culture:**
    | Quality as well as Safety and Security Culture is planned to grow in the SW platform. This shall be fostered by doing process conformance checks and work product reviews, as well as lessons learned
    | after each feature development completion and a process audit after each platform/project release. Delta audits allowed based on variation statement.
    | The main outcome is the :need:`wp__process_impr_report`, which is used to improve the processes for the platform/project.
-
    |
-   | Quality Management:
+   | **Quality Management:**
    | ASPICE 4.0 standard is selected for quality management. Processes will always link to the :ref:`standard_iso26262` standard, :ref:`standard_isopas8926` standard, :ref:`standard_isosae21434` and to the `ASPICE 4.0 <https://eclipse-score.github.io/process_description/main/standards/aspice_40/aspice.html>`_ standard.
    |
-   | Communication:
+   | **Communication:**
    | Cross functional teams are interdisciplinary, so the regular (sprint) planning and review meetings enable communication. The organization of the project is described in the Project Management Plan. Another main communication means are the Pull Request (PR) reviews.
    | Also the standard Eclipse Foundation communication strategies are used (e.g. mailing lists, messenger).
    |
-   | Quality issues, non-conformances and improvements:
+   | **Quality issues, non-conformances and improvements:**
    | Feedback from the field, but also during development of change requests to existing features, bug reporting by the Open Source community or integration of existing SW components into new features may lead to the discovery of issues, non-conformances or improvements.
    | Non-conformance can also be deviations from the development process with impact on safety or security.
    | If these are known at the time of creation of a release they will be part of the :need:`wp__platform_sw_release_note` for the feature.
@@ -47,7 +47,7 @@ Guideline Quality Management Plan
    | Tailoring is done for the whole SW platform by defining only the relevant processes and their resulting outcomes and an argumentation why the others are not needed in `ASPICE 4.0 <https://eclipse-score.github.io/process_description/main/standards/aspice_40/aspice.html>`_.
    |
    | **Planning quality activities:**
-   | In the Quality Management Plan the nomination of the quality manager :need:`rl__quality_manager` and the project lead :need:`rl__project_lead` is documented.
+   | In the Quality Management Plan the nomination of the :need:`rl__quality_manager` and the :need:`rl__project_lead` is documented.
    | The planning of quality activities is done using issues in the :need:`wp__issue_track_system` as specified in the Project Management part of the Project Management Plan.
    | It contains for each issue
    | * objective - as part of the issue description
@@ -73,3 +73,11 @@ Guideline Quality Management Plan
    |
    | **Scheduling of audits, conformance checks, work product reviews, release verification and approval:**
    | Scheduling is done in the same way as for all work products definition by issues. The respective work products are listed in :need:`doc_concept__wp_inspections`.
+   |
+   | **Planning quality trainings:**
+   | Quality trainings are planned also by issues. They should cover the following aspects:
+   | * Target audience
+   | * Training objectives
+   | * Training content
+   | * Training schedule
+   | * Responsible persons

process/process_areas/quality_management/guidance/quality_report_template.rst

@@ -22,43 +22,36 @@ Template Quality Report
    :status: valid
    :complies: std_req__iso26262__management_5423, std_req__aspice_40__SUP-1-BP1, std_req__aspice_40__SUP-1-BP2, std_req__aspice_40__SUP-1-BP3, std_req__aspice_40__SUP-1-BP4, std_req__aspice_40__SUP-1-BP7, std_req__aspice_40__PIM-3-BP1, std_req__aspice_40__PIM-3-BP2, std_req__aspice_40__PIM-3-BP3, std_req__aspice_40__PIM-3-BP4, std_req__aspice_40__PIM-3-BP5, std_req__aspice_40__PIM-3-BP6, std_req__aspice_40__PIM-3-BP7
 
-   This document implements :need:`wp__qms_report`.
+   This document implements :need:`wp__qms_report` and based on the :need:`wp__qms_plan`. It summarizes
+   the results of the quality related activities. It shall be referred in the :need:`wp__platform_sw_release_note`
+   of a platform release.
 
-      | Place the document header here following the `REPLACE_doc__documentation_mgt_plan`.
-      |
-      | This Quality Report is based on the :need:`wp__qms_plan`.
-      |
-      | Quality Report contains:
-      |
-      | **1. Quality Overview**
-      |
-      | **1.1. Lists of all work products**
-      | - List of all work products, compared to the :need:`wp__qms_plan`
-      | - Status (valid / invalid)
-      |
-      | **1.2. Lists of all reports**
-      | - List of all reports, compared to the :need:`wp__qms_plan`
-      | - Results of the reports
-      |
-      | **1.3. Test coverage**
-      | - Overview of test coverage (overall, requirements, architecture)
-      | - Ratio of test coverage to the :need:`wp__verification_plan`
-      |
-      | **1.4. Issues**
-      | - List of all issues, compared to the :need:`wp__qms_plan`
-      | - Status of the issues (open / closed)
-      |
-      | **1.5. Quality Trainings**
-      | - List of all quality trainings, compared to the :need:`wp__qms_plan`
-      | - Status of the quality trainings (planned / completed)
-      |
-      | **1.5. Process Improvement**
-      | - List of all process improvements, compared to the :need:`wp__process_impr_report`
-      | - Status of the process improvements (open / closed)
-      |
-      | **1.6. External reports**
-      | - List of all external reports, compared to the :need:`wp__qms_plan`
-      | - Status of the external reports (valid / invalid)
-      |
+   The Quality Report contains:
+
+   **1. Quality Overview**
+
+   **1.1. Quality Objectives and Goals**
+    - Quality objectives and goals as defined in the :need:`wp__qms_plan`
+    - Status of achievement of the quality objectives and goals
+
+   **1.2. Lists of all work products**
+    - List of all work products, compared to the :need:`wp__qms_plan`
+    - Status (valid / invalid)
+
+   **1.3. Lists of all reports**
+    - List of all reports, compared to the :need:`wp__qms_plan`
+    - Results of the reports
+
+   **1.4. Test coverage**
+    - Overview of test coverage (overall, requirements, architecture)
+    - Ratio of test coverage to the :need:`wp__verification_plan`
+
+   **1.5. Issues**
+    - List of all issues, compared to the :need:`wp__qms_plan`
+    - Status of the issues (open / closed)
+
+   **1.6. Process Improvement**
+    - List of all process improvements, compared to the :need:`wp__process_impr_report`
+    - Status of the process improvements (open / closed)
 
     **Note1:** All the above lists are generated automatically