Rules

• Name: The value can be anything.

  The name of the item.

• Keywords: The value can be anything.

  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.

• Stereotypes: The value can be anything.

  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.

• Documentation: The value can be anything.

  A textual description of the element.

• Visibility: The value shall be a valid literal from the enumeration Visibility Kind.

  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.

Rules

• Arbitrary number of Activity Partition (Activity Partition)

  An activity partition is a kind of activity group for identifying actions that have some characteristic in common.

Rules

• Arbitrary number of elements of the following kinds:
  • Control Flow (Control Flow)
  • Object Flow (Object Flow)

Rules

• Arbitrary number of elements of the following 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)

Rules

• Arbitrary number of elements 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.

  • 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.

• Can be the Target of elements of the following kinds:
  • Abstraction (Abstraction)
  • Dependency (Dependency)
  • Information Flow (Information Flow)
  • Realization (Realization)
  • Substitution (Substitution)
  • Usage (Usage)