Quality Goal This element represents a quality requirement as a goal. characteristic property contains the quality characteristic or factor which the requirement belong to. satisfaction property represents an expression which describes how the quality is satisfied in term of quality metrics.
Quality Level This element represents a quality level. A quality level can include quality goals.
Attack This element represents an attack that could be performed against the system.
Failure This element represents a failure that could happen in the system.
Failure Case This element represents the behavior that the system shows to the user when is in a failure state.
Misuse Case This element represents the misuse of the system that an user does which can lead to a failure.
Change Event This element represents a change event in the system. Usually, environment changes.
Configuration This element represents a configuration in the system.
Self-Management Capability This element represents a self-management capability that the system should have implemented at the end of the development. This capability may have a self-management process associated which is modeled using the node elements provided by SelfMML to be drawn in activity diagrams.
Monitoring Node This element represents a monitoring activity in a self-management process. It does not imply any specific way of doing monitoring. After each monitoring cycle a "token" goes through the outgoing edges starting a new flow in the process.
Analysis Node This element represents an analysis activity in a self-management process. This activity usually makes an evaluation of the reports which come from monitoring in order to decide whether continue with planning or not. It can be used with a Decision Node and a Flow Final Node to abort a flow indicating not to continue with planning.
Plan Construction Node This element represents an activity of constructing a plan (semi-)automatically.
Plan Selection Node This element is a flow control activity. It is used to lead the flow to a specific plan in the process. This element has to be used with "Plan Selection Guard Node" element in order to specify the selection criteria. If this element is used, it is supposed that the selection criteria can be described with OCL or similar language.
Plan Selection Guard Node This element is to constrain the execution of plans. The "specification" property contains a constraint in term of OCL or similar language. When a "token" comes by an incoming edge the constraint is verifed. If it is true then the "token" is copied to all outgoing edges.
Plan Selection Process Node This element represents a selection process. It is useful when the selection of plans cannot be expressed with OCL or similiar language in a clear way. However, all outgoing edges of this element should be constrained with guards and some parameter in order to specify which plan is selected. e.g. parameter:selectedPlan, a guard: [selectedPlan=1]
Plan Execution Node This element represents an execution of a plan.
Plan Step Execution Node This element represents an execution of a step of a plan.
<< affect >>
 Affect This relationship connects "Attack", "MiuseCase", "Failure" or "FailureCase" with a "UseCase" element to indicate that the first affects the normal behavior modeled in the second.
<< cause >>
 Cause This relationship connects "Attack", "MiuseCase", "Failure" or "FailureCase" with a "Failure" element to indicate that the first causes the second.
<< activate >>
 Activate This relationship connects a "Failure" with a "FailureCase" element to indicate that the first activates the wrong behavior modeled in the second.
<< include >>
 Include This relationship connects a "QualityLevel" with a "QualityGoal" element to indicate that the first includes the second in its set of quality goals.
<< require >>
 Require This relationship connects a "SelfManagementCapability" with a "UseCase" element to indicate that the first requires the development of the second.
<< tune >>
 Tune This relationship connects a "SelfManagementCapability" with a "Configuration" element to indicate that the first has the objective of tunning some parameters of the second.
<< complete >>
 Complete This relationship connects a "SelfManagementCapability" with a "Configuration" element to indicate that the first has the objective of completing the configuration of some parameters of the second. e.g. infering the value of them.
<< update >>
 Update This relationship connects a "SelfManagementCapability" with a "Configuration" element to indicate that the first has the objective of updating some parameters of the second, when the some change event happens in the system.
<< defend >>
 Defend This relationships connects a "SelfManagmentCapability" with a "Attack" element to indicate that the first has the objective of defending the system against the second.
<< isolate >>
 Isolate This relationships connects a "SelfManagmentCapability" with a "Failure" element to indicate that the first has the objective of isolating the second to avoid its propagation.
<< avoid >>
 Avoid This relationships connects a "SelfManagmentCapability" with a "Failure", "FailureCase", "Attack" or "MisuseCase" element to indicate that the first has the objective of avoiding (reducing the likelihood to zero) the second.
<<reduceConsequence>>
 Reduce Consequence This relationships connects a "SelfManagmentCapability" with a "Failure", "FailureCase", "Attack" or "MisuseCase" element to indicate that the first has the objective of reducing the consequences of the second.
<<reduceLikelihood>>
 Reduce Likelihood This relationships connects a "SelfManagmentCapability" with a "Failure", "FailureCase", "Attack" or "MisuseCase" element to indicate that the first has the objective of reducing the likelihood of the second.
<< deactivate >>
 Deactivate This relationships connects a "SelfManagmentCapability" with a "FailureCase" element to indicate that the first deactivates the second if its recovery plan finishes successfully.
<< contribute >>
 Contribute This relationships connects a "SelfManagmentCapability" with a "QualityGoal" element to indicate that the first contributes to the satisfaction of the second.
<< threaten >>
 Threaten This relationships connects a "Failure" with a "QualityGoal" element to indicate that the first threatens the satisfaction of the second.
<< recoverFrom >>
 Recover From This relationships connects a "SelfManagmentCapability" with a "Failure" element to indicate that the first has the objective of recovering the system from the second.