Improvement: adapt process area overview status

process/folder_templates/modules/module_name/docs/safety_mgt/index.rst

@@ -21,3 +21,4 @@ Safety Management
    module_safety_plan
    module_safety_plan_fdr
    module_safety_package_fdr
+   module_safety_analysis_fdr

process/folder_templates/modules/module_name/docs/safety_mgt/module_safety_analysis_fdr.rst

@@ -0,0 +1,92 @@
+..
+   # *******************************************************************************
+   # 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 Analysis Checklist
+=========================
+
+.. document:: [Your Module Name] Safety Analysis Checklist
+   :id: doc__module_name_safety_analysis_fdr
+   :status: draft
+   :safety: ASIL_B
+   :security: YES
+   :realizes: wp__fdr_reports
+   :tags: template
+
+.. attention::
+    The above directive must be updated according to your Module.
+
+    - Modify ``Your Module Name`` to be your Module Name
+    - Modify ``id`` to be your Module Name in lower snake case preceded by ``doc__`` and followed by ``_safety _analysis_fdr``
+    - Adjust ``status`` to be ``valid``
+    - Adjust ``safety``, ``security`` and ``tags`` according to your needs
+
+
+**Purpose**
+The purpose of this Safety Analysis (DFA and FMEA) checklist template is to collect the topics to be checked during verification of the Safety Analysis.
+
+**Checklist**
+
+.. list-table:: Safety Analysis Checklist
+      :header-rows: 1
+      :widths: 10,30,30,15,8,8
+
+      * - Review ID
+        - Acceptance Criteria
+        - Guidance
+        - Passed
+        - Remarks
+        - Issue link
+      * - REQ_01_01
+        - Is / are the attribute sufficient set correctly?
+        - The mitigations shall have a direct influence ont the violation by prevention, detection or mitigation to reduce the risk to an acceptable level.
+        - The mitigations are sufficient.
+        - <yes|no>
+        -
+      * - REQ_01_02
+        - Are the templates for DFA and/or FMEA used?
+        - See :ref:`dfa_templates` / :ref:`FMEA_templates` and also :ref:`process_requirements_safety_analysis`
+        - Templates are used to generate the DFA or / and FMEA.
+        - <yes|no>
+        -
+      * - REQ_01_03
+        - Were the failure initiators / fault models applied?
+        - See :need:`gd_guidl__dfa_failure_initiators` / :need:`gd_guidl__fault_models`
+        - The applicable items of the failure initiators / fault models are used to ensure a structured analysis. For all not applicable items an argument shall be given in the content of the document.
+        - <yes|no>
+        -
+      * - REQ_01_04
+        - Are the failure effects clearly and completely described?
+        - Use the generic failure effect descriptions and enlarge the description if it's applicable to the considered element.
+        - The effects of the failure is described completely. The effect can be recognized easily.
+        - <yes|no>
+        -
+      * - REQ_01_06
+        - Is the attribute "mitigated by" linked correct?
+        - Check if the correct failure effect is linked via "mitigated by".
+        - The "mitigated by" link is correct.
+        - <yes|no>
+        -
+      * - REQ_01_07
+        - Is the sufficiency of the "mitigated by" (prevention, detection or mitigation) described or can it be recognized easily?
+        - The sufficiency of the "mitigated by" is described in the content of the document. It can be recognized easily.
+        - The "mitigated by" shows clearly that a fault / failure can be mitigated by the linked requirement by prevention, detection or mitigation. It shall be described in the contend.
+        - <yes|no>
+        -
+      * - REQ_01_08
+        - Is the overall result of the Safety Analysis described in the report?
+        - It shall be shown in the report if the Safety Analysis are finished and if all artifacts are "valid" and "sufficient".
+        - The results of the Safety Analysis are described in the report. The report is available :need:`wp__verification_platform_ver_report`.
+        - <yes|no>
+        -

process/folder_templates/platform/index.rst

@@ -23,3 +23,4 @@ Platform
    safety_analysis/platform_dfa.rst
    requirements/stakeholder/chklst_req_inspection.rst
    safety_planning/index.rst
+   safety_planning/platform_safety_analysis_fdr.rst

process/folder_templates/platform/safety_planning/platform_safety_analysis_fdr.rst

@@ -0,0 +1,92 @@
+..
+   # *******************************************************************************
+   # 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 Analysis Checklist
+=========================
+
+.. document:: [Your Platform Name] Safety Analysis Checklist
+   :id: doc__platform_name_safety_analysis_fdr
+   :status: draft
+   :safety: ASIL_B
+   :security: YES
+   :realizes: wp__fdr_reports
+   :tags: template
+
+.. attention::
+    The above directive must be updated according to your Platform.
+
+    - Modify ``Your Platform Name`` to be your Platform Name
+    - Modify ``id`` to be your Platform Name in lower snake case preceded by ``doc__`` and followed by ``_safety _analysis_fdr``
+    - Adjust ``status`` to be ``valid``
+    - Adjust ``safety``, ``security`` and ``tags`` according to your needs
+
+
+**Purpose**
+The purpose of this Safety Analysis (DFA and FMEA) checklist template is to collect the topics to be checked during verification of the Safety Analysis.
+
+**Checklist**
+
+.. list-table:: Safety Analysis Checklist
+      :header-rows: 1
+      :widths: 10,30,30,15,8,8
+
+      * - Review ID
+        - Acceptance Criteria
+        - Guidance
+        - Passed
+        - Remarks
+        - Issue link
+      * - REQ_01_01
+        - Is / are the attribute sufficient set correctly?
+        - The mitigations shall have a direct influence ont the violation by prevention, detection or mitigation to reduce the risk to an acceptable level.
+        - The mitigations are sufficient.
+        - <yes|no>
+        -
+      * - REQ_01_02
+        - Are the templates for DFA and/or FMEA used?
+        - See :ref:`dfa_templates` / :ref:`FMEA_templates` and also :ref:`process_requirements_safety_analysis`
+        - Templates are used to generate the DFA or / and FMEA.
+        - <yes|no>
+        -
+      * - REQ_01_03
+        - Were the failure initiators / fault models applied?
+        - See :need:`gd_guidl__dfa_failure_initiators` / :need:`gd_guidl__fault_models`
+        - The applicable items of the failure initiators / fault models are used to ensure a structured analysis. For all not applicable items an argument shall be given in the content of the document.
+        - <yes|no>
+        -
+      * - REQ_01_04
+        - Are the failure effects clearly and completely described?
+        - Use the generic failure effect descriptions and enlarge the description if it's applicable to the considered element.
+        - The effects of the failure is described completely. The effect can be recognized easily.
+        - <yes|no>
+        -
+      * - REQ_01_06
+        - Is the attribute "mitigated by" linked correct?
+        - Check if the correct failure effect is linked via "mitigated by".
+        - The "mitigated by" link is correct.
+        - <yes|no>
+        -
+      * - REQ_01_07
+        - Is the sufficiency of the "mitigated by" (prevention, detection or mitigation) described or can it be recognized easily?
+        - The sufficiency of the "mitigated by" is described in the content of the document. It can be recognized easily.
+        - The "mitigated by" shows clearly that a fault / failure can be mitigated by the linked requirement by prevention, detection or mitigation. It shall be described in the contend.
+        - <yes|no>
+        -
+      * - REQ_01_08
+        - Is the overall result of the Safety Analysis described in the report?
+        - It shall be shown in the report if the Safety Analysis are finished and if all artifacts are "valid" and "sufficient".
+        - The results of the Safety Analysis are described in the report. The report is available :need:`wp__verification_platform_ver_report`.
+        - <yes|no>
+        -

process/process_areas/safety_analysis/guidance/safety_analysis_checklist.rst

@@ -20,61 +20,10 @@ Safety Analysis Checklist
    :id: gd_chklst__safety_analysis
    :status: valid
    :tags: safety_analysis
+   :complies: std_req__iso26262__management_64101, std_req__iso26262__management_64102, std_req__iso26262__management_64103, std_req__iso26262__management_64104, std_req__iso26262__management_64105
 
-   **Purpose**
-   The purpose of this Safety Analysis (DFA and FMEA) checklist template is to collect the topics to be checked during verification of the Safety Analysis.
 
-   **Checklist**
+    For the content see here:
 
-   .. list-table:: Safety Analysis Checklist
-      :header-rows: 1
-      :widths: 10,30,30,15,8,8
-
-      * - Review ID
-        - Acceptance Criteria
-        - Guidance
-        - Passed
-        - Remarks
-        - Issue link
-      * - REQ_01_01
-        - Is / are the attribute sufficient set correctly?
-        - The mitigations shall have a direct influence ont the violation by prevention, detection or mitigation to reduce the risk to an acceptable level.
-        - The mitigations are sufficient.
-        - <yes|no>
-        -
-      * - REQ_01_02
-        - Are the templates for DFA and/or FMEA used?
-        - See :ref:`dfa_templates` / :ref:`FMEA_templates` and also :ref:`process_requirements_safety_analysis`
-        - Templates are used to generate the DFA or / and FMEA.
-        - <yes|no>
-        -
-      * - REQ_01_03
-        - Were the failure initiators / fault models applied?
-        - See :need:`gd_guidl__dfa_failure_initiators` / :need:`gd_guidl__fault_models`
-        - The applicable items of the failure initiators / fault models are used to ensure a structured analysis. For all not applicable items an argument shall be given in the content of the document.
-        - <yes|no>
-        -
-      * - REQ_01_04
-        - Are the failure effects clearly and completely described?
-        - Use the generic failure effect descriptions and enlarge the description if it's applicable to the considered element.
-        - The effects of the failure is described completely. The effect can be recognized easily.
-        - <yes|no>
-        -
-      * - REQ_01_06
-        - Is the attribute "mitigated by" linked correct?
-        - Check if the correct failure effect is linked via "mitigated by".
-        - The "mitigated by" link is correct.
-        - <yes|no>
-        -
-      * - REQ_01_07
-        - Is the sufficiency of the "mitigated by" (prevention, detection or mitigation) described or can it be recognized easily?
-        - The sufficiency of the "mitigated by" is described in the content of the document. It can be recognized easily.
-        - The "mitigated by" shows clearly that a fault / failure can be mitigated by the linked requirement by prevention, detection or mitigation. It shall be described in the contend.
-        - <yes|no>
-        -
-      * - REQ_01_08
-        - Is the overall result of the Safety Analysis described in the report?
-        - It shall be shown in the report if the Safety Analysis are finished and if all artifacts are "valid" and "sufficient".
-        - The results of the Safety Analysis are described in the report. The report is available :need:`wp__verification_platform_ver_report`.
-        - <yes|no>
-        -
+    - :need:`doc__platform_name_safety_analysis_fdr` (platform)
+    - :need:`doc__module_name_safety_analysis_fdr` (module)

process/process_areas/safety_management/guidance/checklist_safety_plan.rst

@@ -18,6 +18,6 @@ Safety Plan Formal Review Checklist
 .. gd_chklst:: Safety Plan Formal Review Checklist
    :id: gd_chklst__safety_plan
    :status: valid
-   :complies: std_req__iso26262__management_5425, std_req__iso26262__management_6491, std_req__iso26262__management_6492, std_req__iso26262__management_6493, std_req__iso26262__management_64101, std_req__iso26262__management_64102, std_req__iso26262__management_64103, std_req__iso26262__management_64104, std_req__iso26262__management_64105, std_req__iso26262__management_5427, std_req__iso26262__management_6421, std_req__iso26262__management_6431, std_req__iso26262__management_6461, std_req__iso26262__management_6462, std_req__iso26262__management_6464, std_req__iso26262__management_64610, std_req__iso26262__management_64113
+   :complies: std_req__iso26262__management_64101, std_req__iso26262__management_64102, std_req__iso26262__management_64103, std_req__iso26262__management_64104, std_req__iso26262__management_64105
 
    For the content see here: :need:`doc__module_name_safety_plan_fdr`