Transition Plan (TP)

Transcription

1 Transition Plan (TP) United Directed Marketing Team 9 Fall Semester Chun-Ling Chen Project manager/ Prototyper Chun-Pei Su Lifecycle Planner Shao-yen Cheng System Architect Yuan-Chang Chang Feasibility Analyst Stewart Allen IIV&V/ Requirements Engineer Yen-Kuo Kao Operational Concept Engineer Spring Semester Chun-Pei Su Trainer / Document Maintainer Shao-yen Cheng Chief Developer Stewart Allen Tester / IIV&V / Quality Focal Point Kelvin Zhu Project Manager / Developer 4/20/2013 TP_IOC2_S13b_T09_V2.3.doc Version Date: 4/20/2013

2 Version History Date Author Version Changes made Rationale 11/27/12 Yuan Chang 1.0 Chang Section 1, 3 Initial TP for the draft DC package 1/27/13 Kelvin Zhu 1.1 Fixed spelling and grammar typos throughout documents Correcting typos Updating with new team roster Updated team member list with members from Spring semester 2/19/2013 Stewart Allen 2.0 Updated from comments from ARB Updated document to include section Ready for RDCP so completing document 2 3/31/2013 Stewart Allen 2.1 Ready for the IOC1 Delivery of the IOC1 4/12/13 Chun-Pei Su 2.2 Updated section 3 Satisfied the Draft TPR exit criteria 4/20/13 Chun-Pei Su 2.3 Updated section 2 Satisfied the TS set and made changes after TRR ARB ii

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... 8 iii

4 Table of Tables No table of figures entries found. TP_IOC2_S13b_T09_V2.3.doc iv Version Date: 4/20/13

5 Table of Figures No table of figures entries found. TP_IOC2_S13b_T09_V2.3.doc v Version Date: 4/20/13

6 1. Transition Strategy Because our client s original business website is currently working on her server, we can t test our product on the host. Therefore, we will build this website on a test server and test it with as much detail as possible. After testing it thoroughly and getting permission from our client, we will export our client s original website and install our new website on the host instead. The time of this final transition process should be as short as possible, reducing the cost to our client for cutting off her business website service. 1.1 Transition Objectives The objectives of the transition are: Successful Deployment of the website on the UDM web server which includes Successful Uploading of migrated data. Installation of website on the server. Short service interrupting time Deliver complete document of user manual No additional technique support required after delivering. 1.2 Transition Process Strategy We will install our server and our website on a testing webhost in advance. We will also use this webhost to test and ask our client for advisement. After finishing the alpha test, we will export the client s original website from her webhost and immigrate the whole project into it. At the end, we will do a beta test to make sure everything works well. The following steps will be taken during transition: Alpha-test our product on a test webhost Export client s original website Import migrated data on the My SQL server. Install the website on the server. Beta test of all the functionalities on the client site Train our client to be familiar with the whole system Deliver all the user manual documents to the client 6

7 2. Preparing for Transition 2.2 Hardware Preparation The proposed system will utilize an existing web server that is currently leased by UDM. As a result, the servers will need transitioned to use the new site, as opposed to the legacy UDM website. No other hardware preparation needs to be made. 2.3 Software Preparation The website will be installed on the web server as is. The software should be prepared as followed: PHP FUEL MySQL Client Internet Browser: Google Chrome15, Internet Explorer 9, Firefox Site Preparation No site preparation needs to be made. The team is facilitating the communication with the web hosting company. The team almost transited the website to the clients server. The next step is testing the capabilities on the server 7

8 3. Stakeholder Roles, Responsibilities and Schedule Date Role Responsibility Location 2/15/13 Tester Test the website in programmer s developing Developer s environment. developing 3/10/13 Client, IIVer Provide feedback and concerns about the functionalities environment Developer s developing environment 3/24/13 developer Refine and modify the system based on the feedback and concerns Developer s developing environment 4/6/13 developer Deploy the system on test webhost Testing webhost 4/13/13 Tester, IIV&V Client Verify the system Testing webhost 4/17/13 developer Deploy the system on actual web hosting Client s site account 4/21/13 Trainer Provide training to the client Client s site 4/28/13 Development Team Provide support during transition phase Coder s site & Client s site 5/10/13 Development Team, Client Deliver the system source-code package and all related documentation to the client Client s site 8