 | This articleneeds additional citations forverification. Please helpimprove this article byadding citations to reliable sources. Unsourced material may be challenged and removed. Find sources: "Stereotype" UML – news ·newspapers ·books ·scholar ·JSTOR(January 2010) (Learn how and when to remove this message) |
Astereotype is one of three types ofextensibility mechanisms in theUnified Modeling Language (UML), the other two being tags and constraints.[1]: 73 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 domain or otherwise specialized usage. The nomenclature is derived from the original meaning ofstereotype, used inprinting. For example, when modeling a network, one might need to have symbols for representing routers and hubs. By using stereotyped nodes, these can be made to appear as primitive building blocks.
Graphically, a stereotype is rendered as a name enclosed byguillemets (« » or, if guillemets proper are unavailable, << >>) and placed above the name of another element.[1]: 73 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
One alternative to stereotypes, suggested byPeter Coad in his bookJava Modeling in Color with UML: Enterprise Components and Process is the use of coloredarchetypes. 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.
 | This sectionmay be too technical for most readers to understand. Pleasehelp improve it tomake it understandable to non-experts, without removing the technical details.(June 2015) (Learn how and when to remove this message) |
From version 2.0 the previously independent tagged value is considered to be astereotype attribute. The nametagged value is still kept. Each stereotype has zero or moretag definitions, and all stereotyped UML elements have the corresponding number of tagged values.
In UML,become is akeyword for a specific UML stereotype, and applies to adependency (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.
For example, three are used in theentity–control–boundary pattern (ECB or BCE pattern) and four in therobustness diagram (Boundary, Control, Entity and Actor).
| Actors |
|  | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Concepts |
| ||||||||||||
| Diagrams |
| ||||||||||||
| Derived languages | |||||||||||||
| Other topics | |||||||||||||
 | ThisUnified Modeling Language article is astub. You can help Wikipedia byexpanding it. |