COMPANY LOGO HERE

System Name Here

Release #, User Acceptance Test Plan

Functional Name

Revised of: 4/10/23 7:25 PM

Version 1.1 – DRAFT

Function Name Here User Acceptance Test Plan

Document Revision Control

Date Version Changes Author(s) Approver(s)

Last saved: 4/10/23 7:25 PM Page 2 of 8 Document Name Here

Function Name Here User Acceptance Test Plan

Table of Contents

INTRODUCTION..........................................................................................................................................................................4

Overview.....................................................................................................................................................................................4Purpose.................................................................................................................................................................................................... 4Process..................................................................................................................................................................................................... 4Host Implication......................................................................................................................................................................................4Criticality................................................................................................................................................................................................. 4Exclusions............................................................................................................................................................................................... 4

Test Environment........................................................................................................................................................................4Test Environment Establishment.................................................................................................................................................4High Level Test Case Scenarios..................................................................................................................................................5Detailed Test Case Scenarios.......................................................................................................................................................6

Use Cases:...............................................................................................................................................................................................6Security................................................................................................................................................................................................... 6Performance............................................................................................................................................................................................6All Levels of Functionality.....................................................................................................................................................................6Exception Cases......................................................................................................................................................................................6

Test Tasks and Methodology.......................................................................................................................................................6Gather Test Data.....................................................................................................................................................................................7Perform Tests..........................................................................................................................................................................................7Document Test Results...........................................................................................................................................................................7Acceptance Criteria.................................................................................................................................................................................7Conduct UAT Meetings..........................................................................................................................................................................7UAT Sign-off..........................................................................................................................................................................................7

Testing Teams..............................................................................................................................................................................7Test Schedule...............................................................................................................................................................................7

UAT ISSUE LOG...........................................................................................................................................................................8

Name of function here.................................................................................................................................................................8

Last saved: 4/10/23 7:25 PM Page 3 of 8 Document Name Here

Function Name Here User Acceptance Test Plan

Introduction

This document will outline a test plan that will serve to confirm that the system delivered to the user community has met all of the System Name Here - Release # Requirements. Project Managers from all participating departments including Information Systems, Systems Development, and Operations Implementation are intended to review this document. Sign-off of this document implies that the reviewers are comfortable that at the conclusion of the execution of this test plan, the resulting system will be considered fully tested and worthy of being implemented.

Overview

Purpose

This document will outline all of the testing associated with the “Function Name Here” requirement. The “Function Name Here” will allow the System Name user to initiate an address change from within the System Name application without having to send an “external communication form” to the Operations Group. This process will update the Host system of record the next day via batch processing and the function is intended to be seamless to the user.

Process

The user will enter the needed address change information into the appropriate area of the System Name web page. Address changes entered into System Name will reflect real-time. The address changes to the Host system of record will be a one-day delay.

Host Implication

The existing LeMans lockbox process will need to be expanded to include “Bill To” address changes.

Criticality

This requirement was identified as one of the “Highest Priority” items that will be delivered with Release # functionality before the Y2K freeze.

Exclusions

Customer name changes will not be supported in System Name. These calls are warm transferred to the branch. Lease “Bill To” address changes will not go through Code-1 on the host side, and will therefore not show up on the LM960 report. An audit trail report is not needed. The Lease and Retail Management Summary reports and address exception reports will be sufficient. Scripting will not be included in this release of the project.

Test EnvironmentDescribe what will need to be done to set up a complete test environment for this thread (i.e. host environment set up, web environment setup, etc). Also, list the interfaces that will need to be tested. If a host test environment is needed, name what test region will be used (i.e. test1, test2, etc).

Test Environment EstablishmentList what task will need to be completed before UAT testing can begin.

Last saved: 4/10/23 7:25 PM Page 4 of 8 Document Name Here

Function Name Here User Acceptance Test Plan

High Level Test Case ScenariosExample:

The following is a high-level list of what will be tested during the User Acceptance Test phase for On-line Address Changes:

A garage address change can be made to retail and lease accounts in System Name

A bill to address change can be made to retail and lease accounts in System Name

Special Address information can be associated with a bill to address change made to retail and lease accounts in System Name

Incorrect garage address change for a lease customer shows up on the exception report. Validate that the LM960 exception report reflects the correct number of exceptions.

Lease and Retail management summary reports reflect the correct number of address changes made if System Name

Address change FTP to mainframe is successful. File will go through the “daily process”. The regular lockbox file should be run through the same daily process.

Enter an address change in SYSTEM NAME for a lease customer not including phone number for a “Garage” address change

Enter an address change in SYSTEM NAME for a lease customer including phone number for a “Garage” address change

Enter an address change in SYSTEM NAME for a lease customer including “special address” information for “Bill To” address change

Enter an address change in SYSTEM NAME for a lease customer not including “special address” information for “Bill To” address change

Enter an incorrect zip code in SYSTEM NAME for one of the address changes for a lease customer

Enter address change in SYSTEM NAME for a retail customer not including phone number for a “Garage” address change

Enter address change in SYSTEM NAME for a retail customer including phone number for a “Garage” address change

FTP transfer from SYSTEM NAME to the mainframe

Run file through the daily process. The daily process should include the process to create the Lease and Retail Management Summary Reports. The regular lockbox file should be run through the same daily process.

For lease “Garage” address changes:

Check 5.4 record type 1 to make sure the appropriate fields were updated for the garage address changes made in SYSTEM NAME

For lease “Bill To” address changes:

Check 5.4 record type 9 to make sure the appropriate fields were updated for the “Bill To” address changed made in SYSTEM NAME

For retail “Garage” address changes:

Check transaction ILAS to make sure the appropriate fields were updated for the garage address changes made in SYSTEM NAME

Check the Lease and Retail Management Summary Reports for the correct number of address changes that ran through the systems

Check the LM960 exception report for the address change with the incorrect zip.

Last saved: 4/10/23 7:25 PM Page 5 of 8 Document Name Here

Function Name Here User Acceptance Test Plan

Detailed Test Case ScenariosExample:

The Use cases will explain in detail what may happen with each of the potential scenarios that may occur during an Address Change.

Use Cases:

Use Case 1 Result: Enter an address change in System Name that does not include the phone number

Pre-Conditions: This is a “Garage” address change This is a Lease account

Description: Representative requests identifying information from the customer such as name, social

security number or account number. Representative enters information into System Name and initiates the smart search. The results of the smart search are presented. The Representative reviews the results and selects the appropriate account. The account profile is presented to the Representative. The Representative handles the call appropriately and selects the address change function. The Representative submits the request to change the address successfully and is ready for

the next call.

Security

Performance

All Levels of Functionality

Exception Cases

Test Tasks and MethodologyPossible sections are given below. Add or subtract sections according to the thread.

Last saved: 4/10/23 7:25 PM Page 6 of 8 Document Name Here

Function Name Here User Acceptance Test Plan

Gather Test Data

Perform Tests

Document Test Results

Acceptance Criteria

Conduct UAT Meetings

UAT Sign-off

Testing TeamsList what individuals will be involved or needed as part of the UAT testing. Explain their role in testing – setting up an environment, refreshing data, program fixes, testing, etc.

Test ScheduleDescribe the test schedule. Get the UAT dates for this thread from the project plan, and detail what days you will be completing certain tasks.

Last saved: 4/10/23 7:25 PM Page 7 of 8 Document Name Here

Function Name Here User Acceptance Test Plan

UAT Issue Log

Name of function here

UAT ISSUE LOGName of Function Here As of:

UAT ACCOUNT OPEN/CLOSE RESOLUTION

ISSUE NO. DATE MEMBER NUMBER/SSN ISSUE HOLD & DATE

Last saved: 4/10/23 7:25 PM Page 8 of 8 Document Name Here