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.

• Abstract: The value can be anything.

  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.

• Leaf: The value shall be non-empty.

  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.

Rules

• Arbitrary number of elements of the following kinds:
  • 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.

Rules

• Arbitrary number of elements of the following kinds:
  • 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.

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.

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

• Can be the value of the Type property of elements of the following kinds:
  • 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)
• Can be the Target of elements of the following kinds:
  • 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)