Stereotypes

A standard feature of the UML modelling language is that of stereotypes.

A stereotype can be given to almost any EA element: a Class, Use Case, Requirement, Component or Device. In modeling terms, giving a stereotype to an element is just a further qualification of what that element is. For example, you may have Component elements in your model, and if some are existing ones, and some planned, you might choose to give some an «existing» and some a «planned» stereotype.

In a model, this helps to tell the reader more about the element.

In eaDocX, you can use this to determine how elements are formatted. For example, you may choose to print  «existing» Components in a simple table, but «planned» Components in more detail

To specify the formatting of a stereotype you have defined, select the Add Element button at the bottom of the Profile view; in this view you can then specify the element type and name of your stereotype and then go on to format it as in-line or in a table.

A futher feature of eaDocX is to deliberately specify the formatting for a stereotype as 'none'. This means that you never want elements of that stereotype to appear in the document. For example, you might have details of «retired» Components in your model, which you don't want to print. Specifying them with no formatting means that wherever in the model or the document they might appear, they will never be printed. This can save a lot of time, by excluding a whole set of elements from your documents.