Skip to content

Audit preparation: Safety Analysis #83

@aschemmel-tech

Description

@aschemmel-tech

"not started" topics:

  • none

Actions and Deviations:

  • Action_58: The target of the DFA and the FMEA of the different levels shall be described. What are the acceptance criteria of the analyses. Try to phrase “The DFA of the platform shall show the independence of the features”. The DFA of the Feature shall show …”, the DFA of the component level shall show …”. In other words, the acceptance criteria shall be defined.
  • Action_59: Cascading failures might be covered by the FMEA.
  • Action_60: The FMEA shall describe that systematic software faults shall be analyzed. Systematic faults need either to be avoided (low complexity, full testability, small interface, no historical values, …) or controlled by safety mechanisms. - The Safety Analysis must be done by a “Safety Engineer” who is required to be experienced with software safety analysis.
  • Action_61: It shall be described when Safety Analyses should be performed - Are these triggered by a change request? (“The safety analysis shall be done accompanying to the development. So the results can directly be used for the development of the feature and component.“)
  • proceed with Resolve comments from Interim Audit #5 - Safety Analysis #48

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

Status

Done

Relationships

None yet

Development

No branches or pull requests

Issue actions