The diagram tool uses the BON (Business Object Notation) to represent Eiffel systems. This article will give a summary of all components of an eiffelstudio diagram. For detailed information on BON, please read Seamless Object-Oriented Software Architecture by Kim Waldén and Jean-Marc Nerson, Prentice Hall 1994.
An object class is represented by an ellipse (sometimes referred to as bubble). It contains the class name and formal generics of the Eiffel class it represents. Second, it displays information about properties of a class. These properties are:
See also: Changing class names and formal generics
A cluster is a collection of classes and subclusters. It is represented by a stippled, rounded rectangle. The cluster name is in a similar rectangle, by default located at the top of the cluster just outside of it. A cluster can be iconified, which means it is minimized to take up as less space as possible.
See also: Iconifying a cluster
Inheritance between classes is represented by a red arrow from a class to its parent. Typically, inheritance links point upwards.
See also: Creating inheritance links
Client relationships between classes are represented by a blue arrow with a double line from the client to the supplier. Typically, these links point to the right. A special kind of relationship is the aggregate client/supplier link. Aggregate means that the supplier is an integral part of the client. In the class text, it corresponds to expanded features. In the diagram, an aggregate link has a little line along the back side of the arrow.
See also: Creating client/supplier links