UML model element stereotypes

This product supports a set of standard UML 2.1 model element stereotypes.

The following table lists each stereotype, the model element to which it applies, and a description.

Stereotype Model element Description
«auxiliary» Class This stereotype is applied to a class that supports another class, typically by providing control mechanisms. The supported class is a focus class.
«buildComponent» Component This stereotype is applied to a component that specifies a set of components for organizational or system-level development.
«create» Operation This stereotype is applied to an operation that creates an instance of the classifier; for example, if the operation is a constructor.
«destroy» Operation This stereotype is applied to an operation that destroys an instance of the classifier.
«document» Artifact This stereotype is applied to an artifact that represents a document.
«entity» Component This stereotype is applied to a component that represents a business concept.
«executable» Artifact This stereotype is applied to an artifact that can execute on a node.
«file» Artifact This stereotype is applied to an artifact that contains source code or data.
«focus» Class This stereotype is applied to a class that specifies core logic or control with auxiliary classes that provide subordinate mechanisms.
«framework» Package This stereotype is applied to a package that contains reusable elements such as classes, patterns, and templates.
«implement» Component This stereotype is applied to a component that does not have a specification and is an implementation of a specification on which it has a dependency.
«implementationClass» Class This stereotype is applied to an implementation of a class where the instance of the class cannot have more than one class.
«library» Artifact This stereotype is applied to an artifact that is a static or dynamic library file.
«metaclass» Class This stereotype is applied to a class whose instances are other classes that conform to the metaclass.
«metamodel» Model This stereotype is applied to a package that contains a model that is an abstraction of another model.
«modelLibrary» Package This stereotype is applied to a package that contains model elements for reuse.
«perspective» Package This stereotype is applied to a package that contains only diagrams or subpackages. Extractors bypass packages that have this stereotype applied.
«process» Component This stereotype is applied to a component that is transaction-based.
«realization» Classifier This stereotype is applied to a classifier that specifies the domain of objects and their implementation.
«responsibility» Note, Text This stereotype is applied to a note that describes the obligation of a model element to other model elements.
«script» Artifact This stereotype is applied to a file that can be interpreted by a computer system.
«service» Component This stereotype is applied to a component that computes a value. This component has no state.
«source» Artifact This stereotype is applied to a source file of an executable file.
«specification» Classifier This stereotype is applied to a classifier that specifies the domain of objects, not their implementation.
«subsystem» Component This stereotype is applied to a component that is part of a larger system.
«systemModel» Model This stereotype is applied to a model or package that contains the models that describe different perspectives of a system.
«type» Class This stereotype is applied to a class that describes the domain of objects and their operations, but does not define the implementation of objects.
«utility» Class This stereotype is applied to a class that does not have instances, but whose attributes and operations have class scope.

Feedback