A stereotype denotes a
variation on an existing modeling element with the same
form but with a modified intent. Stereotypes are
effectively used to extend the
UML in a consistent
Figure 2. A
frame encompassing a sequence diagram.
- Name Stereotypes in
<<user interface>> and <<UI>> format.
- List Stereotypes
Last. In Figure 1
the second version of the Customer class lists the
stereotypes for its operations after the operation
signature, not before it.
Indicate Assumed Stereotypes. In Figure 1
I dropped the <<business domain>> stereotype because it
is common practice to assume that unless marked
otherwise that a class is a business domain one.
Prefer Naming Conventions over Stereotypes. For example, instead of applying the stereotype
<<getter>> on an operation, you could simply start all
getters with the text get. This simplifies your
diagrams and increases the consistency of your source
code. Normally would have ditched <<getter>> in
Figure 1 but I left it there for
the discussion of
Values Follow Stereotypes.
Classifier Stereotypes. The stereotype for a classifier,
such as the Customer class in Figure
1 should be centered (as should the name itself).
- Introduce New Stereotypes Sparingly.
Visual Stereotypes Sparingly.
sequence diagram which includes the standard
robustness diagram symbols which are commonly
UML communication diagrams.