the declared visibility. It extends the visibility of the supplier so that the client can see into the supplier. <> Import is a stereotyped permission dependency between two namespaces, denoting that the public contents of the target package are added to the namespace of the source package. Permission stereotype <> Call is a stereotyped usage dependency whose source is an operation and whose target is an operation. The relationship may also be subsumed to the class containing an operation, with the meaning that there exists an operation in the class to which the dependency applies. A call dependency specifies that the source operation or an operation in the source class invokes the target operation or an operation in the target class. A call dependency may connect a source operation to any target operation that is within scope including, but not limited to, operations of the enclosing classifier and operations of other visible classifiers. Usage stereotype <> Create is a stereotyped usage dependency denoting that the client classifier creates instances of the supplier classifier. Usage stereotype <> A stereotyped usage dependency among classifiers indicating that operations on the client create instances of the supplier. Usage stereotype <> Send is a stereotyped usage dependency whose source is an operation and whose target is a signal, specifying that the source sends the target signal. Usage stereotype complete Specifies a constraint applied to a set of generalizations with the same discriminator and the same parent, indicating that any instance of the parent must be an instance of at least one child within the set of generalizations. If a parent has a single discriminator, the set of its child generalizations being complete implies that the parent is abstract. The connotation of declaring a set of generalizations complete is that all of the children with the given discriminator have been declared and that additional ones are not expected (in other words, the set of generalizations is closed), and designs may assume with some confidence that the set of children is fixed. If a new child is nevertheless added in the future, existing models may be adversely affected and Generalization Constraint may require modification. incomplete Specifies a constraint applied to a set of generalizations with the same discriminator, indicating that an instance of the parent need not be an instance of a child within the set (but there is no guarantee that such an instance will actually exist). Being incomplete implies that the parent is concrete. The connotation of declaring a set of generalizations incomplete is that all of the children with the given discriminator have not necessarily been declared and that additional ones are might be added, therefore users should not count on the set of children being fixed. Generalization Constraint disjoint Specifies a constraint applied to a set of generalizations, indicating that instance of the parent may be an instance of no more than one of the given children within the set of generalizations. This is the default semantics of generalization. Generalization Constraint overlapping Specifies a constraint applied to a set of generalizations, indicating that an instance of one child may be simultaneously an instance of another child in the set (but there is no guarantee that such an instance will actually exist). Generalization Constraint <> Specifies that the child inherits the Generalization stereotype implementation of the parent (its attributes, operations and methods) but does not make public the supplier?s interfaces nor guarantee to support them, thereby violating substitutability. This is private inheritance and is usually used only for programming implementation purposes. <> Specifies that the designated feature creates an instance of the classifier to which the feature is attached. May be promoted to the Classifier containing the feature. BehavioralFeature stereotype <> Specifies that the designated feature destroys an instance of the classifier to which the feature is attached. May be promoted to the classifier containing the feature. BehavioralFeature stereotype <> Create is a stereotyped call event denoting that the instance receiving that event has just been created. For state machines, it triggers the initial transition at the topmost level of the state machine (and is the only kind of trigger that may be applied to an initial transition). CallEvent stereotype <> Destroy is a stereotyped call event denoting that the instance receiving the event is being destroyed. CallEvent stereotype <> (Name for the stereotyped class is Derivation.) Specifies a derivation relationship among model elements that are usually, but not necessarily, of the same type. A derived dependency specifies that the client may be computed from the supplier. The mapping specifies the computation. The client may be implemented for design reasons, such as efficiency, even though it is logically redundant. Abstraction stereotype <> (Name for the stereotyped class is Realization.) Specifies a realization relationship between a specification model element or elements (the supplier) and a model element or elements that implement it (the client). The implementation model element is required to support all of the operations or received signals that the specification model element declares. The implementation model element must make or inherit its own declarations of the operations and signal receptions. The mapping specifies the relationship between the two. The mapping may or may not be computable. Realization can be used to model stepwise refinement, optimizations, transformations, templates, model synthesis, framework composition, etc. Abstraction stereotype <> (Name for the stereotyped class is Refinement.) Specifies refinement relationship between model elements at different semantic levels, such as analysis and design. The mapping specifies the relationship between the two elements or sets of elements. The mapping may or may not be computable, and it may be unidirectional or bidirectional. Refinement can be used to model transformations from analysis to design and other such changes. Abstraction stereotype <> (Name for the stereotyped class is Trace.) Specifies a trace relationship between model elements or sets of model elements that represent the same concept in different models. Traces are mainly used for tracking requirements and changes across models. Since model changes can occur in both directions, the directionality of the dependency can often be ignored. The mapping specifies the relationship between the two, but it is Abstraction stereotype rarely computable and is usually informal. derived A true value indicates that the model element can be completely derived from other model elements and is therefore logically redundant. In an analysis model, the element may be included to define a useful name or concept. In a design model, the usual intent is that the element should exist in the implementation recomputation. to avoid the need for ModelElement Tag <> <> <> <> <> documentation <> Denotes a document. Denotes a program that may be run on a node. Denotes a document containing source code or data. Denotes a static or dynamic library. Denotes a data base table. Documentation is a comment, description, or explanation of the element to which it is attached. A metamodel is a stereotyped model denoting that the model is an abstraction of another model, i.e., it is a model of a model. Hence, if M2 is a model of the model M1, then M2 is a metamodel of M1. It follows then that classes in M1 are instances of metaclasses in M2. The stereotype can be recursively applied, as in the case of a 4-layer metamodel architecture. Component Component Component Component Component Element Model stereotype stereotype stereotype stereotype stereotype Tag stereotype <> A systemModel is a stereotyped model that contains a collection of models of the same Model stereotype physical system. A systemModel also contains all relationships and constraints between model elements contained in different models. <> A stub is a stereotyped package representing a package that is incompletely transferred; specifically, a stub provides the public parts of the package, but nothing more. Package stereotype <> A framework is a stereotyped package consisting mainly of patterns, where patterns are defined as template collaborations. Package stereotype <> A facade is a stereotyped package containing only references to model elements owned by another package. It is used to provide a ?public view? of some of the contents of a package. A facade does not contain any model elements of its own. Package stereotype <> TopLevel is a stereotype of package denoting the top-most package in a containment hierarchy. The Package stereotype topLevel stereotype defines the outer limit for looking up names, as namespaces “see” outwards. A topLevel subsystem represents the top of the subsystem containment hierarchy, i.e., it is the model element that represents the boundary of the entire physical system being modeled. <> Specifies the implementation of a class in some programming language in which an instance may not have more than one class. This is in contrast to a general UML Class, for which an instance may have multiple classes at one time and may gain or lose classes over time, and an object (a child of instance) may dynamically have multiple classes. Class stereotype <> Specifies a domain of instances (objects) together with the operations applicable to the objects. A type may not contain any methods, but it may have attributes and associations. Class stereotype <> <> Specifies that the instances of the classifier are classes. Specifies that the classifier is a metatype, the instances of which are children marked by the same discriminator. Classifier Classifier stereotype stereotype <> <> <> Specifies a classifier that represents a Classifier Classifier Classifier stereotype stereotype stereotype heavy-weight flow of control. Specifies a classifier that represents a flow of control. Specifies a classifier that has no instances, but rather denotes a named collection of non-member attributes and operations, all of which are class-scoped. persistence Persistence denotes the permanence of the state of the classifier, marking it as transitory (its state is destroyed when the instance is destroyed) or persistent (its state is not destroyed when the instance is destroyed). Classifier Tag semantics <> Semantics is the specification of the meaning of the classifier. Specifies a constraint that must be attached to a set of classifiers or relationships. It indicates that the conditions of the constraint must hold over time (for the time period of concern in the particular containing element) for the classifiers or relationships and their instances. Classifier Constraint Tag stereotype <> Specifies a constraint that must be attached to an operation, and denotes that the conditions of the constraint must hold after the invocation of the Constraint stereotype