When code and/or data used to perform a responsibility becomes sprawled across numerous classes, Solution Sprawl is in the air. This smell often results from quickly adding a feature to a system without spending enough time simplifying and consolidating the design to best accommodate the feature.
Solution Sprawl is the identical twin brother of Shotgun Surgery, a smell described by Fowler and Beck [F]. You become aware of this smell when adding or updating a system feature causes you to make changes to many different pieces of code. Solution Sprawl and Shotgun Surgery address the same problem, yet are sensed differently. We become aware of Solution Sprawl by observing it, while we become aware of Shotgun Surgery by doing it.
Move Creation Knowledge to Factory (68) is a refactoring that solves the problem of a sprawling object creation responsibility.
