Skip to content

Update Safety Analysis templates and process descriptions #663

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

Merged
aschemmel-tech merged 1 commit into from
Apr 23, 2026
Merged

Update Safety Analysis templates and process descriptions #663

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
2 changes: 1 addition & 1 deletion 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 @@ -32,7 +32,7 @@ DFA (Dependent Failure Analysis)
- 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
- Adjust ``safety``, ``security`` and ``tags`` according to your needs

The DFA for the feature [Your Feature Name] is performed. To show evidence that all failure initiators are considered, the applicability has to be filled out in the
following tables. For all applicable failure initiators, the DFA has to be performed.
Expand Down
2 changes: 1 addition & 1 deletion 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 @@ -32,7 +32,7 @@ FMEA (Failure Modes and Effects Analysis)
- 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 ``_fmea``
- Adjust ``status`` to be ``valid``
- Adjust ``safety`` and ``tags`` according to your needs
- Adjust ``safety``, ``security`` and ``tags`` according to your needs

The FMEA for the feature [Your Feature Name] is performed. To show evidence that all failure initiators are considered, the applicability has to be filled out in the
following tables. For all applicable failure initiators, the FMEA has to be performed.
Expand Down
2 changes: 1 addition & 1 deletion ...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 @@ -32,7 +32,7 @@ DFA (Dependent Failure Analysis)
- Modify ``Your Component Name`` to be your Component Name
- Modify ``id`` to be your Component 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
- Adjust ``safety``, ``security`` and ``tags`` according to your needs

The DFA for the component [Your Component Name] is performed. To show evidence that all failure initiators are considered, the applicability has to be filled out in the
following tables. For all applicable failure initiators, the DFA has to be performed.
Expand Down
2 changes: 1 addition & 1 deletion ...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 @@ -32,7 +32,7 @@ FMEA (Failure Modes and Effects Analysis)
- Modify ``Your Component Name`` to be your Component Name
- Modify ``id`` to be your Component Name in upper snake case preceded by ``doc__`` and succeeded by ``_fmea``
- Adjust ``status`` to be ``valid``
- Adjust ``safety`` and ``tags`` according to your needs
- Adjust ``safety``, ``security`` and ``tags`` according to your needs

The FMEA for the component [Your Component Name] is performed. To show evidence that all failure initiators are considered, the applicability has to be filled out in the
following tables. For all applicable failure initiators, the FMEA has to be performed.
Expand Down
4 changes: 2 additions & 2 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 @@ -81,7 +81,7 @@ Process Safety Analysis Attributes
:satisfies: wf__analyse_platform_featarch, wf__analyse_featarch, wf__analyse_comparch
:complies: std_req__iso26262__analysis_844, std_req__iso26262__analysis_746, std_req__iso26262__analysis_747

If a new mitigation (e.g. prevention, detection or mitigation) is needed, link to the issue and keep status invalid until mitigation is sufficient.
If a new mitigation (e.g. prevention, detection or mitigation) is needed, link to the issue and keep status sufficient == no until mitigation is sufficient.

.. gd_req:: Safety Analysis attribute: sufficient
:id: gd_req__saf_attr_sufficient
Expand Down Expand Up @@ -110,7 +110,7 @@ Process Safety Analysis Attributes
:satisfies: wf__analyse_platform_featarch, wf__analyse_featarch, wf__analyse_comparch
:complies: std_req__iso26262__analysis_848, std_req__iso26262__analysis_749, std_req__isopas8926__44431, std_req__isopas8926__44432

Each Safety Analysis shall have the status invalid until the analysis is finished. The status shall be set to valid if the analysis is finished and all issues are closed.
Each Safety Analysis shall have a status which can be either "valid" or "invalid".

.. gd_req:: Safety Analysis attribute: failure effect
:id: gd_req__saf_attr_feffect
Expand Down
Loading