Editing Coupling (computer programming) (section)

== Solutions ==
One approach to decreasing coupling is [[functional design]], which seeks to limit the responsibilities of modules along functionality. Coupling increases between two classes '''''A''''' and '''''B''''' if:

*'''''A''''' has an attribute that refers to (is of type) '''''B'''''.
*'''''A''''' calls on services of an object '''''B'''''.
*'''''A''''' has a method that references '''''B''''' (via return type or parameter).
*'''''A''''' is a subclass of (or implements) class '''''B'''''.

Low coupling refers to a relationship in which one module interacts with another module through a simple and stable interface and does not need to be concerned with the other module's internal implementation (see [[Information Hiding]]).

Systems such as [[CORBA]] or [[Component Object Model|COM]] allow objects to communicate with each other without having to know anything about the other object's implementation. Both of these systems even allow for objects to communicate with objects written in other languages.