User Acceptance Testing

After completion of system testing & their modifications, the project management concentrates on User acceptance testing to collect feedback.

These are two ways to conduct user acceptance testing. They are µ - testing and b - Testing. 

 
µ - Testing                                

1. By real customers          

2. In development site       

3. Suitable for Applications 

  b - Testing

1. By Model Customers

2. In Model Customer site

3. Suitable for Products

6. Release & Maintenance: -

After completion of user acceptance testing and their modifications, the project management concentrates on the release team.

This release team consists of a few programmers few test engineers & some hardware engineers.

a)     Port Testing

b)     Test Software Changes

 a) Port Testing: -

The corresponding release team conducts port testing on the customer site. During this test, the release team observes the below factors.

•          Compact Installation
  
•         Overall Functionality
  
•         Input device handling
  
•         Output device handling (Like Monitor, Printer, etc)
  
•         Secondary storage device handling (Like Floppy disk, CD-Rom, etc)
  
•         Operating System with other handling
  
•         Co – Execution with other software.
  

After comparison of Port testing, the responsible release team Provides required training sessions to the customer. Side people & get back to the organization.

b) Test Software Changes: -

During the utilization of the released software, the customer side people send change requests (CR) to the organization. To receive these CRs, the organization establishes a special team along with a few programmers, some test engineers & a project manages category person. This team is called “Change Control Board” (CCB).