Transition Plan (TP)

Transcription

1 Transition Plan (TP) LEAMOS Team # 07 Name Primary Role Secondary Role Monty Shah Project Manager Life Cycle Planner Pragya Singh System Architect Prototyper Shantanu Sirsamkar Requirements Engineer Feasibility Analyst Suchita Doshi Prototyper Operational Concept Engineer Swapnil Savdekar Life Cycle Planner System Architect David Wiggins IIV&V Off-campus Shaper

2 Version History Date Author Version Changes made Rationale 11/18/11 Swapnil Savdekar, 1.0 All sections except 2.3 are completed Initial TP for the draft DC package Shantanu Sirsamkar 12/02/11 Swapnil Savdekar 1.1 Changes in transition schedule Updated for DCR ARB

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

4 Table of Tables Table 1: Transition Schedule... 8

5 Table of Figures No table of figures entries found.

6 1. Transition Strategy The Leamos system would be installed on Leamos server at the Leamos office. As we don t have direct access to the Leamos server, the Clarity staff which supports IT activities for Leamos will provide us a sandbox with moodle server. We will start the transition in early April The Transition involves porting the migrated database on My SQL server of Leamos. The Clarity Staff which supports the Leamos site would import all the migrated data into the Leamos MySQL server via csv files. After that Leamos website needs to be installed on the moodle server. Clarity staff will port the website from the sandbox to the actual Leamos server. The website would be fully tested before putting it online and then there would be a beta testing phase for the website. 1.1 Transition Objectives The objectives of the development team for the transition are: Successful Deployment of the system on the Leamos site which includes o Successful Uploading of migrated data. o Installation of website on the server. o Testing of website on the local machine o Beta testing of website after putting it online. Deliver complete Maintenance package to the client which includes o Documentation of the User manual o Video tutorial for uploading new HTML5 videos No additional developer support after complete transition. 1.2 Transition Process Strategy The clarity staff will provide us a sandbox with moodle server where we will be doing initial testing of the website. Also they will provide us with the CourseMerchant which will be integrated with Leamos website and tested on moodle server on sandbox. The following steps would be taken during transition: Importing migrated data on the My SQL server. Installing the website on the server. Alpha testing of all the functionalities at the client site Beta testing After this, the system will be handed over to Leamos and Clarity staff.

7 2. Preparing for Transition 2.1 Hardware Preparation Centro Latino organization already owns the required hardware needed to run the system. Hence, no additional purchase for hardware is required. Although the client has agreed to pay for small costs if the need arises to purchase the additional hardware. If the case arises where the client is required to purchase new hardware, then the dimension of staff time and approval from organization comes into picture. It need not be contemplated upon up and until such situation arises. 2.2 Software Preparation Deliverables: Developers will have to provide the client side staff with all the system related entities such as data, web pages, DLL and so on. The thorough list is yet to be finalized. Licensed Products: The Centro Latino organization is already in possession of licensed software products that are required to run their system. This includes the likes of Course Merchant. Necessary Preparation: For the complete functioning of Leamos system, data migration is the pre-requisite as mentioned in the above section. Upon its completion and installation at the client side, the system will be declared functional once the Leamos website is in place on the moodle platform. Necessary software requirements, if any; apart from those mentioned above are to be communicated by the client to the development team. 2.3 Site Preparation TBD

8 3. Stakeholder Roles, Responsibilities and Schedule Table 1: Transition Schedule Date Role Responsibility Location 4/6/12 Builder Prepare Final Deliverables for deployment Programmer s site 4/9/12 Maintainer Port migrated data on Leamos MySQL Client s site server 4/11/12 Builder, Configure site on Leamos server Client s site Maintainer 4/16/12 Builder, Deploy all the deliverables on Leamos server Client s site Maintainer 4/16/12 Tester Test website after deployment Client s site 4/17/12 Tester Provide test results to Programmer and client Client s site 4/18/12 to 4/23/12 Programmer Make appropriate changes based on testing feedback and release the code again Programmer s site, Client s site 4/24/12 Trainer Prepare user manual Trainer s site 4/25/12 Trainer Prepare video tutorial Client s site 5/2/12 Builder, Trainer Deliver source code along with all the technical documentation to the client/maintainer Client s site