1 / 8

UAT Launch

UAT Launch. 5th February 2003. Introduction. There are 8 distinct parts of UAT to take place between January-April 2003 pre-implementation: RDM/ Sorter Tests x 2 Initial User Validation RMS data set-up-(13 scripts) Parallel Run 1 & 2 –(24 scripts) Foundation Data User Validation

karina-morrison
Download Presentation

UAT Launch

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. UAT Launch 5th February 2003

  2. Introduction • There are 8 distinct parts of UAT to take place between January-April 2003 pre-implementation: • RDM/ Sorter Tests x 2 • Initial User Validation • RMS data set-up-(13 scripts) • Parallel Run 1 & 2 –(24 scripts) • Foundation Data User Validation • Data Validation of 4c in Parallel Run 2 • Data Integrity • Ongoing System Test of CRs, retests, ad hoc functionality

  3. Purpose • Project Odyssey is undertaking these two phases of User Acceptance Testing to allow business users to test that the Odyssey solution provides the requisite functionality, within acceptable tolerances • This is designed to build confidence in the solution before real users commence using it • A number of scripts have been created to be executed during these phases • There will be two elements of testing via scripts performed by the business users: • RMS data set-up 06/02-14/02 • Parallel Run 1 tbc • A second phase of UAT using scripts to test the solution will be performed by Super-users from the business in March • UAT is interlinked with PPT, especially the running of the integrated batch. This is a critical part of PPT, and timings might vary from plan so flexibility & pragmatism will be required within UAT • There will be a different feel to UAT than System Test as users will only be accessing the RMS front end –so more enjoyable!

  4. Team & Structure

  5. Script Ownership

  6. Environment • 8 desks on ground floor of new building-previous System test location • RMS installed on each PC for the users • RMS Production Environment to be used for testing • New log-ons for access to UAT environments • Daily administration like System test • Access to RMS governed by PPT batch running-need for flexibility • Current timetable depends on PPT success in starting running the batch • Need to be aware of updates/ checkpoints during the day at which decisions will be taken on timings of system availability for UAT • Likely updates for this week • Wednesday 5.00pm • Thursday 9.00am, 1.00pm & 5.00pm • Friday 9.00am

  7. Timetable for script execution • Timetable planned around batch availability • Estimated timings of each step within script allow a tailored plan in which individual steps are tested • Allowance that the level of data to be entered can be reduced and results pro-rated • Timetable to be circulated to all users

  8. Administration & Reporting Back-up worksheet capturing red sections where time taken to execute step of script was outside tolerance Similar admin spreadsheet to monitor successful testing by section

More Related