MARTE_ — What about a System Configuration concept having a set of OperationalModes?

The operationalModes association end from rtUnit to rtBehavior has a multiplicity 0..1. This is not enough to model the OperationalMode as understood by fault-tolerance theory. An rtUnit should be capable to have many operationalModes. In addition, an OperationlMode would be need to be defined at system level too (not rtUnit level only). It seems that a separated stereotype (not rtBehavior as currently) would be necessary for OperationalMode. What about a System Configuration concept having a set of OperationalModes?

The concept of Mode (or Operational Mode) is central in embedded systems and
in dependable embedded systems in particular. Having this concept only as an
attribute of the RtUnit concept is indeed insufficient to model the behavioural and
structural aspects of mode sensitive architectures. An operational mode can
represent different things:

• An operational system (or subsystem) state that is managed by reconfiguration
  mechanisms (e.g., fault-tolerance management middleware) according to fault
  conditions.
• A state of system operation with a given level of QoS that can be handled by
  resource management infrastructures (e.g., middleware that assign resources at
  run time according to load demand, timing constraints, or resource usage).
• A phase of a system operation e.g., starting, stopping, reconfiguring switchers,
  in a supervisory control system of an electric grid.
  We propose to adopt a number of minimum concepts to describe operational
  modes and their dynamics with UML state machines. Please notice that a UML
  state machine may be used “as is” to model operational modes and their
  dynamics. However, the need to unambiguously distinguish modal state
  machines, specifying the kind of above-mentioned macro-states, from other
  standard state machines, motivated us for explicitly describing these concepts in
  the MARTE specification. Furthermore, it seems necessary to characterize
  certain MARTE concepts with “modal” information. For instance, defining which entities are active in a given mode, specifying how entities behave in a mode
  transition, or determining what NFP values are valid in a given mode, all require
  means to refer to the entities proposed in this resolution.
  This resolution proposes to define this set of concepts related to operational
  modes in the “Core Elements” chapter. A number of updates are also proposed
  in other MARTE chapters to refer to the concepts added in “Core Elements”.