Transition Plan (TP)

Transcription

1 Transition Plan (TP) Transportation Grant Fund Database Team 14 Team Members Roles Roles Primary Secondary Muruganantham Raju Project Manager Feasibility Analyst Kirill Khistyaev Software Architect Project Manager Karim Sacre Prototyper Requirements Engineer Reza B Far IIV&V Quality Focal Point Secondary Stephan Rice IIV&V System Requirements Engineer Zhanna Seitenova Life Cycle Planner Requirements Engineer Ayman Khalil Operational Concept Engineer Software Architect 11/17/2011 Transition Plan (TP) Document Version Date: 11/17/2011

2 Version History Date Author Version Changes made Rationale 11/17/11 RM 1.0 All sections of the ICSM TP template has been updated Initial draft of the TP to be delivered with Draft DCP Transition Plan (TP) Document ii Version Date: 11/17/2011

3 Table of Contents TRANSITION PLAN (TP)... I VERSION HISTORY... II TABLE OF CONTENTS... III TABLE OF TABLES... IV TABLE OF FIGURES... V 1. Transition Strategy Transition Objectives Transition Process Strategy Preparing for Transition Hardware Preparation Software Preparation Site Preparation Stakeholder Roles, Responsibilities and Schedule... 9 Transition Plan (TP) Document iii Version Date: 11/17/2011

4 Transition Plan (TP) Template Version 1.0 Table of Tables Table 1: Transition Schedule... 9 TP_DCP_F11a_T14_V1.0.doc iv Version Date: 01/12/09

5 Transition Plan (TP) Template Version 1.0 Table of Figures No table of figures entries found. TP_DCP_F11a_T14_V1.0.doc v Version Date: 01/12/09

6 1. Transition Strategy The project follows pilot transition strategy wherein the set of features developed in iteration will be transitioned at the end of the iteration to the support team. The pilot transition also includes basic acceptance tests and training document corresponding to the features targeted for the given iteration. The participating stakeholders will be identified at the beginning of each iteration and be notified about the transition activities upfront. At the end of the project phase, fully operational system will be transitioned to customer site. During this phase, thorough transition readiness check will be conducted to confirm that the full functional system is ready for use by the customers. Transition includes not only product transition but also project transition. Thus the development artifacts including product manuals, training and debugging documents will be handed over. 1.1 Transition Objectives To handover fully operational TGFDB system into LADOT production environment To confirm successful deployment of the system on single production server in LADOT lab infrastructure To provide intermediate support for the transitioned capabilities at the end of every iteration. Note that there wouldn't be any post transition support from development team after the completion of project. To catch production defects early in project life cycle and get feedback from user community (LADOT program managers, project managers, accountants, maintainers etc) as soon as the feature is delivered. To ensure that LADOT maintainers are well positioned to provide technical support for deployed system 1.2 Transition Process Strategy As mentioned in section 1.1, the project follows both pilot transitioning and fully operational transitioning. Pilot iteration target to transition the features developed specific to the iteration and fully operational transition targets to complete the entire product and project transition. The development team and LADOT maintenance team holds primary responsibility of transition activity. Transition Plan (TP) Document 6 Version Date: 11/17/2011

7 2. Preparing for Transition 2.1 Hardware Preparation Following summarizes the minimum hardware requirement for hosting SharePoint2010: x64 processor 8GB memory 80 GB hard disk As LADOT already have SharePoint2010 production server, there is no new hardware to be procured for hosting the delivered system. If there are any hardware configuration changes required specific to the project, it will be included in appropriate document and briefed during the training. If there are any hardware configuration changes/preparation required, then LADOT maintainers may be required to invest time in preparing the existing development server for deployment activity. It will mostly be one time activity. Note that this time may be extended if production environment demands say SharePoint server farms. High level approval is required from LADOT manager to go ahead with proposed hardware preparation 2.2 Software Preparation Following summarizes software requirements for SharePoint2010: Microsoft SharePoint 2010 Enterprise Edition MS SQL 2008 Microsoft Visual Studio 2010 All these setup on Windows 2008 R2 x64 system To support Level of Service (LOS-1), the server must be capable of supporting 100 users. Clients are yet to share the information of the licensing model of production server. The developed feature will be transitioned to LADOT using SharePoint2010 export/import feature LADOT may need to have a configuration management system to keep the source code for further enhancement. The details of the tool will be documented after discussion with LADOT maintenance team. If there are any software level configuration (e.g. OS & DB tuning, DB data population, SharePoint2010 customization, configuration management system changes, etc.) required specific to the project, it will be included in appropriate document and briefed during the training. Transition Plan (TP) Document 7 Version Date: 11/17/2011

8 TGFDB is a standalone system. Hence there is no integration or interoperability preparation anticipated at this time. High level approval is required from LADOT manager to go ahead with proposed software preparation 2.3 Site Preparation TBD Transition Plan (TP) Document 8 Version Date: 11/17/2011

9 3. Stakeholder Roles, Responsibilities and Schedule Table 1: Transition Schedule Date Role Responsibility Location 03/08/12 Builder Execute SharePoint2010 migration procedure Client site for first pilot transfer 03/09/12 Maintainer Acceptance test for first pilot transfer Client site 04/13/12 Builder Execute SharePoint2010 migration procedure Client site for second pilot transfer 04/14/12 Maintainer Acceptance test for second pilot transfer Client site 04/13/12 Builder Execute SharePoint2010 migration procedure Client site for full transfer 05/04/12 Maintainer Acceptance test for full transfer Client site 05/04/12 Maintainer Production hardware preparation activities for Client site full operational transition 05/04/12 Maintainer Production software preparation activities for Client site fill operational transition 05/04/12 Client Manager and Maintainer Training plan tracking and closure Client site Transition Plan (TP) Document 9 Version Date: 11/17/2011