This is an old revision of the document!
The cohesion of a module is a measure for how well the internal parts of a module (e.g. the methods and attributes of a class) belong together. Having a high cohesion means, that a module should only comprise responsibilities which belong together.
Several kinds of cohesion can be distinguished some of which are strong and some of which are loose. So strong forms of coupling should be preferred.
Not adhering to this principle, i.e. having a low cohesion, means that one module has several unrelated or only loosely related responsibilities. A change in the requirements for one of these may thus also affect the others which would not be the case in a highly cohesive module.
See section contrary principles.
W. P. Stevens, G. van Niekerk, G. J. Myers, L. L. Constantine: Structured design
Robert Cecil Martin (Uncle Bob) describes maximal cohesion at class level as “a class in which each variable is used by each method”.
“In general the more variables a method manipulates the more cohesive that method is to its class.” (Clean Code: A Handbook of Agile Software Craftsmanship - Chapter 10)
Discuss this wiki article and the principle on the corresponding talk page.