UML Association

76
rate this page

By umlnotes


There are other forms of containment that do not have whole / part implications (aggregation).

There is not likely to be much difference in the way that the two relationships - Aggregation or Association - are implemented. That is, it would be very difficult to look at the code and determine whether a particular relationship ought to be aggregation or association. For this reason, it is pretty safe to ignore the aggregation relationship altogether. As the amigos said in the UML 0.8 document: “...if you don’t understand don’t use it.”

Aggregation and Association both correspond to the Has-by-reference relationship from the Booch-94 notation.

For example, Each Window refers back to its parent Frame. This is not aggregation since it is not reasonable to consider a parent Frame to be part of a child Window. We use the association relationship to depict this.

The association has an arrowhead to denote that Frame does not know anything about Window. Note the name on the role. This relationship will almost certainly be implemented with a pointer of some kind.
The association has an arrowhead to denote that Frame does not know anything about Window. Note the name on the role. This relationship will almost certainly be implemented with a pointer of some kind.

It is sometimes more expressive to show the attributes as associations:

The above two associations have the same meaning as the attributes in the old version of the  Contact class.
The above two associations have the same meaning as the attributes in the old version of the Contact class.

  —   Rate it:  up  down  [flag this hub]

Comments

RSS for comments on this Hub Small RSS Icon

No comments yet.

Submit a Comment

Members and Guests

Sign in or sign up and post using a hubpages account.


optional



working