.. # ******************************************************************************* # Copyright (c) 2025 Contributors to the Eclipse Foundation # # See the NOTICE file(s) distributed with this work for additional # information regarding copyright ownership. # # This program and the accompanying materials are made available under the # terms of the Apache License Version 2.0 which is available at # https://www.apache.org/licenses/LICENSE-2.0 # # SPDX-License-Identifier: Apache-2.0 # ******************************************************************************* Safety Analysis Checklist ========================= .. document:: [Your Module Name] Safety Analysis Checklist :id: doc__mod_temp_module_name_safety_analysis_fdr :status: draft :safety: ASIL_B :security: YES :realizes: wp__fdr_reports :tags: template .. attention:: The above directive must be updated according to your Module. - Modify ``Your Module Name`` to be your Module Name - Modify ``id`` to be your Module Name in lower snake case preceded by ``doc__`` and followed by ``_safety _analysis_fdr`` - Adjust ``status`` to be ``valid`` - Adjust ``safety``, ``security`` and ``tags`` according to your needs **Purpose** 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. **Conduct** As described in :need:`wf__p_formal_rv`, the formal document review is performed by an "external" safety manager: - reviewer: **Checklist** 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 the review concept for further information about reviews in general and inspection in particular. .. list-table:: Safety Analysis Checklist :header-rows: 1 :widths: 10,10,30,30,20 * - ID - Safety analysis activity - Compliant to ISO 26262? - Reference - Comment * - 1 - 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? - [YES | NO ] - :need:`[[title]] ` - * - 2 - Are the failure initiators :need:`[[title]] ` / fault models :need:`[[title]] ` applied? - [YES | NO ] - :need:`[[title]] ` - * - 3 - Are measures defined to resolute the identified potential dependent failures? - [YES | NO ] - :need:`[[title]] `, :need:`[[title]] ` - * - 4 - Is the result of the safety analysis indicate if the safety requirements are complied? - [YES | NO ] - :need:`[[title]] ` - * - 5 - 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. - [YES | NO ] - :need:`[[title]] ` - * - 6 - Are the mitigations effective and implemented? - [YES | NO ] - :need:`[[title]] ` - * - 7 - Are the templates for DFA and/or FMEA used? See the DFA templates, FMEA templates, and process requirements for safety analysis. - [YES | NO ] - :need:`[[title]] `, :need:`[[title]] `, :need:`[[title]] ` -