Data clumps smell
(New page: Data clumps are groups of data items that are related and are always used together. They are often primitive values. An example of this is a "start" variable and an "end" variable. Martin...) |
|||
| Line 1: | Line 1: | ||
| − | Data clumps are groups of data items that are related and are always used together. They are often primitive values. An example of this is a "start" variable and an "end" variable. | + | Data clumps are groups of data items that are related and are always used or passed around together. They are often primitive values. An example of this is a "start" variable and an "end" variable. |
| − | Martin Fowler suggests replacing these clumps with a single object. In the example above the start and end could be replaced by a "Range" class. Doing this refactoring decreases the size of parameter lists. You can also discover some nice behaviour when you extract the data into an object. For the Range example, you often want to know if a value is within the start and end range, so you could define an "includes" method in the Range class to check for this easily. | + | Martin Fowler suggests replacing these clumps with a single object. In the example above the start and end could be replaced by a "Range" class. Doing this refactoring decreases the size of parameter lists when the values are passed around. This is one solution to the [[Long parameter list smell]]. You can also discover some nice behaviour when you extract the data into an object. For the Range example, you often want to know if a value is within the start and end range, so you could define an "includes" method in the Range class to check for this easily. |
== See also == | == See also == | ||
* [[Long parameter list smell]] | * [[Long parameter list smell]] | ||
* [[Design maxims]] | * [[Design maxims]] | ||
Revision as of 01:47, 6 October 2008
Data clumps are groups of data items that are related and are always used or passed around together. They are often primitive values. An example of this is a "start" variable and an "end" variable.
Martin Fowler suggests replacing these clumps with a single object. In the example above the start and end could be replaced by a "Range" class. Doing this refactoring decreases the size of parameter lists when the values are passed around. This is one solution to the Long parameter list smell. You can also discover some nice behaviour when you extract the data into an object. For the Range example, you often want to know if a value is within the start and end range, so you could define an "includes" method in the Range class to check for this easily.
