A stereotype is one of three types of extensibility mechanisms in the Unified 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 of stereotype, used in printing. For example, when modeling 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 (« » 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
classify method behavior, e.g. with «constructor» and «getter» and
refine the classifier itself, e.g. with «interface».[2]
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.
From version 2.0 the previously independent tagged value is considered to be a stereotype attribute. The name tagged value is still kept. Each stereotype has zero or more tag definitions, and all stereotyped UML elements have the corresponding number of tagged values.
UML-defined stereotypesedit
Becomeedit
In UML, become is a keyword for a specific UML stereotype, and applies to a dependency (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.
^ abBooch, Grady; Rumbaugh, James; Jacobson, Ivar (2005). The unified modeling language user guide: covers UML 2.0. The Addison-Wesley object technologies series (2 ed.). Upper Saddle River, NJ Munich: Addison-Wesley. ISBN978-0-321-26797-9.
^Object Management Group, OMG® Unified Modeling Language® (OMG UML®), v2.5.1, p. 170, December 2017.
stereotype, other, uses, stereotype, this, article, needs, additional, citations, verification, please, help, improve, this, article, adding, citations, reliable, sources, unsourced, material, challenged, removed, find, sources, stereotype, news, newspapers, b. For other uses see Stereotype This article needs additional citations for verification Please help improve this article by adding 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 template message A stereotype is one of three types of extensibility mechanisms in the Unified 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 of stereotype used in printing For example when modeling 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 or if guillemets proper are unavailable lt lt gt gt 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 classify method behavior e g with constructor and getter and refine the classifier itself e g with interface 2 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 1 Stereotype attributes 2 UML defined stereotypes 2 1 Become 3 Examples 4 See also 5 References 6 External linksStereotype attributes editThis section may be too technical for most readers to understand Please help improve it to make it understandable to non experts without removing the technical details June 2015 Learn how and when to remove this template message From version 2 0 the previously independent tagged value is considered to be a stereotype attribute The name tagged value is still kept Each stereotype has zero or more tag definitions and all stereotyped UML elements have the corresponding number of tagged values UML defined stereotypes editBecome edit In UML become is a keyword for a specific UML stereotype and applies to a dependency 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 Examples editFor example three are used in the Entity Control Boundary pattern ECB or BCE pattern and four in the robustness diagram Boundary Control Entity and Actor nbsp Control Class nbsp Boundary Class nbsp Entity Class nbsp Actor nbsp Access ClassSee also editProfile UML Entity control boundaryReferences edit a b Booch Grady Rumbaugh James Jacobson Ivar 2005 The unified modeling language user guide covers UML 2 0 The Addison Wesley object technologies series 2 ed Upper Saddle River NJ Munich Addison Wesley ISBN 978 0 321 26797 9 Object Management Group OMG Unified Modeling Language OMG UML v2 5 1 p 170 December 2017 External links editUML Stereotype nbsp This Unified Modeling Language article is a stub You can help Wikipedia by expanding it vte Retrieved from https en wikipedia org w index php title Stereotype UML amp oldid 1196793643, wikipedia, wiki, book, books, library,
