Transition Plan (TP)

Transcription

1 Transition Plan (TP) FlowerSeeker Team 05 Name Eder Figueroa Sophia Wu Doris Lam Hiram Garcia Roles Primary Role: Project Manager/ Implementer. Secondary Role: Tester. Primary Role: Tester/ Trainer Secondary Role: Implementer Primary Role: IIV&Ver/ Quality Focal Point/ Implementer. Secondary Role: Tester. Primary Role: IIV&Ver/ Quality Focal Point/ Implementer. Secondary Role: Tester. 04/15/13

2 Version History Date Author Version Changes made Rationale 12/10/12 DL 1.0 Filled in Section 1 and 3 Initial version for DCP submission 02/11/13 SW, DL 1.1 Revised cover, filled in Section 2 Reform development team, RDCP updates 04/01/13 DL 1.2 Filled in all sections Filled in section /15/13 DL 1.3 Updated Software Preparation TRR update 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 Table 1: Transition Schedule... 8

5 Table of Figures No table of figures entries found.

6 1. Transition Strategy The client expects the final deliverable to be a beta site with the agreed upon functionalities in Winbook. She had indicated that she will find support from commercial firms after product delivery to maintain and administer the site in the future. Therefore, it is imperative that we deliver all source code and system design documentation so subsequent contractors can pick up maintenance of the site after product delivery. 1.1 Transition Objectives Transfer credentials and any related material about the hosting service (Amazon web services) to the client Transfer credentials to the private code repository hosted on Bitbucket to the client Package all source code and web archive files to give to the client Package up all documentation, UML diagrams, system specification, and user manual for the system to the client Successful training of client on how to operate the site as admin and to administer the site on AWS Successful deployment of an operational beta site to the hosting service and all required capabilities tested Upon transition, the members of the class team will support the client until semester ends, at which point support will end and the client will have to seek maintenance and further features from outside contractors 1.2 Transition Process Strategy Since the client does not have any existing system and we are planning to deploy the system to cloud services, the transition will include educating and training the client in administering the cloud service account until she contracts outside firms to provide maintenance of the site. After the team deploys the system to production environment, the client will have until end of semester to test out and request any trivial or minor changes to the system. At semester end cutover will be instantaneous and client will not receive any more support from the team members. 6

7 2. Preparing for Transition 2.1 Hardware Preparation There is no hardware preparation needed except an Amazon AWS account that provides a year of free usage applicable to the needs of the system. 2.2 Software Preparation The software will be packaged as a war file that can be deployed on AWS Elastic Beanstalk. Amazon provides monitoring tools and an Eclipse plugin that facilitates this process. Configuration files and instructions will be provided where applicable. The client will need to create a PayPal Business account so we can use a PayPal API key to access real PayPal services and submit the application for approval. The client will also need to provide us with any legal wording or license terms for users signing up to the site, and how transaction fees and taxes are to be distributed. In the event that these information are not ready, the implementation of correct payment process or the PayPal submission process can t be completed in time, the site can still be deployed with limited functionality, without checkout or subscription functions. The client will also need to register for an Amazon AWS account so we can deploy the application on ElasticBeanstalk. An EC2 instance running Amazon Linux AMI with Tomcat 7, and an RDS instance for MySQL 5.5 will be needed. The application config will need to be updated with the appropriate database connection parameters. Since the application uses SSL for some parts of the site, a signed certificate will need to be obtained from a signing authority like Verisign. If a signed certificate cannot be obtained in time or the information needed is missing, we can assign a self signed certificate to ElasticBeanstalk s EC2 instance load balancers in order to demonstrate a working version of the product running in the cloud. 2.3 Site Preparation There is no site preparation needed. Everything deliverable to the client will be an electronic artifact or hosted on cloud services source code and any application readme or instruction manual and documents will be hosted in a Bitbucket private repository and web application will be hosted on Amazon AWS (Elastic Beanstalk). 7

8 3. Stakeholder Roles, Responsibilities and Schedule Table 1: Transition Schedule Date Role Responsibility Location 4/10/13 4/17/13 Builder, Tester, Project Perform final requirements checks and testing, resolve any issues USC Manager 4/17/13 Team, Client training and feedback 4/19/13 Client 4/19/13 Builder Install and setup operational site USC 4/19/13 Team, Transition Readiness Review Client, TAs 4/19/13 4/29/13 Team, Client Continue client training and feedback, client test out operational site and raise any issues to be resolved Web conference/usc Web conference/usc Web conference/usc 5/7/13 Client Client evaluation Client s location End of Team, Finish delivery of all products and Web semester Client documentation conference/usc 8