update to platform dfa

Author: PandaeDo

process/folder_templates/features/feature_name/index.rst

@@ -190,3 +190,4 @@ Footnotes
    safety_planning/index.rst
    safety_analysis/fmea.rst
    safety_analysis/dfa.rst
+   safety_analysis/platform_dfa.rst

process/folder_templates/features/feature_name/safety_analysis/platform_dfa.rst

@@ -0,0 +1,59 @@
+..
+   # *******************************************************************************
+   # 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 DFA (Dependent Failure Analysis)
+=========================================
+
+.. document:: Platform DFA
+   :id: doc__platform_dfa
+   :status: draft
+   :safety: ASIL_B
+   :realizes: wp__platform_dfa
+   :tags: template
+
+.. note:: The platform DFA is only performed once at platform level to analyse the dependencies between the features of the platform.
+          The results shall be used as an input for the safety analysis so that general safety mechanisms are only defined once and not in every single safety 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
+----------------------------
+
+.. code-block:: rst
+
+    .. plat_saf_dfa:: <Title>
+       :violates: <Feature architecture>
+       :id: plat_saf_DFA__<Feature>__<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>
+       :mitigation_issue: <ID from Issue Tracker>
+       :sufficient: <yes|no>
+       :status: <valid|invalid>
+.. note::   argument is inside the 'content'. Therefore content is mandatory
+
+.. attention::
+    The above directive must be updated according to the platform DFA.
+
+    - The above "code-block" directive must be updated
+    - Fill in all the needed information in the <brackets>

process/process_areas/safety_analysis/guidance/dfa_failure_initiators.rst

@@ -40,7 +40,7 @@ DFA failure initiators
 
 .. note:: Shared libraries are only than to be considered as a shared resource if the feature and the related safety mechanisms are using this specific library. If the library is not used by the feature or the related safety mechanisms, it is not a shared resource.
 
-.. list-table:: DFA shared resources (used for Platform Feature DFA)
+.. list-table:: DFA shared resources (used for Platform DFA)
   :header-rows: 1
   :widths: 10,50,10
 
@@ -180,7 +180,7 @@ DFA failure initiators
 
 :note: Section shall be applied only once to analyse all dependencies of the features. Results shall be checked during of the analysis of new features if this is applicable to the feature.
 
-.. list-table:: DFA development failure initiators (Feature Platform DFA)
+.. list-table:: DFA development failure initiators (Platform DFA)
   :header-rows: 1
   :widths: 10,50,10
 

process/process_areas/safety_analysis/guidance/dfa_templates.rst

@@ -17,23 +17,12 @@
 DFA Templates
 =============
 
-.. gd_temp:: Feature Platform DFA Templates
-   :id: gd_temp__feat_plat_saf_dfa
+.. gd_temp:: Platform DFA Templates
+   :id: gd_temp__plat_saf_dfa
    :status: valid
    :complies: std_wp__iso26262__analysis_751, std_wp__iso26262__software_753, std_wp__isopas8926__4524, std_req__iso26262__software_7411, std_req__iso26262__analysis_741, std_req__iso26262__analysis_742, std_req__iso26262__analysis_743, std_req__iso26262__analysis_745, std_req__iso26262__analysis_746, std_req__iso26262__analysis_747, std_req__iso26262__analysis_748, std_req__iso26262__analysis_749, std_req__isopas8926__44432
 
-.. code-block:: rst
-
-    .. feat_plat_saf_dfa:: <Title>
-       :violates: <Feature architecture>
-       :id: feat_saf_dfa__<Feature>__<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>
-       :mitigation_issue: <ID from Issue Tracker>
-       :sufficient: <yes|no>
-       :status: <valid|invalid>
-.. note::   argument is inside the 'content'. Therefore content is mandatory
+   For the content see here: :need:`doc__platform_dfa`
 
 
 .. gd_temp:: Feature DFA Templates

process/process_areas/safety_analysis/guidance/safety_analysis_guideline.rst

@@ -22,6 +22,7 @@ Safety Analysis Guidelines
    :complies: std_req__iso26262__analysis_841, std_req__iso26262__analysis_842, std_req__iso26262__analysis_843, std_req__iso26262__analysis_844, std_req__iso26262__analysis_847, std_req__iso26262__analysis_848, std_req__iso26262__analysis_849, std_req__iso26262__analysis_8410, std_req__isopas8926__44431, std_req__isopas8926__44432
 
 This document describes the general guidances for Safety Analysis (DFA and FMEA) based on the concept which is defined :need:`Safety Analysis Concept<doc_concept__safety__analysis>`.
+Use the platform DFA as an input so that general safety mechanisms are only defined once and not in every single safety analysis.
 
 Workflow for Safety Analysis
 ============================
@@ -100,7 +101,7 @@ In the dynamic view of the example the "flow component 1" to the user realizes a
 find possible failures. Therefore we need a mitigation.
 
 .. code-block:: rst
-   
+
    .. feat_saf_fmea:: Component 1 Call message not received
       :violates: feat_arc_dyn__mab__dynamic
       :id: feat_saf_fmea__mab__comp1_call_nreceived
@@ -114,23 +115,9 @@ find possible failures. Therefore we need a mitigation.
     If the message is not received by the feature it will be unavailable for the user. This has to be detected by the User because
     the feature can't detect if it's not called. This requirement is addressed by the AoU requirement aou_req__Mab__func_call_not_received.
 
-.. code-block:: rst
-
-   .. feat_saf_fmea:: Component 1 unintended triggered
-      :violates: feat_arc_dyn__mab__dynamic
-      :id: feat_saf_fmea__mab__component_1
-      :fault_id: MF_01_07
-      :failure_effect: Message is unintended sent. Component 1 will be unintended triggered.
-      :mitigated_by:
-      :mitigation_issue:
-      :sufficient: yes
-      :status: valid
-
-    An unintended return can be neglected as the component is ASIL B developed, non complex and sufficiently tested.
-
-
 For all fault models that are not applicable, the reason has to be documented in the content of the document, so it can be recognized. An example could be that
 
+* Fault model FM_01_07 "Message is unintended sent. Component 1 will be unintended triggered." is not applicable, because the component is ASIL B developed, non complex and sufficiently tested.
 * Fault model FX_01_04 "loss of execution" is not applicable, because feature is completely deterministic. Other failures like HW failures are not considered in this analysis because it's developed as a SEooC.
 
 

process/process_areas/safety_analysis/safety_analysis_workflow.rst

@@ -28,12 +28,12 @@ Safety analysis is used as a umbrella term for the methods FMEA (Failure Modes a
    :approved_by: rl__safety_manager
    :supported_by: rl__contributor, rl__committer, rl__security_manager
    :input: wp__requirements__feat, wp__feature_arch, wp__issue_track_system
-   :output: wp__feature_platform_dfa
+   :output: wp__platform_dfa
    :contains: gd_guidl__dfa_failure_initiators, gd_temp__feat_saf_dfa
    :has: doc_concept__safety__analysis, doc_getstrt__safety_analysis
 
-   | With a platform features DFA the potential common usage of modules shall be analysed. It shall be used as an input for all other DFA's.
-   | There will be only one platform feature DFA.
+   | With a platform DFA the potential common usage of modules shall be analysed. It shall be used as an input for all other DFA's.
+   | There will be only one platform DFA.
 
 .. workflow:: Analyse Feature Architecture
    :id: wf__analyse_featarch
@@ -84,7 +84,7 @@ Safety analysis is used as a umbrella term for the methods FMEA (Failure Modes a
    :responsible: rl__safety_engineer
    :approved_by: rl__safety_manager
    :supported_by: rl__contributor, rl__committer, rl__security_manager
-   :input: wp__feature_platform_dfa, wp__feature_fmea, wp__feature_dfa, wp__sw_component_fmea, wp__sw_component_dfa
+   :input: wp__platform_dfa, wp__feature_fmea, wp__feature_dfa, wp__sw_component_fmea, wp__sw_component_dfa
    :output: wp__verification__platform_ver_report, wp__verification__module_ver_report
    :contains: gd_guidl__dfa_failure_initiators, gd_temp__feat_saf_dfa, gd_temp__comp_saf_dfa, gd_guidl__fault_models, gd_temp__feat_saf_fmea, gd_temp__comp_saf_fmea, gd_chklst__safety_analysis
    :has: doc_concept__safety__analysis, doc_getstrt__safety_analysis

process/process_areas/safety_analysis/safety_analysis_workproducts.rst

@@ -15,8 +15,8 @@
 Workproducts Safety Analysis
 ############################
 
-.. workproduct:: Platform Feature DFA
-   :id: wp__feature_platform_dfa
+.. workproduct:: Platform DFA
+   :id: wp__platform_dfa
    :status: valid
    :complies: std_wp__iso26262__software_751, std_wp__iso26262__software_753, std_wp__isopas8926__4524
 

process/process_areas/verification/workflows.rst

@@ -181,7 +181,7 @@ Workflow Verification
    :supported_by: rl__safety_manager, rl__infrastructure_tooling_community
    :input: wp__verification__plan, wp__requirements__stkh, wp__requirements__feat, wp__requirements__feat_aou,
            wp__feature_arch, wp__platform_sw_release_note, wp__platform_mgmt,
-           wp__feature_fmea, wp__feature_dfa, wp__feature_platform_dfa,
+           wp__feature_fmea, wp__feature_dfa, wp__platform_dfa,
            wp__sw_arch_verification, wp__requirements__inspect,
            wp__verification__feat_int_test, wp__verification__platform_test
    :output: wp__verification__platform_ver_report