Association (object-oriented programming): Difference between revisions

Revision as of 13:14, 4 March 2009

Revision as of 01:05, 22 May 2009

Line 6:

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.

The objects that are related via the association are considered to act in a [[role (object-oriented programming)|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>

==See also==

Line 16 ⟶ 15:

==References==

{{reflist}}

{{compu-lang-stub}}

[[Category:Object-oriented programming]]

{{compu-lang-stub}}

[[de:Assoziation (UML)]]