System and Software Support Plan (SSSP)

Size: px

Start display at page:

Download "System and Software Support Plan (SSSP)"

Dorthy Harrell
5 years ago
Views:

1 System and Software Support Plan (SSSP) PicShare Team 1 Logan Chang Project Manager, Mobile Developer Jiashun Zhou Mobile Developer Yew Hua Chua Backend Developer Haihao Lu Backend Developer Yunwei Yuan Mobile Developer Yao Wang Mobile Developer Weili Zhang Backend Developer Joseph Mouawad Mobile Developer Nicholas Funk Backend Developer, Tester 27 April 2016

2 Version History Date Author Version Changes made Rationale 04/06/16 YY 1.0 Added expected information in each section To comply with Instructional ICM-Sw standard 04/27/16 NGF 1.1 Minor edits Clarity SP_ASBUILT_S16b_T01_V1.1.docx ii Version Date: 04/27/16

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...5 SP_ASBUILT_S16b_T01_V1.1.docx iii Version Date: 04/27/16

4 Table of Tables Table 1: Description of Software required in Support Plan... 3 Table 2: Stakeholders and their supporting responsibilities... 5 SP_ASBUILT_S16b_T01_V1.1.docx iv Version Date: 07/30/12

5 1. Support Objectives and Assumptions 1.1 Support Objectives This support plan is to help developers and people who will continue to implement the PicShare project after this semester understand the project and platforms, framework and tools needed to develop the project. 1.2 Support The assumptions the team made in the creation of this document are as follows: All the documentations are provided to the client at the end of project The maintainers provided by the client are familiar with following programming technologies: Xcode 7.3, Express Framework, Parse, mlab, Programming Language (swift, CSS, html, JavaScript) SP_ASBUILT_S16b_T01_V1.1.docx 1 Version Date: 04/27/16

6 2. Support Strategy 2.1 Support Lifetime We provide support until April 29, 2016, the end of this semester, when the current asbuilt package is delivered. Our backend is deployed on mlab and the guide to mlab can be found here. We cannot provide accurate estimates for how long each of the required services will remain active. In some cases (such as the Parse backend service), our team has taken steps to remove dependency on vendor support by deploying a self-hosted open source solution. In those cases where required services have no advertised end-of-life, we are leaving any assessment of support lifetime up to the client. 2.2 Release Strategy The development team will release the final version which meets the client requirements at the end of this semester. The final version will incorporate client s feedback throughout the project especially during CCD. For further development, we recommend the client to perform the necessary testing before releasing any newer versions. For future pre-production releases, we recommend a similar strategy of configuration management using git branches, fetching the desired feature branch to the target server or ios development environment as appropriate. This guide provides no guidance as far as actual deployment to the ios App Store, nor does it provide guidance for maintenance in a production environment with actual users. 2.3 Release Requirement Determination All the new content should be released only if the projected gain exceeds the efforts to implement new features, creating a competitive edge over competitors. The process is as follows: the key stakeholders determine whether new features would increase the product s appeal to users and then consider the efforts to execute the improvement. 2.4 Release Process The final source code for both mobile application and backend server will be delivered to client via github. If any additional development is required, changes can be made in github. All the test cases in TPC document should be performed before releasing any new version. SP_ASBUILT_S16b_T01_V1.1.docx 2 Version Date: 04/27/16

7 3. Support Environment The most likely source of support issues comes from the Apple iphone and Apple ios ecosystem. This software has been developed to support ios 8.3 or later; at the time of development, ios 9.3 was the latest release. The ios may upgrade to an incompatible version. As our team cannot foresee changes to ios, we are unable to provide support for future ios releases or iphone hardware iterations at this time. The adaptation of the existing PicShare app will be left to the client and his or her maintenance team. 3.1 Hardware Macintosh and iphone will be required to view, modify and test the code. Specifically, the PicShare mobile app is developed for iphone devices supporting ios 8.3 or newer only. Tablet devices such as ipad are not supported. 3.2 Software Table 1: Xcode Software Requirement: Rationale: User/Operator Manual: Availability Information: Note: Xcode Integrated development environment, compiler Apple support None Table 2: Parse Software Requirement: Rationale: User/Operator Manual: Availability Information: Note: Parse open source server code Parse is an open source backend and provides APIs for mobile application Open source, well supported None Table 3: mlab Software Requirement: Rationale: User/Operator Manual: Availability Information: Note: mlab mlab is a fully managed cloud database service Open source, well supported None SP_ASBUILT_S16b_T01_V1.1.docx 3 Version Date: 04/27/16

8 Table 4: Express Software Requirement: Rationale: User/Operator Manual: Availability Information: Note: Express framework Express framework is a minimal and flexible Node.js web application Easy to use, well supported Install Node.js 3.3 Facilities As all hosting is virtualized, no facilities are required. SP_ASBUILT_S16b_T01_V1.1.docx 4 Version Date: 04/27/16

9 4. Support Responsibilities Table 5: Stakeholders and their supporting responsibilities Stakeholder Supporting roles # Supporting Skills Maintainer Software maintenance, database 2 Swift, JavaScript administration, system administration Client Business support 1 Business skills and knowledge SP_ASBUILT_S16b_T01_V1.1.docx 5 Version Date: 04/27/16

System and Software Support Plan (SSSP)

System and Software Support Plan (SSSP) Fōkcus Team 08 Name Role Steven Holland Requirement Engineer, Prototyper Arik Oganesian Operation Concept Engineer, Software Architect Marco Alvarez Feasibility