Feasibility Evidence Description (FED)

Transcription

1 Feasibility Evidence Description (FED) E-Lockbox 05 Team Members Miles Gui Huaiqi Wang Weiyi Zhong Woon Kim Miles Gui Cecilia Jou Roles Project Manager Builder & Feasibility analyst Tester & Operational Concept Engineer Builder & Prototyper Builder & System Architect Builderr & Life Cycle Planner Tester & Quality Focal Point

2 04/28/2014 Version History Date Author Version Changes made Rationale 09/27/ Tailored from ICSM OCD Template to specify risks of the current system To specify current identified risks 10/14/ Feasibility studies carried out Identify ROI, Personnel costs, Level of Service feasibility. 10/20/ Personnel costs, NDI/NCS To fix some of the items from the FCB ARB feedback. 10/23/ Personnel costs and ROI analysis revised Completion of items based on ARB feedback. 11/23/ Business case analysis, COTS listing and risks revised, ROI. To complete all sections for the foundations phase. 12/1/ Explanation for SSL certificate cost, based on FCB feedback. As noted. 12/8/ Recalculation of risk costs As noted 2/17/ Reassessment of risks and mitigation As noted 4/4/ Formatting and additional explanations on COTS To clean up the document and ensure consistency

3 Table of Contents Feasibility Evidence Description (FED)... 1 Version History... 2 Table of Contents... 3 Table of Tables... 3 Table of Figures Introduction Status 5 2. Business Case Analysis Cost Analysis Benefit Analysis ROI Analysis Risk Assessment Level of Service Feasibility NDI/NCS Interoperability Analysis Introduction Evaluation Summary Table of Tables Table 1 Program Model... 6 Table 2 Personnel Costs... 7 Table 3 Hardware and Software Costs Development Phase... 8 Table 4 Hardware and Software Costs, Production... 8 Table 5 Benefits of elockbox System... 9 Table 6 ROI Analysis... 9 Table 7 Risk Assessment Table 8 LOS Feasibility Table 9 NDI Candidate Products Listing Table 10 NDI Evaluation... 14

4 Table of Figures Figure 1: ROI Analysis Graph... 10

5 1. Introduction The FED contains the feasibility study of the project, identifying possible risks, costs, benefits and NDI/NCS components in building the E-Lockbox system. Our client is LivingAdvantage, a public agency that helps foster youth manage their vital records and provide them with services and advice. 1.1 Status The status of the FED is currently at version 4.1 in the development phase, with clarification of risks and formatting fixes. The previous version is 4.0.

6 2. Business Case Analysis Table 1 Program Model Assumptions Foster youth want to have anytime/anywhere electronic access of their vital documents. Stakeholders Initiatives Value Propositions Beneficiaries Developer Living Advantage Foster youth Maintainer Develop system Partner with public agencies Training staff and foster youth to use this system Capture data daily and update quarterly Increase awareness of this system Provide their vital records Manage every valid case of foster youth Enable identification of foster youth Easier access to benefits and services Improved information management process Better tracking of foster youth Saving time, space and cost. Foster youth Living Advantage Costs Development costs including time spent meeting for requirements and feedback in the development phase Maintenance costs Benefits Provides an easy system tailored towards foster youth management Centralized, secure repository for foster youth vital documents Potential source of income through licensing to public agencies.

7 2.1 Cost Analysis Personnel Costs Table 2 Personnel Costs Activities Time Spent (Hours) Development Period (24 weeks) Valuation and Foundations Phases: Time Invested (CS577a, 12 weeks) Client: Meeting via , phone, and other channels [3 hrs/week * 9 weeks * 3 people] Client Representatives: Meeting via , phone, and other channels [1.5 hrs/week * 9 weeks * 1 person] Architecture Review Boards [2 hrs * 2 times * 3 people] Total Development and Operation Phases: Time Invested (CS577b, 12 weeks) Client: Meeting via , phone, and other channels [2 hrs/week * 12 weeks * 3 people] Maintainer: Meeting via , phone, and other channels [1 hrs/biweekly * 6 fortnights * 2 people] Architecture Review Boards and Core Capability Drive-through session [2 hrs * 3 times * 3 people] Deployment of system in operation phase and training - Installation & Deployment [2 hrs * 3 times * 2 people] - Training & Support [3 hrs * 3 times * 4 people] Total 150 Total One-Time Costs Maintenance (Yearly) 10 hrs * 2 maintainers * 12 months 240

8 2.1.2 Hardware and Software Costs Table 3 Hardware and Software Costs Development Phase Type Cost Rationale Hardware - VPS Hosting $5/month Digital Ocean Development server Software - Amazon S3 Free for up to documents at ~200kb each (4.7gb) Domain name $12/year Total $42 $24/hr 1.75 hrs Offsite secure file storage and/or backup Table 4 Hardware and Software Costs, Production Type Cost Rationale Software - SSL Certificate $149/year* Secure login and transport encryption Hardware VPS hosting $20/month Digital Ocean Isolated hosting for the system to ensure security Software - Amazon S3 Free for up to documents at ~200kb each Offsite secure file storage and/or backup (4.7gb) for the first year. $6/year thereafter for 10gb of storage Domain name $12/year Total $407/year 2014: $314 $24/hr hrs 13.1 hrs *Client requested an SSL certificate with Extended Validation i.e. the green bar in browsers.

9 2.2 Benefit Analysis Table 5 Benefits of elockbox System Current activities & resources used % Reduce Time Saved (Hours/Year) Case Management Case creation and tracking (20hrs * 5 case managers * 50 weeks) = 5000 hrs 70% 3500 Document Management Vital document upload (4 hrs * 5 case managers * 50 weeks) = 1000 hrs 33.33% Report Generation Custom reports (3 hrs * 4 monthly reports * 12 months) = 144 hrs for 30% 138 manual reporting User Management User management (2hrs * (5 case managers + 1 administrator) * 50 10% 50 weeks = 500 hrs Total hrs Total saved in 2014 (7 months) hrs 2.3 ROI Analysis Table 6 ROI Analysis Year Cost Benefit Cumulative Cumulative (Effort Saved) Cost Benefit ROI

10 Figure 1: ROI Analysis Graph Based on the ROI analysis, we will break even in 2014.

11 3. Risk Assessment Table 7 Risk Assessment Risks Security risks may turn up in one of our NDI packages or libraries especially the Laravel framework which is constantly being updated. Users may have difficulty adjusting to the new system Public agencies may not be interested or be wary in using the system Complexity some team members do not have all the necessary skills Reports generation requirement changes. Potential Magnitude Risk Exposure Probability Loss Risk Exposure Risk Mitigations Keep up to date with latest versions of packages and apply security patches. We can also provide documentation on the setup to the maintainers Provide extensive training on using the system, and receive feedback from users while developing the system Client can communicate with agencies during the development process to educate them about the system Workshops and assistance from other teammates Brainstorm with clients to find a simpler way without losing functionality.

12 3.1 Level of Service Feasibility Table 8 LOS Feasibility Level of Service Goals LOS-1 Data Size: This system should support at least 5000 users and 5 documents for each. LOS-2 Security: All the documents must be stored securely. LOS-3 Mobile Compatibility: This system should be viewable on mobile devices. LOS-4 Availability: This system should be down no more than 12hrs/monthly (excluding natural disasters) Rationale Both Apache and MySQL can handle this workload. SSL certificates can help encrypt transport data. If we decide to use Amazon S3, it has functionality to generate one-time keys for a limited access time. Responsive design will let us adapt the layout based on screen size. By using a VPS, we can guarantee better uptime. The host will also have a guaranteed uptime. 4. NDI/NCS Interoperability Analysis 4.1 Introduction COTS / GOTS / ROTS / Open Source / NCS Table 9 NDI Candidate Products Listing NDI/NCS Products Open Source NDI - Apache Open Source NDI - Nginx Open Source NDI - MySQL Open Source NDI - PostgreSQL Open Source NDI - Symfony Open Source NDI - Laravel Commercial NCS - Amazon S3 Open Source NDI - Git Open Source NDI - Subversion Purposes Web server Web server Database server Database server PHP MVC framework PHP MVC framework File storage web service Version control Version control

13 4.1.2 Connectors We are using the official Amazon Web Services PHP SDK to perform storage and retrieval on Amazon S3. Composer ( is used for installing and upgrading PHP packages, including the Laravel framework and the AWS SDK Legacy System There is no legacy system. However, the current storage is based on Salesforce which has proved to be unwieldy for the clients needs.

14 4.2 Evaluation Summary Table 10 NDI Evaluation NDI Usages Comments Apache Web server Positive points - Free and widely used - Documentation available Negative points - Heavier footprint than Lighttpd and Nginx which are good alternative servers. - Performs worse under very high loads MySQL 5 Laravel 4 Database server PHP framework Positive points - Free and widely used - Documentation available Negative points - No support except for commercial licensing - Differences in table definition when running in strict mode. Positive points - Open source - Documentation available - Integrated unit testing - Database agnostic development and migrations - Light footprint compared to popular frameworks like Symfony and Zend. Negative points - Command line dependencies - Developers will have to learn how to use it - Relatively new framework Amazon S3 File storage Positive points - Very low cost - Documentation available - Security tokens and limited access - Automatic versioningnegative points - Files stored offsite - Possible increased access time, especially if stored using reduced redundancy. Git Version control Positive points - Open source - Documentation available - Multiplatform - Distributed version control Negative points - None

15