diff options
| author | khussey | 2005-11-17 21:23:32 +0000 |
|---|---|---|
| committer | khussey | 2005-11-17 21:23:32 +0000 |
| commit | 3574be59410e550c42cd8194d687945d81205dce (patch) | |
| tree | 6ab413e5bd2b3fc25f9822f47679f46d4dde1696 /plugins/org.eclipse.uml2.uml/model/UML.ecore | |
| parent | 972a67d28933772a6438973defcc93b8ea3b6dac (diff) | |
| download | org.eclipse.uml2-3574be59410e550c42cd8194d687945d81205dce.tar.gz org.eclipse.uml2-3574be59410e550c42cd8194d687945d81205dce.tar.xz org.eclipse.uml2-3574be59410e550c42cd8194d687945d81205dce.zip | |
[80305] Regenerating code based on updated source model.
Diffstat (limited to 'plugins/org.eclipse.uml2.uml/model/UML.ecore')
| -rw-r--r-- | plugins/org.eclipse.uml2.uml/model/UML.ecore | 146 |
1 files changed, 61 insertions, 85 deletions
diff --git a/plugins/org.eclipse.uml2.uml/model/UML.ecore b/plugins/org.eclipse.uml2.uml/model/UML.ecore index 5b4ce184d..200c5e998 100644 --- a/plugins/org.eclipse.uml2.uml/model/UML.ecore +++ b/plugins/org.eclipse.uml2.uml/model/UML.ecore @@ -229,14 +229,14 @@ <eAnnotations source="http://www.eclipse.org/emf/2002/GenModel"> <details key="documentation" value="NamedElement has a visibility attribute.
A named element represents elements that may have a name. The name is used for identification of the named element within the namespace in which it is defined. A named element also has a qualified name that allows it to be unambiguously identified within a hierarchy of nested namespaces. NamedElement is an abstract metaclass.
NamedElement specializes Kernel::NamedElement and adds a composition association to Expression."/> </eAnnotations> - <eOperations name="no_name" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EBoolean"> + <eOperations name="has_no_qualified_name" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EBoolean"> <eAnnotations source="http://www.eclipse.org/emf/2002/GenModel"> <details key="documentation" value="If there is no name, or one of the containing namespaces has no name, there is no qualified name.
(self.name->isEmpty() or self.allNamespaces()->select(ns | ns.name->isEmpty())->notEmpty())

 implies self.qualifiedName->isEmpty()"/> </eAnnotations> <eParameters name="diagnostics" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EDiagnosticChain"/> <eParameters name="context" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EMap"/> </eOperations> - <eOperations name="qualified_name" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EBoolean"> + <eOperations name="has_qualified_name" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EBoolean"> <eAnnotations source="http://www.eclipse.org/emf/2002/GenModel"> <details key="documentation" value="When there is a name, and all of the containing namespaces have a name, the qualified name is constructed from the names of the containing namespaces.
(self.name->notEmpty() and self.allNamespaces()->select(ns | ns.name->isEmpty())->isEmpty()) implies
 self.qualifiedName = self.allNamespaces()->iterate( ns : Namespace; result: String = self.name | ns.name->union(self.separator())->union(result))"/> </eAnnotations> @@ -515,7 +515,7 @@ <eAnnotations source="http://www.eclipse.org/emf/2002/GenModel"> <details key="documentation" value="TemplateBinding is a directed relationship from a bound templateable element to the template signature of the target template. A TemplateBinding owns a set of template parameter substitutions."/> </eAnnotations> - <eOperations name="parameter_substitution" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EBoolean"> + <eOperations name="parameter_substitution_formal" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EBoolean"> <eAnnotations source="http://www.eclipse.org/emf/2002/GenModel"> <details key="documentation" value="Each parameter substitution must refer to a formal template parameter of the target template signature.
parameterSubstitution->forAll(b | template.parameter->includes(b.formal))"/> </eAnnotations> @@ -594,7 +594,7 @@ <eAnnotations source="http://www.eclipse.org/emf/2002/GenModel"> <details key="documentation" value="A namespace has the ability to import either individial members or all members of a package, thereby making it possible to refer to those named elements without qualification in the importing namespace. In the case of conflicts, it is necessary to use qualified names or aliases to disambiguate the referenced elements.
A namespace is a named element that can own other named elements. Each named element may be owned by at most one namespace. A namespace provides a means for identifying named elements by name. Named elements can be identified by name in a namespace either by being directly owned by the namespace or by being introduced into the namespace by other means e.g. importing or inheriting. Namespace is an abstract metaclass.



A namespace can own constraints. The constraint does not necessarily apply to the namespace itself, but may also apply to elements in the namespace.



A namespace has the ability to import either individual members or all members of a package, thereby making it possible to refer to those named elements without qualification in the importing namespace. In the case of conflicts, it is necessary to use qualified names or aliases to disambiguate the referenced elements.




A namespace is a named element that can own other named elements. Each named element may be owned by at most one namespace. A namespace provides a means for identifying named elements by name. Named elements can be identified by name in a namespace either by being directly owned by the namespace or by being introduced into the namespace by other means e.g. importing or inheriting. Namespace is an abstract metaclass."/> </eAnnotations> - <eOperations name="members_are_distinguishable" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EBoolean"> + <eOperations name="members_distinguishable" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EBoolean"> <eAnnotations source="http://www.eclipse.org/emf/2002/GenModel"> <details key="documentation" value="All the members of a Namespace are distinguishable within it.
membersAreDistinguishable()"/> </eAnnotations> @@ -1157,13 +1157,6 @@ <eParameters name="diagnostics" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EDiagnosticChain"/> <eParameters name="context" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EMap"/> </eOperations> - <eOperations name="specialize_type" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EBoolean"> - <eAnnotations source="http://www.eclipse.org/emf/2002/GenModel"> - <details key="documentation" value="A classifier may only specialize classifiers of a valid type.
self.parents()->forAll(c | self.maySpecializeType(c))"/> - </eAnnotations> - <eParameters name="diagnostics" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EDiagnosticChain"/> - <eParameters name="context" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EMap"/> - </eOperations> <eOperations name="generalization_hierarchies" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EBoolean"> <eAnnotations source="http://www.eclipse.org/emf/2002/GenModel"> <details key="documentation" value="Generalization hierarchies must be directed and acyclical. A classifier can not be both a transitively general and transitively specific classifier of the same classifier.
not self.allParents()->includes(self)"/> @@ -1171,7 +1164,7 @@ <eParameters name="diagnostics" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EDiagnosticChain"/> <eParameters name="context" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EMap"/> </eOperations> - <eOperations name="specialize" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EBoolean"> + <eOperations name="specialize_type" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EBoolean"> <eAnnotations source="http://www.eclipse.org/emf/2002/GenModel"> <details key="documentation" value="A classifier may only specialize classifiers of a valid type.
self.parents()->forAll(c | self.maySpecializeType(c))"/> </eAnnotations> @@ -1185,15 +1178,6 @@ <eParameters name="diagnostics" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EDiagnosticChain"/> <eParameters name="context" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EMap"/> </eOperations> - <eOperations name="maySpecializeType" ordered="false" lowerBound="1" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EBoolean"> - <eAnnotations source="http://www.eclipse.org/emf/2002/GenModel"> - <details key="documentation" value="The query maySpecializeType() determines whether this classifier may have a generalization relationship to classifiers of the specified type. By default a classifier may specialize classifiers of the same or a more general type. It is intended to be redefined by classifiers that have different specialization constraints.
result = self.oclIsKindOf(c.oclType)"/> - </eAnnotations> - <eAnnotations source="http://www.eclipse.org/emf/2002/Ecore"> - <details key="constraints" value="spec"/> - </eAnnotations> - <eParameters name="c" ordered="false" lowerBound="1" eType="#//Classifier"/> - </eOperations> <eOperations name="getGenerals" ordered="false" upperBound="-1" eType="#//Classifier"> <eAnnotations source="http://www.eclipse.org/emf/2002/GenModel"> <details key="documentation" value="The general classifiers are the classifiers referenced by the generalization relationships.
result = self.parents()"/> @@ -1270,6 +1254,7 @@ <eAnnotations source="http://www.eclipse.org/emf/2002/Ecore"> <details key="constraints" value="spec"/> </eAnnotations> + <eParameters name="c" ordered="false" lowerBound="1" eType="#//Classifier"/> </eOperations> <eOperations name="allParents" ordered="false" upperBound="-1" eType="#//Classifier"> <eAnnotations source="http://www.eclipse.org/emf/2002/GenModel"> @@ -1400,16 +1385,6 @@ <eParameters name="diagnostics" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EDiagnosticChain"/> <eParameters name="context" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EMap"/> </eOperations> - <eOperations name="isRedefinitionContextValid" ordered="false" lowerBound="1" - eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EBoolean"> - <eAnnotations source="http://www.eclipse.org/emf/2002/GenModel"> - <details key="documentation" value="The query isRedefinitionContextValid() specifies whether the redefinition contexts of this RedefinableElement are properly related to the redefinition contexts of the specified RedefinableElement to allow this element to redefine the other. By default at least one of the redefinition contexts of this element must be a specialization of at least one of the redefinition contexts of the specified element.
result = self.redefinitionContext->exists(c | redefinable.redefinitionContext->exists(r | c.allParents()->includes(r)))"/> - </eAnnotations> - <eAnnotations source="http://www.eclipse.org/emf/2002/Ecore"> - <details key="constraints" value="spec"/> - </eAnnotations> - <eParameters name="redefinable" ordered="false" lowerBound="1" eType="#//RedefinableElement"/> - </eOperations> <eOperations name="isConsistentWith" ordered="false" lowerBound="1" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EBoolean"> <eAnnotations source="http://www.eclipse.org/emf/2002/GenModel"> <details key="documentation" value="The query isConsistentWith() specifies, for any two RedefinableElements in a context in which redefinition is possible, whether redefinition would be logically consistent. By default, this is false; this operation must be overridden for subclasses of RedefinableElement to define the consistency conditions.
redefinee.isRedefinitionContextValid(self)


result = false"/> @@ -1422,11 +1397,12 @@ <eOperations name="isRedefinitionContextValid" ordered="false" lowerBound="1" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EBoolean"> <eAnnotations source="http://www.eclipse.org/emf/2002/GenModel"> - <details key="documentation" value="The query isRedefinitionContextValid() specifies whether the redefinition contexts of this RedefinableElement are properly related to the redefinition contexts of the specified RedefinableElement to allow this element to redefine the other. By default at least one of the redefinition contexts of this element must be a specialization of at least one of the redefinition contexts of the specified element.
result = redefinitionContext->exists(c | c.allParents()->includes(redefined.redefinitionContext))"/> + <details key="documentation" value="The query isRedefinitionContextValid() specifies whether the redefinition contexts of this RedefinableElement are properly related to the redefinition contexts of the specified RedefinableElement to allow this element to redefine the other. By default at least one of the redefinition contexts of this element must be a specialization of at least one of the redefinition contexts of the specified element.
result = redefinitionContext->exists(c | c.allParents()->includes(redefined.redefinitionContext)))"/> </eAnnotations> <eAnnotations source="http://www.eclipse.org/emf/2002/Ecore"> <details key="constraints" value="spec"/> </eAnnotations> + <eParameters name="redefined" ordered="false" lowerBound="1" eType="#//RedefinableElement"/> </eOperations> <eStructuralFeatures xsi:type="ecore:EAttribute" name="isLeaf" ordered="false" lowerBound="1" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EBoolean" @@ -2232,7 +2208,7 @@ <eParameters name="diagnostics" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EDiagnosticChain"/> <eParameters name="context" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EMap"/> </eOperations> - <eOperations name="subsetting_context" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EBoolean"> + <eOperations name="subsetting_context_conforms" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EBoolean"> <eAnnotations source="http://www.eclipse.org/emf/2002/GenModel"> <details key="documentation" value="Subsetting may only occur when the context of the subsetting property conforms to the context of the subsetted property.
self.subsettedProperty->notEmpty() implies
 (self.subsettingContext()->notEmpty() and self.subsettingContext()->forAll (sc |
 self.subsettedProperty->forAll(sp |
 sp.subsettingContext()->exists(c | sc.conformsTo(c)))))"/> </eAnnotations> @@ -2771,7 +2747,7 @@ <eAnnotations source="http://www.eclipse.org/emf/2002/GenModel"> <details key="documentation" value="The DataType that owns this Operation.
The DataType that owns this Property."/> </eAnnotations> - <eAnnotations source="subsets" references="#//NamedElement/namespace #//RedefinableElement/redefinitionContext #//Feature/featuringClassifier"/> + <eAnnotations source="subsets" references="#//RedefinableElement/redefinitionContext #//NamedElement/namespace #//Feature/featuringClassifier"/> </eStructuralFeatures> <eStructuralFeatures xsi:type="ecore:EReference" name="bodyCondition" ordered="false" eType="#//Constraint" resolveProxies="false"> @@ -2855,7 +2831,7 @@ <eAnnotations source="http://www.eclipse.org/emf/2002/GenModel"> <details key="documentation" value="Behavior is a specification of how its context classifier changes state over time. This specification may be either a definition of possible behavior execution or emergent behavior, or a selective illustration of an interesting subset of possible executions. The latter form is typically used for capturing examples, such as a trace of a particular execution.



A classifier behavior is always a definition of behavior and not an illustration. It describes the sequence of state changes an instance of a classifier may undergo in the course of its lifetime. Its precise semantics depends on the kind of classifier. For example, the classifier behavior of a collaboration represents emergent behavior of all the parts, whereas the classifier behavior of a class is just the behavior of instances of the class separated from the behaviors of any of its parts.

When a behavior is associated as the method of a behavioral feature, it defines the implementation of that feature; i.e., the computation that generates the effects of the behavioral feature.



As a classifier, a behavior can be specialized. Instantiating a behavior is referred to as "invoking" the behavior, an instantiated behavior is also called a behavior "execution." A behavior may be invoked directly or its invocation may be the result of invoking the behavioral feature that specifies this behavior. A behavior can also be instantiated as an object in virtue of it being a class. The specification of a behavior can take a number of forms, as described in the subclasses of Behavior. Behavior is an abstract metaclass factoring out the commonalities of these different specification mechanisms.



When a behavior is invoked, its execution receives a set of input values that are used to affect the course of execution and as a result of its execution it produces a set of output values which are returned, as specified by its parameters. The observable effects of a behavior execution may include changes of values of various objects involved in the execution, the creation and destruction of objects, generation of communications between objects, as well as an explicit set of output values.


The concept of Behavior is extended to own ParameterSets."/> </eAnnotations> - <eOperations name="parameters" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EBoolean"> + <eOperations name="parameters_match" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EBoolean"> <eAnnotations source="http://www.eclipse.org/emf/2002/GenModel"> <details key="documentation" value="The parameters of the behavior must match the parameters of the implemented behavioral feature.
true"/> </eAnnotations> @@ -3159,16 +3135,6 @@ <details key="documentation" value="A state machine owns one or more regions, which in turn own vertices and transitions.

The behaviored classifier context owning a state machine defines which signal and call triggers are defined for the state machine, and which attributes and operations are available in activities of the state machine. Signal triggers and call triggers for the state machine are defined according to the receptions and operations of this classifier.



As a kind of behavior, a state machine may have an associated behavioral feature (specification) and be the method of this behavioral feature. In this case the state machine specifies the behavior of this behavioral feature. The parameters of the state machine in this case match the parameters of the behavioral feature and provide the means for accessing (within the state machine) the behavioral feature parameters.



A state machine without a context classifier may use triggers that are independent of receptions or operations of a classifier, i.e. either just signal triggers or call triggers based upon operation template parameters of the (parameterized) statemachine.

"/> </eAnnotations> <eAnnotations source="duplicates"> - <contents xsi:type="ecore:EOperation" name="isRedefinitionContextValid" ordered="false" - lowerBound="1" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EBoolean"> - <eAnnotations source="http://www.eclipse.org/emf/2002/GenModel"> - <details key="documentation" value="The query isRedefinitionContextValid() specifies whether the redefinition contexts of a statemachine are properly related to the redefinition contexts of the specified statemachine to allow this element to redefine the other. The containing classifier of a redefining statemachine must redefine the containing classifier of the redefined statemachine.
result = true"/> - </eAnnotations> - <eAnnotations source="http://www.eclipse.org/emf/2002/Ecore"> - <details key="constraints" value="spec"/> - </eAnnotations> - <eAnnotations source="redefines" references="#//RedefinableElement/isRedefinitionContextValid.1"/> - </contents> <contents xsi:type="ecore:EOperation" name="isConsistentWith" ordered="false" lowerBound="1" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EBoolean"> <eAnnotations source="http://www.eclipse.org/emf/2002/GenModel"> @@ -3229,6 +3195,17 @@ <eParameters name="s1" ordered="false" lowerBound="1" eType="#//State"/> <eParameters name="s2" ordered="false" lowerBound="1" eType="#//State"/> </eOperations> + <eOperations name="isRedefinitionContextValid" ordered="false" lowerBound="1" + eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EBoolean"> + <eAnnotations source="http://www.eclipse.org/emf/2002/GenModel"> + <details key="documentation" value="The query isRedefinitionContextValid() specifies whether the redefinition contexts of a statemachine are properly related to the redefinition contexts of the specified statemachine to allow this element to redefine the other. The containing classifier of a redefining statemachine must redefine the containing classifier of the redefined statemachine.
result = true"/> + </eAnnotations> + <eAnnotations source="http://www.eclipse.org/emf/2002/Ecore"> + <details key="constraints" value="spec"/> + </eAnnotations> + <eAnnotations source="redefines" references="#//RedefinableElement/isRedefinitionContextValid"/> + <eParameters name="redefined" ordered="false" lowerBound="1" eType="#//StateMachine"/> + </eOperations> <eStructuralFeatures xsi:type="ecore:EReference" name="region" ordered="false" lowerBound="1" upperBound="-1" eType="#//Region" containment="true" resolveProxies="false" eOpposite="#//Region/stateMachine"> @@ -3258,16 +3235,6 @@ <details key="documentation" value="A region is an orthogonal part of either a composite state or a state machine. It contains states and transitions."/> </eAnnotations> <eAnnotations source="duplicates"> - <contents xsi:type="ecore:EOperation" name="isRedefinitionContextValid" ordered="false" - lowerBound="1" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EBoolean"> - <eAnnotations source="http://www.eclipse.org/emf/2002/GenModel"> - <details key="documentation" value="The query isRedefinitionContextValid() specifies whether the redefinition contexts of a region are properly related to the redefinition contexts of the specified region to allow this element to redefine the other. The containing statemachine/state of a redefining region must redefine the containing statemachine/state of the redefined region.
result = true"/> - </eAnnotations> - <eAnnotations source="http://www.eclipse.org/emf/2002/Ecore"> - <details key="constraints" value="spec"/> - </eAnnotations> - <eAnnotations source="redefines" references="#//RedefinableElement/isRedefinitionContextValid.1"/> - </contents> <contents xsi:type="ecore:EOperation" name="isConsistentWith" ordered="false" lowerBound="1" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EBoolean"> <eAnnotations source="http://www.eclipse.org/emf/2002/GenModel"> @@ -3325,6 +3292,17 @@ <details key="constraints" value="spec"/> </eAnnotations> </eOperations> + <eOperations name="isRedefinitionContextValid" ordered="false" lowerBound="1" + eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EBoolean"> + <eAnnotations source="http://www.eclipse.org/emf/2002/GenModel"> + <details key="documentation" value="The query isRedefinitionContextValid() specifies whether the redefinition contexts of a region are properly related to the redefinition contexts of the specified region to allow this element to redefine the other. The containing statemachine/state of a redefining region must redefine the containing statemachine/state of the redefined region.
result = true"/> + </eAnnotations> + <eAnnotations source="http://www.eclipse.org/emf/2002/Ecore"> + <details key="constraints" value="spec"/> + </eAnnotations> + <eAnnotations source="redefines" references="#//RedefinableElement/isRedefinitionContextValid"/> + <eParameters name="redefined" ordered="false" lowerBound="1" eType="#//Region"/> + </eOperations> <eOperations name="containingStateMachine" ordered="false" lowerBound="1" eType="#//StateMachine"> <eAnnotations source="http://www.eclipse.org/emf/2002/GenModel"> <details key="documentation" value="The operation containingStateMachine() returns the sate machine in which this Region is defined
result = if stateMachine->isEmpty() 
then
state.containingStateMachine()
else
stateMachine
endif"/> @@ -3673,16 +3651,6 @@ <details key="documentation" value="A state models a situation during which some (usually implicit) invariant condition holds. The invariant may represent a static situation such as an object waiting for some external event to occur. However, it can also model dynamic conditions such as the process of performing some behavior (i.e., the model element under consideration enters the state when the behavior commences and leaves it as soon as the behavior is completed). The following kinds of states are distinguished:

o Simple state,

o composite state, and

o submachine state.

A composite state is either a simple composite state (with just one region) or an orthogonal state (with more than one region).



Simple state

A simple state is a state that does not have substates, i.e. it has no regions and it has no submachine state machine.



Composite state

A composite state either contains one region or is decomposed into two or more orthogonal regions. Each region has a set of mutually exclusive disjoint subvertices and a set of transitions. A given state may only be decomposed in one of these two ways. 

Any state enclosed within a region of a composite state is called a substate of that composite state. It is called a direct substate when it is not contained by any other state; otherwise it is referred to as a indirect substate. 

Each region of a composite state may have an initial pseudostate and a final state. A transition to the enclosing state represents a transition to the initial pseudostate in each region. A newly-created object takes it's topmost default transitions, originating from the topmost initial pseudostates of each region.



A transition to a final state represents the completion of behavior in the enclosing region. Completion of behavior in all orthogonal regions represents completion of behavior by the enclosing state and triggers a completion event on the enclosing state. Completion of the topmost regions of an object corresponds to its termination.



An entry pseudostate is used to join an external transition terminating on that entry point to an internal transition emanating from that entry point. An exit pseudostate is used to join an internal transition terminating on that exit point to an external transition emanating from that exit point. The main purpose of such entry and exit points is to execute the state entry and exit actions respectively in between the actions that are associated with the joined transitions.



Semantic variation point (default entry rule)

If a transition terminates on an enclosing state and the enclosed regions do not have an initial pseudostate, the interpretation of this situation is a semantic variation point. In some interpretations, this is considered an ill-formed model. That is, in those cases the initial pseudostate is mandatory. 

An alternative interpretation allows this situation and it means that, when such a transition is taken, the state machine stays in the composite state, without entering any of the regions or their substates.



Submachine state

A submachine state specifies the insertion of the specification of a submachine state machine. The state machine that contains the submachine state is called the containing state machine. The same state machine may be a submachine more than once in the context of a single containing state machine.



A submachine state is semantically equivalent to a composite state. The regions of the submachine state machine are the regions of the composite state. The entry, exit and behavior actions, and internal transitions, are defined as part of the state. Submachine state is a decomposition mechanism that allows factoring of common behaviors and their reuse.

Transitions in the containing state machine can have entry/exit points of the inserted state machine as targets/sources.


The states of protocol state machines are exposed to the users of their context classifiers. A protocol state represents an exposed stable situation of its context classifier: when an instance of the classifier is not processing any operation, users of this instance can always know its state configuration."/> </eAnnotations> <eAnnotations source="duplicates"> - <contents xsi:type="ecore:EOperation" name="isRedefinitionContextValid" ordered="false" - lowerBound="1" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EBoolean"> - <eAnnotations source="http://www.eclipse.org/emf/2002/GenModel"> - <details key="documentation" value="The query isRedefinitionContextValid() specifies whether the redefinition contexts of a state are properly related to the redefinition contexts of the specified state to allow this element to redefine the other. The containing region of a redefining state must redefine the containing region of the redefined state.
result = true"/> - </eAnnotations> - <eAnnotations source="http://www.eclipse.org/emf/2002/Ecore"> - <details key="constraints" value="spec"/> - </eAnnotations> - <eAnnotations source="redefines" references="#//RedefinableElement/isRedefinitionContextValid.1"/> - </contents> <contents xsi:type="ecore:EOperation" name="isConsistentWith" ordered="false" lowerBound="1" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EBoolean"> <eAnnotations source="http://www.eclipse.org/emf/2002/GenModel"> @@ -3796,6 +3764,17 @@ <details key="constraints" value="spec"/> </eAnnotations> </eOperations> + <eOperations name="isRedefinitionContextValid" ordered="false" lowerBound="1" + eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EBoolean"> + <eAnnotations source="http://www.eclipse.org/emf/2002/GenModel"> + <details key="documentation" value="The query isRedefinitionContextValid() specifies whether the redefinition contexts of a state are properly related to the redefinition contexts of the specified state to allow this element to redefine the other. The containing region of a redefining state must redefine the containing region of the redefined state.
result = true"/> + </eAnnotations> + <eAnnotations source="http://www.eclipse.org/emf/2002/Ecore"> + <details key="constraints" value="spec"/> + </eAnnotations> + <eAnnotations source="redefines" references="#//RedefinableElement/isRedefinitionContextValid"/> + <eParameters name="redefined" ordered="false" lowerBound="1" eType="#//State"/> + </eOperations> <eStructuralFeatures xsi:type="ecore:EAttribute" name="isComposite" ordered="false" lowerBound="1" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EBoolean" changeable="false" volatile="true" transient="true" derived="true"> @@ -4523,7 +4502,7 @@ <eAnnotations source="redefines" references="#//TemplateParameter/parameteredElement"/> </contents> </eAnnotations> - <eOperations name="constraining_classifier" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EBoolean"> + <eOperations name="has_constraining_classifier" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EBoolean"> <eAnnotations source="http://www.eclipse.org/emf/2002/GenModel"> <details key="documentation" value="If "allowSubstitutable" is true, then there must be a constrainingClassifier.
allowSubstitutable implies constrainingClassifier->notEmpty()"/> </eAnnotations> @@ -5809,7 +5788,7 @@ <eAnnotations source="http://www.eclipse.org/emf/2002/GenModel"> <details key="documentation" value="Partitions divide the nodes and edges to constrain and show a view of the contained nodes. Partitions can share contents. They often correspond to organizational units in a business model. They may be used to allocate characteristics or resources among the nodes of an activity."/> </eAnnotations> - <eOperations name="is_dimension" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EBoolean"> + <eOperations name="dimension_not_contained" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EBoolean"> <eAnnotations source="http://www.eclipse.org/emf/2002/GenModel"> <details key="documentation" value="A partition with isDimension = true may not be contained by another partition.
true"/> </eAnnotations> @@ -6339,14 +6318,14 @@ <eParameters name="diagnostics" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EDiagnosticChain"/> <eParameters name="context" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EMap"/> </eOperations> - <eOperations name="minint" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EBoolean"> + <eOperations name="minint_non_negative" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EBoolean"> <eAnnotations source="http://www.eclipse.org/emf/2002/GenModel"> <details key="documentation" value="If minint is specified, then the expression must evaluate to a non-negative integer.
true"/> </eAnnotations> <eParameters name="diagnostics" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EDiagnosticChain"/> <eParameters name="context" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EMap"/> </eOperations> - <eOperations name="maxint" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EBoolean"> + <eOperations name="maxint_positive" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EBoolean"> <eAnnotations source="http://www.eclipse.org/emf/2002/GenModel"> <details key="documentation" value="If maxint is specified, then the expression must evaluate to a positive integer.
true"/> </eAnnotations> @@ -7461,7 +7440,7 @@ <eAnnotations source="http://www.eclipse.org/emf/2002/GenModel"> <details key="documentation" value="Invocation is an abstract class for the various actions that invoke behavior.
In addition to targeting an object, invocation actions can also invoke behavioral features on ports from where the invocation requests are routed onwards on links deriving from attached connectors. Invocation actions may also be sent to a target via a given port, either on the sending object or on another object."/> </eAnnotations> - <eOperations name="on_port" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EBoolean"> + <eOperations name="on_port_receiver" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EBoolean"> <eAnnotations source="http://www.eclipse.org/emf/2002/GenModel"> <details key="documentation" value="The onPort must be a port on the receiver object.
true"/> </eAnnotations> @@ -8622,7 +8601,7 @@ <eParameters name="diagnostics" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EDiagnosticChain"/> <eParameters name="context" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EMap"/> </eOperations> - <eOperations name="is_unmarshall" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EBoolean"> + <eOperations name="unmarshall_signal_events" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EBoolean"> <eAnnotations source="http://www.eclipse.org/emf/2002/GenModel"> <details key="documentation" value="If isUnmarshall is true, there must be exactly one trigger for events of type SignalEvent. The number of result output pins must be the same as the number of attributes of the signal. The type and ordering of each result output pin must be the same as the corresponding attribute of the signal. The multiplicity of each result output pin must be compatible with the multiplicity of the corresponding attribute.
true"/> </eAnnotations> @@ -8654,16 +8633,6 @@ <eAnnotations source="http://www.eclipse.org/emf/2002/GenModel"> <details key="documentation" value="AcceptCallAction is an accept event action representing the receipt of a synchronous call request. In addition to the normal operation parameters, the action produces an output that is needed later to supply the information to the ReplyAction necessary to return control to the caller. This action is for synchronous calls. If it is used to handle an asynchronous call, execution of the subsequent reply action will complete immediately with no effects."/> </eAnnotations> - <eAnnotations source="duplicates"> - <contents xsi:type="ecore:EOperation" name="is_unmarshall" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EBoolean"> - <eAnnotations source="http://www.eclipse.org/emf/2002/GenModel"> - <details key="documentation" value="isUnmrashall must be true for an AcceptCallAction.
isUnmarshall = true"/> - </eAnnotations> - <eAnnotations source="redefines" references="#//AcceptEventAction/is_unmarshall"/> - <eParameters name="diagnostics" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EDiagnosticChain"/> - <eParameters name="context" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EMap"/> - </contents> - </eAnnotations> <eOperations name="result_pins" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EBoolean"> <eAnnotations source="http://www.eclipse.org/emf/2002/GenModel"> <details key="documentation" value="The result pins must match the in and inout parameters of the operation specified by the trigger event in number, type, and order.
true"/> @@ -8678,6 +8647,13 @@ <eParameters name="diagnostics" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EDiagnosticChain"/> <eParameters name="context" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EMap"/> </eOperations> + <eOperations name="unmarshall" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EBoolean"> + <eAnnotations source="http://www.eclipse.org/emf/2002/GenModel"> + <details key="documentation" value="isUnmrashall must be true for an AcceptCallAction.
isUnmarshall = true"/> + </eAnnotations> + <eParameters name="diagnostics" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EDiagnosticChain"/> + <eParameters name="context" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EMap"/> + </eOperations> <eStructuralFeatures xsi:type="ecore:EReference" name="returnInformation" ordered="false" lowerBound="1" eType="#//OutputPin"> <eAnnotations source="http://www.eclipse.org/emf/2002/GenModel"> @@ -8839,7 +8815,7 @@ <eAnnotations source="http://www.eclipse.org/emf/2002/GenModel"> <details key="documentation" value="Activity parameter nodes are object nodes at the beginning and end of flows that provide a means to accept inputs to an activity and provide outputs from the activity, through the activity parameters."/> </eAnnotations> - <eOperations name="parameter" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EBoolean"> + <eOperations name="has_parameters" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EBoolean"> <eAnnotations source="http://www.eclipse.org/emf/2002/GenModel"> <details key="documentation" value="Activity parameter nodes must have parameters from the containing activity.
true"/> </eAnnotations> @@ -9164,7 +9140,7 @@ <eParameters name="diagnostics" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EDiagnosticChain"/> <eParameters name="context" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EMap"/> </eOperations> - <eOperations name="body_output" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EBoolean"> + <eOperations name="body_output_pins" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EBoolean"> <eAnnotations source="http://www.eclipse.org/emf/2002/GenModel"> <details key="documentation" value="The bodyOutput pins are output pins on actions in the body of the clause.
true"/> </eAnnotations> @@ -9219,7 +9195,7 @@ <eParameters name="diagnostics" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EDiagnosticChain"/> <eParameters name="context" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EMap"/> </eOperations> - <eOperations name="body_output" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EBoolean"> + <eOperations name="body_output_pins" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EBoolean"> <eAnnotations source="http://www.eclipse.org/emf/2002/GenModel"> <details key="documentation" value="The bodyOutput pins are output pins on actions in the body of the loop node.
true"/> </eAnnotations> @@ -9563,7 +9539,7 @@ <eAnnotations source="http://www.eclipse.org/emf/2002/GenModel"> <details key="documentation" value="A protocol transition (transition as specialized in the ProtocolStateMachines package) specifies a legal transition for an operation. Transitions of protocol state machines have the following information: a pre condition (guard), on trigger, and a post condition. Every protocol transition is associated to zero or one operation (referred BehavioralFeature) that belongs to the context classifier of the protocol state machine.



The protocol transition specifies that the associated (referred) operation can be called for an instance in the origin state under the initial condition (guard), and that at the end of the transition, the destination state will be reached under the final condition (post).

"/> </eAnnotations> - <eOperations name="belongs_to_psm" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EBoolean"> + <eOperations name="belongs_psm" eType="ecore:EDataType http://www.eclipse.org/emf/2002/Ecore#//EBoolean"> <eAnnotations source="http://www.eclipse.org/emf/2002/GenModel"> <details key="documentation" value="A protocol transition always belongs to a protocol state machine.
container.belongsToPSM()"/> </eAnnotations> |