If sufficient functional requirements are not provided upfront, then all these "fixes" in production are really just change requests and phase I, II, ~ deployments. A solution that has been in production for months shouldn't be considered "broken" just because someone wakes up one morning and decides it should be working in a different way.

Really, software or database requirements documentation should include test plans with specific screen/report mockups, data inputs, and data outputs that can be unit tested by the programmer during the initial development phase and then reproduced and validated by QA.