Update Safety Analysis Template

[ANegm-ETAS]

relevant docs-as-code PR
eclipse-score/docs-as-code#517

[github-actions]

The created documentation from the pull request is available at: docu-html

[masc2023]

Did you add process requirements for the attributes in the safety analysis process area and mark them as optional?

[ANegm-ETAS]

eclipse-score/docs-as-code#517

yes, added in the PR below
eclipse-score/docs-as-code#517

[masc2023]

eclipse-score/docs-as-code#517

yes, added in the PR below eclipse-score/docs-as-code#517

This is maybe an misunderstanding, I wrote process requirements, has to be added here
https://eclipse-score.github.io/process_description/main/process_areas/safety_analysis/guidance/safety_analysis_process_reqs.html

[ANegm-ETAS]

eclipse-score/docs-as-code#517

yes, added in the PR below eclipse-score/docs-as-code#517

This is maybe an misunderstanding, I wrote process requirements, has to be added here https://eclipse-score.github.io/process_description/main/process_areas/safety_analysis/guidance/safety_analysis_process_reqs.html

you're right i thought you were talking about docs-as-code requirements I'll update this PR

[aschemmel-tech]

In addition to the process requirements it should be also taken over in the guideline (https://eclipse-score.github.io/process_description/main/process_areas/safety_analysis/guidance/safety_analysis_guideline.html#step-by-step-approach-fmea) how these optional attributes should be used. In my current analysises I put the information about the root cause in the rationale section of the failure mode list.

[masc2023]

My comments have been resolved