Class diagrams use standard UML (Unified Modeling Language) notation for class diagrams to represent the static relationships between model entities. You should consult a UML reference for details on UML notation. The following discussion is confined to how Agile Business Suite model entities are represented as class diagrams. By default, the window is Class Diagrams.
The following types of relationship can be expressed on a class diagram:
Aggregation
An aggregation is a relationship between a whole (the aggregating class) and its parts. It is indicated by a solid line, with a filled diamond at the aggregating class.
An example aggregation is between a car (the aggregating class) and its parts, such as steering wheel, engine, tires, and so on. Each of these parts exists in their own right, but they are aggregated as a car.
Dependency
A dependency is a relationship where changes to the supplier class might cause changes in the client class. It is indicated by a dashed line, with an open arrowhead at the supplier class.
An example dependency is between a encoder (the client class) and an encoding algorithm (the supplier entity). Changes to the encoding algorithm might affect the encoder.
Inheritance
An inheritance relationship is between a super class and its sub classes. It is indicated by a solid line, with a hollow arrowhead at the parent entity.
Class diagrams, like folders, do not own their member entities. Entities in a class diagram continue to be owned by the class diagram's parent entity. This effectively means that an entity can appear in more than one class diagram.
Adding a new entity to a class diagram is essentially the same as adding the entity to the class diagram's parent.
Entities that are members of the class diagram's owner can be added as existing entities to the class diagram.
Class diagrams are modified using the Class Diagram page of a diagram.
Refer to Class Diagram Properties for properties applicable to class diagrams.