The following UML-F tags deal with the visual representation of elements. They do not define or add any properties to the annotated modeling elements. See Section 3.4.1 for further information.
Tag form | Summary |
---|---|
Completeness marker The graphical representation is complete e.g. the class methods or attributes are all shown, all generalizations of the class are shown, all information about an association is shown, etc. | |
Incompleteness marker Inverse of . The graphical representation is possibly incomplete e.g. not all class methods or attributes are shown, not all generalizations of the class are shown, not all association information is shown, etc. This is also the default. | |
d | Hierarchical representation The graphical representation shows only members that are introduced or redefined at the current level. Inherited members are not shown. |
? | Flat representation The graphical representation shows inherited members as well as newly introduced or redefined members. The full hierarchy is shown. |
The following graphical elements convey information about methods or attributes in class or object diagrams. They are attached to the side of the class or object box beside the method or attribute to which they apply. If they are contained inside the box, they also indicate that the method or attribute is inaccessible by other elements in the diagram. If they cross the boundary of the class or object box, they indicate that the method or attribute is accessible by other elements in the diagram. See Section 3.4.2 for further information.
Tag form | Summary |
---|---|
Unfilled rectangle The method or attribute is inherited and not redefined. | |
Gray rectangle The method or attribute is either newly defined, or it is inherited but completely redefined. | |
Half-gray/half-unfilled rectangle The method is redefined but uses the inherited method through a super()-call. | |
Unfilled rectangle with diagonal line The method is abstract and must be overridden in subclasses. |
Through the following graphical elements, sequence diagrams become more expressive. It is possible to describe repeated messages, alternatives, etc. See Section 3.4.4 for further information.
Tag form | Summary |
---|---|
* | Unbound repetition For a message: the message can be repeated as often as desired zero occurrences are allowed. For an object: there can be multiple instantiations of the object's class (including zero). |
+ | Optional The message is optional, occurring at most once. |
| | Alternatives The sequence diagram is subdivided into alternative diagrams. |
(A B) | Bound repetition A concise way to describe multiple occurrence of a message or an object (between A and B times). |
trigger | Trigger Marks the message in a sequence diagram that causes the subsequent interaction to occur. |