issue_2501_addition_of_missing_safety_docs_templates

MODULE.bazel

@@ -29,7 +29,7 @@ bazel_dep(name = "rules_pkg", version = "1.1.0")
 # Python version
 #
 ###############################################################################
-bazel_dep(name = "rules_python", version = "1.4.1")
+bazel_dep(name = "rules_python", version = "1.8.3")
 
 PYTHON_VERSION = "3.12"
 

process/folder_templates/modules/module_name/docs/release/release_note.rst

@@ -122,9 +122,6 @@ Release Note
 | Contributor 1
 | Contributor 2
 |
-
----
-
 | Contact Information
 | -------------------
 |

process/folder_templates/modules/module_name/docs/verification/module_verification_report.rst

@@ -33,7 +33,6 @@ Verification Report
     - Adjust ``status`` to be ``valid``
     - Adjust ``safety`` and ``tags`` according to your needs
 
-
 This verification report is based on the :need:`gd_temp__verification_plan`.
 It covers all the components of the above stated module.
 
@@ -86,6 +85,12 @@ Verification Report contains:
 **5. Software component qualification verification report**
        - Contains the needed verification results if for some components a qualification of pre-developed SW is performed.
 
+**6. Test results**
+       - Test result per test case with status passed/failed/not_run
+
+**7. Test logs**
+       - Test log per test case with status passed/failed/not_run
+
 **Note1:** The verification report is valid for the module version tagged together with the report
 
 **Note2:** All the above lists are generated automatically

process/folder_templates/platform/docs/release/release_note.rst

@@ -0,0 +1,121 @@
+..
+   # *******************************************************************************
+   # 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
+   # *******************************************************************************
+
+Platform Release Note
+=====================
+
+.. note:: Document header
+
+.. document:: Platform Release Note
+   :id: doc__platform_release_note
+   :status: draft
+   :safety: ASIL_B
+   :security: NO
+   :realizes: wp__platform_sw_release_note
+   :tags: template
+
+   .. attention::
+    The above directive must be updated.
+
+    - Adjust ``status`` to be ``valid``
+    - Adjust ``safety`` and ``tags`` according to your needs
+
+
+
+| Release Tag: vX.Y.Z
+| Origin Release Tag: vU.V.W
+| Release Commit Hash: a1b2c3d4e5f6g7h8i9j0
+| Release Date: YYYY-MM-DD
+| Safety: [QM | ASIL_B]
+| Security: [NO | YES]
+|
+| Overview
+| --------
+|
+| This document provides an overview of the changes, improvements, and bug fixes included in the software platform release version vX.Y.Z
+|  as compared to the platform's origin release (which is usually the previous release).
+|
+|  Disclaimer
+|  ----------
+|  This release note does not "release for production", as it does not come with a safety argumentation and a performed safety assessment.
+|  The work products compiled in the safety package are created with care according to a process satisfying standards, but the as the project,
+|  being a non-profit and open source organization, can not take over any liability for its content.
+|
+| New Features
+| ------------
+|
+| - **Feature 1**: Brief description of the new feature.
+| - **Feature 2**: Brief description of the new feature.
+| - **Feature 3**: Brief description of the new feature.
+|
+| Improvements
+| ------------
+|
+| - **Improvement 1**: Brief description of the improvement.
+| - **Improvement 2**: Brief description of the improvement.
+| - **Improvement 3**: Brief description of the improvement.
+|
+| Bug Fixes
+| ---------
+|
+| - **Bug 1**: Brief description of the bug fix.
+| - **Bug 2**: Brief description of the bug fix.
+| - **Bug 3**: Brief description of the bug fix.
+|
+| Other changes by Label
+| ----------------------
+|
+| - **Label 1/Refactor 1**: Brief description of the change.
+| - **Label 2/Refactor 2**: Brief description of the change.
+| - **Label 3/Refactor 3**: Brief description of the change.
+|
+| Compatibility
+| -------------
+|
+| - **Dependencies**: List any dependencies and their versions.
+|
+|  Performed Verification
+|  ----------------------
+|  This release note is based on the verification as documented in platform verification report
+|  :need:`doc__platform_verification_report`.
+|
+| Known Issues
+| ------------
+|
+| - **Issue 1**: Brief description of the known issue. Justification regarding safety impact.
+| - **Issue 2**: Brief description of the known issue. Justification regarding safety impact.
+| - **Issue 3**: Brief description of the known issue. Justification regarding safety impact.
+|
+| Known Vulnerabilities
+| ---------------------
+|
+| - **CVE 1**: Brief description of the known CVE. Justification regarding security impact.
+| - **CVE 2**: Brief description of the known CVE. Justification regarding security impact.
+| - **CVE 3**: Brief description of the known CVE. Justification regarding security impact.
+|
+| Upgrade Instructions
+| --------------------
+|
+| 1. **Step 1**: Description of the first step.
+| 2. **Step 2**: Description of the second step.
+| 3. **Step 3**: Description of the third step.
+|
+| Contributors
+| ------------
+|
+| Thanks to everyone who contributed to this release:
+|
+| Contributor 1
+| Contributor 2
+|

process/folder_templates/platform/docs/safety_mgt/index.rst

@@ -0,0 +1,26 @@
+..
+   # *******************************************************************************
+   # Copyright (c) 2026 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 Management
+#################
+
+.. toctree::
+   :titlesonly:
+
+   platform_dfa
+   platform_safety_manual
+   platform_safety_plan_fdr
+   platform_safety_package_fdr
+   platform_safety_analysis_fdr
+   platform_safety_plan

process/folder_templates/platform/safety_analysis/platform_dfa.rst → process/folder_templates/platform/docs/safety_mgt/platform_dfa.rst

@@ -29,13 +29,6 @@ Platform DFA (Dependent Failure Analysis)
 
 .. note:: Use the content of the document to describe e.g. why a fault model is not applicable for the diagram.
 
-.. attention::
-    The above directive must be updated according to your Feature.
-
-    - Modify ``Your Feature Name`` to be your Feature Name
-    - Modify ``id`` to be your Feature Name in upper snake case preceded by ``doc__`` and succeeded by ``_dfa``
-    - Adjust ``status`` to be ``valid``
-    - Adjust ``safety`` and ``tags`` according to your needs
 
 Dependent Failure Initiators
 ----------------------------
@@ -44,10 +37,10 @@ Dependent Failure Initiators
 
     .. plat_saf_dfa:: <Title>
        :violates: <Feature architecture>
-       :id: plat_saf_DFA__<Feature>__<Element descriptor>
+       :id: plat_saf_DFA__Platform__<Element descriptor>
        :failure_id: <ID from DFA failure initiators :need:`gd_guidl__dfa_failure_initiators`>
        :failure_effect: "description of failure effect of the failure initiator on the element"
-       :mitigated_by: <ID from Feature Requirement | ID from AoU Feature Requirement>
+       :mitigated_by: <ID from Stakeholder Requirement | ID from AoU Feature Requirement>
        :mitigation_issue: <ID from Issue Tracker>
        :sufficient: <yes|no>
        :status: <valid|invalid>

process/folder_templates/platform/docs/safety_mgt/platform_safety_analysis_fdr.rst

@@ -0,0 +1,91 @@
+..
+   # *******************************************************************************
+   # Copyright (c) 2026 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
+   # *******************************************************************************
+
+
+Platform Safety Analysis Formal Review Report
+=============================================
+
+.. document:: Platform Safety Analysis Formal Review Report
+   :id: doc__platform_safety_analysis_fdr
+   :status: draft
+   :safety: ASIL_B
+   :security: YES
+   :realizes: wp__fdr_reports
+   :tags: template
+
+
+
+**Purpose**
+The purpose of this Safety Analysis (DFA and FMEA) formal review report template is to collect the topics to be checked during verification of the Platform Safety Analysis.
+
+**Conduct**
+As described in :need:`wf__p_formal_rv`, the formal document review is performed by an "external" safety manager:
+
+- reviewer: **<committer with safety manager skills explicitly named here>**
+
+**Checklist**
+
+Please note that it is mandatory to fill in the "passed" column with "yes" or "no" for each checklist item and additional to add in the remarks why it is passed or not passed. In case of "no" an issue link to the issue tracking system has to be added in the last column. See also :ref:`review_concept` for further information about reviews in general and inspection in particular.
+
+.. list-table:: Safety Analysis Checklist
+      :header-rows: 1
+      :widths: 10,10,30,30,20
+
+      * - ID
+        - Safety analysis activity
+        - Compliant to ISO 26262?
+        - Reference
+        - Comment
+
+      * - 1
+        - Is it plausible that each potential identified dependent failure that has been identified, will lead to a dependent failure which cause a violation of FFI?
+        - [YES | NO ]
+        - :need:`[[title]] <std_req__iso26262__analysis_742>`
+        - <Rationale for result>
+
+      * - 2
+        - Are the failure initiators :need:`[[title]] <gd_guidl__dfa_failure_initiators>` / fault models :need:`[[title]] <gd_guidl__fault_models>` applied?
+        - [YES | NO ]
+        - :need:`[[title]] <std_req__iso26262__analysis_744>`
+        - <Rationale for result>
+
+      * - 3
+        - Are measures defined to resolute the identified potential dependent failures?
+        - [YES | NO ]
+        - :need:`[[title]] <std_req__iso26262__analysis_746>`, :need:`[[title]] <std_req__iso26262__analysis_747>`
+        - <Rationale for result>
+
+      * - 4
+        - Is the result of the safety analysis indicate if the safety requirements are complied?
+        - [YES | NO ]
+        - :need:`[[title]] <std_req__iso26262__analysis_842>`
+        - <Rationale for result>
+
+      * - 5
+        - Are for all not complied safety requirements mitigations defined to resolute the non-compliance? The mitigations shall have a direct influence on the violation by prevention, detection or mitigation to reduce the risk to an acceptable level.
+        - [YES | NO ]
+        - :need:`[[title]] <std_req__iso26262__analysis_843>`
+        - <Rationale for result>
+
+      * - 6
+        - Are the mitigations effective and implemented?
+        - [YES | NO ]
+        - :need:`[[title]] <std_req__iso26262__analysis_844>`
+        - <Rationale for result>
+
+      * - 7
+        - Are the templates for DFA and/or FMEA used? See :ref:`dfa_templates` / :ref:`FMEA_templates` and also :ref:`process_requirements_safety_analysis`
+        - [YES | NO ]
+        - :need:`[[title]] <std_req__iso26262__analysis_748>`, :need:`[[title]] <std_req__iso26262__analysis_849>`, :need:`[[title]] <std_req__iso26262__analysis_8410>`
+        - <Rationale for result>