[Study] Foote, B. & Yoder, J. (2000) Big Ball of Mud.

Some definitions:

THROWAWAY CODE: is quick-and-dirty code intended to be used only once.

PIECEMEAL GROWTH: elements of system sprawl in an uncontrolled fashion.

KEEPING IT WORKING: a strategy of changes taking place at a specific part, while the whole system continues to function.

SHEARING LAYERS: layers develop between parts that change quickly and parts that change slowly

SWEEPING IT UNDER THE RUG: try to control decline by cordoning off the blighted areas.

RECONSTRUCTION: tearing everything down and start over.

Forces:

Forces that lead to the BIG BALL OF MUD include:

1. Time: deadline pressure lead to bad architecture
2. Cost: architecture is expensive. 
3. Experience: affect on the degree of architecture sophistication
4. Skill:
5. Visibility: hard to make the programe visible for build and evaluate
6. Complexity: the organization of the system reflects the sprawl and history of the organization that built it
7. Change: subsequent change is unavoidable.
8. Scale: small vs large project

Reference:

Foote, B., & Yoder, J. (1997). Big ball of mud.Pattern languages of program design, 4, 654-692.