..
   # *******************************************************************************
   # 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
   # *******************************************************************************

Getting Started
###############

.. doc_getstrt:: Getting Started on Safety Analysis (FMEA and DFA)
   :id: doc_getstrt__safety_analysis
   :status: valid
   :tags: safety_analysis


This document outlines the steps for performing, monitoring, and verifying Safety Analysis. Safety Analysis is used as a umbrella term for the methods
DFA (Dependent Failure Analysis) and FMEA (Failure Mode and Effects Analysis).
The concept of performing Safety Analysis is described in :need:`doc_concept__safety_analysis`. The verification of the architecture is described
in :need:`doc_concept__arch_process`.

Safety Analysis Steps
*********************

The goal of the Safety Analysis is to proof that the safety requirements for functions and safety mechanisms are not violated.
The Safety Analysis is performed in three steps.

* Analyse the architecture with a DFA and FMEA.
* Monitor the DFA and FMEA and log any issues in the Issue Tracking system with the ``safety`` label until the analysis is completed.
* Verify the FMEA and DFA results by using :need:`gd_chklst__safety_analysis`. The Safety Analysis are completed when the verification is done, no issues are open and the status is “valid”.

The details of what needs to be done in each step are described in the :need:`gd_guidl__safety_analysis`. For the Safety Analysis
templates are used. The templates are described in the :ref:`FMEA_templates` and :ref:`DFA_templates`.