Differences

This shows you the differences between two versions of the page.

--- principles:low_coupling [2013-02-25 12:10] – IE christian
+++ principles:low_coupling [2021-09-02 12:46] – old revision restored (2021-03-29 09:33) 65.21.179.175
@@ Line 55: / Line 55: @@
   * [[wiki:Examined]]
-  * [[wiki:Accepted]]
+  * [[wiki:Accepted]]: The concept of low coupling is widely known and described in several well-known books for example in Craig Larman's //Applying UML and Patterns//
 /*  * [[wiki:Questioned]]*/
@@ Line 73: / Line 73: @@
   * [[Keep It Simple Stupid]] (KISS): Reducing the coupling often involves the use of complicated interaction patterns, indirections, etc.
   * [[High Cohesion]] (HC): A system consisting of one single module has a very low coupling as there are no dependencies on other modules. But such a system also has low cohesion. The other extreme, very many highly cohesive modules, naturally has a higher coupling between the modules. So here a compromise has to be found.
+  * [[Rule of Explicitness]] (RoE): Direct communication typically has the disadvantage of a higher coupling. Indirection reduces coupling but creates implicit/indirect communication paths.
 ==== Complementary Principles ====
@@ Line 86: / Line 86: @@
 {{page>collections:Principles in "The Pragmatic Programmer"#Box}}
-===== Example =====
+===== Examples =====
@@ Line 101: / Line 101: @@
   * [[wiki>CouplingAndCohesion]]
   * Martin Fowler: //[[http://martinfowler.com/ieeeSoftware/coupling.pdf|Reducing Coupling]]//
+  * Craig Larman: //Applying UML and Patterns – An Introduction to Object-Oriented Analysis and Design and Iterative Development//