|WikiProject Computing / Software||(Rated Stub-class)|
- "In computing, a stereotype is a concept in the Unified Modeling Language, where it is used to encapsulate behaviors"
For me this definition does not seem to be correct. Is there some UML specialist around to check it? Thnks [Casual]
- Common Stereotypes:
Common examples being Control, Entity and Boundary. Given by the UML Specification... just something to be added to this stub [22 June 06 - K]
I propose that we change the name of this article from "Stereotype (computing)" to "Stereotype (UML)". This gets us away from the general category of Computing, where there seems to be no other specific relationships other than UML, thus my proposal. This will also bring the article in line with other similar UML articles such as Activity (UML), Actor (UML), and Event (UML). Thanks! // Brick Thrower 06:53, 9 October 2006 (UTC)
I have read this entry but you don't actually define what a stereotype is. Your definition is too flexible, so I can imagine about 10 different things that match your definition but I don't think they are what you call a stereotype.
Good point, thought after I read the article I could not realize where (if any) is the weakness of the given definition. Rjgodoy 13:26, 26 September 2007 (UTC)
Common UML Stereotypes List
Some that I have seen extremely often:
becomes, extends, includes
Is there a list somewhere of the commonly used, or widely used stereotypes?
Link example: agilemodelling.com
Three types of UML extensibility mechanisms?
In the first sentence you say:
- A stereotype is one of three types of extensibility mechanisms in the Unified Modeling Language (UML).
Which one would those three be then? They should briefly be mentioned here too.
In Unified Modeling Language#Overview it says in contrast:
- UML is extensible, offering the following mechanisms for customization: profiles and stereotype.