Java Reference
In-Depth Information
contain
important
information
pertaining
@Entity
or
@Embeddable, where ever applicable.
• The class diagram remains web framework agnostic. Any
web framework can be leveraged to build the solution.
Class diagram may also contain types, packages,
relationships, and even instances such as objects and links.
Class diagrams are static; they display what interacts but not
what happens when they do interact. A class diagram can
have three kinds of relationships:
• Association is a relationship between instances of the two
classes. An association exists between two classes if an
instance of one class must know about the other to perform its
work. In a diagram, an association is a link connecting two
classes.
• Aggregation is an association in which one class belongs to
a collection. An aggregation shows a diamond end pointing to
the part containing the whole.
• Generalization is an inheritance link indicating one class is a
superclass
of
another.
A
generalization
shows
a
triangle
pointing to the superclass.
Using the initial list of business classes, you develop class
diagrams by identifying and defining the relationships among
the classes from the domain model. This is done in an
interactive development workshop with business partners. It
is also useful to keep these diagrams on display on a
whiteboard or other medium, and to develop it gradually as
the project progresses. The diagrams are stored on a UML
