Output Pin (Pin)
General UML Guidelines
![[bullet]](images/bullet.gif)
Activities
![[bullet]](images/bullet.gif)
Object Nodes
![[bullet]](images/bullet.gif)
Output Pin (Pin)
Output Pin (Pin)
General UML Guidelines
![[bullet]](images/bullet.gif)
Activities
![[bullet]](images/bullet.gif)
Object Nodes
![[bullet]](images/bullet.gif)
Output Pin (Pin)
A pin provides values to actions and accept result values from them. A pin is an object node for inputs and outputs to actions.
An output pin is a pin that holds output values produced by an action.
PropertiesThe pinKind must be 'outputPin'
The name of the item.
A keyword is a lightweight variant of a stereotype to extend the semantics of a model element. As opposite of stereotypes, keywords does not have do be defined in a profile.
If several keywords are given, they should be separated by commas.
A stereotype defines how a model element may be extended, and enables the use of platform or domain specific terminology or notation in place of, or in addition to, the ones used for the extended metaclass.
Stereotypes should be given in the format 'profile::stererotype'. Stereotypes should be separated by commas.
A textual description of the element.
Activity or
Actor or
Artifact or
Association or
Class or
Collaboration or
Communication Path or
Component or
Data Type or
Deployment Specification or
Device or
Enumeration or
Execution Environment or
Extension or
Information Item or
Interaction or
Interface or
Node or
Opaque Behavior or
Primitive Type or
Protocol or
Protocol State Machine or
Signal or
State Machine or
Stereotype or
Use Case.
The type of the element.
Specifies the lower and upper bound of the multiplicity interval.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
Tells whether the pins provide data to the actions, or just controls when it executes it.
Tells whether the type of the object node is to be treated as control.
Indicates whether it is possible to further specialize an item. If the value is true, then it is not possible to further specialize the item.
For a multivalued multiplicity, this attribute specifies whether the values in an instantiation of this element are sequentially ordered.
For a multivalued multiplicity, this attributes specifies whether the values in an instantiation of this element are unique.
Tells whether and how the tokens in the object node are ordered for selection to traverse edges outgoing from the object node.
The maximum number of tokens allowed in the node. Objects cannot flow into the node if the upper bound is reached.
Selects tokens for outgoing edges.
ParentAn element of one of the following kinds:
Accept Call Action (Action)
A constraint is a condition or restriction expressed in natural language text or in a machine readable language for the purpose of declaring some of the semantics of an element.
A constraint is a condition or restriction expressed in natural language text or in a machine readable language for the purpose of declaring some of the semantics of an element.
An action is a named element that is the fundamental unit of executable functionality.
The execution of an action represents some transformation or processing in the modeled system, be it a computer system or otherwise.
An action represents a single step within an activity, that is, one that is not further decomposed within the activity.
An action has pre- and post-conditions.
A accept event action is an action that waits for the occurrence of an event meeting specified conditions.
An accept call action 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 reply action 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.
Accept Event Action (Action)
A constraint is a condition or restriction expressed in natural language text or in a machine readable language for the purpose of declaring some of the semantics of an element.
An action is a named element that is the fundamental unit of executable functionality.
The execution of an action represents some transformation or processing in the modeled system, be it a computer system or otherwise.
An action represents a single step within an activity, that is, one that is not further decomposed within the activity.
An action has pre- and post-conditions.
A accept event action is an action that waits for the occurrence of an event meeting specified conditions.
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Add Structural Feature Value Action (Action)
An action is a named element that is the fundamental unit of executable functionality.
The execution of an action represents some transformation or processing in the modeled system, be it a computer system or otherwise.
An action represents a single step within an activity, that is, one that is not further decomposed within the activity.
An action has pre- and post-conditions.
A read structural feature action is a structural feature action that retrieves the values of a structural feature.
A read structural feature action is a structural feature action that retrieves the values of a structural feature.
A constraint is a condition or restriction expressed in natural language text or in a machine readable language for the purpose of declaring some of the semantics of an element.
An add structural feature value action is a write structural feature action for adding values to a structural feature.
Add Variable Value Action (Action)
An action is a named element that is the fundamental unit of executable functionality.
The execution of an action represents some transformation or processing in the modeled system, be it a computer system or otherwise.
An action represents a single step within an activity, that is, one that is not further decomposed within the activity.
An action has pre- and post-conditions.
A remove variable value action is a write variable action that removes values from variables.
WriteVariableAction is an abstract class for variable actions that change variable values.
A constraint is a condition or restriction expressed in natural language text or in a machine readable language for the purpose of declaring some of the semantics of an element.
An add variable value action is a write variable action for adding values to a variable.
Broadcast Signal Action (Action)
An action is a named element that is the fundamental unit of executable functionality.
The execution of an action represents some transformation or processing in the modeled system, be it a computer system or otherwise.
An action represents a single step within an activity, that is, one that is not further decomposed within the activity.
An action has pre- and post-conditions.
InvocationAction 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.
A constraint is a condition or restriction expressed in natural language text or in a machine readable language for the purpose of declaring some of the semantics of an element.
A broadcast signal action is an action that transmits a signal instance to all the potential target objects in the system, which may cause the firing of a state machine transitions or the execution of associated activities of a target object. The argument values are available to the execution of associated behaviors. The requestor continues execution immediately after the signals are sent out. It does not wait for receipt. Any reply messages are ignored and are not transmitted to the requestor.
Call Behavior Action (Action)
A constraint is a condition or restriction expressed in natural language text or in a machine readable language for the purpose of declaring some of the semantics of an element.
An action is a named element that is the fundamental unit of executable functionality.
The execution of an action represents some transformation or processing in the modeled system, be it a computer system or otherwise.
An action represents a single step within an activity, that is, one that is not further decomposed within the activity.
An action has pre- and post-conditions.
InvocationAction 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.
CallAction is an abstract class for actions that invoke behavior and receive return values.
A call behavior action is a call action that invokes a behavior directly rather than invoking a behavioral feature that, in turn, results in the invocation of that behavior. The argument values of the action are available to the execution of the invoked behavior. For synchronous calls the execution of the call behavior action waits until the execution of the invoked behavior completes and a result is returned on its output pin. The action completes immediately without a result, if the call is asynchronous. In particular, the invoked behavior may be an activity.
Call Operation Action (Action)
A constraint is a condition or restriction expressed in natural language text or in a machine readable language for the purpose of declaring some of the semantics of an element.
An action is a named element that is the fundamental unit of executable functionality.
The execution of an action represents some transformation or processing in the modeled system, be it a computer system or otherwise.
An action represents a single step within an activity, that is, one that is not further decomposed within the activity.
An action has pre- and post-conditions.
InvocationAction 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.
CallAction is an abstract class for actions that invoke behavior and receive return values.
A call operation action is an action that transmits an operation call request to the target object, where it may cause the invocation of associated behavior. The argument values of the action are available to the execution of the invoked behavior. If the action is marked synchronous, the execution of the call operation action waits until the execution of the invoked behavior completes and a reply transmission is returned to the caller; otherwise execution of the action is complete when the invocation of the operation is established and the execution of the invoked operation proceeds concurrently with the execution of the calling behavior. Any values returned as part of the reply transmission are put on the result output pins of the call operation action. Upon receipt of the reply transmission, execution of the call operation action is complete.
Clear Association Action (Action)
A constraint is a condition or restriction expressed in natural language text or in a machine readable language for the purpose of declaring some of the semantics of an element.
An action is a named element that is the fundamental unit of executable functionality.
The execution of an action represents some transformation or processing in the modeled system, be it a computer system or otherwise.
An action represents a single step within an activity, that is, one that is not further decomposed within the activity.
An action has pre- and post-conditions.
A clear association action is an action that destroys all links of an association in which a particular object participates.
Clear Structural Feature Action (Action)
An action is a named element that is the fundamental unit of executable functionality.
The execution of an action represents some transformation or processing in the modeled system, be it a computer system or otherwise.
An action represents a single step within an activity, that is, one that is not further decomposed within the activity.
An action has pre- and post-conditions.
A read structural feature action is a structural feature action that retrieves the values of a structural feature.
A constraint is a condition or restriction expressed in natural language text or in a machine readable language for the purpose of declaring some of the semantics of an element.
A clear structural feature action is a structural feature action that removes all values of a structural feature.
Clear Variable Action (Action)
A constraint is a condition or restriction expressed in natural language text or in a machine readable language for the purpose of declaring some of the semantics of an element.
An action is a named element that is the fundamental unit of executable functionality.
The execution of an action represents some transformation or processing in the modeled system, be it a computer system or otherwise.
An action represents a single step within an activity, that is, one that is not further decomposed within the activity.
An action has pre- and post-conditions.
A remove variable value action is a write variable action that removes values from variables.
A clear variable action is a variable action that removes all values of a variable.
Conditional Node (Action)
A constraint is a condition or restriction expressed in natural language text or in a machine readable language for the purpose of declaring some of the semantics of an element.
An action is a named element that is the fundamental unit of executable functionality.
The execution of an action represents some transformation or processing in the modeled system, be it a computer system or otherwise.
An action represents a single step within an activity, that is, one that is not further decomposed within the activity.
An action has pre- and post-conditions.
A structured activity node is an executable activity node that may have an expansion into subordinate nodes as an activity group. The subordinate nodes must belong to only one structured activity node, although they may be nested. Because of the concurrent nature of the execution of actions within and across activities, it can be difficult to guarantee the consistent access and modification of object memory. In order to avoid race conditions or other concurrency-related problems, it is sometimes necessary to isolate the effects of a group of actions from the effects of actions outside the group. This may be indicated by setting the mustIsolate attribute to true on a structured activity node. If a structured activity node is "isolated," then any object used by an action within the node cannot be accessed by any action outside the node until the structured activity node as a whole completes. Any concurrent actions that would result in accessing such objects are required to have their execution deferred until the completion of the node.
A constraint is a condition or restriction expressed in natural language text or in a machine readable language for the purpose of declaring some of the semantics of an element.
A conditional node is a structured activity node that represents an exclusive choice among some number of alternatives.
Create Link Action (Action)
An action is a named element that is the fundamental unit of executable functionality.
The execution of an action represents some transformation or processing in the modeled system, be it a computer system or otherwise.
An action represents a single step within an activity, that is, one that is not further decomposed within the activity.
An action has pre- and post-conditions.
A read link action is a link action that navigates across associations to retrieve objects on one end.
WriteLinkAction is an abstract class for link actions that create and destroy links.
A constraint is a condition or restriction expressed in natural language text or in a machine readable language for the purpose of declaring some of the semantics of an element.
A create link action is a write link action for creating links.
Create Link Object Action (Action)
An action is a named element that is the fundamental unit of executable functionality.
The execution of an action represents some transformation or processing in the modeled system, be it a computer system or otherwise.
An action represents a single step within an activity, that is, one that is not further decomposed within the activity.
An action has pre- and post-conditions.
A read link action is a link action that navigates across associations to retrieve objects on one end.
WriteLinkAction is an abstract class for link actions that create and destroy links.
A constraint is a condition or restriction expressed in natural language text or in a machine readable language for the purpose of declaring some of the semantics of an element.
A create link object action creates a link object.
Create Object Action (Action)
A constraint is a condition or restriction expressed in natural language text or in a machine readable language for the purpose of declaring some of the semantics of an element.
An action is a named element that is the fundamental unit of executable functionality.
The execution of an action represents some transformation or processing in the modeled system, be it a computer system or otherwise.
An action represents a single step within an activity, that is, one that is not further decomposed within the activity.
An action has pre- and post-conditions.
A create object action is an action that creates an object that conforms to a statically specified classifier and puts it on an output pin at runtime.
Destroy Link Action (Action)
An action is a named element that is the fundamental unit of executable functionality.
The execution of an action represents some transformation or processing in the modeled system, be it a computer system or otherwise.
An action represents a single step within an activity, that is, one that is not further decomposed within the activity.
An action has pre- and post-conditions.
A read link action is a link action that navigates across associations to retrieve objects on one end.
WriteLinkAction is an abstract class for link actions that create and destroy links.
A constraint is a condition or restriction expressed in natural language text or in a machine readable language for the purpose of declaring some of the semantics of an element.
A destroy link action is a write link action that destroys links and link objects.
Destroy Object Action (Action)
A constraint is a condition or restriction expressed in natural language text or in a machine readable language for the purpose of declaring some of the semantics of an element.
An action is a named element that is the fundamental unit of executable functionality.
The execution of an action represents some transformation or processing in the modeled system, be it a computer system or otherwise.
An action represents a single step within an activity, that is, one that is not further decomposed within the activity.
An action has pre- and post-conditions.
A destroy object action is an action that destroys objects.
Expansion Region (Action)
A constraint is a condition or restriction expressed in natural language text or in a machine readable language for the purpose of declaring some of the semantics of an element.
An action is a named element that is the fundamental unit of executable functionality.
The execution of an action represents some transformation or processing in the modeled system, be it a computer system or otherwise.
An action represents a single step within an activity, that is, one that is not further decomposed within the activity.
An action has pre- and post-conditions.
A structured activity node is an executable activity node that may have an expansion into subordinate nodes as an activity group. The subordinate nodes must belong to only one structured activity node, although they may be nested. Because of the concurrent nature of the execution of actions within and across activities, it can be difficult to guarantee the consistent access and modification of object memory. In order to avoid race conditions or other concurrency-related problems, it is sometimes necessary to isolate the effects of a group of actions from the effects of actions outside the group. This may be indicated by setting the mustIsolate attribute to true on a structured activity node. If a structured activity node is "isolated," then any object used by an action within the node cannot be accessed by any action outside the node until the structured activity node as a whole completes. Any concurrent actions that would result in accessing such objects are required to have their execution deferred until the completion of the node.
A constraint is a condition or restriction expressed in natural language text or in a machine readable language for the purpose of declaring some of the semantics of an element.
An expansion region is a structured activity region that executes multiple times corresponding to elements of an input collection.
Loop Node (Action)
A constraint is a condition or restriction expressed in natural language text or in a machine readable language for the purpose of declaring some of the semantics of an element.
An action is a named element that is the fundamental unit of executable functionality.
The execution of an action represents some transformation or processing in the modeled system, be it a computer system or otherwise.
An action represents a single step within an activity, that is, one that is not further decomposed within the activity.
An action has pre- and post-conditions.
A structured activity node is an executable activity node that may have an expansion into subordinate nodes as an activity group. The subordinate nodes must belong to only one structured activity node, although they may be nested. Because of the concurrent nature of the execution of actions within and across activities, it can be difficult to guarantee the consistent access and modification of object memory. In order to avoid race conditions or other concurrency-related problems, it is sometimes necessary to isolate the effects of a group of actions from the effects of actions outside the group. This may be indicated by setting the mustIsolate attribute to true on a structured activity node. If a structured activity node is "isolated," then any object used by an action within the node cannot be accessed by any action outside the node until the structured activity node as a whole completes. Any concurrent actions that would result in accessing such objects are required to have their execution deferred until the completion of the node.
A constraint is a condition or restriction expressed in natural language text or in a machine readable language for the purpose of declaring some of the semantics of an element.
A loop node is a structured activity node that represents a loop with setup, test, and body sections.
Opaque Action (Action)
A constraint is a condition or restriction expressed in natural language text or in a machine readable language for the purpose of declaring some of the semantics of an element.
An action is a named element that is the fundamental unit of executable functionality.
The execution of an action represents some transformation or processing in the modeled system, be it a computer system or otherwise.
An action represents a single step within an activity, that is, one that is not further decomposed within the activity.
An action has pre- and post-conditions.
An opaque action is an action with implementation-specific semantics.
Raise Exception Action (Action)
A constraint is a condition or restriction expressed in natural language text or in a machine readable language for the purpose of declaring some of the semantics of an element.
An action is a named element that is the fundamental unit of executable functionality.
The execution of an action represents some transformation or processing in the modeled system, be it a computer system or otherwise.
An action represents a single step within an activity, that is, one that is not further decomposed within the activity.
An action has pre- and post-conditions.
A raise exception action is an action that causes an exception to occur. The input value becomes the exception object.
Read Extent Action (Action)
A constraint is a condition or restriction expressed in natural language text or in a machine readable language for the purpose of declaring some of the semantics of an element.
An action is a named element that is the fundamental unit of executable functionality.
The execution of an action represents some transformation or processing in the modeled system, be it a computer system or otherwise.
An action represents a single step within an activity, that is, one that is not further decomposed within the activity.
An action has pre- and post-conditions.
A read extent action is an action that retrieves the current instances of a classifier.
Read Is Classified Object Action (Action)
A constraint is a condition or restriction expressed in natural language text or in a machine readable language for the purpose of declaring some of the semantics of an element.
An action is a named element that is the fundamental unit of executable functionality.
The execution of an action represents some transformation or processing in the modeled system, be it a computer system or otherwise.
An action represents a single step within an activity, that is, one that is not further decomposed within the activity.
An action has pre- and post-conditions.
A read is classified object action is an action that determines whether a runtime object is classified by a given classifier.
Read Link Action (Action)
An action is a named element that is the fundamental unit of executable functionality.
The execution of an action represents some transformation or processing in the modeled system, be it a computer system or otherwise.
An action represents a single step within an activity, that is, one that is not further decomposed within the activity.
An action has pre- and post-conditions.
A read link action is a link action that navigates across associations to retrieve objects on one end.
A constraint is a condition or restriction expressed in natural language text or in a machine readable language for the purpose of declaring some of the semantics of an element.
A read link action is a link action that navigates across associations to retrieve objects on one end.
Read Link Object End Action (Action)
A constraint is a condition or restriction expressed in natural language text or in a machine readable language for the purpose of declaring some of the semantics of an element.
An action is a named element that is the fundamental unit of executable functionality.
The execution of an action represents some transformation or processing in the modeled system, be it a computer system or otherwise.
An action represents a single step within an activity, that is, one that is not further decomposed within the activity.
An action has pre- and post-conditions.
A read link object end action is an action that retrieves an end object from a link object.
Read Link Object End Qualifier Action (Action)
A constraint is a condition or restriction expressed in natural language text or in a machine readable language for the purpose of declaring some of the semantics of an element.
An action is a named element that is the fundamental unit of executable functionality.
The execution of an action represents some transformation or processing in the modeled system, be it a computer system or otherwise.
An action represents a single step within an activity, that is, one that is not further decomposed within the activity.
An action has pre- and post-conditions.
A read link object end qualifier action is an action that retrieves a qualifier end value from a link object.
Read Self Action (Action)
A constraint is a condition or restriction expressed in natural language text or in a machine readable language for the purpose of declaring some of the semantics of an element.
An action is a named element that is the fundamental unit of executable functionality.
The execution of an action represents some transformation or processing in the modeled system, be it a computer system or otherwise.
An action represents a single step within an activity, that is, one that is not further decomposed within the activity.
An action has pre- and post-conditions.
A read self action is an action that retrieves the host object of an action.
The following features are supported:
Read Structural Feature Action (Action)
An action is a named element that is the fundamental unit of executable functionality.
The execution of an action represents some transformation or processing in the modeled system, be it a computer system or otherwise.
An action represents a single step within an activity, that is, one that is not further decomposed within the activity.
An action has pre- and post-conditions.
A read structural feature action is a structural feature action that retrieves the values of a structural feature.
A constraint is a condition or restriction expressed in natural language text or in a machine readable language for the purpose of declaring some of the semantics of an element.
A read structural feature action is a structural feature action that retrieves the values of a structural feature.
Read Variable Action (Action)
A constraint is a condition or restriction expressed in natural language text or in a machine readable language for the purpose of declaring some of the semantics of an element.
An action is a named element that is the fundamental unit of executable functionality.
The execution of an action represents some transformation or processing in the modeled system, be it a computer system or otherwise.
An action represents a single step within an activity, that is, one that is not further decomposed within the activity.
An action has pre- and post-conditions.
A remove variable value action is a write variable action that removes values from variables.
A read variable action is a variable action that retrieves the values of a variable.
Reclassify Object Action (Action)
A constraint is a condition or restriction expressed in natural language text or in a machine readable language for the purpose of declaring some of the semantics of an element.
An action is a named element that is the fundamental unit of executable functionality.
The execution of an action represents some transformation or processing in the modeled system, be it a computer system or otherwise.
An action represents a single step within an activity, that is, one that is not further decomposed within the activity.
An action has pre- and post-conditions.
A reclassify object action is an action that changes which classifiers classify an object.
Reduce Action (Action)
A constraint is a condition or restriction expressed in natural language text or in a machine readable language for the purpose of declaring some of the semantics of an element.
An action is a named element that is the fundamental unit of executable functionality.
The execution of an action represents some transformation or processing in the modeled system, be it a computer system or otherwise.
An action represents a single step within an activity, that is, one that is not further decomposed within the activity.
An action has pre- and post-conditions.
A reduce action is an action that reduces a collection to a single value by combining the elements of the collection.
Remove Structural Feature Value Action (Action)
An action is a named element that is the fundamental unit of executable functionality.
The execution of an action represents some transformation or processing in the modeled system, be it a computer system or otherwise.
An action represents a single step within an activity, that is, one that is not further decomposed within the activity.
An action has pre- and post-conditions.
A read structural feature action is a structural feature action that retrieves the values of a structural feature.
A read structural feature action is a structural feature action that retrieves the values of a structural feature.
A constraint is a condition or restriction expressed in natural language text or in a machine readable language for the purpose of declaring some of the semantics of an element.
A remove structural feature value action is a write structural feature action that removes values from structural features.
Remove Variable Value Action (Action)
An action is a named element that is the fundamental unit of executable functionality.
The execution of an action represents some transformation or processing in the modeled system, be it a computer system or otherwise.
An action represents a single step within an activity, that is, one that is not further decomposed within the activity.
An action has pre- and post-conditions.
A remove variable value action is a write variable action that removes values from variables.
WriteVariableAction is an abstract class for variable actions that change variable values.
A constraint is a condition or restriction expressed in natural language text or in a machine readable language for the purpose of declaring some of the semantics of an element.
A remove variable value action is a write variable action that removes values from variables.
Reply Action (Action)
A constraint is a condition or restriction expressed in natural language text or in a machine readable language for the purpose of declaring some of the semantics of an element.
An action is a named element that is the fundamental unit of executable functionality.
The execution of an action represents some transformation or processing in the modeled system, be it a computer system or otherwise.
An action represents a single step within an activity, that is, one that is not further decomposed within the activity.
An action has pre- and post-conditions.
A reply action is an action that accepts a set of return values and a value containing return information produced by a previous accept call action. The reply action returns the values to the caller of the previous call, completing execution of the call.
Send Object Action (Action)
An action is a named element that is the fundamental unit of executable functionality.
The execution of an action represents some transformation or processing in the modeled system, be it a computer system or otherwise.
An action represents a single step within an activity, that is, one that is not further decomposed within the activity.
An action has pre- and post-conditions.
InvocationAction 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.
A constraint is a condition or restriction expressed in natural language text or in a machine readable language for the purpose of declaring some of the semantics of an element.
A send object action is an action that transmits an object to the target object, where it may invoke behavior such as the firing of state machine transitions or the execution of an activity. The value of the object is available to the execution of invoked behaviors. The requestor continues execution immediately. Any reply message is ignored and is not transmitted to the requestor.
Send Signal Action (Action)
An action is a named element that is the fundamental unit of executable functionality.
The execution of an action represents some transformation or processing in the modeled system, be it a computer system or otherwise.
An action represents a single step within an activity, that is, one that is not further decomposed within the activity.
An action has pre- and post-conditions.
InvocationAction 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.
A constraint is a condition or restriction expressed in natural language text or in a machine readable language for the purpose of declaring some of the semantics of an element.
A send signal action is an action that creates a signal instance from its inputs, and transmits it to the target object, where it may cause the firing of a state machine transition or the execution of an activity. The argument values are available to the execution of associated behaviors. The requestor continues execution immediately. Any reply message is ignored and is not transmitted to the requestor. If the input is already a signal instance, use a send object action.
Sequence Node (Action)
A constraint is a condition or restriction expressed in natural language text or in a machine readable language for the purpose of declaring some of the semantics of an element.
An action is a named element that is the fundamental unit of executable functionality.
The execution of an action represents some transformation or processing in the modeled system, be it a computer system or otherwise.
An action represents a single step within an activity, that is, one that is not further decomposed within the activity.
An action has pre- and post-conditions.
A structured activity node is an executable activity node that may have an expansion into subordinate nodes as an activity group. The subordinate nodes must belong to only one structured activity node, although they may be nested. Because of the concurrent nature of the execution of actions within and across activities, it can be difficult to guarantee the consistent access and modification of object memory. In order to avoid race conditions or other concurrency-related problems, it is sometimes necessary to isolate the effects of a group of actions from the effects of actions outside the group. This may be indicated by setting the mustIsolate attribute to true on a structured activity node. If a structured activity node is "isolated," then any object used by an action within the node cannot be accessed by any action outside the node until the structured activity node as a whole completes. Any concurrent actions that would result in accessing such objects are required to have their execution deferred until the completion of the node.
A constraint is a condition or restriction expressed in natural language text or in a machine readable language for the purpose of declaring some of the semantics of an element.
A sequence node is a structured activity node that executes its actions in order.
Start Classifier Behavior Action (Action)
A constraint is a condition or restriction expressed in natural language text or in a machine readable language for the purpose of declaring some of the semantics of an element.
An action is a named element that is the fundamental unit of executable functionality.
The execution of an action represents some transformation or processing in the modeled system, be it a computer system or otherwise.
An action represents a single step within an activity, that is, one that is not further decomposed within the activity.
An action has pre- and post-conditions.
A start classifier behavior action is an action that starts the classifier behavior of the input.
Start Object Behavior Action (Action)
A constraint is a condition or restriction expressed in natural language text or in a machine readable language for the purpose of declaring some of the semantics of an element.
An action is a named element that is the fundamental unit of executable functionality.
The execution of an action represents some transformation or processing in the modeled system, be it a computer system or otherwise.
An action represents a single step within an activity, that is, one that is not further decomposed within the activity.
An action has pre- and post-conditions.
InvocationAction 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.
CallAction is an abstract class for actions that invoke behavior and receive return values.
StartObjectBehaviorAction is an action that starts the execution either of a directly instantiated behavior or of the classifier behavior of an object. Argument values may be supplied for the input parameters of the behavior. If the behavior is invoked synchronously, then output values may be obtained for output
Structured Activity Node (Action)
A constraint is a condition or restriction expressed in natural language text or in a machine readable language for the purpose of declaring some of the semantics of an element.
An action is a named element that is the fundamental unit of executable functionality.
The execution of an action represents some transformation or processing in the modeled system, be it a computer system or otherwise.
An action represents a single step within an activity, that is, one that is not further decomposed within the activity.
An action has pre- and post-conditions.
A structured activity node is an executable activity node that may have an expansion into subordinate nodes as an activity group. The subordinate nodes must belong to only one structured activity node, although they may be nested. Because of the concurrent nature of the execution of actions within and across activities, it can be difficult to guarantee the consistent access and modification of object memory. In order to avoid race conditions or other concurrency-related problems, it is sometimes necessary to isolate the effects of a group of actions from the effects of actions outside the group. This may be indicated by setting the mustIsolate attribute to true on a structured activity node. If a structured activity node is "isolated," then any object used by an action within the node cannot be accessed by any action outside the node until the structured activity node as a whole completes. Any concurrent actions that would result in accessing such objects are required to have their execution deferred until the completion of the node.
Structured Activity Node (Structured Activity Node)
A structured activity node is an executable activity node that may have an expansion into subordinate nodes as an activity group. The subordinate nodes must belong to only one structured activity node, although they may be nested.
Because of the concurrent nature of the execution of actions within and across activities, it can be difficult to guarantee the consistent access and modification of object memory.
In order to avoid race conditions or other concurrency-related problems, it is sometimes necessary to isolate the effects of a group of actions from the effects of actions outside the group. This may be indicated by setting the mustIsolate attribute to true on a structured activity node.
If a structured activity node is "isolated," then any object used by an action within the node cannot be accessed by any action outside the node until the structured activity node as a whole completes. Any concurrent actions that would result in accessing such objects are required to have their execution deferred until the completion of the node.
Test Identity Action (Action)
A constraint is a condition or restriction expressed in natural language text or in a machine readable language for the purpose of declaring some of the semantics of an element.
An action is a named element that is the fundamental unit of executable functionality.
The execution of an action represents some transformation or processing in the modeled system, be it a computer system or otherwise.
An action represents a single step within an activity, that is, one that is not further decomposed within the activity.
An action has pre- and post-conditions.
A test identity action is an action that tests if two values are identical objects.
Unmarshall Action (Action)
A constraint is a condition or restriction expressed in natural language text or in a machine readable language for the purpose of declaring some of the semantics of an element.
An action is a named element that is the fundamental unit of executable functionality.
The execution of an action represents some transformation or processing in the modeled system, be it a computer system or otherwise.
An action represents a single step within an activity, that is, one that is not further decomposed within the activity.
An action has pre- and post-conditions.
An unmarshall action is an action that breaks an object of a known type into outputs each of which is equal to a value from a structural feature of the object.
Value Specification Action (Action)
A constraint is a condition or restriction expressed in natural language text or in a machine readable language for the purpose of declaring some of the semantics of an element.
An action is a named element that is the fundamental unit of executable functionality.
The execution of an action represents some transformation or processing in the modeled system, be it a computer system or otherwise.
An action represents a single step within an activity, that is, one that is not further decomposed within the activity.
An action has pre- and post-conditions.
A value specification action is an action that evaluates a value specification.
Outgoing
Control Flow (Control Flow)
Object Flow (Object Flow)
Incoming
Control Flow (Control Flow)
Object Flow (Object Flow)
Relations
Abstraction (Abstraction)
An abstraction is a relationship that relates two elements or sets of elements that represent the same concept at different levels of abstraction or from different viewpoints.
Dependency (Dependency)
A dependency is a relationship that signifies that a single or a set of model elements requires other model elements for their specification or implementation.
This means that the complete semantics of the depending elements is either semantically or structurally dependent on the definition of the supplier element(s).
Information Flow (Information Flow)
An information flow specifies that one or more information items circulates from its sources to its targets.
Informationflows require some kind of information channel for transmitting information items from the source to the destination. An information channel is represented in various ways depending on the nature of its sources and targets. It may berepresented by connectors, links, associations, or even dependencies.
For example, if the source and destination are partsin some composite structure such as a collaboration, then the information channel is likely to be represented by aconnector between them. Or, if the source and target are objects (which are a kind of instance specification), they may berepresented by a link that joins the two, and so on.
Realization (Realization)
Realization is a specialized abstraction relationship between two sets of model elements, one representing a specification (the supplier) and the other represents an implementation of the latter (the client). Realization can be used to model stepwise refinement, optimizations, transformations, templates, model synthesis, framework composition, etc.
Substitution (Substitution)
A substitution is a relationship between two classifiers signifies that the substituting classifier complies with the contract specified by the contract classifier. This implies that instances of the substituting classifier are runtime substitutable where instances of the contract classifier are expected.
Usage (Usage)
A usage is a relationship in which one element requires another element (or set of elements) for its full implementation or operation. A usage is a dependency in which the client requires the presence of the supplier.
Usage
Abstraction (Abstraction)
Control Flow (Control Flow)
Dependency (Dependency)
Information Flow (Information Flow)
Object Flow (Object Flow)
Realization (Realization)
Substitution (Substitution)
Usage (Usage)
Control Flow (Control Flow)
Object Flow (Object Flow)Model Guidelines generated by MetaModelAgent version 4.2.0.007
| Tuesday, 14 February 2017 15:17 |
![Show help for an Item Guidelines Page [help_web]](images/help_web.png)