create safety management process description

docs/platform_management_plan/release_management.rst

@@ -1,6 +1,6 @@
 ..
    # *******************************************************************************
-   # Copyright (c) 2024 Contributors to the Eclipse Foundation
+   # Copyright (c) 2025 Contributors to the Eclipse Foundation
    #
    # See the NOTICE file(s) distributed with this work for additional
    # information regarding copyright ownership.
@@ -12,6 +12,8 @@
    # SPDX-License-Identifier: Apache-2.0
    # *******************************************************************************
 
+.. _release_management:
+
 Release management
 ------------------------
 

docs/platform_management_plan/safety_management.rst

@@ -14,8 +14,8 @@
 
 .. _safety_management:
 
-Safety management
-------------------------
+Safety management Plan
+----------------------
 
 Purpose
 +++++++
@@ -34,28 +34,36 @@ Tailoring of safety activities:
 
 The following ISO26262 defined safety work products are not relevant for the SCORE SW platform development:
 
-Because these are in responsibility of the system integrator: :need:`STD_WP_ISO26262__management_11`,
-:need:`STD_WP_ISO26262__system_2`, :need:`STD_WP_ISO26262__system_3`, :need:`STD_WP_ISO26262__system_4`,
-:need:`STD_WP_ISO26262__system_5`, :need:`STD_WP_ISO26262__system_6`, :need:`STD_WP_ISO26262__system_7`,
-:need:`STD_WP_ISO26262__system_8`, :need:`STD_WP_ISO26262__system_9`, :need:`STD_WP_ISO26262__system_10`,
-:need:`STD_WP_ISO26262__system_11`
+Because these are in responsibility of the system integrator: :need:`std_wp_iso26262__management_11`,
+:need:`std_wp_iso26262__system_2`, :need:`std_wp_iso26262__system_3`, :need:`std_wp_iso26262__system_4`,
+:need:`std_wp_iso26262__system_5`, :need:`std_wp_iso26262__system_6`, :need:`std_wp_iso26262__system_7`,
+:need:`std_wp_iso26262__system_8`, :need:`std_wp_iso26262__system_9`, :need:`std_wp_iso26262__system_10`,
+:need:`std_wp_iso26262__system_11`
 
-Because there is no calibration used for the SCORE SW platform components, only configuration: :need:`STD_WP_ISO26262__software_19`,
-:need:`STD_WP_ISO26262__software_21`, :need:`STD_WP_ISO26262__software_24`
+Note that stakeholder requirements (:need:`std_wp_iso26262__system_1`) are in scope of the project,
+to be able to cover System and HW related failures which are usually covered by SW (e.g. end to end protection for ECU external communication).
+But those are the "Assumed Technical Safety Requirements" of the SW platform SEooC and do not need to be tested by SEooC supplier.
+I.e. the system testing is out of scope.
+There will be HW/SW integration tests of feature requirements, as required by ISO 26262 part 6.
+These may be reused by the user on his HW platform also to cover his Technical Safety Requirements towards the SW platform.
+But this is the decision of the user.
+
+Because there is no calibration used for the SCORE SW platform components, only configuration: :need:`std_wp_iso26262__software_19`,
+:need:`std_wp_iso26262__software_21`, :need:`std_wp_iso26262__software_24`
 
 Because distributed development is not how the project is organized. All contributors are seen as part of the project team.
-When used, OSS components are qualified and external SEooCs are integrated in the project scope: :need:`STD_WP_ISO26262__support_1`,
-:need:`STD_WP_ISO26262__support_2`, :need:`STD_WP_ISO26262__support_3`, :need:`STD_WP_ISO26262__support_4`, :need:`STD_WP_ISO26262__support_5`
+When used, OSS components are qualified and external SEooCs are integrated in the project scope: :need:`std_wp_iso26262__support_1`,
+:need:`std_wp_iso26262__support_2`, :need:`std_wp_iso26262__support_3`, :need:`std_wp_iso26262__support_4`, :need:`std_wp_iso26262__support_5`
 
-Because in the SCORE SW platform HW elements are out of scope: :need:`STD_WP_ISO26262__support_21`, :need:`STD_WP_ISO26262__support_22`, :need:`STD_WP_ISO26262__support_23`
+Because in the SCORE SW platform HW elements are out of scope: :need:`std_wp_iso26262__support_21`, :need:`std_wp_iso26262__support_22`, :need:`std_wp_iso26262__support_23`
 
-Because in the SCORE SW platform a proven in use argument will not be applied: :need:`STD_WP_ISO26262__support_24`, :need:`STD_WP_ISO26262__support_25`
+Because in the SCORE SW platform a proven in use argument will not be applied: :need:`std_wp_iso26262__support_24`, :need:`std_wp_iso26262__support_25`
 
-Because in the SCORE SW platform interfacing of out of scope of ISO 26262 applications is not planned: :need:`STD_WP_ISO26262__support_26`
+Because in the SCORE SW platform interfacing of out of scope of ISO 26262 applications is not planned: :need:`std_wp_iso26262__support_26`
 
-Because in the SCORE SW platform integration of safety-related systems not developed according to ISO 26262 is not planned: :need:`STD_WP_ISO26262__support_27`
+Because in the SCORE SW platform integration of safety-related systems not developed according to ISO 26262 is not planned: :need:`std_wp_iso26262__support_27`
 
-Because in the SCORE SW platform no ASIL decomposition is planned: :need:`STD_WP_ISO26262__analysis_1`, :need:`STD_WP_ISO26262__analysis_2`
+Because in the SCORE SW platform no ASIL decomposition is planned: :need:`std_wp_iso26262__analysis_1`, :need:`std_wp_iso26262__analysis_2`
 
 
 

docs/platform_management_plan/software_development.rst

@@ -1,6 +1,6 @@
 ..
    # *******************************************************************************
-   # Copyright (c) 2024 Contributors to the Eclipse Foundation
+   # Copyright (c) 2025 Contributors to the Eclipse Foundation
    #
    # See the NOTICE file(s) distributed with this work for additional
    # information regarding copyright ownership.
@@ -12,6 +12,8 @@
    # SPDX-License-Identifier: Apache-2.0
    # *******************************************************************************
 
+.. _sw_development:
+
 Software Development
 ------------------------
 

docs/process/index.rst

@@ -34,6 +34,15 @@ Process Model
 The SCORE process model is described by workflows, executed by roles and is creating work products.
 Workflow activities are supported by guidances.
 
+Process Description
+~~~~~~~~~~~~~~~~~~~
+
+.. toctree::
+   :maxdepth: 1
+   :glob:
+
+   process_areas/safety_management/index.rst
+
 Process Role definition
 ~~~~~~~~~~~~~~~~~~~~~~~
 

docs/process/process_areas/safety_management/guidance/checklist_safety_case_cmr.rst

@@ -0,0 +1,60 @@
+..
+   # *******************************************************************************
+   # 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
+   # *******************************************************************************
+
+Safety Case Confirmation Review Checklist
+=========================================
+
+.. gd_chklst:: Safety Case Confirmation Review Checklist
+   :id: gd_chklst__safety_case
+   :status: valid
+   :complies: std_req_iso26262__management_45, std_req_iso26262__management_46, std_req_iso26262__management_47, std_req_iso26262__management_48, std_req_iso26262__management_49, std_req_iso26262__management_50, std_req_iso26262__management_51, std_req_iso26262__management_52
+
+   **1. Purpose**
+
+   The purpose of this safety case confirmation review checklist is to report status of the confirmation review for the safety case.
+
+   **2. Checklist**
+
+.. list-table:: Safety Case Checklist
+        :header-rows: 1
+
+        * - Id
+          - Safety case activity
+          - Compliant to ISO 26262?
+          - Comment
+
+        * - 1
+          - Is a safety case provided which matches the safety plan (i.e. all planned workproducts referenced)?
+          - [YES | NO ]
+          - <Rationale for result>
+
+        * - 2
+          - Is the argument how functional safety is achieved, provided in the safety case, plausible and sufficient?
+          - NO
+          - The argument is intentionally not provided by SCORE.
+
+        * - 3
+          - Are the referenced work products available?
+          - [YES | NO ]
+          - <Rationale for result>
+
+        * - 4
+          - Are the referenced work products in released state, including the functional safety audit?
+          - [YES | NO ]
+          - <Rationale for result>
+
+        * - 5
+          - If safety related deviations from the process or safety concept are documented, are these argued understandably?
+          - [YES | NO ]
+          - <Rationale for result>

docs/process/process_areas/safety_management/guidance/checklist_safety_plan_cmr.rst

@@ -0,0 +1,91 @@
+..
+   # *******************************************************************************
+   # 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
+   # *******************************************************************************
+
+Safety Plan Confirmation Review Checklist
+=========================================
+
+.. gd_chklst:: Safety Plan Confirmation Review Checklist
+   :id: gd_chklst__safety_plan
+   :status: valid
+   :complies: std_req_iso26262__management_45, std_req_iso26262__management_46, std_req_iso26262__management_47, std_req_iso26262__management_48, std_req_iso26262__management_49, std_req_iso26262__management_50, std_req_iso26262__management_51, std_req_iso26262__management_52
+
+   **1. Purpose**
+
+   The purpose of this safety plan confirmation review checklist is to report status of the confirmation review for the safety plan.
+
+   **2. Checklist**
+
+.. list-table:: Safety Plan Checklist
+        :header-rows: 1
+
+        * - Id
+          - Safety plan activity
+          - Compliant to ISO 26262?
+          - Comment
+
+        * - 1
+          - Is the rationale for the safety work products tailoring included?
+          - [YES | NO ]
+          - <Rationale for result>
+
+        * - 2
+          - Is impact analysis planned in case of re-use of SW (needed for every release following the first formal release)?
+          - [YES | NO ]
+          - <Rationale for result>
+
+        * - 3
+          - Does the safety plan define all needed activities for safety management (incl. Confirmation review and Safety Audit)?
+          - [YES | NO ]
+          - <Rationale for result>
+
+        * - 4
+          - Does the safety plan define all needed activites for System and SW develpoment, integration and verification?
+          - [YES | NO ]
+          - <Rationale for result>
+
+        * - 5
+          - Does the safety plan define all needed activites for safety analysis and DFA?
+          - [YES | NO ]
+          - <Rationale for result>
+
+        * - 6
+          - Does the safety plan define all needed activites for supporting processes (incl. tool mgt)?
+          - [YES | NO ]
+          - <Rationale for result>
+
+        * - 7
+          - Does the safety plan document a responsible for all activities?
+          - [YES | NO ]
+          - <Rationale for result>
+
+        * - 8
+          - If OSS software components is used, is it planned to be qualified?
+          - [YES | NO ]
+          - <Rationale for result>
+
+        * - 9
+          - Is a safety manager and a project manager appointed for the project?
+          - [YES | NO ]
+          - <Rationale for result>
+
+        * - 10
+          - Is safety plan sufficiently linked to the project plan?
+          - [YES | NO ]
+          - <Rationale for result>
+
+        * - 11
+          - Is safety plan updated iteratively to show the progress?
+          - [YES | NO ]
+          - <Rationale for result>
+