Inheritance relationships between stereotypes
If different stereotypes each define identical properties, we recommend defining a stereotype for the shared properties and having the others inherit from it.
Figure 238 extends the example from Figure 232 with the two stereotypes «Technical class» and Analysis element. The «Analysis element» stereotype is abstract and defines the Contact person property of the String type.The fact that the stereotype is abstract is indicated by the fact that its name is displayed in italics in the diagram. The other two stereotypes inherit from «Analysis element».
This means that all use cases with the «Business use case» stereotype and all classes with the «Technical class» stereotype show the Contact property on their Tagged values properties page.
The fact that the «Analysis element» stereotype is abstract and does not itself extend a metaclass means that it cannot be assigned to a UML element. It is merely used to define a property that is to be common to several stereotypes.
Of course, you can also create inheritance relationships between non-abstract stereotypes.