1 / 9

Update on UAT and Parallel System Test

Update on UAT and Parallel System Test. 10 December 2002. Contents. System Test II Timeline for setup of secondary environments Constraints and likely date for availability of environments Actions required to progress Execution plan and resource requirements for System Test II

jaime-tillman
Download Presentation

Update on UAT and Parallel System Test

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. Update on UAT and Parallel System Test 10 December 2002

  2. Contents • System Test II • Timeline for setup of secondary environments • Constraints and likely date for availability of environments • Actions required to progress • Execution plan and resource requirements for System Test II • UAT preparations • Script build plan and resource requirement • Infrastructure • UAT execution • Integration with System Test II • Resource requirement • Execution plan

  3. System test II – secondary environment build 24 to 29/12 16/12 17/12 18/12 19/12 20/12 21/12 22/12 23/12 2/1 4/1 30/12 31/1 1/1 3/1 Release of code from system test XMAS HOLIDAY • Build mainframe code • promote acceptances • Rebind SYST • Mangle JCL • Backup SYST04 libraries • Build mainframe schedule • Backup SYST04 OPCA • Copy and amend SYST04.CNTL • Remove production refs from SYST04 • Backup amended SYST04 runtime library Earliest possible start date for System Test II • Refresh data across RMS and Mainframe environments • Data extracts from SYST (2 days) • Data loads into RMS DEV (5 days) • Refresh DIDOS and UOLAS DEV environments from production Likely start date for System Test II • Complete RDM and RDF build • Align code with system test • Configure dB tables • Refresh data from production/RDM String • Build secondary IF schema • Confirm connectivity requirements • Create additional participating hosts • Build new merchandising, warehousing • and forecasting schemas • Test connectivity

  4. System test II – secondary environment buildAssumptions and constraints Assumptions and constraints: • All planned activities are linked to end of current system test, i.e. no practical parallel work streams exist. • Mainframe activities likely to be achievable without disrupting PPT activities • Absence of experienced conversion resource (DK/SM) on site w/c 16/12 is a concern • Proposed plan assumes availability of RDM TRN during Jan ‘03 for testing • Proposed plan assumes access to Richard Hemmings to build and refresh RDM TRN • Proposed plan assumes access to IF resource to build and test second IF schema • Holiday arrangements over Christmas period likely to determine earliest start of System Test II phase (most likely is 2/1)

  5. System test II – resource requirements • System Test II will need to support continued end to end transactional testing across the majority of applications and business areas rather than point retesting of small areas. This requirement will place a demand on resource to progress STII testing in the following areas: • Mainframe and branch batch and data support • RMS batch, technical and data support • RDM batch and data support • RDF batch and data support • IF technical support • Functional support across RMS, Minerva, Teradata, Finance, RDM, RDF, Branch as a minimum

  6. System test II – secondary environment buildActions to progress

  7. UAT Preparation – Milestones for scripting

  8. UAT Preparation – Script build requirements * Same scripts as parallel run 1 – time added is for revisions following parallel run 1

  9. Consolidated resource planning NOTES: Pinch points for user demand in February and March (especially February) December total does not include and prep for train the trainer or training in general User profile suggests UAT scripts (60 days) need to be built in December as Jan, Feb and March get congested

More Related