Association (object-oriented programming): Difference between revisions

Revision as of 14:54, 15 January 2015

Revision as of 14:55, 15 January 2015

Line 4:

[[Image:UnidirectionalAssociation.png|thumb|225px|Unless otherwise specified, navigation across an association is bidirectional, although it may be limited to just one direction by adorning some end with an arrowhead pointing to the direction of traversal.]]

In generic terms, the [[Causality|causation]] is usually called "sending a [[message]]", "invoking a [[Method (computer science)|method]]" or "calling a [[member function]]" to the controlled object. Concrete implementation usually requires the requesting object to invoke a ''method'' or ''member function'' using a reference or pointer to the memory ___location of the controlled object. kekekeke

The objects that are related via the association are considered to act in a [[role (computer science)|role]] with respect to the association, if object's current state in the active situation allows the other associated objects to use the object in the manner specified by the role. A role can be used to distinguish two objects of the same class when describing its use in the context of the association. A role describes the ''public'' aspects of an object with respect to an association.<ref>{{cite book | title=Object-oriented modeling and design | last=Rumbaugh | first=JR et al. | year=1991 | publisher=Prentice Hall | isbn=0-13-630054-5}}</ref>