An integer is a primitive type representing integer values. A Boolean type is used for logical expression, consisting of the predefined values true and false. A string is a sequence of characters in some suitable character set used to display information about the model. Character sets may include non-Roman alphabets and characters. An unlimited natural is a primitive type representing unlimited natural values. A comment is a textual annotation that can be attached to a set of elements. Specifies a string that is the comment. References the Element(s) being commented. A directed relationship represents a relationship between a collection of source model elements and a collection of target model elements. Specifies the sources of the DirectedRelationship. Specifies the targets of the DirectedRelationship. A literal specification identifies a literal constant being modeled. A literal integer is a specification of an integer value. The specified Integer value. The query isComputable() is redefined to be true. OCL result = true The query integerValue() gives the value. OCL result = value A literal string is a specification of a string value. The specified String value. The query isComputable() is redefined to be true. OCL result = true The query stringValue() gives the value. OCL result = value A literal Boolean is a specification of a Boolean value. The specified Boolean value. The query isComputable() is redefined to be true. OCL result = true The query booleanValue() gives the value. OCL result = value A literal null specifies the lack of a value. The query isComputable() is redefined to be true. OCL result = true The query isNull() returns true. OCL result = true A constraint is a condition or 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 cannot be applied to itself. OCL not constrainedElement->includes(self) The value specification for a constraint must evaluate to a Boolean value. OCL self.specification().booleanValue().isOclKindOf(Boolean) The value specification for a constraint must evaluate to a Boolean value. OCL true Evaluating the value specification for a constraint must not have side effects. OCL true A constraint cannot be applied to itself. OCL not constrainedElement->includes(self) The ordered set of Elements referenced by this Constraint. A condition that must be true when evaluated in order for the constraint to be satisfied. Specifies the namespace that owns the NamedElement. An element import identifies an element in another package, and allows the element to be referenced using its name without a qualifier. The visibility of an ElementImport is either public or private. OCL self.visibility = #public or self.visibility = #private An importedElement has either public visibility or no visibility at all. OCL self.importedElement.visibility.notEmpty() implies self.importedElement.visibility = #public 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. Specifies the name that should be added to the namespace of the importing package in lieu of the name of the imported packagable element. The aliased name must not clash with any other member name in the importing package. By default, no alias is used. Specifies the PackageableElement whose name is to be added to a Namespace. Specifies the Namespace that imports a PackageableElement from another Package. The query getName() returns the name under which the imported PackageableElement will be known in the importing namespace. OCL result = if self.alias->notEmpty() then self.alias else self.importedElement.name endif A typed element is a kind of named element that represents an element with a type. A typed element has a type. This information is derived from the return result for this Operation. The type of the TypedElement. A feature declares a behavioral or structural characteristic of instances of classifiers. Specifies whether this feature characterizes individual instances classified by the classifier (false) or the classifier itself (true). The Classifiers that have this Feature as a feature. A redefinable element is an element that, when defined in the context of a classifier, can be redefined more specifically or differently in the context of another classifier that specializes (directly or indirectly) the context classifier. At least one of the redefinition contexts of the redefining element must be a specialization of at least one of the redefinition contexts for each redefined element. OCL self.redefinedElement->forAll(e | self.isRedefinitionContextValid(e)) A redefining element must be consistent with each redefined element. OCL self.redefinedElement->forAll(re | re.isConsistentWith(self)) Indicates whether it is possible to further specialize a RedefinableElement. If the value is true, then it is not possible to further specialize the RedefinableElement. The redefinable element that is being redefined by this element. References the contexts that this element may be redefined from. The query isConsistentWith() specifies, for any two RedefinableElements in a context in which redefinition is possible, whether redefinition would be logically consistent. By default, this is false; this operation must be overridden for subclasses of RedefinableElement to define the consistency conditions. OCL redefinee.isRedefinitionContextValid(self) OCL result = false The query isRedefinitionContextValid() specifies whether the redefinition contexts of this RedefinableElement are properly related to the redefinition contexts of the specified RedefinableElement to allow this element to redefine the other. By default at least one of the redefinition contexts of this element must be a specialization of at least one of the redefinition contexts of the specified element. OCL result = redefinitionContext->exists(c | c.allParents()->includes(redefined.redefinitionContext))) 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. Indicates whether the specific classifier can be used wherever the general classifier can be used. If true, the execution traces of the specific classifier will be a superset of the execution traces of the general classifier. References the specializing classifier in the Generalization relationship. References the general classifier in the Generalization relationship. A parameter is a specification of an argument used to pass information into or out of an invocation of a behavioral feature. Indicates whether a parameter is being sent into or out of a behavioral element. Specifies a String that represents a value to be used when no argument is supplied for the Parameter. Specifies a ValueSpecification that represents a value to be used when no argument is supplied for the Parameter. References the Operation owning this parameter. A structural feature is a typed feature of a classifier that specifies the structure of instances of the classifier. By specializing multiplicity element, it supports a multiplicity that specifies valid cardinalities for the collection of values associated with an instantiation of the structural feature. States whether the feature's value may be modified by a client. A slot specifies that an entity modeled by an instance specification has a value or values for a specific structural feature. The instance specification that owns this slot. The structural feature that specifies the values that may be held by the slot. The value or values corresponding to the defining feature for the owning instance specification. A package import is a relationship that allows the use of unqualified names to refer to package members from other namespaces. The visibility of a PackageImport is either public or private. OCL self.visibility = #public or self.visibility = #private 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. Specifies the Namespace that imports the members from a Package. Specifies the Package whose members are imported into a Namespace. 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. The Attributes owned by the DataType. The Operations owned by the DataType. The inherit operation is overridden to exclude redefined properties. OCL result = inhs->excluding(inh | ownedMember->select(oclIsKindOf(RedefinableElement))->select(redefinedElement->includes(inh))) An enumeration is a data type whose values are enumerated in the model as enumeration literals. The ordered set of literals for this Enumeration. An enumeration literal is a user-defined data value for an enumeration. The Enumeration that this EnumerationLiteral is a member of. 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. An association describes a set of tuples whose values refer to typed instances. An instance of an association is called a link. An association specializing another association has the same number of ends as the other association. OCL self.parents()->forAll(p | p.memberEnd.size() = self.memberEnd.size()) When an association specializes another association, every end of the specific association corresponds to an end of the general association, and the specific end reaches the same type or a subtype of the more general end. OCL true Only binary associations can be aggregations. OCL self.memberEnd->exists(aggregation <> Aggregation::none) implies self.memberEnd->size() = 2 Association ends of associations with more than two ends must be owned by the association. OCL if memberEnd->size() > 2 then ownedEnd->includesAll(memberEnd) Specifies whether the association is derived from other model elements such as other associations or constraints. The ends that are owned by the association itself. References the classifiers that are used as types of the ends of the association. Each end represents participation of instances of the classifier connected to the end in links of the association. The navigable ends that are owned by the association itself. endType is derived from the types of the member ends. OCL result = self.memberEnd->collect(e | e.type) A value specification is the specification of a (possibly empty) set of instances, including both objects and data values. The query isComputable() determines whether a value specification can be computed in a model. This operation cannot be fully defined in OCL. A conforming implementation is expected to deliver true for this operation for all value specifications that it can compute, and to compute all of those for which the operation is true. A conforming implementation is expected to be able to compute the value of all literals. OCL result = false The query integerValue() gives a single Integer value when one can be computed. OCL result = Set{} The query booleanValue() gives a single Boolean value when one can be computed. OCL result = Set{} The query stringValue() gives a single String value when one can be computed. OCL result = Set{} The query unlimitedValue() gives a single UnlimitedNatural value when one can be computed. OCL result = Set{} The query isNull() returns true when it can be computed that the value is null. OCL result = false Relationship is an abstract concept that specifies some kind of relationship between elements. Specifies the elements related by the Relationship. A package merge defines how the contents of one package are extended by the contents of another package. References the Package that is being extended with the contents of the merged package of the PackageMerge. References the Package that is to be merged with the receiving package of the PackageMerge. An instance value is a value specification that identifies an instance. The instance that is the specified value. A literal unlimited natural is a specification of an unlimited natural number. The specified UnlimitedNatural value. The query isComputable() is redefined to be true. OCL result = true The query unlimitedValue() gives the value. OCL result = value A type is a named element that is used as the type for a typed element. A type can be contained in a package. A type constrains the values represented by a typed element. Specifies the owning package of this classifier, if any. The query conformsTo() gives true for a type that conforms to another. By default, two types do not conform to each other. This query is intended to be redefined for specific conformance situations. OCL result = false An expression is a structured tree of symbols that denotes a (possibly empty) set of values when evaluated in a context. An expression represents a node in an expression tree, which may be non-terminal or terminal. It defines a symbol, and has a possibly empty sequence of operands which are value specifications. The symbol associated with the node in the expression tree. Specifies a sequence of operands. AggregationKind is an enumeration type that specifies the literals for defining the kind of aggregation of a property. Indicates that the property has no aggregation. Indicates that the property has a shared aggregation. Indicates that the property is aggregated compositely, i.e., the composite object has responsibility for the existence and storage of the composed objects (parts). Parameter direction kind is an enumeration type that defines literals used to specify direction of parameters. Indicates that parameter values are passed into the behavioral element by the caller. Indicates that parameter values are passed into a behavioral element by the caller and then back out to the caller from the behavioral element. Indicates that parameter values are passed from a behavioral element out to the caller. Indicates that parameter values are passed as return values from a behavioral element back to the caller. VisibilityKind is an enumeration type that defines literals to determine the visibility of elements in a model. The query bestVisibility() examines a set of VisibilityKinds, and returns public as the preferred visibility. OCL pre: not vis->includes(#protected) and not vis->includes(#package) OCL result = if vis->includes(#public) then #public else #private endif A public element is visible to all elements that can access the contents of the namespace that owns it. A private element is only visible inside the namespace that owns it. A protected element is visible to elements that have a generalization relationship to the namespace that owns it. A package element is owned by a namespace that is not a package, and is visible to elements that are in the same package as its owning namespace. Only named elements that are not owned by packages can be marked as having package visibility. Any element marked as having package visibility is visible to all elements within the nearest enclosing package (given that other owning elements have proper visibility). Outside the nearest enclosing package, an element marked as having package visibility is not visible. Behavior is a specification of how its context classifier changes state over time. This specification may be either a definition of possible behavior execution or emergent behavior, or a selective illustration of an interesting subset of possible executions. The latter form is typically used for capturing examples, such as a trace of a particular execution. The parameters of the behavior must match the parameters of the implemented behavioral feature. OCL true The implemented behavioral feature must be a feature (possibly inherited) of the context classifier of the behavior. OCL true If the implemented behavioral feature has been redefined in the ancestors of the owner of the behavior, then the behavior must realize the latest redefining behavioral feature. OCL true There may be at most one behavior for a given pairing of classifier (as owner of the behavior) and behavioral feature (as specification of the behavior). OCL true Tells whether the behavior can be invoked while it is still executing from a previous invocation. References a behavior that this behavior redefines. A subtype of Behavior may redefine any other subtype of Behavior. If the behavior implements a behavioral feature, it replaces the redefined behavior. If the behavior is a classifier behavior, it extends the redefined behavior. 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). References a list of parameters to the behavior which describes the order and type of arguments that can be given when the behavior is invoked and of the values which will be returned when the behavior completes its 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 optional set of Constraints specifying what must be fulfilled when the behavior is invoked. An optional set of Constraints specifying what is fulfilled after the execution of the behavior is completed, if its precondition was fulfilled before its invocation. An opaque expression is an uninterpreted textual statement that denotes a (possibly empty) set of values when evaluated in a context. Provides a mechanism for precisely defining the behavior of an opaque expression. An opaque expression is defined by a behavior restricted to return one result. If the language attribute is not empty, then the size of the body and language arrays must be the same. OCL language->notEmpty() implies (body->size() = language->size()) The behavior may only have return result parameters. OCL self.behavior.notEmpty() implies self.behavior.ownedParameters->select(p | p.direction<>#return)->isEmpty() The behavior must have exactly one return result parameter. OCL self.behavior.notEmpty() implies self.behavior.ownedParameter->select(p | p.direction=#return)->size() = 1 The text of the expression, possibly in multiple languages. Specifies the languages in which the expression 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. Languages are matched to body strings by order. Restricts an opaque expression to return exactly one return result. When the invocation of the opaque expression completes, a single set of values is returned to its owner. This association is derived from the single return result parameter of the associated behavior. Specifies the behavior of the opaque expression. The query value() gives an integer value for an expression intended to produce one. OCL self.isIntegral() OCL true The query isIntegral() tells whether an expression is intended to produce an integer. OCL result = false The query isPositive() tells whether an integer expression has a positive value. OCL self.isIntegral() OCL result = false The query isNonNegative() tells whether an integer expression has a non-negative value. OCL self.isIntegral() OCL result = false An behavior with implementation-specific semantics. Specifies the behavior in one or more languages. Languages the body strings use in the same order as the body strings. A function behavior is an opaque behavior that does not access or modify any objects or other external data. A function behavior has at least one output parameter. OCL self.ownedParameters-> select(p | p.direction=#out or p.direction=#inout or p.direction=#return)->size() >= 1 The types of parameters are all data types, which may not nest anything but other datatypes. OCL def: hasAllDataTypeAttributes(d : DataType) : Boolean = d.ownedAttribute->forAll(a | a.type.oclIsTypeOf(DataType) and hasAllDataTypeAttributes(a.type)) self.ownedParameters->forAll(p | p.type.notEmpty() and p.oclIsTypeOf(DataType) and hasAllDataTypeAttributes(p)) An action with implementation-specific semantics. Specifies the action in one or more languages. Languages the body strings use, in the same order as the body strings Provides input to the action. Takes output from the action. CallAction is an abstract class for actions that invoke behavior and receive return values. Only synchronous call actions can have result pins. OCL true The number and order of argument pins must be the same as the number and order of parameters of the invoked behavior or behavioral feature. Pins are matched to parameters by order. OCL true The type, ordering, and multiplicity of an argument pin must be the same as the corresponding parameter of the behavior or behavioral feature. OCL true If true, the call is synchronous and the caller waits for completion of the invoked behavior. If false, the call is asynchronous and the caller proceeds immediately and does not expect a return values. A list of output pins where the results of performing the invocation are placed. 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 number and order of argument pins must be the same as the number and order of attributes in the signal. OCL true The type, ordering, and multiplicity of an argument pin must be the same as the corresponding attribute of the signal. OCL true The target object to which the signal is sent. The type of signal transmitted to the target object. 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 number of argument pins and the number of owned parameters of the operation of type in and in-out must be equal. OCL true The number of result pins and the number of owned parameters of the operation of type return, out, and in-out must be equal. OCL true The type, ordering, and multiplicity of an argument or result pin is derived from the corresponding owned parameter of the operation. OCL true The type of the target pin must be the same as the type that owns the operation. OCL true The operation to be invoked by the action execution. The target object to which the request is sent. The classifier of the target object is used to dynamically determine a behavior to invoke. This object constitutes the context of the execution of the operation. 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 number of argument pins and the number of parameters of the behavior of type in and in-out must be equal. OCL true The number of result pins and the number of parameters of the behavior of type return, out, and in-out must be equal. OCL true The type, ordering, and multiplicity of an argument or result pin is derived from the corresponding parameter of the behavior. OCL true The invoked behavior. It must be capable of accepting and returning control. A multiplicity is a definition of an inclusive interval of non-negative integers beginning with a lower bound and ending with a (possibly infinite) upper bound. A multiplicity element embeds this information to specify the allowable cardinalities for an instantiation of this element. A multiplicity must define at least one valid cardinality that is greater than zero. OCL upperBound()->notEmpty() implies upperBound() > 0 The lower bound must be a non-negative integer literal. OCL lowerBound()->notEmpty() implies lowerBound() >= 0 The upper bound must be greater than or equal to the lower bound. OCL (upperBound()->notEmpty() and lowerBound()->notEmpty()) implies upperBound() >= lowerBound() If a non-literal ValueSpecification is used for the lower or upper bound, then evaluating that specification must not have side effects. OCL true If a non-literal ValueSpecification is used for the lower or upper bound, then that specification must be a constant expression. OCL true 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. Specifies the upper bound of the multiplicity interval. Specifies the lower bound of the multiplicity interval. The specification of the upper bound for this multiplicity. The specification of the lower bound for this multiplicity. The derived lower attribute must equal the lowerBound. OCL result = lowerBound() The derived upper attribute must equal the upperBound. OCL result = upperBound() The query isMultivalued() checks whether this multiplicity has an upper bound greater than one. OCL upperBound()->notEmpty() OCL result = upperBound() > 1 The query includesCardinality() checks whether the specified cardinality is valid for this multiplicity. OCL upperBound()->notEmpty() and lowerBound()->notEmpty() OCL result = (lowerBound() <= C) and (upperBound() >= C) The query includesMultiplicity() checks whether this multiplicity includes all the cardinalities allowed by the specified multiplicity. OCL self.upperBound()->notEmpty() and self.lowerBound()->notEmpty() and M.upperBound()->notEmpty() and M.lowerBound()->notEmpty() OCL result = (self.lowerBound() <= M.lowerBound()) and (self.upperBound() >= M.upperBound()) The query lowerBound() returns the lower bound of the multiplicity as an integer. OCL result = if lowerValue->isEmpty() then 1 else lowerValue.integerValue() endif The query upperBound() returns the upper bound of the multiplicity for a bounded multiplicity as an unlimited natural. OCL result = if upperValue->isEmpty() then 1 else upperValue.unlimitedValue() endif The operation compatibleWith takes another multiplicity as input. It checks if one multiplicity is compatible with another. OCL result = Integer.allInstances()->forAll(i : Integer | self.includesCardinality(i) implies other.includesCardinality(i)) The operation is determines if the upper and lower bound of the ranges are the ones given. OCL result = (lowerbound = self.lowerbound and upperbound = self.upperbound) An object node is an abstract activity node that is part of defining object flow in an activity. All edges coming into or going out of object nodes must be object flow edges. OCL true Object nodes are not unique typed elements OCL isUnique = false A control node is an abstract activity node that coordinates flows in an activity. A control flow is an edge that starts an activity node after the previous one is finished. Control flows may not have object nodes at either end, except for object nodes with control type. OCL true An object flow is an activity edge that can have objects or data passing along it. Object flows may not have actions at either end. OCL true Object nodes connected by an object flow, with optionally intervening control nodes, must have compatible types. In particular, the downstream object node type must be the same or a supertype of the upstream object node type. OCL true Object nodes connected by an object flow, with optionally intervening control nodes, must have the same upper bounds. OCL true An initial node is a control node at which flow starts when the activity is invoked. An initial node has no incoming edges. OCL true Only control edges can have initial nodes as source. OCL true An activity parameter node is an object node for inputs and outputs to activities. Activity parameter nodes must have parameters from the containing activity. OCL true The type of an activity parameter node is the same as the type of its parameter. OCL true An activity parameter node may have all incoming edges or all outgoing edges, but it must not have both incoming and outgoing edges. OCL true Activity parameter object nodes with no incoming edges and one or more outgoing edges must have a parameter with in or inout direction. OCL true Activity parameter object nodes with no outgoing edges and one or more incoming edges must have a parameter with out, inout, or return direction. OCL true The parameter the object node will be accepting or providing values for. A pin is a typed element and multiplicity element that provides values to actions and accept result values from them. A pin is an object node for inputs and outputs to actions. A value pin is an input pin that provides a value by evaluating a value specification. The type of value specification must be compatible with the type of the value pin. OCL true Value pins have no incoming edges. OCL true Value that the pin will provide. 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. 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. An composition of an Expression that states the abstraction relationship between the supplier and the client. In some cases, such as Derivation, it is usually formal and unidirectional; in other cases, such as Trace, it is usually informal and bidirectional. The mapping expression is optional and may be omitted if the precise relationship between the elements is not specified. 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). The element(s) independent of the client element(s), in the same respect and the same dependency relationship. In some directed dependency relationships (such as Refinement Abstractions), a common convention in the domain of class-based OO software is to put the more abstract element in this role. Despite this convention, users of UML may stipulate a sense of dependency suitable for their domain, which makes a more abstract element dependent on that which is more specific. The element(s) dependent on the supplier element(s). In some cases (such as a Trace Abstraction) the assignment of direction (that is, the designation of the client element) is at the discretion of the modeler, and is a stipulation. 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. 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. The contract with which the substituting classifier complies. Instances of the substituting classifier are runtime substitutable where instances of the contract classifier are expected. A packageable element indicates a named element that may be owned directly by a package. Indicates that packageable elements must always have a visibility, i.e., visibility is not optional. A namespace is an element in a model that contains a set of named elements that can be identified by name. All the members of a Namespace are distinguishable within it. OCL membersAreDistinguishable() References the ElementImports owned by the Namespace. References the PackageImports owned by the Namespace. Specifies a set of Constraints owned by this Namespace. A collection of NamedElements identifiable within the Namespace, either by being owned or by being introduced by importing or inheritance. References the PackageableElements that are members of this Namespace as a result of either PackageImports or ElementImports. A collection of NamedElements owned by the Namespace. The importedMember property is derived from the ElementImports and the PackageImports. References the PackageableElements that are members of this Namespace as a result of either PackageImports or ElementImports. OCL result = self.importMembers(self.elementImport.importedElement.asSet()- >union(self.packageImport.importedPackage->collect(p | p.visibleMembers()))) The query getNamesOfMember() takes importing into account. It gives back the set of names that an element would have in an importing namespace, either because it is owned, or if not owned then imported individually, or if not individually then from a package. The query getNamesOfMember() gives a set of all of the names that a member would have in a Namespace. In general a member can have multiple names in a Namespace if it is imported more than once with different aliases. The query takes account of importing. It gives back the set of names that an element would have in an importing namespace, either because it is owned, or if not owned then imported individually, or if not individually then from a package. OCL result = if self.ownedMember ->includes(element) then Set{}->include(element.name) else let elementImports: ElementImport = self.elementImport->select(ei | ei.importedElement = element) in if elementImports->notEmpty() then elementImports->collect(el | el.getName()) else self.packageImport->select(pi | pi.importedPackage.visibleMembers()->includes(element))-> collect(pi | pi.importedPackage.getNamesOfMember(element)) endif endif The Boolean query membersAreDistinguishable() determines whether all of the namespace's members are distinguishable within it. OCL result = self.member->forAll( memb | self.member->excluding(memb)->forAll(other | memb.isDistinguishableFrom(other, self))) The query importMembers() defines which of a set of PackageableElements are actually imported into the namespace. This excludes hidden ones, i.e., those which have names that conflict with names of owned members, and also excludes elements which would have the same name when imported. OCL result = self.excludeCollisions(imps)->select(imp | self.ownedMember->forAll(mem | mem.imp.isDistinguishableFrom(mem, self))) The query excludeCollisions() excludes from a set of PackageableElements any that would not be distinguishable from each other in this namespace. OCL result = imps->reject(imp1 | imps.exists(imp2 | not imp1.isDistinguishableFrom(imp2, self))) Indicates the dependencies that reference the supplier. 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. References the Interface specifying the conformance contract. References the BehavioredClassifier that owns this Interfacerealization (i.e., the classifier that realizes the Interface to which it points). A structured classifier is an abstract metaclass that represents any classifier whose behavior can be fully or partly described by the collaboration of owned or referenced instances. The multiplicities on connected elements must be consistent. OCL true References the properties owned by the classifier. References the properties specifying instances that the classifier owns by composition. This association is derived, selecting those owned properties where isComposite is true. References the roles that instances may play in this classifier. References the connectors owned by the classifier. ConnectableElement is an abstract metaclass representing a set of instances that play roles of a classifier. Connectable elements may be joined by attached connectors and specify configurations of linked instances to be created within an instance of the containing classifier. Denotes a connector that attaches to this connectable element. A message defines a particular communication between lifelines of an interaction. If the sending MessageEvent and the receiving MessageEvent of the same Message are on the same Lifeline, the sending MessageEvent must be ordered before the receiving MessageEvent. OCL true The signature must either refer an Operation (in which case messageSort is either synchCall or asynchCall) or a Signal (in which case messageSort is asynchSignal). The name of the NamedElement referenced by signature must be the same as that of the Message. OCL true In the case when the Message signature is an Operation, the arguments of the Message must correspond to the parameters of the Operation. A Parameter corresponds to an Argument if the Argument is of the same Class or a specialization of that of the Parameter. OCL true In the case when the Message signature is a Signal, the arguments of the Message must correspond to the attributes of the Signal. A Message Argument corresponds to a Signal Attribute if the Arguement is of the same Class or a specialization of that of the Attribute. OCL true Arguments of a Message must only be: i) attributes of the sending lifeline ii) constants iii) symbolic values (which are wildcard values representing any legal value) iv) explicit parameters of the enclosing Interaction v) attributes of the class owning the Interaction OCL true Messages cannot cross bounderies of CombinedFragments or their operands. OCL true If the MessageEnds are both OccurrenceSpecifications then the connector must go between the Parts represented by the Lifelines of the two MessageEnds. OCL true The derived kind of the Message (complete, lost, found or unknown) The sort of communication reflected by the Message References the Receiving of the Message References the Sending of the Message. The Connector on which this Message is sent. The enclosing Interaction owning the Message The arguments 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. A general ordering represents a binary relation between two occurrence specifications, to describe that one occurrence specification must occur before the other in a valid trace. This mechanism provides the ability to define partial orders of occurrence cpecifications that may otherwise not have a specified order. The OccurrenceSpecification referenced comes before the OccurrenceSpecification referenced by after. The OccurrenceSpecification referenced comes after the OccurrenceSpecification referenced by before. An execution specification is a specification of the execution of a unit of behavior or action within the lifeline. The duration of an execution specification is represented by two cccurrence specifications, the start occurrence specification and the finish occurrence specification. The startEvent and the finishEvent must be on the same Lifeline OCL start.lifeline = finish.lifeline References the OccurrenceSpecification that designates the start of the Action or Behavior References the OccurrenceSpecification that designates the finish of the Action or Behavior. An occurrence specification is the basic semantic unit of interactions. The sequences of occurrences specified by them are the meanings of interactions. References the Lifeline on which the OccurrenceSpecification appears. References the GeneralOrderings that specify EventOcurrences that must occur after this OccurrenceSpecification References the GeneralOrderings that specify EventOcurrences that must occur before this OccurrenceSpecification References a specification of the occurring event. MessageEnd is an abstract specialization of NamedElement that represents what can occur at the end of a message. References a Message. A state invariant is a runtime constraint on the participants of the interaction. It may be used to specify a variety of different kinds of constraints, such as values of attributes or variables, internal or external states, and so on. A state invariant is an interaction fragment and it is placed on a lifeline. A Constraint that should hold at runtime for this StateInvariant References the Lifeline on which the StateInvariant appears. An action execution specification is a kind of execution specification representing the execution of an action. The Action referenced by the ActionExecutionSpecification, if any, must be owned by the Interaction owning the ActionExecutionOccurrence. OCL true Action whose execution is occurring. A behavior execution specification is a kind of execution specification representing the execution of a behavior. Behavior whose execution is occurring. An execution event models the start or finish of an execution occurrence. A creation event models the creation of an object. No othet OccurrenceSpecification may appear above an OccurrenceSpecification which references a CreationEvent on a given Lifeline in an InteractionOperand. OCL true A destruction event models the destruction of an object. No other OccurrenceSpecifications may appear below an OccurrenceSpecification which references a DestructionEvent on a given Lifeline in an InteractionOperand. OCL true A send operation event models the invocation of an operation call. The operation associated with this event. A send signal event models the sending of a signal. The signal associated with this event. A message occurrence specification pecifies the occurrence of message events, such as sending and receiving of signals or invoking or receiving of operation calls. A message occurrence specification is a kind of message end. Messages are generated either by synchronous operation calls or asynchronous signal sends. They are received by the execution of corresponding accept event actions. An execution occurrence specification represents moments in time at which actions or behaviors start or finish. References the execution specification describing the execution that is started or finished at this execution event. The event referenced is restricted to an execution event. A receive operation event specifies the event of receiving an operation invocation for a particular operation by the target entity. The operation associated with this event. A receive signal event specifies the event of receiving a signal by the target entity. The signal associated with this event. This is an enumerated type that identifies the type of message. sendEvent and receiveEvent are present sendEvent present and receiveEvent absent sendEvent absent and receiveEvent present sendEvent and receiveEvent absent (should not appear) This is an enumerated type that identifies the type of communication action that was used to generate the message. The message was generated by a synchronous call to an operation. The message was generated by an asynchronous call to an operation; i.e., a CallAction with isSynchronous = false. The message was generated by an asynchronous send action. The message designating the creation of another lifeline object. The message designating the termination of another lifeline. The message is a reply message to an operation call. This association shows the lifelines that make up an interaction. A lifeline may be part of more than one interaction use. The event shows the time point at which the action begins execution. The event shows the time point at which the action completes execution. If a Part has multiplicity, multiple lifelines might be used to show it. An actor specifies a role played by a user or any other system that interacts with the subject. An actor can only have associations to use cases, components and classes. Furthermore these associations must be binary. OCL self.ownedAttribute->forAll ( a | (a.association->notEmpty()) implies ((a.association.memberEnd.size() = 2) and (a.opposite.class.oclIsKindOf(UseCase) or (a.opposite.class.oclIsKindOf(Class) and not a.opposite.class.oclIsKindOf(Behavior)))) An actor must have a name. OCL name->notEmpty() 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. The extension points referenced by the extend relationship must belong to the use case that is being extended. OCL extensionLocation->forAll (xp | extendedCase.extensionPoint->includes(xp)) References the use case that is being extended. References the use case that represents the extension and owns the extend relationship. References the condition that must hold when the first extension point is reached for the extension to take place. If no constraint is associated with the extend relationship, the extension is unconditional. An ordered list of extension points belonging to the extended use case, specifying where the respective behavioral fragments of the extending use case are to be inserted. The first fragment in the extending use case is associated with the first extension point in the list, the second fragment with the second point, and so on. (Note that, in most practical cases, the extending use case has just a single behavior fragment, so that the list of extension points is trivial.) An include relationship defines that a use case contains the behavior defined in another use case. References the use case which will include the addition and owns the include relationship. References the use case that is to be included. 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. A UseCase must have a name. OCL self.name -> notEmpty () UseCases can only be involved in binary Associations. OCL true UseCases can not have Associations to UseCases specifying the same subject. OCL true A use case cannot include use cases that directly or indirectly include it. OCL not self.allIncludedUseCases()->includes(self) References the Include relationships owned by this use case. References the Extend relationships owned by this use case. References the ExtensionPoints owned by the use case. References the subjects to which this use case applies. The subject or its parts realize all the use cases that apply to this subject. Use cases need not be attached to any specific subject, however. The subject may, but need not, own the use cases that apply to it. The query allIncludedUseCases() returns the transitive closure of all use cases (directly or indirectly) included by this use case. OCL result = self.include->union(self.include->collect(in | in.allIncludedUseCases())) 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. An ExtensionPoint must have a name. OCL self.name->notEmpty () References the use case that owns this extension point. A classifier is a classification of instances - it describes a set of instances that have features in common. A classifier can specify a generalization hierarchy by referencing its general classifiers. A classifier has the capability to own collaboration uses. These collaboration uses link a collaboration with the classifier to give a description of the workings of the classifier. A classifier has the capability to own use cases. Although the owning classifier typically represents the subject to which the owned use cases apply, this is not necessarily the case. In principle, the same use case can be applied to multiple subjects, as identified by the subject association role of a use case. Generalization hierarchies must be directed and acyclical. A classifier can not be both a transitively general and transitively specific classifier of the same classifier. OCL not self.allParents()->includes(self) Generalization hierarchies must be directed and acyclical. A classifier can not be both a transitively general and transitively specific classifier of the same classifier. OCL not self.allParents()->includes(self) A classifier may only specialize classifiers of a valid type. OCL self.parents()->forAll(c | self.maySpecializeType(c)) 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 the Generalization relationships for this Classifier. These Generalizations navigaten to more general classifiers in the generalization hierarchy. Note that there may be members of the Classifier that are of the type Feature but are not included in this association, e.g. inherited features. Specifies each feature defined in the classifier. Specifies all elements inherited by this classifier from the general classifiers. References the Classifiers that are redefined by this Classifier. References the general classifier in the Generalization relationship. Specifies the general Classifiers for this Classifier. References the substitutions that are owned by this Classifier. Refers to all of the Properties that are direct (i.e. not inherited or imported) attributes of the classifier. References the use cases owned by this classifier. The set of use cases for which this Classifier is the subject. The general classifiers are the classifiers referenced by the generalization relationships. OCL result = self.parents() The inheritedMember association is derived by inheriting the inheritable members of the parents. OCL result = self.inherit(self.parents()->collect(p | p.inheritableMembers(self)) The query allFeatures() gives all of the features in the namespace of the classifier. In general, through mechanisms such as inheritance, this will be a larger set than feature. OCL result = member->select(oclIsKindOf(Feature)) The query parents() gives all of the immediate ancestors of a generalized Classifier. OCL result = generalization.general The query inheritableMembers() gives all of the members of a classifier that may be inherited in one of its descendants, subject to whatever visibility restrictions apply. OCL c.allParents()->includes(self) OCL result = member->select(m | c.hasVisibilityOf(m)) The query hasVisibilityOf() determines whether a named element is visible in the classifier. By default all are visible. It is only called when the argument is something owned by a parent. OCL self.allParents()->collect(c | c.member)->includes(n) OCL result = if (self.inheritedMember->includes(n)) then (n.visibility <> #private) else true The query conformsTo() gives true for a classifier that defines a type that conforms to another. This is used, for example, in the specification of signature conformance for operations. OCL result = (self=other) or (self.allParents()->includes(other)) The inherit operation is overridden to exclude redefined properties. The query inherit() defines how to inherit a set of elements. Here the operation is defined to inherit them all. It is intended to be redefined in circumstances where inheritance is affected by redefinition. OCL result = inhs The query maySpecializeType() determines whether this classifier may have a generalization relationship to classifiers of the specified type. By default a classifier may specialize classifiers of the same or a more general type. It is intended to be redefined by classifiers that have different specialization constraints. OCL result = self.oclIsKindOf(c.oclType) The query allParents() gives all of the direct and indirect ancestors of a generalized Classifier. OCL result = self.parents()->union(self.parents()->collect(p | p.allParents()) A behavioral feature is a feature of a classifier that specifies an aspect of the behavior of its instances. A behavioral feature is implemented (realized) by a behavior. A behavioral feature specifies that a classifier will respond to a designated request by invoking its implementing method. Specifies the ordered set of formal parameters of this BehavioralFeature. 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. A behavioral description that implements the behavioral feature. There may be at most one behavior for a particular pairing of a classifier (as owner of the behavior) and a behavioral feature (as specification of the behavior). 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. References the Types representing exceptions that may be raised during an invocation of this feature. The signals that the behavioral feature raises as exceptions. The query isDistinguishableFrom() determines whether two BehavioralFeatures may coexist in the same Namespace. It specifies that they have to have different signatures. OCL result = if n.oclIsKindOf(BehavioralFeature) then if ns.getNamesOfMember(self)->intersection(ns.getNamesOfMember(n))->notEmpty() then Set{}->including(self)->including(n)->isUnique(bf | bf.ownedParameter->collect(type)) else true endif else true endif A call event models the receipt by an object of a message invoking a call of an operation. Designates the operation whose invocation raised the call event. A change event models a change in the system configuration that makes a condition true. A Boolean-valued expression that will result in a change event whenever its value changes from false to true. 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). The visibility of all features owned by an interface must be public. OCL self.feature->forAll(f | f.visibility = #public) The attributes (i.e. the properties) owned by the class. The operations owned by the class. References all the Classifiers that are defined (nested) within the Class. References all the Interfaces redefined by this Interface. Receptions that objects providing this interface are willing to accept. 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. A Reception can not be a query. OCL not self.isQuery The signal that this reception handles. 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. The attributes owned by the signal. A signal event represents the receipt of an asynchronous signal instance. A signal event may, for example, cause a state machine to trigger a transition. The specific signal that is associated with this event. A message event specifies the receipt by an object of either a call or a signal. A transition trigger associated with an any receive event specifies that the transition is to be triggered by the receipt of any message that is not explicitly referenced in another transition from the same vertex. A behaviored classifier may have an interface realization. A classifier can have behavior specifications defined in its namespace. One of these may specify the behavior of the classifier itself. If a behavior is classifier behavior, it does not have a specification. OCL self.classifierBehavior.notEmpty() implies self.specification.isEmpty() References behavior specifications owned by a classifier. A behavior specification that specifies the behavior of the classifier itself. The set of InterfaceRealizations owned by the BehavioredClassifier. Interface realizations reference the Interfaces of which the BehavioredClassifier is an implementation. References Trigger descriptions owned by a Classifier. An event is the specification of some occurrence that may potentially trigger effects by an object. 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. An operation can have at most one return parameter; i.e., an owned parameter with the direction set to 'return' OCL self.ownedParameter->select(par | par.direction = #return)->size() <= 1 A bodyCondition can only be specified for a query operation. OCL bodyCondition->notEmpty() implies isQuery Specifies whether an execution of the BehavioralFeature leaves the state of the system unchanged (isQuery=true) or whether side effects may occur (isQuery=false). This information is derived from the return result for this Operation. Specifies whether the return parameter is ordered or not, if present. This information is derived from the return result for this Operation. Specifies whether the return parameter is unique or not, if present. This information is derived from the return result for this Operation. Specifies the lower multiplicity of the return parameter, if present. This information is derived from the return result for this Operation. Specifies the upper multiplicity of the return parameter, if present. The class that owns the operation. An optional set of Constraints on the state of the system when the Operation is invoked. An optional set of Constraints specifying the state of the system when the Operation is completed. References the Operations that are redefined by this Operation. The DataType that owns this Operation. An optional Constraint on the result values of an invocation of this Operation. This information is derived from the return result for this Operation. Specifies the return result of the operation, if present. Specifies the ordered set of formal parameters of this BehavioralFeature. Specifies the parameters owned by this Operation. References the Types representing exceptions that may be raised during an invocation of this operation. The Interface that owns this Operation. If this operation has a return parameter, isOrdered equals the value of isOrdered for that parameter. Otherwise isOrdered is false. OCL result = if returnResult()->notEmpty() then returnResult()->any().isOrdered else false endif If this operation has a return parameter, isUnique equals the value of isUnique for that parameter. Otherwise isUnique is true. OCL result = if returnResult()->notEmpty() then returnResult()->any().isUnique else true endif If this operation has a return parameter, lower equals the value of lower for that parameter. Otherwise lower is not defined. OCL result = if returnResult()->notEmpty() then returnResult()->any().lower else Set{} endif If this operation has a return parameter, upper equals the value of upper for that parameter. Otherwise upper is not defined. OCL result = if returnResult()->notEmpty() then returnResult()->any().upper else Set{} endif If this operation has a return parameter, type equals the value of type for that parameter. Otherwise type is not defined. OCL result = if returnResult()->notEmpty() then returnResult()->any().type else Set{} endif The query isConsistentWith() specifies, for any two Operations in a context in which redefinition is possible, whether redefinition would be consistent in the sense of maintaining type covariance. Other senses of consistency may be required, for example to determine consistency in the sense of contravariance. Users may define alternative queries under names different from 'isConsistentWith()', as for example, users may define a query named 'isContravariantWith()'. A redefining operation is consistent with a redefined operation if it has the same number of owned parameters, and the type of each owned parameter conforms to the type of the corresponding redefined parameter. OCL redefinee.isRedefinitionContextValid(self) OCL result = (redefinee.oclIsKindOf(Operation) and let op: Operation = redefinee.oclAsType(Operation) in self.ownedParameter.size() = op.ownedParameter.size() and forAll(i | op.ownedParameter[i].type.conformsTo(self.ownedParameter[i].type)) ) The query returnResult() returns the set containing the return parameter of the Operation if one exists, otherwise, it returns an empty set OCL result = ownedParameter->select (par | par.direction = #return) CallConcurrencyKind is an enumeration type. No concurrency management mechanism is associated with the operation and, therefore, concurrency conflicts may occur. Instances that invoke a behavioral feature need to coordinate so that only one invocation to a target on any behavioral feature occurs at once. Multiple invocations of a behavioral feature may occur simultaneously to one instance, but only one is allowed to commence. The others are blocked until the performance of the first behavioral feature is complete. It is the responsibility of the system designer to ensure that deadlocks do not occur due to simultaneous blocks. Multiple invocations of a behavioral feature may occur simultaneously to one instance and all of them may proceed concurrently. A fork node is a control node that splits a flow into multiple concurrent flows. A fork node has one incoming edge. OCL true The edges coming into and out of a fork node must be either all object flows or all control flows. OCL true A flow final node is a final node that terminates a flow. A central buffer node is an object node for managing flows from multiple sources and destinations. An activity partition is a kind of activity group for identifying actions that have some characteristic in common. A partition with isDimension = true may not be contained by another partition. OCL true If a partition represents a part, then all the non-external partitions in the same dimension and at the same level of nesting in that dimension must represent parts directly contained in the internal structure of the same classifier. OCL true If a non-external partition represents a classifier and is contained in another partition, then the containing partition must represent a classifier, and the classifier of the subpartition must be nested in the classifier represented by the containing partition, or be at the contained end of a strong composition association with the classifier represented by the containing partition. OCL true If a partition represents a part and is contained by another partition, then the part must be of a classifier represented by the containing partition, or of a classifier that is the type of a part representing the containing partition. OCL true Tells whether the partition groups other partitions along a dimension. Tells whether the partition represents an entity to which the partitioning structure does not apply. Edges immediately contained in the group. Nodes immediately contained in the group. Partitions immediately contained in the partition. Partition immediately containing the partition. An element constraining behaviors invoked by nodes in the partition. An activity edge is an abstract class for directed connections between two activity nodes. The source and target of an edge must be in the same activity as the edge. OCL true Activity edges may be owned only by activities or groups. OCL true Activity containing the edge. Node from which tokens are taken when they traverse the edge. Node to which tokens are put when they traverse the edge. Inherited edges replaced by this edge in a specialization of the activity. Partitions containing the edge. Specification evaluated at runtime to determine if the edge can be traversed. Groups containing the edge. 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. A merge node has one outgoing edge. OCL true The edges coming into and out of a merge node must be either all object flows or all control flows. OCL true A decision node is a control node that chooses between outgoing flows. A decision node has one incoming edge. OCL true A decision input behavior has zero or one input parameter and one output parameter. Any input parameter must be the same as or a supertype of the type of object tokens coming along the incoming edge. The behavior cannot have side effects. OCL true The edges coming into and out of a decision node must be either all object flows or all control flows. OCL true Provides input to guard specifications on edges outgoing from the decision node. A final node is an abstract control node at which a flow in an activity stops. A final node has no outgoing edges. OCL true An activity final node is a final node that stops all flows in an activity. A join node is a control node that synchronizes multiple flows. 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. The required interfaces of a port must be provided by elements to which the port is connected. OCL true Port.aggregation must be composite. OCL true When a port is destroyed, all connectors attached to this port will be destroyed also. OCL true A defaultValue for port cannot be specified when the type of the Port is an Interface OCL true 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 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. References the interfaces specifying the set of operations and receptions which the classifier expects its environment to handle. This association is derived as the set of interfaces required by the type of the port or its supertypes. A port may be redefined when its containing classifier is specialized. The redefining port may have additional interfaces to those that are associated with the redefined port or it may replace an interface by one of its subtypes. References the interfaces specifying the set of operations and receptions which the classifier offers to its environment, and which it will handle either directly or by forwarding it to a part of its internal structure. This association is derived from the interfaces realized by the type of the port or by the type of the port, if the port was typed by an interface. A classifier has the ability to own ports as specific and type checked interaction points. References a set of ports that an encapsulated classifier owns. A connector end is an endpoint of a connector, which attaches the connector to a connectable element. Each connector end is part of one connector. The multiplicity of the connector end may not be more general than the multiplicity of the association typing the owning connector. OCL true If a connector end is attached to a port of the containing classifier, partWithPort will be empty. OCL true If a connector end references both a role and a partWithPort, then the role must be a port that is defined by the type of the partWithPort. OCL true The property held in self.partWithPort must not be a Port. OCL true 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. 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. Indicates the role of the internal structure of a classifier with the port to which the connector end is attached. A component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment. The kind of instantiation that applies to a Component. If false, the component is instantiated as an addressable object. If true, the Component is defined at design-time, but at runtime (or execution-time) an object specified by the Component does not exist, that is, the component is instantiated indirectly, through the instantiation of its realizing classifiers or parts. Several standard stereotypes use this meta attribute, e.g. <<specification>>, <<focus>>, <<subsystem>>. The interfaces that the component requires from other components in its environment in order to be able to offer its full set of provided functionality. These interfaces may be Used by the Component or any of its realizingClassifiers, or they may be the Interfaces that are required by its public Ports. The interfaces that the component exposes to its environment. These interfaces may be Realized by the Component or any of its realizingClassifiers, or they may be the Interfaces that are provided by its public Ports. The set of Realizations owned by the Component. Realizations reference the Classifiers of which the Component is an abstraction; i.e., that realize its behavior. Utility returning the set of realized interfaces of a component: OCL result = (classifier.clientDependency-> select(dependency|dependency.oclIsKindOf(Realization) and dependency.supplier.oclIsKindOf(Interface)))-> collect(dependency|dependency.client) Utility returning the set of used interfaces of a component: OCL result = (classifier.supplierDependency-> select(dependency|dependency.oclIsKindOf(Usage) and dependency.supplier.oclIsKindOf(interface)))-> collect(dependency|dependency.supplier) OCL result = let usedInterfaces = UsedInterfaces(self) and let realizingClassifierUsedInterfaces = UsedInterfaces(self.realizingClassifier) and let typesOfUsedPorts = self.ownedPort.required in ((usedInterfaces->union(realizingClassifierUsedInterfaces))-> union(typesOfUsedPorts))->asSet() OCL result = let implementedInterfaces = self.implementation->collect(impl|impl.contract) and let realizedInterfaces = RealizedInterfaces(self) and let realizingClassifierInterfaces = RealizedInterfaces(self.realizingClassifier) and let typesOfRequiredPorts = self.ownedPort.provided in (((implementedInterfaces->union(realizedInterfaces)->union(realizingClassifierInterfaces))-> union(typesOfRequiredPorts))->asSet() 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. The Component that owns this ComponentRealization and which is implemented by its realizing classifiers. A classifier that is involved in the implementation of the Component that owns this ComponentRealization. Specifies a link that enables communication between two or more instances. This link may be an instance of an association, or it may represent the possibility of the instances being able to communicate because their identities are known by virtue of being passed in as parameters, held in variables or slots, or because the communicating instances are the same instance. The link may be realized by something as simple as a pointer or by something as complex as a network connection. In contrast to associations, which specify links between any instance of the associated classifiers, connectors specify links between instances playing the connected parts only. A delegation connector is a connector that links the external contract of a component (as specified by its ports) to the internal realization of that behavior by the component's parts. It represents the forwarding of signals (operation requests and events): a signal that arrives at a port that has a delegation connector to a part or to another port will be passed on to that target for handling. An assembly connector is a connector between two components that defines that one component provides the services that another component requires. An assembly connector is a connector that is defined from a required interface or port to a provided interface or port. The types of the connectable elements that the ends of a connector are attached to must conform to the types of the association ends of the association that types the connector, if any. OCL true The connectable elements attached to the ends of a connector must be compatible. OCL true The ConnectableElements attached as roles to each ConnectorEnd owned by a Connector must be roles of the Classifier that owned the Connector, or they must be ports of such roles. OCL true A delegation connector must only be defined between used Interfaces or Ports of the same kind, e.g. between two provided Ports or between two required Ports. OCL true If a delegation connector is defined between a used Interface or Port and an internal Part Classifier, then that Classifier must have an 'implements' relationship to the Interface type of that Port. OCL true If a delegation connector is defined between a source Interface or Port and a target Interface or Port, then the target Interface must support a signature compatible subset of Operations of the source Interface or Port. OCL true In a complete model, if a source Port has delegation connectors to a set of delegated target Ports, then the union of the Interfaces of these target Ports must be signature compatible with the Interface that types the source Port. OCL true An assembly connector must only be defined from a required Interface or Ports to a provided Interface or Port. OCL true An optional association that specifies the link corresponding to this connector. A connector may be redefined when its containing classifier is specialized. The redefining connector may have a type that specializes the type of the redefined connector. The types of the connector ends of the redefining connector may specialize the types of the connector ends of the redefined connector. The properties of the connector ends of the redefining connector may be replaced. A connector consists of at least two connector ends, each representing the participation of instances of the classifiers typing the connectable elements attached to this end. The set of connector ends is ordered. Indicates the kind of connector. The set of Behaviors that specify the valid interaction patterns across the connector. ConnectorKind is an enumeration type. Indicates that the connector is an assembly connector. Indicates that the connector is a delegation connector. A manifestation is the concrete physical rendering of one or more model elements by an artifact. The model element that is utilized in the manifestation in an Artifact. A deployment is the allocation of an artifact or artifact instance to a deployment target. The Artifacts that are deployed onto a Node. This association specializes the supplier association. The DeployedTarget which is the target of a Deployment. A node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures. The internal structure of a Node (if defined) consists solely of parts of type Node. OCL true The Nodes that are defined (nested) within the Node. 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). 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. A deployment target is the location for a deployed artifact. The set of Deployments for a DeploymentTarget. The set of elements that are manifested in an Artifact that is involved in Deployment to a DeploymentTarget. OCL result = ((self.deployment->collect(deployedArtifact))->collect(manifestation))->collect(utilizedElement) A deployed artifact is an artifact or artifact instance that has been deployed to a deployment target. A communication path is an association between two deployment targets, through which they are able to exchange signals and messages. The association ends of a CommunicationPath are typed by DeploymentTargets. OCL result = self.endType->forAll (t | t.oclIsKindOf(DeploymentTarget)) A property is a structural feature of a classifier that characterizes instances of the classifier. A property related by ownedAttribute to a classifier (other than an association) 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. A property represents a set of instances that are owned by a containing classifier instance. A property has the capability of being a deployment target in a deployment relationship. This enables modeling the deployment to hierarchical nodes that have properties functioning as internal parts. A multiplicity of a composite aggregation must not have an upper bound greater than 1. A multiplicity on an aggregate end of a composite aggregation must not have an upper bound greater than 1. OCL isComposite implies (upperBound()->isEmpty() or upperBound() <= 1) Subsetting may only occur when the context of the subsetting property conforms to the context of the subsetted property. OCL self.subsettedProperty->notEmpty() implies (self.subsettingContext()->notEmpty() and self.subsettingContext()->forAll (sc | self.subsettedProperty->forAll(sp | sp.subsettingContext()->exists(c | sc.conformsTo(c))))) A redefined property must be inherited from a more general classifier containing the redefining property. OCL if (redefinedProperty->notEmpty()) then (redefinitionContext->notEmpty() and redefinedProperty->forAll(rp| ((redefinitionContext->collect(fc| fc.allParents()))->asSet())->collect(c| c.allFeatures())->asSet()->includes(rp)) A subsetting property may strengthen the type of the subsetted property, and its upper bound may be less. OCL self.subsettedProperty->forAll(sp | self.type.conformsTo(sp.type) and ((self.upperBound()->notEmpty() and sp.upperBound()->notEmpty()) implies self.upperBound()<=sp.upperBound() )) Only a navigable property can be marked as readOnly. OCL isReadOnly implies isNavigable() A derived union is derived. OCL isDerivedUnion implies isDerived A derived union is read only. OCL isDerivedUnion implies isReadOnly A property may not subset a property with the same name. OCL true A Property can be a DeploymentTarget if it is a kind of Node and functions as a part in the internal structure of an encompassing Node. OCL true 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. If isReadOnly is true, the attribute may not be written to after initialization. If true, the attribute may only be read, and not written. Specifies whether the property is derived as the union of all of the properties that are constrained to subset it. Specifies a String that represents a value to be used when no argument is supplied for the Property. A String that is evaluated to give a default value for the Property when an object of the owning Classifier is instantiated. Specifies the kind of aggregation that applies to the Property. If isComposite is true, the object containing the attribute is a container for the object or value contained in the attribute. This is a derived value, indicating whether the aggregation of the Property is composite or not. References the Class that owns the Property. References the properties that are redefined by this property. References the owning association of this property, if any. The DataType that owns this Property. A ValueSpecification that is evaluated to give a default value for the Property when an object of the owning Classifier is instantiated. In the case where the property is one navigable end of a binary association with both ends navigable, this gives the other end. References the properties of which this property is constrained to be a subset. References the association of which this property is a member, if any. The query isAttribute() is true if the Property is defined as an attribute of some classifier. OCL result = Classifier.allInstances->exists(c | c.attribute->includes(p)) If this property is owned by a class, associated with a binary association, and the other end of the association is also owned by a class, then opposite gives the other end. OCL result = if owningAssociation->isEmpty() and association.memberEnd->size() = 2 then let otherEnd = (association.memberEnd - self)->any() in if otherEnd.owningAssociation->isEmpty() then otherEnd else Set{} endif else Set {} endif The value of isComposite is true only if aggregation is composite. OCL result = (self.aggregation = #composite) The query isConsistentWith() specifies, for any two Properties in a context in which redefinition is possible, whether redefinition would be logically consistent. A redefining property is consistent with a redefined property if the type of the redefining property conforms to the type of the redefined property, the multiplicity of the redefining property (if specified) is contained in the multiplicity of the redefined property, and the redefining property is derived if the redefined property is derived. OCL redefinee.isRedefinitionContextValid(self) OCL result = redefinee.oclIsKindOf(Property) and let prop : Property = redefinee.oclAsType(Property) in (prop.type.conformsTo(self.type) and ((prop.lowerBound()->notEmpty() and self.lowerBound()->notEmpty()) implies prop.lowerBound() >= self.lowerBound()) and ((prop.upperBound()->notEmpty() and self.upperBound()->notEmpty()) implies prop.lowerBound() <= self.lowerBound()) and (self.isDerived implies prop.isDerived) and (self.isComposite implies prop.isComposite)) The query subsettingContext() gives the context for subsetting a property. It consists, in the case of an attribute, of the corresponding classifier, and in the case of an association end, all of the classifiers at the other ends. OCL result = if association->notEmpty() then association.endType-type else if classifier->notEmpty() then Set{classifier} else Set{} endif endif The query isNavigable() indicates whether it is possible to navigate across the property. OCL result = not classifier->isEmpty() or association.owningAssociation.navigableOwnedEnd->includes(self) 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. The defining feature of each slot is a structural feature (directly or inherited) of a classifier of the instance specification. OCL slot->forAll(s | classifier->exists (c | c.allFeatures()->includes (s.definingFeature))) One structural feature (including the same feature inherited from multiple classifiers) is the defining feature of at most one slot in an instance specification. OCL classifier->forAll(c | (c.allFeatures()->forAll(f | slot->select(s | s.definingFeature = f)->size() <= 1))) An InstanceSpecification can be a DeploymentTarget if it is the instance specification of a Node and functions as a part in the internal structure of an encompassing Node. OCL true An InstanceSpecification can be a DeployedArtifact if it is the instance specification of an Artifact. OCL true The classifier or classifiers of the represented instance. If multiple classifiers are specified, the instance is classified by all of them. A slot giving the value or values of a structural feature of the instance. An instance specification can have one slot per structural feature of its classifiers, including inherited features. It is not necessary to model a slot for each structural feature, in which case the instance specification is a partial description. A specification of how to compute, derive, or construct the instance. 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. A concrete name that is used to refer to the Artifact in a physical context. Example: file system name, universal resource locator. The Artifacts that are defined (nested) within the Artifact. The association is a specialization of the ownedMember association from Namespace to NamedElement. The set of model elements that are manifested in the Artifact. That is, these model elements are utilized in the construction (or generation) of the artifact. The Operations defined for the Artifact. The association is a specialization of the ownedMember association. The attributes or association ends defined for the Artifact. The association is a specialization of the ownedMember association. 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. Actual Gates of the InteractionUse must match Formal Gates of the referred Interaction. Gates match when their names are equal. OCL true The InteractionUse must cover all Lifelines of the enclosing Interaction which appear within the referred Interaction. OCL true The arguments of the InteractionUse must correspond to parameters of the referred Interaction OCL true The arguments must only be constants, parameters of the enclosing Interaction or attributes of the classifier owning the enclosing Interaction. OCL true Refers to the Interaction that defines its meaning The actual gates of the InteractionUse The actual arguments of the Interaction A part decomposition is a description of the internal interactions of one lifeline relative to an interaction. PartDecompositions apply only to Parts that are Parts of Internal Structures not to Parts of Collaborations. OCL true Assume that within Interaction X, Lifeline L is of class C and decomposed to D. Within X there is a sequence of constructs along L (such constructs are CombinedFragments, InteractionUse and (plain) OccurrenceSpecifications). Then a corresponding sequence of constructs must appear within D, matched one-to-one in the same order. i) CombinedFragment covering L are matched with an extra-global CombinedFragment in D ii) An InteractionUse covering L are matched with a global (i.e. covering all Lifelines) InteractionUse in D. iii) A plain OccurrenceSpecification on L is considered an actualGate that must be matched by a formalGate of D OCL true Assume that within Interaction X, Lifeline L is of class C and decomposed to D. Assume also that there is within X an InteractionUse (say) U that covers L. According to the constraint above U will have a counterpart CU within D. Within the Interaction referenced by U, L should also be decomposed, and the decomposition should reference CU. (This rule is called commutativity of decomposition) OCL true An interaction operand is contained in a combined fragment. An interaction operand represents one operand of the expression given by the enclosing combined fragment. The guard must be placed directly prior to (above) the OccurrenceSpecification that will become the first OccurrenceSpecification within this InteractionOperand. OCL true The guard must contain only references to values local to the Lifeline on which it resides, or values global to the whole Interaction. OCL true Constraint of the operand. The fragments of the operand. An interaction constraint is a Boolean expression that guards an operand in a combined fragment. The dynamic variables that take part in the constraint must be owned by the ConnectableElement corresponding to the covered Lifeline. OCL true The constraint may contain references to global data or write-once data. OCL true Minint/maxint can only be present if the InteractionConstraint is associated with the operand of a loop CombinedFragment. OCL true If minint is specified, then the expression must evaluate to a non-negative integer. OCL true If maxint is specified, then the expression must evaluate to a positive integer. OCL true If maxint is specified, then minint must be specified and the evaluation of maxint must be >= the evaluation of minint OCL true The minimum number of iterations of a loop The maximum number of iterations of a loop A gate is a connection point for relating a message outside an interaction fragment with a message inside the interaction fragment. The message leading to/from an actualGate of an InteractionUse must correspond to the message leading from/to the formalGate with the same name of the Interaction referenced by the InteractionUse. OCL true The message leading to/from an (expression) Gate within a CombinedFragment must correspond to the message leading from/to the CombinedFragment on its outside. OCL true 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. If the interactionOperator is opt, loop, break, or neg there must be exactly one operand OCL true The InteractionConstraint with minint and maxint only apply when attached to an InteractionOperand where the interactionOperator is loop. OCL true If the interactionOperator is break, the corresponding InteractionOperand must cover all Lifelines within the enclosing InteractionFragment. OCL true The interaction operators 'consider' and 'ignore' can only be used for the CombineIgnoreFragment subtype of CombinedFragment OCL ((interactionOperator = #consider) or (interactionOperator = #ignore)) implies oclsisTypeOf(CombineIgnoreFragment) Specifies the operation which defines the semantics of this combination of InteractionFragments. The set of operands of the combined fragment. Specifies the gates that form the interface between this CombinedFragment and its surroundings An interaction is a unit of behavior that focuses on the observable exchange of information between connectable elements. Specifies the participants in this Interaction. The Messages contained in this Interaction. The ordered set of fragments in the Interaction. Actions owned by the Interaction. Specifies the gates that form the message interface between this Interaction and any InteractionUses which reference it. 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. If two (or more) InteractionUses within one Interaction, refer to Interactions with 'common Lifelines,' those Lifelines must also appear in the Interaction with the InteractionUses. By common Lifelines we mean Lifelines with the same selector and represents associations. OCL true The selector for a Lifeline must only be specified if the referenced Part is multivalued. OCL (self.selector->isEmpty() implies not self.represents.isMultivalued()) or (not self.selector->isEmpty() implies self.represents.isMultivalued()) The classifier containing the referenced ConnectableElement must be the same classifier, or an ancestor, of the classifier that contains the interaction enclosing this lifeline. OCL if (represents->notEmpty()) then (if selector->notEmpty() then represents.isMultivalued() else not represents.isMultivalued()) References the InteractionFragments in which this Lifeline takes part. References the ConnectableElement within the classifier that contains the enclosing interaction. References the Interaction enclosing this Lifeline. If the referenced ConnectableElement is multivalued, then this specifies the specific individual part within that set. References the Interaction that represents the decomposition. A continuation is a syntactic way to define continuations of different branches of an alternative combined fragment. Continuations is intuitively similar to labels representing intermediate points in a flow of control. Continuations with the same name may only cover the same set of Lifelines (within one Classifier). OCL true Continuations are always global in the enclosing InteractionFragment e.g. it always covers all Lifelines covered by the enclosing InteractionFragment. OCL true Continuations always occur as the very first InteractionFragment or the very last InteractionFragment of the enclosing InteractionFragment. OCL true True: when the Continuation is at the end of the enclosing InteractionFragment and False when it is in the beginning. InteractionFragment is an abstract notion of the most general interaction unit. An interaction fragment is a piece of an interaction. Each interaction fragment is conceptually like an interaction by itself. References the Lifelines that the InteractionFragment involves. The general ordering relationships contained in this fragment. The Interaction enclosing this InteractionFragment. The operand enclosing this InteractionFragment (they may nest recursively) A consider ignore fragment is a kind of combined fragment that is used for the consider and ignore cases, which require lists of pertinent messages to be specified. The interaction operator of a ConsiderIgnoreFragment must be either 'consider' or 'ignore'. OCL (interactionOperator = #consider) or (interactionOperator = #ignore) The NamedElements must be of a type of element that identifies a message (e.g., an Operation, Reception, or a Signal). OCL message->forAll(m | m.oclIsKindOf(Operation) or m.oclIsKindOf(Reception) or m.oclIsKindOf(Signal)) The set of messages that apply to this fragment InteractionOperatorKind is an enumeration designating the different kinds of operators of combined fragments. The interaction operand defines the type of operator of a combined fragment. The interactionOperator seq designates that the CombinedFragment represents a weak sequencing between the behaviors of the operands. The interactionOperator alt designates that the CombinedFragment represents a choice of behavior. At most one of the operands will be chosen. The chosen operand must have an explicit or implicit guard expression that evaluates to true at this point in the interaction. An implicit true guard is implied if the operand has no guard. The interactionOperator opt designates that the CombinedFragment represents a choice of behavior where either the (sole) operand happens or nothing happens. An option is semantically equivalent to an alternative CombinedFragment where there is one operand with non-empty content and the second operand is empty. The interactionOperator break designates that the CombinedFragment represents a breaking scenario in the sense that the operand is a scenario that is performed instead of the remainder of the enclosing InteractionFragment. A break operator with a guard is chosen when the guard is true and the rest of the enclosing Interaction Fragment is ignored. When the guard of the break operand is false, the break operand is ignored and the rest of the enclosing InteractionFragment is chosen. The choice between a break operand without a guard and the rest of the enclosing InteractionFragment is done non-deterministically. The interactionOperator par designates that the CombinedFragment represents a parallel merge between the behaviors of the operands. The OccurrenceSpecifications of the different operands can be interleaved in any way as long as the ordering imposed by each operand as such is preserved. The interactionOperator strict designates that the CombinedFragment represents a strict sequencing between the behaviors of the operands. The semantics of strict sequencing defines a strict ordering of the operands on the first level within the CombinedFragment with interactionOperator strict. Therefore OccurrenceSpecifications within contained CombinedFragment will not directly be compared with other OccurrenceSpecifications of the enclosing CombinedFragment. The interactionOperator loop designates that the CombinedFragment represents a loop. The loop operand will be repeated a number of times. The interactionOperator critical designates that the CombinedFragment represents a critical region. A critical region means that the traces of the region cannot be interleaved by other OccurrenceSpecifications (on those Lifelines covered by the region). This means that the region is treated atomically by the enclosing fragment when determining the set of valid traces. Even though enclosing CombinedFragments may imply that some OccurrenceSpecifications may interleave into the region, such as e.g. with par-operator, this is prevented by defining a region. The interactionOperator neg designates that the CombinedFragment represents traces that are defined to be invalid. The interactionOperator assert designates that the CombinedFragment represents an assertion. The sequences of the operand of the assertion are the only valid continuations. All other continuations result in an invalid trace. The interacionOperator 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. The interactionOperator consider designates which messages should be considered within this combined fragment. This is equivalent to defining every other message to be ignored. 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 classifier cannot be abstract. OCL not (self.classifier.isAbstract = #true) The classifier cannot be an association class OCL not self.classifier.oclIsKindOf(AssociationClass) The type of the result pin must be the same as the classifier of the action. OCL self.result.type = self.classifier The multiplicity of the output pin is 1..1. OCL self.result.multiplicity.is(1,1) Classifier to be instantiated. Gives the output pin on which the result is put. A destroy object action is an action that destroys objects. The multiplicity of the input pin is 1..1. OCL self.target.multiplicity.is(1,1) The input pin has no type. OCL self.target.type->size() = 0 Specifies whether links in which the object participates are destroyed along with the object.