Coupling (computer programming): Difference between revisions

Revision as of 16:30, 11 November 2005

Revision as of 16:41, 11 November 2005

Line 25:

Build systems like [[make]] are also dependency driven in the sense that a more complex object, like a [[Computer_program|program]], only gets [[Linker|linked]] together once all its dependencies, i.e. the objects it is built of, have been [[Compiler|compiled]].

== Low-Coupling / High-Cohesion pattern ==

The Low-Coupling / High-Cohesion isn'tis a specificgeneral patterngoal amongstto [[design pattern (computer science)|design pattern]]s. It's a general [[method]]achieve forwhen structuring [[Computercomputer program|program]]s, so that they're simplerare easier to understand, program and maintain.

The concepts (Low-Coupling / High-Cohesion) are usually related. Low coupling implies high cohesion and viceversa, because if we put together all relationed methods (High Cohesion), the connection between classes tends to get lower (Low Coupling).