principles:high_cohesion
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
principles:high_cohesion [2016-09-03 22:28] – 5.12.30.152 | principles:high_cohesion [2020-10-12 16:15] – old revision restored (2019-05-29 14:46) 159.69.186.191 | ||
---|---|---|---|
Line 20: | Line 20: | ||
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. | 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: FIXME add explanation of cohesion types | + | 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. |
===== Rationale ===== | ===== Rationale ===== | ||
Line 89: | Line 88: | ||
==== Class level cohesion ==== | ==== Class level cohesion ==== | ||
- | Robert Cecil Martin (Uncle Bob) describe | + | Robert Cecil Martin (Uncle Bob) describes |
"In general the more variables a method manipulates the more cohesive that method is to its class." | "In general the more variables a method manipulates the more cohesive that method is to its class." |
principles/high_cohesion.txt · Last modified: 2021-10-18 21:36 by christian