Revision as of 16:24, 11 November 2005 edit Ligulem (talk \| contribs) Pending changes reviewers, Rollbackers 28,245 edits lemma: deleting mostly irrelevant and confusing paragraph about usage of the terms. I might also be wrong. ← Previous edit		Revision as of 16:30, 11 November 2005 edit undo Ligulem (talk \| contribs) Pending changes reviewers, Rollbackers 28,245 edits →Low-Coupling / High-Cohesion pattern: slight change in wording Next edit →
Line 28: The Low-Coupling / High-Cohesion isn't a specific pattern amongst [[design pattern (computer science)\|design pattern]]s. It's a general [[method]] for structuring [[Computer program\|program]]s so that they're simpler to understand, program and maintain. ~~These~~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). === Low Coupling ===

Coupling (computer programming): Difference between revisions