Quality control is an integral part of the software development process that ensures that a finished product meets expectations through predictable and peer-checked design methods. This policy defines quality control measures to make the software development process as efficient and successful as possible.

From the policy:

Summary
Customer satisfaction is the key to business prosperity, so it is not sufficient to merely test software to confirm that it works. Bugs can and do appear months or even years later. While eliminating these bugs may not always be achievable 100% of the time, quality control processes based on code review can help keep their numbers at a minimum.

Furthermore, quality control regulations help establish operational standards that can be followed by new and existing employees to help plan and prioritize workloads and establish credible developmental milestones and due dates.

Policy guidelines

• Quality control staff: The quality control/development manager will establish project managers and personnel to perform quality review for each project. These personnel will work with the developers to examine code to ensure adherence to project/quality standards and goals. Results and feedback will be communicated to project managers.
• Customer focus: To formulate a project plan, current and future customer needs must be examined, established, and agreed upon by all involved parties. This provides the foundation to build out the project requirements.
• Documentation of requirements: All projects should prepare a software requirements specification document that describes the functions, performance, and interface requirements of the finished software product. Where possible, future software needs and/or upgrades should be included in the documentation.