Coupling (computer programming): Difference between revisions

Revision as of 18:32, 10 July 2005

Revision as of 05:19, 18 July 2005

Line 13:

Coupling is usually contrasted with [[cohesion]]. Low coupling often correlates with high cohesion, and vice versa. The software quality metrics of coupling and cohesion were invented by Larry Constantine, original developer of Structured Design.

Dependency is also common in talking about [[software package]] management. One software package, in order to work or to be fully functional, may depend on other software packages and thus must also be installed also, and their specific versions must be known if [[backward compatibility]] is broken between versions. The [[Apt]] package format, as well as some versions of the [[RPM Package Manager|RPM]] package format, include dependency information between packages. This is convenient for updating software but can lead to [[dependency hell]].

Build systems like [[Make]] are also dependency driven in the sencesense 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]].

[[Category:Computer science]]