A bug indicates a potential need for corrective work on already implemented code. Fixing a bug might result in no action beyond changing the state of the bug, or changing the code. To prevent bug fixes from disrupting working code, the bug fixing process must be systematic and controlled. After a bug fix has been completed, the changed code must be checked against the design and coding guidelines, unit tested, reviewed, integrated, and checked in. The bug owner follows all code requirements that pertain to the affected code, as well as the design concepts and guidelines that drove the implementation. Failing to do so can cause the "fix" to be worse than the original problem.