Reference no: EM133448449

Questions: Draw a class diagram showing relationships between pairs of classes that seem to be strongly connected. At this stage, just show inheritance and association - you can refine the associations in the next step if appropriate. If there is a candidate for inheritance, consider introducing abstract classes as necessary (for elegance and for future extension). Whenever you are tempted to use inheritance, make sure that it satisfies the following criteria: • It makes the diagram clearer and therefore easier to understand (especially since nontechnical users will see the diagram). • It is not there to describe implementation ( implementation is a design issue, not an analysis issue). If you find a class that is associated with an existing relationship between two other classes, consider making it an association class.

2 Refine the Associations Some of your associations may be modeled more precisely as aggregation. Can you find any examples? Do you think any of your aggregations qualify as compositions? (Hint: it's probably too early to tell at this stage.)

3 Describe the Relationships For every relationship, except inheritance, you should now consider adding some kind of description: • An association name, describing what the association represents(usually a verb). • A source role, describing the role of the source. • A target role, describing the role of the target. (You don't need to provide all three - provide just the association name or the role names, as you prefer.) In the case of aggregation (or composition) you may decide that the description is obvious and, therefore, you may choose to omit it.