TP_TRR_F11a_T06_V1.0 Version Date: 11/19/11 Transition Plan (TP) Mission Science Information and Data Management System Team #6 Hardik Shah – Feasibility Analyst Celia Kung – Project Manager Yujie Chen – Prototyper Zhenlu Sun – Requirements Engineer Brian Anderson – Operational Concept Engineer Kathleen Barrera – IIV & V Wei Tan – System Architect 11/19/11Transition Plan (TP) Version 1.0 Version no x.xx TP_TRR_F11a_T06_V1.0 Version Date: 11/19/11 ii Version History Date Author Version Changes made Rationale 11/19/11 HS 1.0 - Update default content in all sections to pertain to project specific data - Initial draft for the TRR packageTransition Plan (TP) Version 1.0 Version no x.xx TP_TRR_F11a_T06_V1.0 Version Date: 11/19/11 iii 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............................................................................................................................................. 6 1.1 Transition Objectives ................................................................................................................................. 6 1.2 Transition Process Strategy ....................................................................................................................... 6 2. Preparing for Transition ..................................................................................................................................... 7 2.1 Hardware Preparation ................................................................................................................................ 7 2.2 Software Preparation ................................................................................................................................. 7 2.3 Site Preparation .......................................................................................................................................... 7 3. Stakeholder Roles, Responsibilities and Schedule ............................................................................................ 8Transition Plan (TP) Version 1.0 Version no x.xx TP_TRR_F11a_T06_V1.0.doc iv Version Date: 11/19/11 Table of Tables Table 1: Transition Schedule ......................................................................................................................................... 8Transition Plan (TP) Version 1.0 Version no x.xx TP_TRR_F11a_T06_V1.0.doc v Version Date: 11/19/11 Table of Figures No table of figures entries found.Transition Plan (TP) Version 1.0 TP_TRR_F11a_T06_V1.0 Version Date: 11/19/11 6 1. Transition Strategy 1.1 Transition Objectives - Extent of capability transitioned: limited pilot operation for 1 day and then full operation. - Number and nature of transition sites: Homogeneous (only 1 transition site) - Degree of post-transition developer support: none - Degree of validation of operational satisfaction of stakeholder objectives: We will be running the test cases and also during the pilot operation we will be asking for feedback. - Nature of product transition: It’s a new system altogether with new design - Relation to support objectives: We will have manual for the evolution of the project 1.2 Transition Process Strategy - Phasing of cutover: instantaneous - Role of alpha-testing, beta-testing, independent operational testing and evaluation: The alpha testing will enable us to test a feature independently after which we can merge and test the whole system.Transition Plan (TP) Version 1.0 TP_TRR_F11a_T06_V1.0 Version Date: 11/19/11 7 2. Preparing for Transition 2.1 Hardware Preparation There is no hardware preparation required as the client has the computer where he wants the new system transition to take place. 2.2 Software Preparation The client already has the commercial copy of the MS Access that is required to run the database version which we developed. 2.3 Site Preparation The client has everything prepared already.Transition Plan (TP) Version 1.0 TP_TRR_F11a_T06_V1.0 Version Date: 11/19/11 8 3. Stakeholder Roles, Responsibilities and Schedule Table 1: Transition Schedule Date Role Responsibility Location 12/02/11 Coder Prepare installation CD containing the MS Access database Coder’s site 12/02/11 Client Copy the database on the computer and run it Client’s office 12/02/11 Implementation Team Provide video user manual to client on a CD Client’s
View Full Document
Unlocking...