Skip to content

Commit 5050280

Browse files
aschemmel-techPandaeDo
aschemmel-tech
authored and
PandaeDo
committed
Improvement: add safety analysis checklist to folder templates
1 parent 62c66fb commit 5050280

File tree

6 files changed

+191
-56
lines changed

6 files changed

+191
-56
lines changed

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

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -21,3 +21,4 @@ Safety Management
2121
module_safety_plan
2222
module_safety_plan_fdr
2323
module_safety_package_fdr
24+
module_safety_analysis_fdr

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

Lines changed: 92 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,92 @@
1+
..
2+
# *******************************************************************************
3+
# Copyright (c) 2025 Contributors to the Eclipse Foundation
4+
#
5+
# See the NOTICE file(s) distributed with this work for additional
6+
# information regarding copyright ownership.
7+
#
8+
# This program and the accompanying materials are made available under the
9+
# terms of the Apache License Version 2.0 which is available at
10+
# https://www.apache.org/licenses/LICENSE-2.0
11+
#
12+
# SPDX-License-Identifier: Apache-2.0
13+
# *******************************************************************************
14+
15+
16+
Safety Analysis Checklist
17+
=========================
18+
19+
.. document:: [Your Module Name] Safety Analysis Checklist
20+
:id: doc__module_name_safety_analysis_fdr
21+
:status: draft
22+
:safety: ASIL_B
23+
:security: YES
24+
:realizes: wp__fdr_reports
25+
:tags: template
26+
27+
.. attention::
28+
The above directive must be updated according to your Module.
29+
30+
- Modify ``Your Module Name`` to be your Module Name
31+
- Modify ``id`` to be your Module Name in lower snake case preceded by ``doc__`` and followed by ``_safety _analysis_fdr``
32+
- Adjust ``status`` to be ``valid``
33+
- Adjust ``safety``, ``security`` and ``tags`` according to your needs
34+
35+
36+
**Purpose**
37+
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.
38+
39+
**Checklist**
40+
41+
.. list-table:: Safety Analysis Checklist
42+
:header-rows: 1
43+
:widths: 10,30,30,15,8,8
44+
45+
* - Review ID
46+
- Acceptance Criteria
47+
- Guidance
48+
- Passed
49+
- Remarks
50+
- Issue link
51+
* - REQ_01_01
52+
- Is / are the attribute sufficient set correctly?
53+
- The mitigations shall have a direct influence ont the violation by prevention, detection or mitigation to reduce the risk to an acceptable level.
54+
- The mitigations are sufficient.
55+
- <yes|no>
56+
-
57+
* - REQ_01_02
58+
- Are the templates for DFA and/or FMEA used?
59+
- See :ref:`dfa_templates` / :ref:`FMEA_templates` and also :ref:`process_requirements_safety_analysis`
60+
- Templates are used to generate the DFA or / and FMEA.
61+
- <yes|no>
62+
-
63+
* - REQ_01_03
64+
- Were the failure initiators / fault models applied?
65+
- See :need:`gd_guidl__dfa_failure_initiators` / :need:`gd_guidl__fault_models`
66+
- 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.
67+
- <yes|no>
68+
-
69+
* - REQ_01_04
70+
- Are the failure effects clearly and completely described?
71+
- Use the generic failure effect descriptions and enlarge the description if it's applicable to the considered element.
72+
- The effects of the failure is described completely. The effect can be recognized easily.
73+
- <yes|no>
74+
-
75+
* - REQ_01_06
76+
- Is the attribute "mitigated by" linked correct?
77+
- Check if the correct failure effect is linked via "mitigated by".
78+
- The "mitigated by" link is correct.
79+
- <yes|no>
80+
-
81+
* - REQ_01_07
82+
- Is the sufficiency of the "mitigated by" (prevention, detection or mitigation) described or can it be recognized easily?
83+
- The sufficiency of the "mitigated by" is described in the content of the document. It can be recognized easily.
84+
- 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.
85+
- <yes|no>
86+
-
87+
* - REQ_01_08
88+
- Is the overall result of the Safety Analysis described in the report?
89+
- It shall be shown in the report if the Safety Analysis are finished and if all artifacts are "valid" and "sufficient".
90+
- The results of the Safety Analysis are described in the report. The report is available :need:`wp__verification_platform_ver_report`.
91+
- <yes|no>
92+
-

‎process/folder_templates/platform/index.rst‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -23,3 +23,4 @@ Platform
2323
safety_analysis/platform_dfa.rst
2424
requirements/stakeholder/chklst_req_inspection.rst
2525
safety_planning/index.rst
26+
safety_planning/platform_safety_analysis_fdr.rst

‎process/folder_templates/platform/safety_planning/platform_safety_analysis_fdr.rst‎

Lines changed: 92 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,92 @@
1+
..
2+
# *******************************************************************************
3+
# Copyright (c) 2025 Contributors to the Eclipse Foundation
4+
#
5+
# See the NOTICE file(s) distributed with this work for additional
6+
# information regarding copyright ownership.
7+
#
8+
# This program and the accompanying materials are made available under the
9+
# terms of the Apache License Version 2.0 which is available at
10+
# https://www.apache.org/licenses/LICENSE-2.0
11+
#
12+
# SPDX-License-Identifier: Apache-2.0
13+
# *******************************************************************************
14+
15+
16+
Safety Analysis Checklist
17+
=========================
18+
19+
.. document:: [Your Platform Name] Safety Analysis Checklist
20+
:id: doc__platform_name_safety_analysis_fdr
21+
:status: draft
22+
:safety: ASIL_B
23+
:security: YES
24+
:realizes: wp__fdr_reports
25+
:tags: template
26+
27+
.. attention::
28+
The above directive must be updated according to your Platform.
29+
30+
- Modify ``Your Platform Name`` to be your Platform Name
31+
- Modify ``id`` to be your Platform Name in lower snake case preceded by ``doc__`` and followed by ``_safety _analysis_fdr``
32+
- Adjust ``status`` to be ``valid``
33+
- Adjust ``safety``, ``security`` and ``tags`` according to your needs
34+
35+
36+
**Purpose**
37+
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.
38+
39+
**Checklist**
40+
41+
.. list-table:: Safety Analysis Checklist
42+
:header-rows: 1
43+
:widths: 10,30,30,15,8,8
44+
45+
* - Review ID
46+
- Acceptance Criteria
47+
- Guidance
48+
- Passed
49+
- Remarks
50+
- Issue link
51+
* - REQ_01_01
52+
- Is / are the attribute sufficient set correctly?
53+
- The mitigations shall have a direct influence ont the violation by prevention, detection or mitigation to reduce the risk to an acceptable level.
54+
- The mitigations are sufficient.
55+
- <yes|no>
56+
-
57+
* - REQ_01_02
58+
- Are the templates for DFA and/or FMEA used?
59+
- See :ref:`dfa_templates` / :ref:`FMEA_templates` and also :ref:`process_requirements_safety_analysis`
60+
- Templates are used to generate the DFA or / and FMEA.
61+
- <yes|no>
62+
-
63+
* - REQ_01_03
64+
- Were the failure initiators / fault models applied?
65+
- See :need:`gd_guidl__dfa_failure_initiators` / :need:`gd_guidl__fault_models`
66+
- 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.
67+
- <yes|no>
68+
-
69+
* - REQ_01_04
70+
- Are the failure effects clearly and completely described?
71+
- Use the generic failure effect descriptions and enlarge the description if it's applicable to the considered element.
72+
- The effects of the failure is described completely. The effect can be recognized easily.
73+
- <yes|no>
74+
-
75+
* - REQ_01_06
76+
- Is the attribute "mitigated by" linked correct?
77+
- Check if the correct failure effect is linked via "mitigated by".
78+
- The "mitigated by" link is correct.
79+
- <yes|no>
80+
-
81+
* - REQ_01_07
82+
- Is the sufficiency of the "mitigated by" (prevention, detection or mitigation) described or can it be recognized easily?
83+
- The sufficiency of the "mitigated by" is described in the content of the document. It can be recognized easily.
84+
- 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.
85+
- <yes|no>
86+
-
87+
* - REQ_01_08
88+
- Is the overall result of the Safety Analysis described in the report?
89+
- It shall be shown in the report if the Safety Analysis are finished and if all artifacts are "valid" and "sufficient".
90+
- The results of the Safety Analysis are described in the report. The report is available :need:`wp__verification_platform_ver_report`.
91+
- <yes|no>
92+
-

‎process/process_areas/safety_analysis/guidance/safety_analysis_checklist.rst‎

Lines changed: 4 additions & 55 deletions
Original file line numberDiff line numberDiff line change
@@ -20,61 +20,10 @@ Safety Analysis Checklist
2020
:id: gd_chklst__safety_analysis
2121
:status: valid
2222
:tags: safety_analysis
23+
: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
2324

24-
**Purpose**
25-
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.
2625

27-
**Checklist**
26+
For the content see here:
2827

29-
.. list-table:: Safety Analysis Checklist
30-
:header-rows: 1
31-
:widths: 10,30,30,15,8,8
32-
33-
* - Review ID
34-
- Acceptance Criteria
35-
- Guidance
36-
- Passed
37-
- Remarks
38-
- Issue link
39-
* - REQ_01_01
40-
- Is / are the attribute sufficient set correctly?
41-
- The mitigations shall have a direct influence ont the violation by prevention, detection or mitigation to reduce the risk to an acceptable level.
42-
- The mitigations are sufficient.
43-
- <yes|no>
44-
-
45-
* - REQ_01_02
46-
- Are the templates for DFA and/or FMEA used?
47-
- See :ref:`dfa_templates` / :ref:`FMEA_templates` and also :ref:`process_requirements_safety_analysis`
48-
- Templates are used to generate the DFA or / and FMEA.
49-
- <yes|no>
50-
-
51-
* - REQ_01_03
52-
- Were the failure initiators / fault models applied?
53-
- See :need:`gd_guidl__dfa_failure_initiators` / :need:`gd_guidl__fault_models`
54-
- 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.
55-
- <yes|no>
56-
-
57-
* - REQ_01_04
58-
- Are the failure effects clearly and completely described?
59-
- Use the generic failure effect descriptions and enlarge the description if it's applicable to the considered element.
60-
- The effects of the failure is described completely. The effect can be recognized easily.
61-
- <yes|no>
62-
-
63-
* - REQ_01_06
64-
- Is the attribute "mitigated by" linked correct?
65-
- Check if the correct failure effect is linked via "mitigated by".
66-
- The "mitigated by" link is correct.
67-
- <yes|no>
68-
-
69-
* - REQ_01_07
70-
- Is the sufficiency of the "mitigated by" (prevention, detection or mitigation) described or can it be recognized easily?
71-
- The sufficiency of the "mitigated by" is described in the content of the document. It can be recognized easily.
72-
- 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.
73-
- <yes|no>
74-
-
75-
* - REQ_01_08
76-
- Is the overall result of the Safety Analysis described in the report?
77-
- It shall be shown in the report if the Safety Analysis are finished and if all artifacts are "valid" and "sufficient".
78-
- The results of the Safety Analysis are described in the report. The report is available :need:`wp__verification_platform_ver_report`.
79-
- <yes|no>
80-
-
28+
- :need:`doc__platform_name_safety_analysis_fdr` (platform)
29+
- :need:`doc__module_name_safety_analysis_fdr` (module)

‎process/process_areas/safety_management/guidance/checklist_safety_plan.rst‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,6 +18,6 @@ Safety Plan Formal Review Checklist
1818
.. gd_chklst:: Safety Plan Formal Review Checklist
1919
:id: gd_chklst__safety_plan
2020
:status: valid
21-
: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
21+
: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
2222

2323
For the content see here: :need:`doc__module_name_safety_plan_fdr`

0 commit comments

Comments
 (0)