Class Stereotype
A stereotype is a type of element that extends the semantics of the metamodel. Stereotypes must be based on existing types or classes whose structure they use. Other stereotypes can be created by the user.
Stereotypes available for a class are:
• Org-Unit: represents the role played by something or someone within the enterprise environment of the modeled system.
• Auxiliary:class that supports another central or fundamental class, generally by implementing a secondary logic or a control flow.
• Implementation class: is used to characterize the classes needed for physical implementation of the system.
• Metaclass: class of which the instances are themselves classes. As a general rule, metaclasses are used to build metamodels.
• Control: is used for classes that perform processing internal to the system. These generally require contributions from several classes.
• Entity: enables description of classes that are passive; that is that do not initiate interactions on their own. An entity object may participate in many different use cases and usually outlives any single interaction. They represent objects shared between the different actors who manipulate them.
• Enumeration: datatype containing a list of tabulated values.
• Expression: expressions of complex datatypes based on types.
• Focus: class that defines the main logic or control flow for the auxiliary class(es) that support it.
• Boundary: used to describe classes that are in direct contact with the system environment. Man-machine interfaces are of this type.
• Interface: an interface is a named set of operations that describe the behavior of an element. In particular, an interface represents the visible part of a class or package in a contractual client-supplier type relationship.
These are interfaces between the different components of the computer system. These are not interfaces with system users, as those are considered boundary stereotypes. See
"Specifying Interfaces" for further information.
• Worker: represents a human actor who interacts with the system. A worker interacts with other workers and manipulates entities while participating in use case realizations.
• Case worker: a case worker interacts directly with actors outside the system.
• Internal worker: an internal worker interacts with other workers and other entities within the system.
• PowerType: metatype of which instances are sub-types of another type.
• Structure: class that describes a structure used in the programs.
• Thread: stereotype used in implementation of an active object as a light business process.
• Primitive Type: used to describe the datatypes.
• Utility: a class of this stereotype groups global variables and procedures useful for programming, and described as attributes and operations of this class.
• Schema group: class describing a type of XML element, the sub-elements of which form a group.
• XML Document Definition Root: class that describes the structure of a message exchanged between two systems using the XML language syntax.
Stereotype display option
An option allows you to display stereotypes in the navigation window of objects.
To activate this option:
1. From the HOPEX workspace, select Tools > Options.
2. In the left pane of the options window, select the Workspace folder.
3. In the right pane, select the option Display stereotype of UML objects in navigator.
4. Click OK.
