Class UML 2.4.1::MessageOccurrenceSpecification
Description:
A message occurrence specification pecifies the occurrence of message events,
such as sending and receiving of signals or invoking or receiving of operation
calls. A message occurrence specification is a kind of message end. Messages
are generated either by synchronous operation calls or asynchronous signal
sends. They are received by the execution of corresponding accept event
actions.
Direct Superclasses: OccurrenceSpecification,
MessageEndDirect Subclasses: DestructionOccurrenceSpecificationClass Precedence List: MessageOccurrenceSpecification,
OccurrenceSpecification,
InteractionFragment,
MessageEnd,
NamedElement,
ElementProperties:
covered :
Lifeline (1 1); -- source
OccurrenceSpecification toAfter :
GeneralOrdering (0 *); -- source
OccurrenceSpecification toBefore :
GeneralOrdering (0 *); -- source
OccurrenceSpecification enclosingInteraction :
Interaction (0 1); -- source
InteractionFragment enclosingOperand :
InteractionOperand (0 1); -- source
InteractionFragment generalOrdering :
GeneralOrdering (0 *); -- source
InteractionFragment message :
Message (0 1); -- source
MessageEnd clientDependency :
Dependency (0 *); -- source
NamedElement name : String (0 1); -- source
NamedElement nameExpression :
StringExpression (0 1); -- source
NamedElement namespace :
Namespace (0 1); -- source
NamedElementSpecifies the namespace that owns the NamedElement.
{
readonly}
Derived union with sources: (enclosingOperand, enclosingInteraction)
Subsets: Element.owner
Opposite: Namespace.ownedMember
qualifiedName : String (0 1); -- source
NamedElement visibility :
VisibilityKind (0 1); -- source
NamedElement ownedComment :
Comment (0 *); -- source
Element ownedElement :
Element (0 *); -- source
ElementThe Elements owned by this element.
{
composite,
readonly}
Derived union with sources: (ownedComment, nameExpression, generalOrdering)
Opposite: Element.owner
owner :
Element (0 1); -- source
ElementConstraints:
No additional constraints.
Operations:
No additional operations.
Send questions or comments to
[email protected].