Stereotype (UML)
From Wikipedia, the free encyclopedia
Stereotypes are one of three extensibility mechanisms in Unified Modeling Language (UML). They allow designers to extend the vocabulary of UML in order to create new model elements, derived from existing ones, but that have specific properties that are suitable for a particular problem domain or otherwise specialized usage. For example, when modelling a network you might need to have symbols for representing routers and hubs. By using stereotyped nodes you can make these things appear as primitive building blocks.
Graphically, a stereotype is rendered as a name enclosed by guillemets and placed above the name of another element. In addition or alternatively it may be indicated by a specific icon. The icon image may even replace the entire UML symbol. For instance, in a class diagram stereotypes can be used to classify method behavior such as «constructor» and «getter». Despite its appearance, «interface» is not a stereotype but a classifier[1].
One alternative to stereotypes, suggested by Peter Coad in his book «Java Modeling in Color with UML: Enterprise Components and Process» is the use of colored archetypes. The archetypes indicated by different-colored UML boxes can be used in combination with stereotypes. This added definition of meaning indicates the role that the UML object plays within the larger software system.
Contents |
[edit] Stereotype attributes
From version 2.0 the previously independent tagged value are considered to be a stereotype attribute. The name tagged value is still kept. Each stereotype have zero or more tag definitions, and all stereotyped UML elements have the corresponding number of tagged values.
[edit] UML defined stereotypes
[edit] Become
In the Unified Modeling Language, become is a keyword for a specific UML stereotype, and applies to a Dependency (which is modeled as a dashed arrow). Become shows that the source modeling element (the arrow's tail) is transformed into the target modeling element (the arrow's head), while keeping some sort of identity, even though it may have changed values, state, or even class.
While UML 2.1 uses the «become» stereotype within the specification, it does not define it.
[edit] References
- ^ Object Management Group, UML Superstructure Specification, v2.0 33, August 2005.
