SafetyGoal represents the top-level safety requirement defined in ISO26262. Its purpose is to define how to avoid its associated HazardousEvents, or reduce the risk associated with the hazardous event to an acceptable level.<br/><br/>The SafetyGoal is defined through one or several associated requirement elements.<br/><br/>An ASIL shall be assigned to each SafetyGoal, to represent the integrity level at which the SafetyGoal must be met.<br/><br/>Similar SafetyGoals can be combined into one SafetyGoal. If different ASILs are assigned to similar SafetyGoals, the highest ASIL shall be assigned to the combined SafetyGoal.<br/><br/>For every SafetyGoal, a safe state should be defined, by referencing a specific mode. The safe state is a system state to be maintained or to be reached when a potential source of its hazardous event is detected.<br/><br/>Semantics:<br/>SafetyGoal represents a safety Goal according to ISO26262. Requirements define the SafetyGoal, and HazardousEvents identify the responsibility of each SafetyGoal. HazardClassification defines the integrity classification of the SafetyGoal, and safeStates may be defined through associated Modes.<br/><br/>Notation:<br/>SafetyGoal is a box with text SafetyGoal at the top left.<br/><br/>Extension:<br/>Class<br/>
Name: safeState
For every SafetyGoal, a safe state should be defined, in order to declare a system state to be maintained or to be reached when the failure is detected and so to allow a failure mitigation action without any violation of the associated SafetyGoal.
