1 / 11

UK Link Programme Update to PNUNC August 13 th , 2013

This session provides an overview of the anticipated programme activity for the UK Link replacement. Includes indicative timescales and detailed path analysis for Logical Analysis, High Level Design, Detailed Design, Build, Test, Release, Data Cleansing & Migration, and Stakeholder Engagement.

esthert
Download Presentation

UK Link Programme Update to PNUNC August 13 th , 2013

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. UK Link Programme Update to PNUNC August 13th, 2013

  2. Introduction • The aim of this session is to provide an overview of the anticipated programme activity for the replacement of UK Link • It should be noted that at present these timescales are indicative and as more information becomes available as the programme progresses formal updates will be provided. 2

  3. Programme Indicative Path Logical Analysis DBI Sourcing HLD Detailed Design Cutover and go-live Build & Dev Test System & User Test Design R2 Cutover and go-live Build Test Data Cleansing Stakeholder Engagement Note: assumes a release based approach 3

  4. Indicative Path:Logical Analysis Logical Analysis • Logical Analysis Key Deliverables • Phase started 25th March 2013 • Develop Logical Process & Data Models for the requirements captured in the BRDs during Project Nexus and known future requirements • Undertake a detailed review of the Non-Functional Requirements. • Define and introduce Competency Centre to support delivery of future changes as an enduring service • Output will inform and support all future phases of the Programme Note: assumes a release based approach

  5. Indicative Path:High Level Design • High Level Design Key Deliverables • High Level Architecture Design, details the high level future state business processes and solution design • Security Architecture and Policies, details at high level the framework to protect all assets • Integration Architecture, details at high level, the integration framework between all systems, both internal to Xoserve and external • Test Strategy & Plan, defines the overall test approach and each test phase with corresponding timelines • Programme Delivery, definition and timescales of the remaining phases and indicative release plan High Level Design Note: assumes a release based approach

  6. Indicative Path:Detailed Design • Detailed Design Key Deliverables • Detailed Architecture Design • Detailed Security Architecture and Policies • Detailed Integration Architecture • Detailed Test Strategy & Plan, defines the overall test approach for each test phase with corresponding timelines • Programme Delivery, definition and timescales of the remaining phases and detailed delivery plan • Detailed Data Migration plan Detailed Design Note: assumes a release based approach

  7. Indicative Path:Build Build • Build Key Deliverables • Technical Specification; • Batch Job Configuration; • Installation Guides • Training Content & Materials; • Test scripts • Cutover plan • Service Transition plan • Dependencies / Impact on Legacy Systems Note: assumes a release based approach

  8. Indicative Path:Test • Test Key Deliverables • Under take User and System Test • Review test results • Dev Test • System Test • Integration Test • Performance Test • User Acceptance Test • Technical / Operations Test • Industry / Regulatory • Transition handover document System & User Test R1 Go live Note: assumes a release based approach

  9. Indicative Path:Release 2 Design R2 Go live Build Test • Release 2 Key Deliverables • Same deliverables as Release 1, without High Level Design and potentially shorter timelines. Note: assumes a release based approach

  10. Indicative Path:Data Cleansing & Migration • Data Cleansing Key Deliverables • Data Cleansing Strategy & Approach • Identification of Data Issues • Data Topics • Data Profiling • Data Issue Analysis & Prioritisation • Industry Engagement • UK Link Steady State Cleansing • Data Cleansing Progress Reporting Data Cleansing & MIgration Note: assumes a release based approach

  11. Indicative Path:Stakeholder Engagement • Stakeholder Engagement Key Deliverables • Identify stakeholders • Understand Stakeholder Expectations • Analyse and Map Stakeholders (Involve / Influence) • Develop, maintain an effective communication plan (Review / Modify) • Increase Stakeholder cooperation and success in delivering overall objectives (Impact of Change, Testing phases) • Reduce the risk of misunderstanding the scope of work Stakeholder Engagement Note: assumes a release based approach

More Related