Modes are a way to introduce various configurations in the system to account for different states of the system, or of a hardware entity, or an application. The use of modes can be used to filter different views of the model.<br/><br/>Modes are characterized by a Boolean condition provided as a String, which evaluates to true when the Mode is active.<br/><br/>As far as behavior is concerned, Modes enable the logical organization of a set of triggers and behaviors over a set of functions. Modes are referred to by both FunctionTriggers and FunctionBehaviors (see FunctionTrigger and FunctionBehavior).<br/><br/>Modes can be further organized in mutually exclusive sets with ModeGroups (see that element).<br/><br/>Semantics:<br/>The Mode is active if and only if the condition is true.<br/>
A Boolean expression that characterizes the Mode, it evaluates to true when the Mode is active. The syntax and grammar of this expression is unspecified.<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.