Revision as of 18:01, 11 November 2005 edit Ligulem (talk \| contribs) Pending changes reviewers, Rollbackers 28,245 edits →High / low coupling: renaming section to "Low coupling" ← Previous edit		Revision as of 18:05, 11 November 2005 edit undo Ligulem (talk \| contribs) Pending changes reviewers, Rollbackers 28,245 edits →Low coupling: change order form high/low to low/high Next edit →
Line 4: == Low coupling == Coupling can be "~~high~~low" (oralso "~~tight~~loose"), or "~~low~~high" (oralso "~~loose~~tight"). Low coupling means that one module does not have to be concerned with the internal implementation of another module, and interacts with another module with a stable interface (see [[Information hiding]]). With low coupling, a change in one module will not require a change in the implementation of another module. Low coupling is a sign of a well structured [[computer system]]. However, in order to achieve maximum efficiency, a highly coupled system is probably needed. In modern computing systems, performance can often be traded for lower coupling; the gains in the [[software development]] process are greater than the value of the running performance gain.

Coupling (computer programming): Difference between revisions