User Acceptance Test
1. Definition
The purpose of User Acceptance Testing (UAT) is to ensure that the solution by the project meets the functional and non-functional requirements specified in the business requirements. UAT may also identify issues that have not been specified in the BRD such as those relating to usability. UAT is the final step before rolling out the solution. UAT is typically carried out by end users in an environment that closely models the real world. A well-managed UAT process will give the Project Sponsor, project team and end users confidence that the solution being delivered meets the requirements.
This document outlines the plan for UAT of the project deliverables. This document is a high level guide and will initially be developed during requirements gathering as part of the Business Analysis stage. Detailed test scripts/cases will be developed as part of the UAT Plan and will be used to record the results of user testing. Testing itself and the formal recording of UAT results takes place during the Acceptance stage.
2. Roles and Responsibilities
|
Role |
Responsibilities |
Name |
|
Project Manager |
· Communication with the Business Assurance Coordinator to agree format and scope of UAT · Ensure acceptance criteria are agreed prior to commencing UAT |
Chris Konczak |
|
Technical Architect |
· Validation of UAT environment |
Gordon McKenna |
|
Testers |
· Execute test scripts/cases · Document test results |
See table below |
4. Test Participants
The following business owners are responsible for testing NEWS
|
Name |
Area Represented |
Testing Area of Responsibility |
|
|
Jamie Morton/Paul Martin (Qlikview) |
ADMISMI |
|
|
|
Susan McLaren |
HRMI |
|
|
|
Emma Lyall/Jim Galbraith |
ORGMI |
|
|
|
Jamie Morton/Paul Martin (Qlikview) |
STUDMI |
|
|
|
Maureen Masson/Richard Mann |
SPACEMART (EBISMI) |
|
|
| EFINARCH | Gordon Forbes | ||
| Stefanie Hay | TELSMI | ||
| UNIDESKMI | Andrew McFarlane | ||
5. Test Schedule
|
Activity |
Responsibility |
Target Date |
Date Completed |
|
Confirm testers for UAT |
Project Sponsor / Business Assurance Coordinator |
|
|
|
Confirm test scenarios, test data and scripts/cases |
Project Sponsor / Business Assurance Coordinator Business Analyst |
|
|
|
Ensure UAT environment is configured for testing i.e. new functionality and test data is migrated to the TEST environment prior to the start of UAT
|
Project Sponsor / Business Assurance Coordinator Business Analyst Systems Analyst / Designer Technical Architect |
|
|
|
Oversee testing by UAT participants |
Project Sponsor / Business Assurance Coordinator |
|
|
All upgraded functionality and test data will be migrated to the test environment prior to the start of user acceptance testing.
6. Assumptions
- The UAT environment will be available and fully configured ahead of the UAT.
- The business team has reviewed and accepted functionality identified in the Business Requirements Document (BRD) and System Design Document (SDS).
- Code walkthroughs/reviews have been completed by the Development Team and signed off as part of the Peer Project Build Review (PPBR)
- Integration testing, including where relevant load and performance testing, has been completed and signed off as part of the Peer Project Integration Review.
- Testers will test the functionality documented in the approved BRD (taking into account any changes in business requirement subsequently agreed by the Project Team)
- Resources identified in this plan are available to conduct the UAT and address issues as they are raised by the test team.
-
[Business Analyst should record any additional assumptions here]
The Project Manager must notify the Project Sponsor if any of these assumptions are not correct before commencing the UAT.