Mon Nov 28 10:20:01 GMT 2005
Classes are to big ...
* When it is unclear what the exact responsibility of the class is. (when apparently little changes in requirements often require changes in the same set of classes, time after time)
* When it is difficult to write a unittest to test the behavior of the class. (very common for large classes that combine a lot of functionality)
* When the concept of the class no longer fits the size of your head. (working on the class becomes difficult, meaning you need to scroll a lot, skip between various parts of the code in order to understand the class. Differs a little from person to person.)
(google search) (amazon search)