System and Software Support Plan (SSSP)
LEMA Integrated Scheduling System
Team 12
Name Primary Role Secondary Role David Wiggins Project Manager Developer Aakash Shah Prototyper Developer Kushalpreet Kaur Developer Developer Thammanoon Tester Developer Kawinfruangfukul Eunyoung Hwang Architect Developer Louis Demaria IIV&V Developer Mark Villanueva QFP Developer Sangik Park Developer Developer System and Software Support Plan (SP) Version 1.0
04/09/12
SP_IOC2_S12b_T12_V1.0.doc ii Version Date: 04/09/12 System and Software Support Plan (SP) Version 1.0
Version History
Date Author Versio Changes made Rationale n 04/09/1 EH 1.0 Initial draft For draft TRR Package 2
SP_IOC2_S12b_T12_V1.0.doc iii Version Date: 04/09/12 System and Software Support Plan (SP) Version 1.0
Table of Contents
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...... 2
2.1 Support Lifetime...... 2
2.2 Release Strategy...... 2
2.3 Release Requirement Determination...... 2
2.4 Release Process...... 2
3. Support Environment...... 4
3.1 Hardware...... 4
3.2 Software...... 4
3.3 Facilities...... 5
4. Support Responsibilities...... 6
SP_IOC2_S12b_T12_V1.0.doc iv Version Date: 04/09/12 System and Software Support Plan (SP) Version 1.0
Table of Tables
Table 1: Description of Software required in Support Plan...... 4
Table 2: Stakeholders and their supporting responsibilities...... 6
SP_IOC2_S12b_T12_V1.0.doc v Version Date: 04/09/12 System and Software Support Plan (SP) Version 1.0
A.1. Support Objectives and Assumptions
A.1.1 Support Objectives
The purpose of System and Software Support Plan is to guide the system’s support stakeholders such as administrators, operators or maintainers in successfully operating and maintaining the system. The key driving objectives for support plan are: Help the smooth integration with legacy system, Columbia and SIS. Ensure that the system and software maintainers can easily handle emergent situation after transition. Facilitate the seamless operations once the system has been delivered to the client.
A.1.2 Support
In order for the system and software support plan to be workable, the following assumptions need to be valid: The formats of CSV files created from legacy system needs to be consistent as they were provided as samples during the development phase. The FET (scheduling application) needs to be managed by the software maintainer or its end users (administrators or schedulers). Continuity of funding for Web Hosting and staffing for maintaining and operation.
SP_IOC2_S12b_T12_V1.0.doc 1 Version Date: 04/09/12 System and Software Support Plan (SP) Version 1.0
A.2. Support Strategy
A.2.1 Support Lifetime
LEMA Integrated Scheduling System is operable approximately more than five years as long as the input CSV file formats created from legacy system stay the same as it is currently. The system is highly dependent on legacy system for the students’ and teachers’ final schedule and LAUSD policies and norms for scheduling. The scheduling application, FET: current version integrated with currently developed web page is 5.16.1. For the further information for the application, maintainers or administrators can refer the following web site: http://lalescu.ro/liviu/fet/
A.2.2 Release Strategy
LEMA Scheduling System development team can deliver a couple of additional small releases after the transition to the client’s site if needed regarding the site environment adjustment and minor requirements. The additional release can happen during the first scheduling period by a scheduler, which is before a coming semester and students’ registration. In this way, majority end users such as students and teachers would not affect by the changes and those users’ small requirements need to be covered during their acceptance test periods.
A.2.3 Release Requirement Determination
The primary drivers of new release on LEMA Scheduling System contents will be the following: Minor fix contents such as changing the wording for the labels Reasonable light enhancement on GUI such as changing images or the location of the button. Necessary enhancement for the level of service on must-have functionalities which has not been captured with testing data.
A.2.4 Release Process
The client will need to position a personnel who maintains or operates the system with familiarity of web hosting and a sense of system-wise background especially as a contact person on release. The process for each release would be the following:
SP_IOC2_S12b_T12_V1.0.doc 2 Version Date: 04/09/12 System and Software Support Plan (SP) Version 1.0
Since identify the needs for a new release, developer teams estimate its effort and time and then set the schedule for the release to the site. Once the development has been finished, a tester makes a test plan with possibly new test cases. After testing activity verifies the new version, a maintainer needs to be involved in transition to the site. Before resetting the new version, backup data, source codes and configuration information. A client announces to the affected end users and developer teams transit the new release and test the whole flow and test cases. A maintainer monitors the new release and if there is any problems, report it to the development teams.
SP_IOC2_S12b_T12_V1.0.doc 3 Version Date: 04/09/12 System and Software Support Plan (SP) Version 1.0
A.3. Support Environment
A.3.1 Hardware
We use the web hosting at Dream Host and it needs to meet the following hardware capacity: Processor: Intel Xeon 3.00 GHz RAM: 8 GB Hard Disk: 50 GB Network Connection: Ethernet
A.3.2 Software
Table 1: Description of Software required in Support Plan
Software Requirement: Symfony 2 Rationale: PHP MVC framework for web application User/Operator Manual: http://www.joelverhagen.com/blog/2011/05/how-to-configure-symfony-2-0- on-ubuntu-server-2011-4/ Availability Information: It is free of charge framework and available on the following web site: http://symfony.com/download Note: Web hosting needs to support Symfony 2.
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: 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: Apache 2.2.14 Rationale: Web server for running web application User/Operator Manual: Web hosting provides web server Availability Information: It is available to download from the following web site: http://httpd.apache.org/download.cgi Note: Web hosting needs to support Apache
Software Requirement: Linux or Windows Server
SP_IOC2_S12b_T12_V1.0.doc 4 Version Date: 04/09/12 System and Software Support Plan (SP) Version 1.0
Rationale: Operating system for the LEMA scheduling system web site User/Operator Manual: Web hosting provides Linux or Windows server Availability Information: As long as web hosting service supports the information for server Note:
Software Requirement: FET 5.16.1 Rationale: Scheduling application installing on scheduler’s PC User/Operator Manual: Refer the following web site: http://lalescu.ro/liviu/fet/doc/ and the user manual Availability Information: It is available to download from the following web site: http://lalescu.ro/liviu/fet/ Note:
Software Requirement: Internet Browser: Google Chrome17, Internet Explorer 8, 9, Firefox 11, or Opera11 Rationale: Browse the LEMA scheduling system web site to the end users (schedulers, counselors, teachers, students) User/Operator Manual: Manual provided by each web site Availability Information: It is available to download from the each web site Note: Those are the internet browser which developers tested the web site with
A.3.3 Facilities
Since the main server for web application is located at the web hosting, there would be no specific facilities to maintain. A scheduler’s PC has been installed the legacy system and FET application, so it might cause some workloads, however, the FET application is very light and a scheduler just need to maintain the files has been created by FET. Stable Internet connection is necessary to get student’s registration via online and to create a CSV file as a set of schedule which is imported to the FET.
SP_IOC2_S12b_T12_V1.0.doc 5 Version Date: 04/09/12 System and Software Support Plan (SP) Version 1.0
A.4. Support Responsibilities
The USC development teams at CSCI 577b class as stakeholders are dedicated the project support until the end of the Spring semester in 2012.
Table 2: Stakeholders and their supporting responsibilities
Stakeholder Supporting roles # Supporting Skills A scheduler at Responsible to maintain the FET 1 Maintaining files LEMA application on her/his PC Utilizing Excel Maintain CSV files created from the LEMA scheduling system web site and CSV files from the legacy system Report bugs to development teams
Keep updating the budget on the web hosting A maintainer at Responsible for maintaining the 2 Knowledge on the web LEMA web hosting hosting Support for a new release Concept on web Monitor the web server and application and database database management system USC Development Responsible for version control, 3 PHP programming skills Teams at CSCI 577b data backup on Symfony framework Support for a new release as long as MySQL query usage it meets the criteria MVC architecture Test for the new release pattern concept Future developers Back up database, source code, and 4 PHP programming skills for evolutionary configuration information on Symfony framework project Familiarity with MySQL
SP_IOC2_S12b_T12_V1.0.doc 6 Version Date: 04/09/12