Skip to content

Commit ce103d6

Browse files
PandaeDoPandaeDo
committed
enlarge fdrs and fix failures in process
1 parent dd683ac commit ce103d6

8 files changed

Lines changed: 405 additions & 35 deletions

File tree

‎process/folder_templates/features/feature_name/index.rst‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -184,5 +184,6 @@ Footnotes
184184
requirements/chklst_req_inspection.rst
185185
safety_analysis/fmea.rst
186186
safety_analysis/dfa.rst
187+
safety_analysis/feature_safety_analysis_fdr.rst
187188
safety_planning/index.rst
188189
security_planning/index.rst

‎process/folder_templates/features/feature_name/safety_analysis/feature_safety_analysis_fdr.rst‎

Lines changed: 188 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,188 @@
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 Feature Name] Safety Analysis Checklist
20+
:id: doc__feature_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 Feature.
29+
30+
- Modify ``Your Feature Name`` to be your Feature Name
31+
- Modify ``id`` to be your Feature 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+
38+
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.
39+
40+
**Conduct**
41+
42+
As described in :need:`wf__p_formal_rv`, the formal document review is performed by an "external" safety manager:
43+
44+
- reviewer: <committer with safety manager skills explicitly named here>
45+
46+
**Checklist**
47+
48+
Please note that the "passed" column must contain "yes" or "no" for each checklist item. Additionally, the remarks column must explain why item passed or did not passed. In case of "no" an issue link to the issue tracking system has to be added in the last column. See also :ref:`review_concept` for further information about reviews in general and inspection in particular.
49+
50+
.. list-table:: General Checklist
51+
:header-rows: 1
52+
:widths: 10,10,30,30,20
53+
54+
* - ID
55+
- Safety analysis activity
56+
- Compliant to ISO 26262?
57+
- Reference
58+
- Comment
59+
60+
* - 1
61+
- Are the safety analysis performed according to the defined process and templates? See :ref:`process_requirements_safety_analysis` and also :ref:`FMEA_templates` and :ref:`dfa_templates`
62+
- [YES | NO ]
63+
- :need:`[[title]] <std_req__iso26262__analysis_841>`
64+
- <Rationale for result>
65+
66+
* - 2
67+
- Is the result of the safety analysis indicate if the safety requirements are complied?
68+
- [YES | NO ]
69+
- :need:`[[title]] <std_req__iso26262__analysis_842>`
70+
- <Rationale for result>
71+
72+
* - 3
73+
- Are for all not complied safety requirements mitigations defined to resolute the non-compliance? The mitigations shall have a direct influence on the violation by prevention, detection or mitigation to reduce the risk to an acceptable level.
74+
- [YES | NO ]
75+
- :need:`[[title]] <std_req__iso26262__analysis_843>`
76+
- <Rationale for result>
77+
78+
* - 4
79+
- Are the mitigations effective and implemented?
80+
- [YES | NO ]
81+
- :need:`[[title]] <std_req__iso26262__analysis_844>`
82+
- <Rationale for result>
83+
84+
* - 5
85+
- Are newly identified hazards adressed to be considered in HARA in the safety manual?
86+
- [YES | NO ]
87+
- :need:`[[title]] <std_req__iso26262__analysis_845>`
88+
- <Rationale for result>
89+
90+
* - 6
91+
- Are additional safety-related test cases determined by potential results of the safety analyses?
92+
- [YES | NO ]
93+
- :need:`[[title]] <std_req__iso26262__analysis_847>`
94+
- <Rationale for result>
95+
96+
97+
.. list-table:: DFA Checklist
98+
:header-rows: 1
99+
:widths: 10,10,30,30,20
100+
101+
* - ID
102+
- Safety analysis activity
103+
- Compliant to ISO 26262?
104+
- Reference
105+
- Comment
106+
107+
* - 1
108+
- Are the potential dependent failures identified by performming a DFA?
109+
- [YES | NO ]
110+
- :need:`[[title]] <std_req__iso26262__analysis_741>`
111+
- <Rationale for result>
112+
113+
* - 2
114+
- Is it plausible that each potential identified dependent failure that has been identified, will lead to a dependent failure which cause a violation of FFI?
115+
- [YES | NO ]
116+
- :need:`[[title]] <std_req__iso26262__analysis_742>`
117+
- <Rationale for result>
118+
119+
* - 3
120+
- Are applicable operational situations and operating modes considered?
121+
- [YES | NO ]
122+
- :need:`[[title]] <std_req__iso26262__analysis_743>`
123+
- <Rationale for result>
124+
125+
* - 4
126+
- Are the failure initiators :need:`[[title]] <gd_guidl__dfa_failure_initiators>` suitable and applied?
127+
- [YES | NO ]
128+
- :need:`[[title]] <std_req__iso26262__analysis_744>`
129+
- <Rationale for result>
130+
131+
* - 5
132+
- Is a rationale provided for each identified potential dependent failure?
133+
- [YES | NO ]
134+
- :need:`[[title]] <std_req__iso26262__analysis_745>`
135+
- <Rationale for result>
136+
137+
* - 6
138+
- Are measures defined to resolute the identified potential dependent failures?
139+
- [YES | NO ]
140+
- :need:`[[title]] <std_req__iso26262__analysis_746>`, :need:`[[title]] <std_req__iso26262__analysis_747>`
141+
- <Rationale for result>
142+
143+
* - 7
144+
- Can be the required level of independence shown for the identified potential dependent failures?
145+
- [YES | NO ]
146+
- :need:`[[title]] <std_req__iso26262__analysis_748>`
147+
- <Rationale for result>
148+
149+
* - 8
150+
- Are the templates for DFA used? See :ref:`dfa_templates` and also :ref:`process_requirements_safety_analysis`
151+
- [YES | NO ]
152+
- :need:`[[title]] <std_req__iso26262__analysis_748>`
153+
- <Rationale for result>
154+
155+
* - 9
156+
- Is the DFA performed in a systematic way to identify the potential dependent failures and their effects? Are the failure effect and the mitigation described?
157+
- [YES | NO ]
158+
- :need:`[[title]] <std_req__iso26262__analysis_8410>`
159+
- <Rationale for result>
160+
161+
162+
.. list-table:: FMEA Checklist
163+
:header-rows: 1
164+
:widths: 10,10,30,30,20
165+
166+
* - ID
167+
- Safety analysis activity
168+
- Compliant to ISO 26262?
169+
- Reference
170+
- Comment
171+
172+
* - 1
173+
- Are the fault models suitable and applied for the FMEA? See :ref:`fault_models` and also :ref:`process_requirements_safety_analysis`
174+
- [YES | NO ]
175+
- :need:`[[title]] <std_req__iso26262__analysis_846>`
176+
- <Rationale for result>
177+
178+
* - 2
179+
- Is the FMEA performed in a systmatic way to identify the potential failure modes and their effects? Are the failure effect and the mitigation described?
180+
- [YES | NO ]
181+
- :need:`[[title]] <std_req__iso26262__analysis_849>`
182+
- <Rationale for result>
183+
184+
* - 3
185+
- Are the templates for FMEA used? See :ref:`FMEA_templates` and also :ref:`process_requirements_safety_analysis`
186+
- [YES | NO ]
187+
- :need:`[[title]] <std_req__iso26262__analysis_849>`, :need:`[[title]] <std_req__iso26262__analysis_8410>`
188+
- <Rationale for result>

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

Lines changed: 104 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,8 @@ As described in :need:`wf__p_formal_rv`, the formal document review is performed
4747

4848
Please note that the "passed" column must contain "yes" or "no" for each checklist item. Additionally, the remarks column must explain why item passed or did not passed. In case of "no" an issue link to the issue tracking system has to be added in the last column. See also :ref:`review_concept` for further information about reviews in general and inspection in particular.
4949

50-
.. list-table:: Safety Analysis Checklist
50+
51+
.. list-table:: General Checklist
5152
:header-rows: 1
5253
:widths: 10,10,30,30,20
5354

@@ -58,43 +59,131 @@ Please note that the "passed" column must contain "yes" or "no" for each checkli
5859
- Comment
5960

6061
* - 1
61-
- Is it plausible that each potential identified dependent failure that has been identified, will lead to a dependent failure which cause a violation of FFI?
62+
- Are the safety analysis performed according to the defined process and templates? See :ref:`process_requirements_safety_analysis` and also :ref:`FMEA_templates` and :ref:`dfa_templates`
6263
- [YES | NO ]
63-
- :need:`[[title]] <std_req__iso26262__analysis_742>`
64+
- :need:`[[title]] <std_req__iso26262__analysis_841>`
6465
- <Rationale for result>
6566

6667
* - 2
67-
- Are the failure initiators :need:`[[title]] <gd_guidl__dfa_failure_initiators>` / fault models :need:`[[title]] <gd_guidl__fault_models>` applied?
68+
- Is the result of the safety analysis indicate if the safety requirements are complied?
6869
- [YES | NO ]
69-
- :need:`[[title]] <std_req__iso26262__analysis_744>`
70+
- :need:`[[title]] <std_req__iso26262__analysis_842>`
7071
- <Rationale for result>
7172

7273
* - 3
73-
- Are measures defined to resolute the identified potential dependent failures?
74+
- Are for all not complied safety requirements mitigations defined to resolute the non-compliance? The mitigations shall have a direct influence on the violation by prevention, detection or mitigation to reduce the risk to an acceptable level.
7475
- [YES | NO ]
75-
- :need:`[[title]] <std_req__iso26262__analysis_746>`, :need:`[[title]] <std_req__iso26262__analysis_747>`
76+
- :need:`[[title]] <std_req__iso26262__analysis_843>`
7677
- <Rationale for result>
7778

7879
* - 4
79-
- Is the result of the safety analysis indicate if the safety requirements are complied?
80+
- Are the mitigations effective and implemented?
8081
- [YES | NO ]
81-
- :need:`[[title]] <std_req__iso26262__analysis_842>`
82+
- :need:`[[title]] <std_req__iso26262__analysis_844>`
8283
- <Rationale for result>
8384

8485
* - 5
85-
- Are for all not complied safety requirements mitigations defined to resolute the non-compliance? The mitigations shall have a direct influence on the violation by prevention, detection or mitigation to reduce the risk to an acceptable level.
86+
- Are newly identified hazards adressed to be considered in HARA in the safety manual?
8687
- [YES | NO ]
87-
- :need:`[[title]] <std_req__iso26262__analysis_843>`
88+
- :need:`[[title]] <std_req__iso26262__analysis_845>`
8889
- <Rationale for result>
8990

9091
* - 6
91-
- Are the mitigations effective and implemented?
92+
- Are additional safety-related test cases determined by potential results of the safety analyses?
9293
- [YES | NO ]
93-
- :need:`[[title]] <std_req__iso26262__analysis_844>`
94+
- :need:`[[title]] <std_req__iso26262__analysis_847>`
95+
- <Rationale for result>
96+
97+
98+
.. list-table:: DFA Checklist
99+
:header-rows: 1
100+
:widths: 10,10,30,30,20
101+
102+
* - ID
103+
- Safety analysis activity
104+
- Compliant to ISO 26262?
105+
- Reference
106+
- Comment
107+
108+
* - 1
109+
- Are the potential dependent failures identified by performming a DFA?
110+
- [YES | NO ]
111+
- :need:`[[title]] <std_req__iso26262__analysis_741>`
112+
- <Rationale for result>
113+
114+
* - 2
115+
- Is it plausible that each potential identified dependent failure that has been identified, will lead to a dependent failure which cause a violation of FFI?
116+
- [YES | NO ]
117+
- :need:`[[title]] <std_req__iso26262__analysis_742>`
118+
- <Rationale for result>
119+
120+
* - 3
121+
- Are applicable operational situations and operating modes considered?
122+
- [YES | NO ]
123+
- :need:`[[title]] <std_req__iso26262__analysis_743>`
124+
- <Rationale for result>
125+
126+
* - 4
127+
- Are the failure initiators :need:`[[title]] <gd_guidl__dfa_failure_initiators>` suitable and applied?
128+
- [YES | NO ]
129+
- :need:`[[title]] <std_req__iso26262__analysis_744>`
130+
- <Rationale for result>
131+
132+
* - 5
133+
- Is a rationale provided for each identified potential dependent failure?
134+
- [YES | NO ]
135+
- :need:`[[title]] <std_req__iso26262__analysis_745>`
136+
- <Rationale for result>
137+
138+
* - 6
139+
- Are measures defined to resolute the identified potential dependent failures?
140+
- [YES | NO ]
141+
- :need:`[[title]] <std_req__iso26262__analysis_746>`, :need:`[[title]] <std_req__iso26262__analysis_747>`
94142
- <Rationale for result>
95143

96144
* - 7
97-
- Are the templates for DFA and/or FMEA used? See :ref:`dfa_templates` / :ref:`FMEA_templates` and also :ref:`process_requirements_safety_analysis`
145+
- Can be the required level of independence shown for the identified potential dependent failures?
146+
- [YES | NO ]
147+
- :need:`[[title]] <std_req__iso26262__analysis_748>`
148+
- <Rationale for result>
149+
150+
* - 8
151+
- Are the templates for DFA used? See :ref:`dfa_templates` and also :ref:`process_requirements_safety_analysis`
152+
- [YES | NO ]
153+
- :need:`[[title]] <std_req__iso26262__analysis_748>`
154+
- <Rationale for result>
155+
156+
* - 9
157+
- Is the DFA performed in a systematic way to identify the potential dependent failures and their effects? Are the failure effect and the mitigation described?
158+
- [YES | NO ]
159+
- :need:`[[title]] <std_req__iso26262__analysis_8410>`
160+
- <Rationale for result>
161+
162+
163+
.. list-table:: FMEA Checklist
164+
:header-rows: 1
165+
:widths: 10,10,30,30,20
166+
167+
* - ID
168+
- Safety analysis activity
169+
- Compliant to ISO 26262?
170+
- Reference
171+
- Comment
172+
173+
* - 1
174+
- Are the fault models suitable and applied for the FMEA? See :ref:`fault_models` and also :ref:`process_requirements_safety_analysis`
175+
- [YES | NO ]
176+
- :need:`[[title]] <std_req__iso26262__analysis_846>`
177+
- <Rationale for result>
178+
179+
* - 2
180+
- Is the FMEA performed in a systmatic way to identify the potential failure modes and their effects? Are the failure effect and the mitigation described?
181+
- [YES | NO ]
182+
- :need:`[[title]] <std_req__iso26262__analysis_849>`
183+
- <Rationale for result>
184+
185+
* - 3
186+
- Are the templates for FMEA used? See :ref:`FMEA_templates` and also :ref:`process_requirements_safety_analysis`
98187
- [YES | NO ]
99-
- :need:`[[title]] <std_req__iso26262__analysis_748>`, :need:`[[title]] <std_req__iso26262__analysis_849>`, :need:`[[title]] <std_req__iso26262__analysis_8410>`
188+
- :need:`[[title]] <std_req__iso26262__analysis_849>`, :need:`[[title]] <std_req__iso26262__analysis_8410>`
100189
- <Rationale for result>

0 commit comments

Comments
 (0)