ModelGeneral UML Guidelines
This is version 4.2.0 of the general guidelines for UML models. These guidelines describes all elements, relationships and diagrams within UML.
ModelA model captures a view of a physical system. It is an abstraction of the physical system, with a certain purpose.
This purpose determines what is to be included in the model and what is irrelevant. Thus the model completely describes those aspects of the physical system that are relevant to the purpose of the model, at the appropriate level of detail.
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.
The name of the file that holds the model.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
The name of the viewpoint that is expressed by a model (This name may refer to a profile definition).
An element of one of the following kinds:
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Model (Model)
A model captures a view of a physical system. It is an abstraction of the physical system, with a certain purpose.
This purpose determines what is to be included in the model and what is irrelevant. Thus the model completely describes those aspects of the physical system that are relevant to the purpose of the model, at the appropriate level of detail.
Package (Package)
A package is used to group elements, and provides a namespace for the grouped elements.
A package can have one or more profile applications to indicate which profiles have been applied.
Profile (Profile)
A profile defines limited extensions to a reference metamodel with the purpose of adapting the metamodel to a specific platform or domain.
Template Parameter (Template Parameter)
A template parameter exposes a parameterable element as a formal template parameter of a template.
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Actor (Actor)
An actor specifies a role played by a user or any other system that interacts with the subject.
Artifact (Artifact)
An artifact is the specification of a physical piece of information that is used or produced by a software development process, or by deployment and operation of a system.
Examples of artifacts include model files, source files, scripts, and binary executable files, a table in a database system, a development deliverable, or a word-processing document, a mail message. An artifact is the source of a deployment to a node.
Association (Association)
An association describes a set of tuples whose values refer to typed instances. An instance of an association is called a link.
Call Event (Call Event)
A call event models the receipt by an object of a message invoking a call of an operation.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
Collaboration (Collaboration)
A collaboration defines a set of co-operating roles used collectively to illustrate a specific functionality.
A collaboration should only show the roles and attributes required to accomplish its defined task or function. Isolating the primary roles is an exercise in simplifying the structure and clarifying the behavior, and also provides for re-use. A collaboration often implements a pattern.
Communication Path (Communication Path)
A communication path is an association between two deployment targets, through which they are able to exchange signals and messages.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Constraint (Constraint)
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.
Data Type (Data Type)
A data type is a type whose instances are identified only by their value. A data type may contain attributes to support the modeling of structured data types.
Deployment Specification (Deployment Specification)
A deployment specification specifies a set of properties that determine execution parameters of a component artifact that is deployed on a node.
A deployment specification can be aimed at a specific type of container. An artifact that reifies or implements deployment specification properties is a deployment descriptor.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Enumeration (Enumeration)
An enumeration is a data type whose values are enumerated in the model as enumeration literals.
Enumeration Literal (Enumeration Literal)
An enumeration literal is a user-defined data value for an enumeration.
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Extension (Extension)
An extension is used to indicate that the properties of a metaclass are extended through a stereotype, and gives the ability to flexibly add (and later remove) stereotypes to classes.
Information Item (Information Item)
An information item is an abstraction of all kinds of information that can be exchanged between objects. It is a kind of
classifier intended for representing information in a very abstract way, one which cannot be instantiated.
Instance Specification (Instance Specification)
An instance specification is a model element that represents an instance in a modeled system.
An instance specification has the capability of being a deployment target in a deployment relationship, in the case that it is an instance of a node.
It is also has the capability of being a deployed artifact, if it is an instance of an artifact.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interface (Interface)
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
Model (Model)
A model captures a view of a physical system. It is an abstraction of the physical system, with a certain purpose.
This purpose determines what is to be included in the model and what is irrelevant. Thus the model completely describes those aspects of the physical system that are relevant to the purpose of the model, at the appropriate level of detail.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Package (Package)
A package is used to group elements, and provides a namespace for the grouped elements.
A package can have one or more profile applications to indicate which profiles have been applied.
Primitive Type (Primitive Type)
A primitive type defines a predefined data type, without any relevant substructure (i.e., it has no parts in the context of UML). A primitive datatype may have an algebra and operations defined outside of UML, for example, mathematically.
Profile (Profile)
A profile defines limited extensions to a reference metamodel with the purpose of adapting the metamodel to a specific platform or domain.
Protocol (Protocol)
Only available together with the Real-Time Extension of RSA.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
Signal (Signal)
A signal is a specification of send request instances communicated between objects. The receiving object handles the received request instances as specified by its receptions. The data carried by a send request (which was passed to it by the send invocation occurrence that caused that request) are represented as attributes of the signal.
A signal is defined independently of the classifiers handling the signal occurrence.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
Template Signature (Template Signature)
A template signature bundles the set of formal template parameters for a templated element.
Use Case (Use Case)
A use case is the specification of a set of actions performed by a system, which yields an observable result that is, typically, of value for one or more actors or other stakeholders of the system.
Class Diagram (Class Diagram)
A Class Diagram is a diagram that shows classes and interfaces and their relationships. However a class diagram may also show packages and all kind of classifier elements.
Component Diagram (Component Diagram)
A Component Diagram is a diagram that shows components, interfaces and artifacts and their relationships. However a component diagram may also show packages and all kind of classifier elements.
Deployment Diagram (Deployment Diagram)
A Deployment Diagram is a diagram that shows nodes and artifacts and their relationships. However a deployment diagram may also show packages and all kind of classifier elements.
Freeform Diagram (Freeform Diagram)
A Free Form diagram is a diagram in which you can make free drawings without the restriction of using UML.
Interaction Overview Diagram (Interaction Overview Diagram)
An Interaction Overview Diagram is a visual representation of a control flow of interaction..
Object Diagram (Object Diagram)
An Object Diagram is a diagram that shows instance specification, links and slots.
Use Case Diagram (Use Case Diagram)
A Use-Case Diagram is a diagram that shows actors and use cases and their relationships. However a Use-Case Diagram may also show packages and all kind of classifier elements.
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).
Element Import (Element Import)
An element import identifies an element in another package, and allows the element to be referenced using its name without a qualifier.
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.
Package Import (Package Import)
A package import is a relationship that allows the use of unqualified names to refer to package members from other namespaces.
Package Merge (Package Merge)
A package merge defines how the contents of one package are extended by the contents of another package.
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.
Templatebinding (Templatebinding)
A template binding represents a relationship between a templateable element and a template. A template binding specifies the substitutions of actual parameters for the formal parameters of the template.
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.
Abstraction (Abstraction)Dependency (Dependency)Element Import (Element Import)Information Flow (Information Flow)
Manifestation (Manifestation)Package Import (Package Import)Package Merge (Package Merge)Realization (Realization)Substitution (Substitution)Usage (Usage) PackageA package is used to group elements, and provides a namespace for the grouped elements.
A package can have one or more profile applications to indicate which profiles have been applied.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
An element of one of the following kinds:
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Model (Model)
A model captures a view of a physical system. It is an abstraction of the physical system, with a certain purpose.
This purpose determines what is to be included in the model and what is irrelevant. Thus the model completely describes those aspects of the physical system that are relevant to the purpose of the model, at the appropriate level of detail.
Package (Package)
A package is used to group elements, and provides a namespace for the grouped elements.
A package can have one or more profile applications to indicate which profiles have been applied.
Profile (Profile)
A profile defines limited extensions to a reference metamodel with the purpose of adapting the metamodel to a specific platform or domain.
Template Parameter (Template Parameter)
A template parameter exposes a parameterable element as a formal template parameter of a template.
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Actor (Actor)
An actor specifies a role played by a user or any other system that interacts with the subject.
Artifact (Artifact)
An artifact is the specification of a physical piece of information that is used or produced by a software development process, or by deployment and operation of a system.
Examples of artifacts include model files, source files, scripts, and binary executable files, a table in a database system, a development deliverable, or a word-processing document, a mail message. An artifact is the source of a deployment to a node.
Association (Association)
An association describes a set of tuples whose values refer to typed instances. An instance of an association is called a link.
Call Event (Call Event)
A call event models the receipt by an object of a message invoking a call of an operation.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
Collaboration (Collaboration)
A collaboration defines a set of co-operating roles used collectively to illustrate a specific functionality.
A collaboration should only show the roles and attributes required to accomplish its defined task or function. Isolating the primary roles is an exercise in simplifying the structure and clarifying the behavior, and also provides for re-use. A collaboration often implements a pattern.
Communication Path (Communication Path)
A communication path is an association between two deployment targets, through which they are able to exchange signals and messages.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Constraint (Constraint)
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.
Data Type (Data Type)
A data type is a type whose instances are identified only by their value. A data type may contain attributes to support the modeling of structured data types.
Deployment Specification (Deployment Specification)
A deployment specification specifies a set of properties that determine execution parameters of a component artifact that is deployed on a node.
A deployment specification can be aimed at a specific type of container. An artifact that reifies or implements deployment specification properties is a deployment descriptor.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Enumeration (Enumeration)
An enumeration is a data type whose values are enumerated in the model as enumeration literals.
Enumeration Literal (Enumeration Literal)
An enumeration literal is a user-defined data value for an enumeration.
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Extension (Extension)
An extension is used to indicate that the properties of a metaclass are extended through a stereotype, and gives the ability to flexibly add (and later remove) stereotypes to classes.
Information Item (Information Item)
An information item is an abstraction of all kinds of information that can be exchanged between objects. It is a kind of
classifier intended for representing information in a very abstract way, one which cannot be instantiated.
Instance Specification (Instance Specification)
An instance specification is a model element that represents an instance in a modeled system.
An instance specification has the capability of being a deployment target in a deployment relationship, in the case that it is an instance of a node.
It is also has the capability of being a deployed artifact, if it is an instance of an artifact.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interface (Interface)
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
Model (Model)
A model captures a view of a physical system. It is an abstraction of the physical system, with a certain purpose.
This purpose determines what is to be included in the model and what is irrelevant. Thus the model completely describes those aspects of the physical system that are relevant to the purpose of the model, at the appropriate level of detail.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Package (Package)
A package is used to group elements, and provides a namespace for the grouped elements.
A package can have one or more profile applications to indicate which profiles have been applied.
Primitive Type (Primitive Type)
A primitive type defines a predefined data type, without any relevant substructure (i.e., it has no parts in the context of UML). A primitive datatype may have an algebra and operations defined outside of UML, for example, mathematically.
Profile (Profile)
A profile defines limited extensions to a reference metamodel with the purpose of adapting the metamodel to a specific platform or domain.
Protocol (Protocol)
Only available together with the Real-Time Extension of RSA.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
Signal (Signal)
A signal is a specification of send request instances communicated between objects. The receiving object handles the received request instances as specified by its receptions. The data carried by a send request (which was passed to it by the send invocation occurrence that caused that request) are represented as attributes of the signal.
A signal is defined independently of the classifiers handling the signal occurrence.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
Template Signature (Template Signature)
A template signature bundles the set of formal template parameters for a templated element.
Use Case (Use Case)
A use case is the specification of a set of actions performed by a system, which yields an observable result that is, typically, of value for one or more actors or other stakeholders of the system.
Class Diagram (Class Diagram)
A Class Diagram is a diagram that shows classes and interfaces and their relationships. However a class diagram may also show packages and all kind of classifier elements.
Component Diagram (Component Diagram)
A Component Diagram is a diagram that shows components, interfaces and artifacts and their relationships. However a component diagram may also show packages and all kind of classifier elements.
Deployment Diagram (Deployment Diagram)
A Deployment Diagram is a diagram that shows nodes and artifacts and their relationships. However a deployment diagram may also show packages and all kind of classifier elements.
Freeform Diagram (Freeform Diagram)
A Free Form diagram is a diagram in which you can make free drawings without the restriction of using UML.
Interaction Overview Diagram (Interaction Overview Diagram)
An Interaction Overview Diagram is a visual representation of a control flow of interaction..
Object Diagram (Object Diagram)
An Object Diagram is a diagram that shows instance specification, links and slots.
Use Case Diagram (Use Case Diagram)
A Use-Case Diagram is a diagram that shows actors and use cases and their relationships. However a Use-Case Diagram may also show packages and all kind of classifier elements.
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).
Element Import (Element Import)
An element import identifies an element in another package, and allows the element to be referenced using its name without a qualifier.
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.
Package Import (Package Import)
A package import is a relationship that allows the use of unqualified names to refer to package members from other namespaces.
Package Merge (Package Merge)
A package merge defines how the contents of one package are extended by the contents of another package.
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.
Templatebinding (Templatebinding)
A template binding represents a relationship between a templateable element and a template. A template binding specifies the substitutions of actual parameters for the formal parameters of the template.
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.
Abstraction (Abstraction)Dependency (Dependency)Element Import (Element Import)Information Flow (Information Flow)Manifestation (Manifestation)Package Import (Package Import)Package Merge (Package Merge)Realization (Realization)Substitution (Substitution)Usage (Usage) ProfileA profile defines limited extensions to a reference metamodel with the purpose of adapting the metamodel to a specific platform or domain.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
An element of one of the following kinds:
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Model (Model)
A model captures a view of a physical system. It is an abstraction of the physical system, with a certain purpose.
This purpose determines what is to be included in the model and what is irrelevant. Thus the model completely describes those aspects of the physical system that are relevant to the purpose of the model, at the appropriate level of detail.
Package (Package)
A package is used to group elements, and provides a namespace for the grouped elements.
A package can have one or more profile applications to indicate which profiles have been applied.
Profile (Profile)
A profile defines limited extensions to a reference metamodel with the purpose of adapting the metamodel to a specific platform or domain.
Template Parameter (Template Parameter)
A template parameter exposes a parameterable element as a formal template parameter of a template.
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Actor (Actor)
An actor specifies a role played by a user or any other system that interacts with the subject.
Artifact (Artifact)
An artifact is the specification of a physical piece of information that is used or produced by a software development process, or by deployment and operation of a system.
Examples of artifacts include model files, source files, scripts, and binary executable files, a table in a database system, a development deliverable, or a word-processing document, a mail message. An artifact is the source of a deployment to a node.
Association (Association)
An association describes a set of tuples whose values refer to typed instances. An instance of an association is called a link.
Call Event (Call Event)
A call event models the receipt by an object of a message invoking a call of an operation.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
Collaboration (Collaboration)
A collaboration defines a set of co-operating roles used collectively to illustrate a specific functionality.
A collaboration should only show the roles and attributes required to accomplish its defined task or function. Isolating the primary roles is an exercise in simplifying the structure and clarifying the behavior, and also provides for re-use. A collaboration often implements a pattern.
Communication Path (Communication Path)
A communication path is an association between two deployment targets, through which they are able to exchange signals and messages.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Constraint (Constraint)
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.
Data Type (Data Type)
A data type is a type whose instances are identified only by their value. A data type may contain attributes to support the modeling of structured data types.
Deployment Specification (Deployment Specification)
A deployment specification specifies a set of properties that determine execution parameters of a component artifact that is deployed on a node.
A deployment specification can be aimed at a specific type of container. An artifact that reifies or implements deployment specification properties is a deployment descriptor.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Enumeration (Enumeration)
An enumeration is a data type whose values are enumerated in the model as enumeration literals.
Enumeration Literal (Enumeration Literal)
An enumeration literal is a user-defined data value for an enumeration.
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Extension (Extension)
An extension is used to indicate that the properties of a metaclass are extended through a stereotype, and gives the ability to flexibly add (and later remove) stereotypes to classes.
Information Item (Information Item)
An information item is an abstraction of all kinds of information that can be exchanged between objects. It is a kind of
classifier intended for representing information in a very abstract way, one which cannot be instantiated.
Instance Specification (Instance Specification)
An instance specification is a model element that represents an instance in a modeled system.
An instance specification has the capability of being a deployment target in a deployment relationship, in the case that it is an instance of a node.
It is also has the capability of being a deployed artifact, if it is an instance of an artifact.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interface (Interface)
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
Model (Model)
A model captures a view of a physical system. It is an abstraction of the physical system, with a certain purpose.
This purpose determines what is to be included in the model and what is irrelevant. Thus the model completely describes those aspects of the physical system that are relevant to the purpose of the model, at the appropriate level of detail.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Package (Package)
A package is used to group elements, and provides a namespace for the grouped elements.
A package can have one or more profile applications to indicate which profiles have been applied.
Primitive Type (Primitive Type)
A primitive type defines a predefined data type, without any relevant substructure (i.e., it has no parts in the context of UML). A primitive datatype may have an algebra and operations defined outside of UML, for example, mathematically.
Profile (Profile)
A profile defines limited extensions to a reference metamodel with the purpose of adapting the metamodel to a specific platform or domain.
Protocol (Protocol)
Only available together with the Real-Time Extension of RSA.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
Signal (Signal)
A signal is a specification of send request instances communicated between objects. The receiving object handles the received request instances as specified by its receptions. The data carried by a send request (which was passed to it by the send invocation occurrence that caused that request) are represented as attributes of the signal.
A signal is defined independently of the classifiers handling the signal occurrence.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
Template Signature (Template Signature)
A template signature bundles the set of formal template parameters for a templated element.
Use Case (Use Case)
A use case is the specification of a set of actions performed by a system, which yields an observable result that is, typically, of value for one or more actors or other stakeholders of the system.
Class Diagram (Class Diagram)
A Class Diagram is a diagram that shows classes and interfaces and their relationships. However a class diagram may also show packages and all kind of classifier elements.
Component Diagram (Component Diagram)
A Component Diagram is a diagram that shows components, interfaces and artifacts and their relationships. However a component diagram may also show packages and all kind of classifier elements.
Deployment Diagram (Deployment Diagram)
A Deployment Diagram is a diagram that shows nodes and artifacts and their relationships. However a deployment diagram may also show packages and all kind of classifier elements.
Freeform Diagram (Freeform Diagram)
A Free Form diagram is a diagram in which you can make free drawings without the restriction of using UML.
Interaction Overview Diagram (Interaction Overview Diagram)
An Interaction Overview Diagram is a visual representation of a control flow of interaction..
Object Diagram (Object Diagram)
An Object Diagram is a diagram that shows instance specification, links and slots.
Use Case Diagram (Use Case Diagram)
A Use-Case Diagram is a diagram that shows actors and use cases and their relationships. However a Use-Case Diagram may also show packages and all kind of classifier elements.
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).
Element Import (Element Import)
An element import identifies an element in another package, and allows the element to be referenced using its name without a qualifier.
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.
Package Import (Package Import)
A package import is a relationship that allows the use of unqualified names to refer to package members from other namespaces.
Package Merge (Package Merge)
A package merge defines how the contents of one package are extended by the contents of another package.
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.
Templatebinding (Templatebinding)
A template binding represents a relationship between a templateable element and a template. A template binding specifies the substitutions of actual parameters for the formal parameters of the template.
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.
Abstraction (Abstraction)Dependency (Dependency)Element Import (Element Import)Information Flow (Information Flow)Manifestation (Manifestation)Package Import (Package Import)Package Merge (Package Merge)Realization (Realization)Substitution (Substitution)Usage (Usage) ActorAn actor specifies a role played by a user or any other system that interacts with the subject.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
If true, the Classifier does not provide a complete declaration and can typically not be instantiated.
An abstract classifier is intended to be used by other classifiers e.g. as the target of general metarelationships or generalization relationships.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interface (Interface)
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
Model (Model)
A model captures a view of a physical system. It is an abstraction of the physical system, with a certain purpose.
This purpose determines what is to be included in the model and what is irrelevant. Thus the model completely describes those aspects of the physical system that are relevant to the purpose of the model, at the appropriate level of detail.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Package (Package)
A package is used to group elements, and provides a namespace for the grouped elements.
A package can have one or more profile applications to indicate which profiles have been applied.
Profile (Profile)
A profile defines limited extensions to a reference metamodel with the purpose of adapting the metamodel to a specific platform or domain.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
Template Parameter (Template Parameter)
A template parameter exposes a parameterable element as a formal template parameter of a template.
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Association End (Association End)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An association End is a property that has a reference to an association.
Collaboration Use (Collaboration Use)
A collaboration use represents one particular use of a collaboration to explain the relationships between the properties of a classifier.
A collaboration use shows how the pattern described by a collaboration is applied in a given context, by binding specific entities from that context to the roles of the collaboration. Depending on the context, these entities could be structural features of a classifier, instance specifications, or even roles in some containing collaboration. There may be multiple occurrences of a given collaboration within a classifier, each involving a different set of roles and connectors.
A given role or connector may be involved in multiple occurrences of the same or different collaborations. Associated dependencies map features of the collaboration type to features in the classifier. These dependencies indicate which role in the classifier plays which role in the collaboration.
Constraint (Constraint)
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.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Template Signature (Template Signature)
A template signature bundles the set of formal template parameters for a templated element.
Trigger (Trigger)
A trigger relates an event to a behavior that may affect an instance of the classifier. A trigger specification may be qualified by the port on which the event occurred.
Use Case (Use Case)
A use case is the specification of a set of actions performed by a system, which yields an observable result that is, typically, of value for one or more actors or other stakeholders of the system.
Class Diagram (Class Diagram)
A Class Diagram is a diagram that shows classes and interfaces and their relationships. However a class diagram may also show packages and all kind of classifier elements.
Component Diagram (Component Diagram)
A Component Diagram is a diagram that shows components, interfaces and artifacts and their relationships. However a component diagram may also show packages and all kind of classifier elements.
Deployment Diagram (Deployment Diagram)
A Deployment Diagram is a diagram that shows nodes and artifacts and their relationships. However a deployment diagram may also show packages and all kind of classifier elements.
Freeform Diagram (Freeform Diagram)
A Free Form diagram is a diagram in which you can make free drawings without the restriction of using UML.
Interaction Overview Diagram (Interaction Overview Diagram)
An Interaction Overview Diagram is a visual representation of a control flow of interaction..
Object Diagram (Object Diagram)
An Object Diagram is a diagram that shows instance specification, links and slots.
Use Case Diagram (Use Case Diagram)
A Use-Case Diagram is a diagram that shows actors and use cases and their relationships. However a Use-Case Diagram may also show packages and all kind of classifier elements.
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.
Component Realization (Component Realization)
The realization concept is specialized to (optionally) define the classifiers that realize the contract offered by a component in terms of its provided and required interfaces.
The component forms an abstraction from these various
classifiers.
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).
Element Import (Element Import)
An element import identifies an element in another package, and allows the element to be referenced using its name without a qualifier.
Generalization (Generalization)
A generalization is a taxonomic relationship between a more general classifier and a more specific classifier. Each instance of the specific classifier is also an indirect instance of the general classifier. Thus, the specific classifier inherits the features of the more general classifier.
A generalization relates a specific classifier to a more general classifier, and is owned by the specific classifier.
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.
Interface Realization (Interface Realization)
An interface realization is a specialized realization relationship between a classifier and an interface. This relationship signifies that the realizing classifier conforms to the contract specified by the interface.
Package Import (Package Import)
A package import is a relationship that allows the use of unqualified names to refer to package members from other namespaces.
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.
Templatebinding (Templatebinding)
A template binding represents a relationship between a templateable element and a template. A template binding specifies the substitutions of actual parameters for the formal parameters of the template.
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.
Action Input Pin (Pin)
Activity Parameter Node (Object Node)Association End (Association End)
Attribute (Attribute)
Central Buffer (Object Node)
Data Store Node (Object Node)
Expansion Node (Object Node)
Input Pin (Pin)
Output Pin (Pin)
Parameter (Parameter)
Port (Port)
Value Pin (Pin)Abstraction (Abstraction)Component Realization (Component Realization)Dependency (Dependency)Element Import (Element Import)Generalization (Generalization)Information Flow (Information Flow)Manifestation (Manifestation)Realization (Realization)Substitution (Substitution)Usage (Usage) ArtifactAn artifact is the specification of a physical piece of information that is used or produced by a software development process, or by deployment and operation of a system.
Examples of artifacts include model files, source files, scripts, and binary executable files, a table in a database system, a development deliverable, or a word-processing document, a mail message. An artifact is the source of a deployment to a node.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
If true, the Classifier does not provide a complete declaration and can typically not be instantiated.
An abstract classifier is intended to be used by other classifiers e.g. as the target of general metarelationships or generalization relationships.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Artifact (Artifact)
An artifact is the specification of a physical piece of information that is used or produced by a software development process, or by deployment and operation of a system.
Examples of artifacts include model files, source files, scripts, and binary executable files, a table in a database system, a development deliverable, or a word-processing document, a mail message. An artifact is the source of a deployment to a node.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Deployment Specification (Deployment Specification)
A deployment specification specifies a set of properties that determine execution parameters of a component artifact that is deployed on a node.
A deployment specification can be aimed at a specific type of container. An artifact that reifies or implements deployment specification properties is a deployment descriptor.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interface (Interface)
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
Model (Model)
A model captures a view of a physical system. It is an abstraction of the physical system, with a certain purpose.
This purpose determines what is to be included in the model and what is irrelevant. Thus the model completely describes those aspects of the physical system that are relevant to the purpose of the model, at the appropriate level of detail.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Package (Package)
A package is used to group elements, and provides a namespace for the grouped elements.
A package can have one or more profile applications to indicate which profiles have been applied.
Profile (Profile)
A profile defines limited extensions to a reference metamodel with the purpose of adapting the metamodel to a specific platform or domain.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
Template Parameter (Template Parameter)
A template parameter exposes a parameterable element as a formal template parameter of a template.
Artifact (Artifact)
An artifact is the specification of a physical piece of information that is used or produced by a software development process, or by deployment and operation of a system.
Examples of artifacts include model files, source files, scripts, and binary executable files, a table in a database system, a development deliverable, or a word-processing document, a mail message. An artifact is the source of a deployment to a node.
Association End (Association End)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An association End is a property that has a reference to an association.
Attribute (Attribute)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An attribute is a property that has no reference to an association.
Collaboration Use (Collaboration Use)
A collaboration use represents one particular use of a collaboration to explain the relationships between the properties of a classifier.
A collaboration use shows how the pattern described by a collaboration is applied in a given context, by binding specific entities from that context to the roles of the collaboration. Depending on the context, these entities could be structural features of a classifier, instance specifications, or even roles in some containing collaboration. There may be multiple occurrences of a given collaboration within a classifier, each involving a different set of roles and connectors.
A given role or connector may be involved in multiple occurrences of the same or different collaborations. Associated dependencies map features of the collaboration type to features in the classifier. These dependencies indicate which role in the classifier plays which role in the collaboration.
Constraint (Constraint)
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.
Deployment Specification (Deployment Specification)
A deployment specification specifies a set of properties that determine execution parameters of a component artifact that is deployed on a node.
A deployment specification can be aimed at a specific type of container. An artifact that reifies or implements deployment specification properties is a deployment descriptor.
Operation (Operation)
An operation is a behavioral feature of a classifier that specifies the name, type, parameters, and constraints for invoking an associated behavior. An operation may invoke both the execution of method behaviors as well as other behavioral responses.
Port (Port)
A port is a property of a classifier that specifies a distinct interaction point between that classifier and its environment or between the (behavior of the) classifier and its internal parts.
Ports are connected to properties of the classifier by connectors through which requests can be made to invoke the behavioral features of a classifier.
A Port may specify the services a classifier provides (offers) to its environment as well as the services that a classifier expects (requires) of its environment. A port has an associated protocol state machine.
Template Signature (Template Signature)
A template signature bundles the set of formal template parameters for a templated element.
Use Case (Use Case)
A use case is the specification of a set of actions performed by a system, which yields an observable result that is, typically, of value for one or more actors or other stakeholders of the system.
Class Diagram (Class Diagram)
A Class Diagram is a diagram that shows classes and interfaces and their relationships. However a class diagram may also show packages and all kind of classifier elements.
Component Diagram (Component Diagram)
A Component Diagram is a diagram that shows components, interfaces and artifacts and their relationships. However a component diagram may also show packages and all kind of classifier elements.
Deployment Diagram (Deployment Diagram)
A Deployment Diagram is a diagram that shows nodes and artifacts and their relationships. However a deployment diagram may also show packages and all kind of classifier elements.
Freeform Diagram (Freeform Diagram)
A Free Form diagram is a diagram in which you can make free drawings without the restriction of using UML.
Interaction Overview Diagram (Interaction Overview Diagram)
An Interaction Overview Diagram is a visual representation of a control flow of interaction..
Object Diagram (Object Diagram)
An Object Diagram is a diagram that shows instance specification, links and slots.
Use Case Diagram (Use Case Diagram)
A Use-Case Diagram is a diagram that shows actors and use cases and their relationships. However a Use-Case Diagram may also show packages and all kind of classifier elements.
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.
Component Realization (Component Realization)
The realization concept is specialized to (optionally) define the classifiers that realize the contract offered by a component in terms of its provided and required interfaces.
The component forms an abstraction from these various
classifiers.
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).
Element Import (Element Import)
An element import identifies an element in another package, and allows the element to be referenced using its name without a qualifier.
Generalization (Generalization)
A generalization is a taxonomic relationship between a more general classifier and a more specific classifier. Each instance of the specific classifier is also an indirect instance of the general classifier. Thus, the specific classifier inherits the features of the more general classifier.
A generalization relates a specific classifier to a more general classifier, and is owned by the specific classifier.
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.
Manifestation (Manifestation)
A manifestation is the concrete physical rendering of one or more model elements by an artifact.
Package Import (Package Import)
A package import is a relationship that allows the use of unqualified names to refer to package members from other namespaces.
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.
Templatebinding (Templatebinding)
A template binding represents a relationship between a templateable element and a template. A template binding specifies the substitutions of actual parameters for the formal parameters of the template.
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.
Action Input Pin (Pin)Activity Parameter Node (Object Node)Association End (Association End)Attribute (Attribute)Central Buffer (Object Node)Data Store Node (Object Node)Expansion Node (Object Node)Input Pin (Pin)Output Pin (Pin)Parameter (Parameter)Port (Port)Value Pin (Pin)Abstraction (Abstraction)Component Realization (Component Realization)Dependency (Dependency)
Deployment (Deployment)Element Import (Element Import)Generalization (Generalization)Information Flow (Information Flow)Manifestation (Manifestation)Realization (Realization)Substitution (Substitution)Usage (Usage) AssociationAn association describes a set of tuples whose values refer to typed instances. An instance of an association is called a link.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
If true, the Classifier does not provide a complete declaration and can typically not be instantiated.
An abstract classifier is intended to be used by other classifiers e.g. as the target of general metarelationships or generalization relationships.
Specifies whether the association is derived from other model elements such as other associations or constraints.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interface (Interface)
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
Model (Model)
A model captures a view of a physical system. It is an abstraction of the physical system, with a certain purpose.
This purpose determines what is to be included in the model and what is irrelevant. Thus the model completely describes those aspects of the physical system that are relevant to the purpose of the model, at the appropriate level of detail.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Package (Package)
A package is used to group elements, and provides a namespace for the grouped elements.
A package can have one or more profile applications to indicate which profiles have been applied.
Profile (Profile)
A profile defines limited extensions to a reference metamodel with the purpose of adapting the metamodel to a specific platform or domain.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
Template Parameter (Template Parameter)
A template parameter exposes a parameterable element as a formal template parameter of a template.
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Association End (Association End)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An association End is a property that has a reference to an association.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
Collaboration Use (Collaboration Use)
A collaboration use represents one particular use of a collaboration to explain the relationships between the properties of a classifier.
A collaboration use shows how the pattern described by a collaboration is applied in a given context, by binding specific entities from that context to the roles of the collaboration. Depending on the context, these entities could be structural features of a classifier, instance specifications, or even roles in some containing collaboration. There may be multiple occurrences of a given collaboration within a classifier, each involving a different set of roles and connectors.
A given role or connector may be involved in multiple occurrences of the same or different collaborations. Associated dependencies map features of the collaboration type to features in the classifier. These dependencies indicate which role in the classifier plays which role in the collaboration.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Constraint (Constraint)
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.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
Template Signature (Template Signature)
A template signature bundles the set of formal template parameters for a templated element.
Use Case (Use Case)
A use case is the specification of a set of actions performed by a system, which yields an observable result that is, typically, of value for one or more actors or other stakeholders of the system.
Class Diagram (Class Diagram)
A Class Diagram is a diagram that shows classes and interfaces and their relationships. However a class diagram may also show packages and all kind of classifier elements.
Component Diagram (Component Diagram)
A Component Diagram is a diagram that shows components, interfaces and artifacts and their relationships. However a component diagram may also show packages and all kind of classifier elements.
Deployment Diagram (Deployment Diagram)
A Deployment Diagram is a diagram that shows nodes and artifacts and their relationships. However a deployment diagram may also show packages and all kind of classifier elements.
Freeform Diagram (Freeform Diagram)
A Free Form diagram is a diagram in which you can make free drawings without the restriction of using UML.
Interaction Overview Diagram (Interaction Overview Diagram)
An Interaction Overview Diagram is a visual representation of a control flow of interaction..
Object Diagram (Object Diagram)
An Object Diagram is a diagram that shows instance specification, links and slots.
Use Case Diagram (Use Case Diagram)
A Use-Case Diagram is a diagram that shows actors and use cases and their relationships. However a Use-Case Diagram may also show packages and all kind of classifier elements.
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.
Component Realization (Component Realization)
The realization concept is specialized to (optionally) define the classifiers that realize the contract offered by a component in terms of its provided and required interfaces.
The component forms an abstraction from these various
classifiers.
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).
Element Import (Element Import)
An element import identifies an element in another package, and allows the element to be referenced using its name without a qualifier.
Generalization (Generalization)
A generalization is a taxonomic relationship between a more general classifier and a more specific classifier. Each instance of the specific classifier is also an indirect instance of the general classifier. Thus, the specific classifier inherits the features of the more general classifier.
A generalization relates a specific classifier to a more general classifier, and is owned by the specific classifier.
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.
Package Import (Package Import)
A package import is a relationship that allows the use of unqualified names to refer to package members from other namespaces.
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.
Templatebinding (Templatebinding)
A template binding represents a relationship between a templateable element and a template. A template binding specifies the substitutions of actual parameters for the formal parameters of the template.
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.
Action Input Pin (Pin)Activity Parameter Node (Object Node)Association End (Association End)Attribute (Attribute)Central Buffer (Object Node)Data Store Node (Object Node)Expansion Node (Object Node)Input Pin (Pin)Output Pin (Pin)Parameter (Parameter)Port (Port)Value Pin (Pin)Association End (Association End)Abstraction (Abstraction)Component Realization (Component Realization)Dependency (Dependency)Element Import (Element Import)Generalization (Generalization)Information Flow (Information Flow)Manifestation (Manifestation)Realization (Realization)Substitution (Substitution)Usage (Usage)
Connector (Connector) ClassA class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
If true, the Classifier does not provide a complete declaration and can typically not be instantiated.
An abstract classifier is intended to be used by other classifiers e.g. as the target of general metarelationships or generalization relationships.
Determines whether an object specified by this classifier is active or not. If true, then the owning classifier is referred to as an active classifier. If false, then such a classifier is referred to as a passive classifier.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Association (Association)
An association describes a set of tuples whose values refer to typed instances. An instance of an association is called a link.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
Communication Path (Communication Path)
A communication path is an association between two deployment targets, through which they are able to exchange signals and messages.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Extension (Extension)
An extension is used to indicate that the properties of a metaclass are extended through a stereotype, and gives the ability to flexibly add (and later remove) stereotypes to classes.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interface (Interface)
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
Model (Model)
A model captures a view of a physical system. It is an abstraction of the physical system, with a certain purpose.
This purpose determines what is to be included in the model and what is irrelevant. Thus the model completely describes those aspects of the physical system that are relevant to the purpose of the model, at the appropriate level of detail.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Package (Package)
A package is used to group elements, and provides a namespace for the grouped elements.
A package can have one or more profile applications to indicate which profiles have been applied.
Profile (Profile)
A profile defines limited extensions to a reference metamodel with the purpose of adapting the metamodel to a specific platform or domain.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
Template Parameter (Template Parameter)
A template parameter exposes a parameterable element as a formal template parameter of a template.
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Actor (Actor)
An actor specifies a role played by a user or any other system that interacts with the subject.
Artifact (Artifact)
An artifact is the specification of a physical piece of information that is used or produced by a software development process, or by deployment and operation of a system.
Examples of artifacts include model files, source files, scripts, and binary executable files, a table in a database system, a development deliverable, or a word-processing document, a mail message. An artifact is the source of a deployment to a node.
Association (Association)
An association describes a set of tuples whose values refer to typed instances. An instance of an association is called a link.
Association End (Association End)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An association End is a property that has a reference to an association.
Attribute (Attribute)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An attribute is a property that has no reference to an association.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
Collaboration (Collaboration)
A collaboration defines a set of co-operating roles used collectively to illustrate a specific functionality.
A collaboration should only show the roles and attributes required to accomplish its defined task or function. Isolating the primary roles is an exercise in simplifying the structure and clarifying the behavior, and also provides for re-use. A collaboration often implements a pattern.
Collaboration Use (Collaboration Use)
A collaboration use represents one particular use of a collaboration to explain the relationships between the properties of a classifier.
A collaboration use shows how the pattern described by a collaboration is applied in a given context, by binding specific entities from that context to the roles of the collaboration. Depending on the context, these entities could be structural features of a classifier, instance specifications, or even roles in some containing collaboration. There may be multiple occurrences of a given collaboration within a classifier, each involving a different set of roles and connectors.
A given role or connector may be involved in multiple occurrences of the same or different collaborations. Associated dependencies map features of the collaboration type to features in the classifier. These dependencies indicate which role in the classifier plays which role in the collaboration.
Communication Path (Communication Path)
A communication path is an association between two deployment targets, through which they are able to exchange signals and messages.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Connector (Connector)
Specifies a link that enables communication between two or more instances. This link may be an instance of anassociation, or it may represent the possibility of the instances being able to communicate because their identitiesare known by virtue of being passed in as parameters, held in variables or slots, or because the communicatinginstances are the same instance.
The link may be realized by something as simple as a pointer or by something ascomplex as a network connection. In contrast to associations, which specify links between any instance of theassociated classifiers, connectors specify links between instances playing the connected parts only.
Constraint (Constraint)
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.
Data Type (Data Type)
A data type is a type whose instances are identified only by their value. A data type may contain attributes to support the modeling of structured data types.
Deployment Specification (Deployment Specification)
A deployment specification specifies a set of properties that determine execution parameters of a component artifact that is deployed on a node.
A deployment specification can be aimed at a specific type of container. An artifact that reifies or implements deployment specification properties is a deployment descriptor.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Enumeration (Enumeration)
An enumeration is a data type whose values are enumerated in the model as enumeration literals.
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Extension (Extension)
An extension is used to indicate that the properties of a metaclass are extended through a stereotype, and gives the ability to flexibly add (and later remove) stereotypes to classes.
Information Item (Information Item)
An information item is an abstraction of all kinds of information that can be exchanged between objects. It is a kind of
classifier intended for representing information in a very abstract way, one which cannot be instantiated.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interface (Interface)
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Operation (Operation)
An operation is a behavioral feature of a classifier that specifies the name, type, parameters, and constraints for invoking an associated behavior. An operation may invoke both the execution of method behaviors as well as other behavioral responses.
Port (Port)
A port is a property of a classifier that specifies a distinct interaction point between that classifier and its environment or between the (behavior of the) classifier and its internal parts.
Ports are connected to properties of the classifier by connectors through which requests can be made to invoke the behavioral features of a classifier.
A Port may specify the services a classifier provides (offers) to its environment as well as the services that a classifier expects (requires) of its environment. A port has an associated protocol state machine.
Primitive Type (Primitive Type)
A primitive type defines a predefined data type, without any relevant substructure (i.e., it has no parts in the context of UML). A primitive datatype may have an algebra and operations defined outside of UML, for example, mathematically.
Protocol (Protocol)
Only available together with the Real-Time Extension of RSA.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
Reception (Reception)
A reception is a declaration stating that a classifier is prepared to react to the receipt of a signal. A reception designates a signal and specifies the expected behavioral response.
The details of handling a signal are specified by the behavior associated with the reception or the classifier itself.
Signal (Signal)
A signal is a specification of send request instances communicated between objects. The receiving object handles the received request instances as specified by its receptions. The data carried by a send request (which was passed to it by the send invocation occurrence that caused that request) are represented as attributes of the signal.
A signal is defined independently of the classifiers handling the signal occurrence.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
Template Signature (Template Signature)
A template signature bundles the set of formal template parameters for a templated element.
Trigger (Trigger)
A trigger relates an event to a behavior that may affect an instance of the classifier. A trigger specification may be qualified by the port on which the event occurred.
Use Case (Use Case)
A use case is the specification of a set of actions performed by a system, which yields an observable result that is, typically, of value for one or more actors or other stakeholders of the system.
Class Diagram (Class Diagram)
A Class Diagram is a diagram that shows classes and interfaces and their relationships. However a class diagram may also show packages and all kind of classifier elements.
Component Diagram (Component Diagram)
A Component Diagram is a diagram that shows components, interfaces and artifacts and their relationships. However a component diagram may also show packages and all kind of classifier elements.
Deployment Diagram (Deployment Diagram)
A Deployment Diagram is a diagram that shows nodes and artifacts and their relationships. However a deployment diagram may also show packages and all kind of classifier elements.
Freeform Diagram (Freeform Diagram)
A Free Form diagram is a diagram in which you can make free drawings without the restriction of using UML.
Interaction Overview Diagram (Interaction Overview Diagram)
An Interaction Overview Diagram is a visual representation of a control flow of interaction..
Object Diagram (Object Diagram)
An Object Diagram is a diagram that shows instance specification, links and slots.
Structure Diagram (Structure Diagram)
A Structure Diagram is a diagram that shows the static structure of an element.
Use Case Diagram (Use Case Diagram)
A Use-Case Diagram is a diagram that shows actors and use cases and their relationships. However a Use-Case Diagram may also show packages and all kind of classifier elements.
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.
Component Realization (Component Realization)
The realization concept is specialized to (optionally) define the classifiers that realize the contract offered by a component in terms of its provided and required interfaces.
The component forms an abstraction from these various
classifiers.
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).
Element Import (Element Import)
An element import identifies an element in another package, and allows the element to be referenced using its name without a qualifier.
Generalization (Generalization)
A generalization is a taxonomic relationship between a more general classifier and a more specific classifier. Each instance of the specific classifier is also an indirect instance of the general classifier. Thus, the specific classifier inherits the features of the more general classifier.
A generalization relates a specific classifier to a more general classifier, and is owned by the specific classifier.
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.
Interface Realization (Interface Realization)
An interface realization is a specialized realization relationship between a classifier and an interface. This relationship signifies that the realizing classifier conforms to the contract specified by the interface.
Package Import (Package Import)
A package import is a relationship that allows the use of unqualified names to refer to package members from other namespaces.
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.
Templatebinding (Templatebinding)
A template binding represents a relationship between a templateable element and a template. A template binding specifies the substitutions of actual parameters for the formal parameters of the template.
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.
Action Input Pin (Pin)Activity Parameter Node (Object Node)Association End (Association End)Attribute (Attribute)Central Buffer (Object Node)Data Store Node (Object Node)Expansion Node (Object Node)Input Pin (Pin)Output Pin (Pin)Parameter (Parameter)Port (Port)Value Pin (Pin)Abstraction (Abstraction)Component Realization (Component Realization)Dependency (Dependency)Element Import (Element Import)Generalization (Generalization)Information Flow (Information Flow)Manifestation (Manifestation)Realization (Realization)Substitution (Substitution)Usage (Usage) CollaborationA collaboration defines a set of co-operating roles used collectively to illustrate a specific functionality.
A collaboration should only show the roles and attributes required to accomplish its defined task or function. Isolating the primary roles is an exercise in simplifying the structure and clarifying the behavior, and also provides for re-use. A collaboration often implements a pattern.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
If true, the Classifier does not provide a complete declaration and can typically not be instantiated.
An abstract classifier is intended to be used by other classifiers e.g. as the target of general metarelationships or generalization relationships.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interface (Interface)
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
Model (Model)
A model captures a view of a physical system. It is an abstraction of the physical system, with a certain purpose.
This purpose determines what is to be included in the model and what is irrelevant. Thus the model completely describes those aspects of the physical system that are relevant to the purpose of the model, at the appropriate level of detail.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Package (Package)
A package is used to group elements, and provides a namespace for the grouped elements.
A package can have one or more profile applications to indicate which profiles have been applied.
Profile (Profile)
A profile defines limited extensions to a reference metamodel with the purpose of adapting the metamodel to a specific platform or domain.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
Template Parameter (Template Parameter)
A template parameter exposes a parameterable element as a formal template parameter of a template.
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Association End (Association End)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An association End is a property that has a reference to an association.
Attribute (Attribute)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An attribute is a property that has no reference to an association.
Collaboration Use (Collaboration Use)
A collaboration use represents one particular use of a collaboration to explain the relationships between the properties of a classifier.
A collaboration use shows how the pattern described by a collaboration is applied in a given context, by binding specific entities from that context to the roles of the collaboration. Depending on the context, these entities could be structural features of a classifier, instance specifications, or even roles in some containing collaboration. There may be multiple occurrences of a given collaboration within a classifier, each involving a different set of roles and connectors.
A given role or connector may be involved in multiple occurrences of the same or different collaborations. Associated dependencies map features of the collaboration type to features in the classifier. These dependencies indicate which role in the classifier plays which role in the collaboration.
Connector (Connector)
Specifies a link that enables communication between two or more instances. This link may be an instance of anassociation, or it may represent the possibility of the instances being able to communicate because their identitiesare known by virtue of being passed in as parameters, held in variables or slots, or because the communicatinginstances are the same instance.
The link may be realized by something as simple as a pointer or by something ascomplex as a network connection. In contrast to associations, which specify links between any instance of theassociated classifiers, connectors specify links between instances playing the connected parts only.
Constraint (Constraint)
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.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Port (Port)
A port is a property of a classifier that specifies a distinct interaction point between that classifier and its environment or between the (behavior of the) classifier and its internal parts.
Ports are connected to properties of the classifier by connectors through which requests can be made to invoke the behavioral features of a classifier.
A Port may specify the services a classifier provides (offers) to its environment as well as the services that a classifier expects (requires) of its environment. A port has an associated protocol state machine.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Template Signature (Template Signature)
A template signature bundles the set of formal template parameters for a templated element.
Trigger (Trigger)
A trigger relates an event to a behavior that may affect an instance of the classifier. A trigger specification may be qualified by the port on which the event occurred.
Use Case (Use Case)
A use case is the specification of a set of actions performed by a system, which yields an observable result that is, typically, of value for one or more actors or other stakeholders of the system.
Class Diagram (Class Diagram)
A Class Diagram is a diagram that shows classes and interfaces and their relationships. However a class diagram may also show packages and all kind of classifier elements.
Component Diagram (Component Diagram)
A Component Diagram is a diagram that shows components, interfaces and artifacts and their relationships. However a component diagram may also show packages and all kind of classifier elements.
Deployment Diagram (Deployment Diagram)
A Deployment Diagram is a diagram that shows nodes and artifacts and their relationships. However a deployment diagram may also show packages and all kind of classifier elements.
Freeform Diagram (Freeform Diagram)
A Free Form diagram is a diagram in which you can make free drawings without the restriction of using UML.
Interaction Overview Diagram (Interaction Overview Diagram)
An Interaction Overview Diagram is a visual representation of a control flow of interaction..
Object Diagram (Object Diagram)
An Object Diagram is a diagram that shows instance specification, links and slots.
Use Case Diagram (Use Case Diagram)
A Use-Case Diagram is a diagram that shows actors and use cases and their relationships. However a Use-Case Diagram may also show packages and all kind of classifier elements.
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.
Component Realization (Component Realization)
The realization concept is specialized to (optionally) define the classifiers that realize the contract offered by a component in terms of its provided and required interfaces.
The component forms an abstraction from these various
classifiers.
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).
Element Import (Element Import)
An element import identifies an element in another package, and allows the element to be referenced using its name without a qualifier.
Generalization (Generalization)
A generalization is a taxonomic relationship between a more general classifier and a more specific classifier. Each instance of the specific classifier is also an indirect instance of the general classifier. Thus, the specific classifier inherits the features of the more general classifier.
A generalization relates a specific classifier to a more general classifier, and is owned by the specific classifier.
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.
Interface Realization (Interface Realization)
An interface realization is a specialized realization relationship between a classifier and an interface. This relationship signifies that the realizing classifier conforms to the contract specified by the interface.
Package Import (Package Import)
A package import is a relationship that allows the use of unqualified names to refer to package members from other namespaces.
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.
Templatebinding (Templatebinding)
A template binding represents a relationship between a templateable element and a template. A template binding specifies the substitutions of actual parameters for the formal parameters of the template.
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.
Action Input Pin (Pin)Activity Parameter Node (Object Node)Association End (Association End)Attribute (Attribute)Central Buffer (Object Node)Data Store Node (Object Node)Expansion Node (Object Node)Input Pin (Pin)Output Pin (Pin)Parameter (Parameter)Port (Port)Value Pin (Pin)Abstraction (Abstraction)Component Realization (Component Realization)Dependency (Dependency)Element Import (Element Import)Generalization (Generalization)Information Flow (Information Flow)Manifestation (Manifestation)Realization (Realization)Substitution (Substitution)Usage (Usage) ComponentA component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
If true, the Classifier does not provide a complete declaration and can typically not be instantiated.
An abstract classifier is intended to be used by other classifiers e.g. as the target of general metarelationships or generalization relationships.
Determines whether an object specified by this classifier is active or not. If true, then the owning classifier is referred to as an active classifier. If false, then such a classifier is referred to as a passive classifier.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Association (Association)
An association describes a set of tuples whose values refer to typed instances. An instance of an association is called a link.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
Communication Path (Communication Path)
A communication path is an association between two deployment targets, through which they are able to exchange signals and messages.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Extension (Extension)
An extension is used to indicate that the properties of a metaclass are extended through a stereotype, and gives the ability to flexibly add (and later remove) stereotypes to classes.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interface (Interface)
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
Model (Model)
A model captures a view of a physical system. It is an abstraction of the physical system, with a certain purpose.
This purpose determines what is to be included in the model and what is irrelevant. Thus the model completely describes those aspects of the physical system that are relevant to the purpose of the model, at the appropriate level of detail.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Package (Package)
A package is used to group elements, and provides a namespace for the grouped elements.
A package can have one or more profile applications to indicate which profiles have been applied.
Profile (Profile)
A profile defines limited extensions to a reference metamodel with the purpose of adapting the metamodel to a specific platform or domain.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
Template Parameter (Template Parameter)
A template parameter exposes a parameterable element as a formal template parameter of a template.
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Actor (Actor)
An actor specifies a role played by a user or any other system that interacts with the subject.
Artifact (Artifact)
An artifact is the specification of a physical piece of information that is used or produced by a software development process, or by deployment and operation of a system.
Examples of artifacts include model files, source files, scripts, and binary executable files, a table in a database system, a development deliverable, or a word-processing document, a mail message. An artifact is the source of a deployment to a node.
Association (Association)
An association describes a set of tuples whose values refer to typed instances. An instance of an association is called a link.
Association End (Association End)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An association End is a property that has a reference to an association.
Attribute (Attribute)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An attribute is a property that has no reference to an association.
Call Event (Call Event)
A call event models the receipt by an object of a message invoking a call of an operation.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
Collaboration (Collaboration)
A collaboration defines a set of co-operating roles used collectively to illustrate a specific functionality.
A collaboration should only show the roles and attributes required to accomplish its defined task or function. Isolating the primary roles is an exercise in simplifying the structure and clarifying the behavior, and also provides for re-use. A collaboration often implements a pattern.
Collaboration Use (Collaboration Use)
A collaboration use represents one particular use of a collaboration to explain the relationships between the properties of a classifier.
A collaboration use shows how the pattern described by a collaboration is applied in a given context, by binding specific entities from that context to the roles of the collaboration. Depending on the context, these entities could be structural features of a classifier, instance specifications, or even roles in some containing collaboration. There may be multiple occurrences of a given collaboration within a classifier, each involving a different set of roles and connectors.
A given role or connector may be involved in multiple occurrences of the same or different collaborations. Associated dependencies map features of the collaboration type to features in the classifier. These dependencies indicate which role in the classifier plays which role in the collaboration.
Communication Path (Communication Path)
A communication path is an association between two deployment targets, through which they are able to exchange signals and messages.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Connector (Connector)
Specifies a link that enables communication between two or more instances. This link may be an instance of anassociation, or it may represent the possibility of the instances being able to communicate because their identitiesare known by virtue of being passed in as parameters, held in variables or slots, or because the communicatinginstances are the same instance.
The link may be realized by something as simple as a pointer or by something ascomplex as a network connection. In contrast to associations, which specify links between any instance of theassociated classifiers, connectors specify links between instances playing the connected parts only.
Constraint (Constraint)
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.
Data Type (Data Type)
A data type is a type whose instances are identified only by their value. A data type may contain attributes to support the modeling of structured data types.
Deployment Specification (Deployment Specification)
A deployment specification specifies a set of properties that determine execution parameters of a component artifact that is deployed on a node.
A deployment specification can be aimed at a specific type of container. An artifact that reifies or implements deployment specification properties is a deployment descriptor.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Enumeration (Enumeration)
An enumeration is a data type whose values are enumerated in the model as enumeration literals.
Enumeration Literal (Enumeration Literal)
An enumeration literal is a user-defined data value for an enumeration.
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Extension (Extension)
An extension is used to indicate that the properties of a metaclass are extended through a stereotype, and gives the ability to flexibly add (and later remove) stereotypes to classes.
Information Item (Information Item)
An information item is an abstraction of all kinds of information that can be exchanged between objects. It is a kind of
classifier intended for representing information in a very abstract way, one which cannot be instantiated.
Instance Specification (Instance Specification)
An instance specification is a model element that represents an instance in a modeled system.
An instance specification has the capability of being a deployment target in a deployment relationship, in the case that it is an instance of a node.
It is also has the capability of being a deployed artifact, if it is an instance of an artifact.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interface (Interface)
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
Model (Model)
A model captures a view of a physical system. It is an abstraction of the physical system, with a certain purpose.
This purpose determines what is to be included in the model and what is irrelevant. Thus the model completely describes those aspects of the physical system that are relevant to the purpose of the model, at the appropriate level of detail.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Operation (Operation)
An operation is a behavioral feature of a classifier that specifies the name, type, parameters, and constraints for invoking an associated behavior. An operation may invoke both the execution of method behaviors as well as other behavioral responses.
Package (Package)
A package is used to group elements, and provides a namespace for the grouped elements.
A package can have one or more profile applications to indicate which profiles have been applied.
Port (Port)
A port is a property of a classifier that specifies a distinct interaction point between that classifier and its environment or between the (behavior of the) classifier and its internal parts.
Ports are connected to properties of the classifier by connectors through which requests can be made to invoke the behavioral features of a classifier.
A Port may specify the services a classifier provides (offers) to its environment as well as the services that a classifier expects (requires) of its environment. A port has an associated protocol state machine.
Primitive Type (Primitive Type)
A primitive type defines a predefined data type, without any relevant substructure (i.e., it has no parts in the context of UML). A primitive datatype may have an algebra and operations defined outside of UML, for example, mathematically.
Profile (Profile)
A profile defines limited extensions to a reference metamodel with the purpose of adapting the metamodel to a specific platform or domain.
Protocol (Protocol)
Only available together with the Real-Time Extension of RSA.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
Reception (Reception)
A reception is a declaration stating that a classifier is prepared to react to the receipt of a signal. A reception designates a signal and specifies the expected behavioral response.
The details of handling a signal are specified by the behavior associated with the reception or the classifier itself.
Signal (Signal)
A signal is a specification of send request instances communicated between objects. The receiving object handles the received request instances as specified by its receptions. The data carried by a send request (which was passed to it by the send invocation occurrence that caused that request) are represented as attributes of the signal.
A signal is defined independently of the classifiers handling the signal occurrence.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
Template Signature (Template Signature)
A template signature bundles the set of formal template parameters for a templated element.
Trigger (Trigger)
A trigger relates an event to a behavior that may affect an instance of the classifier. A trigger specification may be qualified by the port on which the event occurred.
Use Case (Use Case)
A use case is the specification of a set of actions performed by a system, which yields an observable result that is, typically, of value for one or more actors or other stakeholders of the system.
Class Diagram (Class Diagram)
A Class Diagram is a diagram that shows classes and interfaces and their relationships. However a class diagram may also show packages and all kind of classifier elements.
Component Diagram (Component Diagram)
A Component Diagram is a diagram that shows components, interfaces and artifacts and their relationships. However a component diagram may also show packages and all kind of classifier elements.
Deployment Diagram (Deployment Diagram)
A Deployment Diagram is a diagram that shows nodes and artifacts and their relationships. However a deployment diagram may also show packages and all kind of classifier elements.
Freeform Diagram (Freeform Diagram)
A Free Form diagram is a diagram in which you can make free drawings without the restriction of using UML.
Interaction Overview Diagram (Interaction Overview Diagram)
An Interaction Overview Diagram is a visual representation of a control flow of interaction..
Object Diagram (Object Diagram)
An Object Diagram is a diagram that shows instance specification, links and slots.
Structure Diagram (Structure Diagram)
A Structure Diagram is a diagram that shows the static structure of an element.
Use Case Diagram (Use Case Diagram)
A Use-Case Diagram is a diagram that shows actors and use cases and their relationships. However a Use-Case Diagram may also show packages and all kind of classifier elements.
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.
Component Realization (Component Realization)
The realization concept is specialized to (optionally) define the classifiers that realize the contract offered by a component in terms of its provided and required interfaces.
The component forms an abstraction from these various
classifiers.
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).
Element Import (Element Import)
An element import identifies an element in another package, and allows the element to be referenced using its name without a qualifier.
Generalization (Generalization)
A generalization is a taxonomic relationship between a more general classifier and a more specific classifier. Each instance of the specific classifier is also an indirect instance of the general classifier. Thus, the specific classifier inherits the features of the more general classifier.
A generalization relates a specific classifier to a more general classifier, and is owned by the specific classifier.
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.
Interface Realization (Interface Realization)
An interface realization is a specialized realization relationship between a classifier and an interface. This relationship signifies that the realizing classifier conforms to the contract specified by the interface.
Package Import (Package Import)
A package import is a relationship that allows the use of unqualified names to refer to package members from other namespaces.
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.
Templatebinding (Templatebinding)
A template binding represents a relationship between a templateable element and a template. A template binding specifies the substitutions of actual parameters for the formal parameters of the template.
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.
Action Input Pin (Pin)Activity Parameter Node (Object Node)Association End (Association End)Attribute (Attribute)Central Buffer (Object Node)Data Store Node (Object Node)Expansion Node (Object Node)Input Pin (Pin)Output Pin (Pin)Parameter (Parameter)Port (Port)Value Pin (Pin)Abstraction (Abstraction)Component Realization (Component Realization)Dependency (Dependency)Element Import (Element Import)Generalization (Generalization)Information Flow (Information Flow)Manifestation (Manifestation)Realization (Realization)Substitution (Substitution)Usage (Usage) Data TypeA data type is a type whose instances are identified only by their value. A data type may contain attributes to support the modeling of structured data types.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
If true, the Classifier does not provide a complete declaration and can typically not be instantiated.
An abstract classifier is intended to be used by other classifiers e.g. as the target of general metarelationships or generalization relationships.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interface (Interface)
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
Model (Model)
A model captures a view of a physical system. It is an abstraction of the physical system, with a certain purpose.
This purpose determines what is to be included in the model and what is irrelevant. Thus the model completely describes those aspects of the physical system that are relevant to the purpose of the model, at the appropriate level of detail.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Package (Package)
A package is used to group elements, and provides a namespace for the grouped elements.
A package can have one or more profile applications to indicate which profiles have been applied.
Profile (Profile)
A profile defines limited extensions to a reference metamodel with the purpose of adapting the metamodel to a specific platform or domain.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
Template Parameter (Template Parameter)
A template parameter exposes a parameterable element as a formal template parameter of a template.
Association End (Association End)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An association End is a property that has a reference to an association.
Attribute (Attribute)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An attribute is a property that has no reference to an association.
Collaboration Use (Collaboration Use)
A collaboration use represents one particular use of a collaboration to explain the relationships between the properties of a classifier.
A collaboration use shows how the pattern described by a collaboration is applied in a given context, by binding specific entities from that context to the roles of the collaboration. Depending on the context, these entities could be structural features of a classifier, instance specifications, or even roles in some containing collaboration. There may be multiple occurrences of a given collaboration within a classifier, each involving a different set of roles and connectors.
A given role or connector may be involved in multiple occurrences of the same or different collaborations. Associated dependencies map features of the collaboration type to features in the classifier. These dependencies indicate which role in the classifier plays which role in the collaboration.
Constraint (Constraint)
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.
Operation (Operation)
An operation is a behavioral feature of a classifier that specifies the name, type, parameters, and constraints for invoking an associated behavior. An operation may invoke both the execution of method behaviors as well as other behavioral responses.
Port (Port)
A port is a property of a classifier that specifies a distinct interaction point between that classifier and its environment or between the (behavior of the) classifier and its internal parts.
Ports are connected to properties of the classifier by connectors through which requests can be made to invoke the behavioral features of a classifier.
A Port may specify the services a classifier provides (offers) to its environment as well as the services that a classifier expects (requires) of its environment. A port has an associated protocol state machine.
Template Signature (Template Signature)
A template signature bundles the set of formal template parameters for a templated element.
Use Case (Use Case)
A use case is the specification of a set of actions performed by a system, which yields an observable result that is, typically, of value for one or more actors or other stakeholders of the system.
Class Diagram (Class Diagram)
A Class Diagram is a diagram that shows classes and interfaces and their relationships. However a class diagram may also show packages and all kind of classifier elements.
Component Diagram (Component Diagram)
A Component Diagram is a diagram that shows components, interfaces and artifacts and their relationships. However a component diagram may also show packages and all kind of classifier elements.
Deployment Diagram (Deployment Diagram)
A Deployment Diagram is a diagram that shows nodes and artifacts and their relationships. However a deployment diagram may also show packages and all kind of classifier elements.
Freeform Diagram (Freeform Diagram)
A Free Form diagram is a diagram in which you can make free drawings without the restriction of using UML.
Interaction Overview Diagram (Interaction Overview Diagram)
An Interaction Overview Diagram is a visual representation of a control flow of interaction..
Object Diagram (Object Diagram)
An Object Diagram is a diagram that shows instance specification, links and slots.
Use Case Diagram (Use Case Diagram)
A Use-Case Diagram is a diagram that shows actors and use cases and their relationships. However a Use-Case Diagram may also show packages and all kind of classifier elements.
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.
Component Realization (Component Realization)
The realization concept is specialized to (optionally) define the classifiers that realize the contract offered by a component in terms of its provided and required interfaces.
The component forms an abstraction from these various
classifiers.
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).
Element Import (Element Import)
An element import identifies an element in another package, and allows the element to be referenced using its name without a qualifier.
Generalization (Generalization)
A generalization is a taxonomic relationship between a more general classifier and a more specific classifier. Each instance of the specific classifier is also an indirect instance of the general classifier. Thus, the specific classifier inherits the features of the more general classifier.
A generalization relates a specific classifier to a more general classifier, and is owned by the specific classifier.
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.
Package Import (Package Import)
A package import is a relationship that allows the use of unqualified names to refer to package members from other namespaces.
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.
Templatebinding (Templatebinding)
A template binding represents a relationship between a templateable element and a template. A template binding specifies the substitutions of actual parameters for the formal parameters of the template.
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.
Action Input Pin (Pin)Activity Parameter Node (Object Node)Association End (Association End)Attribute (Attribute)Central Buffer (Object Node)Data Store Node (Object Node)Expansion Node (Object Node)Input Pin (Pin)Output Pin (Pin)Parameter (Parameter)Port (Port)Value Pin (Pin)Abstraction (Abstraction)Component Realization (Component Realization)Dependency (Dependency)Element Import (Element Import)Generalization (Generalization)Information Flow (Information Flow)Manifestation (Manifestation)Realization (Realization)Substitution (Substitution)Usage (Usage) DeviceA device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
If true, the Classifier does not provide a complete declaration and can typically not be instantiated.
An abstract classifier is intended to be used by other classifiers e.g. as the target of general metarelationships or generalization relationships.
Determines whether an object specified by this classifier is active or not. If true, then the owning classifier is referred to as an active classifier. If false, then such a classifier is referred to as a passive classifier.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Association (Association)
An association describes a set of tuples whose values refer to typed instances. An instance of an association is called a link.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
Communication Path (Communication Path)
A communication path is an association between two deployment targets, through which they are able to exchange signals and messages.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Extension (Extension)
An extension is used to indicate that the properties of a metaclass are extended through a stereotype, and gives the ability to flexibly add (and later remove) stereotypes to classes.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interface (Interface)
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
Model (Model)
A model captures a view of a physical system. It is an abstraction of the physical system, with a certain purpose.
This purpose determines what is to be included in the model and what is irrelevant. Thus the model completely describes those aspects of the physical system that are relevant to the purpose of the model, at the appropriate level of detail.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Package (Package)
A package is used to group elements, and provides a namespace for the grouped elements.
A package can have one or more profile applications to indicate which profiles have been applied.
Profile (Profile)
A profile defines limited extensions to a reference metamodel with the purpose of adapting the metamodel to a specific platform or domain.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
Template Parameter (Template Parameter)
A template parameter exposes a parameterable element as a formal template parameter of a template.
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Actor (Actor)
An actor specifies a role played by a user or any other system that interacts with the subject.
Artifact (Artifact)
An artifact is the specification of a physical piece of information that is used or produced by a software development process, or by deployment and operation of a system.
Examples of artifacts include model files, source files, scripts, and binary executable files, a table in a database system, a development deliverable, or a word-processing document, a mail message. An artifact is the source of a deployment to a node.
Association (Association)
An association describes a set of tuples whose values refer to typed instances. An instance of an association is called a link.
Association End (Association End)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An association End is a property that has a reference to an association.
Attribute (Attribute)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An attribute is a property that has no reference to an association.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
Collaboration (Collaboration)
A collaboration defines a set of co-operating roles used collectively to illustrate a specific functionality.
A collaboration should only show the roles and attributes required to accomplish its defined task or function. Isolating the primary roles is an exercise in simplifying the structure and clarifying the behavior, and also provides for re-use. A collaboration often implements a pattern.
Collaboration Use (Collaboration Use)
A collaboration use represents one particular use of a collaboration to explain the relationships between the properties of a classifier.
A collaboration use shows how the pattern described by a collaboration is applied in a given context, by binding specific entities from that context to the roles of the collaboration. Depending on the context, these entities could be structural features of a classifier, instance specifications, or even roles in some containing collaboration. There may be multiple occurrences of a given collaboration within a classifier, each involving a different set of roles and connectors.
A given role or connector may be involved in multiple occurrences of the same or different collaborations. Associated dependencies map features of the collaboration type to features in the classifier. These dependencies indicate which role in the classifier plays which role in the collaboration.
Communication Path (Communication Path)
A communication path is an association between two deployment targets, through which they are able to exchange signals and messages.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Connector (Connector)
Specifies a link that enables communication between two or more instances. This link may be an instance of anassociation, or it may represent the possibility of the instances being able to communicate because their identitiesare known by virtue of being passed in as parameters, held in variables or slots, or because the communicatinginstances are the same instance.
The link may be realized by something as simple as a pointer or by something ascomplex as a network connection. In contrast to associations, which specify links between any instance of theassociated classifiers, connectors specify links between instances playing the connected parts only.
Constraint (Constraint)
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.
Data Type (Data Type)
A data type is a type whose instances are identified only by their value. A data type may contain attributes to support the modeling of structured data types.
Deployment Specification (Deployment Specification)
A deployment specification specifies a set of properties that determine execution parameters of a component artifact that is deployed on a node.
A deployment specification can be aimed at a specific type of container. An artifact that reifies or implements deployment specification properties is a deployment descriptor.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Enumeration (Enumeration)
An enumeration is a data type whose values are enumerated in the model as enumeration literals.
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Extension (Extension)
An extension is used to indicate that the properties of a metaclass are extended through a stereotype, and gives the ability to flexibly add (and later remove) stereotypes to classes.
Information Item (Information Item)
An information item is an abstraction of all kinds of information that can be exchanged between objects. It is a kind of
classifier intended for representing information in a very abstract way, one which cannot be instantiated.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interface (Interface)
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Operation (Operation)
An operation is a behavioral feature of a classifier that specifies the name, type, parameters, and constraints for invoking an associated behavior. An operation may invoke both the execution of method behaviors as well as other behavioral responses.
Port (Port)
A port is a property of a classifier that specifies a distinct interaction point between that classifier and its environment or between the (behavior of the) classifier and its internal parts.
Ports are connected to properties of the classifier by connectors through which requests can be made to invoke the behavioral features of a classifier.
A Port may specify the services a classifier provides (offers) to its environment as well as the services that a classifier expects (requires) of its environment. A port has an associated protocol state machine.
Primitive Type (Primitive Type)
A primitive type defines a predefined data type, without any relevant substructure (i.e., it has no parts in the context of UML). A primitive datatype may have an algebra and operations defined outside of UML, for example, mathematically.
Protocol (Protocol)
Only available together with the Real-Time Extension of RSA.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
Reception (Reception)
A reception is a declaration stating that a classifier is prepared to react to the receipt of a signal. A reception designates a signal and specifies the expected behavioral response.
The details of handling a signal are specified by the behavior associated with the reception or the classifier itself.
Signal (Signal)
A signal is a specification of send request instances communicated between objects. The receiving object handles the received request instances as specified by its receptions. The data carried by a send request (which was passed to it by the send invocation occurrence that caused that request) are represented as attributes of the signal.
A signal is defined independently of the classifiers handling the signal occurrence.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
Template Signature (Template Signature)
A template signature bundles the set of formal template parameters for a templated element.
Trigger (Trigger)
A trigger relates an event to a behavior that may affect an instance of the classifier. A trigger specification may be qualified by the port on which the event occurred.
Use Case (Use Case)
A use case is the specification of a set of actions performed by a system, which yields an observable result that is, typically, of value for one or more actors or other stakeholders of the system.
Class Diagram (Class Diagram)
A Class Diagram is a diagram that shows classes and interfaces and their relationships. However a class diagram may also show packages and all kind of classifier elements.
Component Diagram (Component Diagram)
A Component Diagram is a diagram that shows components, interfaces and artifacts and their relationships. However a component diagram may also show packages and all kind of classifier elements.
Deployment Diagram (Deployment Diagram)
A Deployment Diagram is a diagram that shows nodes and artifacts and their relationships. However a deployment diagram may also show packages and all kind of classifier elements.
Freeform Diagram (Freeform Diagram)
A Free Form diagram is a diagram in which you can make free drawings without the restriction of using UML.
Interaction Overview Diagram (Interaction Overview Diagram)
An Interaction Overview Diagram is a visual representation of a control flow of interaction..
Object Diagram (Object Diagram)
An Object Diagram is a diagram that shows instance specification, links and slots.
Structure Diagram (Structure Diagram)
A Structure Diagram is a diagram that shows the static structure of an element.
Use Case Diagram (Use Case Diagram)
A Use-Case Diagram is a diagram that shows actors and use cases and their relationships. However a Use-Case Diagram may also show packages and all kind of classifier elements.
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.
Component Realization (Component Realization)
The realization concept is specialized to (optionally) define the classifiers that realize the contract offered by a component in terms of its provided and required interfaces.
The component forms an abstraction from these various
classifiers.
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).
Deployment (Deployment)
A deployment is the allocation of an artifact or artifact instance to a deployment target. A component deployment is the deployment of one or more artifacts or artifact instances to a deployment target, optionally parameterized by a deployment specification. Examples are executables and configuration files.
Element Import (Element Import)
An element import identifies an element in another package, and allows the element to be referenced using its name without a qualifier.
Generalization (Generalization)
A generalization is a taxonomic relationship between a more general classifier and a more specific classifier. Each instance of the specific classifier is also an indirect instance of the general classifier. Thus, the specific classifier inherits the features of the more general classifier.
A generalization relates a specific classifier to a more general classifier, and is owned by the specific classifier.
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.
Interface Realization (Interface Realization)
An interface realization is a specialized realization relationship between a classifier and an interface. This relationship signifies that the realizing classifier conforms to the contract specified by the interface.
Package Import (Package Import)
A package import is a relationship that allows the use of unqualified names to refer to package members from other namespaces.
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.
Templatebinding (Templatebinding)
A template binding represents a relationship between a templateable element and a template. A template binding specifies the substitutions of actual parameters for the formal parameters of the template.
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.
Action Input Pin (Pin)Activity Parameter Node (Object Node)Association End (Association End)Attribute (Attribute)Central Buffer (Object Node)Data Store Node (Object Node)Expansion Node (Object Node)Input Pin (Pin)Output Pin (Pin)Parameter (Parameter)Port (Port)Value Pin (Pin)Abstraction (Abstraction)Component Realization (Component Realization)Dependency (Dependency)Deployment (Deployment)Element Import (Element Import)Generalization (Generalization)Information Flow (Information Flow)Manifestation (Manifestation)Realization (Realization)Substitution (Substitution)Usage (Usage) EnumerationAn enumeration is a data type whose values are enumerated in the model as enumeration literals.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
If true, the Classifier does not provide a complete declaration and can typically not be instantiated.
An abstract classifier is intended to be used by other classifiers e.g. as the target of general metarelationships or generalization relationships.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interface (Interface)
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
Model (Model)
A model captures a view of a physical system. It is an abstraction of the physical system, with a certain purpose.
This purpose determines what is to be included in the model and what is irrelevant. Thus the model completely describes those aspects of the physical system that are relevant to the purpose of the model, at the appropriate level of detail.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Package (Package)
A package is used to group elements, and provides a namespace for the grouped elements.
A package can have one or more profile applications to indicate which profiles have been applied.
Profile (Profile)
A profile defines limited extensions to a reference metamodel with the purpose of adapting the metamodel to a specific platform or domain.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
Template Parameter (Template Parameter)
A template parameter exposes a parameterable element as a formal template parameter of a template.
Association End (Association End)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An association End is a property that has a reference to an association.
Attribute (Attribute)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An attribute is a property that has no reference to an association.
Collaboration Use (Collaboration Use)
A collaboration use represents one particular use of a collaboration to explain the relationships between the properties of a classifier.
A collaboration use shows how the pattern described by a collaboration is applied in a given context, by binding specific entities from that context to the roles of the collaboration. Depending on the context, these entities could be structural features of a classifier, instance specifications, or even roles in some containing collaboration. There may be multiple occurrences of a given collaboration within a classifier, each involving a different set of roles and connectors.
A given role or connector may be involved in multiple occurrences of the same or different collaborations. Associated dependencies map features of the collaboration type to features in the classifier. These dependencies indicate which role in the classifier plays which role in the collaboration.
Constraint (Constraint)
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.
Enumeration Literal (Enumeration Literal)
An enumeration literal is a user-defined data value for an enumeration.
Operation (Operation)
An operation is a behavioral feature of a classifier that specifies the name, type, parameters, and constraints for invoking an associated behavior. An operation may invoke both the execution of method behaviors as well as other behavioral responses.
Port (Port)
A port is a property of a classifier that specifies a distinct interaction point between that classifier and its environment or between the (behavior of the) classifier and its internal parts.
Ports are connected to properties of the classifier by connectors through which requests can be made to invoke the behavioral features of a classifier.
A Port may specify the services a classifier provides (offers) to its environment as well as the services that a classifier expects (requires) of its environment. A port has an associated protocol state machine.
Template Signature (Template Signature)
A template signature bundles the set of formal template parameters for a templated element.
Use Case (Use Case)
A use case is the specification of a set of actions performed by a system, which yields an observable result that is, typically, of value for one or more actors or other stakeholders of the system.
Class Diagram (Class Diagram)
A Class Diagram is a diagram that shows classes and interfaces and their relationships. However a class diagram may also show packages and all kind of classifier elements.
Component Diagram (Component Diagram)
A Component Diagram is a diagram that shows components, interfaces and artifacts and their relationships. However a component diagram may also show packages and all kind of classifier elements.
Deployment Diagram (Deployment Diagram)
A Deployment Diagram is a diagram that shows nodes and artifacts and their relationships. However a deployment diagram may also show packages and all kind of classifier elements.
Freeform Diagram (Freeform Diagram)
A Free Form diagram is a diagram in which you can make free drawings without the restriction of using UML.
Interaction Overview Diagram (Interaction Overview Diagram)
An Interaction Overview Diagram is a visual representation of a control flow of interaction..
Object Diagram (Object Diagram)
An Object Diagram is a diagram that shows instance specification, links and slots.
Use Case Diagram (Use Case Diagram)
A Use-Case Diagram is a diagram that shows actors and use cases and their relationships. However a Use-Case Diagram may also show packages and all kind of classifier elements.
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.
Component Realization (Component Realization)
The realization concept is specialized to (optionally) define the classifiers that realize the contract offered by a component in terms of its provided and required interfaces.
The component forms an abstraction from these various
classifiers.
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).
Element Import (Element Import)
An element import identifies an element in another package, and allows the element to be referenced using its name without a qualifier.
Generalization (Generalization)
A generalization is a taxonomic relationship between a more general classifier and a more specific classifier. Each instance of the specific classifier is also an indirect instance of the general classifier. Thus, the specific classifier inherits the features of the more general classifier.
A generalization relates a specific classifier to a more general classifier, and is owned by the specific classifier.
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.
Package Import (Package Import)
A package import is a relationship that allows the use of unqualified names to refer to package members from other namespaces.
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.
Templatebinding (Templatebinding)
A template binding represents a relationship between a templateable element and a template. A template binding specifies the substitutions of actual parameters for the formal parameters of the template.
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.
Action Input Pin (Pin)Activity Parameter Node (Object Node)Association End (Association End)Attribute (Attribute)Central Buffer (Object Node)Data Store Node (Object Node)Expansion Node (Object Node)Input Pin (Pin)Output Pin (Pin)Parameter (Parameter)Port (Port)Value Pin (Pin)Abstraction (Abstraction)Component Realization (Component Realization)Dependency (Dependency)Element Import (Element Import)Generalization (Generalization)Information Flow (Information Flow)Manifestation (Manifestation)Realization (Realization)Substitution (Substitution)Usage (Usage) ExtensionAn extension is used to indicate that the properties of a metaclass are extended through a stereotype, and gives the ability to flexibly add (and later remove) stereotypes to classes.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
If true, the Classifier does not provide a complete declaration and can typically not be instantiated.
An abstract classifier is intended to be used by other classifiers e.g. as the target of general metarelationships or generalization relationships.
Specifies whether the association is derived from other model elements such as other associations or constraints.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interface (Interface)
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
Model (Model)
A model captures a view of a physical system. It is an abstraction of the physical system, with a certain purpose.
This purpose determines what is to be included in the model and what is irrelevant. Thus the model completely describes those aspects of the physical system that are relevant to the purpose of the model, at the appropriate level of detail.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Package (Package)
A package is used to group elements, and provides a namespace for the grouped elements.
A package can have one or more profile applications to indicate which profiles have been applied.
Profile (Profile)
A profile defines limited extensions to a reference metamodel with the purpose of adapting the metamodel to a specific platform or domain.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
Template Parameter (Template Parameter)
A template parameter exposes a parameterable element as a formal template parameter of a template.
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Association End (Association End)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An association End is a property that has a reference to an association.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
Collaboration Use (Collaboration Use)
A collaboration use represents one particular use of a collaboration to explain the relationships between the properties of a classifier.
A collaboration use shows how the pattern described by a collaboration is applied in a given context, by binding specific entities from that context to the roles of the collaboration. Depending on the context, these entities could be structural features of a classifier, instance specifications, or even roles in some containing collaboration. There may be multiple occurrences of a given collaboration within a classifier, each involving a different set of roles and connectors.
A given role or connector may be involved in multiple occurrences of the same or different collaborations. Associated dependencies map features of the collaboration type to features in the classifier. These dependencies indicate which role in the classifier plays which role in the collaboration.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Constraint (Constraint)
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.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
Template Signature (Template Signature)
A template signature bundles the set of formal template parameters for a templated element.
Use Case (Use Case)
A use case is the specification of a set of actions performed by a system, which yields an observable result that is, typically, of value for one or more actors or other stakeholders of the system.
Class Diagram (Class Diagram)
A Class Diagram is a diagram that shows classes and interfaces and their relationships. However a class diagram may also show packages and all kind of classifier elements.
Component Diagram (Component Diagram)
A Component Diagram is a diagram that shows components, interfaces and artifacts and their relationships. However a component diagram may also show packages and all kind of classifier elements.
Deployment Diagram (Deployment Diagram)
A Deployment Diagram is a diagram that shows nodes and artifacts and their relationships. However a deployment diagram may also show packages and all kind of classifier elements.
Freeform Diagram (Freeform Diagram)
A Free Form diagram is a diagram in which you can make free drawings without the restriction of using UML.
Interaction Overview Diagram (Interaction Overview Diagram)
An Interaction Overview Diagram is a visual representation of a control flow of interaction..
Object Diagram (Object Diagram)
An Object Diagram is a diagram that shows instance specification, links and slots.
Use Case Diagram (Use Case Diagram)
A Use-Case Diagram is a diagram that shows actors and use cases and their relationships. However a Use-Case Diagram may also show packages and all kind of classifier elements.
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.
Component Realization (Component Realization)
The realization concept is specialized to (optionally) define the classifiers that realize the contract offered by a component in terms of its provided and required interfaces.
The component forms an abstraction from these various
classifiers.
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).
Element Import (Element Import)
An element import identifies an element in another package, and allows the element to be referenced using its name without a qualifier.
Generalization (Generalization)
A generalization is a taxonomic relationship between a more general classifier and a more specific classifier. Each instance of the specific classifier is also an indirect instance of the general classifier. Thus, the specific classifier inherits the features of the more general classifier.
A generalization relates a specific classifier to a more general classifier, and is owned by the specific classifier.
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.
Package Import (Package Import)
A package import is a relationship that allows the use of unqualified names to refer to package members from other namespaces.
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.
Templatebinding (Templatebinding)
A template binding represents a relationship between a templateable element and a template. A template binding specifies the substitutions of actual parameters for the formal parameters of the template.
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.
Action Input Pin (Pin)Activity Parameter Node (Object Node)Association End (Association End)Attribute (Attribute)Central Buffer (Object Node)Data Store Node (Object Node)Expansion Node (Object Node)Input Pin (Pin)Output Pin (Pin)Parameter (Parameter)Port (Port)Value Pin (Pin)Association End (Association End)Abstraction (Abstraction)Component Realization (Component Realization)Dependency (Dependency)Element Import (Element Import)Generalization (Generalization)Information Flow (Information Flow)Manifestation (Manifestation)Realization (Realization)Substitution (Substitution)Usage (Usage)Connector (Connector) Information ItemAn information item is an abstraction of all kinds of information that can be exchanged between objects. It is a kind of
classifier intended for representing information in a very abstract way, one which cannot be instantiated.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
If true, the Classifier does not provide a complete declaration and can typically not be instantiated.
An abstract classifier is intended to be used by other classifiers e.g. as the target of general metarelationships or generalization relationships.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interface (Interface)
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
Model (Model)
A model captures a view of a physical system. It is an abstraction of the physical system, with a certain purpose.
This purpose determines what is to be included in the model and what is irrelevant. Thus the model completely describes those aspects of the physical system that are relevant to the purpose of the model, at the appropriate level of detail.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Package (Package)
A package is used to group elements, and provides a namespace for the grouped elements.
A package can have one or more profile applications to indicate which profiles have been applied.
Profile (Profile)
A profile defines limited extensions to a reference metamodel with the purpose of adapting the metamodel to a specific platform or domain.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
Template Parameter (Template Parameter)
A template parameter exposes a parameterable element as a formal template parameter of a template.
Association End (Association End)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An association End is a property that has a reference to an association.
Collaboration Use (Collaboration Use)
A collaboration use represents one particular use of a collaboration to explain the relationships between the properties of a classifier.
A collaboration use shows how the pattern described by a collaboration is applied in a given context, by binding specific entities from that context to the roles of the collaboration. Depending on the context, these entities could be structural features of a classifier, instance specifications, or even roles in some containing collaboration. There may be multiple occurrences of a given collaboration within a classifier, each involving a different set of roles and connectors.
A given role or connector may be involved in multiple occurrences of the same or different collaborations. Associated dependencies map features of the collaboration type to features in the classifier. These dependencies indicate which role in the classifier plays which role in the collaboration.
Constraint (Constraint)
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.
Template Signature (Template Signature)
A template signature bundles the set of formal template parameters for a templated element.
Use Case (Use Case)
A use case is the specification of a set of actions performed by a system, which yields an observable result that is, typically, of value for one or more actors or other stakeholders of the system.
Activity (Activity)Actor (Actor)Artifact (Artifact)Association (Association)Class (Class)Collaboration (Collaboration)Communication Path (Communication Path)Component (Component)Data Type (Data Type)Deployment Specification (Deployment Specification)Device (Device)Enumeration (Enumeration)Execution Environment (Execution Environment)Extension (Extension)Information Item (Information Item)Interaction (Interaction)Interface (Interface)Node (Node)Opaque Behavior (Opaque Behavior)Primitive Type (Primitive Type)Protocol (Protocol)Protocol State Machine (Protocol State Machine)Signal (Signal)State Machine (State Machine)Stereotype (Stereotype)Use Case (Use Case)Class Diagram (Class Diagram)
A Class Diagram is a diagram that shows classes and interfaces and their relationships. However a class diagram may also show packages and all kind of classifier elements.
Component Diagram (Component Diagram)
A Component Diagram is a diagram that shows components, interfaces and artifacts and their relationships. However a component diagram may also show packages and all kind of classifier elements.
Deployment Diagram (Deployment Diagram)
A Deployment Diagram is a diagram that shows nodes and artifacts and their relationships. However a deployment diagram may also show packages and all kind of classifier elements.
Freeform Diagram (Freeform Diagram)
A Free Form diagram is a diagram in which you can make free drawings without the restriction of using UML.
Interaction Overview Diagram (Interaction Overview Diagram)
An Interaction Overview Diagram is a visual representation of a control flow of interaction..
Object Diagram (Object Diagram)
An Object Diagram is a diagram that shows instance specification, links and slots.
Use Case Diagram (Use Case Diagram)
A Use-Case Diagram is a diagram that shows actors and use cases and their relationships. However a Use-Case Diagram may also show packages and all kind of classifier elements.
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.
Component Realization (Component Realization)
The realization concept is specialized to (optionally) define the classifiers that realize the contract offered by a component in terms of its provided and required interfaces.
The component forms an abstraction from these various
classifiers.
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).
Element Import (Element Import)
An element import identifies an element in another package, and allows the element to be referenced using its name without a qualifier.
Generalization (Generalization)
A generalization is a taxonomic relationship between a more general classifier and a more specific classifier. Each instance of the specific classifier is also an indirect instance of the general classifier. Thus, the specific classifier inherits the features of the more general classifier.
A generalization relates a specific classifier to a more general classifier, and is owned by the specific classifier.
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.
Package Import (Package Import)
A package import is a relationship that allows the use of unqualified names to refer to package members from other namespaces.
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.
Templatebinding (Templatebinding)
A template binding represents a relationship between a templateable element and a template. A template binding specifies the substitutions of actual parameters for the formal parameters of the template.
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.
Action Input Pin (Pin)Activity Parameter Node (Object Node)Association End (Association End)Attribute (Attribute)Central Buffer (Object Node)Data Store Node (Object Node)Expansion Node (Object Node)Input Pin (Pin)Output Pin (Pin)Parameter (Parameter)Port (Port)Value Pin (Pin)Abstraction (Abstraction)Component Realization (Component Realization)Dependency (Dependency)Element Import (Element Import)Generalization (Generalization)Information Flow (Information Flow)Manifestation (Manifestation)Realization (Realization)Substitution (Substitution)Usage (Usage) InterfaceAn interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
If true, the Classifier does not provide a complete declaration and can typically not be instantiated.
An abstract classifier is intended to be used by other classifiers e.g. as the target of general metarelationships or generalization relationships.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interface (Interface)
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
Model (Model)
A model captures a view of a physical system. It is an abstraction of the physical system, with a certain purpose.
This purpose determines what is to be included in the model and what is irrelevant. Thus the model completely describes those aspects of the physical system that are relevant to the purpose of the model, at the appropriate level of detail.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Package (Package)
A package is used to group elements, and provides a namespace for the grouped elements.
A package can have one or more profile applications to indicate which profiles have been applied.
Profile (Profile)
A profile defines limited extensions to a reference metamodel with the purpose of adapting the metamodel to a specific platform or domain.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
Template Parameter (Template Parameter)
A template parameter exposes a parameterable element as a formal template parameter of a template.
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Actor (Actor)
An actor specifies a role played by a user or any other system that interacts with the subject.
Artifact (Artifact)
An artifact is the specification of a physical piece of information that is used or produced by a software development process, or by deployment and operation of a system.
Examples of artifacts include model files, source files, scripts, and binary executable files, a table in a database system, a development deliverable, or a word-processing document, a mail message. An artifact is the source of a deployment to a node.
Association (Association)
An association describes a set of tuples whose values refer to typed instances. An instance of an association is called a link.
Association End (Association End)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An association End is a property that has a reference to an association.
Attribute (Attribute)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An attribute is a property that has no reference to an association.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
Collaboration (Collaboration)
A collaboration defines a set of co-operating roles used collectively to illustrate a specific functionality.
A collaboration should only show the roles and attributes required to accomplish its defined task or function. Isolating the primary roles is an exercise in simplifying the structure and clarifying the behavior, and also provides for re-use. A collaboration often implements a pattern.
Collaboration Use (Collaboration Use)
A collaboration use represents one particular use of a collaboration to explain the relationships between the properties of a classifier.
A collaboration use shows how the pattern described by a collaboration is applied in a given context, by binding specific entities from that context to the roles of the collaboration. Depending on the context, these entities could be structural features of a classifier, instance specifications, or even roles in some containing collaboration. There may be multiple occurrences of a given collaboration within a classifier, each involving a different set of roles and connectors.
A given role or connector may be involved in multiple occurrences of the same or different collaborations. Associated dependencies map features of the collaboration type to features in the classifier. These dependencies indicate which role in the classifier plays which role in the collaboration.
Communication Path (Communication Path)
A communication path is an association between two deployment targets, through which they are able to exchange signals and messages.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Constraint (Constraint)
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.
Data Type (Data Type)
A data type is a type whose instances are identified only by their value. A data type may contain attributes to support the modeling of structured data types.
Deployment Specification (Deployment Specification)
A deployment specification specifies a set of properties that determine execution parameters of a component artifact that is deployed on a node.
A deployment specification can be aimed at a specific type of container. An artifact that reifies or implements deployment specification properties is a deployment descriptor.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Enumeration (Enumeration)
An enumeration is a data type whose values are enumerated in the model as enumeration literals.
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Extension (Extension)
An extension is used to indicate that the properties of a metaclass are extended through a stereotype, and gives the ability to flexibly add (and later remove) stereotypes to classes.
Information Item (Information Item)
An information item is an abstraction of all kinds of information that can be exchanged between objects. It is a kind of
classifier intended for representing information in a very abstract way, one which cannot be instantiated.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interface (Interface)
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Operation (Operation)
An operation is a behavioral feature of a classifier that specifies the name, type, parameters, and constraints for invoking an associated behavior. An operation may invoke both the execution of method behaviors as well as other behavioral responses.
Port (Port)
A port is a property of a classifier that specifies a distinct interaction point between that classifier and its environment or between the (behavior of the) classifier and its internal parts.
Ports are connected to properties of the classifier by connectors through which requests can be made to invoke the behavioral features of a classifier.
A Port may specify the services a classifier provides (offers) to its environment as well as the services that a classifier expects (requires) of its environment. A port has an associated protocol state machine.
Primitive Type (Primitive Type)
A primitive type defines a predefined data type, without any relevant substructure (i.e., it has no parts in the context of UML). A primitive datatype may have an algebra and operations defined outside of UML, for example, mathematically.
Protocol (Protocol)
Only available together with the Real-Time Extension of RSA.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
Reception (Reception)
A reception is a declaration stating that a classifier is prepared to react to the receipt of a signal. A reception designates a signal and specifies the expected behavioral response.
The details of handling a signal are specified by the behavior associated with the reception or the classifier itself.
Signal (Signal)
A signal is a specification of send request instances communicated between objects. The receiving object handles the received request instances as specified by its receptions. The data carried by a send request (which was passed to it by the send invocation occurrence that caused that request) are represented as attributes of the signal.
A signal is defined independently of the classifiers handling the signal occurrence.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
Template Signature (Template Signature)
A template signature bundles the set of formal template parameters for a templated element.
Use Case (Use Case)
A use case is the specification of a set of actions performed by a system, which yields an observable result that is, typically, of value for one or more actors or other stakeholders of the system.
Class Diagram (Class Diagram)
A Class Diagram is a diagram that shows classes and interfaces and their relationships. However a class diagram may also show packages and all kind of classifier elements.
Component Diagram (Component Diagram)
A Component Diagram is a diagram that shows components, interfaces and artifacts and their relationships. However a component diagram may also show packages and all kind of classifier elements.
Deployment Diagram (Deployment Diagram)
A Deployment Diagram is a diagram that shows nodes and artifacts and their relationships. However a deployment diagram may also show packages and all kind of classifier elements.
Freeform Diagram (Freeform Diagram)
A Free Form diagram is a diagram in which you can make free drawings without the restriction of using UML.
Interaction Overview Diagram (Interaction Overview Diagram)
An Interaction Overview Diagram is a visual representation of a control flow of interaction..
Object Diagram (Object Diagram)
An Object Diagram is a diagram that shows instance specification, links and slots.
Use Case Diagram (Use Case Diagram)
A Use-Case Diagram is a diagram that shows actors and use cases and their relationships. However a Use-Case Diagram may also show packages and all kind of classifier elements.
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.
Component Realization (Component Realization)
The realization concept is specialized to (optionally) define the classifiers that realize the contract offered by a component in terms of its provided and required interfaces.
The component forms an abstraction from these various
classifiers.
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).
Element Import (Element Import)
An element import identifies an element in another package, and allows the element to be referenced using its name without a qualifier.
Generalization (Generalization)
A generalization is a taxonomic relationship between a more general classifier and a more specific classifier. Each instance of the specific classifier is also an indirect instance of the general classifier. Thus, the specific classifier inherits the features of the more general classifier.
A generalization relates a specific classifier to a more general classifier, and is owned by the specific classifier.
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.
Package Import (Package Import)
A package import is a relationship that allows the use of unqualified names to refer to package members from other namespaces.
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.
Templatebinding (Templatebinding)
A template binding represents a relationship between a templateable element and a template. A template binding specifies the substitutions of actual parameters for the formal parameters of the template.
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.
Action Input Pin (Pin)Activity Parameter Node (Object Node)Association End (Association End)Attribute (Attribute)Central Buffer (Object Node)Data Store Node (Object Node)Expansion Node (Object Node)Input Pin (Pin)Output Pin (Pin)Parameter (Parameter)Port (Port)Value Pin (Pin)Abstraction (Abstraction)Component Realization (Component Realization)Dependency (Dependency)Element Import (Element Import)Generalization (Generalization)Information Flow (Information Flow)Interface Realization (Interface Realization)Manifestation (Manifestation)Realization (Realization)Substitution (Substitution)Usage (Usage) Opaque BehaviorAn behavior with implementation-specific semantics.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
Designates a behavioral feature that the behavior implements.
The behavioral feature must be owned by the classifier that owns the behavior or be inherited by it. The parameters of the behavioral feature and the implementing behavior must match.
If a behavior does not have a specification, it is directly associated with a classifier (i.e., it is the behavior of the classifier as a whole).
Specifies which languages that are used in the bodies.
If true, the Classifier does not provide a complete declaration and can typically not be instantiated.
An abstract classifier is intended to be used by other classifiers e.g. as the target of general metarelationships or generalization relationships.
Determines whether an object specified by this classifier is active or not. If true, then the owning classifier is referred to as an active classifier. If false, then such a classifier is referred to as a passive classifier.
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.
Tells whether the behavior can be invoked while it is still executing from a previous invocation.
Specifies the behavior in one or more languages.
The classifier that is the context for the execution of the behavior.
If the behavior is owned by a BehavioredClassifier, that classifier is the context. Otherwise, the context is the first BehavioredClassifier reached by following the chain of owner relationships.
For example, following this algorithm, the context of an entry action in a state machine is the classifier that owns the state machine. The features of the context classifier as well as the elements visible to the context classifier are visible to the behavior
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Actor (Actor)
An actor specifies a role played by a user or any other system that interacts with the subject.
Association (Association)
An association describes a set of tuples whose values refer to typed instances. An instance of an association is called a link.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
Collaboration (Collaboration)
A collaboration defines a set of co-operating roles used collectively to illustrate a specific functionality.
A collaboration should only show the roles and attributes required to accomplish its defined task or function. Isolating the primary roles is an exercise in simplifying the structure and clarifying the behavior, and also provides for re-use. A collaboration often implements a pattern.
Communication Path (Communication Path)
A communication path is an association between two deployment targets, through which they are able to exchange signals and messages.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Extension (Extension)
An extension is used to indicate that the properties of a metaclass are extended through a stereotype, and gives the ability to flexibly add (and later remove) stereotypes to classes.
Final State (Final State)
A special kind of state signifying that the enclosing region is completed.
If the enclosing region is directly contained in a state machine and all other regions in the state machine also are completed, then it means that the entire state machine is completed.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interface (Interface)
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
Model (Model)
A model captures a view of a physical system. It is an abstraction of the physical system, with a certain purpose.
This purpose determines what is to be included in the model and what is irrelevant. Thus the model completely describes those aspects of the physical system that are relevant to the purpose of the model, at the appropriate level of detail.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Package (Package)
A package is used to group elements, and provides a namespace for the grouped elements.
A package can have one or more profile applications to indicate which profiles have been applied.
Profile (Profile)
A profile defines limited extensions to a reference metamodel with the purpose of adapting the metamodel to a specific platform or domain.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
Protocol Transition (Protocol Transition)
A protocol transition 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.
State (State)
A state models a situation during which some (usually implicit) invariant condition holds.
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.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
Template Parameter (Template Parameter)
A template parameter exposes a parameterable element as a formal template parameter of a template.
Transition (Transition)
A transition is a directed relationship between a source vertex and a target vertex.
It may be part of a compound transition, which takes the state machine from one state configuration to another, representing the complete response of the state machine to an occurrence of an event of a particular type.
Use Case (Use Case)
A use case is the specification of a set of actions performed by a system, which yields an observable result that is, typically, of value for one or more actors or other stakeholders of the system.
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Actor (Actor)
An actor specifies a role played by a user or any other system that interacts with the subject.
Artifact (Artifact)
An artifact is the specification of a physical piece of information that is used or produced by a software development process, or by deployment and operation of a system.
Examples of artifacts include model files, source files, scripts, and binary executable files, a table in a database system, a development deliverable, or a word-processing document, a mail message. An artifact is the source of a deployment to a node.
Association (Association)
An association describes a set of tuples whose values refer to typed instances. An instance of an association is called a link.
Association End (Association End)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An association End is a property that has a reference to an association.
Attribute (Attribute)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An attribute is a property that has no reference to an association.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
Collaboration (Collaboration)
A collaboration defines a set of co-operating roles used collectively to illustrate a specific functionality.
A collaboration should only show the roles and attributes required to accomplish its defined task or function. Isolating the primary roles is an exercise in simplifying the structure and clarifying the behavior, and also provides for re-use. A collaboration often implements a pattern.
Collaboration Use (Collaboration Use)
A collaboration use represents one particular use of a collaboration to explain the relationships between the properties of a classifier.
A collaboration use shows how the pattern described by a collaboration is applied in a given context, by binding specific entities from that context to the roles of the collaboration. Depending on the context, these entities could be structural features of a classifier, instance specifications, or even roles in some containing collaboration. There may be multiple occurrences of a given collaboration within a classifier, each involving a different set of roles and connectors.
A given role or connector may be involved in multiple occurrences of the same or different collaborations. Associated dependencies map features of the collaboration type to features in the classifier. These dependencies indicate which role in the classifier plays which role in the collaboration.
Communication Path (Communication Path)
A communication path is an association between two deployment targets, through which they are able to exchange signals and messages.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Connector (Connector)
Specifies a link that enables communication between two or more instances. This link may be an instance of anassociation, or it may represent the possibility of the instances being able to communicate because their identitiesare known by virtue of being passed in as parameters, held in variables or slots, or because the communicatinginstances are the same instance.
The link may be realized by something as simple as a pointer or by something ascomplex as a network connection. In contrast to associations, which specify links between any instance of theassociated classifiers, connectors specify links between instances playing the connected parts only.
Constraint (Constraint)
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.
Data Type (Data Type)
A data type is a type whose instances are identified only by their value. A data type may contain attributes to support the modeling of structured data types.
Deployment Specification (Deployment Specification)
A deployment specification specifies a set of properties that determine execution parameters of a component artifact that is deployed on a node.
A deployment specification can be aimed at a specific type of container. An artifact that reifies or implements deployment specification properties is a deployment descriptor.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Enumeration (Enumeration)
An enumeration is a data type whose values are enumerated in the model as enumeration literals.
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Extension (Extension)
An extension is used to indicate that the properties of a metaclass are extended through a stereotype, and gives the ability to flexibly add (and later remove) stereotypes to classes.
Information Item (Information Item)
An information item is an abstraction of all kinds of information that can be exchanged between objects. It is a kind of
classifier intended for representing information in a very abstract way, one which cannot be instantiated.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interface (Interface)
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Operation (Operation)
An operation is a behavioral feature of a classifier that specifies the name, type, parameters, and constraints for invoking an associated behavior. An operation may invoke both the execution of method behaviors as well as other behavioral responses.
Parameter (Parameter)
A parameter is a specification of an argument used to pass information into or out of an invocation of a behavioral feature. Parameters are allowed to be treated as connectable elements. Parameters have support for streaming, exceptions, and parameter sets.
Port (Port)
A port is a property of a classifier that specifies a distinct interaction point between that classifier and its environment or between the (behavior of the) classifier and its internal parts.
Ports are connected to properties of the classifier by connectors through which requests can be made to invoke the behavioral features of a classifier.
A Port may specify the services a classifier provides (offers) to its environment as well as the services that a classifier expects (requires) of its environment. A port has an associated protocol state machine.
Primitive Type (Primitive Type)
A primitive type defines a predefined data type, without any relevant substructure (i.e., it has no parts in the context of UML). A primitive datatype may have an algebra and operations defined outside of UML, for example, mathematically.
Protocol (Protocol)
Only available together with the Real-Time Extension of RSA.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
Reception (Reception)
A reception is a declaration stating that a classifier is prepared to react to the receipt of a signal. A reception designates a signal and specifies the expected behavioral response.
The details of handling a signal are specified by the behavior associated with the reception or the classifier itself.
Signal (Signal)
A signal is a specification of send request instances communicated between objects. The receiving object handles the received request instances as specified by its receptions. The data carried by a send request (which was passed to it by the send invocation occurrence that caused that request) are represented as attributes of the signal.
A signal is defined independently of the classifiers handling the signal occurrence.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
Template Signature (Template Signature)
A template signature bundles the set of formal template parameters for a templated element.
Trigger (Trigger)
A trigger relates an event to a behavior that may affect an instance of the classifier. A trigger specification may be qualified by the port on which the event occurred.
Use Case (Use Case)
A use case is the specification of a set of actions performed by a system, which yields an observable result that is, typically, of value for one or more actors or other stakeholders of the system.
Class Diagram (Class Diagram)
A Class Diagram is a diagram that shows classes and interfaces and their relationships. However a class diagram may also show packages and all kind of classifier elements.
Component Diagram (Component Diagram)
A Component Diagram is a diagram that shows components, interfaces and artifacts and their relationships. However a component diagram may also show packages and all kind of classifier elements.
Deployment Diagram (Deployment Diagram)
A Deployment Diagram is a diagram that shows nodes and artifacts and their relationships. However a deployment diagram may also show packages and all kind of classifier elements.
Freeform Diagram (Freeform Diagram)
A Free Form diagram is a diagram in which you can make free drawings without the restriction of using UML.
Interaction Overview Diagram (Interaction Overview Diagram)
An Interaction Overview Diagram is a visual representation of a control flow of interaction..
Object Diagram (Object Diagram)
An Object Diagram is a diagram that shows instance specification, links and slots.
Structure Diagram (Structure Diagram)
A Structure Diagram is a diagram that shows the static structure of an element.
Use Case Diagram (Use Case Diagram)
A Use-Case Diagram is a diagram that shows actors and use cases and their relationships. However a Use-Case Diagram may also show packages and all kind of classifier elements.
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.
Component Realization (Component Realization)
The realization concept is specialized to (optionally) define the classifiers that realize the contract offered by a component in terms of its provided and required interfaces.
The component forms an abstraction from these various
classifiers.
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).
Element Import (Element Import)
An element import identifies an element in another package, and allows the element to be referenced using its name without a qualifier.
Generalization (Generalization)
A generalization is a taxonomic relationship between a more general classifier and a more specific classifier. Each instance of the specific classifier is also an indirect instance of the general classifier. Thus, the specific classifier inherits the features of the more general classifier.
A generalization relates a specific classifier to a more general classifier, and is owned by the specific classifier.
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.
Interface Realization (Interface Realization)
An interface realization is a specialized realization relationship between a classifier and an interface. This relationship signifies that the realizing classifier conforms to the contract specified by the interface.
Package Import (Package Import)
A package import is a relationship that allows the use of unqualified names to refer to package members from other namespaces.
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.
Templatebinding (Templatebinding)
A template binding represents a relationship between a templateable element and a template. A template binding specifies the substitutions of actual parameters for the formal parameters of the template.
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.
Action Input Pin (Pin)Activity Parameter Node (Object Node)Association End (Association End)Attribute (Attribute)Central Buffer (Object Node)Data Store Node (Object Node)Expansion Node (Object Node)Input Pin (Pin)Output Pin (Pin)Parameter (Parameter)Port (Port)Value Pin (Pin)
Call Behavior Action (Action)Abstraction (Abstraction)Component Realization (Component Realization)Dependency (Dependency)Element Import (Element Import)Generalization (Generalization)Information Flow (Information Flow)Manifestation (Manifestation)Realization (Realization)Substitution (Substitution)Usage (Usage)Action Input Pin (Pin)Activity Parameter Node (Object Node)Central Buffer (Object Node)Data Store Node (Object Node)Expansion Node (Object Node)Input Pin (Pin)
Object Flow (Object Flow)Output Pin (Pin)Value Pin (Pin)Object Flow (Object Flow) Primitive TypeA primitive type defines a predefined data type, without any relevant substructure (i.e., it has no parts in the context of UML). A primitive datatype may have an algebra and operations defined outside of UML, for example, mathematically.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
If true, the Classifier does not provide a complete declaration and can typically not be instantiated.
An abstract classifier is intended to be used by other classifiers e.g. as the target of general metarelationships or generalization relationships.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interface (Interface)
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
Model (Model)
A model captures a view of a physical system. It is an abstraction of the physical system, with a certain purpose.
This purpose determines what is to be included in the model and what is irrelevant. Thus the model completely describes those aspects of the physical system that are relevant to the purpose of the model, at the appropriate level of detail.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Package (Package)
A package is used to group elements, and provides a namespace for the grouped elements.
A package can have one or more profile applications to indicate which profiles have been applied.
Profile (Profile)
A profile defines limited extensions to a reference metamodel with the purpose of adapting the metamodel to a specific platform or domain.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
Template Parameter (Template Parameter)
A template parameter exposes a parameterable element as a formal template parameter of a template.
Association End (Association End)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An association End is a property that has a reference to an association.
Attribute (Attribute)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An attribute is a property that has no reference to an association.
Collaboration Use (Collaboration Use)
A collaboration use represents one particular use of a collaboration to explain the relationships between the properties of a classifier.
A collaboration use shows how the pattern described by a collaboration is applied in a given context, by binding specific entities from that context to the roles of the collaboration. Depending on the context, these entities could be structural features of a classifier, instance specifications, or even roles in some containing collaboration. There may be multiple occurrences of a given collaboration within a classifier, each involving a different set of roles and connectors.
A given role or connector may be involved in multiple occurrences of the same or different collaborations. Associated dependencies map features of the collaboration type to features in the classifier. These dependencies indicate which role in the classifier plays which role in the collaboration.
Constraint (Constraint)
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.
Operation (Operation)
An operation is a behavioral feature of a classifier that specifies the name, type, parameters, and constraints for invoking an associated behavior. An operation may invoke both the execution of method behaviors as well as other behavioral responses.
Port (Port)
A port is a property of a classifier that specifies a distinct interaction point between that classifier and its environment or between the (behavior of the) classifier and its internal parts.
Ports are connected to properties of the classifier by connectors through which requests can be made to invoke the behavioral features of a classifier.
A Port may specify the services a classifier provides (offers) to its environment as well as the services that a classifier expects (requires) of its environment. A port has an associated protocol state machine.
Template Signature (Template Signature)
A template signature bundles the set of formal template parameters for a templated element.
Use Case (Use Case)
A use case is the specification of a set of actions performed by a system, which yields an observable result that is, typically, of value for one or more actors or other stakeholders of the system.
Class Diagram (Class Diagram)
A Class Diagram is a diagram that shows classes and interfaces and their relationships. However a class diagram may also show packages and all kind of classifier elements.
Component Diagram (Component Diagram)
A Component Diagram is a diagram that shows components, interfaces and artifacts and their relationships. However a component diagram may also show packages and all kind of classifier elements.
Deployment Diagram (Deployment Diagram)
A Deployment Diagram is a diagram that shows nodes and artifacts and their relationships. However a deployment diagram may also show packages and all kind of classifier elements.
Freeform Diagram (Freeform Diagram)
A Free Form diagram is a diagram in which you can make free drawings without the restriction of using UML.
Interaction Overview Diagram (Interaction Overview Diagram)
An Interaction Overview Diagram is a visual representation of a control flow of interaction..
Object Diagram (Object Diagram)
An Object Diagram is a diagram that shows instance specification, links and slots.
Use Case Diagram (Use Case Diagram)
A Use-Case Diagram is a diagram that shows actors and use cases and their relationships. However a Use-Case Diagram may also show packages and all kind of classifier elements.
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.
Component Realization (Component Realization)
The realization concept is specialized to (optionally) define the classifiers that realize the contract offered by a component in terms of its provided and required interfaces.
The component forms an abstraction from these various
classifiers.
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).
Element Import (Element Import)
An element import identifies an element in another package, and allows the element to be referenced using its name without a qualifier.
Generalization (Generalization)
A generalization is a taxonomic relationship between a more general classifier and a more specific classifier. Each instance of the specific classifier is also an indirect instance of the general classifier. Thus, the specific classifier inherits the features of the more general classifier.
A generalization relates a specific classifier to a more general classifier, and is owned by the specific classifier.
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.
Package Import (Package Import)
A package import is a relationship that allows the use of unqualified names to refer to package members from other namespaces.
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.
Templatebinding (Templatebinding)
A template binding represents a relationship between a templateable element and a template. A template binding specifies the substitutions of actual parameters for the formal parameters of the template.
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.
Action Input Pin (Pin)Activity Parameter Node (Object Node)Association End (Association End)Attribute (Attribute)Central Buffer (Object Node)Data Store Node (Object Node)Expansion Node (Object Node)Input Pin (Pin)Output Pin (Pin)Parameter (Parameter)Port (Port)Value Pin (Pin)Abstraction (Abstraction)Component Realization (Component Realization)Dependency (Dependency)Element Import (Element Import)Generalization (Generalization)Information Flow (Information Flow)Manifestation (Manifestation)Realization (Realization)Substitution (Substitution)Usage (Usage) ProtocolOnly available together with the Real-Time Extension of RSA.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
If true, the Classifier does not provide a complete declaration and can typically not be instantiated.
An abstract classifier is intended to be used by other classifiers e.g. as the target of general metarelationships or generalization relationships.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interface (Interface)
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
Model (Model)
A model captures a view of a physical system. It is an abstraction of the physical system, with a certain purpose.
This purpose determines what is to be included in the model and what is irrelevant. Thus the model completely describes those aspects of the physical system that are relevant to the purpose of the model, at the appropriate level of detail.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Package (Package)
A package is used to group elements, and provides a namespace for the grouped elements.
A package can have one or more profile applications to indicate which profiles have been applied.
Profile (Profile)
A profile defines limited extensions to a reference metamodel with the purpose of adapting the metamodel to a specific platform or domain.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
Template Parameter (Template Parameter)
A template parameter exposes a parameterable element as a formal template parameter of a template.
Association End (Association End)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An association End is a property that has a reference to an association.
Attribute (Attribute)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An attribute is a property that has no reference to an association.
Call Event (Call Event)
A call event models the receipt by an object of a message invoking a call of an operation.
Collaboration Use (Collaboration Use)
A collaboration use represents one particular use of a collaboration to explain the relationships between the properties of a classifier.
A collaboration use shows how the pattern described by a collaboration is applied in a given context, by binding specific entities from that context to the roles of the collaboration. Depending on the context, these entities could be structural features of a classifier, instance specifications, or even roles in some containing collaboration. There may be multiple occurrences of a given collaboration within a classifier, each involving a different set of roles and connectors.
A given role or connector may be involved in multiple occurrences of the same or different collaborations. Associated dependencies map features of the collaboration type to features in the classifier. These dependencies indicate which role in the classifier plays which role in the collaboration.
Constraint (Constraint)
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.
Port (Port)
A port is a property of a classifier that specifies a distinct interaction point between that classifier and its environment or between the (behavior of the) classifier and its internal parts.
Ports are connected to properties of the classifier by connectors through which requests can be made to invoke the behavioral features of a classifier.
A Port may specify the services a classifier provides (offers) to its environment as well as the services that a classifier expects (requires) of its environment. A port has an associated protocol state machine.
Template Signature (Template Signature)
A template signature bundles the set of formal template parameters for a templated element.
Use Case (Use Case)
A use case is the specification of a set of actions performed by a system, which yields an observable result that is, typically, of value for one or more actors or other stakeholders of the system.
Class Diagram (Class Diagram)
A Class Diagram is a diagram that shows classes and interfaces and their relationships. However a class diagram may also show packages and all kind of classifier elements.
Component Diagram (Component Diagram)
A Component Diagram is a diagram that shows components, interfaces and artifacts and their relationships. However a component diagram may also show packages and all kind of classifier elements.
Deployment Diagram (Deployment Diagram)
A Deployment Diagram is a diagram that shows nodes and artifacts and their relationships. However a deployment diagram may also show packages and all kind of classifier elements.
Freeform Diagram (Freeform Diagram)
A Free Form diagram is a diagram in which you can make free drawings without the restriction of using UML.
Interaction Overview Diagram (Interaction Overview Diagram)
An Interaction Overview Diagram is a visual representation of a control flow of interaction..
Object Diagram (Object Diagram)
An Object Diagram is a diagram that shows instance specification, links and slots.
Use Case Diagram (Use Case Diagram)
A Use-Case Diagram is a diagram that shows actors and use cases and their relationships. However a Use-Case Diagram may also show packages and all kind of classifier elements.
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.
Component Realization (Component Realization)
The realization concept is specialized to (optionally) define the classifiers that realize the contract offered by a component in terms of its provided and required interfaces.
The component forms an abstraction from these various
classifiers.
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).
Element Import (Element Import)
An element import identifies an element in another package, and allows the element to be referenced using its name without a qualifier.
Generalization (Generalization)
A generalization is a taxonomic relationship between a more general classifier and a more specific classifier. Each instance of the specific classifier is also an indirect instance of the general classifier. Thus, the specific classifier inherits the features of the more general classifier.
A generalization relates a specific classifier to a more general classifier, and is owned by the specific classifier.
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.
Package Import (Package Import)
A package import is a relationship that allows the use of unqualified names to refer to package members from other namespaces.
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.
Templatebinding (Templatebinding)
A template binding represents a relationship between a templateable element and a template. A template binding specifies the substitutions of actual parameters for the formal parameters of the template.
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.
Action Input Pin (Pin)Activity Parameter Node (Object Node)Association End (Association End)Attribute (Attribute)Central Buffer (Object Node)Data Store Node (Object Node)Expansion Node (Object Node)Input Pin (Pin)Output Pin (Pin)Parameter (Parameter)Port (Port)Value Pin (Pin)Abstraction (Abstraction)Component Realization (Component Realization)Dependency (Dependency)Element Import (Element Import)Generalization (Generalization)Information Flow (Information Flow)Manifestation (Manifestation)Realization (Realization)Substitution (Substitution)Usage (Usage) SignalA signal is a specification of send request instances communicated between objects. The receiving object handles the received request instances as specified by its receptions. The data carried by a send request (which was passed to it by the send invocation occurrence that caused that request) are represented as attributes of the signal.
A signal is defined independently of the classifiers handling the signal occurrence.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
If true, the Classifier does not provide a complete declaration and can typically not be instantiated.
An abstract classifier is intended to be used by other classifiers e.g. as the target of general metarelationships or generalization relationships.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interface (Interface)
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
Model (Model)
A model captures a view of a physical system. It is an abstraction of the physical system, with a certain purpose.
This purpose determines what is to be included in the model and what is irrelevant. Thus the model completely describes those aspects of the physical system that are relevant to the purpose of the model, at the appropriate level of detail.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Package (Package)
A package is used to group elements, and provides a namespace for the grouped elements.
A package can have one or more profile applications to indicate which profiles have been applied.
Profile (Profile)
A profile defines limited extensions to a reference metamodel with the purpose of adapting the metamodel to a specific platform or domain.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
Template Parameter (Template Parameter)
A template parameter exposes a parameterable element as a formal template parameter of a template.
Association End (Association End)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An association End is a property that has a reference to an association.
Attribute (Attribute)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An attribute is a property that has no reference to an association.
Collaboration Use (Collaboration Use)
A collaboration use represents one particular use of a collaboration to explain the relationships between the properties of a classifier.
A collaboration use shows how the pattern described by a collaboration is applied in a given context, by binding specific entities from that context to the roles of the collaboration. Depending on the context, these entities could be structural features of a classifier, instance specifications, or even roles in some containing collaboration. There may be multiple occurrences of a given collaboration within a classifier, each involving a different set of roles and connectors.
A given role or connector may be involved in multiple occurrences of the same or different collaborations. Associated dependencies map features of the collaboration type to features in the classifier. These dependencies indicate which role in the classifier plays which role in the collaboration.
Constraint (Constraint)
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.
Port (Port)
A port is a property of a classifier that specifies a distinct interaction point between that classifier and its environment or between the (behavior of the) classifier and its internal parts.
Ports are connected to properties of the classifier by connectors through which requests can be made to invoke the behavioral features of a classifier.
A Port may specify the services a classifier provides (offers) to its environment as well as the services that a classifier expects (requires) of its environment. A port has an associated protocol state machine.
Template Signature (Template Signature)
A template signature bundles the set of formal template parameters for a templated element.
Use Case (Use Case)
A use case is the specification of a set of actions performed by a system, which yields an observable result that is, typically, of value for one or more actors or other stakeholders of the system.
Class Diagram (Class Diagram)
A Class Diagram is a diagram that shows classes and interfaces and their relationships. However a class diagram may also show packages and all kind of classifier elements.
Component Diagram (Component Diagram)
A Component Diagram is a diagram that shows components, interfaces and artifacts and their relationships. However a component diagram may also show packages and all kind of classifier elements.
Deployment Diagram (Deployment Diagram)
A Deployment Diagram is a diagram that shows nodes and artifacts and their relationships. However a deployment diagram may also show packages and all kind of classifier elements.
Freeform Diagram (Freeform Diagram)
A Free Form diagram is a diagram in which you can make free drawings without the restriction of using UML.
Interaction Overview Diagram (Interaction Overview Diagram)
An Interaction Overview Diagram is a visual representation of a control flow of interaction..
Object Diagram (Object Diagram)
An Object Diagram is a diagram that shows instance specification, links and slots.
Use Case Diagram (Use Case Diagram)
A Use-Case Diagram is a diagram that shows actors and use cases and their relationships. However a Use-Case Diagram may also show packages and all kind of classifier elements.
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.
Component Realization (Component Realization)
The realization concept is specialized to (optionally) define the classifiers that realize the contract offered by a component in terms of its provided and required interfaces.
The component forms an abstraction from these various
classifiers.
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).
Element Import (Element Import)
An element import identifies an element in another package, and allows the element to be referenced using its name without a qualifier.
Generalization (Generalization)
A generalization is a taxonomic relationship between a more general classifier and a more specific classifier. Each instance of the specific classifier is also an indirect instance of the general classifier. Thus, the specific classifier inherits the features of the more general classifier.
A generalization relates a specific classifier to a more general classifier, and is owned by the specific classifier.
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.
Package Import (Package Import)
A package import is a relationship that allows the use of unqualified names to refer to package members from other namespaces.
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.
Templatebinding (Templatebinding)
A template binding represents a relationship between a templateable element and a template. A template binding specifies the substitutions of actual parameters for the formal parameters of the template.
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.
Action Input Pin (Pin)Activity Parameter Node (Object Node)Association End (Association End)Attribute (Attribute)Central Buffer (Object Node)Data Store Node (Object Node)Expansion Node (Object Node)Input Pin (Pin)Output Pin (Pin)Parameter (Parameter)Port (Port)Value Pin (Pin)Reception (Reception)Abstraction (Abstraction)Component Realization (Component Realization)Dependency (Dependency)Element Import (Element Import)Generalization (Generalization)Information Flow (Information Flow)Manifestation (Manifestation)Realization (Realization)Substitution (Substitution)Usage (Usage)
Send Signal Action (Action) StereotypeA stereotype defines how an existing metaclass 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.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
If true, the Classifier does not provide a complete declaration and can typically not be instantiated.
An abstract classifier is intended to be used by other classifiers e.g. as the target of general metarelationships or generalization relationships.
Determines whether an object specified by this classifier is active or not. If true, then the owning classifier is referred to as an active classifier. If false, then such a classifier is referred to as a passive classifier.
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.
Category is used to group stereotype properties under the same logical name. If the category is not empty, stereotype properties will be grouped under the category name in the Property View.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Association (Association)
An association describes a set of tuples whose values refer to typed instances. An instance of an association is called a link.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
Communication Path (Communication Path)
A communication path is an association between two deployment targets, through which they are able to exchange signals and messages.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Extension (Extension)
An extension is used to indicate that the properties of a metaclass are extended through a stereotype, and gives the ability to flexibly add (and later remove) stereotypes to classes.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interface (Interface)
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
Model (Model)
A model captures a view of a physical system. It is an abstraction of the physical system, with a certain purpose.
This purpose determines what is to be included in the model and what is irrelevant. Thus the model completely describes those aspects of the physical system that are relevant to the purpose of the model, at the appropriate level of detail.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Package (Package)
A package is used to group elements, and provides a namespace for the grouped elements.
A package can have one or more profile applications to indicate which profiles have been applied.
Profile (Profile)
A profile defines limited extensions to a reference metamodel with the purpose of adapting the metamodel to a specific platform or domain.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
Template Parameter (Template Parameter)
A template parameter exposes a parameterable element as a formal template parameter of a template.
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Actor (Actor)
An actor specifies a role played by a user or any other system that interacts with the subject.
Artifact (Artifact)
An artifact is the specification of a physical piece of information that is used or produced by a software development process, or by deployment and operation of a system.
Examples of artifacts include model files, source files, scripts, and binary executable files, a table in a database system, a development deliverable, or a word-processing document, a mail message. An artifact is the source of a deployment to a node.
Association (Association)
An association describes a set of tuples whose values refer to typed instances. An instance of an association is called a link.
Association End (Association End)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An association End is a property that has a reference to an association.
Attribute (Attribute)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An attribute is a property that has no reference to an association.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
Collaboration (Collaboration)
A collaboration defines a set of co-operating roles used collectively to illustrate a specific functionality.
A collaboration should only show the roles and attributes required to accomplish its defined task or function. Isolating the primary roles is an exercise in simplifying the structure and clarifying the behavior, and also provides for re-use. A collaboration often implements a pattern.
Collaboration Use (Collaboration Use)
A collaboration use represents one particular use of a collaboration to explain the relationships between the properties of a classifier.
A collaboration use shows how the pattern described by a collaboration is applied in a given context, by binding specific entities from that context to the roles of the collaboration. Depending on the context, these entities could be structural features of a classifier, instance specifications, or even roles in some containing collaboration. There may be multiple occurrences of a given collaboration within a classifier, each involving a different set of roles and connectors.
A given role or connector may be involved in multiple occurrences of the same or different collaborations. Associated dependencies map features of the collaboration type to features in the classifier. These dependencies indicate which role in the classifier plays which role in the collaboration.
Communication Path (Communication Path)
A communication path is an association between two deployment targets, through which they are able to exchange signals and messages.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Connector (Connector)
Specifies a link that enables communication between two or more instances. This link may be an instance of anassociation, or it may represent the possibility of the instances being able to communicate because their identitiesare known by virtue of being passed in as parameters, held in variables or slots, or because the communicatinginstances are the same instance.
The link may be realized by something as simple as a pointer or by something ascomplex as a network connection. In contrast to associations, which specify links between any instance of theassociated classifiers, connectors specify links between instances playing the connected parts only.
Constraint (Constraint)
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.
Data Type (Data Type)
A data type is a type whose instances are identified only by their value. A data type may contain attributes to support the modeling of structured data types.
Deployment Specification (Deployment Specification)
A deployment specification specifies a set of properties that determine execution parameters of a component artifact that is deployed on a node.
A deployment specification can be aimed at a specific type of container. An artifact that reifies or implements deployment specification properties is a deployment descriptor.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Enumeration (Enumeration)
An enumeration is a data type whose values are enumerated in the model as enumeration literals.
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Extension (Extension)
An extension is used to indicate that the properties of a metaclass are extended through a stereotype, and gives the ability to flexibly add (and later remove) stereotypes to classes.
Information Item (Information Item)
An information item is an abstraction of all kinds of information that can be exchanged between objects. It is a kind of
classifier intended for representing information in a very abstract way, one which cannot be instantiated.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interface (Interface)
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Operation (Operation)
An operation is a behavioral feature of a classifier that specifies the name, type, parameters, and constraints for invoking an associated behavior. An operation may invoke both the execution of method behaviors as well as other behavioral responses.
Port (Port)
A port is a property of a classifier that specifies a distinct interaction point between that classifier and its environment or between the (behavior of the) classifier and its internal parts.
Ports are connected to properties of the classifier by connectors through which requests can be made to invoke the behavioral features of a classifier.
A Port may specify the services a classifier provides (offers) to its environment as well as the services that a classifier expects (requires) of its environment. A port has an associated protocol state machine.
Primitive Type (Primitive Type)
A primitive type defines a predefined data type, without any relevant substructure (i.e., it has no parts in the context of UML). A primitive datatype may have an algebra and operations defined outside of UML, for example, mathematically.
Protocol (Protocol)
Only available together with the Real-Time Extension of RSA.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
Reception (Reception)
A reception is a declaration stating that a classifier is prepared to react to the receipt of a signal. A reception designates a signal and specifies the expected behavioral response.
The details of handling a signal are specified by the behavior associated with the reception or the classifier itself.
Signal (Signal)
A signal is a specification of send request instances communicated between objects. The receiving object handles the received request instances as specified by its receptions. The data carried by a send request (which was passed to it by the send invocation occurrence that caused that request) are represented as attributes of the signal.
A signal is defined independently of the classifiers handling the signal occurrence.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
Template Signature (Template Signature)
A template signature bundles the set of formal template parameters for a templated element.
Trigger (Trigger)
A trigger relates an event to a behavior that may affect an instance of the classifier. A trigger specification may be qualified by the port on which the event occurred.
Use Case (Use Case)
A use case is the specification of a set of actions performed by a system, which yields an observable result that is, typically, of value for one or more actors or other stakeholders of the system.
Class Diagram (Class Diagram)
A Class Diagram is a diagram that shows classes and interfaces and their relationships. However a class diagram may also show packages and all kind of classifier elements.
Component Diagram (Component Diagram)
A Component Diagram is a diagram that shows components, interfaces and artifacts and their relationships. However a component diagram may also show packages and all kind of classifier elements.
Deployment Diagram (Deployment Diagram)
A Deployment Diagram is a diagram that shows nodes and artifacts and their relationships. However a deployment diagram may also show packages and all kind of classifier elements.
Freeform Diagram (Freeform Diagram)
A Free Form diagram is a diagram in which you can make free drawings without the restriction of using UML.
Interaction Overview Diagram (Interaction Overview Diagram)
An Interaction Overview Diagram is a visual representation of a control flow of interaction..
Object Diagram (Object Diagram)
An Object Diagram is a diagram that shows instance specification, links and slots.
Structure Diagram (Structure Diagram)
A Structure Diagram is a diagram that shows the static structure of an element.
Use Case Diagram (Use Case Diagram)
A Use-Case Diagram is a diagram that shows actors and use cases and their relationships. However a Use-Case Diagram may also show packages and all kind of classifier elements.
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.
Component Realization (Component Realization)
The realization concept is specialized to (optionally) define the classifiers that realize the contract offered by a component in terms of its provided and required interfaces.
The component forms an abstraction from these various
classifiers.
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).
Element Import (Element Import)
An element import identifies an element in another package, and allows the element to be referenced using its name without a qualifier.
Generalization (Generalization)
A generalization is a taxonomic relationship between a more general classifier and a more specific classifier. Each instance of the specific classifier is also an indirect instance of the general classifier. Thus, the specific classifier inherits the features of the more general classifier.
A generalization relates a specific classifier to a more general classifier, and is owned by the specific classifier.
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.
Interface Realization (Interface Realization)
An interface realization is a specialized realization relationship between a classifier and an interface. This relationship signifies that the realizing classifier conforms to the contract specified by the interface.
Package Import (Package Import)
A package import is a relationship that allows the use of unqualified names to refer to package members from other namespaces.
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.
Templatebinding (Templatebinding)
A template binding represents a relationship between a templateable element and a template. A template binding specifies the substitutions of actual parameters for the formal parameters of the template.
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.
Action Input Pin (Pin)Activity Parameter Node (Object Node)Association End (Association End)Attribute (Attribute)Central Buffer (Object Node)Data Store Node (Object Node)Expansion Node (Object Node)Input Pin (Pin)Output Pin (Pin)Parameter (Parameter)Port (Port)Value Pin (Pin)Abstraction (Abstraction)Component Realization (Component Realization)Dependency (Dependency)Element Import (Element Import)Generalization (Generalization)Information Flow (Information Flow)Manifestation (Manifestation)Realization (Realization)Substitution (Substitution)Usage (Usage) Use CaseA use case is the specification of a set of actions performed by a system, which yields an observable result that is, typically, of value for one or more actors or other stakeholders of the system.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
If true, the Classifier does not provide a complete declaration and can typically not be instantiated.
An abstract classifier is intended to be used by other classifiers e.g. as the target of general metarelationships or generalization relationships.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Actor (Actor)
An actor specifies a role played by a user or any other system that interacts with the subject.
Artifact (Artifact)
An artifact is the specification of a physical piece of information that is used or produced by a software development process, or by deployment and operation of a system.
Examples of artifacts include model files, source files, scripts, and binary executable files, a table in a database system, a development deliverable, or a word-processing document, a mail message. An artifact is the source of a deployment to a node.
Association (Association)
An association describes a set of tuples whose values refer to typed instances. An instance of an association is called a link.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
Collaboration (Collaboration)
A collaboration defines a set of co-operating roles used collectively to illustrate a specific functionality.
A collaboration should only show the roles and attributes required to accomplish its defined task or function. Isolating the primary roles is an exercise in simplifying the structure and clarifying the behavior, and also provides for re-use. A collaboration often implements a pattern.
Communication Path (Communication Path)
A communication path is an association between two deployment targets, through which they are able to exchange signals and messages.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Data Type (Data Type)
A data type is a type whose instances are identified only by their value. A data type may contain attributes to support the modeling of structured data types.
Deployment Specification (Deployment Specification)
A deployment specification specifies a set of properties that determine execution parameters of a component artifact that is deployed on a node.
A deployment specification can be aimed at a specific type of container. An artifact that reifies or implements deployment specification properties is a deployment descriptor.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Enumeration (Enumeration)
An enumeration is a data type whose values are enumerated in the model as enumeration literals.
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Extension (Extension)
An extension is used to indicate that the properties of a metaclass are extended through a stereotype, and gives the ability to flexibly add (and later remove) stereotypes to classes.
Information Item (Information Item)
An information item is an abstraction of all kinds of information that can be exchanged between objects. It is a kind of
classifier intended for representing information in a very abstract way, one which cannot be instantiated.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interface (Interface)
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
Model (Model)
A model captures a view of a physical system. It is an abstraction of the physical system, with a certain purpose.
This purpose determines what is to be included in the model and what is irrelevant. Thus the model completely describes those aspects of the physical system that are relevant to the purpose of the model, at the appropriate level of detail.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Package (Package)
A package is used to group elements, and provides a namespace for the grouped elements.
A package can have one or more profile applications to indicate which profiles have been applied.
Primitive Type (Primitive Type)
A primitive type defines a predefined data type, without any relevant substructure (i.e., it has no parts in the context of UML). A primitive datatype may have an algebra and operations defined outside of UML, for example, mathematically.
Profile (Profile)
A profile defines limited extensions to a reference metamodel with the purpose of adapting the metamodel to a specific platform or domain.
Protocol (Protocol)
Only available together with the Real-Time Extension of RSA.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
Signal (Signal)
A signal is a specification of send request instances communicated between objects. The receiving object handles the received request instances as specified by its receptions. The data carried by a send request (which was passed to it by the send invocation occurrence that caused that request) are represented as attributes of the signal.
A signal is defined independently of the classifiers handling the signal occurrence.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
Template Parameter (Template Parameter)
A template parameter exposes a parameterable element as a formal template parameter of a template.
Use Case (Use Case)
A use case is the specification of a set of actions performed by a system, which yields an observable result that is, typically, of value for one or more actors or other stakeholders of the system.
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Association End (Association End)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An association End is a property that has a reference to an association.
Collaboration Use (Collaboration Use)
A collaboration use represents one particular use of a collaboration to explain the relationships between the properties of a classifier.
A collaboration use shows how the pattern described by a collaboration is applied in a given context, by binding specific entities from that context to the roles of the collaboration. Depending on the context, these entities could be structural features of a classifier, instance specifications, or even roles in some containing collaboration. There may be multiple occurrences of a given collaboration within a classifier, each involving a different set of roles and connectors.
A given role or connector may be involved in multiple occurrences of the same or different collaborations. Associated dependencies map features of the collaboration type to features in the classifier. These dependencies indicate which role in the classifier plays which role in the collaboration.
Constraint (Constraint)
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.
Extension Point (Extension Point)
An extension point identifies a point in the behavior of a use case where that behavior can be extended by the behavior of some other (extending) use case, as specified by an extend relationship.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Template Signature (Template Signature)
A template signature bundles the set of formal template parameters for a templated element.
Trigger (Trigger)
A trigger relates an event to a behavior that may affect an instance of the classifier. A trigger specification may be qualified by the port on which the event occurred.
Use Case (Use Case)
A use case is the specification of a set of actions performed by a system, which yields an observable result that is, typically, of value for one or more actors or other stakeholders of the system.
Activity (Activity)Actor (Actor)Artifact (Artifact)Association (Association)Class (Class)Collaboration (Collaboration)Communication Path (Communication Path)Component (Component)Data Type (Data Type)Deployment Specification (Deployment Specification)Device (Device)Enumeration (Enumeration)Execution Environment (Execution Environment)Extension (Extension)Information Item (Information Item)Interaction (Interaction)Interface (Interface)Node (Node)Opaque Behavior (Opaque Behavior)Primitive Type (Primitive Type)Protocol (Protocol)Protocol State Machine (Protocol State Machine)Signal (Signal)State Machine (State Machine)Stereotype (Stereotype)Use Case (Use Case)Class Diagram (Class Diagram)
A Class Diagram is a diagram that shows classes and interfaces and their relationships. However a class diagram may also show packages and all kind of classifier elements.
Component Diagram (Component Diagram)
A Component Diagram is a diagram that shows components, interfaces and artifacts and their relationships. However a component diagram may also show packages and all kind of classifier elements.
Deployment Diagram (Deployment Diagram)
A Deployment Diagram is a diagram that shows nodes and artifacts and their relationships. However a deployment diagram may also show packages and all kind of classifier elements.
Freeform Diagram (Freeform Diagram)
A Free Form diagram is a diagram in which you can make free drawings without the restriction of using UML.
Interaction Overview Diagram (Interaction Overview Diagram)
An Interaction Overview Diagram is a visual representation of a control flow of interaction..
Object Diagram (Object Diagram)
An Object Diagram is a diagram that shows instance specification, links and slots.
Use Case Diagram (Use Case Diagram)
A Use-Case Diagram is a diagram that shows actors and use cases and their relationships. However a Use-Case Diagram may also show packages and all kind of classifier elements.
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.
Component Realization (Component Realization)
The realization concept is specialized to (optionally) define the classifiers that realize the contract offered by a component in terms of its provided and required interfaces.
The component forms an abstraction from these various
classifiers.
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).
Element Import (Element Import)
An element import identifies an element in another package, and allows the element to be referenced using its name without a qualifier.
Extend (Extend)
A relationship from an extending use case to an extended use case that specifies how and when the behavior defined in the extending use case can be inserted into the behavior defined in the extended use case.
Generalization (Generalization)
A generalization is a taxonomic relationship between a more general classifier and a more specific classifier. Each instance of the specific classifier is also an indirect instance of the general classifier. Thus, the specific classifier inherits the features of the more general classifier.
A generalization relates a specific classifier to a more general classifier, and is owned by the specific classifier.
Include (Include)
An include relationship defines that a use case contains the behavior defined in another use case.
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.
Interface Realization (Interface Realization)
An interface realization is a specialized realization relationship between a classifier and an interface. This relationship signifies that the realizing classifier conforms to the contract specified by the interface.
Package Import (Package Import)
A package import is a relationship that allows the use of unqualified names to refer to package members from other namespaces.
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.
Templatebinding (Templatebinding)
A template binding represents a relationship between a templateable element and a template. A template binding specifies the substitutions of actual parameters for the formal parameters of the template.
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.
Action Input Pin (Pin)Activity Parameter Node (Object Node)Association End (Association End)Attribute (Attribute)Central Buffer (Object Node)Data Store Node (Object Node)Expansion Node (Object Node)Input Pin (Pin)Output Pin (Pin)Parameter (Parameter)Port (Port)Value Pin (Pin)Abstraction (Abstraction)Component Realization (Component Realization)Dependency (Dependency)Element Import (Element Import)Extend (Extend)Generalization (Generalization)Include (Include)Information Flow (Information Flow)Manifestation (Manifestation)Realization (Realization)Substitution (Substitution)Usage (Usage) Association EndA property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An association End is a property that has a reference to an association.
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.
A String that is evaluated to give a default value for the Property when an object of the owning Classifier is instantiated.
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.
Specifies the kind of aggregation that applies to the Property.
If isDerived is true, the value of the attribute is derived from information elsewhere. Specifies whether the Property is derived, i.e., whether its value or values can be computed from other information.
Specifies whether the property is derived as the union of all of the properties that are constrained to subset it.
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.
A property is navigable if it is possible to navigate from an instance of the owner of the property to an instance of the type of the property.
For a multivalued multiplicity, this attribute specifies whether the values in an instantiation of this element are sequentially ordered.
States whether the attribute's value may be modified by a client.
Specifies whether this feature characterizes individual instances classified by the classifier (false) or the classifier itself (true).
For a multivalued multiplicity, this attributes specifies whether the values in an instantiation of this element are unique.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Actor (Actor)
An actor specifies a role played by a user or any other system that interacts with the subject.
Artifact (Artifact)
An artifact is the specification of a physical piece of information that is used or produced by a software development process, or by deployment and operation of a system.
Examples of artifacts include model files, source files, scripts, and binary executable files, a table in a database system, a development deliverable, or a word-processing document, a mail message. An artifact is the source of a deployment to a node.
Association (Association)
An association describes a set of tuples whose values refer to typed instances. An instance of an association is called a link.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
Collaboration (Collaboration)
A collaboration defines a set of co-operating roles used collectively to illustrate a specific functionality.
A collaboration should only show the roles and attributes required to accomplish its defined task or function. Isolating the primary roles is an exercise in simplifying the structure and clarifying the behavior, and also provides for re-use. A collaboration often implements a pattern.
Communication Path (Communication Path)
A communication path is an association between two deployment targets, through which they are able to exchange signals and messages.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Data Type (Data Type)
A data type is a type whose instances are identified only by their value. A data type may contain attributes to support the modeling of structured data types.
Deployment Specification (Deployment Specification)
A deployment specification specifies a set of properties that determine execution parameters of a component artifact that is deployed on a node.
A deployment specification can be aimed at a specific type of container. An artifact that reifies or implements deployment specification properties is a deployment descriptor.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Enumeration (Enumeration)
An enumeration is a data type whose values are enumerated in the model as enumeration literals.
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Extension (Extension)
An extension is used to indicate that the properties of a metaclass are extended through a stereotype, and gives the ability to flexibly add (and later remove) stereotypes to classes.
Information Item (Information Item)
An information item is an abstraction of all kinds of information that can be exchanged between objects. It is a kind of
classifier intended for representing information in a very abstract way, one which cannot be instantiated.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interface (Interface)
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Primitive Type (Primitive Type)
A primitive type defines a predefined data type, without any relevant substructure (i.e., it has no parts in the context of UML). A primitive datatype may have an algebra and operations defined outside of UML, for example, mathematically.
Protocol (Protocol)
Only available together with the Real-Time Extension of RSA.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
Signal (Signal)
A signal is a specification of send request instances communicated between objects. The receiving object handles the received request instances as specified by its receptions. The data carried by a send request (which was passed to it by the send invocation occurrence that caused that request) are represented as attributes of the signal.
A signal is defined independently of the classifiers handling the signal occurrence.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
Template Parameter (Template Parameter)
A template parameter exposes a parameterable element as a formal template parameter of a template.
Use Case (Use Case)
A use case is the specification of a set of actions performed by a system, which yields an observable result that is, typically, of value for one or more actors or other stakeholders of the system.
An item of one of the following item kinds:
Activity (Activity)Actor (Actor)Artifact (Artifact)Association (Association)Class (Class)Collaboration (Collaboration)Communication Path (Communication Path)Component (Component)Data Type (Data Type)Deployment Specification (Deployment Specification)Device (Device)Enumeration (Enumeration)Execution Environment (Execution Environment)Extension (Extension)Information Item (Information Item)Interaction (Interaction)Interface (Interface)Node (Node)Opaque Behavior (Opaque Behavior)Primitive Type (Primitive Type)Protocol (Protocol)Protocol State Machine (Protocol State Machine)Signal (Signal)State Machine (State Machine)Stereotype (Stereotype)Use Case (Use Case)An item of one of the following item kinds:
Association (Association)Communication Path (Communication Path)Extension (Extension)
Connector End (Connector End)
Slot (Slot)Connector End (Connector End)Abstraction (Abstraction)Dependency (Dependency)Deployment (Deployment)Information Flow (Information Flow)Realization (Realization)Substitution (Substitution)Usage (Usage)Connector End (Connector End) AttributeA property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An attribute is a property that has no reference to an association.
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.
A String that is evaluated to give a default value for the Property when an object of the owning Classifier is instantiated.
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.
Specifies the kind of aggregation that applies to the Property.
If isDerived is true, the value of the attribute is derived from information elsewhere. Specifies whether the Property is derived, i.e., whether its value or values can be computed from other information.
Specifies whether the property is derived as the union of all of the properties that are constrained to subset it.
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.
A property is navigable if it is possible to navigate from an instance of the owner of the property to an instance of the type of the property.
For a multivalued multiplicity, this attribute specifies whether the values in an instantiation of this element are sequentially ordered.
States whether the attribute's value may be modified by a client.
Specifies whether this feature characterizes individual instances classified by the classifier (false) or the classifier itself (true).
For a multivalued multiplicity, this attributes specifies whether the values in an instantiation of this element are unique.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Artifact (Artifact)
An artifact is the specification of a physical piece of information that is used or produced by a software development process, or by deployment and operation of a system.
Examples of artifacts include model files, source files, scripts, and binary executable files, a table in a database system, a development deliverable, or a word-processing document, a mail message. An artifact is the source of a deployment to a node.
Association End (Association End)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An association End is a property that has a reference to an association.
Attribute (Attribute)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An attribute is a property that has no reference to an association.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
Collaboration (Collaboration)
A collaboration defines a set of co-operating roles used collectively to illustrate a specific functionality.
A collaboration should only show the roles and attributes required to accomplish its defined task or function. Isolating the primary roles is an exercise in simplifying the structure and clarifying the behavior, and also provides for re-use. A collaboration often implements a pattern.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Data Type (Data Type)
A data type is a type whose instances are identified only by their value. A data type may contain attributes to support the modeling of structured data types.
Deployment Specification (Deployment Specification)
A deployment specification specifies a set of properties that determine execution parameters of a component artifact that is deployed on a node.
A deployment specification can be aimed at a specific type of container. An artifact that reifies or implements deployment specification properties is a deployment descriptor.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Enumeration (Enumeration)
An enumeration is a data type whose values are enumerated in the model as enumeration literals.
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interface (Interface)
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Port (Port)
A port is a property of a classifier that specifies a distinct interaction point between that classifier and its environment or between the (behavior of the) classifier and its internal parts.
Ports are connected to properties of the classifier by connectors through which requests can be made to invoke the behavioral features of a classifier.
A Port may specify the services a classifier provides (offers) to its environment as well as the services that a classifier expects (requires) of its environment. A port has an associated protocol state machine.
Primitive Type (Primitive Type)
A primitive type defines a predefined data type, without any relevant substructure (i.e., it has no parts in the context of UML). A primitive datatype may have an algebra and operations defined outside of UML, for example, mathematically.
Protocol (Protocol)
Only available together with the Real-Time Extension of RSA.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
Signal (Signal)
A signal is a specification of send request instances communicated between objects. The receiving object handles the received request instances as specified by its receptions. The data carried by a send request (which was passed to it by the send invocation occurrence that caused that request) are represented as attributes of the signal.
A signal is defined independently of the classifiers handling the signal occurrence.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
Template Parameter (Template Parameter)
A template parameter exposes a parameterable element as a formal template parameter of a template.
Attribute (Attribute)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An attribute is a property that has no reference to an association.
Template Signature (Template Signature)
A template signature bundles the set of formal template parameters for a templated element.
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.
Templatebinding (Templatebinding)
A template binding represents a relationship between a templateable element and a template. A template binding specifies the substitutions of actual parameters for the formal parameters of the template.
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.
Connector End (Connector End)Slot (Slot)Connector End (Connector End)Abstraction (Abstraction)Dependency (Dependency)Deployment (Deployment)Information Flow (Information Flow)Realization (Realization)Substitution (Substitution)Usage (Usage)Connector End (Connector End) Call EventA call event models the receipt by an object of a message invoking a call of an operation.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
Operation.
Designates the operation whose invocation raised the call event.
An element of one of the following kinds:
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Model (Model)
A model captures a view of a physical system. It is an abstraction of the physical system, with a certain purpose.
This purpose determines what is to be included in the model and what is irrelevant. Thus the model completely describes those aspects of the physical system that are relevant to the purpose of the model, at the appropriate level of detail.
Package (Package)
A package is used to group elements, and provides a namespace for the grouped elements.
A package can have one or more profile applications to indicate which profiles have been applied.
Profile (Profile)
A profile defines limited extensions to a reference metamodel with the purpose of adapting the metamodel to a specific platform or domain.
Protocol (Protocol)
Only available together with the Real-Time Extension of RSA.
Template Parameter (Template Parameter)
A template parameter exposes a parameterable element as a formal template parameter of a template.
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.
Abstraction (Abstraction)Dependency (Dependency)Element Import (Element Import)Information Flow (Information Flow)Manifestation (Manifestation)Realization (Realization)Substitution (Substitution)Usage (Usage) Collaboration UseA collaboration use represents one particular use of a collaboration to explain the relationships between the properties of a classifier.
A collaboration use shows how the pattern described by a collaboration is applied in a given context, by binding specific entities from that context to the roles of the collaboration. Depending on the context, these entities could be structural features of a classifier, instance specifications, or even roles in some containing collaboration. There may be multiple occurrences of a given collaboration within a classifier, each involving a different set of roles and connectors.
A given role or connector may be involved in multiple occurrences of the same or different collaborations. Associated dependencies map features of the collaboration type to features in the classifier. These dependencies indicate which role in the classifier plays which role in the collaboration.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Actor (Actor)
An actor specifies a role played by a user or any other system that interacts with the subject.
Artifact (Artifact)
An artifact is the specification of a physical piece of information that is used or produced by a software development process, or by deployment and operation of a system.
Examples of artifacts include model files, source files, scripts, and binary executable files, a table in a database system, a development deliverable, or a word-processing document, a mail message. An artifact is the source of a deployment to a node.
Association (Association)
An association describes a set of tuples whose values refer to typed instances. An instance of an association is called a link.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
Collaboration (Collaboration)
A collaboration defines a set of co-operating roles used collectively to illustrate a specific functionality.
A collaboration should only show the roles and attributes required to accomplish its defined task or function. Isolating the primary roles is an exercise in simplifying the structure and clarifying the behavior, and also provides for re-use. A collaboration often implements a pattern.
Communication Path (Communication Path)
A communication path is an association between two deployment targets, through which they are able to exchange signals and messages.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Data Type (Data Type)
A data type is a type whose instances are identified only by their value. A data type may contain attributes to support the modeling of structured data types.
Deployment Specification (Deployment Specification)
A deployment specification specifies a set of properties that determine execution parameters of a component artifact that is deployed on a node.
A deployment specification can be aimed at a specific type of container. An artifact that reifies or implements deployment specification properties is a deployment descriptor.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Enumeration (Enumeration)
An enumeration is a data type whose values are enumerated in the model as enumeration literals.
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Extension (Extension)
An extension is used to indicate that the properties of a metaclass are extended through a stereotype, and gives the ability to flexibly add (and later remove) stereotypes to classes.
Information Item (Information Item)
An information item is an abstraction of all kinds of information that can be exchanged between objects. It is a kind of
classifier intended for representing information in a very abstract way, one which cannot be instantiated.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interface (Interface)
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Primitive Type (Primitive Type)
A primitive type defines a predefined data type, without any relevant substructure (i.e., it has no parts in the context of UML). A primitive datatype may have an algebra and operations defined outside of UML, for example, mathematically.
Protocol (Protocol)
Only available together with the Real-Time Extension of RSA.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
Signal (Signal)
A signal is a specification of send request instances communicated between objects. The receiving object handles the received request instances as specified by its receptions. The data carried by a send request (which was passed to it by the send invocation occurrence that caused that request) are represented as attributes of the signal.
A signal is defined independently of the classifiers handling the signal occurrence.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
Use Case (Use Case)
A use case is the specification of a set of actions performed by a system, which yields an observable result that is, typically, of value for one or more actors or other stakeholders of the system.
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.
Abstraction (Abstraction)Dependency (Dependency)Information Flow (Information Flow)Realization (Realization)Substitution (Substitution)Usage (Usage)
Connection Point ReferenceA connection point reference represents a usage (as part of a submachine state) of an entry/exit point defined in the statemachine reference by the submachine state.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
An element of one of the following kinds:
Final State (Final State)
A special kind of state signifying that the enclosing region is completed.
If the enclosing region is directly contained in a state machine and all other regions in the state machine also are completed, then it means that the entire state machine is completed.
Region (Region)
A region is an orthogonal part of either a composite state or a state machine. It contains states and transitions.
State (State)
A state models a situation during which some (usually implicit) invariant condition holds.
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.
Choice (Pseudo State)
Deep History (Pseudo State)
Entry Point (Pseudo State)
Exit Point (Pseudo State)
Fork (Pseudo State)
Initial (Pseudo State)
Join (Pseudo State)
Junction (Pseudo State)
Shallow History (Pseudo State)
Terminate (Pseudo State)Protocol Transition (Protocol Transition)Transition (Transition)Choice (Pseudo State)Deep History (Pseudo State)Entry Point (Pseudo State)Exit Point (Pseudo State)Fork (Pseudo State)Initial (Pseudo State)Join (Pseudo State)Junction (Pseudo State)Shallow History (Pseudo State)Terminate (Pseudo State)Protocol Transition (Protocol Transition)Transition (Transition)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.
Abstraction (Abstraction)Dependency (Dependency)Information Flow (Information Flow)Protocol Transition (Protocol Transition)Realization (Realization)Substitution (Substitution)Transition (Transition)Usage (Usage)Protocol Transition (Protocol Transition)Transition (Transition) Connector EndA connector end is an endpoint of a connector, which attaches the connector to a connectable element. Each connector end is
part of one connector.
A derived association referencing the corresponding association end on the association which types the connector owing this connector end.
This association is derived by selecting the association end at the same place in the ordering of association ends as this connector end.
Indicates the role of the internal structure of a classifier with the port to which the connector end is attached.
The connectable element attached at this connector end. When an instance of the containing classifier is created, a link may (depending on the multiplicities) be created to an instance of the classifier that types this connectable element.
Connector (Connector)
Specifies a link that enables communication between two or more instances. This link may be an instance of anassociation, or it may represent the possibility of the instances being able to communicate because their identitiesare known by virtue of being passed in as parameters, held in variables or slots, or because the communicatinginstances are the same instance.
The link may be realized by something as simple as a pointer or by something ascomplex as a network connection. In contrast to associations, which specify links between any instance of theassociated classifiers, connectors specify links between instances playing the connected parts only.
Enumeration LiteralAn enumeration literal is a user-defined data value for an enumeration.
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.
The classifier or classifiers of the represented instance. If multiple classifiers are specified, the instance is classified by all of them.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
An enumeration literal is a user-defined data value for an enumeration.
An element of one of the following kinds:
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Enumeration (Enumeration)
An enumeration is a data type whose values are enumerated in the model as enumeration literals.
Model (Model)
A model captures a view of a physical system. It is an abstraction of the physical system, with a certain purpose.
This purpose determines what is to be included in the model and what is irrelevant. Thus the model completely describes those aspects of the physical system that are relevant to the purpose of the model, at the appropriate level of detail.
Package (Package)
A package is used to group elements, and provides a namespace for the grouped elements.
A package can have one or more profile applications to indicate which profiles have been applied.
Profile (Profile)
A profile defines limited extensions to a reference metamodel with the purpose of adapting the metamodel to a specific platform or domain.
Template Parameter (Template Parameter)
A template parameter exposes a parameterable element as a formal template parameter of a template.
Slot (Slot)
A slot specifies that an entity modeled by an instance specification has a value or values for a specific structural feature.
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.
Abstraction (Abstraction)Dependency (Dependency)Deployment (Deployment)Element Import (Element Import)Information Flow (Information Flow)Manifestation (Manifestation)Realization (Realization)Substitution (Substitution)Usage (Usage)
ExtensionEnd (Extension End)An extension end is used to tie an extension to a stereotype when extending a metaclass. The default multiplicity of an extension end is 0..1.
Extension PointAn extension point identifies a point in the behavior of a use case where that behavior can be extended by the behavior of some other (extending) use case, as specified by an extend relationship.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
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.
Use Case (Use Case)
A use case is the specification of a set of actions performed by a system, which yields an observable result that is, typically, of value for one or more actors or other stakeholders of the system.
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.
Abstraction (Abstraction)Dependency (Dependency)Information Flow (Information Flow)Realization (Realization)Substitution (Substitution)Usage (Usage)
GuardA guard is a condition or restriction expressed in natural language text or in a machine readable language that must be fulfilled for a transition to become possible.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
The specification of the guard. The language that is used should be specified in the language property.
The language used in the guard specification, for example OCL.
An element of one of the following kinds:
Protocol Transition (Protocol Transition)
A protocol transition 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.
Transition (Transition)
A transition is a directed relationship between a source vertex and a target vertex.
It may be part of a compound transition, which takes the state machine from one state configuration to another, representing the complete response of the state machine to an occurrence of an event of a particular type.
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.
Abstraction (Abstraction)Dependency (Dependency)Information Flow (Information Flow)Realization (Realization)Substitution (Substitution)Usage (Usage) OperationAn operation is a behavioral feature of a classifier that specifies the name, type, parameters, and constraints for invoking an associated behavior. An operation may invoke both the execution of method behaviors as well as other behavioral responses.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
If true, then the behavioral feature does not have an implementation, and one must be supplied by a more specific element.
If false, the behavioral feature must have an implementation in the classifier or one must be inherited from a more general element.
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.
Specifies whether an execution of the operation leaves the state of the system unchanged (isQuery=true) or whether side effects may occur (isQuery=false).
Specifies whether this feature characterizes individual instances classified by the classifier (false) or the classifier itself (true).
Specifies the semantics of concurrent calls to the same passive instance (i.e., an instance originating from a class with isActive being false).
Active instances control access to their own behavioral features.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Artifact (Artifact)
An artifact is the specification of a physical piece of information that is used or produced by a software development process, or by deployment and operation of a system.
Examples of artifacts include model files, source files, scripts, and binary executable files, a table in a database system, a development deliverable, or a word-processing document, a mail message. An artifact is the source of a deployment to a node.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Data Type (Data Type)
A data type is a type whose instances are identified only by their value. A data type may contain attributes to support the modeling of structured data types.
Deployment Specification (Deployment Specification)
A deployment specification specifies a set of properties that determine execution parameters of a component artifact that is deployed on a node.
A deployment specification can be aimed at a specific type of container. An artifact that reifies or implements deployment specification properties is a deployment descriptor.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Enumeration (Enumeration)
An enumeration is a data type whose values are enumerated in the model as enumeration literals.
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interface (Interface)
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Primitive Type (Primitive Type)
A primitive type defines a predefined data type, without any relevant substructure (i.e., it has no parts in the context of UML). A primitive datatype may have an algebra and operations defined outside of UML, for example, mathematically.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
Template Parameter (Template Parameter)
A template parameter exposes a parameterable element as a formal template parameter of a template.
Constraint (Constraint)
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.
Parameter (Parameter)
A parameter is a specification of an argument used to pass information into or out of an invocation of a behavioral feature. Parameters are allowed to be treated as connectable elements. Parameters have support for streaming, exceptions, and parameter sets.
Template Signature (Template Signature)
A template signature bundles the set of formal template parameters for a templated element.
Activity (Activity)Actor (Actor)Artifact (Artifact)Association (Association)Class (Class)Collaboration (Collaboration)Communication Path (Communication Path)Component (Component)Data Type (Data Type)Deployment Specification (Deployment Specification)Device (Device)Enumeration (Enumeration)Execution Environment (Execution Environment)Extension (Extension)Information Item (Information Item)Interaction (Interaction)Interface (Interface)Node (Node)Opaque Behavior (Opaque Behavior)Primitive Type (Primitive Type)Protocol (Protocol)Protocol State Machine (Protocol State Machine)Signal (Signal)State Machine (State Machine)Stereotype (Stereotype)Use Case (Use Case)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).
Element Import (Element Import)
An element import identifies an element in another package, and allows the element to be referenced using its name without a qualifier.
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.
Package Import (Package Import)
A package import is a relationship that allows the use of unqualified names to refer to package members from other namespaces.
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.
Templatebinding (Templatebinding)
A template binding represents a relationship between a templateable element and a template. A template binding specifies the substitutions of actual parameters for the formal parameters of the template.
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.
Abstraction (Abstraction)Dependency (Dependency)Information Flow (Information Flow)Realization (Realization)Substitution (Substitution)Usage (Usage)Call Event (Call Event)
Call Operation Action (Action) ParameterA parameter is a specification of an argument used to pass information into or out of an invocation of a behavioral feature. Parameters are allowed to be treated as connectable elements. Parameters have support for streaming, exceptions, and parameter sets.
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 a ValueSpecification that represents a value to be used when no argument is supplied for the Parameter.
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.
Indicates whether a parameter is being sent into or out of a behavioral element.
Tells whether an output parameter may emit a value to the exclusion of the other outputs.
For a multivalued multiplicity, this attribute specifies whether the values in an instantiation of this element are sequentially ordered.
Tells whether an input parameter may accept values while its behavior is executing, or whether an output parameter post values while the behavior is executing.
For a multivalued multiplicity, this attributes specifies whether the values in an instantiation of this element are unique.
Specifies the effect that the owner of the parameter has on values passed in or out of the parameter.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Operation (Operation)
An operation is a behavioral feature of a classifier that specifies the name, type, parameters, and constraints for invoking an associated behavior. An operation may invoke both the execution of method behaviors as well as other behavioral responses.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
Reception (Reception)
A reception is a declaration stating that a classifier is prepared to react to the receipt of a signal. A reception designates a signal and specifies the expected behavioral response.
The details of handling a signal are specified by the behavior associated with the reception or the classifier itself.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Template Parameter (Template Parameter)
A template parameter exposes a parameterable element as a formal template parameter of a template.
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.
Connector End (Connector End)Abstraction (Abstraction)Dependency (Dependency)Information Flow (Information Flow)Realization (Realization)Substitution (Substitution)Usage (Usage) PortA port is a property of a classifier that specifies a distinct interaction point between that classifier and its environment or between the (behavior of the) classifier and its internal parts.
Ports are connected to properties of the classifier by connectors through which requests can be made to invoke the behavioral features of a classifier.
A Port may specify the services a classifier provides (offers) to its environment as well as the services that a classifier expects (requires) of its environment. A port has an associated protocol state machine.
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.
A String that is evaluated to give a default value for the Property when an object of the owning Classifier is instantiated.
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.
Specifies the kind of aggregation that applies to the Property.
Specifies whether requests arriving at this port are sent to the classifier behavior of this classifier.
Such ports are referred to as behavior port. Any invocation of a behavioral feature targeted at a behavior port will be handled by the instance of the owning classifier itself, rather than by any instances that this classifier may contain.
If isDerived is true, the value of the attribute is derived from information elsewhere. Specifies whether the Property is derived, i.e., whether its value or values can be computed from other information.
Specifies whether the property is derived as the union of all of the properties that are constrained to subset it.
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.
A property is navigable if it is possible to navigate from an instance of the owner of the property to an instance of the type of the property.
For a multivalued multiplicity, this attribute specifies whether the values in an instantiation of this element are sequentially ordered.
States whether the attribute's value may be modified by a client.
If true indicates that this port is used to provide the published functionality of a classifier.
If false, this port is used to implement the classifier but is not part of the essential externally-visible functionality of the classifier and can, therefore, be altered or deleted along with the internal implementation of the classifier and other properties that are considered part of its implementation.
Specifies whether this feature characterizes individual instances classified by the classifier (false) or the classifier itself (true).
For a multivalued multiplicity, this attributes specifies whether the values in an instantiation of this element are unique.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Artifact (Artifact)
An artifact is the specification of a physical piece of information that is used or produced by a software development process, or by deployment and operation of a system.
Examples of artifacts include model files, source files, scripts, and binary executable files, a table in a database system, a development deliverable, or a word-processing document, a mail message. An artifact is the source of a deployment to a node.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
Collaboration (Collaboration)
A collaboration defines a set of co-operating roles used collectively to illustrate a specific functionality.
A collaboration should only show the roles and attributes required to accomplish its defined task or function. Isolating the primary roles is an exercise in simplifying the structure and clarifying the behavior, and also provides for re-use. A collaboration often implements a pattern.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Data Type (Data Type)
A data type is a type whose instances are identified only by their value. A data type may contain attributes to support the modeling of structured data types.
Deployment Specification (Deployment Specification)
A deployment specification specifies a set of properties that determine execution parameters of a component artifact that is deployed on a node.
A deployment specification can be aimed at a specific type of container. An artifact that reifies or implements deployment specification properties is a deployment descriptor.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Enumeration (Enumeration)
An enumeration is a data type whose values are enumerated in the model as enumeration literals.
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interface (Interface)
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Primitive Type (Primitive Type)
A primitive type defines a predefined data type, without any relevant substructure (i.e., it has no parts in the context of UML). A primitive datatype may have an algebra and operations defined outside of UML, for example, mathematically.
Protocol (Protocol)
Only available together with the Real-Time Extension of RSA.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
Signal (Signal)
A signal is a specification of send request instances communicated between objects. The receiving object handles the received request instances as specified by its receptions. The data carried by a send request (which was passed to it by the send invocation occurrence that caused that request) are represented as attributes of the signal.
A signal is defined independently of the classifiers handling the signal occurrence.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
Template Parameter (Template Parameter)
A template parameter exposes a parameterable element as a formal template parameter of a template.
Attribute (Attribute)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An attribute is a property that has no reference to an association.
Template Signature (Template Signature)
A template signature bundles the set of formal template parameters for a templated element.
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.
Templatebinding (Templatebinding)
A template binding represents a relationship between a templateable element and a template. A template binding specifies the substitutions of actual parameters for the formal parameters of the template.
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.
Connector End (Connector End)Slot (Slot)Connector End (Connector End)Abstraction (Abstraction)Dependency (Dependency)Deployment (Deployment)Information Flow (Information Flow)Realization (Realization)Substitution (Substitution)Usage (Usage)Connector End (Connector End) ReceptionA reception is a declaration stating that a classifier is prepared to react to the receipt of a signal. A reception designates a signal and specifies the expected behavioral response.
The details of handling a signal are specified by the behavior associated with the reception or the classifier itself.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
If true, then the behavioral feature does not have an implementation, and one must be supplied by a more specific element.
If false, the behavioral feature must have an implementation in the classifier or one must be inherited from a more general element.
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.
Specifies whether this feature characterizes individual instances classified by the classifier (false) or the classifier itself (true).
Specifies the semantics of concurrent calls to the same passive instance (i.e., an instance originating from a class with isActive being false).
Active instances control access to their own behavioral features.
The signal that this reception handles.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interface (Interface)
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
Constraint (Constraint)
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.
Parameter (Parameter)
A parameter is a specification of an argument used to pass information into or out of an invocation of a behavioral feature. Parameters are allowed to be treated as connectable elements. Parameters have support for streaming, exceptions, and parameter sets.
Activity (Activity)Actor (Actor)Artifact (Artifact)Association (Association)Class (Class)Collaboration (Collaboration)Communication Path (Communication Path)Component (Component)Data Type (Data Type)Deployment Specification (Deployment Specification)Device (Device)Enumeration (Enumeration)Execution Environment (Execution Environment)Extension (Extension)Information Item (Information Item)Interaction (Interaction)Interface (Interface)Node (Node)Opaque Behavior (Opaque Behavior)Primitive Type (Primitive Type)Protocol (Protocol)Protocol State Machine (Protocol State Machine)Signal (Signal)State Machine (State Machine)Stereotype (Stereotype)Use Case (Use Case)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).
Element Import (Element Import)
An element import identifies an element in another package, and allows the element to be referenced using its name without a qualifier.
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.
Package Import (Package Import)
A package import is a relationship that allows the use of unqualified names to refer to package members from other namespaces.
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.
Abstraction (Abstraction)Dependency (Dependency)Information Flow (Information Flow)Realization (Realization)Substitution (Substitution)Usage (Usage) SlotA slot specifies that an entity modeled by an instance specification has a value or values for a specific structural feature.
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.
The structural feature that specifies the values that may be held by the slot.
The value corresponding to the defining feature for the owning instance specification.
An element of one of the following kinds:
Enumeration Literal (Enumeration Literal)
An enumeration literal is a user-defined data value for an enumeration.
Instance Specification (Instance Specification)
An instance specification is a model element that represents an instance in a modeled system.
An instance specification has the capability of being a deployment target in a deployment relationship, in the case that it is an instance of a node.
It is also has the capability of being a deployed artifact, if it is an instance of an artifact.
Template ParameterA template parameter exposes a parameterable element as a formal template parameter of a template.
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.
Template Signature (Template Signature)
A template signature bundles the set of formal template parameters for a templated element.
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Actor (Actor)
An actor specifies a role played by a user or any other system that interacts with the subject.
Artifact (Artifact)
An artifact is the specification of a physical piece of information that is used or produced by a software development process, or by deployment and operation of a system.
Examples of artifacts include model files, source files, scripts, and binary executable files, a table in a database system, a development deliverable, or a word-processing document, a mail message. An artifact is the source of a deployment to a node.
Association (Association)
An association describes a set of tuples whose values refer to typed instances. An instance of an association is called a link.
Association End (Association End)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An association End is a property that has a reference to an association.
Attribute (Attribute)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An attribute is a property that has no reference to an association.
Call Event (Call Event)
A call event models the receipt by an object of a message invoking a call of an operation.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
Collaboration (Collaboration)
A collaboration defines a set of co-operating roles used collectively to illustrate a specific functionality.
A collaboration should only show the roles and attributes required to accomplish its defined task or function. Isolating the primary roles is an exercise in simplifying the structure and clarifying the behavior, and also provides for re-use. A collaboration often implements a pattern.
Communication Path (Communication Path)
A communication path is an association between two deployment targets, through which they are able to exchange signals and messages.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Data Type (Data Type)
A data type is a type whose instances are identified only by their value. A data type may contain attributes to support the modeling of structured data types.
Deployment Specification (Deployment Specification)
A deployment specification specifies a set of properties that determine execution parameters of a component artifact that is deployed on a node.
A deployment specification can be aimed at a specific type of container. An artifact that reifies or implements deployment specification properties is a deployment descriptor.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Enumeration (Enumeration)
An enumeration is a data type whose values are enumerated in the model as enumeration literals.
Enumeration Literal (Enumeration Literal)
An enumeration literal is a user-defined data value for an enumeration.
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Extension (Extension)
An extension is used to indicate that the properties of a metaclass are extended through a stereotype, and gives the ability to flexibly add (and later remove) stereotypes to classes.
Information Item (Information Item)
An information item is an abstraction of all kinds of information that can be exchanged between objects. It is a kind of
classifier intended for representing information in a very abstract way, one which cannot be instantiated.
Instance Specification (Instance Specification)
An instance specification is a model element that represents an instance in a modeled system.
An instance specification has the capability of being a deployment target in a deployment relationship, in the case that it is an instance of a node.
It is also has the capability of being a deployed artifact, if it is an instance of an artifact.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interface (Interface)
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
Model (Model)
A model captures a view of a physical system. It is an abstraction of the physical system, with a certain purpose.
This purpose determines what is to be included in the model and what is irrelevant. Thus the model completely describes those aspects of the physical system that are relevant to the purpose of the model, at the appropriate level of detail.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Operation (Operation)
An operation is a behavioral feature of a classifier that specifies the name, type, parameters, and constraints for invoking an associated behavior. An operation may invoke both the execution of method behaviors as well as other behavioral responses.
Package (Package)
A package is used to group elements, and provides a namespace for the grouped elements.
A package can have one or more profile applications to indicate which profiles have been applied.
Parameter (Parameter)
A parameter is a specification of an argument used to pass information into or out of an invocation of a behavioral feature. Parameters are allowed to be treated as connectable elements. Parameters have support for streaming, exceptions, and parameter sets.
Port (Port)
A port is a property of a classifier that specifies a distinct interaction point between that classifier and its environment or between the (behavior of the) classifier and its internal parts.
Ports are connected to properties of the classifier by connectors through which requests can be made to invoke the behavioral features of a classifier.
A Port may specify the services a classifier provides (offers) to its environment as well as the services that a classifier expects (requires) of its environment. A port has an associated protocol state machine.
Primitive Type (Primitive Type)
A primitive type defines a predefined data type, without any relevant substructure (i.e., it has no parts in the context of UML). A primitive datatype may have an algebra and operations defined outside of UML, for example, mathematically.
Profile (Profile)
A profile defines limited extensions to a reference metamodel with the purpose of adapting the metamodel to a specific platform or domain.
Protocol (Protocol)
Only available together with the Real-Time Extension of RSA.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
Signal (Signal)
A signal is a specification of send request instances communicated between objects. The receiving object handles the received request instances as specified by its receptions. The data carried by a send request (which was passed to it by the send invocation occurrence that caused that request) are represented as attributes of the signal.
A signal is defined independently of the classifiers handling the signal occurrence.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
Use Case (Use Case)
A use case is the specification of a set of actions performed by a system, which yields an observable result that is, typically, of value for one or more actors or other stakeholders of the system.
ConnectorSpecifies a link that enables communication between two or more instances. This link may be an instance of anassociation, or it may represent the possibility of the instances being able to communicate because their identitiesare known by virtue of being passed in as parameters, held in variables or slots, or because the communicatinginstances are the same instance.
The link may be realized by something as simple as a pointer or by something ascomplex as a network connection. In contrast to associations, which specify links between any instance of theassociated classifiers, connectors specify links between instances playing the connected parts only.
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.
Association or Communication Path or Extension.
An optional association that specifies the link corresponding to this connector.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
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.
Specifies whether this feature characterizes individual instances classified by the classifier (false) or the classifier itself (true).
Indicates the kind of connector.
A delegation connector is a connector that links the external contract of a component (as specified by its ports) tothe internal realization of that behavior by the component's parts. It represents the forwarding of signals (operationrequests and events): a signal that arrives at a port that has a delegation connector to a part or to another port willbe passed on to that target for handling.
An assembly connector is a connector between two components that defines that one component provides the services thatanother component requires. An assembly connector is a connector that is defined from a required interface or port to aprovided interface or port.
Abstraction (Abstraction)Dependency (Dependency)Information Flow (Information Flow)Realization (Realization)Substitution (Substitution)Usage (Usage) Protocol TransitionA protocol transition 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 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.
Choice or Connection Point Reference or Deep History or Entry Point or Exit Point or Final State or Fork or Initial or Join or Junction or Shallow History or State or Terminate.
Designates the originating vertex (state or pseudostate) of the transition.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
Indicates the precise type of the transition.
An item of one of the following item kinds:
Choice (Pseudo State)Connection Point Reference (Connection Point Reference)Deep History (Pseudo State)Entry Point (Pseudo State)Exit Point (Pseudo State)Final State (Final State)Fork (Pseudo State)Initial (Pseudo State)Join (Pseudo State)Junction (Pseudo State)Shallow History (Pseudo State)State (State)Terminate (Pseudo State)An item of one of the following item kinds:
Choice (Pseudo State)Connection Point Reference (Connection Point Reference)Deep History (Pseudo State)Entry Point (Pseudo State)Exit Point (Pseudo State)Final State (Final State)Fork (Pseudo State)Initial (Pseudo State)Join (Pseudo State)Junction (Pseudo State)Shallow History (Pseudo State)State (State)Terminate (Pseudo State)Abstraction (Abstraction)Dependency (Dependency)Information Flow (Information Flow)Realization (Realization)Substitution (Substitution)Usage (Usage) AbstractionAn 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.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
An element of one of the following kinds:
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.
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.
Action Input 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 input pin is a pin that holds input values to be consumed by an action.
An action input pin is a kind of pin that executes an action to determine the values to input to another.
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Activity Final Node (Control Node)
A control node is an abstract activity node that coordinates flows in an activity.
A final node is an abstract control node at which a flow in an activity stops.
An activity final node is a final node that stops all flows in an activity.
Activity Parameter Node (Object Node)
An object node is an abstract activity node that is part of defining object flow in an activity. Object nodes have support for token selection, limitation on the number of tokens, specifying the state required for tokens, and carrying control values.
An activity parameter node is an object node for inputs and outputs to activities.
Activity Partition (Activity Partition)
An activity partition is a kind of activity group for identifying actions that have some characteristic in common.
Actor (Actor)
An actor specifies a role played by a user or any other system that interacts with the subject.
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.
Artifact (Artifact)
An artifact is the specification of a physical piece of information that is used or produced by a software development process, or by deployment and operation of a system.
Examples of artifacts include model files, source files, scripts, and binary executable files, a table in a database system, a development deliverable, or a word-processing document, a mail message. An artifact is the source of a deployment to a node.
Association (Association)
An association describes a set of tuples whose values refer to typed instances. An instance of an association is called a link.
Association End (Association End)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An association End is a property that has a reference to an association.
Attribute (Attribute)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An attribute is a property that has no reference to an association.
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 Event (Call Event)
A call event models the receipt by an object of a message invoking a call of an operation.
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.
Central Buffer (Object Node)
An object node is an abstract activity node that is part of defining object flow in an activity. Object nodes have support for token selection, limitation on the number of tokens, specifying the state required for tokens, and carrying control values.
A central buffer node is an object node for managing flows from multiple sources and destinations.
Choice (Pseudo State)
Choice vertices which, when reached, result in the dynamic evaluation of the guards of the triggers of its outgoing transitions. This realizes a dynamic conditional branch. It allows splitting of transitions into multiple outgoing paths such that the decision on which path to take may be a function of the results of prior actions performed in the same run-tocompletion step. If more than one of the guards evaluates to true, an arbitrary one is selected. If none of the guards evaluates to true, then the model is considered ill-formed. (To avoid this, it is recommended to define one outgoing transition with the predefined else guard for every choice vertex.) Choice vertices should be distinguished from static branch points that are based on junction points.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
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.
Collaboration (Collaboration)
A collaboration defines a set of co-operating roles used collectively to illustrate a specific functionality.
A collaboration should only show the roles and attributes required to accomplish its defined task or function. Isolating the primary roles is an exercise in simplifying the structure and clarifying the behavior, and also provides for re-use. A collaboration often implements a pattern.
Collaboration Use (Collaboration Use)
A collaboration use represents one particular use of a collaboration to explain the relationships between the properties of a classifier.
A collaboration use shows how the pattern described by a collaboration is applied in a given context, by binding specific entities from that context to the roles of the collaboration. Depending on the context, these entities could be structural features of a classifier, instance specifications, or even roles in some containing collaboration. There may be multiple occurrences of a given collaboration within a classifier, each involving a different set of roles and connectors.
A given role or connector may be involved in multiple occurrences of the same or different collaborations. Associated dependencies map features of the collaboration type to features in the classifier. These dependencies indicate which role in the classifier plays which role in the collaboration.
Combined Fragment (Combined Fragment)
A combined fragment defines an expression of interaction fragments. A combined fragment is defined by an interaction operator and corresponding interaction operands. Through the use of combined fragments the user will be able to describe a number of traces in a compact and concise manner.
Communication Path (Communication Path)
A communication path is an association between two deployment targets, through which they are able to exchange signals and messages.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Component Realization (Component Realization)
The realization concept is specialized to (optionally) define the classifiers that realize the contract offered by a component in terms of its provided and required interfaces.
The component forms an abstraction from these various
classifiers.
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.
Connection Point Reference (Connection Point Reference)
A connection point reference represents a usage (as part of a submachine state) of an entry/exit point defined in the statemachine reference by the submachine state.
Connector (Connector)
Specifies a link that enables communication between two or more instances. This link may be an instance of anassociation, or it may represent the possibility of the instances being able to communicate because their identitiesare known by virtue of being passed in as parameters, held in variables or slots, or because the communicatinginstances are the same instance.
The link may be realized by something as simple as a pointer or by something ascomplex as a network connection. In contrast to associations, which specify links between any instance of theassociated classifiers, connectors specify links between instances playing the connected parts only.
Control Flow (Control Flow)
A control flow is an edge that starts an activity node after the previous one is finished.
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.
Data Store Node (Object Node)
An object node is an abstract activity node that is part of defining object flow in an activity. Object nodes have support for token selection, limitation on the number of tokens, specifying the state required for tokens, and carrying control values.
A central buffer node is an object node for managing flows from multiple sources and destinations.
A data store node is a central buffer node for non-transient information.
Data Type (Data Type)
A data type is a type whose instances are identified only by their value. A data type may contain attributes to support the modeling of structured data types.
Decision Node (Control Node)
A control node is an abstract activity node that coordinates flows in an activity.
A decision node is a control node that chooses between outgoing flows.
Deep History (Pseudo State)
DeepHistory represents the most recent active configuration of the composite state that directly contains this pseudostate; e.g. the state configuration that was active when the composite state was last exited. A composite state can have at most one deep history vertex. At most one transition may originate from the history connector to the default deep history state. This transition is taken in case the composite state had never been active before. Entry actions of states entered on the path to the state represented by a deep history are performed.
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).
Deployment (Deployment)
A deployment is the allocation of an artifact or artifact instance to a deployment target. A component deployment is the deployment of one or more artifacts or artifact instances to a deployment target, optionally parameterized by a deployment specification. Examples are executables and configuration files.
Deployment Specification (Deployment Specification)
A deployment specification specifies a set of properties that determine execution parameters of a component artifact that is deployed on a node.
A deployment specification can be aimed at a specific type of container. An artifact that reifies or implements deployment specification properties is a deployment descriptor.
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.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Entry Point (Pseudo State)
An entry point pseudostate is an entry point of a state machine or composite state. In each region of the state machine or composite state it has a single transition to a vertex within the same region.
Enumeration (Enumeration)
An enumeration is a data type whose values are enumerated in the model as enumeration literals.
Enumeration Literal (Enumeration Literal)
An enumeration literal is a user-defined data value for an enumeration.
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Exit Point (Pseudo State)
An exit point pseudostate is an exit point of a state machine or composite state. Entering an exit point within any region of the composite state or state machine referenced by a submachine state implies the exit of this composite state or submachine state and the triggering of the transition that has this exit point as source in the state machine enclosing the submachine or composite state.
Expansion Node (Object Node)
An object node is an abstract activity node that is part of defining object flow in an activity. Object nodes have support for token selection, limitation on the number of tokens, specifying the state required for tokens, and carrying control values.
An expansion node is an object node used to indicate a flow across the boundary of an expansion region. A flow into a region contains a collection that is broken into its individual elements inside the region, which is executed once per element. A flow out of a region combines individual elements into a collection for use outside the region.
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.
Extend (Extend)
A relationship from an extending use case to an extended use case that specifies how and when the behavior defined in the extending use case can be inserted into the behavior defined in the extended use case.
Extension (Extension)
An extension is used to indicate that the properties of a metaclass are extended through a stereotype, and gives the ability to flexibly add (and later remove) stereotypes to classes.
Extension Point (Extension Point)
An extension point identifies a point in the behavior of a use case where that behavior can be extended by the behavior of some other (extending) use case, as specified by an extend relationship.
Final State (Final State)
A special kind of state signifying that the enclosing region is completed.
If the enclosing region is directly contained in a state machine and all other regions in the state machine also are completed, then it means that the entire state machine is completed.
Flow Final Node (Control Node)
A control node is an abstract activity node that coordinates flows in an activity.
A final node is an abstract control node at which a flow in an activity stops.
A flow final node is a final node that terminates a flow.
Fork (Pseudo State)
Fork vertices serve to split an incoming transition into two or more transitions terminating on orthogonal target vertices (i.e. vertices in different regions of a composite state). The segments outgoing from a fork vertex must not have guards or triggers.
Fork Node (Control Node)
A control node is an abstract activity node that coordinates flows in an activity.
A fork node is a control node that splits a flow into multiple concurrent flows.
Gate (Gate)
A gate is a connection point for relating a message outside an interaction fragment with a message inside the interaction fragment.
Guard (Guard)
A guard is a condition or restriction expressed in natural language text or in a machine readable language that must be fulfilled for a transition to become possible.
Include (Include)
An include relationship defines that a use case contains the behavior defined in another use case.
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.
Information Item (Information Item)
An information item is an abstraction of all kinds of information that can be exchanged between objects. It is a kind of
classifier intended for representing information in a very abstract way, one which cannot be instantiated.
Initial (Pseudo State)
An initial pseudostate represents a default vertex that is the source for a single transition to the default state of a composite state. There can be at most one initial vertex in a region. The outgoing transition from the initial vertex may have a behavior, but not a trigger or guard.
Initial Node (Control Node)
A control node is an abstract activity node that coordinates flows in an activity.
An initial node is a control node at which flow starts when the activity is invoked.
Input 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 input pin is a pin that holds input values to be consumed by an action.
Instance Specification (Instance Specification)
An instance specification is a model element that represents an instance in a modeled system.
An instance specification has the capability of being a deployment target in a deployment relationship, in the case that it is an instance of a node.
It is also has the capability of being a deployed artifact, if it is an instance of an artifact.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interaction Use (Interaction Use)
An interaction use refers to an interaction. The interaction use is a shorthand for copying the contents of the referenced interaction where the interaction use is. To be accurate the copying must take into account substituting parameters with arguments and connect the formal gates with the actual ones.
Interface (Interface)
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
Interface Realization (Interface Realization)
An interface realization is a specialized realization relationship between a classifier and an interface. This relationship signifies that the realizing classifier conforms to the contract specified by the interface.
Join (Pseudo State)
Join vertices serve to merge several transitions emanating from source vertices in different orthogonal regions. The transitions entering a join vertex cannot have guards or triggers.
Join Node (Control Node)
A control node is an abstract activity node that coordinates flows in an activity.
A join node is a control node that synchronizes multiple flows. Join nodes have a Boolean value specification using the names of the incoming edges to specify the conditions under which the join will emit a token.
Junction (Pseudo State)
Junction vertices are semantic-free vertices that are used to chain together multiple transitions. They are used to construct compound transition paths between states. For example, a junction can be used to converge multiple incoming transitions into a single outgoing transition representing a shared transition path (this is known as an merge). Conversely, they can be used to split an incoming transition into multiple outgoing transition segments with different guard conditions. This realizes a static conditional branch. (In the latter case, outgoing transitions whose guard conditions evaluate to false are disabled. A predefined guard denoted 'else' may be defined for at most one outgoing transition. This transition is enabled if all the guards labeling the other transitions are false.) Static conditional branches are distinct from dynamic conditional branches that are realized by choice vertices.
Lifeline (Lifeline)
A lifeline represents an individual participant in the interaction. While parts and structural features may have multiplicity greater than 1, lifelines represent only one interacting entity.
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.
Manifestation (Manifestation)
A manifestation is the concrete physical rendering of one or more model elements by an artifact.
Merge Node (Control Node)
A control node is an abstract activity node that coordinates flows in an activity.
A merge node is a control node that brings together multiple alternate flows. It is not used to synchronize concurrent flows but to accept one among several alternate flows.
Message (Message)
A message defines a particular communication between lifelines of an interaction.
Model (Model)
A model captures a view of a physical system. It is an abstraction of the physical system, with a certain purpose.
This purpose determines what is to be included in the model and what is irrelevant. Thus the model completely describes those aspects of the physical system that are relevant to the purpose of the model, at the appropriate level of detail.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Object Flow (Object Flow)
An object flow is an activity edge that can have objects or data passing along it. Object flows have support for multicast/receive, token selection from object nodes, and transformation of tokens.
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.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Operation (Operation)
An operation is a behavioral feature of a classifier that specifies the name, type, parameters, and constraints for invoking an associated behavior. An operation may invoke both the execution of method behaviors as well as other behavioral responses.
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.
Package (Package)
A package is used to group elements, and provides a namespace for the grouped elements.
A package can have one or more profile applications to indicate which profiles have been applied.
Parameter (Parameter)
A parameter is a specification of an argument used to pass information into or out of an invocation of a behavioral feature. Parameters are allowed to be treated as connectable elements. Parameters have support for streaming, exceptions, and parameter sets.
Port (Port)
A port is a property of a classifier that specifies a distinct interaction point between that classifier and its environment or between the (behavior of the) classifier and its internal parts.
Ports are connected to properties of the classifier by connectors through which requests can be made to invoke the behavioral features of a classifier.
A Port may specify the services a classifier provides (offers) to its environment as well as the services that a classifier expects (requires) of its environment. A port has an associated protocol state machine.
Primitive Type (Primitive Type)
A primitive type defines a predefined data type, without any relevant substructure (i.e., it has no parts in the context of UML). A primitive datatype may have an algebra and operations defined outside of UML, for example, mathematically.
Profile (Profile)
A profile defines limited extensions to a reference metamodel with the purpose of adapting the metamodel to a specific platform or domain.
Protocol (Protocol)
Only available together with the Real-Time Extension of RSA.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
Protocol Transition (Protocol Transition)
A protocol transition 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.
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.
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.
Reception (Reception)
A reception is a declaration stating that a classifier is prepared to react to the receipt of a signal. A reception designates a signal and specifies the expected behavioral response.
The details of handling a signal are specified by the behavior associated with the reception or the classifier itself.
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.
Region (Region)
A region is an orthogonal part of either a composite state or a state machine. It contains states and transitions.
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.
Shallow History (Pseudo State)
ShallowHistory represents the most recent active substate of its containing state (but not the substates of that substate). A composite state can have at most one shallow history vertex. A transition coming into the shallow history vertex is equivalent to a transition coming into the most recent active substate of a state. At most one transition may originate from the history connector to the default shallow history state. This transition is taken in case the composite state had never been active before. Entry actions of states entered on the path to the state represented by a shallow history are performed.
Signal (Signal)
A signal is a specification of send request instances communicated between objects. The receiving object handles the received request instances as specified by its receptions. The data carried by a send request (which was passed to it by the send invocation occurrence that caused that request) are represented as attributes of the signal.
A signal is defined independently of the classifiers handling the signal occurrence.
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
State (State)
A state models a situation during which some (usually implicit) invariant condition holds.
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.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
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.
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.
Terminate (Pseudo State)
Entering a terminate pseudostate implies that the execution of this state machine by means of its context object is terminated. The state machine does not exit any states nor does it perform any exit actions other than those associated with the transition leading to the terminate pseudostate. Entering a terminate pseudostate is equivalent to invoking a DestroyObjectAction.
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.
Transition (Transition)
A transition is a directed relationship between a source vertex and a target vertex.
It may be part of a compound transition, which takes the state machine from one state configuration to another, representing the complete response of the state machine to an occurrence of an event of a particular type.
Trigger (Trigger)
A trigger relates an event to a behavior that may affect an instance of the classifier. A trigger specification may be qualified by the port on which the event occurred.
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.
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.
Use Case (Use Case)
A use case is the specification of a set of actions performed by a system, which yields an observable result that is, typically, of value for one or more actors or other stakeholders of the system.
Value 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 input pin is a pin that holds input values to be consumed by an action.
A value pin is an input pin that provides a value by evaluating a value specification.
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.
An item of one of the following item kinds:
Abstraction (Abstraction)Accept Call Action (Action)Accept Event Action (Action)Action Input Pin (Pin)Activity (Activity)Activity Final Node (Control Node)Activity Parameter Node (Object Node)Activity Partition (Activity Partition)Actor (Actor)Add Structural Feature Value Action (Action)Add Variable Value Action (Action)Artifact (Artifact)Association (Association)Association End (Association End)Attribute (Attribute)Broadcast Signal Action (Action)Call Behavior Action (Action)Call Event (Call Event)Call Operation Action (Action)Central Buffer (Object Node)Choice (Pseudo State)Class (Class)Clear Association Action (Action)Clear Structural Feature Action (Action)Clear Variable Action (Action)Collaboration (Collaboration)Collaboration Use (Collaboration Use)Combined Fragment (Combined Fragment)Communication Path (Communication Path)Component (Component)Component Realization (Component Realization)Conditional Node (Action)Connection Point Reference (Connection Point Reference)Connector (Connector)Control Flow (Control Flow)Create Link Action (Action)Create Link Object Action (Action)Create Object Action (Action)Data Store Node (Object Node)Data Type (Data Type)Decision Node (Control Node)Deep History (Pseudo State)Dependency (Dependency)Deployment (Deployment)Deployment Specification (Deployment Specification)Destroy Link Action (Action)Destroy Object Action (Action)Device (Device)Entry Point (Pseudo State)Enumeration (Enumeration)Enumeration Literal (Enumeration Literal)Execution Environment (Execution Environment)Exit Point (Pseudo State)Expansion Node (Object Node)Expansion Region (Action)Extend (Extend)Extension (Extension)Extension Point (Extension Point)Final State (Final State)Flow Final Node (Control Node)Fork (Pseudo State)Fork Node (Control Node)Gate (Gate)Guard (Guard)Include (Include)Information Flow (Information Flow)Information Item (Information Item)Initial (Pseudo State)Initial Node (Control Node)Input Pin (Pin)Instance Specification (Instance Specification)Interaction (Interaction)Interaction Use (Interaction Use)Interface (Interface)Interface Realization (Interface Realization)Join (Pseudo State)Join Node (Control Node)Junction (Pseudo State)Lifeline (Lifeline)Loop Node (Action)Manifestation (Manifestation)Merge Node (Control Node)Message (Message)Model (Model)Node (Node)Object Flow (Object Flow)Opaque Action (Action)Opaque Behavior (Opaque Behavior)Operation (Operation)Output Pin (Pin)Package (Package)Parameter (Parameter)Port (Port)Primitive Type (Primitive Type)Profile (Profile)Protocol (Protocol)Protocol State Machine (Protocol State Machine)Protocol Transition (Protocol Transition)Raise Exception Action (Action)Read Extent Action (Action)Read Is Classified Object Action (Action)Read Link Action (Action)Read Link Object End Action (Action)Read Link Object End Qualifier Action (Action)Read Self Action (Action)Read Structural Feature Action (Action)Read Variable Action (Action)Realization (Realization)Reception (Reception)Reclassify Object Action (Action)Reduce Action (Action)Region (Region)Remove Structural Feature Value Action (Action)Remove Variable Value Action (Action)Reply Action (Action)Send Object Action (Action)Send Signal Action (Action)Sequence Node (Action)Shallow History (Pseudo State)Signal (Signal)Start Classifier Behavior Action (Action)Start Object Behavior Action (Action)State (State)State Machine (State Machine)Stereotype (Stereotype)Structured Activity Node (Action)Structured Activity Node (Structured Activity Node)Substitution (Substitution)Terminate (Pseudo State)Test Identity Action (Action)Transition (Transition)Trigger (Trigger)Unmarshall Action (Action)Usage (Usage)Use Case (Use Case)Value Pin (Pin)Value Specification Action (Action)Abstraction (Abstraction)Dependency (Dependency)Information Flow (Information Flow)Realization (Realization)Substitution (Substitution)Usage (Usage) Component RealizationThe realization concept is specialized to (optionally) define the classifiers that realize the contract offered by a component in terms of its provided and required interfaces.
The component forms an abstraction from these various
classifiers.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Actor (Actor)
An actor specifies a role played by a user or any other system that interacts with the subject.
Artifact (Artifact)
An artifact is the specification of a physical piece of information that is used or produced by a software development process, or by deployment and operation of a system.
Examples of artifacts include model files, source files, scripts, and binary executable files, a table in a database system, a development deliverable, or a word-processing document, a mail message. An artifact is the source of a deployment to a node.
Association (Association)
An association describes a set of tuples whose values refer to typed instances. An instance of an association is called a link.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
Collaboration (Collaboration)
A collaboration defines a set of co-operating roles used collectively to illustrate a specific functionality.
A collaboration should only show the roles and attributes required to accomplish its defined task or function. Isolating the primary roles is an exercise in simplifying the structure and clarifying the behavior, and also provides for re-use. A collaboration often implements a pattern.
Communication Path (Communication Path)
A communication path is an association between two deployment targets, through which they are able to exchange signals and messages.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Data Type (Data Type)
A data type is a type whose instances are identified only by their value. A data type may contain attributes to support the modeling of structured data types.
Deployment Specification (Deployment Specification)
A deployment specification specifies a set of properties that determine execution parameters of a component artifact that is deployed on a node.
A deployment specification can be aimed at a specific type of container. An artifact that reifies or implements deployment specification properties is a deployment descriptor.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Enumeration (Enumeration)
An enumeration is a data type whose values are enumerated in the model as enumeration literals.
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Extension (Extension)
An extension is used to indicate that the properties of a metaclass are extended through a stereotype, and gives the ability to flexibly add (and later remove) stereotypes to classes.
Information Item (Information Item)
An information item is an abstraction of all kinds of information that can be exchanged between objects. It is a kind of
classifier intended for representing information in a very abstract way, one which cannot be instantiated.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interface (Interface)
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Primitive Type (Primitive Type)
A primitive type defines a predefined data type, without any relevant substructure (i.e., it has no parts in the context of UML). A primitive datatype may have an algebra and operations defined outside of UML, for example, mathematically.
Protocol (Protocol)
Only available together with the Real-Time Extension of RSA.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
Signal (Signal)
A signal is a specification of send request instances communicated between objects. The receiving object handles the received request instances as specified by its receptions. The data carried by a send request (which was passed to it by the send invocation occurrence that caused that request) are represented as attributes of the signal.
A signal is defined independently of the classifiers handling the signal occurrence.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
Use Case (Use Case)
A use case is the specification of a set of actions performed by a system, which yields an observable result that is, typically, of value for one or more actors or other stakeholders of the system.
An item of one of the following item kinds:
Activity (Activity)Actor (Actor)Artifact (Artifact)Association (Association)Class (Class)Collaboration (Collaboration)Communication Path (Communication Path)Component (Component)Data Type (Data Type)Deployment Specification (Deployment Specification)Device (Device)Enumeration (Enumeration)Execution Environment (Execution Environment)Extension (Extension)Information Item (Information Item)Interaction (Interaction)Interface (Interface)Node (Node)Opaque Behavior (Opaque Behavior)Primitive Type (Primitive Type)Protocol (Protocol)Protocol State Machine (Protocol State Machine)Signal (Signal)State Machine (State Machine)Stereotype (Stereotype)Use Case (Use Case)Abstraction (Abstraction)Dependency (Dependency)Information Flow (Information Flow)Realization (Realization)Substitution (Substitution)Usage (Usage) DeploymentA deployment is the allocation of an artifact or artifact instance to a deployment target. A component deployment is the deployment of one or more artifacts or artifact instances to a deployment target, optionally parameterized by a deployment specification. Examples are executables and configuration files.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
An element of one of the following kinds:
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
An item of one of the following item kinds:
Artifact (Artifact)Association End (Association End)Attribute (Attribute)Deployment Specification (Deployment Specification)Device (Device)Enumeration Literal (Enumeration Literal)Execution Environment (Execution Environment)Instance Specification (Instance Specification)Node (Node)Port (Port)Abstraction (Abstraction)Dependency (Dependency)Information Flow (Information Flow)Realization (Realization)Substitution (Substitution)Usage (Usage) ExtendA relationship from an extending use case to an extended use case that specifies how and when the behavior defined in the extending use case can be inserted into the behavior defined in the extended use case.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
Use Case (Use Case)
A use case is the specification of a set of actions performed by a system, which yields an observable result that is, typically, of value for one or more actors or other stakeholders of the system.
Use Case (Use Case)
Abstraction (Abstraction)Dependency (Dependency)Information Flow (Information Flow)Realization (Realization)Substitution (Substitution)Usage (Usage) GeneralizationA generalization is a taxonomic relationship between a more general classifier and a more specific classifier. Each instance of the specific classifier is also an indirect instance of the general classifier. Thus, the specific classifier inherits the features of the more general classifier.
A generalization relates a specific classifier to a more general classifier, and is owned by the specific classifier.
Indicates whether the specific item can be used wherever the general item can be used.
If true, the execution traces of the specific item will be a superset of the execution traces of the general item.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Actor (Actor)
An actor specifies a role played by a user or any other system that interacts with the subject.
Artifact (Artifact)
An artifact is the specification of a physical piece of information that is used or produced by a software development process, or by deployment and operation of a system.
Examples of artifacts include model files, source files, scripts, and binary executable files, a table in a database system, a development deliverable, or a word-processing document, a mail message. An artifact is the source of a deployment to a node.
Association (Association)
An association describes a set of tuples whose values refer to typed instances. An instance of an association is called a link.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
Collaboration (Collaboration)
A collaboration defines a set of co-operating roles used collectively to illustrate a specific functionality.
A collaboration should only show the roles and attributes required to accomplish its defined task or function. Isolating the primary roles is an exercise in simplifying the structure and clarifying the behavior, and also provides for re-use. A collaboration often implements a pattern.
Communication Path (Communication Path)
A communication path is an association between two deployment targets, through which they are able to exchange signals and messages.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Data Type (Data Type)
A data type is a type whose instances are identified only by their value. A data type may contain attributes to support the modeling of structured data types.
Deployment Specification (Deployment Specification)
A deployment specification specifies a set of properties that determine execution parameters of a component artifact that is deployed on a node.
A deployment specification can be aimed at a specific type of container. An artifact that reifies or implements deployment specification properties is a deployment descriptor.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Enumeration (Enumeration)
An enumeration is a data type whose values are enumerated in the model as enumeration literals.
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Extension (Extension)
An extension is used to indicate that the properties of a metaclass are extended through a stereotype, and gives the ability to flexibly add (and later remove) stereotypes to classes.
Information Item (Information Item)
An information item is an abstraction of all kinds of information that can be exchanged between objects. It is a kind of
classifier intended for representing information in a very abstract way, one which cannot be instantiated.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interface (Interface)
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Primitive Type (Primitive Type)
A primitive type defines a predefined data type, without any relevant substructure (i.e., it has no parts in the context of UML). A primitive datatype may have an algebra and operations defined outside of UML, for example, mathematically.
Protocol (Protocol)
Only available together with the Real-Time Extension of RSA.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
Signal (Signal)
A signal is a specification of send request instances communicated between objects. The receiving object handles the received request instances as specified by its receptions. The data carried by a send request (which was passed to it by the send invocation occurrence that caused that request) are represented as attributes of the signal.
A signal is defined independently of the classifiers handling the signal occurrence.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
Use Case (Use Case)
A use case is the specification of a set of actions performed by a system, which yields an observable result that is, typically, of value for one or more actors or other stakeholders of the system.
An item of one of the following item kinds:
Activity (Activity)Actor (Actor)Artifact (Artifact)Association (Association)Class (Class)Collaboration (Collaboration)Communication Path (Communication Path)Component (Component)Data Type (Data Type)Deployment Specification (Deployment Specification)Device (Device)Enumeration (Enumeration)Execution Environment (Execution Environment)Extension (Extension)Information Item (Information Item)Interaction (Interaction)Interface (Interface)Node (Node)Opaque Behavior (Opaque Behavior)Primitive Type (Primitive Type)Protocol (Protocol)Protocol State Machine (Protocol State Machine)Signal (Signal)State Machine (State Machine)Stereotype (Stereotype)Use Case (Use Case) IncludeAn include relationship defines that a use case contains the behavior defined in another use case.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
Use Case (Use Case)
A use case is the specification of a set of actions performed by a system, which yields an observable result that is, typically, of value for one or more actors or other stakeholders of the system.
Use Case (Use Case)
Abstraction (Abstraction)Dependency (Dependency)Information Flow (Information Flow)Realization (Realization)Substitution (Substitution)Usage (Usage) Information FlowAn 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.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
An element of one of the following kinds:
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.
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.
Action Input 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 input pin is a pin that holds input values to be consumed by an action.
An action input pin is a kind of pin that executes an action to determine the values to input to another.
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Activity Final Node (Control Node)
A control node is an abstract activity node that coordinates flows in an activity.
A final node is an abstract control node at which a flow in an activity stops.
An activity final node is a final node that stops all flows in an activity.
Activity Parameter Node (Object Node)
An object node is an abstract activity node that is part of defining object flow in an activity. Object nodes have support for token selection, limitation on the number of tokens, specifying the state required for tokens, and carrying control values.
An activity parameter node is an object node for inputs and outputs to activities.
Activity Partition (Activity Partition)
An activity partition is a kind of activity group for identifying actions that have some characteristic in common.
Actor (Actor)
An actor specifies a role played by a user or any other system that interacts with the subject.
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.
Artifact (Artifact)
An artifact is the specification of a physical piece of information that is used or produced by a software development process, or by deployment and operation of a system.
Examples of artifacts include model files, source files, scripts, and binary executable files, a table in a database system, a development deliverable, or a word-processing document, a mail message. An artifact is the source of a deployment to a node.
Association (Association)
An association describes a set of tuples whose values refer to typed instances. An instance of an association is called a link.
Association End (Association End)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An association End is a property that has a reference to an association.
Attribute (Attribute)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An attribute is a property that has no reference to an association.
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 Event (Call Event)
A call event models the receipt by an object of a message invoking a call of an operation.
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.
Central Buffer (Object Node)
An object node is an abstract activity node that is part of defining object flow in an activity. Object nodes have support for token selection, limitation on the number of tokens, specifying the state required for tokens, and carrying control values.
A central buffer node is an object node for managing flows from multiple sources and destinations.
Choice (Pseudo State)
Choice vertices which, when reached, result in the dynamic evaluation of the guards of the triggers of its outgoing transitions. This realizes a dynamic conditional branch. It allows splitting of transitions into multiple outgoing paths such that the decision on which path to take may be a function of the results of prior actions performed in the same run-tocompletion step. If more than one of the guards evaluates to true, an arbitrary one is selected. If none of the guards evaluates to true, then the model is considered ill-formed. (To avoid this, it is recommended to define one outgoing transition with the predefined else guard for every choice vertex.) Choice vertices should be distinguished from static branch points that are based on junction points.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
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.
Collaboration (Collaboration)
A collaboration defines a set of co-operating roles used collectively to illustrate a specific functionality.
A collaboration should only show the roles and attributes required to accomplish its defined task or function. Isolating the primary roles is an exercise in simplifying the structure and clarifying the behavior, and also provides for re-use. A collaboration often implements a pattern.
Collaboration Use (Collaboration Use)
A collaboration use represents one particular use of a collaboration to explain the relationships between the properties of a classifier.
A collaboration use shows how the pattern described by a collaboration is applied in a given context, by binding specific entities from that context to the roles of the collaboration. Depending on the context, these entities could be structural features of a classifier, instance specifications, or even roles in some containing collaboration. There may be multiple occurrences of a given collaboration within a classifier, each involving a different set of roles and connectors.
A given role or connector may be involved in multiple occurrences of the same or different collaborations. Associated dependencies map features of the collaboration type to features in the classifier. These dependencies indicate which role in the classifier plays which role in the collaboration.
Combined Fragment (Combined Fragment)
A combined fragment defines an expression of interaction fragments. A combined fragment is defined by an interaction operator and corresponding interaction operands. Through the use of combined fragments the user will be able to describe a number of traces in a compact and concise manner.
Communication Path (Communication Path)
A communication path is an association between two deployment targets, through which they are able to exchange signals and messages.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Component Realization (Component Realization)
The realization concept is specialized to (optionally) define the classifiers that realize the contract offered by a component in terms of its provided and required interfaces.
The component forms an abstraction from these various
classifiers.
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.
Connection Point Reference (Connection Point Reference)
A connection point reference represents a usage (as part of a submachine state) of an entry/exit point defined in the statemachine reference by the submachine state.
Connector (Connector)
Specifies a link that enables communication between two or more instances. This link may be an instance of anassociation, or it may represent the possibility of the instances being able to communicate because their identitiesare known by virtue of being passed in as parameters, held in variables or slots, or because the communicatinginstances are the same instance.
The link may be realized by something as simple as a pointer or by something ascomplex as a network connection. In contrast to associations, which specify links between any instance of theassociated classifiers, connectors specify links between instances playing the connected parts only.
Control Flow (Control Flow)
A control flow is an edge that starts an activity node after the previous one is finished.
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.
Data Store Node (Object Node)
An object node is an abstract activity node that is part of defining object flow in an activity. Object nodes have support for token selection, limitation on the number of tokens, specifying the state required for tokens, and carrying control values.
A central buffer node is an object node for managing flows from multiple sources and destinations.
A data store node is a central buffer node for non-transient information.
Data Type (Data Type)
A data type is a type whose instances are identified only by their value. A data type may contain attributes to support the modeling of structured data types.
Decision Node (Control Node)
A control node is an abstract activity node that coordinates flows in an activity.
A decision node is a control node that chooses between outgoing flows.
Deep History (Pseudo State)
DeepHistory represents the most recent active configuration of the composite state that directly contains this pseudostate; e.g. the state configuration that was active when the composite state was last exited. A composite state can have at most one deep history vertex. At most one transition may originate from the history connector to the default deep history state. This transition is taken in case the composite state had never been active before. Entry actions of states entered on the path to the state represented by a deep history are performed.
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).
Deployment (Deployment)
A deployment is the allocation of an artifact or artifact instance to a deployment target. A component deployment is the deployment of one or more artifacts or artifact instances to a deployment target, optionally parameterized by a deployment specification. Examples are executables and configuration files.
Deployment Specification (Deployment Specification)
A deployment specification specifies a set of properties that determine execution parameters of a component artifact that is deployed on a node.
A deployment specification can be aimed at a specific type of container. An artifact that reifies or implements deployment specification properties is a deployment descriptor.
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.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Entry Point (Pseudo State)
An entry point pseudostate is an entry point of a state machine or composite state. In each region of the state machine or composite state it has a single transition to a vertex within the same region.
Enumeration (Enumeration)
An enumeration is a data type whose values are enumerated in the model as enumeration literals.
Enumeration Literal (Enumeration Literal)
An enumeration literal is a user-defined data value for an enumeration.
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Exit Point (Pseudo State)
An exit point pseudostate is an exit point of a state machine or composite state. Entering an exit point within any region of the composite state or state machine referenced by a submachine state implies the exit of this composite state or submachine state and the triggering of the transition that has this exit point as source in the state machine enclosing the submachine or composite state.
Expansion Node (Object Node)
An object node is an abstract activity node that is part of defining object flow in an activity. Object nodes have support for token selection, limitation on the number of tokens, specifying the state required for tokens, and carrying control values.
An expansion node is an object node used to indicate a flow across the boundary of an expansion region. A flow into a region contains a collection that is broken into its individual elements inside the region, which is executed once per element. A flow out of a region combines individual elements into a collection for use outside the region.
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.
Extend (Extend)
A relationship from an extending use case to an extended use case that specifies how and when the behavior defined in the extending use case can be inserted into the behavior defined in the extended use case.
Extension (Extension)
An extension is used to indicate that the properties of a metaclass are extended through a stereotype, and gives the ability to flexibly add (and later remove) stereotypes to classes.
Extension Point (Extension Point)
An extension point identifies a point in the behavior of a use case where that behavior can be extended by the behavior of some other (extending) use case, as specified by an extend relationship.
Final State (Final State)
A special kind of state signifying that the enclosing region is completed.
If the enclosing region is directly contained in a state machine and all other regions in the state machine also are completed, then it means that the entire state machine is completed.
Flow Final Node (Control Node)
A control node is an abstract activity node that coordinates flows in an activity.
A final node is an abstract control node at which a flow in an activity stops.
A flow final node is a final node that terminates a flow.
Fork (Pseudo State)
Fork vertices serve to split an incoming transition into two or more transitions terminating on orthogonal target vertices (i.e. vertices in different regions of a composite state). The segments outgoing from a fork vertex must not have guards or triggers.
Fork Node (Control Node)
A control node is an abstract activity node that coordinates flows in an activity.
A fork node is a control node that splits a flow into multiple concurrent flows.
Gate (Gate)
A gate is a connection point for relating a message outside an interaction fragment with a message inside the interaction fragment.
Guard (Guard)
A guard is a condition or restriction expressed in natural language text or in a machine readable language that must be fulfilled for a transition to become possible.
Include (Include)
An include relationship defines that a use case contains the behavior defined in another use case.
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.
Information Item (Information Item)
An information item is an abstraction of all kinds of information that can be exchanged between objects. It is a kind of
classifier intended for representing information in a very abstract way, one which cannot be instantiated.
Initial (Pseudo State)
An initial pseudostate represents a default vertex that is the source for a single transition to the default state of a composite state. There can be at most one initial vertex in a region. The outgoing transition from the initial vertex may have a behavior, but not a trigger or guard.
Initial Node (Control Node)
A control node is an abstract activity node that coordinates flows in an activity.
An initial node is a control node at which flow starts when the activity is invoked.
Input 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 input pin is a pin that holds input values to be consumed by an action.
Instance Specification (Instance Specification)
An instance specification is a model element that represents an instance in a modeled system.
An instance specification has the capability of being a deployment target in a deployment relationship, in the case that it is an instance of a node.
It is also has the capability of being a deployed artifact, if it is an instance of an artifact.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interaction Use (Interaction Use)
An interaction use refers to an interaction. The interaction use is a shorthand for copying the contents of the referenced interaction where the interaction use is. To be accurate the copying must take into account substituting parameters with arguments and connect the formal gates with the actual ones.
Interface (Interface)
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
Interface Realization (Interface Realization)
An interface realization is a specialized realization relationship between a classifier and an interface. This relationship signifies that the realizing classifier conforms to the contract specified by the interface.
Join (Pseudo State)
Join vertices serve to merge several transitions emanating from source vertices in different orthogonal regions. The transitions entering a join vertex cannot have guards or triggers.
Join Node (Control Node)
A control node is an abstract activity node that coordinates flows in an activity.
A join node is a control node that synchronizes multiple flows. Join nodes have a Boolean value specification using the names of the incoming edges to specify the conditions under which the join will emit a token.
Junction (Pseudo State)
Junction vertices are semantic-free vertices that are used to chain together multiple transitions. They are used to construct compound transition paths between states. For example, a junction can be used to converge multiple incoming transitions into a single outgoing transition representing a shared transition path (this is known as an merge). Conversely, they can be used to split an incoming transition into multiple outgoing transition segments with different guard conditions. This realizes a static conditional branch. (In the latter case, outgoing transitions whose guard conditions evaluate to false are disabled. A predefined guard denoted 'else' may be defined for at most one outgoing transition. This transition is enabled if all the guards labeling the other transitions are false.) Static conditional branches are distinct from dynamic conditional branches that are realized by choice vertices.
Lifeline (Lifeline)
A lifeline represents an individual participant in the interaction. While parts and structural features may have multiplicity greater than 1, lifelines represent only one interacting entity.
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.
Manifestation (Manifestation)
A manifestation is the concrete physical rendering of one or more model elements by an artifact.
Merge Node (Control Node)
A control node is an abstract activity node that coordinates flows in an activity.
A merge node is a control node that brings together multiple alternate flows. It is not used to synchronize concurrent flows but to accept one among several alternate flows.
Message (Message)
A message defines a particular communication between lifelines of an interaction.
Model (Model)
A model captures a view of a physical system. It is an abstraction of the physical system, with a certain purpose.
This purpose determines what is to be included in the model and what is irrelevant. Thus the model completely describes those aspects of the physical system that are relevant to the purpose of the model, at the appropriate level of detail.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Object Flow (Object Flow)
An object flow is an activity edge that can have objects or data passing along it. Object flows have support for multicast/receive, token selection from object nodes, and transformation of tokens.
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.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Operation (Operation)
An operation is a behavioral feature of a classifier that specifies the name, type, parameters, and constraints for invoking an associated behavior. An operation may invoke both the execution of method behaviors as well as other behavioral responses.
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.
Package (Package)
A package is used to group elements, and provides a namespace for the grouped elements.
A package can have one or more profile applications to indicate which profiles have been applied.
Parameter (Parameter)
A parameter is a specification of an argument used to pass information into or out of an invocation of a behavioral feature. Parameters are allowed to be treated as connectable elements. Parameters have support for streaming, exceptions, and parameter sets.
Port (Port)
A port is a property of a classifier that specifies a distinct interaction point between that classifier and its environment or between the (behavior of the) classifier and its internal parts.
Ports are connected to properties of the classifier by connectors through which requests can be made to invoke the behavioral features of a classifier.
A Port may specify the services a classifier provides (offers) to its environment as well as the services that a classifier expects (requires) of its environment. A port has an associated protocol state machine.
Primitive Type (Primitive Type)
A primitive type defines a predefined data type, without any relevant substructure (i.e., it has no parts in the context of UML). A primitive datatype may have an algebra and operations defined outside of UML, for example, mathematically.
Profile (Profile)
A profile defines limited extensions to a reference metamodel with the purpose of adapting the metamodel to a specific platform or domain.
Protocol (Protocol)
Only available together with the Real-Time Extension of RSA.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
Protocol Transition (Protocol Transition)
A protocol transition 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.
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.
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.
Reception (Reception)
A reception is a declaration stating that a classifier is prepared to react to the receipt of a signal. A reception designates a signal and specifies the expected behavioral response.
The details of handling a signal are specified by the behavior associated with the reception or the classifier itself.
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.
Region (Region)
A region is an orthogonal part of either a composite state or a state machine. It contains states and transitions.
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.
Shallow History (Pseudo State)
ShallowHistory represents the most recent active substate of its containing state (but not the substates of that substate). A composite state can have at most one shallow history vertex. A transition coming into the shallow history vertex is equivalent to a transition coming into the most recent active substate of a state. At most one transition may originate from the history connector to the default shallow history state. This transition is taken in case the composite state had never been active before. Entry actions of states entered on the path to the state represented by a shallow history are performed.
Signal (Signal)
A signal is a specification of send request instances communicated between objects. The receiving object handles the received request instances as specified by its receptions. The data carried by a send request (which was passed to it by the send invocation occurrence that caused that request) are represented as attributes of the signal.
A signal is defined independently of the classifiers handling the signal occurrence.
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
State (State)
A state models a situation during which some (usually implicit) invariant condition holds.
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.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
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.
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.
Terminate (Pseudo State)
Entering a terminate pseudostate implies that the execution of this state machine by means of its context object is terminated. The state machine does not exit any states nor does it perform any exit actions other than those associated with the transition leading to the terminate pseudostate. Entering a terminate pseudostate is equivalent to invoking a DestroyObjectAction.
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.
Transition (Transition)
A transition is a directed relationship between a source vertex and a target vertex.
It may be part of a compound transition, which takes the state machine from one state configuration to another, representing the complete response of the state machine to an occurrence of an event of a particular type.
Trigger (Trigger)
A trigger relates an event to a behavior that may affect an instance of the classifier. A trigger specification may be qualified by the port on which the event occurred.
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.
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.
Use Case (Use Case)
A use case is the specification of a set of actions performed by a system, which yields an observable result that is, typically, of value for one or more actors or other stakeholders of the system.
Value 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 input pin is a pin that holds input values to be consumed by an action.
A value pin is an input pin that provides a value by evaluating a value specification.
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.
An item of one of the following item kinds:
Abstraction (Abstraction)Accept Call Action (Action)Accept Event Action (Action)Action Input Pin (Pin)Activity (Activity)Activity Final Node (Control Node)Activity Parameter Node (Object Node)Activity Partition (Activity Partition)Actor (Actor)Add Structural Feature Value Action (Action)Add Variable Value Action (Action)Artifact (Artifact)Association (Association)Association End (Association End)Attribute (Attribute)Broadcast Signal Action (Action)Call Behavior Action (Action)Call Event (Call Event)Call Operation Action (Action)Central Buffer (Object Node)Choice (Pseudo State)Class (Class)Clear Association Action (Action)Clear Structural Feature Action (Action)Clear Variable Action (Action)Collaboration (Collaboration)Collaboration Use (Collaboration Use)Combined Fragment (Combined Fragment)Communication Path (Communication Path)Component (Component)Component Realization (Component Realization)Conditional Node (Action)Connection Point Reference (Connection Point Reference)Connector (Connector)Control Flow (Control Flow)Create Link Action (Action)Create Link Object Action (Action)Create Object Action (Action)Data Store Node (Object Node)Data Type (Data Type)Decision Node (Control Node)Deep History (Pseudo State)Dependency (Dependency)Deployment (Deployment)Deployment Specification (Deployment Specification)Destroy Link Action (Action)Destroy Object Action (Action)Device (Device)Entry Point (Pseudo State)Enumeration (Enumeration)Enumeration Literal (Enumeration Literal)Execution Environment (Execution Environment)Exit Point (Pseudo State)Expansion Node (Object Node)Expansion Region (Action)Extend (Extend)Extension (Extension)Extension Point (Extension Point)Final State (Final State)Flow Final Node (Control Node)Fork (Pseudo State)Fork Node (Control Node)Gate (Gate)Guard (Guard)Include (Include)Information Flow (Information Flow)Information Item (Information Item)Initial (Pseudo State)Initial Node (Control Node)Input Pin (Pin)Instance Specification (Instance Specification)Interaction (Interaction)Interaction Use (Interaction Use)Interface (Interface)Interface Realization (Interface Realization)Join (Pseudo State)Join Node (Control Node)Junction (Pseudo State)Lifeline (Lifeline)Loop Node (Action)Manifestation (Manifestation)Merge Node (Control Node)Message (Message)Model (Model)Node (Node)Object Flow (Object Flow)Opaque Action (Action)Opaque Behavior (Opaque Behavior)Operation (Operation)Output Pin (Pin)Package (Package)Parameter (Parameter)Port (Port)Primitive Type (Primitive Type)Profile (Profile)Protocol (Protocol)Protocol State Machine (Protocol State Machine)Protocol Transition (Protocol Transition)Raise Exception Action (Action)Read Extent Action (Action)Read Is Classified Object Action (Action)Read Link Action (Action)Read Link Object End Action (Action)Read Link Object End Qualifier Action (Action)Read Self Action (Action)Read Structural Feature Action (Action)Read Variable Action (Action)Realization (Realization)Reception (Reception)Reclassify Object Action (Action)Reduce Action (Action)Region (Region)Remove Structural Feature Value Action (Action)Remove Variable Value Action (Action)Reply Action (Action)Send Object Action (Action)Send Signal Action (Action)Sequence Node (Action)Shallow History (Pseudo State)Signal (Signal)Start Classifier Behavior Action (Action)Start Object Behavior Action (Action)State (State)State Machine (State Machine)Stereotype (Stereotype)Structured Activity Node (Action)Structured Activity Node (Structured Activity Node)Substitution (Substitution)Terminate (Pseudo State)Test Identity Action (Action)Transition (Transition)Trigger (Trigger)Unmarshall Action (Action)Usage (Usage)Use Case (Use Case)Value Pin (Pin)Value Specification Action (Action)Abstraction (Abstraction)Dependency (Dependency)Information Flow (Information Flow)Realization (Realization)Substitution (Substitution)Usage (Usage) Interface RealizationAn interface realization is a specialized realization relationship between a classifier and an interface. This relationship signifies that the realizing classifier conforms to the contract specified by the interface.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Actor (Actor)
An actor specifies a role played by a user or any other system that interacts with the subject.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
Collaboration (Collaboration)
A collaboration defines a set of co-operating roles used collectively to illustrate a specific functionality.
A collaboration should only show the roles and attributes required to accomplish its defined task or function. Isolating the primary roles is an exercise in simplifying the structure and clarifying the behavior, and also provides for re-use. A collaboration often implements a pattern.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
Use Case (Use Case)
A use case is the specification of a set of actions performed by a system, which yields an observable result that is, typically, of value for one or more actors or other stakeholders of the system.
Interface (Interface)
Abstraction (Abstraction)Dependency (Dependency)Information Flow (Information Flow)Realization (Realization)Substitution (Substitution)Usage (Usage) ManifestationA manifestation is the concrete physical rendering of one or more model elements by an artifact.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
An element of one of the following kinds:
Artifact (Artifact)
An artifact is the specification of a physical piece of information that is used or produced by a software development process, or by deployment and operation of a system.
Examples of artifacts include model files, source files, scripts, and binary executable files, a table in a database system, a development deliverable, or a word-processing document, a mail message. An artifact is the source of a deployment to a node.
Deployment Specification (Deployment Specification)
A deployment specification specifies a set of properties that determine execution parameters of a component artifact that is deployed on a node.
A deployment specification can be aimed at a specific type of container. An artifact that reifies or implements deployment specification properties is a deployment descriptor.
An item of one of the following item kinds:
Activity (Activity)Actor (Actor)Artifact (Artifact)Association (Association)Call Event (Call Event)Class (Class)Collaboration (Collaboration)Communication Path (Communication Path)Component (Component)Data Type (Data Type)Deployment Specification (Deployment Specification)Device (Device)Enumeration (Enumeration)Enumeration Literal (Enumeration Literal)Execution Environment (Execution Environment)Extension (Extension)Information Item (Information Item)Instance Specification (Instance Specification)Interaction (Interaction)Interface (Interface)Model (Model)Node (Node)Opaque Behavior (Opaque Behavior)Package (Package)Primitive Type (Primitive Type)Profile (Profile)Protocol (Protocol)Protocol State Machine (Protocol State Machine)Signal (Signal)State Machine (State Machine)Stereotype (Stereotype)Use Case (Use Case)Abstraction (Abstraction)Dependency (Dependency)Information Flow (Information Flow)Realization (Realization)Substitution (Substitution)Usage (Usage)
Protocol ConformanceProtocol state machines can be redefined into more specific protocol state machines, or into behavioral state machines.
Protocol conformance declares that the specific protocol state machine specifies a protocol that conforms to the general state machine one, or that the specific behavioral state machine abide by the protocol of the general protocol state machine.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
Protocol State Machine (Protocol State Machine)
RealizationRealization 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.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
An element of one of the following kinds:
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.
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.
Action Input 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 input pin is a pin that holds input values to be consumed by an action.
An action input pin is a kind of pin that executes an action to determine the values to input to another.
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Activity Final Node (Control Node)
A control node is an abstract activity node that coordinates flows in an activity.
A final node is an abstract control node at which a flow in an activity stops.
An activity final node is a final node that stops all flows in an activity.
Activity Parameter Node (Object Node)
An object node is an abstract activity node that is part of defining object flow in an activity. Object nodes have support for token selection, limitation on the number of tokens, specifying the state required for tokens, and carrying control values.
An activity parameter node is an object node for inputs and outputs to activities.
Activity Partition (Activity Partition)
An activity partition is a kind of activity group for identifying actions that have some characteristic in common.
Actor (Actor)
An actor specifies a role played by a user or any other system that interacts with the subject.
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.
Artifact (Artifact)
An artifact is the specification of a physical piece of information that is used or produced by a software development process, or by deployment and operation of a system.
Examples of artifacts include model files, source files, scripts, and binary executable files, a table in a database system, a development deliverable, or a word-processing document, a mail message. An artifact is the source of a deployment to a node.
Association (Association)
An association describes a set of tuples whose values refer to typed instances. An instance of an association is called a link.
Association End (Association End)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An association End is a property that has a reference to an association.
Attribute (Attribute)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An attribute is a property that has no reference to an association.
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 Event (Call Event)
A call event models the receipt by an object of a message invoking a call of an operation.
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.
Central Buffer (Object Node)
An object node is an abstract activity node that is part of defining object flow in an activity. Object nodes have support for token selection, limitation on the number of tokens, specifying the state required for tokens, and carrying control values.
A central buffer node is an object node for managing flows from multiple sources and destinations.
Choice (Pseudo State)
Choice vertices which, when reached, result in the dynamic evaluation of the guards of the triggers of its outgoing transitions. This realizes a dynamic conditional branch. It allows splitting of transitions into multiple outgoing paths such that the decision on which path to take may be a function of the results of prior actions performed in the same run-tocompletion step. If more than one of the guards evaluates to true, an arbitrary one is selected. If none of the guards evaluates to true, then the model is considered ill-formed. (To avoid this, it is recommended to define one outgoing transition with the predefined else guard for every choice vertex.) Choice vertices should be distinguished from static branch points that are based on junction points.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
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.
Collaboration (Collaboration)
A collaboration defines a set of co-operating roles used collectively to illustrate a specific functionality.
A collaboration should only show the roles and attributes required to accomplish its defined task or function. Isolating the primary roles is an exercise in simplifying the structure and clarifying the behavior, and also provides for re-use. A collaboration often implements a pattern.
Collaboration Use (Collaboration Use)
A collaboration use represents one particular use of a collaboration to explain the relationships between the properties of a classifier.
A collaboration use shows how the pattern described by a collaboration is applied in a given context, by binding specific entities from that context to the roles of the collaboration. Depending on the context, these entities could be structural features of a classifier, instance specifications, or even roles in some containing collaboration. There may be multiple occurrences of a given collaboration within a classifier, each involving a different set of roles and connectors.
A given role or connector may be involved in multiple occurrences of the same or different collaborations. Associated dependencies map features of the collaboration type to features in the classifier. These dependencies indicate which role in the classifier plays which role in the collaboration.
Combined Fragment (Combined Fragment)
A combined fragment defines an expression of interaction fragments. A combined fragment is defined by an interaction operator and corresponding interaction operands. Through the use of combined fragments the user will be able to describe a number of traces in a compact and concise manner.
Communication Path (Communication Path)
A communication path is an association between two deployment targets, through which they are able to exchange signals and messages.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Component Realization (Component Realization)
The realization concept is specialized to (optionally) define the classifiers that realize the contract offered by a component in terms of its provided and required interfaces.
The component forms an abstraction from these various
classifiers.
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.
Connection Point Reference (Connection Point Reference)
A connection point reference represents a usage (as part of a submachine state) of an entry/exit point defined in the statemachine reference by the submachine state.
Connector (Connector)
Specifies a link that enables communication between two or more instances. This link may be an instance of anassociation, or it may represent the possibility of the instances being able to communicate because their identitiesare known by virtue of being passed in as parameters, held in variables or slots, or because the communicatinginstances are the same instance.
The link may be realized by something as simple as a pointer or by something ascomplex as a network connection. In contrast to associations, which specify links between any instance of theassociated classifiers, connectors specify links between instances playing the connected parts only.
Control Flow (Control Flow)
A control flow is an edge that starts an activity node after the previous one is finished.
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.
Data Store Node (Object Node)
An object node is an abstract activity node that is part of defining object flow in an activity. Object nodes have support for token selection, limitation on the number of tokens, specifying the state required for tokens, and carrying control values.
A central buffer node is an object node for managing flows from multiple sources and destinations.
A data store node is a central buffer node for non-transient information.
Data Type (Data Type)
A data type is a type whose instances are identified only by their value. A data type may contain attributes to support the modeling of structured data types.
Decision Node (Control Node)
A control node is an abstract activity node that coordinates flows in an activity.
A decision node is a control node that chooses between outgoing flows.
Deep History (Pseudo State)
DeepHistory represents the most recent active configuration of the composite state that directly contains this pseudostate; e.g. the state configuration that was active when the composite state was last exited. A composite state can have at most one deep history vertex. At most one transition may originate from the history connector to the default deep history state. This transition is taken in case the composite state had never been active before. Entry actions of states entered on the path to the state represented by a deep history are performed.
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).
Deployment (Deployment)
A deployment is the allocation of an artifact or artifact instance to a deployment target. A component deployment is the deployment of one or more artifacts or artifact instances to a deployment target, optionally parameterized by a deployment specification. Examples are executables and configuration files.
Deployment Specification (Deployment Specification)
A deployment specification specifies a set of properties that determine execution parameters of a component artifact that is deployed on a node.
A deployment specification can be aimed at a specific type of container. An artifact that reifies or implements deployment specification properties is a deployment descriptor.
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.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Entry Point (Pseudo State)
An entry point pseudostate is an entry point of a state machine or composite state. In each region of the state machine or composite state it has a single transition to a vertex within the same region.
Enumeration (Enumeration)
An enumeration is a data type whose values are enumerated in the model as enumeration literals.
Enumeration Literal (Enumeration Literal)
An enumeration literal is a user-defined data value for an enumeration.
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Exit Point (Pseudo State)
An exit point pseudostate is an exit point of a state machine or composite state. Entering an exit point within any region of the composite state or state machine referenced by a submachine state implies the exit of this composite state or submachine state and the triggering of the transition that has this exit point as source in the state machine enclosing the submachine or composite state.
Expansion Node (Object Node)
An object node is an abstract activity node that is part of defining object flow in an activity. Object nodes have support for token selection, limitation on the number of tokens, specifying the state required for tokens, and carrying control values.
An expansion node is an object node used to indicate a flow across the boundary of an expansion region. A flow into a region contains a collection that is broken into its individual elements inside the region, which is executed once per element. A flow out of a region combines individual elements into a collection for use outside the region.
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.
Extend (Extend)
A relationship from an extending use case to an extended use case that specifies how and when the behavior defined in the extending use case can be inserted into the behavior defined in the extended use case.
Extension (Extension)
An extension is used to indicate that the properties of a metaclass are extended through a stereotype, and gives the ability to flexibly add (and later remove) stereotypes to classes.
Extension Point (Extension Point)
An extension point identifies a point in the behavior of a use case where that behavior can be extended by the behavior of some other (extending) use case, as specified by an extend relationship.
Final State (Final State)
A special kind of state signifying that the enclosing region is completed.
If the enclosing region is directly contained in a state machine and all other regions in the state machine also are completed, then it means that the entire state machine is completed.
Flow Final Node (Control Node)
A control node is an abstract activity node that coordinates flows in an activity.
A final node is an abstract control node at which a flow in an activity stops.
A flow final node is a final node that terminates a flow.
Fork (Pseudo State)
Fork vertices serve to split an incoming transition into two or more transitions terminating on orthogonal target vertices (i.e. vertices in different regions of a composite state). The segments outgoing from a fork vertex must not have guards or triggers.
Fork Node (Control Node)
A control node is an abstract activity node that coordinates flows in an activity.
A fork node is a control node that splits a flow into multiple concurrent flows.
Gate (Gate)
A gate is a connection point for relating a message outside an interaction fragment with a message inside the interaction fragment.
Guard (Guard)
A guard is a condition or restriction expressed in natural language text or in a machine readable language that must be fulfilled for a transition to become possible.
Include (Include)
An include relationship defines that a use case contains the behavior defined in another use case.
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.
Information Item (Information Item)
An information item is an abstraction of all kinds of information that can be exchanged between objects. It is a kind of
classifier intended for representing information in a very abstract way, one which cannot be instantiated.
Initial (Pseudo State)
An initial pseudostate represents a default vertex that is the source for a single transition to the default state of a composite state. There can be at most one initial vertex in a region. The outgoing transition from the initial vertex may have a behavior, but not a trigger or guard.
Initial Node (Control Node)
A control node is an abstract activity node that coordinates flows in an activity.
An initial node is a control node at which flow starts when the activity is invoked.
Input 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 input pin is a pin that holds input values to be consumed by an action.
Instance Specification (Instance Specification)
An instance specification is a model element that represents an instance in a modeled system.
An instance specification has the capability of being a deployment target in a deployment relationship, in the case that it is an instance of a node.
It is also has the capability of being a deployed artifact, if it is an instance of an artifact.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interaction Use (Interaction Use)
An interaction use refers to an interaction. The interaction use is a shorthand for copying the contents of the referenced interaction where the interaction use is. To be accurate the copying must take into account substituting parameters with arguments and connect the formal gates with the actual ones.
Interface (Interface)
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
Interface Realization (Interface Realization)
An interface realization is a specialized realization relationship between a classifier and an interface. This relationship signifies that the realizing classifier conforms to the contract specified by the interface.
Join (Pseudo State)
Join vertices serve to merge several transitions emanating from source vertices in different orthogonal regions. The transitions entering a join vertex cannot have guards or triggers.
Join Node (Control Node)
A control node is an abstract activity node that coordinates flows in an activity.
A join node is a control node that synchronizes multiple flows. Join nodes have a Boolean value specification using the names of the incoming edges to specify the conditions under which the join will emit a token.
Junction (Pseudo State)
Junction vertices are semantic-free vertices that are used to chain together multiple transitions. They are used to construct compound transition paths between states. For example, a junction can be used to converge multiple incoming transitions into a single outgoing transition representing a shared transition path (this is known as an merge). Conversely, they can be used to split an incoming transition into multiple outgoing transition segments with different guard conditions. This realizes a static conditional branch. (In the latter case, outgoing transitions whose guard conditions evaluate to false are disabled. A predefined guard denoted 'else' may be defined for at most one outgoing transition. This transition is enabled if all the guards labeling the other transitions are false.) Static conditional branches are distinct from dynamic conditional branches that are realized by choice vertices.
Lifeline (Lifeline)
A lifeline represents an individual participant in the interaction. While parts and structural features may have multiplicity greater than 1, lifelines represent only one interacting entity.
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.
Manifestation (Manifestation)
A manifestation is the concrete physical rendering of one or more model elements by an artifact.
Merge Node (Control Node)
A control node is an abstract activity node that coordinates flows in an activity.
A merge node is a control node that brings together multiple alternate flows. It is not used to synchronize concurrent flows but to accept one among several alternate flows.
Message (Message)
A message defines a particular communication between lifelines of an interaction.
Model (Model)
A model captures a view of a physical system. It is an abstraction of the physical system, with a certain purpose.
This purpose determines what is to be included in the model and what is irrelevant. Thus the model completely describes those aspects of the physical system that are relevant to the purpose of the model, at the appropriate level of detail.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Object Flow (Object Flow)
An object flow is an activity edge that can have objects or data passing along it. Object flows have support for multicast/receive, token selection from object nodes, and transformation of tokens.
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.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Operation (Operation)
An operation is a behavioral feature of a classifier that specifies the name, type, parameters, and constraints for invoking an associated behavior. An operation may invoke both the execution of method behaviors as well as other behavioral responses.
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.
Package (Package)
A package is used to group elements, and provides a namespace for the grouped elements.
A package can have one or more profile applications to indicate which profiles have been applied.
Parameter (Parameter)
A parameter is a specification of an argument used to pass information into or out of an invocation of a behavioral feature. Parameters are allowed to be treated as connectable elements. Parameters have support for streaming, exceptions, and parameter sets.
Port (Port)
A port is a property of a classifier that specifies a distinct interaction point between that classifier and its environment or between the (behavior of the) classifier and its internal parts.
Ports are connected to properties of the classifier by connectors through which requests can be made to invoke the behavioral features of a classifier.
A Port may specify the services a classifier provides (offers) to its environment as well as the services that a classifier expects (requires) of its environment. A port has an associated protocol state machine.
Primitive Type (Primitive Type)
A primitive type defines a predefined data type, without any relevant substructure (i.e., it has no parts in the context of UML). A primitive datatype may have an algebra and operations defined outside of UML, for example, mathematically.
Profile (Profile)
A profile defines limited extensions to a reference metamodel with the purpose of adapting the metamodel to a specific platform or domain.
Protocol (Protocol)
Only available together with the Real-Time Extension of RSA.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
Protocol Transition (Protocol Transition)
A protocol transition 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.
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.
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.
Reception (Reception)
A reception is a declaration stating that a classifier is prepared to react to the receipt of a signal. A reception designates a signal and specifies the expected behavioral response.
The details of handling a signal are specified by the behavior associated with the reception or the classifier itself.
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.
Region (Region)
A region is an orthogonal part of either a composite state or a state machine. It contains states and transitions.
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.
Shallow History (Pseudo State)
ShallowHistory represents the most recent active substate of its containing state (but not the substates of that substate). A composite state can have at most one shallow history vertex. A transition coming into the shallow history vertex is equivalent to a transition coming into the most recent active substate of a state. At most one transition may originate from the history connector to the default shallow history state. This transition is taken in case the composite state had never been active before. Entry actions of states entered on the path to the state represented by a shallow history are performed.
Signal (Signal)
A signal is a specification of send request instances communicated between objects. The receiving object handles the received request instances as specified by its receptions. The data carried by a send request (which was passed to it by the send invocation occurrence that caused that request) are represented as attributes of the signal.
A signal is defined independently of the classifiers handling the signal occurrence.
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
State (State)
A state models a situation during which some (usually implicit) invariant condition holds.
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.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
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.
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.
Terminate (Pseudo State)
Entering a terminate pseudostate implies that the execution of this state machine by means of its context object is terminated. The state machine does not exit any states nor does it perform any exit actions other than those associated with the transition leading to the terminate pseudostate. Entering a terminate pseudostate is equivalent to invoking a DestroyObjectAction.
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.
Transition (Transition)
A transition is a directed relationship between a source vertex and a target vertex.
It may be part of a compound transition, which takes the state machine from one state configuration to another, representing the complete response of the state machine to an occurrence of an event of a particular type.
Trigger (Trigger)
A trigger relates an event to a behavior that may affect an instance of the classifier. A trigger specification may be qualified by the port on which the event occurred.
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.
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.
Use Case (Use Case)
A use case is the specification of a set of actions performed by a system, which yields an observable result that is, typically, of value for one or more actors or other stakeholders of the system.
Value 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 input pin is a pin that holds input values to be consumed by an action.
A value pin is an input pin that provides a value by evaluating a value specification.
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.
An item of one of the following item kinds:
Abstraction (Abstraction)Accept Call Action (Action)Accept Event Action (Action)Action Input Pin (Pin)Activity (Activity)Activity Final Node (Control Node)Activity Parameter Node (Object Node)Activity Partition (Activity Partition)Actor (Actor)Add Structural Feature Value Action (Action)Add Variable Value Action (Action)Artifact (Artifact)Association (Association)Association End (Association End)Attribute (Attribute)Broadcast Signal Action (Action)Call Behavior Action (Action)Call Event (Call Event)Call Operation Action (Action)Central Buffer (Object Node)Choice (Pseudo State)Class (Class)Clear Association Action (Action)Clear Structural Feature Action (Action)Clear Variable Action (Action)Collaboration (Collaboration)Collaboration Use (Collaboration Use)Combined Fragment (Combined Fragment)Communication Path (Communication Path)Component (Component)Component Realization (Component Realization)Conditional Node (Action)Connection Point Reference (Connection Point Reference)Connector (Connector)Control Flow (Control Flow)Create Link Action (Action)Create Link Object Action (Action)Create Object Action (Action)Data Store Node (Object Node)Data Type (Data Type)Decision Node (Control Node)Deep History (Pseudo State)Dependency (Dependency)Deployment (Deployment)Deployment Specification (Deployment Specification)Destroy Link Action (Action)Destroy Object Action (Action)Device (Device)Entry Point (Pseudo State)Enumeration (Enumeration)Enumeration Literal (Enumeration Literal)Execution Environment (Execution Environment)Exit Point (Pseudo State)Expansion Node (Object Node)Expansion Region (Action)Extend (Extend)Extension (Extension)Extension Point (Extension Point)Final State (Final State)Flow Final Node (Control Node)Fork (Pseudo State)Fork Node (Control Node)Gate (Gate)Guard (Guard)Include (Include)Information Flow (Information Flow)Information Item (Information Item)Initial (Pseudo State)Initial Node (Control Node)Input Pin (Pin)Instance Specification (Instance Specification)Interaction (Interaction)Interaction Use (Interaction Use)Interface (Interface)Interface Realization (Interface Realization)Join (Pseudo State)Join Node (Control Node)Junction (Pseudo State)Lifeline (Lifeline)Loop Node (Action)Manifestation (Manifestation)Merge Node (Control Node)Message (Message)Model (Model)Node (Node)Object Flow (Object Flow)Opaque Action (Action)Opaque Behavior (Opaque Behavior)Operation (Operation)Output Pin (Pin)Package (Package)Parameter (Parameter)Port (Port)Primitive Type (Primitive Type)Profile (Profile)Protocol (Protocol)Protocol State Machine (Protocol State Machine)Protocol Transition (Protocol Transition)Raise Exception Action (Action)Read Extent Action (Action)Read Is Classified Object Action (Action)Read Link Action (Action)Read Link Object End Action (Action)Read Link Object End Qualifier Action (Action)Read Self Action (Action)Read Structural Feature Action (Action)Read Variable Action (Action)Realization (Realization)Reception (Reception)Reclassify Object Action (Action)Reduce Action (Action)Region (Region)Remove Structural Feature Value Action (Action)Remove Variable Value Action (Action)Reply Action (Action)Send Object Action (Action)Send Signal Action (Action)Sequence Node (Action)Shallow History (Pseudo State)Signal (Signal)Start Classifier Behavior Action (Action)Start Object Behavior Action (Action)State (State)State Machine (State Machine)Stereotype (Stereotype)Structured Activity Node (Action)Structured Activity Node (Structured Activity Node)Substitution (Substitution)Terminate (Pseudo State)Test Identity Action (Action)Transition (Transition)Trigger (Trigger)Unmarshall Action (Action)Usage (Usage)Use Case (Use Case)Value Pin (Pin)Value Specification Action (Action)Abstraction (Abstraction)Dependency (Dependency)Information Flow (Information Flow)Realization (Realization)Substitution (Substitution)Usage (Usage) SubstitutionA 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.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
An element of one of the following kinds:
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.
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.
Action Input 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 input pin is a pin that holds input values to be consumed by an action.
An action input pin is a kind of pin that executes an action to determine the values to input to another.
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Activity Final Node (Control Node)
A control node is an abstract activity node that coordinates flows in an activity.
A final node is an abstract control node at which a flow in an activity stops.
An activity final node is a final node that stops all flows in an activity.
Activity Parameter Node (Object Node)
An object node is an abstract activity node that is part of defining object flow in an activity. Object nodes have support for token selection, limitation on the number of tokens, specifying the state required for tokens, and carrying control values.
An activity parameter node is an object node for inputs and outputs to activities.
Activity Partition (Activity Partition)
An activity partition is a kind of activity group for identifying actions that have some characteristic in common.
Actor (Actor)
An actor specifies a role played by a user or any other system that interacts with the subject.
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.
Artifact (Artifact)
An artifact is the specification of a physical piece of information that is used or produced by a software development process, or by deployment and operation of a system.
Examples of artifacts include model files, source files, scripts, and binary executable files, a table in a database system, a development deliverable, or a word-processing document, a mail message. An artifact is the source of a deployment to a node.
Association (Association)
An association describes a set of tuples whose values refer to typed instances. An instance of an association is called a link.
Association End (Association End)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An association End is a property that has a reference to an association.
Attribute (Attribute)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An attribute is a property that has no reference to an association.
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 Event (Call Event)
A call event models the receipt by an object of a message invoking a call of an operation.
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.
Central Buffer (Object Node)
An object node is an abstract activity node that is part of defining object flow in an activity. Object nodes have support for token selection, limitation on the number of tokens, specifying the state required for tokens, and carrying control values.
A central buffer node is an object node for managing flows from multiple sources and destinations.
Choice (Pseudo State)
Choice vertices which, when reached, result in the dynamic evaluation of the guards of the triggers of its outgoing transitions. This realizes a dynamic conditional branch. It allows splitting of transitions into multiple outgoing paths such that the decision on which path to take may be a function of the results of prior actions performed in the same run-tocompletion step. If more than one of the guards evaluates to true, an arbitrary one is selected. If none of the guards evaluates to true, then the model is considered ill-formed. (To avoid this, it is recommended to define one outgoing transition with the predefined else guard for every choice vertex.) Choice vertices should be distinguished from static branch points that are based on junction points.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
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.
Collaboration (Collaboration)
A collaboration defines a set of co-operating roles used collectively to illustrate a specific functionality.
A collaboration should only show the roles and attributes required to accomplish its defined task or function. Isolating the primary roles is an exercise in simplifying the structure and clarifying the behavior, and also provides for re-use. A collaboration often implements a pattern.
Collaboration Use (Collaboration Use)
A collaboration use represents one particular use of a collaboration to explain the relationships between the properties of a classifier.
A collaboration use shows how the pattern described by a collaboration is applied in a given context, by binding specific entities from that context to the roles of the collaboration. Depending on the context, these entities could be structural features of a classifier, instance specifications, or even roles in some containing collaboration. There may be multiple occurrences of a given collaboration within a classifier, each involving a different set of roles and connectors.
A given role or connector may be involved in multiple occurrences of the same or different collaborations. Associated dependencies map features of the collaboration type to features in the classifier. These dependencies indicate which role in the classifier plays which role in the collaboration.
Combined Fragment (Combined Fragment)
A combined fragment defines an expression of interaction fragments. A combined fragment is defined by an interaction operator and corresponding interaction operands. Through the use of combined fragments the user will be able to describe a number of traces in a compact and concise manner.
Communication Path (Communication Path)
A communication path is an association between two deployment targets, through which they are able to exchange signals and messages.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Component Realization (Component Realization)
The realization concept is specialized to (optionally) define the classifiers that realize the contract offered by a component in terms of its provided and required interfaces.
The component forms an abstraction from these various
classifiers.
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.
Connection Point Reference (Connection Point Reference)
A connection point reference represents a usage (as part of a submachine state) of an entry/exit point defined in the statemachine reference by the submachine state.
Connector (Connector)
Specifies a link that enables communication between two or more instances. This link may be an instance of anassociation, or it may represent the possibility of the instances being able to communicate because their identitiesare known by virtue of being passed in as parameters, held in variables or slots, or because the communicatinginstances are the same instance.
The link may be realized by something as simple as a pointer or by something ascomplex as a network connection. In contrast to associations, which specify links between any instance of theassociated classifiers, connectors specify links between instances playing the connected parts only.
Control Flow (Control Flow)
A control flow is an edge that starts an activity node after the previous one is finished.
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.
Data Store Node (Object Node)
An object node is an abstract activity node that is part of defining object flow in an activity. Object nodes have support for token selection, limitation on the number of tokens, specifying the state required for tokens, and carrying control values.
A central buffer node is an object node for managing flows from multiple sources and destinations.
A data store node is a central buffer node for non-transient information.
Data Type (Data Type)
A data type is a type whose instances are identified only by their value. A data type may contain attributes to support the modeling of structured data types.
Decision Node (Control Node)
A control node is an abstract activity node that coordinates flows in an activity.
A decision node is a control node that chooses between outgoing flows.
Deep History (Pseudo State)
DeepHistory represents the most recent active configuration of the composite state that directly contains this pseudostate; e.g. the state configuration that was active when the composite state was last exited. A composite state can have at most one deep history vertex. At most one transition may originate from the history connector to the default deep history state. This transition is taken in case the composite state had never been active before. Entry actions of states entered on the path to the state represented by a deep history are performed.
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).
Deployment (Deployment)
A deployment is the allocation of an artifact or artifact instance to a deployment target. A component deployment is the deployment of one or more artifacts or artifact instances to a deployment target, optionally parameterized by a deployment specification. Examples are executables and configuration files.
Deployment Specification (Deployment Specification)
A deployment specification specifies a set of properties that determine execution parameters of a component artifact that is deployed on a node.
A deployment specification can be aimed at a specific type of container. An artifact that reifies or implements deployment specification properties is a deployment descriptor.
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.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Entry Point (Pseudo State)
An entry point pseudostate is an entry point of a state machine or composite state. In each region of the state machine or composite state it has a single transition to a vertex within the same region.
Enumeration (Enumeration)
An enumeration is a data type whose values are enumerated in the model as enumeration literals.
Enumeration Literal (Enumeration Literal)
An enumeration literal is a user-defined data value for an enumeration.
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Exit Point (Pseudo State)
An exit point pseudostate is an exit point of a state machine or composite state. Entering an exit point within any region of the composite state or state machine referenced by a submachine state implies the exit of this composite state or submachine state and the triggering of the transition that has this exit point as source in the state machine enclosing the submachine or composite state.
Expansion Node (Object Node)
An object node is an abstract activity node that is part of defining object flow in an activity. Object nodes have support for token selection, limitation on the number of tokens, specifying the state required for tokens, and carrying control values.
An expansion node is an object node used to indicate a flow across the boundary of an expansion region. A flow into a region contains a collection that is broken into its individual elements inside the region, which is executed once per element. A flow out of a region combines individual elements into a collection for use outside the region.
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.
Extend (Extend)
A relationship from an extending use case to an extended use case that specifies how and when the behavior defined in the extending use case can be inserted into the behavior defined in the extended use case.
Extension (Extension)
An extension is used to indicate that the properties of a metaclass are extended through a stereotype, and gives the ability to flexibly add (and later remove) stereotypes to classes.
Extension Point (Extension Point)
An extension point identifies a point in the behavior of a use case where that behavior can be extended by the behavior of some other (extending) use case, as specified by an extend relationship.
Final State (Final State)
A special kind of state signifying that the enclosing region is completed.
If the enclosing region is directly contained in a state machine and all other regions in the state machine also are completed, then it means that the entire state machine is completed.
Flow Final Node (Control Node)
A control node is an abstract activity node that coordinates flows in an activity.
A final node is an abstract control node at which a flow in an activity stops.
A flow final node is a final node that terminates a flow.
Fork (Pseudo State)
Fork vertices serve to split an incoming transition into two or more transitions terminating on orthogonal target vertices (i.e. vertices in different regions of a composite state). The segments outgoing from a fork vertex must not have guards or triggers.
Fork Node (Control Node)
A control node is an abstract activity node that coordinates flows in an activity.
A fork node is a control node that splits a flow into multiple concurrent flows.
Gate (Gate)
A gate is a connection point for relating a message outside an interaction fragment with a message inside the interaction fragment.
Guard (Guard)
A guard is a condition or restriction expressed in natural language text or in a machine readable language that must be fulfilled for a transition to become possible.
Include (Include)
An include relationship defines that a use case contains the behavior defined in another use case.
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.
Information Item (Information Item)
An information item is an abstraction of all kinds of information that can be exchanged between objects. It is a kind of
classifier intended for representing information in a very abstract way, one which cannot be instantiated.
Initial (Pseudo State)
An initial pseudostate represents a default vertex that is the source for a single transition to the default state of a composite state. There can be at most one initial vertex in a region. The outgoing transition from the initial vertex may have a behavior, but not a trigger or guard.
Initial Node (Control Node)
A control node is an abstract activity node that coordinates flows in an activity.
An initial node is a control node at which flow starts when the activity is invoked.
Input 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 input pin is a pin that holds input values to be consumed by an action.
Instance Specification (Instance Specification)
An instance specification is a model element that represents an instance in a modeled system.
An instance specification has the capability of being a deployment target in a deployment relationship, in the case that it is an instance of a node.
It is also has the capability of being a deployed artifact, if it is an instance of an artifact.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interaction Use (Interaction Use)
An interaction use refers to an interaction. The interaction use is a shorthand for copying the contents of the referenced interaction where the interaction use is. To be accurate the copying must take into account substituting parameters with arguments and connect the formal gates with the actual ones.
Interface (Interface)
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
Interface Realization (Interface Realization)
An interface realization is a specialized realization relationship between a classifier and an interface. This relationship signifies that the realizing classifier conforms to the contract specified by the interface.
Join (Pseudo State)
Join vertices serve to merge several transitions emanating from source vertices in different orthogonal regions. The transitions entering a join vertex cannot have guards or triggers.
Join Node (Control Node)
A control node is an abstract activity node that coordinates flows in an activity.
A join node is a control node that synchronizes multiple flows. Join nodes have a Boolean value specification using the names of the incoming edges to specify the conditions under which the join will emit a token.
Junction (Pseudo State)
Junction vertices are semantic-free vertices that are used to chain together multiple transitions. They are used to construct compound transition paths between states. For example, a junction can be used to converge multiple incoming transitions into a single outgoing transition representing a shared transition path (this is known as an merge). Conversely, they can be used to split an incoming transition into multiple outgoing transition segments with different guard conditions. This realizes a static conditional branch. (In the latter case, outgoing transitions whose guard conditions evaluate to false are disabled. A predefined guard denoted 'else' may be defined for at most one outgoing transition. This transition is enabled if all the guards labeling the other transitions are false.) Static conditional branches are distinct from dynamic conditional branches that are realized by choice vertices.
Lifeline (Lifeline)
A lifeline represents an individual participant in the interaction. While parts and structural features may have multiplicity greater than 1, lifelines represent only one interacting entity.
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.
Manifestation (Manifestation)
A manifestation is the concrete physical rendering of one or more model elements by an artifact.
Merge Node (Control Node)
A control node is an abstract activity node that coordinates flows in an activity.
A merge node is a control node that brings together multiple alternate flows. It is not used to synchronize concurrent flows but to accept one among several alternate flows.
Message (Message)
A message defines a particular communication between lifelines of an interaction.
Model (Model)
A model captures a view of a physical system. It is an abstraction of the physical system, with a certain purpose.
This purpose determines what is to be included in the model and what is irrelevant. Thus the model completely describes those aspects of the physical system that are relevant to the purpose of the model, at the appropriate level of detail.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Object Flow (Object Flow)
An object flow is an activity edge that can have objects or data passing along it. Object flows have support for multicast/receive, token selection from object nodes, and transformation of tokens.
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.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Operation (Operation)
An operation is a behavioral feature of a classifier that specifies the name, type, parameters, and constraints for invoking an associated behavior. An operation may invoke both the execution of method behaviors as well as other behavioral responses.
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.
Package (Package)
A package is used to group elements, and provides a namespace for the grouped elements.
A package can have one or more profile applications to indicate which profiles have been applied.
Parameter (Parameter)
A parameter is a specification of an argument used to pass information into or out of an invocation of a behavioral feature. Parameters are allowed to be treated as connectable elements. Parameters have support for streaming, exceptions, and parameter sets.
Port (Port)
A port is a property of a classifier that specifies a distinct interaction point between that classifier and its environment or between the (behavior of the) classifier and its internal parts.
Ports are connected to properties of the classifier by connectors through which requests can be made to invoke the behavioral features of a classifier.
A Port may specify the services a classifier provides (offers) to its environment as well as the services that a classifier expects (requires) of its environment. A port has an associated protocol state machine.
Primitive Type (Primitive Type)
A primitive type defines a predefined data type, without any relevant substructure (i.e., it has no parts in the context of UML). A primitive datatype may have an algebra and operations defined outside of UML, for example, mathematically.
Profile (Profile)
A profile defines limited extensions to a reference metamodel with the purpose of adapting the metamodel to a specific platform or domain.
Protocol (Protocol)
Only available together with the Real-Time Extension of RSA.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
Protocol Transition (Protocol Transition)
A protocol transition 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.
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.
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.
Reception (Reception)
A reception is a declaration stating that a classifier is prepared to react to the receipt of a signal. A reception designates a signal and specifies the expected behavioral response.
The details of handling a signal are specified by the behavior associated with the reception or the classifier itself.
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.
Region (Region)
A region is an orthogonal part of either a composite state or a state machine. It contains states and transitions.
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.
Shallow History (Pseudo State)
ShallowHistory represents the most recent active substate of its containing state (but not the substates of that substate). A composite state can have at most one shallow history vertex. A transition coming into the shallow history vertex is equivalent to a transition coming into the most recent active substate of a state. At most one transition may originate from the history connector to the default shallow history state. This transition is taken in case the composite state had never been active before. Entry actions of states entered on the path to the state represented by a shallow history are performed.
Signal (Signal)
A signal is a specification of send request instances communicated between objects. The receiving object handles the received request instances as specified by its receptions. The data carried by a send request (which was passed to it by the send invocation occurrence that caused that request) are represented as attributes of the signal.
A signal is defined independently of the classifiers handling the signal occurrence.
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
State (State)
A state models a situation during which some (usually implicit) invariant condition holds.
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.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
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.
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.
Terminate (Pseudo State)
Entering a terminate pseudostate implies that the execution of this state machine by means of its context object is terminated. The state machine does not exit any states nor does it perform any exit actions other than those associated with the transition leading to the terminate pseudostate. Entering a terminate pseudostate is equivalent to invoking a DestroyObjectAction.
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.
Transition (Transition)
A transition is a directed relationship between a source vertex and a target vertex.
It may be part of a compound transition, which takes the state machine from one state configuration to another, representing the complete response of the state machine to an occurrence of an event of a particular type.
Trigger (Trigger)
A trigger relates an event to a behavior that may affect an instance of the classifier. A trigger specification may be qualified by the port on which the event occurred.
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.
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.
Use Case (Use Case)
A use case is the specification of a set of actions performed by a system, which yields an observable result that is, typically, of value for one or more actors or other stakeholders of the system.
Value 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 input pin is a pin that holds input values to be consumed by an action.
A value pin is an input pin that provides a value by evaluating a value specification.
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.
An item of one of the following item kinds:
Abstraction (Abstraction)Accept Call Action (Action)Accept Event Action (Action)Action Input Pin (Pin)Activity (Activity)Activity Final Node (Control Node)Activity Parameter Node (Object Node)Activity Partition (Activity Partition)Actor (Actor)Add Structural Feature Value Action (Action)Add Variable Value Action (Action)Artifact (Artifact)Association (Association)Association End (Association End)Attribute (Attribute)Broadcast Signal Action (Action)Call Behavior Action (Action)Call Event (Call Event)Call Operation Action (Action)Central Buffer (Object Node)Choice (Pseudo State)Class (Class)Clear Association Action (Action)Clear Structural Feature Action (Action)Clear Variable Action (Action)Collaboration (Collaboration)Collaboration Use (Collaboration Use)Combined Fragment (Combined Fragment)Communication Path (Communication Path)Component (Component)Component Realization (Component Realization)Conditional Node (Action)Connection Point Reference (Connection Point Reference)Connector (Connector)Control Flow (Control Flow)Create Link Action (Action)Create Link Object Action (Action)Create Object Action (Action)Data Store Node (Object Node)Data Type (Data Type)Decision Node (Control Node)Deep History (Pseudo State)Dependency (Dependency)Deployment (Deployment)Deployment Specification (Deployment Specification)Destroy Link Action (Action)Destroy Object Action (Action)Device (Device)Entry Point (Pseudo State)Enumeration (Enumeration)Enumeration Literal (Enumeration Literal)Execution Environment (Execution Environment)Exit Point (Pseudo State)Expansion Node (Object Node)Expansion Region (Action)Extend (Extend)Extension (Extension)Extension Point (Extension Point)Final State (Final State)Flow Final Node (Control Node)Fork (Pseudo State)Fork Node (Control Node)Gate (Gate)Guard (Guard)Include (Include)Information Flow (Information Flow)Information Item (Information Item)Initial (Pseudo State)Initial Node (Control Node)Input Pin (Pin)Instance Specification (Instance Specification)Interaction (Interaction)Interaction Use (Interaction Use)Interface (Interface)Interface Realization (Interface Realization)Join (Pseudo State)Join Node (Control Node)Junction (Pseudo State)Lifeline (Lifeline)Loop Node (Action)Manifestation (Manifestation)Merge Node (Control Node)Message (Message)Model (Model)Node (Node)Object Flow (Object Flow)Opaque Action (Action)Opaque Behavior (Opaque Behavior)Operation (Operation)Output Pin (Pin)Package (Package)Parameter (Parameter)Port (Port)Primitive Type (Primitive Type)Profile (Profile)Protocol (Protocol)Protocol State Machine (Protocol State Machine)Protocol Transition (Protocol Transition)Raise Exception Action (Action)Read Extent Action (Action)Read Is Classified Object Action (Action)Read Link Action (Action)Read Link Object End Action (Action)Read Link Object End Qualifier Action (Action)Read Self Action (Action)Read Structural Feature Action (Action)Read Variable Action (Action)Realization (Realization)Reception (Reception)Reclassify Object Action (Action)Reduce Action (Action)Region (Region)Remove Structural Feature Value Action (Action)Remove Variable Value Action (Action)Reply Action (Action)Send Object Action (Action)Send Signal Action (Action)Sequence Node (Action)Shallow History (Pseudo State)Signal (Signal)Start Classifier Behavior Action (Action)Start Object Behavior Action (Action)State (State)State Machine (State Machine)Stereotype (Stereotype)Structured Activity Node (Action)Structured Activity Node (Structured Activity Node)Substitution (Substitution)Terminate (Pseudo State)Test Identity Action (Action)Transition (Transition)Trigger (Trigger)Unmarshall Action (Action)Usage (Usage)Use Case (Use Case)Value Pin (Pin)Value Specification Action (Action)Abstraction (Abstraction)Dependency (Dependency)Information Flow (Information Flow)Realization (Realization)Substitution (Substitution)Usage (Usage) TemplatebindingA template binding represents a relationship between a templateable element and a template. A template binding specifies the substitutions of actual parameters for the formal parameters of the template.
Template Signature.
The template signature for the template that is the target of the binding.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Actor (Actor)
An actor specifies a role played by a user or any other system that interacts with the subject.
Artifact (Artifact)
An artifact is the specification of a physical piece of information that is used or produced by a software development process, or by deployment and operation of a system.
Examples of artifacts include model files, source files, scripts, and binary executable files, a table in a database system, a development deliverable, or a word-processing document, a mail message. An artifact is the source of a deployment to a node.
Association (Association)
An association describes a set of tuples whose values refer to typed instances. An instance of an association is called a link.
Association End (Association End)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An association End is a property that has a reference to an association.
Attribute (Attribute)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An attribute is a property that has no reference to an association.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
Collaboration (Collaboration)
A collaboration defines a set of co-operating roles used collectively to illustrate a specific functionality.
A collaboration should only show the roles and attributes required to accomplish its defined task or function. Isolating the primary roles is an exercise in simplifying the structure and clarifying the behavior, and also provides for re-use. A collaboration often implements a pattern.
Communication Path (Communication Path)
A communication path is an association between two deployment targets, through which they are able to exchange signals and messages.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Data Type (Data Type)
A data type is a type whose instances are identified only by their value. A data type may contain attributes to support the modeling of structured data types.
Deployment Specification (Deployment Specification)
A deployment specification specifies a set of properties that determine execution parameters of a component artifact that is deployed on a node.
A deployment specification can be aimed at a specific type of container. An artifact that reifies or implements deployment specification properties is a deployment descriptor.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Enumeration (Enumeration)
An enumeration is a data type whose values are enumerated in the model as enumeration literals.
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Extension (Extension)
An extension is used to indicate that the properties of a metaclass are extended through a stereotype, and gives the ability to flexibly add (and later remove) stereotypes to classes.
Information Item (Information Item)
An information item is an abstraction of all kinds of information that can be exchanged between objects. It is a kind of
classifier intended for representing information in a very abstract way, one which cannot be instantiated.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interface (Interface)
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
Model (Model)
A model captures a view of a physical system. It is an abstraction of the physical system, with a certain purpose.
This purpose determines what is to be included in the model and what is irrelevant. Thus the model completely describes those aspects of the physical system that are relevant to the purpose of the model, at the appropriate level of detail.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Operation (Operation)
An operation is a behavioral feature of a classifier that specifies the name, type, parameters, and constraints for invoking an associated behavior. An operation may invoke both the execution of method behaviors as well as other behavioral responses.
Package (Package)
A package is used to group elements, and provides a namespace for the grouped elements.
A package can have one or more profile applications to indicate which profiles have been applied.
Port (Port)
A port is a property of a classifier that specifies a distinct interaction point between that classifier and its environment or between the (behavior of the) classifier and its internal parts.
Ports are connected to properties of the classifier by connectors through which requests can be made to invoke the behavioral features of a classifier.
A Port may specify the services a classifier provides (offers) to its environment as well as the services that a classifier expects (requires) of its environment. A port has an associated protocol state machine.
Primitive Type (Primitive Type)
A primitive type defines a predefined data type, without any relevant substructure (i.e., it has no parts in the context of UML). A primitive datatype may have an algebra and operations defined outside of UML, for example, mathematically.
Profile (Profile)
A profile defines limited extensions to a reference metamodel with the purpose of adapting the metamodel to a specific platform or domain.
Protocol (Protocol)
Only available together with the Real-Time Extension of RSA.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
Signal (Signal)
A signal is a specification of send request instances communicated between objects. The receiving object handles the received request instances as specified by its receptions. The data carried by a send request (which was passed to it by the send invocation occurrence that caused that request) are represented as attributes of the signal.
A signal is defined independently of the classifiers handling the signal occurrence.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
Use Case (Use Case)
A use case is the specification of a set of actions performed by a system, which yields an observable result that is, typically, of value for one or more actors or other stakeholders of the system.
UsageA 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.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
An element of one of the following kinds:
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.
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.
Action Input 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 input pin is a pin that holds input values to be consumed by an action.
An action input pin is a kind of pin that executes an action to determine the values to input to another.
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Activity Final Node (Control Node)
A control node is an abstract activity node that coordinates flows in an activity.
A final node is an abstract control node at which a flow in an activity stops.
An activity final node is a final node that stops all flows in an activity.
Activity Parameter Node (Object Node)
An object node is an abstract activity node that is part of defining object flow in an activity. Object nodes have support for token selection, limitation on the number of tokens, specifying the state required for tokens, and carrying control values.
An activity parameter node is an object node for inputs and outputs to activities.
Activity Partition (Activity Partition)
An activity partition is a kind of activity group for identifying actions that have some characteristic in common.
Actor (Actor)
An actor specifies a role played by a user or any other system that interacts with the subject.
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.
Artifact (Artifact)
An artifact is the specification of a physical piece of information that is used or produced by a software development process, or by deployment and operation of a system.
Examples of artifacts include model files, source files, scripts, and binary executable files, a table in a database system, a development deliverable, or a word-processing document, a mail message. An artifact is the source of a deployment to a node.
Association (Association)
An association describes a set of tuples whose values refer to typed instances. An instance of an association is called a link.
Association End (Association End)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An association End is a property that has a reference to an association.
Attribute (Attribute)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An attribute is a property that has no reference to an association.
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 Event (Call Event)
A call event models the receipt by an object of a message invoking a call of an operation.
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.
Central Buffer (Object Node)
An object node is an abstract activity node that is part of defining object flow in an activity. Object nodes have support for token selection, limitation on the number of tokens, specifying the state required for tokens, and carrying control values.
A central buffer node is an object node for managing flows from multiple sources and destinations.
Choice (Pseudo State)
Choice vertices which, when reached, result in the dynamic evaluation of the guards of the triggers of its outgoing transitions. This realizes a dynamic conditional branch. It allows splitting of transitions into multiple outgoing paths such that the decision on which path to take may be a function of the results of prior actions performed in the same run-tocompletion step. If more than one of the guards evaluates to true, an arbitrary one is selected. If none of the guards evaluates to true, then the model is considered ill-formed. (To avoid this, it is recommended to define one outgoing transition with the predefined else guard for every choice vertex.) Choice vertices should be distinguished from static branch points that are based on junction points.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
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.
Collaboration (Collaboration)
A collaboration defines a set of co-operating roles used collectively to illustrate a specific functionality.
A collaboration should only show the roles and attributes required to accomplish its defined task or function. Isolating the primary roles is an exercise in simplifying the structure and clarifying the behavior, and also provides for re-use. A collaboration often implements a pattern.
Collaboration Use (Collaboration Use)
A collaboration use represents one particular use of a collaboration to explain the relationships between the properties of a classifier.
A collaboration use shows how the pattern described by a collaboration is applied in a given context, by binding specific entities from that context to the roles of the collaboration. Depending on the context, these entities could be structural features of a classifier, instance specifications, or even roles in some containing collaboration. There may be multiple occurrences of a given collaboration within a classifier, each involving a different set of roles and connectors.
A given role or connector may be involved in multiple occurrences of the same or different collaborations. Associated dependencies map features of the collaboration type to features in the classifier. These dependencies indicate which role in the classifier plays which role in the collaboration.
Combined Fragment (Combined Fragment)
A combined fragment defines an expression of interaction fragments. A combined fragment is defined by an interaction operator and corresponding interaction operands. Through the use of combined fragments the user will be able to describe a number of traces in a compact and concise manner.
Communication Path (Communication Path)
A communication path is an association between two deployment targets, through which they are able to exchange signals and messages.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Component Realization (Component Realization)
The realization concept is specialized to (optionally) define the classifiers that realize the contract offered by a component in terms of its provided and required interfaces.
The component forms an abstraction from these various
classifiers.
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.
Connection Point Reference (Connection Point Reference)
A connection point reference represents a usage (as part of a submachine state) of an entry/exit point defined in the statemachine reference by the submachine state.
Connector (Connector)
Specifies a link that enables communication between two or more instances. This link may be an instance of anassociation, or it may represent the possibility of the instances being able to communicate because their identitiesare known by virtue of being passed in as parameters, held in variables or slots, or because the communicatinginstances are the same instance.
The link may be realized by something as simple as a pointer or by something ascomplex as a network connection. In contrast to associations, which specify links between any instance of theassociated classifiers, connectors specify links between instances playing the connected parts only.
Control Flow (Control Flow)
A control flow is an edge that starts an activity node after the previous one is finished.
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.
Data Store Node (Object Node)
An object node is an abstract activity node that is part of defining object flow in an activity. Object nodes have support for token selection, limitation on the number of tokens, specifying the state required for tokens, and carrying control values.
A central buffer node is an object node for managing flows from multiple sources and destinations.
A data store node is a central buffer node for non-transient information.
Data Type (Data Type)
A data type is a type whose instances are identified only by their value. A data type may contain attributes to support the modeling of structured data types.
Decision Node (Control Node)
A control node is an abstract activity node that coordinates flows in an activity.
A decision node is a control node that chooses between outgoing flows.
Deep History (Pseudo State)
DeepHistory represents the most recent active configuration of the composite state that directly contains this pseudostate; e.g. the state configuration that was active when the composite state was last exited. A composite state can have at most one deep history vertex. At most one transition may originate from the history connector to the default deep history state. This transition is taken in case the composite state had never been active before. Entry actions of states entered on the path to the state represented by a deep history are performed.
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).
Deployment (Deployment)
A deployment is the allocation of an artifact or artifact instance to a deployment target. A component deployment is the deployment of one or more artifacts or artifact instances to a deployment target, optionally parameterized by a deployment specification. Examples are executables and configuration files.
Deployment Specification (Deployment Specification)
A deployment specification specifies a set of properties that determine execution parameters of a component artifact that is deployed on a node.
A deployment specification can be aimed at a specific type of container. An artifact that reifies or implements deployment specification properties is a deployment descriptor.
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.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Entry Point (Pseudo State)
An entry point pseudostate is an entry point of a state machine or composite state. In each region of the state machine or composite state it has a single transition to a vertex within the same region.
Enumeration (Enumeration)
An enumeration is a data type whose values are enumerated in the model as enumeration literals.
Enumeration Literal (Enumeration Literal)
An enumeration literal is a user-defined data value for an enumeration.
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Exit Point (Pseudo State)
An exit point pseudostate is an exit point of a state machine or composite state. Entering an exit point within any region of the composite state or state machine referenced by a submachine state implies the exit of this composite state or submachine state and the triggering of the transition that has this exit point as source in the state machine enclosing the submachine or composite state.
Expansion Node (Object Node)
An object node is an abstract activity node that is part of defining object flow in an activity. Object nodes have support for token selection, limitation on the number of tokens, specifying the state required for tokens, and carrying control values.
An expansion node is an object node used to indicate a flow across the boundary of an expansion region. A flow into a region contains a collection that is broken into its individual elements inside the region, which is executed once per element. A flow out of a region combines individual elements into a collection for use outside the region.
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.
Extend (Extend)
A relationship from an extending use case to an extended use case that specifies how and when the behavior defined in the extending use case can be inserted into the behavior defined in the extended use case.
Extension (Extension)
An extension is used to indicate that the properties of a metaclass are extended through a stereotype, and gives the ability to flexibly add (and later remove) stereotypes to classes.
Extension Point (Extension Point)
An extension point identifies a point in the behavior of a use case where that behavior can be extended by the behavior of some other (extending) use case, as specified by an extend relationship.
Final State (Final State)
A special kind of state signifying that the enclosing region is completed.
If the enclosing region is directly contained in a state machine and all other regions in the state machine also are completed, then it means that the entire state machine is completed.
Flow Final Node (Control Node)
A control node is an abstract activity node that coordinates flows in an activity.
A final node is an abstract control node at which a flow in an activity stops.
A flow final node is a final node that terminates a flow.
Fork (Pseudo State)
Fork vertices serve to split an incoming transition into two or more transitions terminating on orthogonal target vertices (i.e. vertices in different regions of a composite state). The segments outgoing from a fork vertex must not have guards or triggers.
Fork Node (Control Node)
A control node is an abstract activity node that coordinates flows in an activity.
A fork node is a control node that splits a flow into multiple concurrent flows.
Gate (Gate)
A gate is a connection point for relating a message outside an interaction fragment with a message inside the interaction fragment.
Guard (Guard)
A guard is a condition or restriction expressed in natural language text or in a machine readable language that must be fulfilled for a transition to become possible.
Include (Include)
An include relationship defines that a use case contains the behavior defined in another use case.
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.
Information Item (Information Item)
An information item is an abstraction of all kinds of information that can be exchanged between objects. It is a kind of
classifier intended for representing information in a very abstract way, one which cannot be instantiated.
Initial (Pseudo State)
An initial pseudostate represents a default vertex that is the source for a single transition to the default state of a composite state. There can be at most one initial vertex in a region. The outgoing transition from the initial vertex may have a behavior, but not a trigger or guard.
Initial Node (Control Node)
A control node is an abstract activity node that coordinates flows in an activity.
An initial node is a control node at which flow starts when the activity is invoked.
Input 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 input pin is a pin that holds input values to be consumed by an action.
Instance Specification (Instance Specification)
An instance specification is a model element that represents an instance in a modeled system.
An instance specification has the capability of being a deployment target in a deployment relationship, in the case that it is an instance of a node.
It is also has the capability of being a deployed artifact, if it is an instance of an artifact.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interaction Use (Interaction Use)
An interaction use refers to an interaction. The interaction use is a shorthand for copying the contents of the referenced interaction where the interaction use is. To be accurate the copying must take into account substituting parameters with arguments and connect the formal gates with the actual ones.
Interface (Interface)
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
Interface Realization (Interface Realization)
An interface realization is a specialized realization relationship between a classifier and an interface. This relationship signifies that the realizing classifier conforms to the contract specified by the interface.
Join (Pseudo State)
Join vertices serve to merge several transitions emanating from source vertices in different orthogonal regions. The transitions entering a join vertex cannot have guards or triggers.
Join Node (Control Node)
A control node is an abstract activity node that coordinates flows in an activity.
A join node is a control node that synchronizes multiple flows. Join nodes have a Boolean value specification using the names of the incoming edges to specify the conditions under which the join will emit a token.
Junction (Pseudo State)
Junction vertices are semantic-free vertices that are used to chain together multiple transitions. They are used to construct compound transition paths between states. For example, a junction can be used to converge multiple incoming transitions into a single outgoing transition representing a shared transition path (this is known as an merge). Conversely, they can be used to split an incoming transition into multiple outgoing transition segments with different guard conditions. This realizes a static conditional branch. (In the latter case, outgoing transitions whose guard conditions evaluate to false are disabled. A predefined guard denoted 'else' may be defined for at most one outgoing transition. This transition is enabled if all the guards labeling the other transitions are false.) Static conditional branches are distinct from dynamic conditional branches that are realized by choice vertices.
Lifeline (Lifeline)
A lifeline represents an individual participant in the interaction. While parts and structural features may have multiplicity greater than 1, lifelines represent only one interacting entity.
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.
Manifestation (Manifestation)
A manifestation is the concrete physical rendering of one or more model elements by an artifact.
Merge Node (Control Node)
A control node is an abstract activity node that coordinates flows in an activity.
A merge node is a control node that brings together multiple alternate flows. It is not used to synchronize concurrent flows but to accept one among several alternate flows.
Message (Message)
A message defines a particular communication between lifelines of an interaction.
Model (Model)
A model captures a view of a physical system. It is an abstraction of the physical system, with a certain purpose.
This purpose determines what is to be included in the model and what is irrelevant. Thus the model completely describes those aspects of the physical system that are relevant to the purpose of the model, at the appropriate level of detail.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Object Flow (Object Flow)
An object flow is an activity edge that can have objects or data passing along it. Object flows have support for multicast/receive, token selection from object nodes, and transformation of tokens.
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.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Operation (Operation)
An operation is a behavioral feature of a classifier that specifies the name, type, parameters, and constraints for invoking an associated behavior. An operation may invoke both the execution of method behaviors as well as other behavioral responses.
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.
Package (Package)
A package is used to group elements, and provides a namespace for the grouped elements.
A package can have one or more profile applications to indicate which profiles have been applied.
Parameter (Parameter)
A parameter is a specification of an argument used to pass information into or out of an invocation of a behavioral feature. Parameters are allowed to be treated as connectable elements. Parameters have support for streaming, exceptions, and parameter sets.
Port (Port)
A port is a property of a classifier that specifies a distinct interaction point between that classifier and its environment or between the (behavior of the) classifier and its internal parts.
Ports are connected to properties of the classifier by connectors through which requests can be made to invoke the behavioral features of a classifier.
A Port may specify the services a classifier provides (offers) to its environment as well as the services that a classifier expects (requires) of its environment. A port has an associated protocol state machine.
Primitive Type (Primitive Type)
A primitive type defines a predefined data type, without any relevant substructure (i.e., it has no parts in the context of UML). A primitive datatype may have an algebra and operations defined outside of UML, for example, mathematically.
Profile (Profile)
A profile defines limited extensions to a reference metamodel with the purpose of adapting the metamodel to a specific platform or domain.
Protocol (Protocol)
Only available together with the Real-Time Extension of RSA.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
Protocol Transition (Protocol Transition)
A protocol transition 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.
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.
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.
Reception (Reception)
A reception is a declaration stating that a classifier is prepared to react to the receipt of a signal. A reception designates a signal and specifies the expected behavioral response.
The details of handling a signal are specified by the behavior associated with the reception or the classifier itself.
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.
Region (Region)
A region is an orthogonal part of either a composite state or a state machine. It contains states and transitions.
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.
Shallow History (Pseudo State)
ShallowHistory represents the most recent active substate of its containing state (but not the substates of that substate). A composite state can have at most one shallow history vertex. A transition coming into the shallow history vertex is equivalent to a transition coming into the most recent active substate of a state. At most one transition may originate from the history connector to the default shallow history state. This transition is taken in case the composite state had never been active before. Entry actions of states entered on the path to the state represented by a shallow history are performed.
Signal (Signal)
A signal is a specification of send request instances communicated between objects. The receiving object handles the received request instances as specified by its receptions. The data carried by a send request (which was passed to it by the send invocation occurrence that caused that request) are represented as attributes of the signal.
A signal is defined independently of the classifiers handling the signal occurrence.
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
State (State)
A state models a situation during which some (usually implicit) invariant condition holds.
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.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
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.
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.
Terminate (Pseudo State)
Entering a terminate pseudostate implies that the execution of this state machine by means of its context object is terminated. The state machine does not exit any states nor does it perform any exit actions other than those associated with the transition leading to the terminate pseudostate. Entering a terminate pseudostate is equivalent to invoking a DestroyObjectAction.
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.
Transition (Transition)
A transition is a directed relationship between a source vertex and a target vertex.
It may be part of a compound transition, which takes the state machine from one state configuration to another, representing the complete response of the state machine to an occurrence of an event of a particular type.
Trigger (Trigger)
A trigger relates an event to a behavior that may affect an instance of the classifier. A trigger specification may be qualified by the port on which the event occurred.
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.
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.
Use Case (Use Case)
A use case is the specification of a set of actions performed by a system, which yields an observable result that is, typically, of value for one or more actors or other stakeholders of the system.
Value 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 input pin is a pin that holds input values to be consumed by an action.
A value pin is an input pin that provides a value by evaluating a value specification.
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.
An item of one of the following item kinds:
Abstraction (Abstraction)Accept Call Action (Action)Accept Event Action (Action)Action Input Pin (Pin)Activity (Activity)Activity Final Node (Control Node)Activity Parameter Node (Object Node)Activity Partition (Activity Partition)Actor (Actor)Add Structural Feature Value Action (Action)Add Variable Value Action (Action)Artifact (Artifact)Association (Association)Association End (Association End)Attribute (Attribute)Broadcast Signal Action (Action)Call Behavior Action (Action)Call Event (Call Event)Call Operation Action (Action)Central Buffer (Object Node)Choice (Pseudo State)Class (Class)Clear Association Action (Action)Clear Structural Feature Action (Action)Clear Variable Action (Action)Collaboration (Collaboration)Collaboration Use (Collaboration Use)Combined Fragment (Combined Fragment)Communication Path (Communication Path)Component (Component)Component Realization (Component Realization)Conditional Node (Action)Connection Point Reference (Connection Point Reference)Connector (Connector)Control Flow (Control Flow)Create Link Action (Action)Create Link Object Action (Action)Create Object Action (Action)Data Store Node (Object Node)Data Type (Data Type)Decision Node (Control Node)Deep History (Pseudo State)Dependency (Dependency)Deployment (Deployment)Deployment Specification (Deployment Specification)Destroy Link Action (Action)Destroy Object Action (Action)Device (Device)Entry Point (Pseudo State)Enumeration (Enumeration)Enumeration Literal (Enumeration Literal)Execution Environment (Execution Environment)Exit Point (Pseudo State)Expansion Node (Object Node)Expansion Region (Action)Extend (Extend)Extension (Extension)Extension Point (Extension Point)Final State (Final State)Flow Final Node (Control Node)Fork (Pseudo State)Fork Node (Control Node)Gate (Gate)Guard (Guard)Include (Include)Information Flow (Information Flow)Information Item (Information Item)Initial (Pseudo State)Initial Node (Control Node)Input Pin (Pin)Instance Specification (Instance Specification)Interaction (Interaction)Interaction Use (Interaction Use)Interface (Interface)Interface Realization (Interface Realization)Join (Pseudo State)Join Node (Control Node)Junction (Pseudo State)Lifeline (Lifeline)Loop Node (Action)Manifestation (Manifestation)Merge Node (Control Node)Message (Message)Model (Model)Node (Node)Object Flow (Object Flow)Opaque Action (Action)Opaque Behavior (Opaque Behavior)Operation (Operation)Output Pin (Pin)Package (Package)Parameter (Parameter)Port (Port)Primitive Type (Primitive Type)Profile (Profile)Protocol (Protocol)Protocol State Machine (Protocol State Machine)Protocol Transition (Protocol Transition)Raise Exception Action (Action)Read Extent Action (Action)Read Is Classified Object Action (Action)Read Link Action (Action)Read Link Object End Action (Action)Read Link Object End Qualifier Action (Action)Read Self Action (Action)Read Structural Feature Action (Action)Read Variable Action (Action)Realization (Realization)Reception (Reception)Reclassify Object Action (Action)Reduce Action (Action)Region (Region)Remove Structural Feature Value Action (Action)Remove Variable Value Action (Action)Reply Action (Action)Send Object Action (Action)Send Signal Action (Action)Sequence Node (Action)Shallow History (Pseudo State)Signal (Signal)Start Classifier Behavior Action (Action)Start Object Behavior Action (Action)State (State)State Machine (State Machine)Stereotype (Stereotype)Structured Activity Node (Action)Structured Activity Node (Structured Activity Node)Substitution (Substitution)Terminate (Pseudo State)Test Identity Action (Action)Transition (Transition)Trigger (Trigger)Unmarshall Action (Action)Usage (Usage)Use Case (Use Case)Value Pin (Pin)Value Specification Action (Action)Abstraction (Abstraction)Dependency (Dependency)Information Flow (Information Flow)Realization (Realization)Substitution (Substitution)Usage (Usage) Template SignatureA template signature bundles the set of formal template parameters for a templated element.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Actor (Actor)
An actor specifies a role played by a user or any other system that interacts with the subject.
Artifact (Artifact)
An artifact is the specification of a physical piece of information that is used or produced by a software development process, or by deployment and operation of a system.
Examples of artifacts include model files, source files, scripts, and binary executable files, a table in a database system, a development deliverable, or a word-processing document, a mail message. An artifact is the source of a deployment to a node.
Association (Association)
An association describes a set of tuples whose values refer to typed instances. An instance of an association is called a link.
Association End (Association End)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An association End is a property that has a reference to an association.
Attribute (Attribute)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An attribute is a property that has no reference to an association.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
Collaboration (Collaboration)
A collaboration defines a set of co-operating roles used collectively to illustrate a specific functionality.
A collaboration should only show the roles and attributes required to accomplish its defined task or function. Isolating the primary roles is an exercise in simplifying the structure and clarifying the behavior, and also provides for re-use. A collaboration often implements a pattern.
Communication Path (Communication Path)
A communication path is an association between two deployment targets, through which they are able to exchange signals and messages.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Data Type (Data Type)
A data type is a type whose instances are identified only by their value. A data type may contain attributes to support the modeling of structured data types.
Deployment Specification (Deployment Specification)
A deployment specification specifies a set of properties that determine execution parameters of a component artifact that is deployed on a node.
A deployment specification can be aimed at a specific type of container. An artifact that reifies or implements deployment specification properties is a deployment descriptor.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Enumeration (Enumeration)
An enumeration is a data type whose values are enumerated in the model as enumeration literals.
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Extension (Extension)
An extension is used to indicate that the properties of a metaclass are extended through a stereotype, and gives the ability to flexibly add (and later remove) stereotypes to classes.
Information Item (Information Item)
An information item is an abstraction of all kinds of information that can be exchanged between objects. It is a kind of
classifier intended for representing information in a very abstract way, one which cannot be instantiated.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interface (Interface)
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
Model (Model)
A model captures a view of a physical system. It is an abstraction of the physical system, with a certain purpose.
This purpose determines what is to be included in the model and what is irrelevant. Thus the model completely describes those aspects of the physical system that are relevant to the purpose of the model, at the appropriate level of detail.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Operation (Operation)
An operation is a behavioral feature of a classifier that specifies the name, type, parameters, and constraints for invoking an associated behavior. An operation may invoke both the execution of method behaviors as well as other behavioral responses.
Package (Package)
A package is used to group elements, and provides a namespace for the grouped elements.
A package can have one or more profile applications to indicate which profiles have been applied.
Port (Port)
A port is a property of a classifier that specifies a distinct interaction point between that classifier and its environment or between the (behavior of the) classifier and its internal parts.
Ports are connected to properties of the classifier by connectors through which requests can be made to invoke the behavioral features of a classifier.
A Port may specify the services a classifier provides (offers) to its environment as well as the services that a classifier expects (requires) of its environment. A port has an associated protocol state machine.
Primitive Type (Primitive Type)
A primitive type defines a predefined data type, without any relevant substructure (i.e., it has no parts in the context of UML). A primitive datatype may have an algebra and operations defined outside of UML, for example, mathematically.
Profile (Profile)
A profile defines limited extensions to a reference metamodel with the purpose of adapting the metamodel to a specific platform or domain.
Protocol (Protocol)
Only available together with the Real-Time Extension of RSA.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
Signal (Signal)
A signal is a specification of send request instances communicated between objects. The receiving object handles the received request instances as specified by its receptions. The data carried by a send request (which was passed to it by the send invocation occurrence that caused that request) are represented as attributes of the signal.
A signal is defined independently of the classifiers handling the signal occurrence.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
Use Case (Use Case)
A use case is the specification of a set of actions performed by a system, which yields an observable result that is, typically, of value for one or more actors or other stakeholders of the system.
Template Parameter (Template Parameter)
A template parameter exposes a parameterable element as a formal template parameter of a template.
Templatebinding (Templatebinding) Deployment SpecificationA deployment specification specifies a set of properties that determine execution parameters of a component artifact that is deployed on a node.
A deployment specification can be aimed at a specific type of container. An artifact that reifies or implements deployment specification properties is a deployment descriptor.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
If true, the Classifier does not provide a complete declaration and can typically not be instantiated.
An abstract classifier is intended to be used by other classifiers e.g. as the target of general metarelationships or generalization relationships.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Artifact (Artifact)
An artifact is the specification of a physical piece of information that is used or produced by a software development process, or by deployment and operation of a system.
Examples of artifacts include model files, source files, scripts, and binary executable files, a table in a database system, a development deliverable, or a word-processing document, a mail message. An artifact is the source of a deployment to a node.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Deployment (Deployment)
A deployment is the allocation of an artifact or artifact instance to a deployment target. A component deployment is the deployment of one or more artifacts or artifact instances to a deployment target, optionally parameterized by a deployment specification. Examples are executables and configuration files.
Deployment Specification (Deployment Specification)
A deployment specification specifies a set of properties that determine execution parameters of a component artifact that is deployed on a node.
A deployment specification can be aimed at a specific type of container. An artifact that reifies or implements deployment specification properties is a deployment descriptor.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interface (Interface)
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
Model (Model)
A model captures a view of a physical system. It is an abstraction of the physical system, with a certain purpose.
This purpose determines what is to be included in the model and what is irrelevant. Thus the model completely describes those aspects of the physical system that are relevant to the purpose of the model, at the appropriate level of detail.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Package (Package)
A package is used to group elements, and provides a namespace for the grouped elements.
A package can have one or more profile applications to indicate which profiles have been applied.
Profile (Profile)
A profile defines limited extensions to a reference metamodel with the purpose of adapting the metamodel to a specific platform or domain.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
Template Parameter (Template Parameter)
A template parameter exposes a parameterable element as a formal template parameter of a template.
Artifact (Artifact)
An artifact is the specification of a physical piece of information that is used or produced by a software development process, or by deployment and operation of a system.
Examples of artifacts include model files, source files, scripts, and binary executable files, a table in a database system, a development deliverable, or a word-processing document, a mail message. An artifact is the source of a deployment to a node.
Association End (Association End)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An association End is a property that has a reference to an association.
Attribute (Attribute)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An attribute is a property that has no reference to an association.
Collaboration Use (Collaboration Use)
A collaboration use represents one particular use of a collaboration to explain the relationships between the properties of a classifier.
A collaboration use shows how the pattern described by a collaboration is applied in a given context, by binding specific entities from that context to the roles of the collaboration. Depending on the context, these entities could be structural features of a classifier, instance specifications, or even roles in some containing collaboration. There may be multiple occurrences of a given collaboration within a classifier, each involving a different set of roles and connectors.
A given role or connector may be involved in multiple occurrences of the same or different collaborations. Associated dependencies map features of the collaboration type to features in the classifier. These dependencies indicate which role in the classifier plays which role in the collaboration.
Constraint (Constraint)
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.
Deployment Specification (Deployment Specification)
A deployment specification specifies a set of properties that determine execution parameters of a component artifact that is deployed on a node.
A deployment specification can be aimed at a specific type of container. An artifact that reifies or implements deployment specification properties is a deployment descriptor.
Operation (Operation)
An operation is a behavioral feature of a classifier that specifies the name, type, parameters, and constraints for invoking an associated behavior. An operation may invoke both the execution of method behaviors as well as other behavioral responses.
Port (Port)
A port is a property of a classifier that specifies a distinct interaction point between that classifier and its environment or between the (behavior of the) classifier and its internal parts.
Ports are connected to properties of the classifier by connectors through which requests can be made to invoke the behavioral features of a classifier.
A Port may specify the services a classifier provides (offers) to its environment as well as the services that a classifier expects (requires) of its environment. A port has an associated protocol state machine.
Template Signature (Template Signature)
A template signature bundles the set of formal template parameters for a templated element.
Use Case (Use Case)
A use case is the specification of a set of actions performed by a system, which yields an observable result that is, typically, of value for one or more actors or other stakeholders of the system.
Class Diagram (Class Diagram)
A Class Diagram is a diagram that shows classes and interfaces and their relationships. However a class diagram may also show packages and all kind of classifier elements.
Component Diagram (Component Diagram)
A Component Diagram is a diagram that shows components, interfaces and artifacts and their relationships. However a component diagram may also show packages and all kind of classifier elements.
Deployment Diagram (Deployment Diagram)
A Deployment Diagram is a diagram that shows nodes and artifacts and their relationships. However a deployment diagram may also show packages and all kind of classifier elements.
Freeform Diagram (Freeform Diagram)
A Free Form diagram is a diagram in which you can make free drawings without the restriction of using UML.
Interaction Overview Diagram (Interaction Overview Diagram)
An Interaction Overview Diagram is a visual representation of a control flow of interaction..
Object Diagram (Object Diagram)
An Object Diagram is a diagram that shows instance specification, links and slots.
Use Case Diagram (Use Case Diagram)
A Use-Case Diagram is a diagram that shows actors and use cases and their relationships. However a Use-Case Diagram may also show packages and all kind of classifier elements.
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.
Component Realization (Component Realization)
The realization concept is specialized to (optionally) define the classifiers that realize the contract offered by a component in terms of its provided and required interfaces.
The component forms an abstraction from these various
classifiers.
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).
Element Import (Element Import)
An element import identifies an element in another package, and allows the element to be referenced using its name without a qualifier.
Generalization (Generalization)
A generalization is a taxonomic relationship between a more general classifier and a more specific classifier. Each instance of the specific classifier is also an indirect instance of the general classifier. Thus, the specific classifier inherits the features of the more general classifier.
A generalization relates a specific classifier to a more general classifier, and is owned by the specific classifier.
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.
Manifestation (Manifestation)
A manifestation is the concrete physical rendering of one or more model elements by an artifact.
Package Import (Package Import)
A package import is a relationship that allows the use of unqualified names to refer to package members from other namespaces.
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.
Templatebinding (Templatebinding)
A template binding represents a relationship between a templateable element and a template. A template binding specifies the substitutions of actual parameters for the formal parameters of the template.
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.
Action Input Pin (Pin)Activity Parameter Node (Object Node)Association End (Association End)Attribute (Attribute)Central Buffer (Object Node)Data Store Node (Object Node)Expansion Node (Object Node)Input Pin (Pin)Output Pin (Pin)Parameter (Parameter)Port (Port)Value Pin (Pin)Abstraction (Abstraction)Component Realization (Component Realization)Dependency (Dependency)Deployment (Deployment)Element Import (Element Import)Generalization (Generalization)Information Flow (Information Flow)Manifestation (Manifestation)Realization (Realization)Substitution (Substitution)Usage (Usage) Execution EnvironmentAn execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
If true, the Classifier does not provide a complete declaration and can typically not be instantiated.
An abstract classifier is intended to be used by other classifiers e.g. as the target of general metarelationships or generalization relationships.
Determines whether an object specified by this classifier is active or not. If true, then the owning classifier is referred to as an active classifier. If false, then such a classifier is referred to as a passive classifier.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Association (Association)
An association describes a set of tuples whose values refer to typed instances. An instance of an association is called a link.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
Communication Path (Communication Path)
A communication path is an association between two deployment targets, through which they are able to exchange signals and messages.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Extension (Extension)
An extension is used to indicate that the properties of a metaclass are extended through a stereotype, and gives the ability to flexibly add (and later remove) stereotypes to classes.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interface (Interface)
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
Model (Model)
A model captures a view of a physical system. It is an abstraction of the physical system, with a certain purpose.
This purpose determines what is to be included in the model and what is irrelevant. Thus the model completely describes those aspects of the physical system that are relevant to the purpose of the model, at the appropriate level of detail.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Package (Package)
A package is used to group elements, and provides a namespace for the grouped elements.
A package can have one or more profile applications to indicate which profiles have been applied.
Profile (Profile)
A profile defines limited extensions to a reference metamodel with the purpose of adapting the metamodel to a specific platform or domain.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
Template Parameter (Template Parameter)
A template parameter exposes a parameterable element as a formal template parameter of a template.
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Actor (Actor)
An actor specifies a role played by a user or any other system that interacts with the subject.
Artifact (Artifact)
An artifact is the specification of a physical piece of information that is used or produced by a software development process, or by deployment and operation of a system.
Examples of artifacts include model files, source files, scripts, and binary executable files, a table in a database system, a development deliverable, or a word-processing document, a mail message. An artifact is the source of a deployment to a node.
Association (Association)
An association describes a set of tuples whose values refer to typed instances. An instance of an association is called a link.
Association End (Association End)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An association End is a property that has a reference to an association.
Attribute (Attribute)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An attribute is a property that has no reference to an association.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
Collaboration (Collaboration)
A collaboration defines a set of co-operating roles used collectively to illustrate a specific functionality.
A collaboration should only show the roles and attributes required to accomplish its defined task or function. Isolating the primary roles is an exercise in simplifying the structure and clarifying the behavior, and also provides for re-use. A collaboration often implements a pattern.
Collaboration Use (Collaboration Use)
A collaboration use represents one particular use of a collaboration to explain the relationships between the properties of a classifier.
A collaboration use shows how the pattern described by a collaboration is applied in a given context, by binding specific entities from that context to the roles of the collaboration. Depending on the context, these entities could be structural features of a classifier, instance specifications, or even roles in some containing collaboration. There may be multiple occurrences of a given collaboration within a classifier, each involving a different set of roles and connectors.
A given role or connector may be involved in multiple occurrences of the same or different collaborations. Associated dependencies map features of the collaboration type to features in the classifier. These dependencies indicate which role in the classifier plays which role in the collaboration.
Communication Path (Communication Path)
A communication path is an association between two deployment targets, through which they are able to exchange signals and messages.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Connector (Connector)
Specifies a link that enables communication between two or more instances. This link may be an instance of anassociation, or it may represent the possibility of the instances being able to communicate because their identitiesare known by virtue of being passed in as parameters, held in variables or slots, or because the communicatinginstances are the same instance.
The link may be realized by something as simple as a pointer or by something ascomplex as a network connection. In contrast to associations, which specify links between any instance of theassociated classifiers, connectors specify links between instances playing the connected parts only.
Constraint (Constraint)
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.
Data Type (Data Type)
A data type is a type whose instances are identified only by their value. A data type may contain attributes to support the modeling of structured data types.
Deployment Specification (Deployment Specification)
A deployment specification specifies a set of properties that determine execution parameters of a component artifact that is deployed on a node.
A deployment specification can be aimed at a specific type of container. An artifact that reifies or implements deployment specification properties is a deployment descriptor.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Enumeration (Enumeration)
An enumeration is a data type whose values are enumerated in the model as enumeration literals.
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Extension (Extension)
An extension is used to indicate that the properties of a metaclass are extended through a stereotype, and gives the ability to flexibly add (and later remove) stereotypes to classes.
Information Item (Information Item)
An information item is an abstraction of all kinds of information that can be exchanged between objects. It is a kind of
classifier intended for representing information in a very abstract way, one which cannot be instantiated.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interface (Interface)
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Operation (Operation)
An operation is a behavioral feature of a classifier that specifies the name, type, parameters, and constraints for invoking an associated behavior. An operation may invoke both the execution of method behaviors as well as other behavioral responses.
Port (Port)
A port is a property of a classifier that specifies a distinct interaction point between that classifier and its environment or between the (behavior of the) classifier and its internal parts.
Ports are connected to properties of the classifier by connectors through which requests can be made to invoke the behavioral features of a classifier.
A Port may specify the services a classifier provides (offers) to its environment as well as the services that a classifier expects (requires) of its environment. A port has an associated protocol state machine.
Primitive Type (Primitive Type)
A primitive type defines a predefined data type, without any relevant substructure (i.e., it has no parts in the context of UML). A primitive datatype may have an algebra and operations defined outside of UML, for example, mathematically.
Protocol (Protocol)
Only available together with the Real-Time Extension of RSA.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
Reception (Reception)
A reception is a declaration stating that a classifier is prepared to react to the receipt of a signal. A reception designates a signal and specifies the expected behavioral response.
The details of handling a signal are specified by the behavior associated with the reception or the classifier itself.
Signal (Signal)
A signal is a specification of send request instances communicated between objects. The receiving object handles the received request instances as specified by its receptions. The data carried by a send request (which was passed to it by the send invocation occurrence that caused that request) are represented as attributes of the signal.
A signal is defined independently of the classifiers handling the signal occurrence.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
Template Signature (Template Signature)
A template signature bundles the set of formal template parameters for a templated element.
Trigger (Trigger)
A trigger relates an event to a behavior that may affect an instance of the classifier. A trigger specification may be qualified by the port on which the event occurred.
Use Case (Use Case)
A use case is the specification of a set of actions performed by a system, which yields an observable result that is, typically, of value for one or more actors or other stakeholders of the system.
Class Diagram (Class Diagram)
A Class Diagram is a diagram that shows classes and interfaces and their relationships. However a class diagram may also show packages and all kind of classifier elements.
Component Diagram (Component Diagram)
A Component Diagram is a diagram that shows components, interfaces and artifacts and their relationships. However a component diagram may also show packages and all kind of classifier elements.
Deployment Diagram (Deployment Diagram)
A Deployment Diagram is a diagram that shows nodes and artifacts and their relationships. However a deployment diagram may also show packages and all kind of classifier elements.
Freeform Diagram (Freeform Diagram)
A Free Form diagram is a diagram in which you can make free drawings without the restriction of using UML.
Interaction Overview Diagram (Interaction Overview Diagram)
An Interaction Overview Diagram is a visual representation of a control flow of interaction..
Object Diagram (Object Diagram)
An Object Diagram is a diagram that shows instance specification, links and slots.
Structure Diagram (Structure Diagram)
A Structure Diagram is a diagram that shows the static structure of an element.
Use Case Diagram (Use Case Diagram)
A Use-Case Diagram is a diagram that shows actors and use cases and their relationships. However a Use-Case Diagram may also show packages and all kind of classifier elements.
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.
Component Realization (Component Realization)
The realization concept is specialized to (optionally) define the classifiers that realize the contract offered by a component in terms of its provided and required interfaces.
The component forms an abstraction from these various
classifiers.
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).
Deployment (Deployment)
A deployment is the allocation of an artifact or artifact instance to a deployment target. A component deployment is the deployment of one or more artifacts or artifact instances to a deployment target, optionally parameterized by a deployment specification. Examples are executables and configuration files.
Element Import (Element Import)
An element import identifies an element in another package, and allows the element to be referenced using its name without a qualifier.
Generalization (Generalization)
A generalization is a taxonomic relationship between a more general classifier and a more specific classifier. Each instance of the specific classifier is also an indirect instance of the general classifier. Thus, the specific classifier inherits the features of the more general classifier.
A generalization relates a specific classifier to a more general classifier, and is owned by the specific classifier.
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.
Interface Realization (Interface Realization)
An interface realization is a specialized realization relationship between a classifier and an interface. This relationship signifies that the realizing classifier conforms to the contract specified by the interface.
Package Import (Package Import)
A package import is a relationship that allows the use of unqualified names to refer to package members from other namespaces.
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.
Templatebinding (Templatebinding)
A template binding represents a relationship between a templateable element and a template. A template binding specifies the substitutions of actual parameters for the formal parameters of the template.
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.
Action Input Pin (Pin)Activity Parameter Node (Object Node)Association End (Association End)Attribute (Attribute)Central Buffer (Object Node)Data Store Node (Object Node)Expansion Node (Object Node)Input Pin (Pin)Output Pin (Pin)Parameter (Parameter)Port (Port)Value Pin (Pin)Abstraction (Abstraction)Component Realization (Component Realization)Dependency (Dependency)Deployment (Deployment)Element Import (Element Import)Generalization (Generalization)Information Flow (Information Flow)Manifestation (Manifestation)Realization (Realization)Substitution (Substitution)Usage (Usage) NodeA node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
If true, the Classifier does not provide a complete declaration and can typically not be instantiated.
An abstract classifier is intended to be used by other classifiers e.g. as the target of general metarelationships or generalization relationships.
Determines whether an object specified by this classifier is active or not. If true, then the owning classifier is referred to as an active classifier. If false, then such a classifier is referred to as a passive classifier.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Association (Association)
An association describes a set of tuples whose values refer to typed instances. An instance of an association is called a link.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
Communication Path (Communication Path)
A communication path is an association between two deployment targets, through which they are able to exchange signals and messages.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Extension (Extension)
An extension is used to indicate that the properties of a metaclass are extended through a stereotype, and gives the ability to flexibly add (and later remove) stereotypes to classes.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interface (Interface)
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
Model (Model)
A model captures a view of a physical system. It is an abstraction of the physical system, with a certain purpose.
This purpose determines what is to be included in the model and what is irrelevant. Thus the model completely describes those aspects of the physical system that are relevant to the purpose of the model, at the appropriate level of detail.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Package (Package)
A package is used to group elements, and provides a namespace for the grouped elements.
A package can have one or more profile applications to indicate which profiles have been applied.
Profile (Profile)
A profile defines limited extensions to a reference metamodel with the purpose of adapting the metamodel to a specific platform or domain.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
Template Parameter (Template Parameter)
A template parameter exposes a parameterable element as a formal template parameter of a template.
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Actor (Actor)
An actor specifies a role played by a user or any other system that interacts with the subject.
Artifact (Artifact)
An artifact is the specification of a physical piece of information that is used or produced by a software development process, or by deployment and operation of a system.
Examples of artifacts include model files, source files, scripts, and binary executable files, a table in a database system, a development deliverable, or a word-processing document, a mail message. An artifact is the source of a deployment to a node.
Association (Association)
An association describes a set of tuples whose values refer to typed instances. An instance of an association is called a link.
Association End (Association End)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An association End is a property that has a reference to an association.
Attribute (Attribute)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An attribute is a property that has no reference to an association.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
Collaboration (Collaboration)
A collaboration defines a set of co-operating roles used collectively to illustrate a specific functionality.
A collaboration should only show the roles and attributes required to accomplish its defined task or function. Isolating the primary roles is an exercise in simplifying the structure and clarifying the behavior, and also provides for re-use. A collaboration often implements a pattern.
Collaboration Use (Collaboration Use)
A collaboration use represents one particular use of a collaboration to explain the relationships between the properties of a classifier.
A collaboration use shows how the pattern described by a collaboration is applied in a given context, by binding specific entities from that context to the roles of the collaboration. Depending on the context, these entities could be structural features of a classifier, instance specifications, or even roles in some containing collaboration. There may be multiple occurrences of a given collaboration within a classifier, each involving a different set of roles and connectors.
A given role or connector may be involved in multiple occurrences of the same or different collaborations. Associated dependencies map features of the collaboration type to features in the classifier. These dependencies indicate which role in the classifier plays which role in the collaboration.
Communication Path (Communication Path)
A communication path is an association between two deployment targets, through which they are able to exchange signals and messages.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Connector (Connector)
Specifies a link that enables communication between two or more instances. This link may be an instance of anassociation, or it may represent the possibility of the instances being able to communicate because their identitiesare known by virtue of being passed in as parameters, held in variables or slots, or because the communicatinginstances are the same instance.
The link may be realized by something as simple as a pointer or by something ascomplex as a network connection. In contrast to associations, which specify links between any instance of theassociated classifiers, connectors specify links between instances playing the connected parts only.
Constraint (Constraint)
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.
Data Type (Data Type)
A data type is a type whose instances are identified only by their value. A data type may contain attributes to support the modeling of structured data types.
Deployment Specification (Deployment Specification)
A deployment specification specifies a set of properties that determine execution parameters of a component artifact that is deployed on a node.
A deployment specification can be aimed at a specific type of container. An artifact that reifies or implements deployment specification properties is a deployment descriptor.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Enumeration (Enumeration)
An enumeration is a data type whose values are enumerated in the model as enumeration literals.
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Extension (Extension)
An extension is used to indicate that the properties of a metaclass are extended through a stereotype, and gives the ability to flexibly add (and later remove) stereotypes to classes.
Information Item (Information Item)
An information item is an abstraction of all kinds of information that can be exchanged between objects. It is a kind of
classifier intended for representing information in a very abstract way, one which cannot be instantiated.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interface (Interface)
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Operation (Operation)
An operation is a behavioral feature of a classifier that specifies the name, type, parameters, and constraints for invoking an associated behavior. An operation may invoke both the execution of method behaviors as well as other behavioral responses.
Port (Port)
A port is a property of a classifier that specifies a distinct interaction point between that classifier and its environment or between the (behavior of the) classifier and its internal parts.
Ports are connected to properties of the classifier by connectors through which requests can be made to invoke the behavioral features of a classifier.
A Port may specify the services a classifier provides (offers) to its environment as well as the services that a classifier expects (requires) of its environment. A port has an associated protocol state machine.
Primitive Type (Primitive Type)
A primitive type defines a predefined data type, without any relevant substructure (i.e., it has no parts in the context of UML). A primitive datatype may have an algebra and operations defined outside of UML, for example, mathematically.
Protocol (Protocol)
Only available together with the Real-Time Extension of RSA.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
Reception (Reception)
A reception is a declaration stating that a classifier is prepared to react to the receipt of a signal. A reception designates a signal and specifies the expected behavioral response.
The details of handling a signal are specified by the behavior associated with the reception or the classifier itself.
Signal (Signal)
A signal is a specification of send request instances communicated between objects. The receiving object handles the received request instances as specified by its receptions. The data carried by a send request (which was passed to it by the send invocation occurrence that caused that request) are represented as attributes of the signal.
A signal is defined independently of the classifiers handling the signal occurrence.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
Template Signature (Template Signature)
A template signature bundles the set of formal template parameters for a templated element.
Trigger (Trigger)
A trigger relates an event to a behavior that may affect an instance of the classifier. A trigger specification may be qualified by the port on which the event occurred.
Use Case (Use Case)
A use case is the specification of a set of actions performed by a system, which yields an observable result that is, typically, of value for one or more actors or other stakeholders of the system.
Class Diagram (Class Diagram)
A Class Diagram is a diagram that shows classes and interfaces and their relationships. However a class diagram may also show packages and all kind of classifier elements.
Component Diagram (Component Diagram)
A Component Diagram is a diagram that shows components, interfaces and artifacts and their relationships. However a component diagram may also show packages and all kind of classifier elements.
Deployment Diagram (Deployment Diagram)
A Deployment Diagram is a diagram that shows nodes and artifacts and their relationships. However a deployment diagram may also show packages and all kind of classifier elements.
Freeform Diagram (Freeform Diagram)
A Free Form diagram is a diagram in which you can make free drawings without the restriction of using UML.
Interaction Overview Diagram (Interaction Overview Diagram)
An Interaction Overview Diagram is a visual representation of a control flow of interaction..
Object Diagram (Object Diagram)
An Object Diagram is a diagram that shows instance specification, links and slots.
Structure Diagram (Structure Diagram)
A Structure Diagram is a diagram that shows the static structure of an element.
Use Case Diagram (Use Case Diagram)
A Use-Case Diagram is a diagram that shows actors and use cases and their relationships. However a Use-Case Diagram may also show packages and all kind of classifier elements.
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.
Component Realization (Component Realization)
The realization concept is specialized to (optionally) define the classifiers that realize the contract offered by a component in terms of its provided and required interfaces.
The component forms an abstraction from these various
classifiers.
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).
Deployment (Deployment)
A deployment is the allocation of an artifact or artifact instance to a deployment target. A component deployment is the deployment of one or more artifacts or artifact instances to a deployment target, optionally parameterized by a deployment specification. Examples are executables and configuration files.
Element Import (Element Import)
An element import identifies an element in another package, and allows the element to be referenced using its name without a qualifier.
Generalization (Generalization)
A generalization is a taxonomic relationship between a more general classifier and a more specific classifier. Each instance of the specific classifier is also an indirect instance of the general classifier. Thus, the specific classifier inherits the features of the more general classifier.
A generalization relates a specific classifier to a more general classifier, and is owned by the specific classifier.
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.
Interface Realization (Interface Realization)
An interface realization is a specialized realization relationship between a classifier and an interface. This relationship signifies that the realizing classifier conforms to the contract specified by the interface.
Package Import (Package Import)
A package import is a relationship that allows the use of unqualified names to refer to package members from other namespaces.
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.
Templatebinding (Templatebinding)
A template binding represents a relationship between a templateable element and a template. A template binding specifies the substitutions of actual parameters for the formal parameters of the template.
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.
Action Input Pin (Pin)Activity Parameter Node (Object Node)Association End (Association End)Attribute (Attribute)Central Buffer (Object Node)Data Store Node (Object Node)Expansion Node (Object Node)Input Pin (Pin)Output Pin (Pin)Parameter (Parameter)Port (Port)Value Pin (Pin)Abstraction (Abstraction)Component Realization (Component Realization)Dependency (Dependency)Deployment (Deployment)Element Import (Element Import)Generalization (Generalization)Information Flow (Information Flow)Manifestation (Manifestation)Realization (Realization)Substitution (Substitution)Usage (Usage) Communication PathA communication path is an association between two deployment targets, through which they are able to exchange signals and messages.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
If true, the Classifier does not provide a complete declaration and can typically not be instantiated.
An abstract classifier is intended to be used by other classifiers e.g. as the target of general metarelationships or generalization relationships.
Specifies whether the association is derived from other model elements such as other associations or constraints.
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.
Action Input Pin (Pin)Activity Parameter Node (Object Node)Association End (Association End)Attribute (Attribute)Central Buffer (Object Node)Data Store Node (Object Node)Expansion Node (Object Node)Input Pin (Pin)Output Pin (Pin)Parameter (Parameter)Port (Port)Value Pin (Pin)Association End (Association End)Abstraction (Abstraction)Component Realization (Component Realization)Dependency (Dependency)Element Import (Element Import)Generalization (Generalization)Information Flow (Information Flow)Manifestation (Manifestation)Realization (Realization)Substitution (Substitution)Usage (Usage)Connector (Connector) InteractionAn interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
Designates a behavioral feature that the behavior implements.
The behavioral feature must be owned by the classifier that owns the behavior or be inherited by it. The parameters of the behavioral feature and the implementing behavior must match.
If a behavior does not have a specification, it is directly associated with a classifier (i.e., it is the behavior of the classifier as a whole).
If true, the Classifier does not provide a complete declaration and can typically not be instantiated.
An abstract classifier is intended to be used by other classifiers e.g. as the target of general metarelationships or generalization relationships.
Determines whether an object specified by this classifier is active or not. If true, then the owning classifier is referred to as an active classifier. If false, then such a classifier is referred to as a passive classifier.
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.
Tells whether the behavior can be invoked while it is still executing from a previous invocation.
The classifier that is the context for the execution of the behavior.
If the behavior is owned by a BehavioredClassifier, that classifier is the context. Otherwise, the context is the first BehavioredClassifier reached by following the chain of owner relationships.
For example, following this algorithm, the context of an entry action in a state machine is the classifier that owns the state machine. The features of the context classifier as well as the elements visible to the context classifier are visible to the behavior
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Actor (Actor)
An actor specifies a role played by a user or any other system that interacts with the subject.
Association (Association)
An association describes a set of tuples whose values refer to typed instances. An instance of an association is called a link.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
Collaboration (Collaboration)
A collaboration defines a set of co-operating roles used collectively to illustrate a specific functionality.
A collaboration should only show the roles and attributes required to accomplish its defined task or function. Isolating the primary roles is an exercise in simplifying the structure and clarifying the behavior, and also provides for re-use. A collaboration often implements a pattern.
Communication Path (Communication Path)
A communication path is an association between two deployment targets, through which they are able to exchange signals and messages.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Extension (Extension)
An extension is used to indicate that the properties of a metaclass are extended through a stereotype, and gives the ability to flexibly add (and later remove) stereotypes to classes.
Final State (Final State)
A special kind of state signifying that the enclosing region is completed.
If the enclosing region is directly contained in a state machine and all other regions in the state machine also are completed, then it means that the entire state machine is completed.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interface (Interface)
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
Model (Model)
A model captures a view of a physical system. It is an abstraction of the physical system, with a certain purpose.
This purpose determines what is to be included in the model and what is irrelevant. Thus the model completely describes those aspects of the physical system that are relevant to the purpose of the model, at the appropriate level of detail.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Package (Package)
A package is used to group elements, and provides a namespace for the grouped elements.
A package can have one or more profile applications to indicate which profiles have been applied.
Profile (Profile)
A profile defines limited extensions to a reference metamodel with the purpose of adapting the metamodel to a specific platform or domain.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
Protocol Transition (Protocol Transition)
A protocol transition 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.
State (State)
A state models a situation during which some (usually implicit) invariant condition holds.
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.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
Template Parameter (Template Parameter)
A template parameter exposes a parameterable element as a formal template parameter of a template.
Transition (Transition)
A transition is a directed relationship between a source vertex and a target vertex.
It may be part of a compound transition, which takes the state machine from one state configuration to another, representing the complete response of the state machine to an occurrence of an event of a particular type.
Use Case (Use Case)
A use case is the specification of a set of actions performed by a system, which yields an observable result that is, typically, of value for one or more actors or other stakeholders of the system.
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Actor (Actor)
An actor specifies a role played by a user or any other system that interacts with the subject.
Artifact (Artifact)
An artifact is the specification of a physical piece of information that is used or produced by a software development process, or by deployment and operation of a system.
Examples of artifacts include model files, source files, scripts, and binary executable files, a table in a database system, a development deliverable, or a word-processing document, a mail message. An artifact is the source of a deployment to a node.
Association (Association)
An association describes a set of tuples whose values refer to typed instances. An instance of an association is called a link.
Association End (Association End)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An association End is a property that has a reference to an association.
Attribute (Attribute)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An attribute is a property that has no reference to an association.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
Collaboration (Collaboration)
A collaboration defines a set of co-operating roles used collectively to illustrate a specific functionality.
A collaboration should only show the roles and attributes required to accomplish its defined task or function. Isolating the primary roles is an exercise in simplifying the structure and clarifying the behavior, and also provides for re-use. A collaboration often implements a pattern.
Collaboration Use (Collaboration Use)
A collaboration use represents one particular use of a collaboration to explain the relationships between the properties of a classifier.
A collaboration use shows how the pattern described by a collaboration is applied in a given context, by binding specific entities from that context to the roles of the collaboration. Depending on the context, these entities could be structural features of a classifier, instance specifications, or even roles in some containing collaboration. There may be multiple occurrences of a given collaboration within a classifier, each involving a different set of roles and connectors.
A given role or connector may be involved in multiple occurrences of the same or different collaborations. Associated dependencies map features of the collaboration type to features in the classifier. These dependencies indicate which role in the classifier plays which role in the collaboration.
Combined Fragment (Combined Fragment)
A combined fragment defines an expression of interaction fragments. A combined fragment is defined by an interaction operator and corresponding interaction operands. Through the use of combined fragments the user will be able to describe a number of traces in a compact and concise manner.
Communication Path (Communication Path)
A communication path is an association between two deployment targets, through which they are able to exchange signals and messages.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Connector (Connector)
Specifies a link that enables communication between two or more instances. This link may be an instance of anassociation, or it may represent the possibility of the instances being able to communicate because their identitiesare known by virtue of being passed in as parameters, held in variables or slots, or because the communicatinginstances are the same instance.
The link may be realized by something as simple as a pointer or by something ascomplex as a network connection. In contrast to associations, which specify links between any instance of theassociated classifiers, connectors specify links between instances playing the connected parts only.
Constraint (Constraint)
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.
Data Type (Data Type)
A data type is a type whose instances are identified only by their value. A data type may contain attributes to support the modeling of structured data types.
Deployment Specification (Deployment Specification)
A deployment specification specifies a set of properties that determine execution parameters of a component artifact that is deployed on a node.
A deployment specification can be aimed at a specific type of container. An artifact that reifies or implements deployment specification properties is a deployment descriptor.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Enumeration (Enumeration)
An enumeration is a data type whose values are enumerated in the model as enumeration literals.
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Extension (Extension)
An extension is used to indicate that the properties of a metaclass are extended through a stereotype, and gives the ability to flexibly add (and later remove) stereotypes to classes.
Gate (Gate)
A gate is a connection point for relating a message outside an interaction fragment with a message inside the interaction fragment.
Information Item (Information Item)
An information item is an abstraction of all kinds of information that can be exchanged between objects. It is a kind of
classifier intended for representing information in a very abstract way, one which cannot be instantiated.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interaction Use (Interaction Use)
An interaction use refers to an interaction. The interaction use is a shorthand for copying the contents of the referenced interaction where the interaction use is. To be accurate the copying must take into account substituting parameters with arguments and connect the formal gates with the actual ones.
Interface (Interface)
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
Lifeline (Lifeline)
A lifeline represents an individual participant in the interaction. While parts and structural features may have multiplicity greater than 1, lifelines represent only one interacting entity.
Message (Message)
A message defines a particular communication between lifelines of an interaction.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Operation (Operation)
An operation is a behavioral feature of a classifier that specifies the name, type, parameters, and constraints for invoking an associated behavior. An operation may invoke both the execution of method behaviors as well as other behavioral responses.
Parameter (Parameter)
A parameter is a specification of an argument used to pass information into or out of an invocation of a behavioral feature. Parameters are allowed to be treated as connectable elements. Parameters have support for streaming, exceptions, and parameter sets.
Port (Port)
A port is a property of a classifier that specifies a distinct interaction point between that classifier and its environment or between the (behavior of the) classifier and its internal parts.
Ports are connected to properties of the classifier by connectors through which requests can be made to invoke the behavioral features of a classifier.
A Port may specify the services a classifier provides (offers) to its environment as well as the services that a classifier expects (requires) of its environment. A port has an associated protocol state machine.
Primitive Type (Primitive Type)
A primitive type defines a predefined data type, without any relevant substructure (i.e., it has no parts in the context of UML). A primitive datatype may have an algebra and operations defined outside of UML, for example, mathematically.
Protocol (Protocol)
Only available together with the Real-Time Extension of RSA.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
Reception (Reception)
A reception is a declaration stating that a classifier is prepared to react to the receipt of a signal. A reception designates a signal and specifies the expected behavioral response.
The details of handling a signal are specified by the behavior associated with the reception or the classifier itself.
Signal (Signal)
A signal is a specification of send request instances communicated between objects. The receiving object handles the received request instances as specified by its receptions. The data carried by a send request (which was passed to it by the send invocation occurrence that caused that request) are represented as attributes of the signal.
A signal is defined independently of the classifiers handling the signal occurrence.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
Template Signature (Template Signature)
A template signature bundles the set of formal template parameters for a templated element.
Trigger (Trigger)
A trigger relates an event to a behavior that may affect an instance of the classifier. A trigger specification may be qualified by the port on which the event occurred.
Use Case (Use Case)
A use case is the specification of a set of actions performed by a system, which yields an observable result that is, typically, of value for one or more actors or other stakeholders of the system.
Class Diagram (Class Diagram)
A Class Diagram is a diagram that shows classes and interfaces and their relationships. However a class diagram may also show packages and all kind of classifier elements.
Communication Diagram (Communication Diagram)
A Communication Diagram is a visual representation of an interaction between a set of objects.
Component Diagram (Component Diagram)
A Component Diagram is a diagram that shows components, interfaces and artifacts and their relationships. However a component diagram may also show packages and all kind of classifier elements.
Deployment Diagram (Deployment Diagram)
A Deployment Diagram is a diagram that shows nodes and artifacts and their relationships. However a deployment diagram may also show packages and all kind of classifier elements.
Freeform Diagram (Freeform Diagram)
A Free Form diagram is a diagram in which you can make free drawings without the restriction of using UML.
Interaction Overview Diagram (Interaction Overview Diagram)
An Interaction Overview Diagram is a visual representation of a control flow of interaction..
Object Diagram (Object Diagram)
An Object Diagram is a diagram that shows instance specification, links and slots.
Sequence Diagram (Sequence Diagram)
A Sequence Diagram is a visual representation of an interaction between a set of objects.
Structure Diagram (Structure Diagram)
A Structure Diagram is a diagram that shows the static structure of an element.
Timing Diagram (Timing Diagram)
A Timing Diagram is a visual representation of timing constraints between a set of objects.
Use Case Diagram (Use Case Diagram)
A Use-Case Diagram is a diagram that shows actors and use cases and their relationships. However a Use-Case Diagram may also show packages and all kind of classifier elements.
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.
Component Realization (Component Realization)
The realization concept is specialized to (optionally) define the classifiers that realize the contract offered by a component in terms of its provided and required interfaces.
The component forms an abstraction from these various
classifiers.
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).
Element Import (Element Import)
An element import identifies an element in another package, and allows the element to be referenced using its name without a qualifier.
Generalization (Generalization)
A generalization is a taxonomic relationship between a more general classifier and a more specific classifier. Each instance of the specific classifier is also an indirect instance of the general classifier. Thus, the specific classifier inherits the features of the more general classifier.
A generalization relates a specific classifier to a more general classifier, and is owned by the specific classifier.
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.
Interface Realization (Interface Realization)
An interface realization is a specialized realization relationship between a classifier and an interface. This relationship signifies that the realizing classifier conforms to the contract specified by the interface.
Package Import (Package Import)
A package import is a relationship that allows the use of unqualified names to refer to package members from other namespaces.
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.
Templatebinding (Templatebinding)
A template binding represents a relationship between a templateable element and a template. A template binding specifies the substitutions of actual parameters for the formal parameters of the template.
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.
Action Input Pin (Pin)Activity Parameter Node (Object Node)Association End (Association End)Attribute (Attribute)Central Buffer (Object Node)Data Store Node (Object Node)Expansion Node (Object Node)Input Pin (Pin)Output Pin (Pin)Parameter (Parameter)Port (Port)Value Pin (Pin)Call Behavior Action (Action)Abstraction (Abstraction)Component Realization (Component Realization)Dependency (Dependency)Element Import (Element Import)Generalization (Generalization)Information Flow (Information Flow)Manifestation (Manifestation)Realization (Realization)Substitution (Substitution)Usage (Usage)Action Input Pin (Pin)Activity Parameter Node (Object Node)Central Buffer (Object Node)Data Store Node (Object Node)Expansion Node (Object Node)Input Pin (Pin)Object Flow (Object Flow)Output Pin (Pin)Value Pin (Pin)Interaction Use (Interaction Use)Object Flow (Object Flow) Combined FragmentA combined fragment defines an expression of interaction fragments. A combined fragment is defined by an interaction operator and corresponding interaction operands. Through the use of combined fragments the user will be able to describe a number of traces in a compact and concise manner.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
Specifies the operation which defines the semantics of this combination of InteractionFragments.
alt - represents a choice of behavior. At most one of the
operands will be chosen.
assert - designates that the CombinedFragment represents an assertion.
break - represents a breaking scenario in the sense that
the operand is a scenario that is performed instead of the remainder of the enclosing InteractionFragment.
critical - represents a critical region.
ignore - designates that there are some message types that are not shown within this combined
fragment. These message types can be considered insignificant and are implicitly ignored if they appear in a
corresponding execution. Alternatively, one can understand ignore to mean that the message types that are ignored can
appear anywhere in the traces.
loop - represents a loop.
neg - represents traces that are defined to be invalid.
opt - represents a choice of behavior where either the
(sole) operand happens or nothing happens.
par - represents a parallel merge between the behaviors
of the operands.
seq - represents a weak sequencing between the
behaviors of the operands.
strict - represents a strict sequencing between the
behaviors of the operands.
neg - represents traces that are defined to be invalid.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Lifeline (Lifeline)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.
Abstraction (Abstraction)Dependency (Dependency)Information Flow (Information Flow)Realization (Realization)Substitution (Substitution)Usage (Usage) GateA gate is a connection point for relating a message outside an interaction fragment with a message inside the interaction fragment.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
Message.
References a Message.
An element of one of the following kinds:
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interaction Use (Interaction Use)
An interaction use refers to an interaction. The interaction use is a shorthand for copying the contents of the referenced interaction where the interaction use is. To be accurate the copying must take into account substituting parameters with arguments and connect the formal gates with the actual ones.
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.
Message (Message)Abstraction (Abstraction)Dependency (Dependency)Information Flow (Information Flow)Realization (Realization)Substitution (Substitution)Usage (Usage)Message (Message) Interaction UseAn interaction use refers to an interaction. The interaction use is a shorthand for copying the contents of the referenced interaction where the interaction use is. To be accurate the copying must take into account substituting parameters with arguments and connect the formal gates with the actual ones.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
Interaction.
Refers to the Interaction that defines its meaning
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Gate (Gate)
A gate is a connection point for relating a message outside an interaction fragment with a message inside the interaction fragment.
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.
Abstraction (Abstraction)Dependency (Dependency)Information Flow (Information Flow)Realization (Realization)Substitution (Substitution)Usage (Usage) LifelineA lifeline represents an individual participant in the interaction. While parts and structural features may have multiplicity greater than 1, lifelines represent only one interacting entity.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
References the ConnectableElement within the classifier that contains the enclosing interaction.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Message (Message)Message (Message)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.
Message (Message)Abstraction (Abstraction)Dependency (Dependency)Information Flow (Information Flow)Realization (Realization)Substitution (Substitution)Usage (Usage)Message (Message) MessageA message defines a particular communication between lifelines of an interaction.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
The derived kind of the Message (complete, lost, found or unknown).
The sort of communication reflected by the Message.
Gate or Lifeline.
References the Sending of the Message
Gate or Lifeline.
References the Receiving of the Message
The definition of the type or signature of the Message (depending on its kind).
The associated named element is derived from the message end that constitutes the sending or receiving message event.
If both a sending event and a receiving message event are present, the signature is obtained from the sending event.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
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.
Gate (Gate)Abstraction (Abstraction)Dependency (Dependency)Information Flow (Information Flow)Realization (Realization)Substitution (Substitution)Usage (Usage) ActivityAn activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
Designates a behavioral feature that the behavior implements.
The behavioral feature must be owned by the classifier that owns the behavior or be inherited by it. The parameters of the behavioral feature and the implementing behavior must match.
If a behavior does not have a specification, it is directly associated with a classifier (i.e., it is the behavior of the classifier as a whole).
If true, the Classifier does not provide a complete declaration and can typically not be instantiated.
An abstract classifier is intended to be used by other classifiers e.g. as the target of general metarelationships or generalization relationships.
Determines whether an object specified by this classifier is active or not. If true, then the owning classifier is referred to as an active classifier. If false, then such a classifier is referred to as a passive classifier.
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.
If true, this activity must not make any changes to variables outside the activity or to objects.
(This is an assertion, not an executable property. It may be used by an execution engine to optimize model execution. If the assertion is violated by the action, then the model is ill-formed.)
The default is false (an activity may make nonlocal changes).
Tells whether the behavior can be invoked while it is still executing from a previous invocation.
If true, all invocations of the activity are handled by the same execution.
The classifier that is the context for the execution of the behavior.
If the behavior is owned by a BehavioredClassifier, that classifier is the context. Otherwise, the context is the first BehavioredClassifier reached by following the chain of owner relationships.
For example, following this algorithm, the context of an entry action in a state machine is the classifier that owns the state machine. The features of the context classifier as well as the elements visible to the context classifier are visible to the behavior
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Actor (Actor)
An actor specifies a role played by a user or any other system that interacts with the subject.
Association (Association)
An association describes a set of tuples whose values refer to typed instances. An instance of an association is called a link.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
Collaboration (Collaboration)
A collaboration defines a set of co-operating roles used collectively to illustrate a specific functionality.
A collaboration should only show the roles and attributes required to accomplish its defined task or function. Isolating the primary roles is an exercise in simplifying the structure and clarifying the behavior, and also provides for re-use. A collaboration often implements a pattern.
Communication Path (Communication Path)
A communication path is an association between two deployment targets, through which they are able to exchange signals and messages.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Extension (Extension)
An extension is used to indicate that the properties of a metaclass are extended through a stereotype, and gives the ability to flexibly add (and later remove) stereotypes to classes.
Final State (Final State)
A special kind of state signifying that the enclosing region is completed.
If the enclosing region is directly contained in a state machine and all other regions in the state machine also are completed, then it means that the entire state machine is completed.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interface (Interface)
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
Model (Model)
A model captures a view of a physical system. It is an abstraction of the physical system, with a certain purpose.
This purpose determines what is to be included in the model and what is irrelevant. Thus the model completely describes those aspects of the physical system that are relevant to the purpose of the model, at the appropriate level of detail.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Package (Package)
A package is used to group elements, and provides a namespace for the grouped elements.
A package can have one or more profile applications to indicate which profiles have been applied.
Profile (Profile)
A profile defines limited extensions to a reference metamodel with the purpose of adapting the metamodel to a specific platform or domain.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
Protocol Transition (Protocol Transition)
A protocol transition 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.
State (State)
A state models a situation during which some (usually implicit) invariant condition holds.
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.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
Template Parameter (Template Parameter)
A template parameter exposes a parameterable element as a formal template parameter of a template.
Transition (Transition)
A transition is a directed relationship between a source vertex and a target vertex.
It may be part of a compound transition, which takes the state machine from one state configuration to another, representing the complete response of the state machine to an occurrence of an event of a particular type.
Use Case (Use Case)
A use case is the specification of a set of actions performed by a system, which yields an observable result that is, typically, of value for one or more actors or other stakeholders of the system.
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.
Action Input 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 input pin is a pin that holds input values to be consumed by an action.
An action input pin is a kind of pin that executes an action to determine the values to input to another.
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Activity Final Node (Control Node)
A control node is an abstract activity node that coordinates flows in an activity.
A final node is an abstract control node at which a flow in an activity stops.
An activity final node is a final node that stops all flows in an activity.
Activity Parameter Node (Object Node)
An object node is an abstract activity node that is part of defining object flow in an activity. Object nodes have support for token selection, limitation on the number of tokens, specifying the state required for tokens, and carrying control values.
An activity parameter node is an object node for inputs and outputs to activities.
Activity Partition (Activity Partition)
An activity partition is a kind of activity group for identifying actions that have some characteristic in common.
Actor (Actor)
An actor specifies a role played by a user or any other system that interacts with the subject.
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.
Artifact (Artifact)
An artifact is the specification of a physical piece of information that is used or produced by a software development process, or by deployment and operation of a system.
Examples of artifacts include model files, source files, scripts, and binary executable files, a table in a database system, a development deliverable, or a word-processing document, a mail message. An artifact is the source of a deployment to a node.
Association (Association)
An association describes a set of tuples whose values refer to typed instances. An instance of an association is called a link.
Association End (Association End)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An association End is a property that has a reference to an association.
Attribute (Attribute)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An attribute is a property that has no reference to an association.
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.
Central Buffer (Object Node)
An object node is an abstract activity node that is part of defining object flow in an activity. Object nodes have support for token selection, limitation on the number of tokens, specifying the state required for tokens, and carrying control values.
A central buffer node is an object node for managing flows from multiple sources and destinations.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
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.
Collaboration (Collaboration)
A collaboration defines a set of co-operating roles used collectively to illustrate a specific functionality.
A collaboration should only show the roles and attributes required to accomplish its defined task or function. Isolating the primary roles is an exercise in simplifying the structure and clarifying the behavior, and also provides for re-use. A collaboration often implements a pattern.
Collaboration Use (Collaboration Use)
A collaboration use represents one particular use of a collaboration to explain the relationships between the properties of a classifier.
A collaboration use shows how the pattern described by a collaboration is applied in a given context, by binding specific entities from that context to the roles of the collaboration. Depending on the context, these entities could be structural features of a classifier, instance specifications, or even roles in some containing collaboration. There may be multiple occurrences of a given collaboration within a classifier, each involving a different set of roles and connectors.
A given role or connector may be involved in multiple occurrences of the same or different collaborations. Associated dependencies map features of the collaboration type to features in the classifier. These dependencies indicate which role in the classifier plays which role in the collaboration.
Communication Path (Communication Path)
A communication path is an association between two deployment targets, through which they are able to exchange signals and messages.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
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.
Connector (Connector)
Specifies a link that enables communication between two or more instances. This link may be an instance of anassociation, or it may represent the possibility of the instances being able to communicate because their identitiesare known by virtue of being passed in as parameters, held in variables or slots, or because the communicatinginstances are the same instance.
The link may be realized by something as simple as a pointer or by something ascomplex as a network connection. In contrast to associations, which specify links between any instance of theassociated classifiers, connectors specify links between instances playing the connected parts only.
Constraint (Constraint)
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.
Control Flow (Control Flow)
A control flow is an edge that starts an activity node after the previous one is finished.
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.
Data Store Node (Object Node)
An object node is an abstract activity node that is part of defining object flow in an activity. Object nodes have support for token selection, limitation on the number of tokens, specifying the state required for tokens, and carrying control values.
A central buffer node is an object node for managing flows from multiple sources and destinations.
A data store node is a central buffer node for non-transient information.
Data Type (Data Type)
A data type is a type whose instances are identified only by their value. A data type may contain attributes to support the modeling of structured data types.
Decision Node (Control Node)
A control node is an abstract activity node that coordinates flows in an activity.
A decision node is a control node that chooses between outgoing flows.
Deployment Specification (Deployment Specification)
A deployment specification specifies a set of properties that determine execution parameters of a component artifact that is deployed on a node.
A deployment specification can be aimed at a specific type of container. An artifact that reifies or implements deployment specification properties is a deployment descriptor.
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.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Enumeration (Enumeration)
An enumeration is a data type whose values are enumerated in the model as enumeration literals.
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Expansion Node (Object Node)
An object node is an abstract activity node that is part of defining object flow in an activity. Object nodes have support for token selection, limitation on the number of tokens, specifying the state required for tokens, and carrying control values.
An expansion node is an object node used to indicate a flow across the boundary of an expansion region. A flow into a region contains a collection that is broken into its individual elements inside the region, which is executed once per element. A flow out of a region combines individual elements into a collection for use outside the region.
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.
Extension (Extension)
An extension is used to indicate that the properties of a metaclass are extended through a stereotype, and gives the ability to flexibly add (and later remove) stereotypes to classes.
Flow Final Node (Control Node)
A control node is an abstract activity node that coordinates flows in an activity.
A final node is an abstract control node at which a flow in an activity stops.
A flow final node is a final node that terminates a flow.
Fork Node (Control Node)
A control node is an abstract activity node that coordinates flows in an activity.
A fork node is a control node that splits a flow into multiple concurrent flows.
Information Item (Information Item)
An information item is an abstraction of all kinds of information that can be exchanged between objects. It is a kind of
classifier intended for representing information in a very abstract way, one which cannot be instantiated.
Initial Node (Control Node)
A control node is an abstract activity node that coordinates flows in an activity.
An initial node is a control node at which flow starts when the activity is invoked.
Input 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 input pin is a pin that holds input values to be consumed by an action.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interface (Interface)
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
Join Node (Control Node)
A control node is an abstract activity node that coordinates flows in an activity.
A join node is a control node that synchronizes multiple flows. Join nodes have a Boolean value specification using the names of the incoming edges to specify the conditions under which the join will emit a token.
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.
Merge Node (Control Node)
A control node is an abstract activity node that coordinates flows in an activity.
A merge node is a control node that brings together multiple alternate flows. It is not used to synchronize concurrent flows but to accept one among several alternate flows.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Object Flow (Object Flow)
An object flow is an activity edge that can have objects or data passing along it. Object flows have support for multicast/receive, token selection from object nodes, and transformation of tokens.
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.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Operation (Operation)
An operation is a behavioral feature of a classifier that specifies the name, type, parameters, and constraints for invoking an associated behavior. An operation may invoke both the execution of method behaviors as well as other behavioral responses.
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.
Parameter (Parameter)
A parameter is a specification of an argument used to pass information into or out of an invocation of a behavioral feature. Parameters are allowed to be treated as connectable elements. Parameters have support for streaming, exceptions, and parameter sets.
Port (Port)
A port is a property of a classifier that specifies a distinct interaction point between that classifier and its environment or between the (behavior of the) classifier and its internal parts.
Ports are connected to properties of the classifier by connectors through which requests can be made to invoke the behavioral features of a classifier.
A Port may specify the services a classifier provides (offers) to its environment as well as the services that a classifier expects (requires) of its environment. A port has an associated protocol state machine.
Primitive Type (Primitive Type)
A primitive type defines a predefined data type, without any relevant substructure (i.e., it has no parts in the context of UML). A primitive datatype may have an algebra and operations defined outside of UML, for example, mathematically.
Protocol (Protocol)
Only available together with the Real-Time Extension of RSA.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
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.
Reception (Reception)
A reception is a declaration stating that a classifier is prepared to react to the receipt of a signal. A reception designates a signal and specifies the expected behavioral response.
The details of handling a signal are specified by the behavior associated with the reception or the classifier itself.
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.
Signal (Signal)
A signal is a specification of send request instances communicated between objects. The receiving object handles the received request instances as specified by its receptions. The data carried by a send request (which was passed to it by the send invocation occurrence that caused that request) are represented as attributes of the signal.
A signal is defined independently of the classifiers handling the signal occurrence.
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
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
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.
Template Signature (Template Signature)
A template signature bundles the set of formal template parameters for a templated element.
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.
Trigger (Trigger)
A trigger relates an event to a behavior that may affect an instance of the classifier. A trigger specification may be qualified by the port on which the event occurred.
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.
Use Case (Use Case)
A use case is the specification of a set of actions performed by a system, which yields an observable result that is, typically, of value for one or more actors or other stakeholders of the system.
Value 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 input pin is a pin that holds input values to be consumed by an action.
A value pin is an input pin that provides a value by evaluating a value specification.
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.
Activity Diagram (Activity Diagram)
An Activity Diagram is a diagram that shows the decomposition of an activity into actions and the control and dataflow between these behavorial elements.
Class Diagram (Class Diagram)
A Class Diagram is a diagram that shows classes and interfaces and their relationships. However a class diagram may also show packages and all kind of classifier elements.
Component Diagram (Component Diagram)
A Component Diagram is a diagram that shows components, interfaces and artifacts and their relationships. However a component diagram may also show packages and all kind of classifier elements.
Deployment Diagram (Deployment Diagram)
A Deployment Diagram is a diagram that shows nodes and artifacts and their relationships. However a deployment diagram may also show packages and all kind of classifier elements.
Freeform Diagram (Freeform Diagram)
A Free Form diagram is a diagram in which you can make free drawings without the restriction of using UML.
Interaction Overview Diagram (Interaction Overview Diagram)
An Interaction Overview Diagram is a visual representation of a control flow of interaction..
Object Diagram (Object Diagram)
An Object Diagram is a diagram that shows instance specification, links and slots.
Structure Diagram (Structure Diagram)
A Structure Diagram is a diagram that shows the static structure of an element.
Use Case Diagram (Use Case Diagram)
A Use-Case Diagram is a diagram that shows actors and use cases and their relationships. However a Use-Case Diagram may also show packages and all kind of classifier elements.
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.
Component Realization (Component Realization)
The realization concept is specialized to (optionally) define the classifiers that realize the contract offered by a component in terms of its provided and required interfaces.
The component forms an abstraction from these various
classifiers.
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).
Element Import (Element Import)
An element import identifies an element in another package, and allows the element to be referenced using its name without a qualifier.
Generalization (Generalization)
A generalization is a taxonomic relationship between a more general classifier and a more specific classifier. Each instance of the specific classifier is also an indirect instance of the general classifier. Thus, the specific classifier inherits the features of the more general classifier.
A generalization relates a specific classifier to a more general classifier, and is owned by the specific classifier.
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.
Interface Realization (Interface Realization)
An interface realization is a specialized realization relationship between a classifier and an interface. This relationship signifies that the realizing classifier conforms to the contract specified by the interface.
Package Import (Package Import)
A package import is a relationship that allows the use of unqualified names to refer to package members from other namespaces.
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.
Templatebinding (Templatebinding)
A template binding represents a relationship between a templateable element and a template. A template binding specifies the substitutions of actual parameters for the formal parameters of the template.
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.
Action Input Pin (Pin)Activity Parameter Node (Object Node)Association End (Association End)Attribute (Attribute)Central Buffer (Object Node)Data Store Node (Object Node)Expansion Node (Object Node)Input Pin (Pin)Output Pin (Pin)Parameter (Parameter)Port (Port)Value Pin (Pin)Call Behavior Action (Action)Abstraction (Abstraction)Component Realization (Component Realization)Dependency (Dependency)Element Import (Element Import)Generalization (Generalization)Information Flow (Information Flow)Manifestation (Manifestation)Realization (Realization)Substitution (Substitution)Usage (Usage)Action Input Pin (Pin)Activity Parameter Node (Object Node)Central Buffer (Object Node)Data Store Node (Object Node)Expansion Node (Object Node)Input Pin (Pin)Object Flow (Object Flow)Output Pin (Pin)Value Pin (Pin)Object Flow (Object Flow) 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.
The 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.
An 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.
Control Flow (Control Flow)Object Flow (Object Flow)Control Flow (Control Flow)Object Flow (Object Flow)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.
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) Action Input 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 input pin is a pin that holds input values to be consumed by an action.
An action input pin is a kind of pin that executes an action to determine the values to input to another.
The pinKind must be 'actionInputPin'
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.
An 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.
Control Flow (Control Flow)Object Flow (Object Flow)Control Flow (Control Flow)Object Flow (Object Flow)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.
Abstraction (Abstraction)Control Flow (Control Flow)Dependency (Dependency)Information Flow (Information Flow)Object Flow (Object Flow)Realization (Realization)Send Object Action (Action)Send Signal Action (Action)Substitution (Substitution)Usage (Usage)Control Flow (Control Flow)Object Flow (Object Flow) Value 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 input pin is a pin that holds input values to be consumed by an action.
A value pin is an input pin that provides a value by evaluating a value specification.
The pinKind must be 'valuePin'
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.
Value that the pin will provide.
An 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.
Control Flow (Control Flow)Object Flow (Object Flow)Control Flow (Control Flow)Object Flow (Object Flow)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.
Abstraction (Abstraction)Control Flow (Control Flow)Dependency (Dependency)Information Flow (Information Flow)Object Flow (Object Flow)Realization (Realization)Send Object Action (Action)Send Signal Action (Action)Substitution (Substitution)Usage (Usage)Control Flow (Control Flow)Object Flow (Object Flow) Input 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 input pin is a pin that holds input values to be consumed by an action.
The pinKind must be 'inputPin'
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.
An 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.
Control Flow (Control Flow)Object Flow (Object Flow)Control Flow (Control Flow)Object Flow (Object Flow)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.
Abstraction (Abstraction)Control Flow (Control Flow)Dependency (Dependency)Information Flow (Information Flow)Object Flow (Object Flow)Realization (Realization)Send Object Action (Action)Send Signal Action (Action)Substitution (Substitution)Usage (Usage)Control Flow (Control Flow)Object Flow (Object Flow) RegionA region is an orthogonal part of either a composite state or a state machine. It contains states and transitions.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
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.
An element of one of the following kinds:
Final State (Final State)
A special kind of state signifying that the enclosing region is completed.
If the enclosing region is directly contained in a state machine and all other regions in the state machine also are completed, then it means that the entire state machine is completed.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
State (State)
A state models a situation during which some (usually implicit) invariant condition holds.
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.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Choice (Pseudo State)
Choice vertices which, when reached, result in the dynamic evaluation of the guards of the triggers of its outgoing transitions. This realizes a dynamic conditional branch. It allows splitting of transitions into multiple outgoing paths such that the decision on which path to take may be a function of the results of prior actions performed in the same run-tocompletion step. If more than one of the guards evaluates to true, an arbitrary one is selected. If none of the guards evaluates to true, then the model is considered ill-formed. (To avoid this, it is recommended to define one outgoing transition with the predefined else guard for every choice vertex.) Choice vertices should be distinguished from static branch points that are based on junction points.
Connection Point Reference (Connection Point Reference)
A connection point reference represents a usage (as part of a submachine state) of an entry/exit point defined in the statemachine reference by the submachine state.
Constraint (Constraint)
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.
Deep History (Pseudo State)
DeepHistory represents the most recent active configuration of the composite state that directly contains this pseudostate; e.g. the state configuration that was active when the composite state was last exited. A composite state can have at most one deep history vertex. At most one transition may originate from the history connector to the default deep history state. This transition is taken in case the composite state had never been active before. Entry actions of states entered on the path to the state represented by a deep history are performed.
Entry Point (Pseudo State)
An entry point pseudostate is an entry point of a state machine or composite state. In each region of the state machine or composite state it has a single transition to a vertex within the same region.
Exit Point (Pseudo State)
An exit point pseudostate is an exit point of a state machine or composite state. Entering an exit point within any region of the composite state or state machine referenced by a submachine state implies the exit of this composite state or submachine state and the triggering of the transition that has this exit point as source in the state machine enclosing the submachine or composite state.
Final State (Final State)
A special kind of state signifying that the enclosing region is completed.
If the enclosing region is directly contained in a state machine and all other regions in the state machine also are completed, then it means that the entire state machine is completed.
Fork (Pseudo State)
Fork vertices serve to split an incoming transition into two or more transitions terminating on orthogonal target vertices (i.e. vertices in different regions of a composite state). The segments outgoing from a fork vertex must not have guards or triggers.
Initial (Pseudo State)
An initial pseudostate represents a default vertex that is the source for a single transition to the default state of a composite state. There can be at most one initial vertex in a region. The outgoing transition from the initial vertex may have a behavior, but not a trigger or guard.
Join (Pseudo State)
Join vertices serve to merge several transitions emanating from source vertices in different orthogonal regions. The transitions entering a join vertex cannot have guards or triggers.
Junction (Pseudo State)
Junction vertices are semantic-free vertices that are used to chain together multiple transitions. They are used to construct compound transition paths between states. For example, a junction can be used to converge multiple incoming transitions into a single outgoing transition representing a shared transition path (this is known as an merge). Conversely, they can be used to split an incoming transition into multiple outgoing transition segments with different guard conditions. This realizes a static conditional branch. (In the latter case, outgoing transitions whose guard conditions evaluate to false are disabled. A predefined guard denoted 'else' may be defined for at most one outgoing transition. This transition is enabled if all the guards labeling the other transitions are false.) Static conditional branches are distinct from dynamic conditional branches that are realized by choice vertices.
Protocol Transition (Protocol Transition)
A protocol transition 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.
Shallow History (Pseudo State)
ShallowHistory represents the most recent active substate of its containing state (but not the substates of that substate). A composite state can have at most one shallow history vertex. A transition coming into the shallow history vertex is equivalent to a transition coming into the most recent active substate of a state. At most one transition may originate from the history connector to the default shallow history state. This transition is taken in case the composite state had never been active before. Entry actions of states entered on the path to the state represented by a shallow history are performed.
State (State)
A state models a situation during which some (usually implicit) invariant condition holds.
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.
Terminate (Pseudo State)
Entering a terminate pseudostate implies that the execution of this state machine by means of its context object is terminated. The state machine does not exit any states nor does it perform any exit actions other than those associated with the transition leading to the terminate pseudostate. Entering a terminate pseudostate is equivalent to invoking a DestroyObjectAction.
Transition (Transition)
A transition is a directed relationship between a source vertex and a target vertex.
It may be part of a compound transition, which takes the state machine from one state configuration to another, representing the complete response of the state machine to an occurrence of an event of a particular type.
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).
Element Import (Element Import)
An element import identifies an element in another package, and allows the element to be referenced using its name without a qualifier.
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.
Package Import (Package Import)
A package import is a relationship that allows the use of unqualified names to refer to package members from other namespaces.
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.
Abstraction (Abstraction)Dependency (Dependency)Information Flow (Information Flow)Realization (Realization)Substitution (Substitution)Usage (Usage) TriggerA trigger relates an event to a behavior that may affect an instance of the classifier. A trigger specification may be qualified by the port on which the event occurred.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
The event that causes the trigger.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Actor (Actor)
An actor specifies a role played by a user or any other system that interacts with the subject.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
Collaboration (Collaboration)
A collaboration defines a set of co-operating roles used collectively to illustrate a specific functionality.
A collaboration should only show the roles and attributes required to accomplish its defined task or function. Isolating the primary roles is an exercise in simplifying the structure and clarifying the behavior, and also provides for re-use. A collaboration often implements a pattern.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Final State (Final State)
A special kind of state signifying that the enclosing region is completed.
If the enclosing region is directly contained in a state machine and all other regions in the state machine also are completed, then it means that the entire state machine is completed.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
Protocol Transition (Protocol Transition)
A protocol transition 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.
State (State)
A state models a situation during which some (usually implicit) invariant condition holds.
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.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
Transition (Transition)
A transition is a directed relationship between a source vertex and a target vertex.
It may be part of a compound transition, which takes the state machine from one state configuration to another, representing the complete response of the state machine to an occurrence of an event of a particular type.
Use Case (Use Case)
A use case is the specification of a set of actions performed by a system, which yields an observable result that is, typically, of value for one or more actors or other stakeholders of the system.
Port (Port)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.
Abstraction (Abstraction)Dependency (Dependency)Information Flow (Information Flow)Realization (Realization)Substitution (Substitution)Usage (Usage) 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.
The value must be ''.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
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.
Action Input 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 input pin is a pin that holds input values to be consumed by an action.
An action input pin is a kind of pin that executes an action to determine the values to input to another.
Constraint (Constraint)
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.
Input 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 input pin is a pin that holds input values to be consumed by an action.
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.
Value 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 input pin is a pin that holds input values to be consumed by an action.
A value pin is an input pin that provides a value by evaluating a value specification.
Control Flow (Control Flow)Object Flow (Object Flow)Control Flow (Control Flow)Object Flow (Object Flow)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.
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) 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.
The value must be ''.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
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.
Action Input 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 input pin is a pin that holds input values to be consumed by an action.
An action input pin is a kind of pin that executes an action to determine the values to input to another.
Constraint (Constraint)
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.
Input 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 input pin is a pin that holds input values to be consumed by an action.
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.
Value 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 input pin is a pin that holds input values to be consumed by an action.
A value pin is an input pin that provides a value by evaluating a value specification.
Control Flow (Control Flow)Object Flow (Object Flow)Control Flow (Control Flow)Object Flow (Object Flow)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.
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) 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.
The value must be ''.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
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.
Action Input 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 input pin is a pin that holds input values to be consumed by an action.
An action input pin is a kind of pin that executes an action to determine the values to input to another.
Constraint (Constraint)
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.
Input 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 input pin is a pin that holds input values to be consumed by an action.
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.
Value 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 input pin is a pin that holds input values to be consumed by an action.
A value pin is an input pin that provides a value by evaluating a value specification.
Control Flow (Control Flow)Object Flow (Object Flow)Control Flow (Control Flow)Object Flow (Object Flow)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.
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) 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.
The value must be ''.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
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.
Action Input 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 input pin is a pin that holds input values to be consumed by an action.
An action input pin is a kind of pin that executes an action to determine the values to input to another.
Constraint (Constraint)
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.
Input 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 input pin is a pin that holds input values to be consumed by an action.
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.
Value 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 input pin is a pin that holds input values to be consumed by an action.
A value pin is an input pin that provides a value by evaluating a value specification.
Control Flow (Control Flow)Object Flow (Object Flow)Control Flow (Control Flow)Object Flow (Object Flow)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.
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) 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.
The value must be ''.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
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.
Action Input 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 input pin is a pin that holds input values to be consumed by an action.
An action input pin is a kind of pin that executes an action to determine the values to input to another.
Constraint (Constraint)
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.
Input 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 input pin is a pin that holds input values to be consumed by an action.
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.
Value 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 input pin is a pin that holds input values to be consumed by an action.
A value pin is an input pin that provides a value by evaluating a value specification.
Control Flow (Control Flow)Object Flow (Object Flow)Control Flow (Control Flow)Object Flow (Object Flow)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.
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) 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.
The value must be ''.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
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.
Action Input 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 input pin is a pin that holds input values to be consumed by an action.
An action input pin is a kind of pin that executes an action to determine the values to input to another.
Constraint (Constraint)
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.
Input 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 input pin is a pin that holds input values to be consumed by an action.
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.
Value 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 input pin is a pin that holds input values to be consumed by an action.
A value pin is an input pin that provides a value by evaluating a value specification.
Control Flow (Control Flow)Object Flow (Object Flow)Control Flow (Control Flow)Object Flow (Object Flow)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.
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) 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.
The value must be ''.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
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.
Action Input 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 input pin is a pin that holds input values to be consumed by an action.
An action input pin is a kind of pin that executes an action to determine the values to input to another.
Constraint (Constraint)
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.
Input 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 input pin is a pin that holds input values to be consumed by an action.
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.
Value 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 input pin is a pin that holds input values to be consumed by an action.
A value pin is an input pin that provides a value by evaluating a value specification.
Control Flow (Control Flow)Object Flow (Object Flow)Control Flow (Control Flow)Object Flow (Object Flow)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.
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) 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.
The value must be ''.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
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.
Action Input 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 input pin is a pin that holds input values to be consumed by an action.
An action input pin is a kind of pin that executes an action to determine the values to input to another.
Constraint (Constraint)
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.
Input 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 input pin is a pin that holds input values to be consumed by an action.
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.
Value 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 input pin is a pin that holds input values to be consumed by an action.
A value pin is an input pin that provides a value by evaluating a value specification.
Control Flow (Control Flow)Object Flow (Object Flow)Control Flow (Control Flow)Object Flow (Object Flow)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.
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) 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.
The value must be ''.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
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.
The type of signal transmitted to the target object.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
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.
Action Input 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 input pin is a pin that holds input values to be consumed by an action.
An action input pin is a kind of pin that executes an action to determine the values to input to another.
Constraint (Constraint)
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.
Input 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 input pin is a pin that holds input values to be consumed by an action.
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.
Value 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 input pin is a pin that holds input values to be consumed by an action.
A value pin is an input pin that provides a value by evaluating a value specification.
Control Flow (Control Flow)Object Flow (Object Flow)Control Flow (Control Flow)Object Flow (Object Flow)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.
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) 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.
The value must be ''.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
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.
Action Input 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 input pin is a pin that holds input values to be consumed by an action.
An action input pin is a kind of pin that executes an action to determine the values to input to another.
Constraint (Constraint)
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.
Input 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 input pin is a pin that holds input values to be consumed by an action.
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.
Value 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 input pin is a pin that holds input values to be consumed by an action.
A value pin is an input pin that provides a value by evaluating a value specification.
Control Flow (Control Flow)Object Flow (Object Flow)Control Flow (Control Flow)Object Flow (Object Flow)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.
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) 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.
The value must be ''.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
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.
Action Input 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 input pin is a pin that holds input values to be consumed by an action.
An action input pin is a kind of pin that executes an action to determine the values to input to another.
Constraint (Constraint)
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.
Input 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 input pin is a pin that holds input values to be consumed by an action.
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.
Value 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 input pin is a pin that holds input values to be consumed by an action.
A value pin is an input pin that provides a value by evaluating a value specification.
Control Flow (Control Flow)Object Flow (Object Flow)Control Flow (Control Flow)Object Flow (Object Flow)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.
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) 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.
The value must be ''.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
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.
Action Input 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 input pin is a pin that holds input values to be consumed by an action.
An action input pin is a kind of pin that executes an action to determine the values to input to another.
Constraint (Constraint)
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.
Input 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 input pin is a pin that holds input values to be consumed by an action.
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.
Value 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 input pin is a pin that holds input values to be consumed by an action.
A value pin is an input pin that provides a value by evaluating a value specification.
Control Flow (Control Flow)Object Flow (Object Flow)Control Flow (Control Flow)Object Flow (Object Flow)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.
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) 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
The value must be ''.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
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.
Action Input 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 input pin is a pin that holds input values to be consumed by an action.
An action input pin is a kind of pin that executes an action to determine the values to input to another.
Constraint (Constraint)
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.
Input 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 input pin is a pin that holds input values to be consumed by an action.
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.
Value 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 input pin is a pin that holds input values to be consumed by an action.
A value pin is an input pin that provides a value by evaluating a value specification.
Control Flow (Control Flow)Object Flow (Object Flow)Control Flow (Control Flow)Object Flow (Object Flow)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.
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) 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.
The value must be ''.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
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.
Action Input 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 input pin is a pin that holds input values to be consumed by an action.
An action input pin is a kind of pin that executes an action to determine the values to input to another.
Constraint (Constraint)
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.
Input 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 input pin is a pin that holds input values to be consumed by an action.
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.
Value 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 input pin is a pin that holds input values to be consumed by an action.
A value pin is an input pin that provides a value by evaluating a value specification.
Control Flow (Control Flow)Object Flow (Object Flow)Control Flow (Control Flow)Object Flow (Object Flow)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.
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) 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.
The value must be ''.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
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.
Action Input 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 input pin is a pin that holds input values to be consumed by an action.
An action input pin is a kind of pin that executes an action to determine the values to input to another.
Constraint (Constraint)
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.
Input 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 input pin is a pin that holds input values to be consumed by an action.
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.
Value 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 input pin is a pin that holds input values to be consumed by an action.
A value pin is an input pin that provides a value by evaluating a value specification.
Control Flow (Control Flow)Object Flow (Object Flow)Control Flow (Control Flow)Object Flow (Object Flow)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.
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) 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.
The value must be ''.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
The operation to be invoked by the action execution.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
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.
Action Input 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 input pin is a pin that holds input values to be consumed by an action.
An action input pin is a kind of pin that executes an action to determine the values to input to another.
Constraint (Constraint)
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.
Input 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 input pin is a pin that holds input values to be consumed by an action.
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.
Value 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 input pin is a pin that holds input values to be consumed by an action.
A value pin is an input pin that provides a value by evaluating a value specification.
Control Flow (Control Flow)Object Flow (Object Flow)Control Flow (Control Flow)Object Flow (Object Flow)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.
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) 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.
The value must be ''.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
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.
Action Input 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 input pin is a pin that holds input values to be consumed by an action.
An action input pin is a kind of pin that executes an action to determine the values to input to another.
Constraint (Constraint)
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.
Input 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 input pin is a pin that holds input values to be consumed by an action.
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.
Value 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 input pin is a pin that holds input values to be consumed by an action.
A value pin is an input pin that provides a value by evaluating a value specification.
Control Flow (Control Flow)Object Flow (Object Flow)Control Flow (Control Flow)Object Flow (Object Flow)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.
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) 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.
The value must be ''.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
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.
Action Input 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 input pin is a pin that holds input values to be consumed by an action.
An action input pin is a kind of pin that executes an action to determine the values to input to another.
Constraint (Constraint)
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.
Input 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 input pin is a pin that holds input values to be consumed by an action.
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.
Value 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 input pin is a pin that holds input values to be consumed by an action.
A value pin is an input pin that provides a value by evaluating a value specification.
Control Flow (Control Flow)Object Flow (Object Flow)Control Flow (Control Flow)Object Flow (Object Flow)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.
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) 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.
The value must be ''.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
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.
The invoked behavior. It must be capable of accepting and returning control.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
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.
Action Input 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 input pin is a pin that holds input values to be consumed by an action.
An action input pin is a kind of pin that executes an action to determine the values to input to another.
Constraint (Constraint)
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.
Input 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 input pin is a pin that holds input values to be consumed by an action.
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.
Value 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 input pin is a pin that holds input values to be consumed by an action.
A value pin is an input pin that provides a value by evaluating a value specification.
Control Flow (Control Flow)Object Flow (Object Flow)Control Flow (Control Flow)Object Flow (Object Flow)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.
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) 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.
The value must be ''.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
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.
Indicates whether there is a single output pin for the event, or multiple output pins for attributes of the event.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
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.
Action Input 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 input pin is a pin that holds input values to be consumed by an action.
An action input pin is a kind of pin that executes an action to determine the values to input to another.
Constraint (Constraint)
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.
Input 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 input pin is a pin that holds input values to be consumed by an action.
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.
Value 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 input pin is a pin that holds input values to be consumed by an action.
A value pin is an input pin that provides a value by evaluating a value specification.
Control Flow (Control Flow)Object Flow (Object Flow)Control Flow (Control Flow)Object Flow (Object Flow)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.
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) 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.
The value must be ''.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
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.
Action Input 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 input pin is a pin that holds input values to be consumed by an action.
An action input pin is a kind of pin that executes an action to determine the values to input to another.
Constraint (Constraint)
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.
Input 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 input pin is a pin that holds input values to be consumed by an action.
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.
Value 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 input pin is a pin that holds input values to be consumed by an action.
A value pin is an input pin that provides a value by evaluating a value specification.
Control Flow (Control Flow)Object Flow (Object Flow)Control Flow (Control Flow)Object Flow (Object Flow)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.
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) 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.
The value must be ''.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
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.
Action Input 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 input pin is a pin that holds input values to be consumed by an action.
An action input pin is a kind of pin that executes an action to determine the values to input to another.
Constraint (Constraint)
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.
Input 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 input pin is a pin that holds input values to be consumed by an action.
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.
Value 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 input pin is a pin that holds input values to be consumed by an action.
A value pin is an input pin that provides a value by evaluating a value specification.
Control Flow (Control Flow)Object Flow (Object Flow)Control Flow (Control Flow)Object Flow (Object Flow)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.
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) 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.
The value must be ''.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
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.
Action Input 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 input pin is a pin that holds input values to be consumed by an action.
An action input pin is a kind of pin that executes an action to determine the values to input to another.
Constraint (Constraint)
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.
Input 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 input pin is a pin that holds input values to be consumed by an action.
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.
Value 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 input pin is a pin that holds input values to be consumed by an action.
A value pin is an input pin that provides a value by evaluating a value specification.
Control Flow (Control Flow)Object Flow (Object Flow)Control Flow (Control Flow)Object Flow (Object Flow)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.
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) 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.
The value must be ''.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
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.
Action Input 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 input pin is a pin that holds input values to be consumed by an action.
An action input pin is a kind of pin that executes an action to determine the values to input to another.
Constraint (Constraint)
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.
Input 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 input pin is a pin that holds input values to be consumed by an action.
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.
Value 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 input pin is a pin that holds input values to be consumed by an action.
A value pin is an input pin that provides a value by evaluating a value specification.
Control Flow (Control Flow)Object Flow (Object Flow)Control Flow (Control Flow)Object Flow (Object Flow)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.
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) 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.
The value must be ''.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
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.
Action Input 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 input pin is a pin that holds input values to be consumed by an action.
An action input pin is a kind of pin that executes an action to determine the values to input to another.
Constraint (Constraint)
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.
Input 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 input pin is a pin that holds input values to be consumed by an action.
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.
Value 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 input pin is a pin that holds input values to be consumed by an action.
A value pin is an input pin that provides a value by evaluating a value specification.
Control Flow (Control Flow)Object Flow (Object Flow)Control Flow (Control Flow)Object Flow (Object Flow)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.
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) 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.
The value must be ''.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
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.
Action Input 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 input pin is a pin that holds input values to be consumed by an action.
An action input pin is a kind of pin that executes an action to determine the values to input to another.
Constraint (Constraint)
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.
Input 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 input pin is a pin that holds input values to be consumed by an action.
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.
Value 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 input pin is a pin that holds input values to be consumed by an action.
A value pin is an input pin that provides a value by evaluating a value specification.
Control Flow (Control Flow)Object Flow (Object Flow)Control Flow (Control Flow)Object Flow (Object Flow)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.
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) 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.
The value must be ''.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
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.
Indicates whether there is a single output pin for the event, or multiple output pins for attributes of the event.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
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.
Action Input 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 input pin is a pin that holds input values to be consumed by an action.
An action input pin is a kind of pin that executes an action to determine the values to input to another.
Constraint (Constraint)
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.
Input 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 input pin is a pin that holds input values to be consumed by an action.
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.
Value 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 input pin is a pin that holds input values to be consumed by an action.
A value pin is an input pin that provides a value by evaluating a value specification.
Control Flow (Control Flow)Object Flow (Object Flow)Control Flow (Control Flow)Object Flow (Object Flow)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.
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) 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.
The value must be ''.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
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.
Action Input 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 input pin is a pin that holds input values to be consumed by an action.
An action input pin is a kind of pin that executes an action to determine the values to input to another.
Constraint (Constraint)
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.
Input 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 input pin is a pin that holds input values to be consumed by an action.
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.
Value 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 input pin is a pin that holds input values to be consumed by an action.
A value pin is an input pin that provides a value by evaluating a value specification.
Control Flow (Control Flow)Object Flow (Object Flow)Control Flow (Control Flow)Object Flow (Object Flow)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.
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) 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.
The value must be ''.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
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.
Action Input 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 input pin is a pin that holds input values to be consumed by an action.
An action input pin is a kind of pin that executes an action to determine the values to input to another.
Constraint (Constraint)
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.
Input 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 input pin is a pin that holds input values to be consumed by an action.
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.
Value 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 input pin is a pin that holds input values to be consumed by an action.
A value pin is an input pin that provides a value by evaluating a value specification.
Control Flow (Control Flow)Object Flow (Object Flow)Control Flow (Control Flow)Object Flow (Object Flow)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.
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) 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.
The value must be ''.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
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.
Action Input 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 input pin is a pin that holds input values to be consumed by an action.
An action input pin is a kind of pin that executes an action to determine the values to input to another.
Constraint (Constraint)
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.
Input 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 input pin is a pin that holds input values to be consumed by an action.
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.
Value 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 input pin is a pin that holds input values to be consumed by an action.
A value pin is an input pin that provides a value by evaluating a value specification.
Control Flow (Control Flow)Object Flow (Object Flow)Control Flow (Control Flow)Object Flow (Object Flow)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.
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) 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.
The value must be ''.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
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.
Action Input 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 input pin is a pin that holds input values to be consumed by an action.
An action input pin is a kind of pin that executes an action to determine the values to input to another.
Constraint (Constraint)
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.
Input 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 input pin is a pin that holds input values to be consumed by an action.
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.
Value 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 input pin is a pin that holds input values to be consumed by an action.
A value pin is an input pin that provides a value by evaluating a value specification.
Control Flow (Control Flow)Object Flow (Object Flow)Control Flow (Control Flow)Object Flow (Object Flow)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.
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) 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.
The value must be ''.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
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.
Action Input 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 input pin is a pin that holds input values to be consumed by an action.
An action input pin is a kind of pin that executes an action to determine the values to input to another.
Constraint (Constraint)
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.
Input 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 input pin is a pin that holds input values to be consumed by an action.
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.
Value 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 input pin is a pin that holds input values to be consumed by an action.
A value pin is an input pin that provides a value by evaluating a value specification.
Control Flow (Control Flow)Object Flow (Object Flow)Control Flow (Control Flow)Object Flow (Object Flow)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.
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) 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.
The value must be ''.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
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.
Action Input 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 input pin is a pin that holds input values to be consumed by an action.
An action input pin is a kind of pin that executes an action to determine the values to input to another.
Constraint (Constraint)
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.
Input 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 input pin is a pin that holds input values to be consumed by an action.
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.
Value 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 input pin is a pin that holds input values to be consumed by an action.
A value pin is an input pin that provides a value by evaluating a value specification.
Control Flow (Control Flow)Object Flow (Object Flow)Control Flow (Control Flow)Object Flow (Object Flow)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.
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) 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.
The value must be ''.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
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.
Action Input 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 input pin is a pin that holds input values to be consumed by an action.
An action input pin is a kind of pin that executes an action to determine the values to input to another.
Constraint (Constraint)
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.
Input 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 input pin is a pin that holds input values to be consumed by an action.
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.
Value 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 input pin is a pin that holds input values to be consumed by an action.
A value pin is an input pin that provides a value by evaluating a value specification.
Control Flow (Control Flow)Object Flow (Object Flow)Control Flow (Control Flow)Object Flow (Object Flow)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.
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) 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.
The value must be ''.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
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.
Action Input 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 input pin is a pin that holds input values to be consumed by an action.
An action input pin is a kind of pin that executes an action to determine the values to input to another.
Constraint (Constraint)
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.
Input 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 input pin is a pin that holds input values to be consumed by an action.
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.
Value 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 input pin is a pin that holds input values to be consumed by an action.
A value pin is an input pin that provides a value by evaluating a value specification.
Control Flow (Control Flow)Object Flow (Object Flow)Control Flow (Control Flow)Object Flow (Object Flow)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.
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) 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.
The value must be ''.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
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.
Action Input 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 input pin is a pin that holds input values to be consumed by an action.
An action input pin is a kind of pin that executes an action to determine the values to input to another.
Constraint (Constraint)
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.
Input 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 input pin is a pin that holds input values to be consumed by an action.
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.
Value 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 input pin is a pin that holds input values to be consumed by an action.
A value pin is an input pin that provides a value by evaluating a value specification.
Control Flow (Control Flow)Object Flow (Object Flow)Control Flow (Control Flow)Object Flow (Object Flow)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.
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) 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.
The value must be ''.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
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.
Action Input 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 input pin is a pin that holds input values to be consumed by an action.
An action input pin is a kind of pin that executes an action to determine the values to input to another.
Constraint (Constraint)
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.
Input 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 input pin is a pin that holds input values to be consumed by an action.
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.
Value 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 input pin is a pin that holds input values to be consumed by an action.
A value pin is an input pin that provides a value by evaluating a value specification.
Control Flow (Control Flow)Object Flow (Object Flow)Control Flow (Control Flow)Object Flow (Object Flow)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.
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) 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.
The value must be ''.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
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.
Action Input 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 input pin is a pin that holds input values to be consumed by an action.
An action input pin is a kind of pin that executes an action to determine the values to input to another.
Constraint (Constraint)
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.
Input 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 input pin is a pin that holds input values to be consumed by an action.
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.
Value 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 input pin is a pin that holds input values to be consumed by an action.
A value pin is an input pin that provides a value by evaluating a value specification.
Control Flow (Control Flow)Object Flow (Object Flow)Control Flow (Control Flow)Object Flow (Object Flow)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.
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) 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.
The value must be ''.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
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.
Action Input 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 input pin is a pin that holds input values to be consumed by an action.
An action input pin is a kind of pin that executes an action to determine the values to input to another.
Constraint (Constraint)
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.
Input 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 input pin is a pin that holds input values to be consumed by an action.
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.
Value 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 input pin is a pin that holds input values to be consumed by an action.
A value pin is an input pin that provides a value by evaluating a value specification.
Control Flow (Control Flow)Object Flow (Object Flow)Control Flow (Control Flow)Object Flow (Object Flow)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.
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) 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.
The value must be ''.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
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.
Action Input 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 input pin is a pin that holds input values to be consumed by an action.
An action input pin is a kind of pin that executes an action to determine the values to input to another.
Constraint (Constraint)
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.
Input 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 input pin is a pin that holds input values to be consumed by an action.
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.
Value 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 input pin is a pin that holds input values to be consumed by an action.
A value pin is an input pin that provides a value by evaluating a value specification.
Control Flow (Control Flow)Object Flow (Object Flow)Control Flow (Control Flow)Object Flow (Object Flow)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.
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) 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:
The value must be ''.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
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.
Action Input 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 input pin is a pin that holds input values to be consumed by an action.
An action input pin is a kind of pin that executes an action to determine the values to input to another.
Constraint (Constraint)
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.
Input 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 input pin is a pin that holds input values to be consumed by an action.
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.
Value 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 input pin is a pin that holds input values to be consumed by an action.
A value pin is an input pin that provides a value by evaluating a value specification.
Control Flow (Control Flow)Object Flow (Object Flow)Control Flow (Control Flow)Object Flow (Object Flow)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.
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) 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.
The value must be ''.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
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.
Action Input 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 input pin is a pin that holds input values to be consumed by an action.
An action input pin is a kind of pin that executes an action to determine the values to input to another.
Constraint (Constraint)
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.
Input 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 input pin is a pin that holds input values to be consumed by an action.
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.
Value 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 input pin is a pin that holds input values to be consumed by an action.
A value pin is an input pin that provides a value by evaluating a value specification.
Control Flow (Control Flow)Object Flow (Object Flow)Control Flow (Control Flow)Object Flow (Object Flow)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.
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) Activity PartitionAn activity partition is a kind of activity group for identifying actions that have some characteristic in common.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Activity Partition (Activity Partition)
An activity partition is a kind of activity group for identifying actions that have some characteristic in common.
Activity Partition (Activity Partition)
An activity partition is a kind of activity group for identifying actions that have some characteristic in common.
Control Flow (Control Flow)Object Flow (Object Flow)Accept Call Action (Action)Accept Event Action (Action)Action Input Pin (Pin)Activity Final Node (Control Node)Activity Parameter Node (Object Node)Add Structural Feature Value Action (Action)Add Variable Value Action (Action)Broadcast Signal Action (Action)Call Behavior Action (Action)Call Operation Action (Action)Central Buffer (Object Node)Clear Association Action (Action)Clear Structural Feature Action (Action)Clear Variable Action (Action)Conditional Node (Action)Create Link Action (Action)Create Link Object Action (Action)Create Object Action (Action)Data Store Node (Object Node)Decision Node (Control Node)Destroy Link Action (Action)Destroy Object Action (Action)Expansion Node (Object Node)Expansion Region (Action)Flow Final Node (Control Node)Fork Node (Control Node)Initial Node (Control Node)Input Pin (Pin)Join Node (Control Node)Loop Node (Action)Merge Node (Control Node)Opaque Action (Action)Output Pin (Pin)Raise Exception Action (Action)Read Extent Action (Action)Read Is Classified Object Action (Action)Read Link Action (Action)Read Link Object End Action (Action)Read Link Object End Qualifier Action (Action)Read Self Action (Action)Read Structural Feature Action (Action)Read Variable Action (Action)Reclassify Object Action (Action)Reduce Action (Action)Remove Structural Feature Value Action (Action)Remove Variable Value Action (Action)Reply Action (Action)Send Object Action (Action)Send Signal Action (Action)Sequence Node (Action)Start Classifier Behavior Action (Action)Start Object Behavior Action (Action)Structured Activity Node (Action)Structured Activity Node (Structured Activity Node)Test Identity Action (Action)Unmarshall Action (Action)Value Pin (Pin)Value Specification Action (Action)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.
Abstraction (Abstraction)Dependency (Dependency)Information Flow (Information Flow)Realization (Realization)Substitution (Substitution)Usage (Usage) Decision Node (Control Node)A control node is an abstract activity node that coordinates flows in an activity.
A decision node is a control node that chooses between outgoing flows.
The value must be 'decisionNode'
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
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.
Control Flow (Control Flow)Object Flow (Object Flow)Control Flow (Control Flow)Object Flow (Object Flow)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.
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) Initial Node (Control Node)A control node is an abstract activity node that coordinates flows in an activity.
An initial node is a control node at which flow starts when the activity is invoked.
The value must be ''
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
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.
Control Flow (Control Flow)Object Flow (Object Flow)Control Flow (Control Flow)Object Flow (Object Flow)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.
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) Join Node (Control Node)A control node is an abstract activity node that coordinates flows in an activity.
A join node is a control node that synchronizes multiple flows. Join nodes have a Boolean value specification using the names of the incoming edges to specify the conditions under which the join will emit a token.
The value must be 'joinNode'
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
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.
Control Flow (Control Flow)Object Flow (Object Flow)Control Flow (Control Flow)Object Flow (Object Flow)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.
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) Flow Final Node (Control Node)A control node is an abstract activity node that coordinates flows in an activity.
A final node is an abstract control node at which a flow in an activity stops.
A flow final node is a final node that terminates a flow.
The value must be 'flowFinalNode'.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
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.
Control Flow (Control Flow)Object Flow (Object Flow)Control Flow (Control Flow)Object Flow (Object Flow)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.
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) Merge Node (Control Node)A control node is an abstract activity node that coordinates flows in an activity.
A merge node is a control node that brings together multiple alternate flows. It is not used to synchronize concurrent flows but to accept one among several alternate flows.
The value must be 'mergeNode'
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
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.
Control Flow (Control Flow)Object Flow (Object Flow)Control Flow (Control Flow)Object Flow (Object Flow)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.
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) Activity Final Node (Control Node)A control node is an abstract activity node that coordinates flows in an activity.
A final node is an abstract control node at which a flow in an activity stops.
An activity final node is a final node that stops all flows in an activity.
The value must be 'activityFinalNode'
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
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.
Control Flow (Control Flow)Object Flow (Object Flow)Control Flow (Control Flow)Object Flow (Object Flow)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.
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) Fork Node (Control Node)A control node is an abstract activity node that coordinates flows in an activity.
A fork node is a control node that splits a flow into multiple concurrent flows.
The value must be 'forkNode'
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
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.
Control Flow (Control Flow)Object Flow (Object Flow)Control Flow (Control Flow)Object Flow (Object Flow)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.
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) Data Store Node (Object Node)An object node is an abstract activity node that is part of defining object flow in an activity. Object nodes have support for token selection, limitation on the number of tokens, specifying the state required for tokens, and carrying control values.
A central buffer node is an object node for managing flows from multiple sources and destinations.
A data store node is a central buffer node for non-transient information.
The objectNodeKind must be 'dataStoreNode'
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
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.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
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.
Control Flow (Control Flow)Object Flow (Object Flow)Control Flow (Control Flow)Object Flow (Object Flow)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.
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) Central Buffer (Object Node)An object node is an abstract activity node that is part of defining object flow in an activity. Object nodes have support for token selection, limitation on the number of tokens, specifying the state required for tokens, and carrying control values.
A central buffer node is an object node for managing flows from multiple sources and destinations.
The objectNodeKind must be 'centralBufferNode'
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
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.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
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.
Control Flow (Control Flow)Object Flow (Object Flow)Control Flow (Control Flow)Object Flow (Object Flow)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.
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) Activity Parameter Node (Object Node)An object node is an abstract activity node that is part of defining object flow in an activity. Object nodes have support for token selection, limitation on the number of tokens, specifying the state required for tokens, and carrying control values.
An activity parameter node is an object node for inputs and outputs to activities.
The objectNodeKind must be 'activityParameterNode'
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
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.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
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.
Control Flow (Control Flow)Object Flow (Object Flow)Control Flow (Control Flow)Object Flow (Object Flow)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.
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) Expansion Node (Object Node)An object node is an abstract activity node that is part of defining object flow in an activity. Object nodes have support for token selection, limitation on the number of tokens, specifying the state required for tokens, and carrying control values.
An expansion node is an object node used to indicate a flow across the boundary of an expansion region. A flow into a region contains a collection that is broken into its individual elements inside the region, which is executed once per element. A flow out of a region combines individual elements into a collection for use outside the region.
The objectNodeKind must be expansionNode'
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
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.
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.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
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.
Control Flow (Control Flow)Object Flow (Object Flow)Control Flow (Control Flow)Object Flow (Object Flow)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.
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) Structured Activity NodeA 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.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
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.
If true, then the actions in the node execute in isolation from actions outside the node.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
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.
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.
Action Input 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 input pin is a pin that holds input values to be consumed by an action.
An action input pin is a kind of pin that executes an action to determine the values to input to another.
Activity Final Node (Control Node)
A control node is an abstract activity node that coordinates flows in an activity.
A final node is an abstract control node at which a flow in an activity stops.
An activity final node is a final node that stops all flows in an activity.
Activity Parameter Node (Object Node)
An object node is an abstract activity node that is part of defining object flow in an activity. Object nodes have support for token selection, limitation on the number of tokens, specifying the state required for tokens, and carrying control values.
An activity parameter node is an object node for inputs and outputs to activities.
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.
Central Buffer (Object Node)
An object node is an abstract activity node that is part of defining object flow in an activity. Object nodes have support for token selection, limitation on the number of tokens, specifying the state required for tokens, and carrying control values.
A central buffer node is an object node for managing flows from multiple sources and destinations.
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.
Constraint (Constraint)
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.
Control Flow (Control Flow)
A control flow is an edge that starts an activity node after the previous one is finished.
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.
Data Store Node (Object Node)
An object node is an abstract activity node that is part of defining object flow in an activity. Object nodes have support for token selection, limitation on the number of tokens, specifying the state required for tokens, and carrying control values.
A central buffer node is an object node for managing flows from multiple sources and destinations.
A data store node is a central buffer node for non-transient information.
Decision Node (Control Node)
A control node is an abstract activity node that coordinates flows in an activity.
A decision node is a control node that chooses between outgoing flows.
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 Node (Object Node)
An object node is an abstract activity node that is part of defining object flow in an activity. Object nodes have support for token selection, limitation on the number of tokens, specifying the state required for tokens, and carrying control values.
An expansion node is an object node used to indicate a flow across the boundary of an expansion region. A flow into a region contains a collection that is broken into its individual elements inside the region, which is executed once per element. A flow out of a region combines individual elements into a collection for use outside the region.
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.
Flow Final Node (Control Node)
A control node is an abstract activity node that coordinates flows in an activity.
A final node is an abstract control node at which a flow in an activity stops.
A flow final node is a final node that terminates a flow.
Fork Node (Control Node)
A control node is an abstract activity node that coordinates flows in an activity.
A fork node is a control node that splits a flow into multiple concurrent flows.
Initial Node (Control Node)
A control node is an abstract activity node that coordinates flows in an activity.
An initial node is a control node at which flow starts when the activity is invoked.
Input 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 input pin is a pin that holds input values to be consumed by an action.
Join Node (Control Node)
A control node is an abstract activity node that coordinates flows in an activity.
A join node is a control node that synchronizes multiple flows. Join nodes have a Boolean value specification using the names of the incoming edges to specify the conditions under which the join will emit a token.
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.
Merge Node (Control Node)
A control node is an abstract activity node that coordinates flows in an activity.
A merge node is a control node that brings together multiple alternate flows. It is not used to synchronize concurrent flows but to accept one among several alternate flows.
Object Flow (Object Flow)
An object flow is an activity edge that can have objects or data passing along it. Object flows have support for multicast/receive, token selection from object nodes, and transformation of tokens.
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.
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.
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 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 input pin is a pin that holds input values to be consumed by an action.
A value pin is an input pin that provides a value by evaluating a value specification.
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.
Control Flow (Control Flow)Object Flow (Object Flow)Control Flow (Control Flow)Object Flow (Object Flow)Activity Diagram (Activity Diagram)
An Activity Diagram is a diagram that shows the decomposition of an activity into actions and the control and dataflow between these behavorial elements.
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).
Element Import (Element Import)
An element import identifies an element in another package, and allows the element to be referenced using its name without a qualifier.
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.
Package Import (Package Import)
A package import is a relationship that allows the use of unqualified names to refer to package members from other namespaces.
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.
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) Control FlowA control flow is an edge that starts an activity node after the previous one is finished.
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.
Accept Call Action or Accept Event Action or Action Input Pin or Activity Final Node or Activity Parameter Node or Add Structural Feature Value Action or Add Variable Value Action or Broadcast Signal Action or Call Behavior Action or Call Operation Action or Central Buffer or Clear Association Action or Clear Structural Feature Action or Clear Variable Action or Conditional Node or Create Link Action or Create Link Object Action or Create Object Action or Data Store Node or Decision Node or Destroy Link Action or Destroy Object Action or Expansion Node or Expansion Region or Flow Final Node or Fork Node or Initial Node or Input Pin or Join Node or Loop Node or Merge Node or Opaque Action or Output Pin or Raise Exception Action or Read Extent Action or Read Is Classified Object Action or Read Link Action or Read Link Object End Action or Read Link Object End Qualifier Action or Read Self Action or Read Structural Feature Action or Read Variable Action or Reclassify Object Action or Reduce Action or Remove Structural Feature Value Action or Remove Variable Value Action or Reply Action or Send Object Action or Send Signal Action or Sequence Node or Start Classifier Behavior Action or Start Object Behavior Action or Structured Activity Node or Structured Activity Node or Test Identity Action or Unmarshall Action or Value Pin or Value Specification Action.
Node from which tokens are taken when they traverse the edge.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
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.
Specification evaluated at runtime to determine if the edge can be traversed.
The minimum number of tokens that must traverse the edge at the same time.
An item of one of the following item kinds:
Accept Call Action (Action)Accept Event Action (Action)Action Input Pin (Pin)Activity Final Node (Control Node)Activity Parameter Node (Object Node)Add Structural Feature Value Action (Action)Add Variable Value Action (Action)Broadcast Signal Action (Action)Call Behavior Action (Action)Call Operation Action (Action)Central Buffer (Object Node)Clear Association Action (Action)Clear Structural Feature Action (Action)Clear Variable Action (Action)Conditional Node (Action)Create Link Action (Action)Create Link Object Action (Action)Create Object Action (Action)Data Store Node (Object Node)Decision Node (Control Node)Destroy Link Action (Action)Destroy Object Action (Action)Expansion Node (Object Node)Expansion Region (Action)Flow Final Node (Control Node)Fork Node (Control Node)Initial Node (Control Node)Input Pin (Pin)Join Node (Control Node)Loop Node (Action)Merge Node (Control Node)Opaque Action (Action)Output Pin (Pin)Raise Exception Action (Action)Read Extent Action (Action)Read Is Classified Object Action (Action)Read Link Action (Action)Read Link Object End Action (Action)Read Link Object End Qualifier Action (Action)Read Self Action (Action)Read Structural Feature Action (Action)Read Variable Action (Action)Reclassify Object Action (Action)Reduce Action (Action)Remove Structural Feature Value Action (Action)Remove Variable Value Action (Action)Reply Action (Action)Send Object Action (Action)Send Signal Action (Action)Sequence Node (Action)Start Classifier Behavior Action (Action)Start Object Behavior Action (Action)Structured Activity Node (Action)Structured Activity Node (Structured Activity Node)Test Identity Action (Action)Unmarshall Action (Action)Value Pin (Pin)Value Specification Action (Action)An item of one of the following item kinds:
Accept Call Action (Action)Accept Event Action (Action)Action Input Pin (Pin)Activity Final Node (Control Node)Activity Parameter Node (Object Node)Add Structural Feature Value Action (Action)Add Variable Value Action (Action)Broadcast Signal Action (Action)Call Behavior Action (Action)Call Operation Action (Action)Central Buffer (Object Node)Clear Association Action (Action)Clear Structural Feature Action (Action)Clear Variable Action (Action)Conditional Node (Action)Create Link Action (Action)Create Link Object Action (Action)Create Object Action (Action)Data Store Node (Object Node)Decision Node (Control Node)Destroy Link Action (Action)Destroy Object Action (Action)Expansion Node (Object Node)Expansion Region (Action)Flow Final Node (Control Node)Fork Node (Control Node)Initial Node (Control Node)Input Pin (Pin)Join Node (Control Node)Loop Node (Action)Merge Node (Control Node)Opaque Action (Action)Output Pin (Pin)Raise Exception Action (Action)Read Extent Action (Action)Read Is Classified Object Action (Action)Read Link Action (Action)Read Link Object End Action (Action)Read Link Object End Qualifier Action (Action)Read Self Action (Action)Read Structural Feature Action (Action)Read Variable Action (Action)Reclassify Object Action (Action)Reduce Action (Action)Remove Structural Feature Value Action (Action)Remove Variable Value Action (Action)Reply Action (Action)Send Object Action (Action)Send Signal Action (Action)Sequence Node (Action)Start Classifier Behavior Action (Action)Start Object Behavior Action (Action)Structured Activity Node (Action)Structured Activity Node (Structured Activity Node)Test Identity Action (Action)Unmarshall Action (Action)Value Pin (Pin)Value Specification Action (Action)Abstraction (Abstraction)Dependency (Dependency)Information Flow (Information Flow)Realization (Realization)Substitution (Substitution)Usage (Usage) Object FlowAn object flow is an activity edge that can have objects or data passing along it. Object flows have support for multicast/receive, token selection from object nodes, and transformation of tokens.
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.
Accept Call Action or Accept Event Action or Action Input Pin or Activity Final Node or Activity Parameter Node or Add Structural Feature Value Action or Add Variable Value Action or Broadcast Signal Action or Call Behavior Action or Call Operation Action or Central Buffer or Clear Association Action or Clear Structural Feature Action or Clear Variable Action or Conditional Node or Create Link Action or Create Link Object Action or Create Object Action or Data Store Node or Decision Node or Destroy Link Action or Destroy Object Action or Expansion Node or Expansion Region or Flow Final Node or Fork Node or Initial Node or Input Pin or Join Node or Loop Node or Merge Node or Opaque Action or Output Pin or Raise Exception Action or Read Extent Action or Read Is Classified Object Action or Read Link Action or Read Link Object End Action or Read Link Object End Qualifier Action or Read Self Action or Read Structural Feature Action or Read Variable Action or Reclassify Object Action or Reduce Action or Remove Structural Feature Value Action or Remove Variable Value Action or Reply Action or Send Object Action or Send Signal Action or Sequence Node or Start Classifier Behavior Action or Start Object Behavior Action or Structured Activity Node or Structured Activity Node or Test Identity Action or Unmarshall Action or Value Pin or Value Specification Action.
Node from which tokens are taken when they traverse the edge.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
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.
Tells whether the objects in the flow are passed by multicasting.
Tells whether the objects in the flow are gathered from respondents to multicasting.
Activity or Interaction or Opaque Behavior or Protocol State Machine or State Machine.
Selects tokens from a source object node.
Activity or Interaction or Opaque Behavior or Protocol State Machine or State Machine.
Changes or replaces data tokens flowing along edge
Specification evaluated at runtime to determine if the edge can be traversed.
The minimum number of tokens that must traverse the edge at the same time.
An item of one of the following item kinds:
Accept Call Action (Action)Accept Event Action (Action)Action Input Pin (Pin)Activity Final Node (Control Node)Activity Parameter Node (Object Node)Add Structural Feature Value Action (Action)Add Variable Value Action (Action)Broadcast Signal Action (Action)Call Behavior Action (Action)Call Operation Action (Action)Central Buffer (Object Node)Clear Association Action (Action)Clear Structural Feature Action (Action)Clear Variable Action (Action)Conditional Node (Action)Create Link Action (Action)Create Link Object Action (Action)Create Object Action (Action)Data Store Node (Object Node)Decision Node (Control Node)Destroy Link Action (Action)Destroy Object Action (Action)Expansion Node (Object Node)Expansion Region (Action)Flow Final Node (Control Node)Fork Node (Control Node)Initial Node (Control Node)Input Pin (Pin)Join Node (Control Node)Loop Node (Action)Merge Node (Control Node)Opaque Action (Action)Output Pin (Pin)Raise Exception Action (Action)Read Extent Action (Action)Read Is Classified Object Action (Action)Read Link Action (Action)Read Link Object End Action (Action)Read Link Object End Qualifier Action (Action)Read Self Action (Action)Read Structural Feature Action (Action)Read Variable Action (Action)Reclassify Object Action (Action)Reduce Action (Action)Remove Structural Feature Value Action (Action)Remove Variable Value Action (Action)Reply Action (Action)Send Object Action (Action)Send Signal Action (Action)Sequence Node (Action)Start Classifier Behavior Action (Action)Start Object Behavior Action (Action)Structured Activity Node (Action)Structured Activity Node (Structured Activity Node)Test Identity Action (Action)Unmarshall Action (Action)Value Pin (Pin)Value Specification Action (Action)An item of one of the following item kinds:
Accept Call Action (Action)Accept Event Action (Action)Action Input Pin (Pin)Activity Final Node (Control Node)Activity Parameter Node (Object Node)Add Structural Feature Value Action (Action)Add Variable Value Action (Action)Broadcast Signal Action (Action)Call Behavior Action (Action)Call Operation Action (Action)Central Buffer (Object Node)Clear Association Action (Action)Clear Structural Feature Action (Action)Clear Variable Action (Action)Conditional Node (Action)Create Link Action (Action)Create Link Object Action (Action)Create Object Action (Action)Data Store Node (Object Node)Decision Node (Control Node)Destroy Link Action (Action)Destroy Object Action (Action)Expansion Node (Object Node)Expansion Region (Action)Flow Final Node (Control Node)Fork Node (Control Node)Initial Node (Control Node)Input Pin (Pin)Join Node (Control Node)Loop Node (Action)Merge Node (Control Node)Opaque Action (Action)Output Pin (Pin)Raise Exception Action (Action)Read Extent Action (Action)Read Is Classified Object Action (Action)Read Link Action (Action)Read Link Object End Action (Action)Read Link Object End Qualifier Action (Action)Read Self Action (Action)Read Structural Feature Action (Action)Read Variable Action (Action)Reclassify Object Action (Action)Reduce Action (Action)Remove Structural Feature Value Action (Action)Remove Variable Value Action (Action)Reply Action (Action)Send Object Action (Action)Send Signal Action (Action)Sequence Node (Action)Start Classifier Behavior Action (Action)Start Object Behavior Action (Action)Structured Activity Node (Action)Structured Activity Node (Structured Activity Node)Test Identity Action (Action)Unmarshall Action (Action)Value Pin (Pin)Value Specification Action (Action)Abstraction (Abstraction)Dependency (Dependency)Information Flow (Information Flow)Realization (Realization)Substitution (Substitution)Usage (Usage) Protocol State MachineA protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
Designates a behavioral feature that the behavior implements.
The behavioral feature must be owned by the classifier that owns the behavior or be inherited by it. The parameters of the behavioral feature and the implementing behavior must match.
If a behavior does not have a specification, it is directly associated with a classifier (i.e., it is the behavior of the classifier as a whole).
If true, the Classifier does not provide a complete declaration and can typically not be instantiated.
An abstract classifier is intended to be used by other classifiers e.g. as the target of general metarelationships or generalization relationships.
Determines whether an object specified by this classifier is active or not. If true, then the owning classifier is referred to as an active classifier. If false, then such a classifier is referred to as a passive classifier.
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.
Tells whether the behavior can be invoked while it is still executing from a previous invocation.
The classifier that is the context for the execution of the behavior.
If the behavior is owned by a BehavioredClassifier, that classifier is the context. Otherwise, the context is the first BehavioredClassifier reached by following the chain of owner relationships.
For example, following this algorithm, the context of an entry action in a state machine is the classifier that owns the state machine. The features of the context classifier as well as the elements visible to the context classifier are visible to the behavior
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Actor (Actor)
An actor specifies a role played by a user or any other system that interacts with the subject.
Association (Association)
An association describes a set of tuples whose values refer to typed instances. An instance of an association is called a link.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
Collaboration (Collaboration)
A collaboration defines a set of co-operating roles used collectively to illustrate a specific functionality.
A collaboration should only show the roles and attributes required to accomplish its defined task or function. Isolating the primary roles is an exercise in simplifying the structure and clarifying the behavior, and also provides for re-use. A collaboration often implements a pattern.
Communication Path (Communication Path)
A communication path is an association between two deployment targets, through which they are able to exchange signals and messages.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Extension (Extension)
An extension is used to indicate that the properties of a metaclass are extended through a stereotype, and gives the ability to flexibly add (and later remove) stereotypes to classes.
Final State (Final State)
A special kind of state signifying that the enclosing region is completed.
If the enclosing region is directly contained in a state machine and all other regions in the state machine also are completed, then it means that the entire state machine is completed.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interface (Interface)
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
Model (Model)
A model captures a view of a physical system. It is an abstraction of the physical system, with a certain purpose.
This purpose determines what is to be included in the model and what is irrelevant. Thus the model completely describes those aspects of the physical system that are relevant to the purpose of the model, at the appropriate level of detail.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Package (Package)
A package is used to group elements, and provides a namespace for the grouped elements.
A package can have one or more profile applications to indicate which profiles have been applied.
Profile (Profile)
A profile defines limited extensions to a reference metamodel with the purpose of adapting the metamodel to a specific platform or domain.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
Protocol Transition (Protocol Transition)
A protocol transition 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.
State (State)
A state models a situation during which some (usually implicit) invariant condition holds.
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.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
Template Parameter (Template Parameter)
A template parameter exposes a parameterable element as a formal template parameter of a template.
Transition (Transition)
A transition is a directed relationship between a source vertex and a target vertex.
It may be part of a compound transition, which takes the state machine from one state configuration to another, representing the complete response of the state machine to an occurrence of an event of a particular type.
Use Case (Use Case)
A use case is the specification of a set of actions performed by a system, which yields an observable result that is, typically, of value for one or more actors or other stakeholders of the system.
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Actor (Actor)
An actor specifies a role played by a user or any other system that interacts with the subject.
Artifact (Artifact)
An artifact is the specification of a physical piece of information that is used or produced by a software development process, or by deployment and operation of a system.
Examples of artifacts include model files, source files, scripts, and binary executable files, a table in a database system, a development deliverable, or a word-processing document, a mail message. An artifact is the source of a deployment to a node.
Association (Association)
An association describes a set of tuples whose values refer to typed instances. An instance of an association is called a link.
Association End (Association End)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An association End is a property that has a reference to an association.
Attribute (Attribute)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An attribute is a property that has no reference to an association.
Choice (Pseudo State)
Choice vertices which, when reached, result in the dynamic evaluation of the guards of the triggers of its outgoing transitions. This realizes a dynamic conditional branch. It allows splitting of transitions into multiple outgoing paths such that the decision on which path to take may be a function of the results of prior actions performed in the same run-tocompletion step. If more than one of the guards evaluates to true, an arbitrary one is selected. If none of the guards evaluates to true, then the model is considered ill-formed. (To avoid this, it is recommended to define one outgoing transition with the predefined else guard for every choice vertex.) Choice vertices should be distinguished from static branch points that are based on junction points.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
Collaboration (Collaboration)
A collaboration defines a set of co-operating roles used collectively to illustrate a specific functionality.
A collaboration should only show the roles and attributes required to accomplish its defined task or function. Isolating the primary roles is an exercise in simplifying the structure and clarifying the behavior, and also provides for re-use. A collaboration often implements a pattern.
Collaboration Use (Collaboration Use)
A collaboration use represents one particular use of a collaboration to explain the relationships between the properties of a classifier.
A collaboration use shows how the pattern described by a collaboration is applied in a given context, by binding specific entities from that context to the roles of the collaboration. Depending on the context, these entities could be structural features of a classifier, instance specifications, or even roles in some containing collaboration. There may be multiple occurrences of a given collaboration within a classifier, each involving a different set of roles and connectors.
A given role or connector may be involved in multiple occurrences of the same or different collaborations. Associated dependencies map features of the collaboration type to features in the classifier. These dependencies indicate which role in the classifier plays which role in the collaboration.
Communication Path (Communication Path)
A communication path is an association between two deployment targets, through which they are able to exchange signals and messages.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Connector (Connector)
Specifies a link that enables communication between two or more instances. This link may be an instance of anassociation, or it may represent the possibility of the instances being able to communicate because their identitiesare known by virtue of being passed in as parameters, held in variables or slots, or because the communicatinginstances are the same instance.
The link may be realized by something as simple as a pointer or by something ascomplex as a network connection. In contrast to associations, which specify links between any instance of theassociated classifiers, connectors specify links between instances playing the connected parts only.
Constraint (Constraint)
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.
Data Type (Data Type)
A data type is a type whose instances are identified only by their value. A data type may contain attributes to support the modeling of structured data types.
Deep History (Pseudo State)
DeepHistory represents the most recent active configuration of the composite state that directly contains this pseudostate; e.g. the state configuration that was active when the composite state was last exited. A composite state can have at most one deep history vertex. At most one transition may originate from the history connector to the default deep history state. This transition is taken in case the composite state had never been active before. Entry actions of states entered on the path to the state represented by a deep history are performed.
Deployment Specification (Deployment Specification)
A deployment specification specifies a set of properties that determine execution parameters of a component artifact that is deployed on a node.
A deployment specification can be aimed at a specific type of container. An artifact that reifies or implements deployment specification properties is a deployment descriptor.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Entry Point (Pseudo State)
An entry point pseudostate is an entry point of a state machine or composite state. In each region of the state machine or composite state it has a single transition to a vertex within the same region.
Enumeration (Enumeration)
An enumeration is a data type whose values are enumerated in the model as enumeration literals.
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Exit Point (Pseudo State)
An exit point pseudostate is an exit point of a state machine or composite state. Entering an exit point within any region of the composite state or state machine referenced by a submachine state implies the exit of this composite state or submachine state and the triggering of the transition that has this exit point as source in the state machine enclosing the submachine or composite state.
Extension (Extension)
An extension is used to indicate that the properties of a metaclass are extended through a stereotype, and gives the ability to flexibly add (and later remove) stereotypes to classes.
Fork (Pseudo State)
Fork vertices serve to split an incoming transition into two or more transitions terminating on orthogonal target vertices (i.e. vertices in different regions of a composite state). The segments outgoing from a fork vertex must not have guards or triggers.
Information Item (Information Item)
An information item is an abstraction of all kinds of information that can be exchanged between objects. It is a kind of
classifier intended for representing information in a very abstract way, one which cannot be instantiated.
Initial (Pseudo State)
An initial pseudostate represents a default vertex that is the source for a single transition to the default state of a composite state. There can be at most one initial vertex in a region. The outgoing transition from the initial vertex may have a behavior, but not a trigger or guard.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interface (Interface)
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
Join (Pseudo State)
Join vertices serve to merge several transitions emanating from source vertices in different orthogonal regions. The transitions entering a join vertex cannot have guards or triggers.
Junction (Pseudo State)
Junction vertices are semantic-free vertices that are used to chain together multiple transitions. They are used to construct compound transition paths between states. For example, a junction can be used to converge multiple incoming transitions into a single outgoing transition representing a shared transition path (this is known as an merge). Conversely, they can be used to split an incoming transition into multiple outgoing transition segments with different guard conditions. This realizes a static conditional branch. (In the latter case, outgoing transitions whose guard conditions evaluate to false are disabled. A predefined guard denoted 'else' may be defined for at most one outgoing transition. This transition is enabled if all the guards labeling the other transitions are false.) Static conditional branches are distinct from dynamic conditional branches that are realized by choice vertices.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Operation (Operation)
An operation is a behavioral feature of a classifier that specifies the name, type, parameters, and constraints for invoking an associated behavior. An operation may invoke both the execution of method behaviors as well as other behavioral responses.
Parameter (Parameter)
A parameter is a specification of an argument used to pass information into or out of an invocation of a behavioral feature. Parameters are allowed to be treated as connectable elements. Parameters have support for streaming, exceptions, and parameter sets.
Port (Port)
A port is a property of a classifier that specifies a distinct interaction point between that classifier and its environment or between the (behavior of the) classifier and its internal parts.
Ports are connected to properties of the classifier by connectors through which requests can be made to invoke the behavioral features of a classifier.
A Port may specify the services a classifier provides (offers) to its environment as well as the services that a classifier expects (requires) of its environment. A port has an associated protocol state machine.
Primitive Type (Primitive Type)
A primitive type defines a predefined data type, without any relevant substructure (i.e., it has no parts in the context of UML). A primitive datatype may have an algebra and operations defined outside of UML, for example, mathematically.
Protocol (Protocol)
Only available together with the Real-Time Extension of RSA.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
Reception (Reception)
A reception is a declaration stating that a classifier is prepared to react to the receipt of a signal. A reception designates a signal and specifies the expected behavioral response.
The details of handling a signal are specified by the behavior associated with the reception or the classifier itself.
Region (Region)
A region is an orthogonal part of either a composite state or a state machine. It contains states and transitions.
Shallow History (Pseudo State)
ShallowHistory represents the most recent active substate of its containing state (but not the substates of that substate). A composite state can have at most one shallow history vertex. A transition coming into the shallow history vertex is equivalent to a transition coming into the most recent active substate of a state. At most one transition may originate from the history connector to the default shallow history state. This transition is taken in case the composite state had never been active before. Entry actions of states entered on the path to the state represented by a shallow history are performed.
Signal (Signal)
A signal is a specification of send request instances communicated between objects. The receiving object handles the received request instances as specified by its receptions. The data carried by a send request (which was passed to it by the send invocation occurrence that caused that request) are represented as attributes of the signal.
A signal is defined independently of the classifiers handling the signal occurrence.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
Template Signature (Template Signature)
A template signature bundles the set of formal template parameters for a templated element.
Terminate (Pseudo State)
Entering a terminate pseudostate implies that the execution of this state machine by means of its context object is terminated. The state machine does not exit any states nor does it perform any exit actions other than those associated with the transition leading to the terminate pseudostate. Entering a terminate pseudostate is equivalent to invoking a DestroyObjectAction.
Trigger (Trigger)
A trigger relates an event to a behavior that may affect an instance of the classifier. A trigger specification may be qualified by the port on which the event occurred.
Use Case (Use Case)
A use case is the specification of a set of actions performed by a system, which yields an observable result that is, typically, of value for one or more actors or other stakeholders of the system.
Class Diagram (Class Diagram)
A Class Diagram is a diagram that shows classes and interfaces and their relationships. However a class diagram may also show packages and all kind of classifier elements.
Component Diagram (Component Diagram)
A Component Diagram is a diagram that shows components, interfaces and artifacts and their relationships. However a component diagram may also show packages and all kind of classifier elements.
Deployment Diagram (Deployment Diagram)
A Deployment Diagram is a diagram that shows nodes and artifacts and their relationships. However a deployment diagram may also show packages and all kind of classifier elements.
Freeform Diagram (Freeform Diagram)
A Free Form diagram is a diagram in which you can make free drawings without the restriction of using UML.
Interaction Overview Diagram (Interaction Overview Diagram)
An Interaction Overview Diagram is a visual representation of a control flow of interaction..
Object Diagram (Object Diagram)
An Object Diagram is a diagram that shows instance specification, links and slots.
Statechart Diagram (Statechart Diagram)
A State Machine Diagram is a diagram that shows a state machine for some element. A state machine is composed of states and transitions. States may be divided into substates.
Structure Diagram (Structure Diagram)
A Structure Diagram is a diagram that shows the static structure of an element.
Use Case Diagram (Use Case Diagram)
A Use-Case Diagram is a diagram that shows actors and use cases and their relationships. However a Use-Case Diagram may also show packages and all kind of classifier elements.
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.
Component Realization (Component Realization)
The realization concept is specialized to (optionally) define the classifiers that realize the contract offered by a component in terms of its provided and required interfaces.
The component forms an abstraction from these various
classifiers.
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).
Element Import (Element Import)
An element import identifies an element in another package, and allows the element to be referenced using its name without a qualifier.
Generalization (Generalization)
A generalization is a taxonomic relationship between a more general classifier and a more specific classifier. Each instance of the specific classifier is also an indirect instance of the general classifier. Thus, the specific classifier inherits the features of the more general classifier.
A generalization relates a specific classifier to a more general classifier, and is owned by the specific classifier.
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.
Interface Realization (Interface Realization)
An interface realization is a specialized realization relationship between a classifier and an interface. This relationship signifies that the realizing classifier conforms to the contract specified by the interface.
Package Import (Package Import)
A package import is a relationship that allows the use of unqualified names to refer to package members from other namespaces.
Protocol Conformance (Protocol Conformance)
Protocol state machines can be redefined into more specific protocol state machines, or into behavioral state machines.
Protocol conformance declares that the specific protocol state machine specifies a protocol that conforms to the general state machine one, or that the specific behavioral state machine abide by the protocol of the general protocol state machine.
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.
Templatebinding (Templatebinding)
A template binding represents a relationship between a templateable element and a template. A template binding specifies the substitutions of actual parameters for the formal parameters of the template.
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.
Action Input Pin (Pin)Activity Parameter Node (Object Node)Association End (Association End)Attribute (Attribute)Central Buffer (Object Node)Data Store Node (Object Node)Expansion Node (Object Node)Input Pin (Pin)Output Pin (Pin)Parameter (Parameter)Port (Port)Value Pin (Pin)Call Behavior Action (Action)Abstraction (Abstraction)Component Realization (Component Realization)Dependency (Dependency)Element Import (Element Import)Generalization (Generalization)Information Flow (Information Flow)Manifestation (Manifestation)Protocol Conformance (Protocol Conformance)Realization (Realization)Substitution (Substitution)Usage (Usage)Action Input Pin (Pin)Activity Parameter Node (Object Node)Central Buffer (Object Node)Data Store Node (Object Node)Expansion Node (Object Node)Input Pin (Pin)Object Flow (Object Flow)Output Pin (Pin)Value Pin (Pin)Object Flow (Object Flow) State MachineState machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
Designates a behavioral feature that the behavior implements.
The behavioral feature must be owned by the classifier that owns the behavior or be inherited by it. The parameters of the behavioral feature and the implementing behavior must match.
If a behavior does not have a specification, it is directly associated with a classifier (i.e., it is the behavior of the classifier as a whole).
If true, the Classifier does not provide a complete declaration and can typically not be instantiated.
An abstract classifier is intended to be used by other classifiers e.g. as the target of general metarelationships or generalization relationships.
Determines whether an object specified by this classifier is active or not. If true, then the owning classifier is referred to as an active classifier. If false, then such a classifier is referred to as a passive classifier.
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.
Tells whether the behavior can be invoked while it is still executing from a previous invocation.
The classifier that is the context for the execution of the behavior.
If the behavior is owned by a BehavioredClassifier, that classifier is the context. Otherwise, the context is the first BehavioredClassifier reached by following the chain of owner relationships.
For example, following this algorithm, the context of an entry action in a state machine is the classifier that owns the state machine. The features of the context classifier as well as the elements visible to the context classifier are visible to the behavior
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Actor (Actor)
An actor specifies a role played by a user or any other system that interacts with the subject.
Association (Association)
An association describes a set of tuples whose values refer to typed instances. An instance of an association is called a link.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
Collaboration (Collaboration)
A collaboration defines a set of co-operating roles used collectively to illustrate a specific functionality.
A collaboration should only show the roles and attributes required to accomplish its defined task or function. Isolating the primary roles is an exercise in simplifying the structure and clarifying the behavior, and also provides for re-use. A collaboration often implements a pattern.
Communication Path (Communication Path)
A communication path is an association between two deployment targets, through which they are able to exchange signals and messages.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Extension (Extension)
An extension is used to indicate that the properties of a metaclass are extended through a stereotype, and gives the ability to flexibly add (and later remove) stereotypes to classes.
Final State (Final State)
A special kind of state signifying that the enclosing region is completed.
If the enclosing region is directly contained in a state machine and all other regions in the state machine also are completed, then it means that the entire state machine is completed.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interface (Interface)
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
Model (Model)
A model captures a view of a physical system. It is an abstraction of the physical system, with a certain purpose.
This purpose determines what is to be included in the model and what is irrelevant. Thus the model completely describes those aspects of the physical system that are relevant to the purpose of the model, at the appropriate level of detail.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Package (Package)
A package is used to group elements, and provides a namespace for the grouped elements.
A package can have one or more profile applications to indicate which profiles have been applied.
Profile (Profile)
A profile defines limited extensions to a reference metamodel with the purpose of adapting the metamodel to a specific platform or domain.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
Protocol Transition (Protocol Transition)
A protocol transition 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.
State (State)
A state models a situation during which some (usually implicit) invariant condition holds.
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.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
Template Parameter (Template Parameter)
A template parameter exposes a parameterable element as a formal template parameter of a template.
Transition (Transition)
A transition is a directed relationship between a source vertex and a target vertex.
It may be part of a compound transition, which takes the state machine from one state configuration to another, representing the complete response of the state machine to an occurrence of an event of a particular type.
Use Case (Use Case)
A use case is the specification of a set of actions performed by a system, which yields an observable result that is, typically, of value for one or more actors or other stakeholders of the system.
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Actor (Actor)
An actor specifies a role played by a user or any other system that interacts with the subject.
Artifact (Artifact)
An artifact is the specification of a physical piece of information that is used or produced by a software development process, or by deployment and operation of a system.
Examples of artifacts include model files, source files, scripts, and binary executable files, a table in a database system, a development deliverable, or a word-processing document, a mail message. An artifact is the source of a deployment to a node.
Association (Association)
An association describes a set of tuples whose values refer to typed instances. An instance of an association is called a link.
Association End (Association End)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An association End is a property that has a reference to an association.
Attribute (Attribute)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An attribute is a property that has no reference to an association.
Choice (Pseudo State)
Choice vertices which, when reached, result in the dynamic evaluation of the guards of the triggers of its outgoing transitions. This realizes a dynamic conditional branch. It allows splitting of transitions into multiple outgoing paths such that the decision on which path to take may be a function of the results of prior actions performed in the same run-tocompletion step. If more than one of the guards evaluates to true, an arbitrary one is selected. If none of the guards evaluates to true, then the model is considered ill-formed. (To avoid this, it is recommended to define one outgoing transition with the predefined else guard for every choice vertex.) Choice vertices should be distinguished from static branch points that are based on junction points.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
Collaboration (Collaboration)
A collaboration defines a set of co-operating roles used collectively to illustrate a specific functionality.
A collaboration should only show the roles and attributes required to accomplish its defined task or function. Isolating the primary roles is an exercise in simplifying the structure and clarifying the behavior, and also provides for re-use. A collaboration often implements a pattern.
Collaboration Use (Collaboration Use)
A collaboration use represents one particular use of a collaboration to explain the relationships between the properties of a classifier.
A collaboration use shows how the pattern described by a collaboration is applied in a given context, by binding specific entities from that context to the roles of the collaboration. Depending on the context, these entities could be structural features of a classifier, instance specifications, or even roles in some containing collaboration. There may be multiple occurrences of a given collaboration within a classifier, each involving a different set of roles and connectors.
A given role or connector may be involved in multiple occurrences of the same or different collaborations. Associated dependencies map features of the collaboration type to features in the classifier. These dependencies indicate which role in the classifier plays which role in the collaboration.
Communication Path (Communication Path)
A communication path is an association between two deployment targets, through which they are able to exchange signals and messages.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Connector (Connector)
Specifies a link that enables communication between two or more instances. This link may be an instance of anassociation, or it may represent the possibility of the instances being able to communicate because their identitiesare known by virtue of being passed in as parameters, held in variables or slots, or because the communicatinginstances are the same instance.
The link may be realized by something as simple as a pointer or by something ascomplex as a network connection. In contrast to associations, which specify links between any instance of theassociated classifiers, connectors specify links between instances playing the connected parts only.
Constraint (Constraint)
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.
Data Type (Data Type)
A data type is a type whose instances are identified only by their value. A data type may contain attributes to support the modeling of structured data types.
Deep History (Pseudo State)
DeepHistory represents the most recent active configuration of the composite state that directly contains this pseudostate; e.g. the state configuration that was active when the composite state was last exited. A composite state can have at most one deep history vertex. At most one transition may originate from the history connector to the default deep history state. This transition is taken in case the composite state had never been active before. Entry actions of states entered on the path to the state represented by a deep history are performed.
Deployment Specification (Deployment Specification)
A deployment specification specifies a set of properties that determine execution parameters of a component artifact that is deployed on a node.
A deployment specification can be aimed at a specific type of container. An artifact that reifies or implements deployment specification properties is a deployment descriptor.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Entry Point (Pseudo State)
An entry point pseudostate is an entry point of a state machine or composite state. In each region of the state machine or composite state it has a single transition to a vertex within the same region.
Enumeration (Enumeration)
An enumeration is a data type whose values are enumerated in the model as enumeration literals.
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Exit Point (Pseudo State)
An exit point pseudostate is an exit point of a state machine or composite state. Entering an exit point within any region of the composite state or state machine referenced by a submachine state implies the exit of this composite state or submachine state and the triggering of the transition that has this exit point as source in the state machine enclosing the submachine or composite state.
Extension (Extension)
An extension is used to indicate that the properties of a metaclass are extended through a stereotype, and gives the ability to flexibly add (and later remove) stereotypes to classes.
Fork (Pseudo State)
Fork vertices serve to split an incoming transition into two or more transitions terminating on orthogonal target vertices (i.e. vertices in different regions of a composite state). The segments outgoing from a fork vertex must not have guards or triggers.
Information Item (Information Item)
An information item is an abstraction of all kinds of information that can be exchanged between objects. It is a kind of
classifier intended for representing information in a very abstract way, one which cannot be instantiated.
Initial (Pseudo State)
An initial pseudostate represents a default vertex that is the source for a single transition to the default state of a composite state. There can be at most one initial vertex in a region. The outgoing transition from the initial vertex may have a behavior, but not a trigger or guard.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interface (Interface)
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
Join (Pseudo State)
Join vertices serve to merge several transitions emanating from source vertices in different orthogonal regions. The transitions entering a join vertex cannot have guards or triggers.
Junction (Pseudo State)
Junction vertices are semantic-free vertices that are used to chain together multiple transitions. They are used to construct compound transition paths between states. For example, a junction can be used to converge multiple incoming transitions into a single outgoing transition representing a shared transition path (this is known as an merge). Conversely, they can be used to split an incoming transition into multiple outgoing transition segments with different guard conditions. This realizes a static conditional branch. (In the latter case, outgoing transitions whose guard conditions evaluate to false are disabled. A predefined guard denoted 'else' may be defined for at most one outgoing transition. This transition is enabled if all the guards labeling the other transitions are false.) Static conditional branches are distinct from dynamic conditional branches that are realized by choice vertices.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Operation (Operation)
An operation is a behavioral feature of a classifier that specifies the name, type, parameters, and constraints for invoking an associated behavior. An operation may invoke both the execution of method behaviors as well as other behavioral responses.
Parameter (Parameter)
A parameter is a specification of an argument used to pass information into or out of an invocation of a behavioral feature. Parameters are allowed to be treated as connectable elements. Parameters have support for streaming, exceptions, and parameter sets.
Port (Port)
A port is a property of a classifier that specifies a distinct interaction point between that classifier and its environment or between the (behavior of the) classifier and its internal parts.
Ports are connected to properties of the classifier by connectors through which requests can be made to invoke the behavioral features of a classifier.
A Port may specify the services a classifier provides (offers) to its environment as well as the services that a classifier expects (requires) of its environment. A port has an associated protocol state machine.
Primitive Type (Primitive Type)
A primitive type defines a predefined data type, without any relevant substructure (i.e., it has no parts in the context of UML). A primitive datatype may have an algebra and operations defined outside of UML, for example, mathematically.
Protocol (Protocol)
Only available together with the Real-Time Extension of RSA.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
Reception (Reception)
A reception is a declaration stating that a classifier is prepared to react to the receipt of a signal. A reception designates a signal and specifies the expected behavioral response.
The details of handling a signal are specified by the behavior associated with the reception or the classifier itself.
Region (Region)
A region is an orthogonal part of either a composite state or a state machine. It contains states and transitions.
Shallow History (Pseudo State)
ShallowHistory represents the most recent active substate of its containing state (but not the substates of that substate). A composite state can have at most one shallow history vertex. A transition coming into the shallow history vertex is equivalent to a transition coming into the most recent active substate of a state. At most one transition may originate from the history connector to the default shallow history state. This transition is taken in case the composite state had never been active before. Entry actions of states entered on the path to the state represented by a shallow history are performed.
Signal (Signal)
A signal is a specification of send request instances communicated between objects. The receiving object handles the received request instances as specified by its receptions. The data carried by a send request (which was passed to it by the send invocation occurrence that caused that request) are represented as attributes of the signal.
A signal is defined independently of the classifiers handling the signal occurrence.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
Template Signature (Template Signature)
A template signature bundles the set of formal template parameters for a templated element.
Terminate (Pseudo State)
Entering a terminate pseudostate implies that the execution of this state machine by means of its context object is terminated. The state machine does not exit any states nor does it perform any exit actions other than those associated with the transition leading to the terminate pseudostate. Entering a terminate pseudostate is equivalent to invoking a DestroyObjectAction.
Trigger (Trigger)
A trigger relates an event to a behavior that may affect an instance of the classifier. A trigger specification may be qualified by the port on which the event occurred.
Use Case (Use Case)
A use case is the specification of a set of actions performed by a system, which yields an observable result that is, typically, of value for one or more actors or other stakeholders of the system.
Class Diagram (Class Diagram)
A Class Diagram is a diagram that shows classes and interfaces and their relationships. However a class diagram may also show packages and all kind of classifier elements.
Component Diagram (Component Diagram)
A Component Diagram is a diagram that shows components, interfaces and artifacts and their relationships. However a component diagram may also show packages and all kind of classifier elements.
Deployment Diagram (Deployment Diagram)
A Deployment Diagram is a diagram that shows nodes and artifacts and their relationships. However a deployment diagram may also show packages and all kind of classifier elements.
Freeform Diagram (Freeform Diagram)
A Free Form diagram is a diagram in which you can make free drawings without the restriction of using UML.
Interaction Overview Diagram (Interaction Overview Diagram)
An Interaction Overview Diagram is a visual representation of a control flow of interaction..
Object Diagram (Object Diagram)
An Object Diagram is a diagram that shows instance specification, links and slots.
Statechart Diagram (Statechart Diagram)
A State Machine Diagram is a diagram that shows a state machine for some element. A state machine is composed of states and transitions. States may be divided into substates.
Structure Diagram (Structure Diagram)
A Structure Diagram is a diagram that shows the static structure of an element.
Use Case Diagram (Use Case Diagram)
A Use-Case Diagram is a diagram that shows actors and use cases and their relationships. However a Use-Case Diagram may also show packages and all kind of classifier elements.
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.
Component Realization (Component Realization)
The realization concept is specialized to (optionally) define the classifiers that realize the contract offered by a component in terms of its provided and required interfaces.
The component forms an abstraction from these various
classifiers.
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).
Element Import (Element Import)
An element import identifies an element in another package, and allows the element to be referenced using its name without a qualifier.
Generalization (Generalization)
A generalization is a taxonomic relationship between a more general classifier and a more specific classifier. Each instance of the specific classifier is also an indirect instance of the general classifier. Thus, the specific classifier inherits the features of the more general classifier.
A generalization relates a specific classifier to a more general classifier, and is owned by the specific classifier.
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.
Interface Realization (Interface Realization)
An interface realization is a specialized realization relationship between a classifier and an interface. This relationship signifies that the realizing classifier conforms to the contract specified by the interface.
Package Import (Package Import)
A package import is a relationship that allows the use of unqualified names to refer to package members from other namespaces.
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.
Templatebinding (Templatebinding)
A template binding represents a relationship between a templateable element and a template. A template binding specifies the substitutions of actual parameters for the formal parameters of the template.
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.
Action Input Pin (Pin)Activity Parameter Node (Object Node)Association End (Association End)Attribute (Attribute)Central Buffer (Object Node)Data Store Node (Object Node)Expansion Node (Object Node)Input Pin (Pin)Output Pin (Pin)Parameter (Parameter)Port (Port)Value Pin (Pin)Call Behavior Action (Action)Abstraction (Abstraction)Component Realization (Component Realization)Dependency (Dependency)Element Import (Element Import)Generalization (Generalization)Information Flow (Information Flow)Manifestation (Manifestation)Realization (Realization)Substitution (Substitution)Usage (Usage)Action Input Pin (Pin)Activity Parameter Node (Object Node)Central Buffer (Object Node)Data Store Node (Object Node)Expansion Node (Object Node)Input Pin (Pin)Object Flow (Object Flow)Output Pin (Pin)Value Pin (Pin)Object Flow (Object Flow) Final StateA special kind of state signifying that the enclosing region is completed.
If the enclosing region is directly contained in a state machine and all other regions in the state machine also are completed, then it means that the entire state machine is completed.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
A composite state is a state that contains at least one region.
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.
An orthogonal composite state contains two or more regions.
A simple state does not have any regions and it does not refer to any submachine state machine.
A state that refers to a state machine.
Region (Region)
A region is an orthogonal part of either a composite state or a state machine. It contains states and transitions.
Choice (Pseudo State)
Choice vertices which, when reached, result in the dynamic evaluation of the guards of the triggers of its outgoing transitions. This realizes a dynamic conditional branch. It allows splitting of transitions into multiple outgoing paths such that the decision on which path to take may be a function of the results of prior actions performed in the same run-tocompletion step. If more than one of the guards evaluates to true, an arbitrary one is selected. If none of the guards evaluates to true, then the model is considered ill-formed. (To avoid this, it is recommended to define one outgoing transition with the predefined else guard for every choice vertex.) Choice vertices should be distinguished from static branch points that are based on junction points.
Connection Point Reference (Connection Point Reference)
A connection point reference represents a usage (as part of a submachine state) of an entry/exit point defined in the statemachine reference by the submachine state.
Constraint (Constraint)
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.
Deep History (Pseudo State)
DeepHistory represents the most recent active configuration of the composite state that directly contains this pseudostate; e.g. the state configuration that was active when the composite state was last exited. A composite state can have at most one deep history vertex. At most one transition may originate from the history connector to the default deep history state. This transition is taken in case the composite state had never been active before. Entry actions of states entered on the path to the state represented by a deep history are performed.
Entry Point (Pseudo State)
An entry point pseudostate is an entry point of a state machine or composite state. In each region of the state machine or composite state it has a single transition to a vertex within the same region.
Exit Point (Pseudo State)
An exit point pseudostate is an exit point of a state machine or composite state. Entering an exit point within any region of the composite state or state machine referenced by a submachine state implies the exit of this composite state or submachine state and the triggering of the transition that has this exit point as source in the state machine enclosing the submachine or composite state.
Fork (Pseudo State)
Fork vertices serve to split an incoming transition into two or more transitions terminating on orthogonal target vertices (i.e. vertices in different regions of a composite state). The segments outgoing from a fork vertex must not have guards or triggers.
Initial (Pseudo State)
An initial pseudostate represents a default vertex that is the source for a single transition to the default state of a composite state. There can be at most one initial vertex in a region. The outgoing transition from the initial vertex may have a behavior, but not a trigger or guard.
Join (Pseudo State)
Join vertices serve to merge several transitions emanating from source vertices in different orthogonal regions. The transitions entering a join vertex cannot have guards or triggers.
Junction (Pseudo State)
Junction vertices are semantic-free vertices that are used to chain together multiple transitions. They are used to construct compound transition paths between states. For example, a junction can be used to converge multiple incoming transitions into a single outgoing transition representing a shared transition path (this is known as an merge). Conversely, they can be used to split an incoming transition into multiple outgoing transition segments with different guard conditions. This realizes a static conditional branch. (In the latter case, outgoing transitions whose guard conditions evaluate to false are disabled. A predefined guard denoted 'else' may be defined for at most one outgoing transition. This transition is enabled if all the guards labeling the other transitions are false.) Static conditional branches are distinct from dynamic conditional branches that are realized by choice vertices.
Region (Region)
A region is an orthogonal part of either a composite state or a state machine. It contains states and transitions.
Shallow History (Pseudo State)
ShallowHistory represents the most recent active substate of its containing state (but not the substates of that substate). A composite state can have at most one shallow history vertex. A transition coming into the shallow history vertex is equivalent to a transition coming into the most recent active substate of a state. At most one transition may originate from the history connector to the default shallow history state. This transition is taken in case the composite state had never been active before. Entry actions of states entered on the path to the state represented by a shallow history are performed.
Terminate (Pseudo State)
Entering a terminate pseudostate implies that the execution of this state machine by means of its context object is terminated. The state machine does not exit any states nor does it perform any exit actions other than those associated with the transition leading to the terminate pseudostate. Entering a terminate pseudostate is equivalent to invoking a DestroyObjectAction.
Trigger (Trigger)
A trigger relates an event to a behavior that may affect an instance of the classifier. A trigger specification may be qualified by the port on which the event occurred.
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Protocol Transition (Protocol Transition)Transition (Transition)Protocol Transition (Protocol Transition)Transition (Transition)Statechart Diagram (Statechart Diagram)
A State Machine Diagram is a diagram that shows a state machine for some element. A state machine is composed of states and transitions. States may be divided into substates.
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).
Element Import (Element Import)
An element import identifies an element in another package, and allows the element to be referenced using its name without a qualifier.
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.
Package Import (Package Import)
A package import is a relationship that allows the use of unqualified names to refer to package members from other namespaces.
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.
Abstraction (Abstraction)Dependency (Dependency)Information Flow (Information Flow)Protocol Transition (Protocol Transition)Realization (Realization)Substitution (Substitution)Transition (Transition)Usage (Usage)Protocol Transition (Protocol Transition)Transition (Transition) Entry Point (Pseudo State)An entry point pseudostate is an entry point of a state machine or composite state. In each region of the state machine or composite state it has a single transition to a vertex within the same region.
Determines the precise type of the Pseudostate.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
An element of one of the following kinds:
Final State (Final State)
A special kind of state signifying that the enclosing region is completed.
If the enclosing region is directly contained in a state machine and all other regions in the state machine also are completed, then it means that the entire state machine is completed.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
Region (Region)
A region is an orthogonal part of either a composite state or a state machine. It contains states and transitions.
State (State)
A state models a situation during which some (usually implicit) invariant condition holds.
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.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Protocol Transition (Protocol Transition)Transition (Transition)Protocol Transition (Protocol Transition)Transition (Transition)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.
Abstraction (Abstraction)Dependency (Dependency)Information Flow (Information Flow)Protocol Transition (Protocol Transition)Realization (Realization)Substitution (Substitution)Transition (Transition)Usage (Usage)Protocol Transition (Protocol Transition)Transition (Transition) Terminate (Pseudo State)Entering a terminate pseudostate implies that the execution of this state machine by means of its context object is terminated. The state machine does not exit any states nor does it perform any exit actions other than those associated with the transition leading to the terminate pseudostate. Entering a terminate pseudostate is equivalent to invoking a DestroyObjectAction.
Determines the precise type of the Pseudostate.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
An element of one of the following kinds:
Final State (Final State)
A special kind of state signifying that the enclosing region is completed.
If the enclosing region is directly contained in a state machine and all other regions in the state machine also are completed, then it means that the entire state machine is completed.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
Region (Region)
A region is an orthogonal part of either a composite state or a state machine. It contains states and transitions.
State (State)
A state models a situation during which some (usually implicit) invariant condition holds.
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.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Protocol Transition (Protocol Transition)Transition (Transition)Protocol Transition (Protocol Transition)Transition (Transition)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.
Abstraction (Abstraction)Dependency (Dependency)Information Flow (Information Flow)Protocol Transition (Protocol Transition)Realization (Realization)Substitution (Substitution)Transition (Transition)Usage (Usage)Protocol Transition (Protocol Transition)Transition (Transition) Exit Point (Pseudo State)An exit point pseudostate is an exit point of a state machine or composite state. Entering an exit point within any region of the composite state or state machine referenced by a submachine state implies the exit of this composite state or submachine state and the triggering of the transition that has this exit point as source in the state machine enclosing the submachine or composite state.
Determines the precise type of the Pseudostate.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
An element of one of the following kinds:
Final State (Final State)
A special kind of state signifying that the enclosing region is completed.
If the enclosing region is directly contained in a state machine and all other regions in the state machine also are completed, then it means that the entire state machine is completed.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
Region (Region)
A region is an orthogonal part of either a composite state or a state machine. It contains states and transitions.
State (State)
A state models a situation during which some (usually implicit) invariant condition holds.
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.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Protocol Transition (Protocol Transition)Transition (Transition)Protocol Transition (Protocol Transition)Transition (Transition)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.
Abstraction (Abstraction)Dependency (Dependency)Information Flow (Information Flow)Protocol Transition (Protocol Transition)Realization (Realization)Substitution (Substitution)Transition (Transition)Usage (Usage)Protocol Transition (Protocol Transition)Transition (Transition) Join (Pseudo State)Join vertices serve to merge several transitions emanating from source vertices in different orthogonal regions. The transitions entering a join vertex cannot have guards or triggers.
Determines the precise type of the Pseudostate.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
An element of one of the following kinds:
Final State (Final State)
A special kind of state signifying that the enclosing region is completed.
If the enclosing region is directly contained in a state machine and all other regions in the state machine also are completed, then it means that the entire state machine is completed.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
Region (Region)
A region is an orthogonal part of either a composite state or a state machine. It contains states and transitions.
State (State)
A state models a situation during which some (usually implicit) invariant condition holds.
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.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Protocol Transition (Protocol Transition)Transition (Transition)Protocol Transition (Protocol Transition)Transition (Transition)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.
Abstraction (Abstraction)Dependency (Dependency)Information Flow (Information Flow)Protocol Transition (Protocol Transition)Realization (Realization)Substitution (Substitution)Transition (Transition)Usage (Usage)Protocol Transition (Protocol Transition)Transition (Transition) Fork (Pseudo State)Fork vertices serve to split an incoming transition into two or more transitions terminating on orthogonal target vertices (i.e. vertices in different regions of a composite state). The segments outgoing from a fork vertex must not have guards or triggers.
Determines the precise type of the Pseudostate.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
An element of one of the following kinds:
Final State (Final State)
A special kind of state signifying that the enclosing region is completed.
If the enclosing region is directly contained in a state machine and all other regions in the state machine also are completed, then it means that the entire state machine is completed.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
Region (Region)
A region is an orthogonal part of either a composite state or a state machine. It contains states and transitions.
State (State)
A state models a situation during which some (usually implicit) invariant condition holds.
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.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Protocol Transition (Protocol Transition)Transition (Transition)Protocol Transition (Protocol Transition)Transition (Transition)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.
Abstraction (Abstraction)Dependency (Dependency)Information Flow (Information Flow)Protocol Transition (Protocol Transition)Realization (Realization)Substitution (Substitution)Transition (Transition)Usage (Usage)Protocol Transition (Protocol Transition)Transition (Transition) Choice (Pseudo State)Choice vertices which, when reached, result in the dynamic evaluation of the guards of the triggers of its outgoing transitions. This realizes a dynamic conditional branch. It allows splitting of transitions into multiple outgoing paths such that the decision on which path to take may be a function of the results of prior actions performed in the same run-tocompletion step. If more than one of the guards evaluates to true, an arbitrary one is selected. If none of the guards evaluates to true, then the model is considered ill-formed. (To avoid this, it is recommended to define one outgoing transition with the predefined else guard for every choice vertex.) Choice vertices should be distinguished from static branch points that are based on junction points.
Determines the precise type of the Pseudostate.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
An element of one of the following kinds:
Final State (Final State)
A special kind of state signifying that the enclosing region is completed.
If the enclosing region is directly contained in a state machine and all other regions in the state machine also are completed, then it means that the entire state machine is completed.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
Region (Region)
A region is an orthogonal part of either a composite state or a state machine. It contains states and transitions.
State (State)
A state models a situation during which some (usually implicit) invariant condition holds.
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.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Protocol Transition (Protocol Transition)Transition (Transition)Protocol Transition (Protocol Transition)Transition (Transition)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.
Abstraction (Abstraction)Dependency (Dependency)Information Flow (Information Flow)Protocol Transition (Protocol Transition)Realization (Realization)Substitution (Substitution)Transition (Transition)Usage (Usage)Protocol Transition (Protocol Transition)Transition (Transition) Initial (Pseudo State)An initial pseudostate represents a default vertex that is the source for a single transition to the default state of a composite state. There can be at most one initial vertex in a region. The outgoing transition from the initial vertex may have a behavior, but not a trigger or guard.
Determines the precise type of the Pseudostate.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
An element of one of the following kinds:
Final State (Final State)
A special kind of state signifying that the enclosing region is completed.
If the enclosing region is directly contained in a state machine and all other regions in the state machine also are completed, then it means that the entire state machine is completed.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
Region (Region)
A region is an orthogonal part of either a composite state or a state machine. It contains states and transitions.
State (State)
A state models a situation during which some (usually implicit) invariant condition holds.
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.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Protocol Transition (Protocol Transition)Transition (Transition)Protocol Transition (Protocol Transition)Transition (Transition)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.
Abstraction (Abstraction)Dependency (Dependency)Information Flow (Information Flow)Protocol Transition (Protocol Transition)Realization (Realization)Substitution (Substitution)Transition (Transition)Usage (Usage)Protocol Transition (Protocol Transition)Transition (Transition) Shallow History (Pseudo State)ShallowHistory represents the most recent active substate of its containing state (but not the substates of that substate). A composite state can have at most one shallow history vertex. A transition coming into the shallow history vertex is equivalent to a transition coming into the most recent active substate of a state. At most one transition may originate from the history connector to the default shallow history state. This transition is taken in case the composite state had never been active before. Entry actions of states entered on the path to the state represented by a shallow history are performed.
Determines the precise type of the Pseudostate.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
An element of one of the following kinds:
Final State (Final State)
A special kind of state signifying that the enclosing region is completed.
If the enclosing region is directly contained in a state machine and all other regions in the state machine also are completed, then it means that the entire state machine is completed.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
Region (Region)
A region is an orthogonal part of either a composite state or a state machine. It contains states and transitions.
State (State)
A state models a situation during which some (usually implicit) invariant condition holds.
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.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Protocol Transition (Protocol Transition)Transition (Transition)Protocol Transition (Protocol Transition)Transition (Transition)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.
Abstraction (Abstraction)Dependency (Dependency)Information Flow (Information Flow)Protocol Transition (Protocol Transition)Realization (Realization)Substitution (Substitution)Transition (Transition)Usage (Usage)Protocol Transition (Protocol Transition)Transition (Transition) Deep History (Pseudo State)DeepHistory represents the most recent active configuration of the composite state that directly contains this pseudostate; e.g. the state configuration that was active when the composite state was last exited. A composite state can have at most one deep history vertex. At most one transition may originate from the history connector to the default deep history state. This transition is taken in case the composite state had never been active before. Entry actions of states entered on the path to the state represented by a deep history are performed.
Determines the precise type of the Pseudostate.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
An element of one of the following kinds:
Final State (Final State)
A special kind of state signifying that the enclosing region is completed.
If the enclosing region is directly contained in a state machine and all other regions in the state machine also are completed, then it means that the entire state machine is completed.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
Region (Region)
A region is an orthogonal part of either a composite state or a state machine. It contains states and transitions.
State (State)
A state models a situation during which some (usually implicit) invariant condition holds.
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.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Protocol Transition (Protocol Transition)Transition (Transition)Protocol Transition (Protocol Transition)Transition (Transition)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.
Abstraction (Abstraction)Dependency (Dependency)Information Flow (Information Flow)Protocol Transition (Protocol Transition)Realization (Realization)Substitution (Substitution)Transition (Transition)Usage (Usage)Protocol Transition (Protocol Transition)Transition (Transition) Junction (Pseudo State)Junction vertices are semantic-free vertices that are used to chain together multiple transitions. They are used to construct compound transition paths between states. For example, a junction can be used to converge multiple incoming transitions into a single outgoing transition representing a shared transition path (this is known as an merge). Conversely, they can be used to split an incoming transition into multiple outgoing transition segments with different guard conditions. This realizes a static conditional branch. (In the latter case, outgoing transitions whose guard conditions evaluate to false are disabled. A predefined guard denoted 'else' may be defined for at most one outgoing transition. This transition is enabled if all the guards labeling the other transitions are false.) Static conditional branches are distinct from dynamic conditional branches that are realized by choice vertices.
Determines the precise type of the Pseudostate.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
An element of one of the following kinds:
Final State (Final State)
A special kind of state signifying that the enclosing region is completed.
If the enclosing region is directly contained in a state machine and all other regions in the state machine also are completed, then it means that the entire state machine is completed.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
Region (Region)
A region is an orthogonal part of either a composite state or a state machine. It contains states and transitions.
State (State)
A state models a situation during which some (usually implicit) invariant condition holds.
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.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Protocol Transition (Protocol Transition)Transition (Transition)Protocol Transition (Protocol Transition)Transition (Transition)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.
Abstraction (Abstraction)Dependency (Dependency)Information Flow (Information Flow)Protocol Transition (Protocol Transition)Realization (Realization)Substitution (Substitution)Transition (Transition)Usage (Usage)Protocol Transition (Protocol Transition)Transition (Transition) StateA state models a situation during which some (usually implicit) invariant condition holds.
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.
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
A composite state is a state that contains at least one region.
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.
An orthogonal composite state contains two or more regions.
A simple state does not have any regions and it does not refer to any submachine state machine.
A state that refers to a state machine.
Region (Region)
A region is an orthogonal part of either a composite state or a state machine. It contains states and transitions.
Choice (Pseudo State)
Choice vertices which, when reached, result in the dynamic evaluation of the guards of the triggers of its outgoing transitions. This realizes a dynamic conditional branch. It allows splitting of transitions into multiple outgoing paths such that the decision on which path to take may be a function of the results of prior actions performed in the same run-tocompletion step. If more than one of the guards evaluates to true, an arbitrary one is selected. If none of the guards evaluates to true, then the model is considered ill-formed. (To avoid this, it is recommended to define one outgoing transition with the predefined else guard for every choice vertex.) Choice vertices should be distinguished from static branch points that are based on junction points.
Connection Point Reference (Connection Point Reference)
A connection point reference represents a usage (as part of a submachine state) of an entry/exit point defined in the statemachine reference by the submachine state.
Constraint (Constraint)
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.
Deep History (Pseudo State)
DeepHistory represents the most recent active configuration of the composite state that directly contains this pseudostate; e.g. the state configuration that was active when the composite state was last exited. A composite state can have at most one deep history vertex. At most one transition may originate from the history connector to the default deep history state. This transition is taken in case the composite state had never been active before. Entry actions of states entered on the path to the state represented by a deep history are performed.
Entry Point (Pseudo State)
An entry point pseudostate is an entry point of a state machine or composite state. In each region of the state machine or composite state it has a single transition to a vertex within the same region.
Exit Point (Pseudo State)
An exit point pseudostate is an exit point of a state machine or composite state. Entering an exit point within any region of the composite state or state machine referenced by a submachine state implies the exit of this composite state or submachine state and the triggering of the transition that has this exit point as source in the state machine enclosing the submachine or composite state.
Fork (Pseudo State)
Fork vertices serve to split an incoming transition into two or more transitions terminating on orthogonal target vertices (i.e. vertices in different regions of a composite state). The segments outgoing from a fork vertex must not have guards or triggers.
Initial (Pseudo State)
An initial pseudostate represents a default vertex that is the source for a single transition to the default state of a composite state. There can be at most one initial vertex in a region. The outgoing transition from the initial vertex may have a behavior, but not a trigger or guard.
Join (Pseudo State)
Join vertices serve to merge several transitions emanating from source vertices in different orthogonal regions. The transitions entering a join vertex cannot have guards or triggers.
Junction (Pseudo State)
Junction vertices are semantic-free vertices that are used to chain together multiple transitions. They are used to construct compound transition paths between states. For example, a junction can be used to converge multiple incoming transitions into a single outgoing transition representing a shared transition path (this is known as an merge). Conversely, they can be used to split an incoming transition into multiple outgoing transition segments with different guard conditions. This realizes a static conditional branch. (In the latter case, outgoing transitions whose guard conditions evaluate to false are disabled. A predefined guard denoted 'else' may be defined for at most one outgoing transition. This transition is enabled if all the guards labeling the other transitions are false.) Static conditional branches are distinct from dynamic conditional branches that are realized by choice vertices.
Region (Region)
A region is an orthogonal part of either a composite state or a state machine. It contains states and transitions.
Shallow History (Pseudo State)
ShallowHistory represents the most recent active substate of its containing state (but not the substates of that substate). A composite state can have at most one shallow history vertex. A transition coming into the shallow history vertex is equivalent to a transition coming into the most recent active substate of a state. At most one transition may originate from the history connector to the default shallow history state. This transition is taken in case the composite state had never been active before. Entry actions of states entered on the path to the state represented by a shallow history are performed.
Terminate (Pseudo State)
Entering a terminate pseudostate implies that the execution of this state machine by means of its context object is terminated. The state machine does not exit any states nor does it perform any exit actions other than those associated with the transition leading to the terminate pseudostate. Entering a terminate pseudostate is equivalent to invoking a DestroyObjectAction.
Trigger (Trigger)
A trigger relates an event to a behavior that may affect an instance of the classifier. A trigger specification may be qualified by the port on which the event occurred.
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Protocol Transition (Protocol Transition)Transition (Transition)Protocol Transition (Protocol Transition)Transition (Transition)Statechart Diagram (Statechart Diagram)
A State Machine Diagram is a diagram that shows a state machine for some element. A state machine is composed of states and transitions. States may be divided into substates.
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).
Element Import (Element Import)
An element import identifies an element in another package, and allows the element to be referenced using its name without a qualifier.
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.
Package Import (Package Import)
A package import is a relationship that allows the use of unqualified names to refer to package members from other namespaces.
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.
Abstraction (Abstraction)Dependency (Dependency)Information Flow (Information Flow)Protocol Transition (Protocol Transition)Realization (Realization)Substitution (Substitution)Transition (Transition)Usage (Usage)Protocol Transition (Protocol Transition)Transition (Transition) TransitionA transition is a directed relationship between a source vertex and a target vertex.
It may be part of a compound transition, which takes the state machine from one state configuration to another, representing the complete response of the state machine to an occurrence of an event of a particular type.
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.
Choice or Connection Point Reference or Deep History or Entry Point or Exit Point or Final State or Fork or Initial or Join or Junction or Shallow History or State or Terminate.
Designates the originating vertex (state or pseudostate) of the transition.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
Indicates the precise type of the transition.
An item of one of the following item kinds:
Choice (Pseudo State)Connection Point Reference (Connection Point Reference)Deep History (Pseudo State)Entry Point (Pseudo State)Exit Point (Pseudo State)Final State (Final State)Fork (Pseudo State)Initial (Pseudo State)Join (Pseudo State)Junction (Pseudo State)Shallow History (Pseudo State)State (State)Terminate (Pseudo State)An item of one of the following item kinds:
Choice (Pseudo State)Connection Point Reference (Connection Point Reference)Deep History (Pseudo State)Entry Point (Pseudo State)Exit Point (Pseudo State)Final State (Final State)Fork (Pseudo State)Initial (Pseudo State)Join (Pseudo State)Junction (Pseudo State)Shallow History (Pseudo State)State (State)Terminate (Pseudo State)Abstraction (Abstraction)Dependency (Dependency)Information Flow (Information Flow)Realization (Realization)Substitution (Substitution)Usage (Usage) Instance SpecificationAn instance specification is a model element that represents an instance in a modeled system.
An instance specification has the capability of being a deployment target in a deployment relationship, in the case that it is an instance of a node.
It is also has the capability of being a deployed artifact, if it is an instance of an artifact.
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.
The classifier or classifiers of the represented instance. If multiple classifiers are specified, the instance is classified by all of them.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
An element of one of the following kinds:
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Model (Model)
A model captures a view of a physical system. It is an abstraction of the physical system, with a certain purpose.
This purpose determines what is to be included in the model and what is irrelevant. Thus the model completely describes those aspects of the physical system that are relevant to the purpose of the model, at the appropriate level of detail.
Package (Package)
A package is used to group elements, and provides a namespace for the grouped elements.
A package can have one or more profile applications to indicate which profiles have been applied.
Profile (Profile)
A profile defines limited extensions to a reference metamodel with the purpose of adapting the metamodel to a specific platform or domain.
Template Parameter (Template Parameter)
A template parameter exposes a parameterable element as a formal template parameter of a template.
Slot (Slot)
A slot specifies that an entity modeled by an instance specification has a value or values for a specific structural feature.
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.
Abstraction (Abstraction)Dependency (Dependency)Deployment (Deployment)Element Import (Element Import)Information Flow (Information Flow)Manifestation (Manifestation)Realization (Realization)Substitution (Substitution)Usage (Usage) DependencyA 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).
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.
Determines where the item appears within different Namespaces within the overall model, and its accessibility.
An element of one of the following kinds:
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.
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.
Action Input 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 input pin is a pin that holds input values to be consumed by an action.
An action input pin is a kind of pin that executes an action to determine the values to input to another.
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Activity Final Node (Control Node)
A control node is an abstract activity node that coordinates flows in an activity.
A final node is an abstract control node at which a flow in an activity stops.
An activity final node is a final node that stops all flows in an activity.
Activity Parameter Node (Object Node)
An object node is an abstract activity node that is part of defining object flow in an activity. Object nodes have support for token selection, limitation on the number of tokens, specifying the state required for tokens, and carrying control values.
An activity parameter node is an object node for inputs and outputs to activities.
Activity Partition (Activity Partition)
An activity partition is a kind of activity group for identifying actions that have some characteristic in common.
Actor (Actor)
An actor specifies a role played by a user or any other system that interacts with the subject.
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.
Artifact (Artifact)
An artifact is the specification of a physical piece of information that is used or produced by a software development process, or by deployment and operation of a system.
Examples of artifacts include model files, source files, scripts, and binary executable files, a table in a database system, a development deliverable, or a word-processing document, a mail message. An artifact is the source of a deployment to a node.
Association (Association)
An association describes a set of tuples whose values refer to typed instances. An instance of an association is called a link.
Association End (Association End)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An association End is a property that has a reference to an association.
Attribute (Attribute)
A property is a structural feature of a classifier that characterizes instances of the classifier.
A property may represents an attribute and might also represent an association end. It relates an instance of the class to a value or set of values of the type of the attribute.
A property related by memberEnd or its specializations to an association represents an end of the association. The type of the property is the type of the end of the association.
An attribute is a property that has no reference to an association.
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 Event (Call Event)
A call event models the receipt by an object of a message invoking a call of an operation.
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.
Central Buffer (Object Node)
An object node is an abstract activity node that is part of defining object flow in an activity. Object nodes have support for token selection, limitation on the number of tokens, specifying the state required for tokens, and carrying control values.
A central buffer node is an object node for managing flows from multiple sources and destinations.
Choice (Pseudo State)
Choice vertices which, when reached, result in the dynamic evaluation of the guards of the triggers of its outgoing transitions. This realizes a dynamic conditional branch. It allows splitting of transitions into multiple outgoing paths such that the decision on which path to take may be a function of the results of prior actions performed in the same run-tocompletion step. If more than one of the guards evaluates to true, an arbitrary one is selected. If none of the guards evaluates to true, then the model is considered ill-formed. (To avoid this, it is recommended to define one outgoing transition with the predefined else guard for every choice vertex.) Choice vertices should be distinguished from static branch points that are based on junction points.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
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.
Collaboration (Collaboration)
A collaboration defines a set of co-operating roles used collectively to illustrate a specific functionality.
A collaboration should only show the roles and attributes required to accomplish its defined task or function. Isolating the primary roles is an exercise in simplifying the structure and clarifying the behavior, and also provides for re-use. A collaboration often implements a pattern.
Collaboration Use (Collaboration Use)
A collaboration use represents one particular use of a collaboration to explain the relationships between the properties of a classifier.
A collaboration use shows how the pattern described by a collaboration is applied in a given context, by binding specific entities from that context to the roles of the collaboration. Depending on the context, these entities could be structural features of a classifier, instance specifications, or even roles in some containing collaboration. There may be multiple occurrences of a given collaboration within a classifier, each involving a different set of roles and connectors.
A given role or connector may be involved in multiple occurrences of the same or different collaborations. Associated dependencies map features of the collaboration type to features in the classifier. These dependencies indicate which role in the classifier plays which role in the collaboration.
Combined Fragment (Combined Fragment)
A combined fragment defines an expression of interaction fragments. A combined fragment is defined by an interaction operator and corresponding interaction operands. Through the use of combined fragments the user will be able to describe a number of traces in a compact and concise manner.
Communication Path (Communication Path)
A communication path is an association between two deployment targets, through which they are able to exchange signals and messages.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Component Realization (Component Realization)
The realization concept is specialized to (optionally) define the classifiers that realize the contract offered by a component in terms of its provided and required interfaces.
The component forms an abstraction from these various
classifiers.
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.
Connection Point Reference (Connection Point Reference)
A connection point reference represents a usage (as part of a submachine state) of an entry/exit point defined in the statemachine reference by the submachine state.
Connector (Connector)
Specifies a link that enables communication between two or more instances. This link may be an instance of anassociation, or it may represent the possibility of the instances being able to communicate because their identitiesare known by virtue of being passed in as parameters, held in variables or slots, or because the communicatinginstances are the same instance.
The link may be realized by something as simple as a pointer or by something ascomplex as a network connection. In contrast to associations, which specify links between any instance of theassociated classifiers, connectors specify links between instances playing the connected parts only.
Control Flow (Control Flow)
A control flow is an edge that starts an activity node after the previous one is finished.
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.
Data Store Node (Object Node)
An object node is an abstract activity node that is part of defining object flow in an activity. Object nodes have support for token selection, limitation on the number of tokens, specifying the state required for tokens, and carrying control values.
A central buffer node is an object node for managing flows from multiple sources and destinations.
A data store node is a central buffer node for non-transient information.
Data Type (Data Type)
A data type is a type whose instances are identified only by their value. A data type may contain attributes to support the modeling of structured data types.
Decision Node (Control Node)
A control node is an abstract activity node that coordinates flows in an activity.
A decision node is a control node that chooses between outgoing flows.
Deep History (Pseudo State)
DeepHistory represents the most recent active configuration of the composite state that directly contains this pseudostate; e.g. the state configuration that was active when the composite state was last exited. A composite state can have at most one deep history vertex. At most one transition may originate from the history connector to the default deep history state. This transition is taken in case the composite state had never been active before. Entry actions of states entered on the path to the state represented by a deep history are performed.
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).
Deployment (Deployment)
A deployment is the allocation of an artifact or artifact instance to a deployment target. A component deployment is the deployment of one or more artifacts or artifact instances to a deployment target, optionally parameterized by a deployment specification. Examples are executables and configuration files.
Deployment Specification (Deployment Specification)
A deployment specification specifies a set of properties that determine execution parameters of a component artifact that is deployed on a node.
A deployment specification can be aimed at a specific type of container. An artifact that reifies or implements deployment specification properties is a deployment descriptor.
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.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Entry Point (Pseudo State)
An entry point pseudostate is an entry point of a state machine or composite state. In each region of the state machine or composite state it has a single transition to a vertex within the same region.
Enumeration (Enumeration)
An enumeration is a data type whose values are enumerated in the model as enumeration literals.
Enumeration Literal (Enumeration Literal)
An enumeration literal is a user-defined data value for an enumeration.
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Exit Point (Pseudo State)
An exit point pseudostate is an exit point of a state machine or composite state. Entering an exit point within any region of the composite state or state machine referenced by a submachine state implies the exit of this composite state or submachine state and the triggering of the transition that has this exit point as source in the state machine enclosing the submachine or composite state.
Expansion Node (Object Node)
An object node is an abstract activity node that is part of defining object flow in an activity. Object nodes have support for token selection, limitation on the number of tokens, specifying the state required for tokens, and carrying control values.
An expansion node is an object node used to indicate a flow across the boundary of an expansion region. A flow into a region contains a collection that is broken into its individual elements inside the region, which is executed once per element. A flow out of a region combines individual elements into a collection for use outside the region.
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.
Extend (Extend)
A relationship from an extending use case to an extended use case that specifies how and when the behavior defined in the extending use case can be inserted into the behavior defined in the extended use case.
Extension (Extension)
An extension is used to indicate that the properties of a metaclass are extended through a stereotype, and gives the ability to flexibly add (and later remove) stereotypes to classes.
Extension Point (Extension Point)
An extension point identifies a point in the behavior of a use case where that behavior can be extended by the behavior of some other (extending) use case, as specified by an extend relationship.
Final State (Final State)
A special kind of state signifying that the enclosing region is completed.
If the enclosing region is directly contained in a state machine and all other regions in the state machine also are completed, then it means that the entire state machine is completed.
Flow Final Node (Control Node)
A control node is an abstract activity node that coordinates flows in an activity.
A final node is an abstract control node at which a flow in an activity stops.
A flow final node is a final node that terminates a flow.
Fork (Pseudo State)
Fork vertices serve to split an incoming transition into two or more transitions terminating on orthogonal target vertices (i.e. vertices in different regions of a composite state). The segments outgoing from a fork vertex must not have guards or triggers.
Fork Node (Control Node)
A control node is an abstract activity node that coordinates flows in an activity.
A fork node is a control node that splits a flow into multiple concurrent flows.
Gate (Gate)
A gate is a connection point for relating a message outside an interaction fragment with a message inside the interaction fragment.
Guard (Guard)
A guard is a condition or restriction expressed in natural language text or in a machine readable language that must be fulfilled for a transition to become possible.
Include (Include)
An include relationship defines that a use case contains the behavior defined in another use case.
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.
Information Item (Information Item)
An information item is an abstraction of all kinds of information that can be exchanged between objects. It is a kind of
classifier intended for representing information in a very abstract way, one which cannot be instantiated.
Initial (Pseudo State)
An initial pseudostate represents a default vertex that is the source for a single transition to the default state of a composite state. There can be at most one initial vertex in a region. The outgoing transition from the initial vertex may have a behavior, but not a trigger or guard.
Initial Node (Control Node)
A control node is an abstract activity node that coordinates flows in an activity.
An initial node is a control node at which flow starts when the activity is invoked.
Input 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 input pin is a pin that holds input values to be consumed by an action.
Instance Specification (Instance Specification)
An instance specification is a model element that represents an instance in a modeled system.
An instance specification has the capability of being a deployment target in a deployment relationship, in the case that it is an instance of a node.
It is also has the capability of being a deployed artifact, if it is an instance of an artifact.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interaction Use (Interaction Use)
An interaction use refers to an interaction. The interaction use is a shorthand for copying the contents of the referenced interaction where the interaction use is. To be accurate the copying must take into account substituting parameters with arguments and connect the formal gates with the actual ones.
Interface (Interface)
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
Interface Realization (Interface Realization)
An interface realization is a specialized realization relationship between a classifier and an interface. This relationship signifies that the realizing classifier conforms to the contract specified by the interface.
Join (Pseudo State)
Join vertices serve to merge several transitions emanating from source vertices in different orthogonal regions. The transitions entering a join vertex cannot have guards or triggers.
Join Node (Control Node)
A control node is an abstract activity node that coordinates flows in an activity.
A join node is a control node that synchronizes multiple flows. Join nodes have a Boolean value specification using the names of the incoming edges to specify the conditions under which the join will emit a token.
Junction (Pseudo State)
Junction vertices are semantic-free vertices that are used to chain together multiple transitions. They are used to construct compound transition paths between states. For example, a junction can be used to converge multiple incoming transitions into a single outgoing transition representing a shared transition path (this is known as an merge). Conversely, they can be used to split an incoming transition into multiple outgoing transition segments with different guard conditions. This realizes a static conditional branch. (In the latter case, outgoing transitions whose guard conditions evaluate to false are disabled. A predefined guard denoted 'else' may be defined for at most one outgoing transition. This transition is enabled if all the guards labeling the other transitions are false.) Static conditional branches are distinct from dynamic conditional branches that are realized by choice vertices.
Lifeline (Lifeline)
A lifeline represents an individual participant in the interaction. While parts and structural features may have multiplicity greater than 1, lifelines represent only one interacting entity.
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.
Manifestation (Manifestation)
A manifestation is the concrete physical rendering of one or more model elements by an artifact.
Merge Node (Control Node)
A control node is an abstract activity node that coordinates flows in an activity.
A merge node is a control node that brings together multiple alternate flows. It is not used to synchronize concurrent flows but to accept one among several alternate flows.
Message (Message)
A message defines a particular communication between lifelines of an interaction.
Model (Model)
A model captures a view of a physical system. It is an abstraction of the physical system, with a certain purpose.
This purpose determines what is to be included in the model and what is irrelevant. Thus the model completely describes those aspects of the physical system that are relevant to the purpose of the model, at the appropriate level of detail.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Object Flow (Object Flow)
An object flow is an activity edge that can have objects or data passing along it. Object flows have support for multicast/receive, token selection from object nodes, and transformation of tokens.
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.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Operation (Operation)
An operation is a behavioral feature of a classifier that specifies the name, type, parameters, and constraints for invoking an associated behavior. An operation may invoke both the execution of method behaviors as well as other behavioral responses.
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.
Package (Package)
A package is used to group elements, and provides a namespace for the grouped elements.
A package can have one or more profile applications to indicate which profiles have been applied.
Parameter (Parameter)
A parameter is a specification of an argument used to pass information into or out of an invocation of a behavioral feature. Parameters are allowed to be treated as connectable elements. Parameters have support for streaming, exceptions, and parameter sets.
Port (Port)
A port is a property of a classifier that specifies a distinct interaction point between that classifier and its environment or between the (behavior of the) classifier and its internal parts.
Ports are connected to properties of the classifier by connectors through which requests can be made to invoke the behavioral features of a classifier.
A Port may specify the services a classifier provides (offers) to its environment as well as the services that a classifier expects (requires) of its environment. A port has an associated protocol state machine.
Primitive Type (Primitive Type)
A primitive type defines a predefined data type, without any relevant substructure (i.e., it has no parts in the context of UML). A primitive datatype may have an algebra and operations defined outside of UML, for example, mathematically.
Profile (Profile)
A profile defines limited extensions to a reference metamodel with the purpose of adapting the metamodel to a specific platform or domain.
Protocol (Protocol)
Only available together with the Real-Time Extension of RSA.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
Protocol Transition (Protocol Transition)
A protocol transition 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.
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.
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.
Reception (Reception)
A reception is a declaration stating that a classifier is prepared to react to the receipt of a signal. A reception designates a signal and specifies the expected behavioral response.
The details of handling a signal are specified by the behavior associated with the reception or the classifier itself.
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.
Region (Region)
A region is an orthogonal part of either a composite state or a state machine. It contains states and transitions.
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.
Shallow History (Pseudo State)
ShallowHistory represents the most recent active substate of its containing state (but not the substates of that substate). A composite state can have at most one shallow history vertex. A transition coming into the shallow history vertex is equivalent to a transition coming into the most recent active substate of a state. At most one transition may originate from the history connector to the default shallow history state. This transition is taken in case the composite state had never been active before. Entry actions of states entered on the path to the state represented by a shallow history are performed.
Signal (Signal)
A signal is a specification of send request instances communicated between objects. The receiving object handles the received request instances as specified by its receptions. The data carried by a send request (which was passed to it by the send invocation occurrence that caused that request) are represented as attributes of the signal.
A signal is defined independently of the classifiers handling the signal occurrence.
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
State (State)
A state models a situation during which some (usually implicit) invariant condition holds.
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.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
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.
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.
Terminate (Pseudo State)
Entering a terminate pseudostate implies that the execution of this state machine by means of its context object is terminated. The state machine does not exit any states nor does it perform any exit actions other than those associated with the transition leading to the terminate pseudostate. Entering a terminate pseudostate is equivalent to invoking a DestroyObjectAction.
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.
Transition (Transition)
A transition is a directed relationship between a source vertex and a target vertex.
It may be part of a compound transition, which takes the state machine from one state configuration to another, representing the complete response of the state machine to an occurrence of an event of a particular type.
Trigger (Trigger)
A trigger relates an event to a behavior that may affect an instance of the classifier. A trigger specification may be qualified by the port on which the event occurred.
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.
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.
Use Case (Use Case)
A use case is the specification of a set of actions performed by a system, which yields an observable result that is, typically, of value for one or more actors or other stakeholders of the system.
Value 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 input pin is a pin that holds input values to be consumed by an action.
A value pin is an input pin that provides a value by evaluating a value specification.
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.
An item of one of the following item kinds:
Abstraction (Abstraction)Accept Call Action (Action)Accept Event Action (Action)Action Input Pin (Pin)Activity (Activity)Activity Final Node (Control Node)Activity Parameter Node (Object Node)Activity Partition (Activity Partition)Actor (Actor)Add Structural Feature Value Action (Action)Add Variable Value Action (Action)Artifact (Artifact)Association (Association)Association End (Association End)Attribute (Attribute)Broadcast Signal Action (Action)Call Behavior Action (Action)Call Event (Call Event)Call Operation Action (Action)Central Buffer (Object Node)Choice (Pseudo State)Class (Class)Clear Association Action (Action)Clear Structural Feature Action (Action)Clear Variable Action (Action)Collaboration (Collaboration)Collaboration Use (Collaboration Use)Combined Fragment (Combined Fragment)Communication Path (Communication Path)Component (Component)Component Realization (Component Realization)Conditional Node (Action)Connection Point Reference (Connection Point Reference)Connector (Connector)Control Flow (Control Flow)Create Link Action (Action)Create Link Object Action (Action)Create Object Action (Action)Data Store Node (Object Node)Data Type (Data Type)Decision Node (Control Node)Deep History (Pseudo State)Dependency (Dependency)Deployment (Deployment)Deployment Specification (Deployment Specification)Destroy Link Action (Action)Destroy Object Action (Action)Device (Device)Entry Point (Pseudo State)Enumeration (Enumeration)Enumeration Literal (Enumeration Literal)Execution Environment (Execution Environment)Exit Point (Pseudo State)Expansion Node (Object Node)Expansion Region (Action)Extend (Extend)Extension (Extension)Extension Point (Extension Point)Final State (Final State)Flow Final Node (Control Node)Fork (Pseudo State)Fork Node (Control Node)Gate (Gate)Guard (Guard)Include (Include)Information Flow (Information Flow)Information Item (Information Item)Initial (Pseudo State)Initial Node (Control Node)Input Pin (Pin)Instance Specification (Instance Specification)Interaction (Interaction)Interaction Use (Interaction Use)Interface (Interface)Interface Realization (Interface Realization)Join (Pseudo State)Join Node (Control Node)Junction (Pseudo State)Lifeline (Lifeline)Loop Node (Action)Manifestation (Manifestation)Merge Node (Control Node)Message (Message)Model (Model)Node (Node)Object Flow (Object Flow)Opaque Action (Action)Opaque Behavior (Opaque Behavior)Operation (Operation)Output Pin (Pin)Package (Package)Parameter (Parameter)Port (Port)Primitive Type (Primitive Type)Profile (Profile)Protocol (Protocol)Protocol State Machine (Protocol State Machine)Protocol Transition (Protocol Transition)Raise Exception Action (Action)Read Extent Action (Action)Read Is Classified Object Action (Action)Read Link Action (Action)Read Link Object End Action (Action)Read Link Object End Qualifier Action (Action)Read Self Action (Action)Read Structural Feature Action (Action)Read Variable Action (Action)Realization (Realization)Reception (Reception)Reclassify Object Action (Action)Reduce Action (Action)Region (Region)Remove Structural Feature Value Action (Action)Remove Variable Value Action (Action)Reply Action (Action)Send Object Action (Action)Send Signal Action (Action)Sequence Node (Action)Shallow History (Pseudo State)Signal (Signal)Start Classifier Behavior Action (Action)Start Object Behavior Action (Action)State (State)State Machine (State Machine)Stereotype (Stereotype)Structured Activity Node (Action)Structured Activity Node (Structured Activity Node)Substitution (Substitution)Terminate (Pseudo State)Test Identity Action (Action)Transition (Transition)Trigger (Trigger)Unmarshall Action (Action)Usage (Usage)Use Case (Use Case)Value Pin (Pin)Value Specification Action (Action)Abstraction (Abstraction)Dependency (Dependency)Information Flow (Information Flow)Realization (Realization)Substitution (Substitution)Usage (Usage) Element ImportAn element import identifies an element in another package, and allows the element to be referenced using its name without a qualifier.
Specifies the visibility of the imported PackageableElement within the importing Package. The default visibility is the same as that of the imported element. If the imported element does not have a visibility, it is possible to add visibility to the element import.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Actor (Actor)
An actor specifies a role played by a user or any other system that interacts with the subject.
Artifact (Artifact)
An artifact is the specification of a physical piece of information that is used or produced by a software development process, or by deployment and operation of a system.
Examples of artifacts include model files, source files, scripts, and binary executable files, a table in a database system, a development deliverable, or a word-processing document, a mail message. An artifact is the source of a deployment to a node.
Association (Association)
An association describes a set of tuples whose values refer to typed instances. An instance of an association is called a link.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
Collaboration (Collaboration)
A collaboration defines a set of co-operating roles used collectively to illustrate a specific functionality.
A collaboration should only show the roles and attributes required to accomplish its defined task or function. Isolating the primary roles is an exercise in simplifying the structure and clarifying the behavior, and also provides for re-use. A collaboration often implements a pattern.
Communication Path (Communication Path)
A communication path is an association between two deployment targets, through which they are able to exchange signals and messages.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Data Type (Data Type)
A data type is a type whose instances are identified only by their value. A data type may contain attributes to support the modeling of structured data types.
Deployment Specification (Deployment Specification)
A deployment specification specifies a set of properties that determine execution parameters of a component artifact that is deployed on a node.
A deployment specification can be aimed at a specific type of container. An artifact that reifies or implements deployment specification properties is a deployment descriptor.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Enumeration (Enumeration)
An enumeration is a data type whose values are enumerated in the model as enumeration literals.
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Extension (Extension)
An extension is used to indicate that the properties of a metaclass are extended through a stereotype, and gives the ability to flexibly add (and later remove) stereotypes to classes.
Final State (Final State)
A special kind of state signifying that the enclosing region is completed.
If the enclosing region is directly contained in a state machine and all other regions in the state machine also are completed, then it means that the entire state machine is completed.
Information Item (Information Item)
An information item is an abstraction of all kinds of information that can be exchanged between objects. It is a kind of
classifier intended for representing information in a very abstract way, one which cannot be instantiated.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interface (Interface)
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
Model (Model)
A model captures a view of a physical system. It is an abstraction of the physical system, with a certain purpose.
This purpose determines what is to be included in the model and what is irrelevant. Thus the model completely describes those aspects of the physical system that are relevant to the purpose of the model, at the appropriate level of detail.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Operation (Operation)
An operation is a behavioral feature of a classifier that specifies the name, type, parameters, and constraints for invoking an associated behavior. An operation may invoke both the execution of method behaviors as well as other behavioral responses.
Package (Package)
A package is used to group elements, and provides a namespace for the grouped elements.
A package can have one or more profile applications to indicate which profiles have been applied.
Primitive Type (Primitive Type)
A primitive type defines a predefined data type, without any relevant substructure (i.e., it has no parts in the context of UML). A primitive datatype may have an algebra and operations defined outside of UML, for example, mathematically.
Profile (Profile)
A profile defines limited extensions to a reference metamodel with the purpose of adapting the metamodel to a specific platform or domain.
Protocol (Protocol)
Only available together with the Real-Time Extension of RSA.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
Protocol Transition (Protocol Transition)
A protocol transition 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.
Reception (Reception)
A reception is a declaration stating that a classifier is prepared to react to the receipt of a signal. A reception designates a signal and specifies the expected behavioral response.
The details of handling a signal are specified by the behavior associated with the reception or the classifier itself.
Region (Region)
A region is an orthogonal part of either a composite state or a state machine. It contains states and transitions.
Signal (Signal)
A signal is a specification of send request instances communicated between objects. The receiving object handles the received request instances as specified by its receptions. The data carried by a send request (which was passed to it by the send invocation occurrence that caused that request) are represented as attributes of the signal.
A signal is defined independently of the classifiers handling the signal occurrence.
State (State)
A state models a situation during which some (usually implicit) invariant condition holds.
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.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
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.
Transition (Transition)
A transition is a directed relationship between a source vertex and a target vertex.
It may be part of a compound transition, which takes the state machine from one state configuration to another, representing the complete response of the state machine to an occurrence of an event of a particular type.
Use Case (Use Case)
A use case is the specification of a set of actions performed by a system, which yields an observable result that is, typically, of value for one or more actors or other stakeholders of the system.
An item of one of the following item kinds:
Activity (Activity)Actor (Actor)Artifact (Artifact)Association (Association)Call Event (Call Event)Class (Class)Collaboration (Collaboration)Communication Path (Communication Path)Component (Component)Data Type (Data Type)Deployment Specification (Deployment Specification)Device (Device)Enumeration (Enumeration)Enumeration Literal (Enumeration Literal)Execution Environment (Execution Environment)Extension (Extension)Information Item (Information Item)Instance Specification (Instance Specification)Interaction (Interaction)Interface (Interface)Model (Model)Node (Node)Opaque Behavior (Opaque Behavior)Package (Package)Primitive Type (Primitive Type)Profile (Profile)Protocol (Protocol)Protocol State Machine (Protocol State Machine)Signal (Signal)State Machine (State Machine)Stereotype (Stereotype)Use Case (Use Case) Package ImportA package import is a relationship that allows the use of unqualified names to refer to package members from other namespaces.
Specifies the visibility of the imported PackageableElements within the importing Namespace, i.e., whether imported elements will in turn be visible to other packages that use that importingPackage as an importedPackage. If the PackageImport is public, the imported elements will be visible outside the package, while if it is private they will not.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Actor (Actor)
An actor specifies a role played by a user or any other system that interacts with the subject.
Artifact (Artifact)
An artifact is the specification of a physical piece of information that is used or produced by a software development process, or by deployment and operation of a system.
Examples of artifacts include model files, source files, scripts, and binary executable files, a table in a database system, a development deliverable, or a word-processing document, a mail message. An artifact is the source of a deployment to a node.
Association (Association)
An association describes a set of tuples whose values refer to typed instances. An instance of an association is called a link.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
Collaboration (Collaboration)
A collaboration defines a set of co-operating roles used collectively to illustrate a specific functionality.
A collaboration should only show the roles and attributes required to accomplish its defined task or function. Isolating the primary roles is an exercise in simplifying the structure and clarifying the behavior, and also provides for re-use. A collaboration often implements a pattern.
Communication Path (Communication Path)
A communication path is an association between two deployment targets, through which they are able to exchange signals and messages.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Data Type (Data Type)
A data type is a type whose instances are identified only by their value. A data type may contain attributes to support the modeling of structured data types.
Deployment Specification (Deployment Specification)
A deployment specification specifies a set of properties that determine execution parameters of a component artifact that is deployed on a node.
A deployment specification can be aimed at a specific type of container. An artifact that reifies or implements deployment specification properties is a deployment descriptor.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Enumeration (Enumeration)
An enumeration is a data type whose values are enumerated in the model as enumeration literals.
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Extension (Extension)
An extension is used to indicate that the properties of a metaclass are extended through a stereotype, and gives the ability to flexibly add (and later remove) stereotypes to classes.
Final State (Final State)
A special kind of state signifying that the enclosing region is completed.
If the enclosing region is directly contained in a state machine and all other regions in the state machine also are completed, then it means that the entire state machine is completed.
Information Item (Information Item)
An information item is an abstraction of all kinds of information that can be exchanged between objects. It is a kind of
classifier intended for representing information in a very abstract way, one which cannot be instantiated.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interface (Interface)
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
Model (Model)
A model captures a view of a physical system. It is an abstraction of the physical system, with a certain purpose.
This purpose determines what is to be included in the model and what is irrelevant. Thus the model completely describes those aspects of the physical system that are relevant to the purpose of the model, at the appropriate level of detail.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Operation (Operation)
An operation is a behavioral feature of a classifier that specifies the name, type, parameters, and constraints for invoking an associated behavior. An operation may invoke both the execution of method behaviors as well as other behavioral responses.
Package (Package)
A package is used to group elements, and provides a namespace for the grouped elements.
A package can have one or more profile applications to indicate which profiles have been applied.
Primitive Type (Primitive Type)
A primitive type defines a predefined data type, without any relevant substructure (i.e., it has no parts in the context of UML). A primitive datatype may have an algebra and operations defined outside of UML, for example, mathematically.
Profile (Profile)
A profile defines limited extensions to a reference metamodel with the purpose of adapting the metamodel to a specific platform or domain.
Protocol (Protocol)
Only available together with the Real-Time Extension of RSA.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
Protocol Transition (Protocol Transition)
A protocol transition 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.
Reception (Reception)
A reception is a declaration stating that a classifier is prepared to react to the receipt of a signal. A reception designates a signal and specifies the expected behavioral response.
The details of handling a signal are specified by the behavior associated with the reception or the classifier itself.
Region (Region)
A region is an orthogonal part of either a composite state or a state machine. It contains states and transitions.
Signal (Signal)
A signal is a specification of send request instances communicated between objects. The receiving object handles the received request instances as specified by its receptions. The data carried by a send request (which was passed to it by the send invocation occurrence that caused that request) are represented as attributes of the signal.
A signal is defined independently of the classifiers handling the signal occurrence.
State (State)
A state models a situation during which some (usually implicit) invariant condition holds.
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.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
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.
Transition (Transition)
A transition is a directed relationship between a source vertex and a target vertex.
It may be part of a compound transition, which takes the state machine from one state configuration to another, representing the complete response of the state machine to an occurrence of an event of a particular type.
Use Case (Use Case)
A use case is the specification of a set of actions performed by a system, which yields an observable result that is, typically, of value for one or more actors or other stakeholders of the system.
An item of one of the following item kinds:
Package MergeA package merge defines how the contents of one package are extended by the contents of another package.
An element of one of the following kinds:
Model (Model)
A model captures a view of a physical system. It is an abstraction of the physical system, with a certain purpose.
This purpose determines what is to be included in the model and what is irrelevant. Thus the model completely describes those aspects of the physical system that are relevant to the purpose of the model, at the appropriate level of detail.
Package (Package)
A package is used to group elements, and provides a namespace for the grouped elements.
A package can have one or more profile applications to indicate which profiles have been applied.
Profile (Profile)
A profile defines limited extensions to a reference metamodel with the purpose of adapting the metamodel to a specific platform or domain.
An item of one of the following item kinds:
ConstraintA 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.
The name of the constraint
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 constraint.
Specifies the languages in which the constraint is stated. The interpretation of the expression body depends on the languages. If the languages are unspecified, they might be implicit from the expression body or the context.
The condition or the restriction of the constraint
The ordered set of elements referenced by this constraint.
May contain any kind of item supported by UML.
Activity DiagramAn Activity Diagram is a diagram that shows the decomposition of an activity into actions and the control and dataflow between these behavorial elements.
The name of the diagram.
A textual description of the element.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
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.
Class DiagramA Class Diagram is a diagram that shows classes and interfaces and their relationships. However a class diagram may also show packages and all kind of classifier elements.
The name of the diagram.
A textual description of the element.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Actor (Actor)
An actor specifies a role played by a user or any other system that interacts with the subject.
Artifact (Artifact)
An artifact is the specification of a physical piece of information that is used or produced by a software development process, or by deployment and operation of a system.
Examples of artifacts include model files, source files, scripts, and binary executable files, a table in a database system, a development deliverable, or a word-processing document, a mail message. An artifact is the source of a deployment to a node.
Association (Association)
An association describes a set of tuples whose values refer to typed instances. An instance of an association is called a link.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
Collaboration (Collaboration)
A collaboration defines a set of co-operating roles used collectively to illustrate a specific functionality.
A collaboration should only show the roles and attributes required to accomplish its defined task or function. Isolating the primary roles is an exercise in simplifying the structure and clarifying the behavior, and also provides for re-use. A collaboration often implements a pattern.
Communication Path (Communication Path)
A communication path is an association between two deployment targets, through which they are able to exchange signals and messages.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Data Type (Data Type)
A data type is a type whose instances are identified only by their value. A data type may contain attributes to support the modeling of structured data types.
Deployment Specification (Deployment Specification)
A deployment specification specifies a set of properties that determine execution parameters of a component artifact that is deployed on a node.
A deployment specification can be aimed at a specific type of container. An artifact that reifies or implements deployment specification properties is a deployment descriptor.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Enumeration (Enumeration)
An enumeration is a data type whose values are enumerated in the model as enumeration literals.
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Extension (Extension)
An extension is used to indicate that the properties of a metaclass are extended through a stereotype, and gives the ability to flexibly add (and later remove) stereotypes to classes.
Information Item (Information Item)
An information item is an abstraction of all kinds of information that can be exchanged between objects. It is a kind of
classifier intended for representing information in a very abstract way, one which cannot be instantiated.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interface (Interface)
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
Model (Model)
A model captures a view of a physical system. It is an abstraction of the physical system, with a certain purpose.
This purpose determines what is to be included in the model and what is irrelevant. Thus the model completely describes those aspects of the physical system that are relevant to the purpose of the model, at the appropriate level of detail.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Package (Package)
A package is used to group elements, and provides a namespace for the grouped elements.
A package can have one or more profile applications to indicate which profiles have been applied.
Primitive Type (Primitive Type)
A primitive type defines a predefined data type, without any relevant substructure (i.e., it has no parts in the context of UML). A primitive datatype may have an algebra and operations defined outside of UML, for example, mathematically.
Profile (Profile)
A profile defines limited extensions to a reference metamodel with the purpose of adapting the metamodel to a specific platform or domain.
Protocol (Protocol)
Only available together with the Real-Time Extension of RSA.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
Signal (Signal)
A signal is a specification of send request instances communicated between objects. The receiving object handles the received request instances as specified by its receptions. The data carried by a send request (which was passed to it by the send invocation occurrence that caused that request) are represented as attributes of the signal.
A signal is defined independently of the classifiers handling the signal occurrence.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
Use Case (Use Case)
A use case is the specification of a set of actions performed by a system, which yields an observable result that is, typically, of value for one or more actors or other stakeholders of the system.
Activity (Activity)Actor (Actor)Artifact (Artifact)Association (Association)Call Event (Call Event)Class (Class)Collaboration (Collaboration)Communication Path (Communication Path)Component (Component)Constraint (Constraint)Data Type (Data Type)Deployment Specification (Deployment Specification)Device (Device)Enumeration (Enumeration)Enumeration Literal (Enumeration Literal)Execution Environment (Execution Environment)Extension (Extension)Information Item (Information Item)Instance Specification (Instance Specification)Interaction (Interaction)Interface (Interface)Model (Model)Node (Node)Opaque Behavior (Opaque Behavior)Package (Package)Primitive Type (Primitive Type)Profile (Profile)Protocol (Protocol)Protocol State Machine (Protocol State Machine)Signal (Signal)State Machine (State Machine)Stereotype (Stereotype)Use Case (Use Case) Communication DiagramA Communication Diagram is a visual representation of an interaction between a set of objects.
The name of the diagram.
A textual description of the element.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Component DiagramA Component Diagram is a diagram that shows components, interfaces and artifacts and their relationships. However a component diagram may also show packages and all kind of classifier elements.
The name of the diagram.
A textual description of the element.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Actor (Actor)
An actor specifies a role played by a user or any other system that interacts with the subject.
Artifact (Artifact)
An artifact is the specification of a physical piece of information that is used or produced by a software development process, or by deployment and operation of a system.
Examples of artifacts include model files, source files, scripts, and binary executable files, a table in a database system, a development deliverable, or a word-processing document, a mail message. An artifact is the source of a deployment to a node.
Association (Association)
An association describes a set of tuples whose values refer to typed instances. An instance of an association is called a link.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
Collaboration (Collaboration)
A collaboration defines a set of co-operating roles used collectively to illustrate a specific functionality.
A collaboration should only show the roles and attributes required to accomplish its defined task or function. Isolating the primary roles is an exercise in simplifying the structure and clarifying the behavior, and also provides for re-use. A collaboration often implements a pattern.
Communication Path (Communication Path)
A communication path is an association between two deployment targets, through which they are able to exchange signals and messages.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Data Type (Data Type)
A data type is a type whose instances are identified only by their value. A data type may contain attributes to support the modeling of structured data types.
Deployment Specification (Deployment Specification)
A deployment specification specifies a set of properties that determine execution parameters of a component artifact that is deployed on a node.
A deployment specification can be aimed at a specific type of container. An artifact that reifies or implements deployment specification properties is a deployment descriptor.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Enumeration (Enumeration)
An enumeration is a data type whose values are enumerated in the model as enumeration literals.
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Extension (Extension)
An extension is used to indicate that the properties of a metaclass are extended through a stereotype, and gives the ability to flexibly add (and later remove) stereotypes to classes.
Information Item (Information Item)
An information item is an abstraction of all kinds of information that can be exchanged between objects. It is a kind of
classifier intended for representing information in a very abstract way, one which cannot be instantiated.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interface (Interface)
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
Model (Model)
A model captures a view of a physical system. It is an abstraction of the physical system, with a certain purpose.
This purpose determines what is to be included in the model and what is irrelevant. Thus the model completely describes those aspects of the physical system that are relevant to the purpose of the model, at the appropriate level of detail.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Package (Package)
A package is used to group elements, and provides a namespace for the grouped elements.
A package can have one or more profile applications to indicate which profiles have been applied.
Primitive Type (Primitive Type)
A primitive type defines a predefined data type, without any relevant substructure (i.e., it has no parts in the context of UML). A primitive datatype may have an algebra and operations defined outside of UML, for example, mathematically.
Profile (Profile)
A profile defines limited extensions to a reference metamodel with the purpose of adapting the metamodel to a specific platform or domain.
Protocol (Protocol)
Only available together with the Real-Time Extension of RSA.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
Signal (Signal)
A signal is a specification of send request instances communicated between objects. The receiving object handles the received request instances as specified by its receptions. The data carried by a send request (which was passed to it by the send invocation occurrence that caused that request) are represented as attributes of the signal.
A signal is defined independently of the classifiers handling the signal occurrence.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
Use Case (Use Case)
A use case is the specification of a set of actions performed by a system, which yields an observable result that is, typically, of value for one or more actors or other stakeholders of the system.
Activity (Activity)Actor (Actor)Artifact (Artifact)Association (Association)Call Event (Call Event)Class (Class)Collaboration (Collaboration)Communication Path (Communication Path)Component (Component)Constraint (Constraint)Data Type (Data Type)Deployment Specification (Deployment Specification)Device (Device)Enumeration (Enumeration)Enumeration Literal (Enumeration Literal)Execution Environment (Execution Environment)Extension (Extension)Information Item (Information Item)Instance Specification (Instance Specification)Interaction (Interaction)Interface (Interface)Model (Model)Node (Node)Opaque Behavior (Opaque Behavior)Package (Package)Primitive Type (Primitive Type)Profile (Profile)Protocol (Protocol)Protocol State Machine (Protocol State Machine)Signal (Signal)State Machine (State Machine)Stereotype (Stereotype)Use Case (Use Case) Deployment DiagramA Deployment Diagram is a diagram that shows nodes and artifacts and their relationships. However a deployment diagram may also show packages and all kind of classifier elements.
The name of the diagram.
A textual description of the element.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Actor (Actor)
An actor specifies a role played by a user or any other system that interacts with the subject.
Artifact (Artifact)
An artifact is the specification of a physical piece of information that is used or produced by a software development process, or by deployment and operation of a system.
Examples of artifacts include model files, source files, scripts, and binary executable files, a table in a database system, a development deliverable, or a word-processing document, a mail message. An artifact is the source of a deployment to a node.
Association (Association)
An association describes a set of tuples whose values refer to typed instances. An instance of an association is called a link.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
Collaboration (Collaboration)
A collaboration defines a set of co-operating roles used collectively to illustrate a specific functionality.
A collaboration should only show the roles and attributes required to accomplish its defined task or function. Isolating the primary roles is an exercise in simplifying the structure and clarifying the behavior, and also provides for re-use. A collaboration often implements a pattern.
Communication Path (Communication Path)
A communication path is an association between two deployment targets, through which they are able to exchange signals and messages.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Data Type (Data Type)
A data type is a type whose instances are identified only by their value. A data type may contain attributes to support the modeling of structured data types.
Deployment Specification (Deployment Specification)
A deployment specification specifies a set of properties that determine execution parameters of a component artifact that is deployed on a node.
A deployment specification can be aimed at a specific type of container. An artifact that reifies or implements deployment specification properties is a deployment descriptor.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Enumeration (Enumeration)
An enumeration is a data type whose values are enumerated in the model as enumeration literals.
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Extension (Extension)
An extension is used to indicate that the properties of a metaclass are extended through a stereotype, and gives the ability to flexibly add (and later remove) stereotypes to classes.
Information Item (Information Item)
An information item is an abstraction of all kinds of information that can be exchanged between objects. It is a kind of
classifier intended for representing information in a very abstract way, one which cannot be instantiated.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interface (Interface)
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
Model (Model)
A model captures a view of a physical system. It is an abstraction of the physical system, with a certain purpose.
This purpose determines what is to be included in the model and what is irrelevant. Thus the model completely describes those aspects of the physical system that are relevant to the purpose of the model, at the appropriate level of detail.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Package (Package)
A package is used to group elements, and provides a namespace for the grouped elements.
A package can have one or more profile applications to indicate which profiles have been applied.
Primitive Type (Primitive Type)
A primitive type defines a predefined data type, without any relevant substructure (i.e., it has no parts in the context of UML). A primitive datatype may have an algebra and operations defined outside of UML, for example, mathematically.
Profile (Profile)
A profile defines limited extensions to a reference metamodel with the purpose of adapting the metamodel to a specific platform or domain.
Protocol (Protocol)
Only available together with the Real-Time Extension of RSA.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
Signal (Signal)
A signal is a specification of send request instances communicated between objects. The receiving object handles the received request instances as specified by its receptions. The data carried by a send request (which was passed to it by the send invocation occurrence that caused that request) are represented as attributes of the signal.
A signal is defined independently of the classifiers handling the signal occurrence.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
Use Case (Use Case)
A use case is the specification of a set of actions performed by a system, which yields an observable result that is, typically, of value for one or more actors or other stakeholders of the system.
Activity (Activity)Actor (Actor)Artifact (Artifact)Association (Association)Call Event (Call Event)Class (Class)Collaboration (Collaboration)Communication Path (Communication Path)Component (Component)Constraint (Constraint)Data Type (Data Type)Deployment Specification (Deployment Specification)Device (Device)Enumeration (Enumeration)Enumeration Literal (Enumeration Literal)Execution Environment (Execution Environment)Extension (Extension)Information Item (Information Item)Instance Specification (Instance Specification)Interaction (Interaction)Interface (Interface)Model (Model)Node (Node)Opaque Behavior (Opaque Behavior)Package (Package)Primitive Type (Primitive Type)Profile (Profile)Protocol (Protocol)Protocol State Machine (Protocol State Machine)Signal (Signal)State Machine (State Machine)Stereotype (Stereotype)Use Case (Use Case) Freeform DiagramA Free Form diagram is a diagram in which you can make free drawings without the restriction of using UML.
The name of the diagram.
A textual description of the element.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Actor (Actor)
An actor specifies a role played by a user or any other system that interacts with the subject.
Artifact (Artifact)
An artifact is the specification of a physical piece of information that is used or produced by a software development process, or by deployment and operation of a system.
Examples of artifacts include model files, source files, scripts, and binary executable files, a table in a database system, a development deliverable, or a word-processing document, a mail message. An artifact is the source of a deployment to a node.
Association (Association)
An association describes a set of tuples whose values refer to typed instances. An instance of an association is called a link.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
Collaboration (Collaboration)
A collaboration defines a set of co-operating roles used collectively to illustrate a specific functionality.
A collaboration should only show the roles and attributes required to accomplish its defined task or function. Isolating the primary roles is an exercise in simplifying the structure and clarifying the behavior, and also provides for re-use. A collaboration often implements a pattern.
Communication Path (Communication Path)
A communication path is an association between two deployment targets, through which they are able to exchange signals and messages.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Data Type (Data Type)
A data type is a type whose instances are identified only by their value. A data type may contain attributes to support the modeling of structured data types.
Deployment Specification (Deployment Specification)
A deployment specification specifies a set of properties that determine execution parameters of a component artifact that is deployed on a node.
A deployment specification can be aimed at a specific type of container. An artifact that reifies or implements deployment specification properties is a deployment descriptor.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Enumeration (Enumeration)
An enumeration is a data type whose values are enumerated in the model as enumeration literals.
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Extension (Extension)
An extension is used to indicate that the properties of a metaclass are extended through a stereotype, and gives the ability to flexibly add (and later remove) stereotypes to classes.
Information Item (Information Item)
An information item is an abstraction of all kinds of information that can be exchanged between objects. It is a kind of
classifier intended for representing information in a very abstract way, one which cannot be instantiated.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interface (Interface)
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
Model (Model)
A model captures a view of a physical system. It is an abstraction of the physical system, with a certain purpose.
This purpose determines what is to be included in the model and what is irrelevant. Thus the model completely describes those aspects of the physical system that are relevant to the purpose of the model, at the appropriate level of detail.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Package (Package)
A package is used to group elements, and provides a namespace for the grouped elements.
A package can have one or more profile applications to indicate which profiles have been applied.
Primitive Type (Primitive Type)
A primitive type defines a predefined data type, without any relevant substructure (i.e., it has no parts in the context of UML). A primitive datatype may have an algebra and operations defined outside of UML, for example, mathematically.
Profile (Profile)
A profile defines limited extensions to a reference metamodel with the purpose of adapting the metamodel to a specific platform or domain.
Protocol (Protocol)
Only available together with the Real-Time Extension of RSA.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
Signal (Signal)
A signal is a specification of send request instances communicated between objects. The receiving object handles the received request instances as specified by its receptions. The data carried by a send request (which was passed to it by the send invocation occurrence that caused that request) are represented as attributes of the signal.
A signal is defined independently of the classifiers handling the signal occurrence.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
Use Case (Use Case)
A use case is the specification of a set of actions performed by a system, which yields an observable result that is, typically, of value for one or more actors or other stakeholders of the system.
Activity (Activity)Actor (Actor)Artifact (Artifact)Association (Association)Call Event (Call Event)Class (Class)Collaboration (Collaboration)Communication Path (Communication Path)Component (Component)Constraint (Constraint)Data Type (Data Type)Deployment Specification (Deployment Specification)Device (Device)Enumeration (Enumeration)Enumeration Literal (Enumeration Literal)Execution Environment (Execution Environment)Extension (Extension)Information Item (Information Item)Instance Specification (Instance Specification)Interaction (Interaction)Interface (Interface)Model (Model)Node (Node)Opaque Behavior (Opaque Behavior)Package (Package)Primitive Type (Primitive Type)Profile (Profile)Protocol (Protocol)Protocol State Machine (Protocol State Machine)Signal (Signal)State Machine (State Machine)Stereotype (Stereotype)Use Case (Use Case) Interaction Overview DiagramAn Interaction Overview Diagram is a visual representation of a control flow of interaction..
The name of the diagram.
A textual description of the element.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Actor (Actor)
An actor specifies a role played by a user or any other system that interacts with the subject.
Artifact (Artifact)
An artifact is the specification of a physical piece of information that is used or produced by a software development process, or by deployment and operation of a system.
Examples of artifacts include model files, source files, scripts, and binary executable files, a table in a database system, a development deliverable, or a word-processing document, a mail message. An artifact is the source of a deployment to a node.
Association (Association)
An association describes a set of tuples whose values refer to typed instances. An instance of an association is called a link.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
Collaboration (Collaboration)
A collaboration defines a set of co-operating roles used collectively to illustrate a specific functionality.
A collaboration should only show the roles and attributes required to accomplish its defined task or function. Isolating the primary roles is an exercise in simplifying the structure and clarifying the behavior, and also provides for re-use. A collaboration often implements a pattern.
Communication Path (Communication Path)
A communication path is an association between two deployment targets, through which they are able to exchange signals and messages.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Data Type (Data Type)
A data type is a type whose instances are identified only by their value. A data type may contain attributes to support the modeling of structured data types.
Deployment Specification (Deployment Specification)
A deployment specification specifies a set of properties that determine execution parameters of a component artifact that is deployed on a node.
A deployment specification can be aimed at a specific type of container. An artifact that reifies or implements deployment specification properties is a deployment descriptor.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Enumeration (Enumeration)
An enumeration is a data type whose values are enumerated in the model as enumeration literals.
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Extension (Extension)
An extension is used to indicate that the properties of a metaclass are extended through a stereotype, and gives the ability to flexibly add (and later remove) stereotypes to classes.
Information Item (Information Item)
An information item is an abstraction of all kinds of information that can be exchanged between objects. It is a kind of
classifier intended for representing information in a very abstract way, one which cannot be instantiated.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interface (Interface)
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
Model (Model)
A model captures a view of a physical system. It is an abstraction of the physical system, with a certain purpose.
This purpose determines what is to be included in the model and what is irrelevant. Thus the model completely describes those aspects of the physical system that are relevant to the purpose of the model, at the appropriate level of detail.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Package (Package)
A package is used to group elements, and provides a namespace for the grouped elements.
A package can have one or more profile applications to indicate which profiles have been applied.
Primitive Type (Primitive Type)
A primitive type defines a predefined data type, without any relevant substructure (i.e., it has no parts in the context of UML). A primitive datatype may have an algebra and operations defined outside of UML, for example, mathematically.
Profile (Profile)
A profile defines limited extensions to a reference metamodel with the purpose of adapting the metamodel to a specific platform or domain.
Protocol (Protocol)
Only available together with the Real-Time Extension of RSA.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
Signal (Signal)
A signal is a specification of send request instances communicated between objects. The receiving object handles the received request instances as specified by its receptions. The data carried by a send request (which was passed to it by the send invocation occurrence that caused that request) are represented as attributes of the signal.
A signal is defined independently of the classifiers handling the signal occurrence.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
Use Case (Use Case)
A use case is the specification of a set of actions performed by a system, which yields an observable result that is, typically, of value for one or more actors or other stakeholders of the system.
Object DiagramAn Object Diagram is a diagram that shows instance specification, links and slots.
The name of the diagram.
A textual description of the element.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Actor (Actor)
An actor specifies a role played by a user or any other system that interacts with the subject.
Artifact (Artifact)
An artifact is the specification of a physical piece of information that is used or produced by a software development process, or by deployment and operation of a system.
Examples of artifacts include model files, source files, scripts, and binary executable files, a table in a database system, a development deliverable, or a word-processing document, a mail message. An artifact is the source of a deployment to a node.
Association (Association)
An association describes a set of tuples whose values refer to typed instances. An instance of an association is called a link.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
Collaboration (Collaboration)
A collaboration defines a set of co-operating roles used collectively to illustrate a specific functionality.
A collaboration should only show the roles and attributes required to accomplish its defined task or function. Isolating the primary roles is an exercise in simplifying the structure and clarifying the behavior, and also provides for re-use. A collaboration often implements a pattern.
Communication Path (Communication Path)
A communication path is an association between two deployment targets, through which they are able to exchange signals and messages.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Data Type (Data Type)
A data type is a type whose instances are identified only by their value. A data type may contain attributes to support the modeling of structured data types.
Deployment Specification (Deployment Specification)
A deployment specification specifies a set of properties that determine execution parameters of a component artifact that is deployed on a node.
A deployment specification can be aimed at a specific type of container. An artifact that reifies or implements deployment specification properties is a deployment descriptor.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Enumeration (Enumeration)
An enumeration is a data type whose values are enumerated in the model as enumeration literals.
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Extension (Extension)
An extension is used to indicate that the properties of a metaclass are extended through a stereotype, and gives the ability to flexibly add (and later remove) stereotypes to classes.
Information Item (Information Item)
An information item is an abstraction of all kinds of information that can be exchanged between objects. It is a kind of
classifier intended for representing information in a very abstract way, one which cannot be instantiated.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interface (Interface)
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
Model (Model)
A model captures a view of a physical system. It is an abstraction of the physical system, with a certain purpose.
This purpose determines what is to be included in the model and what is irrelevant. Thus the model completely describes those aspects of the physical system that are relevant to the purpose of the model, at the appropriate level of detail.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Package (Package)
A package is used to group elements, and provides a namespace for the grouped elements.
A package can have one or more profile applications to indicate which profiles have been applied.
Primitive Type (Primitive Type)
A primitive type defines a predefined data type, without any relevant substructure (i.e., it has no parts in the context of UML). A primitive datatype may have an algebra and operations defined outside of UML, for example, mathematically.
Profile (Profile)
A profile defines limited extensions to a reference metamodel with the purpose of adapting the metamodel to a specific platform or domain.
Protocol (Protocol)
Only available together with the Real-Time Extension of RSA.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
Signal (Signal)
A signal is a specification of send request instances communicated between objects. The receiving object handles the received request instances as specified by its receptions. The data carried by a send request (which was passed to it by the send invocation occurrence that caused that request) are represented as attributes of the signal.
A signal is defined independently of the classifiers handling the signal occurrence.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
Use Case (Use Case)
A use case is the specification of a set of actions performed by a system, which yields an observable result that is, typically, of value for one or more actors or other stakeholders of the system.
Constraint (Constraint)Enumeration Literal (Enumeration Literal)Instance Specification (Instance Specification) Sequence DiagramA Sequence Diagram is a visual representation of an interaction between a set of objects.
The name of the diagram.
A textual description of the element.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Statechart DiagramA State Machine Diagram is a diagram that shows a state machine for some element. A state machine is composed of states and transitions. States may be divided into substates.
The name of the diagram.
A textual description of the element.
An element of one of the following kinds:
Final State (Final State)
A special kind of state signifying that the enclosing region is completed.
If the enclosing region is directly contained in a state machine and all other regions in the state machine also are completed, then it means that the entire state machine is completed.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
State (State)
A state models a situation during which some (usually implicit) invariant condition holds.
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.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Structure DiagramA Structure Diagram is a diagram that shows the static structure of an element.
The name of the diagram.
A textual description of the element.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
Timing DiagramA Timing Diagram is a visual representation of timing constraints between a set of objects.
The name of the diagram.
A textual description of the element.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Use Case DiagramA Use-Case Diagram is a diagram that shows actors and use cases and their relationships. However a Use-Case Diagram may also show packages and all kind of classifier elements.
The name of the diagram.
A textual description of the element.
An element of one of the following kinds:
Activity (Activity)
An activity is the specification of parameterized behavior as the coordinated sequencing of subordinate units whose individual elements are actions.
Actor (Actor)
An actor specifies a role played by a user or any other system that interacts with the subject.
Artifact (Artifact)
An artifact is the specification of a physical piece of information that is used or produced by a software development process, or by deployment and operation of a system.
Examples of artifacts include model files, source files, scripts, and binary executable files, a table in a database system, a development deliverable, or a word-processing document, a mail message. An artifact is the source of a deployment to a node.
Association (Association)
An association describes a set of tuples whose values refer to typed instances. An instance of an association is called a link.
Class (Class)
A class describes a set of objects that share the same specifications of features, constraints, and semantics.
A class may be designated as active (i.e., each of its instances having its own thread of control) or passive (i.e., each of its instances executing within the context of some other object).
A class may also specify which signals the instances of this class handle. A class has the capability to have an internal structure and ports. Class has derived association that indicates how it may be extended through one or more stereotypes. Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
Collaboration (Collaboration)
A collaboration defines a set of co-operating roles used collectively to illustrate a specific functionality.
A collaboration should only show the roles and attributes required to accomplish its defined task or function. Isolating the primary roles is an exercise in simplifying the structure and clarifying the behavior, and also provides for re-use. A collaboration often implements a pattern.
Communication Path (Communication Path)
A communication path is an association between two deployment targets, through which they are able to exchange signals and messages.
Component (Component)
A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment.
In the namespace of a component, all model elements that are involved in or related to its definition are either owned or imported explicitly. This may include, for example, use cases and dependencies (e.g. mappings), packages, components, and artifacts.
Data Type (Data Type)
A data type is a type whose instances are identified only by their value. A data type may contain attributes to support the modeling of structured data types.
Deployment Specification (Deployment Specification)
A deployment specification specifies a set of properties that determine execution parameters of a component artifact that is deployed on a node.
A deployment specification can be aimed at a specific type of container. An artifact that reifies or implements deployment specification properties is a deployment descriptor.
Device (Device)
A device is a physical computational resource with processing capability upon which artifacts may be deployed for execution.
Devices may be complex (i.e., they may consist of other devices).
Enumeration (Enumeration)
An enumeration is a data type whose values are enumerated in the model as enumeration literals.
Execution Environment (Execution Environment)
An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
Extension (Extension)
An extension is used to indicate that the properties of a metaclass are extended through a stereotype, and gives the ability to flexibly add (and later remove) stereotypes to classes.
Information Item (Information Item)
An information item is an abstraction of all kinds of information that can be exchanged between objects. It is a kind of
classifier intended for representing information in a very abstract way, one which cannot be instantiated.
Interaction (Interaction)
An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements.
Interface (Interface)
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations.
An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract.
The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.
Interfaces may include receptions (in addition to operations). Since an interface specifies conformance characteristics, it does not own detailed behavior specifications. Instead, interfaces may own a protocol state machine that specifies event sequences and pre/post conditions for the operations and receptions described by the interface.
Model (Model)
A model captures a view of a physical system. It is an abstraction of the physical system, with a certain purpose.
This purpose determines what is to be included in the model and what is irrelevant. Thus the model completely describes those aspects of the physical system that are relevant to the purpose of the model, at the appropriate level of detail.
Node (Node)
A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures.
Opaque Behavior (Opaque Behavior)
An behavior with implementation-specific semantics.
Package (Package)
A package is used to group elements, and provides a namespace for the grouped elements.
A package can have one or more profile applications to indicate which profiles have been applied.
Primitive Type (Primitive Type)
A primitive type defines a predefined data type, without any relevant substructure (i.e., it has no parts in the context of UML). A primitive datatype may have an algebra and operations defined outside of UML, for example, mathematically.
Profile (Profile)
A profile defines limited extensions to a reference metamodel with the purpose of adapting the metamodel to a specific platform or domain.
Protocol (Protocol)
Only available together with the Real-Time Extension of RSA.
Protocol State Machine (Protocol State Machine)
A protocol state machine is always defined in the context of a classifier. It specifies which operations of the classifier can be called in which state and under which condition, thus specifying the allowed call sequences on the classifier's operations.
A protocol state machine presents the possible and permitted transitions on the instances of its context classifier, together with the operations which carry the transitions. In this manner, an instance lifecycle can be created for a classifier, by specifying the order in which the operations can be activated and the states through which an instance progresses during its existence.
Signal (Signal)
A signal is a specification of send request instances communicated between objects. The receiving object handles the received request instances as specified by its receptions. The data carried by a send request (which was passed to it by the send invocation occurrence that caused that request) are represented as attributes of the signal.
A signal is defined independently of the classifiers handling the signal occurrence.
State Machine (State Machine)
State machines can be used to express the behavior of part of a system.
Behavior is modeled as a traversal of a graph of state nodes interconnected by one or more joined transition arcs that are triggered by the dispatching of series of (event) occurrences. During this traversal, the state machine executes a series of activities associated with various elements of the state machine.
Stereotype (Stereotype)
A stereotype defines how an existing metaclass 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.
Use Case (Use Case)
A use case is the specification of a set of actions performed by a system, which yields an observable result that is, typically, of value for one or more actors or other stakeholders of the system.
Activity (Activity)Actor (Actor)Artifact (Artifact)Association (Association)Call Event (Call Event)Class (Class)Collaboration (Collaboration)Communication Path (Communication Path)Component (Component)Constraint (Constraint)Data Type (Data Type)Deployment Specification (Deployment Specification)Device (Device)Enumeration (Enumeration)Enumeration Literal (Enumeration Literal)Execution Environment (Execution Environment)Extension (Extension)Information Item (Information Item)Instance Specification (Instance Specification)Interaction (Interaction)Interface (Interface)Model (Model)Node (Node)Opaque Behavior (Opaque Behavior)Package (Package)Primitive Type (Primitive Type)Profile (Profile)Protocol (Protocol)Protocol State Machine (Protocol State Machine)Signal (Signal)State Machine (State Machine)Stereotype (Stereotype)Use Case (Use Case)Model Guidelines generated by ![[Adocus_icon_small]](images/Adocus_icon_small.png){kind=icon} Adocus ![[MetaModelAgent_small]](images/MetaModelAgent_small.png) MetaModelAgent version 4.2.0.007
| Tuesday, 14 February 2017 15:17 |