1 Reduce risk, detect an error early and remove
The risk of problems with the systems during the operational process can be reduced by means of intensive testing. The quality of the software system will be increased, while errors will be found and corrected before the operational release. Test activities in the system or software life cycle should start as early as possible and pursue clearly defined objectives.

2 Specification and Standards
Software Testing can be necessary in order to fulfil industrial standards as well as contractual, legal or specific requirements.

3 Measuring of the Software Quality
The quality of the software can be measured by testing and be expressed by the number of found errors (e.g. serviceability, reliability, efficiency etc.)

4 Avoid Professional Blinkers
An internal quality assurance being subordinated to the project administration, can be blinkered with problems. Here an external quality assurance should become active in addition.

5 Cost reduction
Errors arrive via the Support into the development. There the new developments are delayed by the work on bug-fixes. For the new developments remain less time and more errors are creeping in. All in all the expenses at the departments are increasing.

A flexible external support in the areas of testing / quality assurance offers cover of peak demands without heightening more own capacities. For example, before delivery of new versions or the launch of new software or systems.