Transition Plan (TP)

System and Software Support Plan (SP) Template Version 1.0 Version no x.xx

System and Software Support Plan

(SSSP)

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/13/2013

Version History

Date / Author / Version / Changes made / Rationale /
4/13/13 / CS / 1.0 / · Added information to each sections / · Satisfied Draft TPR package exit criteria

System and Software Support Plan (SSSP) I

Version History II

Table of Contents .III

Table of Tables IV

1. Support Objectives and Assumptions 1

1.1 Support Objectives 1

1.2 Support 1

2. Support Strategy 1

2.1 Support Lifetime 1

2.2 Release Strategy 2

2.3 Release Requirement Determination 2

2.4 Release Process 2

3. Support Environment 3

3.1 Hardware 3

3.2 Software 3

3.3 Facilities 3

4. Support Responsibilities 4

SP_IOC2_S13b_T09_V1.0.doc Version Date: 4/13/13

Transition Plan (TP) Table of Contents

Table of Tables

Table 1: Description of Software required in Support Plan 3

Table 2: Stakeholders and their supporting responsibilities 4

Table of Figures

No table of figures entries found.

SP_IOC2_S13b_T09_V1.0.doc Version Date: 4/13/13

System and Software Support Plan (SP) Version 1.0

1. Support Objectives and Assumptions

1.1 Support Objectives

The purpose of System and Software Support Plan is to provide administrator and user a clearly guild to maintain and operate the system. There are some important objectives for support plan are:

l Make sure the maintainer/ client can handle the system easily after transition

l Ensure the client notices the date of development team will support the system ends by May 10

l Facilitate the seamless operations once the system has been delivered to the client

l Help to merge the Web system and environment with UDM website

1.2 Support

In order to make sure the support plan can be workable, the following assumptions should be identified:

· The administrator understands all the work flow of the system and know how to maintain.

· The development team will deliver the system related documentations and files to the client

· After transiting the system, the development team and client will test all the capabilities to make sure there is no problems exist in the system.

2. Support Strategy

2.1 Support Lifetime

The development team is responsible to provide seamless support and operation for the United Direct Marketing System until the end of the semester, May 10th, 2013. The team will provide the client a technical knowledge to understand how to use the system and deliver a detail user manual.

2.2 Release Strategy

Our overall release strategy is based on our client’s feedback and requirements. All the capabilities are done before transition. Currently, the team fixes the bugs and related issues after receiving the feedback from client. The team relies on the client’s requirements and suggestion to make improvement of the system. Therefore, we can realize the actual situation and make a properly adjustment while client used the system.

2.3 Release Requirement Determination

The criteria for determining if a new release is required will be:

· Testing results collected from previous version

· Feedback from the client and customer

· Development team’s schedule

· A Necessary enhancement or improvement for the system

2.4 Release Process

Following is the process that should be followed for each new release:

· If there are new requirements or needs for a new release, developer teams will estimate its effort and time and then schedule the time to develop.

· Once the development has been finished, the team will have test plan and test the system with new test cases.

· After testing activity, the team will ask client to test the new version of system to make sure the new version can be transited.

· Back up the codes and configuration and then install in the client’s server.

· Client will test it again and the team will assist client during the testing activity.

A trainer monitors the new release system and if there is any problems, report it to the development teams.

3. Support Environment

The support environmental includes the hardware and software utilities required for the system, they are:

3.1 Hardware

The following hardware specifications should be met:

· 64-bit processor

· 8 GB RAM

· 80 GB for system drive

The proposed system will utilize an existing web server that is currently leased by UDM. Therefore, there is no other hardware preparation needs to be made.

3.2 Software

Table 1: Description of Software required in Support Plan

Software Requirement: / PHP 5.3.2
Rationale: / Server side scripting language for web application
User/Operator Manual: / http://us2.php.net/manual/en/install.php
Availability Information: / It is available to download from the following web site: http://php.net/downloads.php
Note: / Web hosting needs to support PHP
Software Requirement: / FUEL
Rationale: / Provides powerful CMS interface ready to use
User/Operator Manual: / http://www.getfuelcms.com/user_guide
Availability Information: / It is available to download from the following web site: http://www.getfuelcms.com/
Note: / Web hosting needs to support FUEL
Software Requirement: / MySQL Client 5.1.41
Rationale: / Database management software for web application
User/Operator Manual: / http://dev.mysql.com/doc/
Availability Information: / It is available to download from the following web site: http://dev.mysql.com/downloads/
Note: / Web hosting needs to support MySQL
Software Requirement: / Internet Browser: Google Chrome15, Internet Explorer 9, Firefox 8
Rationale: / Browse the UDM system web site to the end users (customers, administrator)
User/Operator Manual: / The manual is provided by each web site
Availability Information: / It is available to download from each web site
Note: / Those are the internet browser which developers tested the web site with

3.3 Facilities

The main server for web application is located at the web hosting, so it would be no specific facilities to maintain. Stable Internet connection is necessary to get customers request.

4. Support Responsibilities

Table 2: Stakeholders and their supporting responsibilities

Stakeholder / Supporting roles / # / Supporting Skills
Samta (UDM president) / · System Administration
· Software Maintenance
· Network troubleshooting and maintenance
· Users training and help desk / 1 / · Maintain the case study and show case files
· The basic web hosting and HTML knowledge
Development team / · System upgrades and releases
· Users training
· Testing plan for the new release / 4 / · PHP programming skill and database query
· Troubleshooting with the system

SP_IOC2_S13b_T09_V1.0.doc Version Date: 4/13/13