Thursday, August 31, 2006

UAT outline description

From JISC Infonet

User Acceptance Testing is a key feature of projects to implement new systems or processes. It is the formal means by which we ensure that the new system or process does actually meet the essential user requirements. Each module to be implemented will be subject to one or more User Acceptance Tests (UAT) before being ‘signed off’ as meeting user needs. The following overview answers some of the main questions that have been asked about UATs.

A User Acceptance Test is:
  • A chance to completely test business processes and software
  • A scaled-down or condensed version of a system
  • The final UAT for each system module is the last chance to perform the above in a test situation
The scope of each User Acceptance Test will vary depending on which business process is
being tested. In general however, tests will cover the following broad areas:
  • A number of defined test cases using quality data to validate end-to-end business processes
  • A comparison of actual test results against expected results
  • A meeting/discussion forum to evaluate the process and facilitate issue resolution
Objectives of the User Acceptance Test are for a group of key users to:
  • Validate system set-up for transactions and user access
  • Confirm use of system in performing business processes
  • Verify performance on business critical functions
  • • Confirm integrity of converted and additional data, for example values that appear in a look-up table
  • •Assess and sign off go-live readiness
User acceptance test UAT

No comments: