This document contains an instructional text style and an instructional list bullet style, both identifiable in blue paragraphs.

Prior to finalising your document ensure you remove all instructional text. To do this: Word 2003 Right click on any blue paragraph. From the menu Select text with similar formatting. Hit Delete on your keyboard. If instructional text bullet styles are present click on any blue paragraph bullet style and repeat the step. Word 2007 Right click on any blue paragraph. From the menu select Styles and then Select text with similar formatting. Hit Delete on your keyboard. If instructional text bullet styles are present click on any blue paragraph bullet style and repeat the step. NB: Page and sections breaks may be out of alignment until all instructional text is removed.

User Acceptance Test Plan and Test Cases

This template is designed for simple projects. If your project is identified as complex you may need multiple Test Case documents to cover the various components of the solution. In this case, you should also separate the Test Plan out into its own document

Type the Programme Name below if applicable. Delete the line if not required. If the project is identified as complex it is advisable to use a separate document for the Test Plan. This will mean that there will be separate documents for Test Cases & Scenarios and Test Plans

<Programme Name>
Follow these steps to set Document Properties. Word 2003 Open File/Properties/Summary. In the Subject field enter the Project Name. In the Author field enter Your Name. Click OK and save the document. Word 2007 Click MS Office Button/Prepare/Properties. In the Subject field enter the Project Name. In the Author field enter Your Name. Save the document. Update Fields You must now update these fields in the document. Click on a field and then the F9 key. Ensure you update fields on the cover page and headers in all sections of your document.

<Set Project Name in Document Properties>

Information Technology Services

<Set Project Name in Document Properties>

UAT Plan and Scenarios

Document Identification File name: Version: Status: Date: Prepared by: Contributors: 0000-Business_Analysis Template UAT Plan and Test Cases v103.docx 103 Final

The status field should indicate whether the document is Draft or Approved. Contributors are stakeholders that have contributed directly to the contents of this document.

Responsible Authorities Project Sponsor: Project Manager: Senior User: Senior Supplier: Service Owner: System Owner:

Add or delete Authorities as required.

Page 2 of 16

<Set Project Name in Document Properties>

UAT Plan and Scenarios

Document purpose
The purpose of this document is to outline the User Acceptance Test (UAT) activities planned for the <name of solution> application and will focus on the following objectives: To define the scope of the UAT To define the sources of the information used to prepare the plan To define the environment and test tools required to conduct the UAT To define scenarios, test cases and scripts to be carried out To outline activities required to prepare for and conduct the UAT To communicate to all responsible parties the tasks to be performed To validate that the solution is performing at an acceptable level based on criteria agreed to by the delivery team and the customer

Table of contents
1 Introduction ........................................................................................................... 4
1.1 1.2 Audience ...................................................................................................................................4 References ................................................................................................................................4 In scope .....................................................................................................................................6 Out of scope ..............................................................................................................................6 Assumptions .............................................................................................................................6 Risks/issues ..............................................................................................................................6 Constraints ................................................................................................................................6 UAT Approach ...........................................................................................................................8 Solution acceptance criteria .....................................................................................................8 Roles and responsibilities .........................................................................................................8 UAT resource requirements ...................................................................................................10 UAT activity list & schedule .....................................................................................................11 Problem reporting/corrective action ........................................................................................11 Scenario - <Scenario name> ..................................................................................................12 Glossary ..................................................................................................................................14 Appendix .................................................................................................................................14

Scope overview..................................................................................................... 6
2.1 2.2 2.3 2.4 2.5

UAT plan ................................................................................................................ 8

3.1 3.2 3.3 3.4 3.5 3.6

4 5

UAT scenarios & test cases ............................................................................... 12

4.1 5.1 5.2

Appendices ......................................................................................................... 14

Document control ............................................................................................... 15

Page 3 of 16

<Set Project Name in Document Properties>

UAT Plan and Scenarios

Introduction

You should provide here a brief overview of the project that is no more than two paragraphs long. This should present in as few words as possible the background and aims of the project. This section must reflect the content in the Service Brief / Business Case (depending on which stage the project is at). While this may seem needlessly repetitive, keep in mind that the audience may not have seen the preceding project documents for months if at all.

1.1

Audience

You are free to leave the text below as is or alter it according to your needs. The UAT document is intended for use by the following people:
No 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. Name Project Sponsor Business System Owner Senior User Business Subject Matter Expert Business Users Service Owner Senior Supplier Project Manager UAT Manager Testers Solution Architects Other ITS Staff User Description The person to whom the project will be delivered and who will sign off on its successful delivery The person within the business who has been nominated at the system owner The nominated Senior User is usually expected to review the document and approve its use as the basis for UAT These people are the initial contributor to the Business Requirement Documents. They will be required to carry out the UAT according to the test cases and scripts Nominated front end staff to perform appropriate testing and gauge results. The person responsible for the outcomes of the service being delivered External Third parties that will be responsible for the supply of software or other services The project manager will use this document as a basis for planning the project and estimating the effort, resources and cots involved in delivering the desired outcomes The person responsible for managing the UAT effort The People who will be responsible for conducting UAT The designers of this solution to assist the testers where required to provide further clarity on limitations and constraints Other staff may refer to this document to help them improve their understanding of the deliverables and how it may be related to the work they are undertaking

1.2

References

It is expected that most projects will make use of the following documents types: Service Brief Stakeholder Analysis spread sheet Business Case Business Requirements Overview Requirements Traceability Matrix Use Cases

If these documents have been created for your project, they should be listed in this section. It is important to list all relevant documents here so add as many entries as needed. Other documents such as meeting minutes and those created by external parties may also be referenced.

Page 4 of 16

<Set Project Name in Document Properties>

UAT Plan and Scenarios

The reference structure provided below is a guide only. Include as much information as makes sense for each document. We generally do not include the location of documents as these are typically not very stable and are often inaccessible to the audience anyway.
No 1. 2. 3. Document Name Author Publisher Version Year

Page 5 of 16

<Set Project Name in Document Properties>

UAT Plan and Scenarios

2
2.1

Scope overview
In scope

Scope statements should define the boundaries for what the project will be attempting to deliver. They may refer to subjects such as UAT approach, UAT plan and etc. This is an outline of what will be delivered as part of this test plan. If it is intended to use high level modules as part of this test plan, completion of this section is at the discretion of the author, and is directed by the size of the project. If outlining the scope for a specific module of a project then completion of all sections listed under scope overview is advised. The following are considered to be within the scope of this UAT plan: 1. 2. 3. Testing of appropriate validation routines Testing of appropriate access priveleges. Testing of adequate report generation and functionality

2.2

Out of scope

List any specific exclusions from this UAT. It is important to be explicit and precise with each of the statements listed here. These statements should be reviewed carefully by the project manager, senior users and business sponsor. The following are considered to be excluded from the scope of this UAT: 1. Functional system testing 2. System parameter testing

2.3

Assumptions

Clearly document any assumptions and dependencies that have been made that are important for understanding the context of this document. Each assumption should be presented in only enough detail to allow the reader to understand the significance of the assumption. The following assumptions have been made when formulating these requirements: 1. 2. Significant system issues which may delay testing will be fixed quickly Adequate project team resources will be made available as a precondition for UAT to commence

2.4

Risks/issues

List any activities or deliverables that the successful outcome of this UAT is depending on but for which the UAT manager is not directly responsible for providing. Examples: The successful delivery of this UAT is dependent upon the following: 1.

2.5

Constraints

A constraint describes any known restrictions or limitations imposed on the UAT. Constraints are normally expressed by the project sponsor or steering group. As with assumptions, any changes to these constraints are likely to have an impact upon the project scope, business requirements and solution design. The following constraints have been identified that may limit the execution of this UAT:
Page 6 of 16

<Set Project Name in Document Properties>

UAT Plan and Scenarios

1.

Certain technical requirements wont be available and may restrict aspects of User Acceptance Testing

Page 7 of 16

<Set Project Name in Document Properties>

UAT Plan and Scenarios

3
3.1

UAT plan
UAT Approach

UAT will be based on test scenarios and acceptance criteria agreed to by the Project Manager, ITS and business users. The test cases have been sourced from the Business Requirement Document (BRD) or use case documents. The test scenarios will be mapped to functional groups from Requirements in the BRD. Test results will then be evaluated by business users based on expected results for each scenario. The following are preconditions for UAT commencement List any pre-conditions that must be in place to support the commencement of the UAT

3.2

Service Acceptance Criteria

Define a list of acceptance criteria agreed to by the Business owner/ users, BRM and Project Manager. Refer back to the acceptance criteria in the business case which must be further clarified and confirmed with the relevant business and ITS stakeholders. The following are examples of acceptance criteria that you might use; 1. The UAT user(s) have executed all test scenarios assigned to them 2. A requirement will be deemed to be accepted once it has reached a PASS indicator during UAT 3. Partial compliance will be deemed to constitute a FAIL indicator

3.3

Roles and Responsibilities

ITS will be responsible for conducting UAT sessions. The UAT sessions will be managed by the ITS Project Manager and Business Analyst. The tables below specify the person(s) responsible for, and involved in, all aspects of UAT including preparation and execution

3.3.1

Internal Resources

Define a list of relevant personnel who will be engaged to support the delivery of UAT. Please alter or expand the current list to include other roles and responsibilities if applicable For projects that are not allocated a Change and Communication Manager, the responsibilities of Change and Communication Manager are expected to be carried out by the Project Manager
No 1. Name Role Project Manager Responsibilities Review UAT test strategy and the test plan to ensure its alignment with master project schedule Communicate with customer to agree on format, scope and acceptance criteria of UAT prior to commencing UAT Accountable for the UAT phase

Page 8 of 16

<Set Project Name in Document Properties>

UAT Plan and Scenarios

No 2.

Name

Role Business Analyst

Responsibilities Develop UAT plan, strategy and cases Communicate/educate participants on testing approach and expectations Conduct the UAT session(s) Provide functional support during UAT Confirm logged UAT defects are valid defects and forward to development team Review outstanding issues for resolution and coordinate re-testing as required Prepare a list of unresolved issues to be handed over to the operational team and business Review the Results of User Acceptance Testing Approve and sign-off of results Advised of rollout of Solution Sign-off on delivery of the solution Validate the communications are in line with project communication plan Update the communications in the communications calendar Organise the required venue for UAT Ensure the required UAT environment is ready for UAT (Refer to Section 3.4) Review all UAT problem reports once PM and BA have determined that the issues are within the scope of the project Ascertain that the technical aspects of the solution meet requirements Ascertain operational aspects of the solution meet SOE requirements Review bug fix from UAT sessions Advise on the design of the solution Advise on test methods to be performed Analyse results and determine further testing if required

3.

Project Sponsor / Service Owner

4.

Change and Communication Manager

5. 6.

Project Co-ordinator Service Delivery Manager

7. Subject Matter Experts

3.3.2
No 1. Name

Business users
Role Business User Responsibilities Conduct User Acceptance Testing

Define a list of Business users who will be engaged to support the delivery of UAT.

Execute and Identify Scenarios

Page 9 of 16

<Set Project Name in Document Properties>

UAT Plan and Scenarios

No 2.

Name

Role Vendors

Responsibilities To advise on system limitations and performance parameters To advise on appropriate test cases To be advised of any required changes to the system as a result of UAT

To advise on System limitations and performance boundaries

3.4

UAT resource requirements

3.4.1 Site

List any UAT requirements in respect of the physical location where the UAT will be conducted, e.g. The site must provide sufficient space (including seating and desk) with a minimum of 2 concurrent users and up to 4 concurrent users The site must provide sufficient number of RJ45 wall sockets that allow a minimum of 2 concurrent connections and up to 4 concurrent connections

3.4.2

Hardware

List any UAT requirements in respect of hardware that will be required. e.g. 4 Windows based desktop computers with a minimum of i5 2.0 GHz process 2 GB RAM 320 GB HDD 4 units of 21 inch 16:9 LCD monitors each with A VGA and/or DVI input A minimum resolution of 1440 x 900

3.4.3

Software

List any UAT requirements in respect of software that will be required. e.g. For each Windows based desktop computer the following software must be installed Windows XP 32bit SP2 Internet Explorer 7 !! The application you are testing if it is not web based

3.4.4

Data

List any UAT requirements in respect of sample data that will be required. e.g.
Page 10 of 16

<Set Project Name in Document Properties>

UAT Plan and Scenarios

The Customer table must contain at least (not limited to) 2 sets of complete and valid data sets 2 sets of incomplete and invalid data sets

3.4.5

Network

List any UAT requirements in respect of any database, virtual environment, remote terminal connectivity that will be required. e.g. For each Windows based desktop computer, it be have the following connection session enabled A connection session to Oracle database

3.4.6

Other

List any UAT requirements for any other aspect. e.g. There must be at least 8 sample username and password created

3.5

UAT activity list & schedule

Below is an approximate schedule for the first round of UAT sessions. Any UAT related activities after bug fix and re-test will be documented in the project schedule.
No 1. 2. Activity Responsibility Start Date End Date

3.6

Problem reporting/corrective action strategy

Describe the strategy to report issues/problem found during and after the UAT session. Describe the strategy to verify the validity of issues/problems reported and how the issues and problem will be addressed

Page 11 of 16

<Set Project Name in Document Properties>

UAT Plan and Scenarios

UAT scenarios & test cases

A Scenario is a sequence of test cases that have been strung together to mimic what a user of the system may be expected to do at one sitting in order to achieve a desired outcome. For example, a scenario called Alter meeting time may be designed to test the system as if a user where to: log in, open the calendar, search for an event, open the event, alter the event time, save the event, log off. The usage of scenarios is optional. A Test Case is sequence of steps involving the user and the system that are designed to test whether a particular function or capability of the system is behaving as expected.

The Result will be rated in accordance with the matrix below: Pass (P): the sequence/scenario can be executed following the specified user behaviour and expected system behaviour Fail (F): the sequence/scenario is not executed or has failed the execution process

The Actual System Behaviour will be rated in accordance with the matrix below: As expected (AE): the actual system behaviour matches the specified expected system behaviour Description: Please describe the actual system behaviour being observed and note especially the variation to the expected system behaviour

4.1

Scenario - <Scenario name>

Scenario Description

Scenario Preparation

4.1.1

<Test Case Name>

Provide a short description of what is being tested. For example: Authentication: This test case is designed to test the systems login function and its ability to respond to user under different scenarios
Seq. User Behaviour Expected System Behaviour Actual System Behaviour Business Requirement Reference Seq. Result

1.
Page 12 of 16

<Set Project Name in Document Properties>

UAT Plan and Scenarios

Seq.

User Behaviour

Expected System Behaviour

Actual System Behaviour

Business Requirement Reference

Seq. Result

2. 3.

Page 13 of 16

<Set Project Name in Document Properties>

UAT Plan and Scenarios

Appendices

Add any appendices that are needed to support the requirements. Some standard tables are provided which you may delete if they are not appropriate for your project but we encourage you to make use of them. Examples: Test data

5.1

Glossary

Term

Definition

5.2

Appendix

Page 14 of 16

<Set Project Name in Document Properties>

UAT Plan and Scenarios

Document control

Approvals
Version No. Approval Date Name Title Signature/Email ref

Review history
Version No. Review Date Name Title

Version history
Version No. Version Date Summary of Changes Prepared by:

Page 15 of 16

<Set Project Name in Document Properties>

UAT Plan and Scenarios

Template control
Delete the template control page prior to using/publishing your document.
Template Name User Acceptance Test Plan and Test Cases Location ITS>Projects>Project Toolbox>Templates, Guides and Tools

Template approvals
Version No. Approval Date Name Title Signature/Email ref

Template review history

Version No. 001 Review Date August 22 2011 Name Kosta Stathoulis Heather Foster Rajesh Padmawar Ann Turudic 002 August 30 2011 September 12 2011 David Bonello Cassandra Davies Title Senior Business Analyst Test Analyst Solution Architect Change & Communication Manager Service Delivery Manager Senior Project Manager

Template version history

Version No. 001 002 003 004-007 008 009 100 101 102 103 Version Date August 19 2011 August 22 2011 September 12 2011 October 2011 November 12 2011 November 16 2011 12 December 2011 18 January 2012 18 January 2012 19 January 2012 Summary of Changes First Draft 2
nd rd

Prepared by Ryan Lin Ryan Lin Ryan Lin Kosta Stathoulis Kosta Stathoulis Deepa Ponnappan Kosta Stathoulis Deepa Ponnappan David Hodgman Deepa Ponnappan

draft incorporating review feedback

3 draft incorporating review feedback SBA Team review 7

th

draft incorporating feedback

Minor edits to guideline section Acceptance of all edits and final endorsement Modifications based on PMO review Internal Review Apply changes

Page 16 of 16