Process description quality management takeover from old process repository

process/process_areas/index.rst

@@ -26,6 +26,7 @@ Process Areas
    implementation/index.rst
    platform_management/index.rst
    problem_resolution/index.rst
+   quality_management/index.rst
    release_management/index.rst
    requirements_engineering/index.rst
    safety_analysis/index.rst

process/process_areas/quality_management/guidance/index.rst

@@ -0,0 +1,26 @@
+..
+   # *******************************************************************************
+   # Copyright (c) 2025 Contributors to the Eclipse Foundation
+   #
+   # See the NOTICE file(s) distributed with this work for additional
+   # information regarding copyright ownership.
+   #
+   # This program and the accompanying materials are made available under the
+   # terms of the Apache License Version 2.0 which is available at
+   # https://www.apache.org/licenses/LICENSE-2.0
+   #
+   # SPDX-License-Identifier: Apache-2.0
+   # *******************************************************************************
+
+Guidance
+########
+
+.. toctree::
+   :maxdepth: 1
+
+   quality_report_template
+   quality_review_checklist
+   quality_plan_guideline
+   quality_process_reqs
+   quality_work_product_review_guideline
+   quality_plan_template

process/process_areas/quality_management/guidance/quality_plan_guideline.rst

@@ -0,0 +1,75 @@
+..
+   # *******************************************************************************
+   # Copyright (c) 2025 Contributors to the Eclipse Foundation
+   #
+   # See the NOTICE file(s) distributed with this work for additional
+   # information regarding copyright ownership.
+   #
+   # This program and the accompanying materials are made available under the
+   # terms of the Apache License Version 2.0 which is available at
+   # https://www.apache.org/licenses/LICENSE-2.0
+   #
+   # SPDX-License-Identifier: Apache-2.0
+   # *******************************************************************************
+
+.. _guideline_quality_plan:
+
+Guideline Quality Management Plan
+#################################
+
+.. gd_guidl:: Quality Management Plan Definitions Guideline
+   :id: gd_guidl__qlm_plan_definitions
+   :status: valid
+   :complies: std_wp__iso26262__management_553, 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 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:
+   | 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:
+   | 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:
+   | 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.
+   | Other issues and non-conformances relevant for already delivered releases will be identified as such and communicated (as defined in Problem Resolution part of the Project Management Plan) via the :need:`wp__issue_track_system`.
+   |
+   | **Tailoring quality activities:**
+   | Main tailoring driver is that the SW platform is pure SW development and is provided as "SW element" - this explains mainly the generic, platform wide tailoring.
+   | 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.
+   | 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
+   | * dependencies on other activities or information - by links to the respective issues
+   | * responsible person for the activity - as issue assignee
+   | * required resources for the activity - by selecting a team label (or "project") pointing to a team of committers dedicated to the issue resolution
+   | * duration in time, including start and end point - by selecting a milestone
+   | * UID of the resulting work products - stated in the issue title
+   |
+   | The planning of quality activities is part of
+   | * generic planning, dealing with all work products needed only once for the platform. This is included in the Quality Management Platform Plan.
+   |
+   | **Planning supporting processes:**
+   | Supporting processes (Requirements Management, Configuration Management, Change Management, Documentation Management, Tool Management) are planned within the Project Management Plan.
+   |
+   | **Planning integration and verification:**
+   | Integration on the target hardware is not done in the scope of the SW platform project, but SW/SW integration up to the feature level is performed and its test results are part of the :need:`wp__verification__platform_ver_report`.
+   | The integration on the target hardware, done by the distributor or OEM, is supported by delivering a set of HW/SW feature integration and platform tests which were already run successfully on a reference HW platform.
+   | This is planned by the respective workproducts:
+   | * :need:`wp__verification__feat_int_test`
+   | * :need:`wp__verification__platform_test`
+   | Verification planning is documented in :need:`wp__verification__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`.

process/process_areas/quality_management/guidance/quality_plan_template.rst

@@ -0,0 +1,123 @@
+..
+   # *******************************************************************************
+   # Copyright (c) 2025 Contributors to the Eclipse Foundation
+   #
+   # See the NOTICE file(s) distributed with this work for additional
+   # information regarding copyright ownership.
+   #
+   # This program and the accompanying materials are made available under the
+   # terms of the Apache License Version 2.0 which is available at
+   # https://www.apache.org/licenses/LICENSE-2.0
+   #
+   # SPDX-License-Identifier: Apache-2.0
+   # *******************************************************************************
+
+.. _quality templates:
+
+Template Quality Plan
+=====================
+
+.. gd_temp:: Quality Management Plan Template
+   :id: gd_temp__qlm_plan
+   :status: valid
+   :complies: std_wp__iso26262__management_553, 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
+
+:note: The quality management plan shall be continuously maintained during the project.
+       Deviations to the platform plan should be documented here.
+
+Purpose
+-------
+Description of the purpose of the Quality Management Plan.
+
+Statement of Independence
+-------------------------
+Description of the used approach for independence.
+
+Objectives and scope
+--------------------
+
+3.1 Quality Objectives
+^^^^^^^^^^^^^^^^^^^^^^
+
+.. list-table:: Standards to comply with
+    :header-rows: 1
+    :widths: 15,85,15
+
+    * - #
+      - **Standard Name**
+      - **Version**
+    * - 1
+      - Automotive SPICE PAM
+      - 4.0
+    * - 2
+      - ISO 262626:2018
+      - 2018
+    * - 3
+      - ISO/SAE 21434:2021
+      - 2021
+    * - 4
+      - ISO PAS 8926:2024 (will be integrated into ISO 26262 3rd edition as updated part 8 clause 12)
+      - 2024
+
+3.2 Quality Performance Objectives
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+Description of the Quality Performance Objectives.
+
+3.3 Quantitative Quality Goals
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+Description of the Quantitative Quality Goals.
+
+3.4 Work Product Quality Goals
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+Description of the Work Product Quality Goals.
+
+3.5 Quality Management Scope
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+Description of the Quality Management Scope.
+
+**Tailoring of quality assurance activities**
+Describe the used tailoring of quality assurance activities.
+
+3.6 Quality Management Organization
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+Describe the project strategy to qualify the platform or components of the platform to the appropriate international standards and directives.
+
+**Eclipse Roles**
+Description of Eclipse roles.
+
+**Project Roles**
+Description of project roles.
+
+**Critical dependencies**
+Description of critical dependencies.
+
+**Risks**
+Description of used risk management.
+
+**Skills**
+Description of the used skill approvals.
+
+1. Quality Management Planning
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+4.1 Quality Resources
+""""""""""""""""""""""
+Description of the used resources and milestones.
+Description of the planning of resources and milestones.
+
+4.2 Quality Management Communication
+""""""""""""""""""""""""""""""""""""
+Description of used Communication possibilities.
+
+**Reporting**
+Description of used reporting.
+
+**Escalation**
+Description of used Escalation path.
+
+4.3 Quality Management Specifics
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+Description of Quality Management Specifics.
+
+4.4 Quality Management Generic workproducts
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+Description of used Generic Workproducts for Quality Management.

process/process_areas/quality_management/guidance/quality_process_reqs.rst

@@ -0,0 +1,26 @@
+..
+   # *******************************************************************************
+   # Copyright (c) 2025 Contributors to the Eclipse Foundation
+   #
+   # See the NOTICE file(s) distributed with this work for additional
+   # information regarding copyright ownership.
+   #
+   # This program and the accompanying materials are made available under the
+   # terms of the Apache License Version 2.0 which is available at
+   # https://www.apache.org/licenses/LICENSE-2.0
+   #
+   # SPDX-License-Identifier: Apache-2.0
+   # *******************************************************************************
+
+Process Requirements
+====================
+
+.. gd_req:: Quality report automated generation
+   :id: gd_req__qlm_report
+   :status: valid
+   :tags: quality_management
+   :satisfies: wf__mr_imp_qlm_plan_processes
+   :complies: std_req__iso26262__management_5423, std_req__aspice_40__SUP-1-BP5, std_req__aspice_40__SUP-1-BP6
+
+   | The quality report shall be generated progressively and automatically compiling the work products.
+   | A template exists to guide the reporting and the right collection of the required work products.