When the code is complete.

When the design is complete.

When the software requirements have been approved.

When the first code module is ready for unit testing

Done by the Developer

Done by the Test Engineers

Done By Management

Done by an Entity Outside the Project’s sphere of influence

(iii) and (ii)

(i) and (iv)

(ii) and (i)

(i) and (iii)

Unit testing, system testing, acceptance testing, maintenance testing.

System testing, unit testing, acceptance testing, maintenance testing.

Acceptance testing, system testing, maintenance testing, unit testing.

Unit testing, maintenance testing, system testing, acceptance testing.

To cause as many failures as possible so that defects in the software are identified and
can be fixed

To confirm that the system works as expected and that requirements have been met

To assess the quality of the software with no intention of fixing defects

To give information to stakeholders of the risk of releasing the system at a given time