Skip to content

Update Safety Analysis Template #669

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ANegm-ETAS wants to merge 4 commits into
base: main
Choose a base branch
from
Open

Update Safety Analysis Template #669

Show file tree
Hide file tree
Changes from 2 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
4eef32d
Update Safety Analysis Template
AdhamN861 Apr 1, 2026
015106a
Update Safety Analysis Process requirement
AdhamN861 Apr 30, 2026
38b7218
Update Safety Analysis Guideline
AdhamN861 Apr 30, 2026
67d5e9f
update language in sagfety analysis guidance
AdhamN861 May 12, 2026
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
1 change: 1 addition & 0 deletions process/folder_templates/features/feature_name/safety_analysis/dfa.rst
View file
Open in desktop
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>
Copy link
Copy Markdown
Contributor

@aschemmel-tech aschemmel-tech Apr 30, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What would be the consequence of setting :safety_relevant: no ? No need to set :mitigated_by:, :mitigation_issue: and :sufficient: ? Would also need a check updated.

Copy link
Copy Markdown
Contributor Author

@ANegm-ETAS ANegm-ETAS May 12, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

in case of :safety_relevant: no, i would say the threshold to be :sufficient: yes is lower, for example simply planning an issue would be sufficient. If you agree on this approach, i can update the Safety Analysis Attribute Requirements to make it clearer.

Would also need a check updated.

Do you mean to add a point in the Safety Analysis Checklist ?

:mitigated_by: <ID from Feature Requirement | ID from AoU Feature Requirement>
:mitigation_issue: <ID from Issue Tracker>
:sufficient: <yes|no>
Expand Down
2 changes: 2 additions & 0 deletions process/folder_templates/features/feature_name/safety_analysis/fmea.rst
View file
Open in desktop
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
1 change: 1 addition & 0 deletions ...older_templates/modules/module_name/component_name/docs/safety_analysis/dfa.rst
View file
Open in desktop
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
2 changes: 2 additions & 0 deletions ...lder_templates/modules/module_name/component_name/docs/safety_analysis/fmea.rst
View file
Open in desktop
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
1 change: 1 addition & 0 deletions process/folder_templates/platform/docs/safety_mgt/platform_dfa.rst
View file
Open in desktop
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
18 changes: 18 additions & 0 deletions process/process_areas/safety_analysis/guidance/safety_analysis_process_reqs.rst
View file
Open in desktop
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