Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -193,6 +193,7 @@ For all identified applicable failure initiators, the DFA is performed in the fo
: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"
:safety_relevant: <yes|no>
:mitigated_by: <ID from Feature Requirement | ID from AoU Feature Requirement>
:mitigation_issue: <ID from Issue Tracker>
:sufficient: <yes|no>
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -122,6 +122,8 @@ For all identified applicable failure initiators, the FMEA is performed in the f
:id: feat_saf_fmea__<Feature>__<Element descriptor>
:fault_id: <ID from fault model :need:`gd_guidl__fault_models`>
:failure_effect: "description of failure effect of the fault model on the element"
:failure_root_cause: "description of the root cause of the failure"
:safety_relevant: <yes|no>
:mitigated_by: <ID from Feature Requirement | ID from AoU Feature Requirement>
:mitigation_issue: <ID from Issue Tracker>
:sufficient: <yes|no>
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -193,6 +193,7 @@ For all identified applicable failure initiators, the DFA is performed in the fo
:id: comp_saf_dfa__<Component>__<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"
:safety_relevant: <yes|no>
:mitigated_by: <ID from Component Requirement | ID from AoU Component Requirement>
:mitigation_issue: <ID from Issue Tracker>
:sufficient: <yes|no>
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -121,6 +121,8 @@ For all identified applicable failure initiators, the FMEA is performed in the f
:id: comp_saf_fmea__<Component>__<Element descriptor>
:fault_id: <ID from fault model :need:`gd_guidl__fault_models`>
:failure_effect: "description of failure effect of the fault model on the element"
:failure_root_cause: "description of the root cause of the failure"
:safety_relevant: <yes|no>
:mitigated_by: <ID from Component Requirement | ID from AoU Component Requirement>
:mitigation_issue: <ID from Issue Tracker>
:sufficient: <yes|no>
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -263,6 +263,7 @@ For all identified applicable failure initiators, the DFA is performed in the fo
: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"
:safety_relevant: <yes|no>
:mitigated_by: <ID from Stakeholder Requirement | ID from AoU Feature Requirement>
:mitigation_issue: <ID from Issue Tracker>
:sufficient: <yes|no>
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -50,6 +50,8 @@ The attributes of the template are described in :ref:`process_requirements_safet
#. Replace the placeholders in the "id" attribute with the name of the feature or component and a short description of the element so that it can be easily identified.
#. Document the fault ID from the fault model :need:`gd_guidl__fault_models` that applies to the element in the "fault_id" attribute.
#. Describe the failure effect of the fault model on the element in the "failure_effect" attribute. Use the failure mode description and enlarge the if it's applicable to the considered element.
#. Document the root cause of the failure in the "failure_root_cause" attribute.
#. Indicate whether the analysed failure is safety relevant using the "safety_relevant" attribute (<yes> or <no>).
#. Document the safety mitigation. This can be a detection, prevention or mitigation of the fault. If only testability is defined as mitigation measure, complexity requirements shall be allocated to the feature/component.
#. If there is no mitigation or existing mitigation is not sufficient a mitigation issue has to be created in the Issue Tracking system and linked in the "mitigation_issue" attribute.
#. The analysis is finished, if for each identified fault a sufficient mitigation exists.
Expand Down Expand Up @@ -79,6 +81,7 @@ The attributes of the template are described in :ref:`process_requirements_safet
#. Replace the placeholders in the "id" attribute with the name of the feature or component and a short description of the element so that it can be easily identified.
#. Document the failure ID from the failure initiator :need:`gd_guidl__dfa_failure_initiators` that applies to the element in the "failure_id" attribute.
#. Describe the failure effect of the failure initiator on the element in the "failure_effect" attribute. Use the violation cause description and enlarge the if it's applicable to the considered element.
#. Indicate whether the analysed failure is safety relevant using the "safety_relevant" attribute (<yes> or <no>).
#. Document the safety mitigation. This can be a detection, prevention or mitigation of the fault. If only testability is defined as mitigation measure, complexity requirements shall be allocated to the feature/component.
#. If there is no mitigation or the mitigation is not sufficient a mitigation issue has to be created in the Issue Tracking system and linked in the "mitigation_issue" attribute.
#. The analysis is finished, if for each identified fault a sufficient mitigation exists.
Expand Down Expand Up @@ -107,6 +110,8 @@ find possible failures. Therefore we need a mitigation.
:id: feat_saf_fmea__mab__comp1_call_nreceived
:fault_id: MF_01_01
:failure_effect: Message is not received. This leads to a unavailability of a safety related functionality of the feature.
:failure_root_cause: The message is lost due to a communication error.
:safety_relevant: yes
:mitigated_by: aou_req__mab__call_not_received
:mitigation_issue:
:sufficient: yes
Expand All @@ -132,6 +137,7 @@ In the static view of the example could be seen that component 1 uses component
:id: feat_saf_dfa__mab__data_corruption
:failure_id: CO_01_02
:failure_effect: Data or message corruption will lead to a corruption of the data or message that could violate a safety functionality.
:safety_relevant: yes
:mitigated_by: feat_req__mab_integritiy_check
:mitigation_issue:
:sufficient: yes
Expand Down Expand Up @@ -171,6 +177,7 @@ Additionally in the static view we see Component 4 is a library used by Componen
:id: comp_saf_dfa__component4__allocated_memory
:failure_id: SR_01_10
:failure_effect: Component 4 is using allocated memory of Component 3
:safety_relevant: yes
:mitigated_by: comp_req__memory_management
:mitigation_issue:
:sufficient: yes
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -121,6 +121,24 @@ Process Safety Analysis Attributes

Every Safety Analysis shall have a short description of the failure effect (e.g. failure lead to an unintended actuation of the analysed element)

.. gd_req:: Safety Analysis attribute: safety relevant
:id: gd_req__saf_attr_safety_relevant
:status: valid
:tags: done_automation, attribute, optional
:satisfies: wf__analyse_platform_featarch, wf__analyse_featarch, wf__analyse_comparch
:complies: std_req__iso26262__analysis_742

Each Safety Analysis may indicate whether the analysed failure is safety relevant. The value shall be either <yes> or <no>.

.. gd_req:: FMEA attribute: failure root cause
:id: gd_req__saf_attr_failure_root_cause
:status: valid
:tags: done_automation, attribute, optional
:satisfies: wf__analyse_featarch, wf__analyse_comparch
:complies: std_req__iso26262__analysis_742

Each FMEA may provide a short description of the root cause of the failure.

.. _process_requirements_safety_analysis_linkage:

Safety Analysis Linkage
Expand Down
Loading