V - Model : Validation Phases

1. Validation Phases

   1. Unit Testing

In the V-model of software development, unit testing implies the first stage of dynamic testing process. It involves analysis of the written code with the intention of eliminating errors. It also verifies that the codes are efficient and adheres to the adopted coding standards. Testing is usually white box. It is done using the Unit test design prepared during the module design phase. This may be carried out by software testers, software developers or both.

2. Integration Testing

In integration testing the separate modules will be tested together to expose faults in the interfaces and in the interaction between integrated components. Testing is usually black box as the code is not directly checked for errors. It is done using the integration test design prepared during the architecture design phase. Integration testing is generally conducted by software testers.

3. System Testing

System testing will compare the system specifications against the actual system. The system test design is derived from the system design documents and is used in this phase. Sometimes system testing is automated using testing tools. Once all the modules are integrated several errors may arise. Testing done at this stage is called system testing.

4. User Acceptance Testing

Acceptance testing:

• To determine whether a system satisfies its acceptance criteria or not.
• To enable the customer to determine whether to accept the system or not.
• To test the software in the "real world" by the intended audience.

Purpose of acceptance testing:

- To verify the system or changes according to the original needs.

Procedures for conducting the acceptance testing:

Define the acceptance criteria:

• Functionality requirements.
• Performance requirements.
• Interface quality requirements.
• Overall software quality requirements.

Develop an acceptance plan:

• Project description.
• User responsibilities.
• Acceptance description.
• Execute the acceptance test plan.