System and Software Support Plan (SP) Version 1.0

System and Software Support Plan (SSSP)

E-Lockbox

Team 05

Name / Roles
Chen "Miles" Gui / Primary Role: Project Manager/ Implementer.
Secondary Role: Tester.
Huaiqi Wang / Primary Role: Tester
Secondary Role: Implementer
Weiyi Zhong / Primary Role: Implementer.
Secondary Role: Tester.
Woon Kim / Primary Role: IIV&Ver.
Secondary Role: Tester.
Azuka Okuleye / Primary Role: Implementer.
Secondary Role: Tester.
Cecilia Jou / Primary Role: IIV&Ver.
Secondary Role: Tester.

4/14/13

Version History

Date / Author / Version / Changes made / Rationale /
03/30/14 / Huaiqi Wang / 1.0 / ·  Initial version / ·  Initial support plan

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 3

3.1 Hardware 3

3.2 Software 3

3.3 Facilities 5

4. Support Responsibilities 6

SP_IOC2_S14b_T05_V1.0 6 Version Date: 03/30/14

Feasibility Rationale Description (FRD) Table of Contents

Table of Tables

Table 1: Netbeans IDE 3

Table 2: MySQL 3

Table 3: Apache 3

Table 4: SourceTree 4

Table 5: Wercker 4

Table 6: Laravel Framework 4

Table 7: JQuery 4

Table 8: Bootstrap 5

Table 9: Amazon S3 5

Table 10: Stakeholders and their supporting responsibilities 6

SP_IOC2_S14b_T05_V1.0 6 Version Date: 03/30/14

System and Software Support Plan (SP) Version 1.0

1.  Support Objectives and Assumptions

1.1  Support Objectives

The purpose of this support plan is to aid developers and support personnel in understanding the system and the tools and resources needed to provide continued development and maintenance after transition.

1.2  Support

The 577b team will not be providing support after the Spring 2014 semester ends. The client will need to secure a developer who understands and ideally have experience with the following:

·  PHP, Apache, MySQL

·  Laravel web framework – Laravel MVC

·  Web development – HTML, CSS, JavaScript, JQuery and Bootstrap libraries

·  Amazon S3

·  Netbeans/Eclipse IDE

2.  Support Strategy

2.1  Support Lifetime

The 577b team will not be providing support after the Spring 2014 semester ends.

Below are a list of sites with information and documentation that pertain to the libraries and services used by the system. They are all popular and well maintained and will exist for the foreseeable future.

·  Laravel framework (community support) –

http://laravel.com/,

http://laravel.com/docs/quick,

http://laravel.com/api/4.1/,

http://laravel.io/forum

·  JQuery - http://jquery.com/

·  Bootstrap - http://getbootstrap.com/

·  Amazon S3 - http://aws.amazon.com/s3/

2.2  Release Strategy

After initial deployment at the end of the semester, the team will not be responsible for new releases. It’s recommended that continuous or frequent releases be made after initial transition to fix bugs and increase functionality.

2.3  Release Requirement Determination

Release requirements are primarily determined by win-win negotiations and new information Living Advantage needs to document. Features that securely store vital documents and conveniently manage cases and users should be prioritized.

2.4  Release Process

A release is taken from the master branch. We have an automatic build system on Wercker that gets the code, runs unit tests and checks for build errors. On success a deploy script is called to push changes to the server.

3.  Support Environment

The anticipated long-term environment for operating the system is in the cloud. The system relies heavily on using open source libraries and web services, therefore future API changes or upgrades of these services would have impact on supporting the system.

3.1  Hardware

There is no specific hardware needed for maintaining the system except a computer with a modern OS and development environment.

3.2  Software

Table 1: Netbeans IDE

Software Requirement: / NetBeans IDE 7.4 for HTML5PHP
Rationale: / Integrated development environment, compiler
User/Operator Manual: / https://netbeans.org/
Availability Information: / Well supported, open source, worldwide community
of users and developers
Note:

Table 2: MySQL

Software Requirement: / MySQL 5.5.x
Rationale: / Relational Database for storing system data
User/Operator Manual: / http://www.mysql.com/
Availability Information: / Well supported, open source, Oracle
Note:

Table 3: Apache

Software Requirement: / Apache 2.2
Rationale: / Web app container for serving the application
User/Operator Manual: / http://httpd.apache.org/
Availability Information: / Well supported, open source
Note:

Table 4: SourceTree

Software Requirement: / SourceTree Version 1.8.1
Rationale: / Version control system
User/Operator Manual: / http://www.sourcetreeapp.com/
Availability Information: / Well supported, Full-powered DVCS, Perfect for newcomers, Powerful enough for experts, Git-flow and Hg-flow out of the box
Note: / Alternative: Git

Table 5: Wercker

Software Requirement: / Wercker
Rationale: / Test and deploy the web application.
User/Operator Manual: / http://wercker.com/
Availability Information: / Well supported, integrates with GitHub
Note:

Table 6: Laravel Framework

Software Requirement: / Laravel Framework 4.1
Rationale: / PHP web framework and dependency injection framework
User/Operator Manual: / http://laravel.com/docs/quick
Availability Information: / Well supported, open source, RESTful routing
Note:

Table 7: JQuery

Software Requirement: / JQuery 1.9.x
Rationale: / Javascript library for easier dom and ajax manipulation
User/Operator Manual: / http://jquery.com/
Availability Information: / Well supported, open source
Note: / Various jquery plugins can be used, currently also using jquery form plugin to transform html forms into ajax - http://malsup.com/jquery/form/

Table 8: Bootstrap

Software Requirement: / Bootstrap 2.2.2
Rationale: / Web frontend framework and ui components
User/Operator Manual: / http://getbootstrap.com/
Availability Information: / Well supported, open source, also themes available and can create own themes
http://bootswatch.com/
https://wrapbootstrap.com/
Note: / There are other frontend frameworks that can replace bootstrap if desirable – below are some bootstrap extensions and alternatives:
Jasny extensions - http://jasny.github.io/bootstrap/
Foundation - http://foundation.zurb.com/
Knockoutjs – not a replacement, but something to consider if the pages need to be more dynamic and ajaxy - http://knockoutjs.com/

Table 9: Amazon S3

Software Requirement: / AWS S3
Rationale: / Storage for the Internet to store vital documents
User/Operator Manual: / http://aws.amazon.com/s3/
Availability Information: / Well supported by Amazon
Note: / Secure: Built to provide infrastructure that allows the customer to maintain full control over who has access to their data. Customers must also be able to easily secure their data in transit and at rest.
Reliable: Store data with up to 99.999999999% durability, with 99.99% availability. There can be no single points of failure. All failures must be tolerated or repaired by the system without any downtime.
3.3  Facilities

No special facilities are needed.

4.  Support Responsibilities

Table 10: Stakeholders and their supporting responsibilities

Stakeholder / Supporting roles / # / Supporting Skills
Pamela R. Clay / User and business support / 1 / Knowledge of domain and information needed to be documented
N/A / Software development and maintenance, database and deployment support, testing / 1-3 / See section 1.2
N/A / Trainer, administrator / 1 / Amazon S3, GitHub

SP_IOC2_S14b_T05_V1.0 6 Version Date: 03/30/14