OBJECTIVE

The objective of this phase is to prove that the developed system satisfies the requirements defined in the functional specification documents. Several types of tests will be conducted in this phase. First, subsystem integration tests shall be executed and evaluated by the development team to prove that the program components integrate properly into the subsystems and that the subsystems integrate properly into an application. Next, the testing team conducts and evaluates system tests to ensure the developed system meets all technical requirements, including performance requirements. Next, the testing team should conduct security tests to validate that the access and data security requirements are met. Finally, users participate in acceptance testing to confirm that the developed system meets all user requirements as stated in the functional specification documents. Acceptance testing shall be done in a simulated “real” user environment with the users using simulated or real target platforms and infrastructures.

TASKS AND ACTIVITIES

The tasks and activities actually performed depend on the nature of the project.

1.  Establish the Test Environment

Establish the various test teams and ensure the test system(s) are ready.

2.  Conduct Integration Tests

The test and evaluation team is responsible for creating/loading the test database(s) and executing the integration test(s). This is to ensure that program components integrate properly into the subsystems and the subsystems integrate properly into an application.

3.  Conduct Subsystem/System Testing

The test and evaluation team is responsible for creating/loading the test database(s) and executing the system test(s). All results should be documented on the Test Analysis Report. Any failed components should be migrated back to the development phase for rework, and the passed components should be migrated ahead for security testing.

4.  Conduct Security Testing

The test and evaluation team will again create or load the test database(s) and execute security (penetration) test(s). All tests will be documented, similar to those above. Failed components will be migrated back to the development phase for rework, and passed components will be migrated ahead for acceptance testing.

5.  Conduct Acceptance Testing

The test and evaluation team will create/load the test database(s) and execute the acceptance test(s). All tests will be documented, similar to those above. Failed components will be migrated back to the development phase for rework, and passed components will migrate ahead for implementation.