System and Software Support Plan (SSSP)

Transcription

1 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 Kawinfruangfukul Tester Developer Eunyoung Hwang Architect Developer Louis Demaria IIV&V Developer Mark Villanueva QFP Developer Sangik Park Developer Developer 04/12/12

2 Version History Date Author Version Changes made Rationale 04/09/12 EH 1.0 All section covered For draft TRR Package 04/12/12 EH 1.1 Section 1, 2 has been changed Before TRR SP_IOC2_S12b_T12_V1.1.doc ii Version Date: 04/12/12

3 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 Support Objectives Support Support Strategy Support Lifetime Release Strategy Release Requirement Determination Release Process Support Environment Hardware Software Facilities Support Responsibilities... 6 SP_IOC2_S12b_T12_V1.1.doc iii Version Date: 04/12/12

4 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.1.doc iv Version Date: 04/12/12

5 1. Support Objectives and Assumptions 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: To facilitate the seamless operations once the system has been delivered to the client. To ensure that system and software maintainers can easily handle emergent situation after transition. To identify the support environment on hardware, software, and facilities. To help the smooth integration for usage with legacy system, Columbia and SIS. 1.2 Support In order for the system and software support plan to be workable, the following assumptions need to be valid: If system requires modification during the support period, the client will notify the project team with the stable requirements and schedules. Continuity of funding for Web Hosting and staffing for maintaining and operation. The client is responsible for upgrades, operation and maintenance of the system after it is deployed. The system is highly dependent on legacy system for the students and teachers basic information, final schedules and LAUSD policies and norms for scheduling. o The formats of CSV files created from legacy system needs to be consistent as they were provided as samples during the development phase. o The FET (scheduling application) needs to be managed by the software maintainer or its end users (administrators or schedulers). SP_IOC2_S12b_T12_V1.1.doc 1 Version Date: 04/12/12

6 2. Support Strategy 2.1 Support Lifetime The CSCI577 development team is responsible to provide seamless support for the LEMA Integrated Scheduling System until the end of the semester, May 4 th, A user and technical training will be provided to the clients and maintainers with detailed manual. The support for COTS to provide guidelines and documents is available via their web sites as a reference type. 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 Operational Phase after deployment while a scheduler simulates the first scheduling period. Those users small requirements need to be covered during support lifetime. Other than that, it would be handled by the future evolutionary project team. 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. 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: 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. SP_IOC2_S12b_T12_V1.1.doc 2 Version Date: 04/12/12

7 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.1.doc 3 Version Date: 04/12/12

8 3. Support Environment 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 3.2 Software Table 1: Description of Software required in Support Plan Software Requirement: Symfony 2 PHP MVC framework for web application User/Operator Manual: on-ubuntu-server / Availability Information: It is free of charge framework and available on the following web site: Web hosting needs to support Symfony 2. Software Requirement: PHP Server side scripting language for web application User/Operator Manual: Availability Information: It is available to download from the following web site: Web hosting needs to support PHP Software Requirement: MySQL Client Database management software for web application User/Operator Manual: Availability Information: It is available to download from the following web site: Web hosting needs to support MySQL Software Requirement: Apache 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: Web hosting needs to support Apache Software Requirement: Linux or Windows Server SP_IOC2_S12b_T12_V1.1.doc 4 Version Date: 04/12/12

9 User/Operator Manual: Availability Information: Operating system for the LEMA scheduling system web site Web hosting provides Linux or Windows server As long as web hosting service supports the information for server Software Requirement: FET Scheduling application installing on scheduler s PC User/Operator Manual: Refer the following web site: and the user manual Availability Information: It is available to download from the following web site: Software Requirement: User/Operator Manual: Availability Information: Internet Browser: Google Chrome17, Internet Explorer 8, 9, Firefox 11, or Opera11 Browse the LEMA scheduling system web site to the end users (schedulers, counselors, teachers, students) Manual provided by each web site It is available to download from the each web site Those are the internet browser which developers tested the web site with 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.1.doc 5 Version Date: 04/12/12

10 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 Table 2: Stakeholders and their supporting responsibilities Stakeholder Supporting roles # Supporting Skills A scheduler at LEMA (Roberta Responsible to maintain the FET application on her/his PC 1 Maintaining CSV files Mailman) Maintain CSV files created from the LEMA scheduling system web site and CSV files from the legacy system Keep updating the budget on the web hosting A maintainer at LEMA (Beverly Goldin) Responsible for maintaining the web hosting Support for a new release Monitor the web server 1 Knowledge on the web hosting Concept on web application and database management system USC Development Teams at CSCI 577b Responsible for version control, data backup Support for a new release as long as it meets the criteria Test for the new release 5 PHP programming skills on Symfony framework MySQL query usage MVC architecture pattern concept Future developers for evolutionary project Back up database, source code, and configuration information PHP programming skills on Symfony framework Familiarity with MySQL SP_IOC2_S12b_T12_V1.1.doc 6 Version Date: 04/12/12