Feasibility Evidence Description (FED) - Spring 2018 · Feasibility Evidence Description (FED) Team...

Feasibility Evidence Description (FED)

Team 02

Member Name Role Email

Rajat Verma Project Manager, Lifecycle Planner, Dev [email protected]

Preksha Gupta Software Architect, Operational Concept Engineer

[email protected]

Mangalore Rakesh Shenoy Software Developer, Prototyper [email protected]

Ankit Gupta Requirements Engineer, Tester [email protected]

Snehal Surendra Desai Prototyper, Software Developer [email protected]

Lu Wu Quality Focal Point, Tester [email protected]

Heidi Negron-Arroyo IIV and V, Feasibility Analyst [email protected]

10/17/2016

mailto:[email protected]

Feasibility Evidence Description (FED) Version 1.1

FED_FCP_F16_T02_V1.1.doc ii Version Date: 10/17/16

Version History

Date Author Version Changes made Rationale

10/13/16 Heidi 1.0 Added purpose of the FED and

status of the FED Initial draft for FC Package

10/17/16 Heidi 1.1 Added Business Case Analysis

Added Architecture Feasibility

and Process Feasibility

Added Risk Assessment and

NDI/NCS Interoperability

Analysis

Completed for FC Package


FED_FCP_F16_T02_V1.1.doc iii Version Date: 10/17/16

Table of Contents

Feasibility Evidence Description (FED) ......................................................................................................................i

Version History ........................................................................................................................................................... ii

Table of Contents ....................................................................................................................................................... iii

Table of Tables ............................................................................................................................................................iv

Table of Figures ........................................................................................................................................................... v

1. Introduction .......................................................................................................................................................... 1

1.1 Purpose of the FED Document ..................................................................................................................... 1

1.2 Status of the FED Document ........................................................................................................................ 1

2. Business Case Analysis ......................................................................................................................................... 2

2.1 Cost Analysis .................................................................................................................................................. 2

2.2 Benefit Analysis ............................................................................................................................................. 3

2.3 ROI Analysis .................................................................................................................................................. 4

3. Architecture Feasibility ........................................................................................................................................ 5

3.1 Level of Service Feasibility ........................................................................................................................... 5

3.2 Capability Feasibility .................................................................................................................................... 5

3.3 Evolutionary Feasibility ................................................................................................................................ 7

4. Process Feasibility ................................................................................................................................................ 8

5. Risk Assessment .................................................................................................................................................. 10

6. NDI/NCS Interoperability Analysis .................................................................................................................. 11

6.1 Introduction ................................................................................................................................................. 11

6.2 Evaluation Summary .................................................................................................................................. 12


FED_FCP_F16_T02_V1.1.doc iv Version Date: 10/17/16

Table of Tables

Table 1: Personnel Costs ............................................................................................................................................... 3

Table 2: Hardware and Software Costs ........................................................................................................................ 3

Table 3: Benefits of VYMA System ................................................................................................................................ 3

Table 4: ROI Analysis .................................................................................................................................................... 4

Table 5: Level of Service Feasibility ............................................................................................................................. 5

Table 6: Capability Requirements and Their Feasibility Evidence ............................................................................... 5

Table 7: Rationales for Selecting COTS-Based System ................................................................................................. 8

Table 8: Risk Assessment ............................................................................................................................................. 10

Table 9: NDI Products Listing .................................................................................................................................... 11

Table 10: NDI Evaluation ........................................................................................................................................... 12


Table of Figures

Figure 1: ROI Analysis Graph ...................................................................................................................................... 4


FED_FCP_F16_T02_V1.1.doc 1 Version Date: 10/17/16

1. Introduction

1.1 Purpose of the FED Document

The Feasibility Evidence Document (FED) provides a throughout analysis documenting the

feasibility of the VYMA project to be completed according to schedule and budget constraints.

Our conclusions are drawn from the different types of analysis presented in the following

sections: Business Case, Architecture Feasibility, Process Feasibility, Risk Assessment and

NDI/NCS Interoperability Analysis.

1.2 Status of the FED Document

The status of this FED is currently at the version number 1.1, which will be submitted along with

Foundations Commitment Package. This version will be reviewed with the necessary

stakeholders and if there are no changes to be made, the latest version of this document will be

delivered to the client.



2. Business Case Analysis

2.1 Cost Analysis

This section presents an analysis on the time (monetary and non-monetary) spent by the clients

on the different phases of the VYMA project.



2.1.1 Personnel Costs

Table 1: Personnel Costs

Activities Time Spent(Hours)

Total Time Available(12 weeks)

Exploration Phase

• Client Meetings (2 hours*1 week*1 person)

• Win Win Session 1 (1 hour * 1 person)

2 hours

1 hour

Valuation and Foundation Phase

• Win Win Session 2 (1 hours* 1 person) • Weekly Discussion Remote Meetings(1 hours*3

weeks*1 person) • Architecture Review Boards(1.5 hours* 2 times * 1

person)

1 hour

3 hours

3 hours

Development, Foundations, Operations Phase

• Weekly Client Meetings(1hour*6 weeks*1 person) • Handover Activities ( 2 hours* 2 weeks * 1 person

6 hours

4 hours

Total time spent 20 hours

2.1.2 Hardware and Software Costs

Table 2: Hardware and Software Costs

Type Cost Rationale

Squarespace Business Plan

(includes web hosting)

$18/per

month

Plan is needed for accessing Squarespace

features for creating and maintaining VYMA

website, cloud hosting and 24/7 customer

support.

Total 216

2.2 Benefit Analysis

Table 3: Benefits of VYMA System

Current activities & resources used % Reduce Time Saved (Hours/Year)

Registration System

User: Submit Registration application for 99 336



music courses

Website Maintenance Efforts

Volunteer updates multiple websites

regularly 40 9

Website Navigation

User: Search classes schedule (calendar) in

public website and download notes from

password protected website

50 3

Audience Outreach

Volunteer manages site’s search engine

presence 40 3

Total 351

2.3 ROI Analysis

Table 4: ROI Analysis

Year Cost Benefit

(Effort Saved)

Cumulative

Cost

Cumulative

Benefit ROI

2016 23 0 23 0 -1

2017 15 351 38 351 8.236842105

2018 16.5 351 54.5 702 11.88073394

2019 18.15 351 72.65 1053 13.49415003

2020 19.965 351 92.615 1404 14.15953139

Figure 1: ROI Analysis Graph



3. Architecture Feasibility

3.1 Level of Service Feasibility

Table 5: Level of Service Feasibility

Level of Service Requirement Product Satisfaction

LOS-1: 24/7 Customer Support Product Strategies: Squarespace Business Plan provides

online customer support 24/7 for addressing client inquiries.

Process Strategies: N/A

Analysis: Customer support can help client in creating and

maintaining website, adding services and integrations, and

maximizing use of resources available.

3.2 Capability Feasibility

Table 6: Capability Requirements and Their Feasibility Evidence

Capability Requirement Product Satisfaction

CR-1: Make Donations

Online

Software/Technology used: Squarespace ‘Donations’ block

Feasibility Evidence: Donations feature is supported by Squarespace

via the creation of a ‘Donations’ block that can be placed on a page

and allows visitors to donate amount of money desired

Referred use case diagram: UC-11

CR-2: Download music

notes

Software/Technology used: Squarespace File Management

Feasibility Evidence: The admin of website can upload files by

attaching them to links in text, navigation and images


CR-3: Access password

protected content

Software/Technology used: Squarespace ‘Private Page’ feature

Feasibility Evidence: Squarespace allows to set a page password

which prevents anyone without the password from viewing the page

Referred use case diagram: UC-3, UC-4

CR-4: Send

Inquiries/feedbacks

through ‘Contact Us’ page

Software/Technology used: Squarespace ‘Form Block’ feature

Feasibility Evidence: Form can be used to create contact form and

forward submission to email address


CR-5: Access details of

music courses and

schedule of classes

Software/Technology used: Squarespace ‘Create Page’ features

Feasibility Evidence: Admin can manage and customize content of

every page to organize information as desired


CR-6: Register for music

courses

Software/Technology used: Squarespace ‘Custom Checkout Form’

Feasibility Evidence: Admin can create custom forms that users can

later complete and submit




CR-7: Pay tuition Software/Technology used: Squarespace ‘Custom Checkout Form’

Feasibility Evidence: When users use registration form, they will be

asked billing information for successful completion of registration


CR-8: Maintain/Access

VYMA events calendar

Software/Technology used: Squarespace ‘Events Page’

Feasibility Evidence: Events Page feature allows admin to add

calendar or list of events to site


CR-9: Update News

(Announcements) section

Software/Technology used: Squarespace ‘Blog Page’, ‘Blog post’

and Mailchimp integration features

Feasibility Evidence: Using Blog page/Blog post allows admin to

post news and important notifications regularly.


CR-10: Access

registration forms

Software/Technology used: Squarespace form forwarding

Feasibility Evidence: When forms are submitted Squarespace

forwards it to an email address. Submissions can also be exported as

.csv files


CR-11: Browse pictures Software/Technology used: Squarespace ‘Gallery Block’ for

uploading images

Feasibility Evidence: Squarespace provides features for presenting

media (videos, images, audio) via blocks that can be added to page,


CR-12: Shop for concerts

DVDs

Software/Technology used: Squarespace ‘Products Page’

Feasibility Evidence: Squarespace ‘Business Plan’ allows to sell

unlimited products and maintain a shopping cart


CR-13: Receive email

notifications and

reminders

Software/Technology used: Squarespace ‘Build Mailing List’

feature using Mailchimp

Feasibility Evidence: Using Mailchimp allows admin to disseminate

information easily among subscribers


CR-14: View Roster Page

of Parents’ Information

Software/Technology used: Squarespace ‘Private Page’ feature

Feasibility Evidence: Admin can create a password-protected page

including details of Parents’ contact information


CR-15: View Trailers Software/Technology used: Squarespace Galleries features

Feasibility Evidence: Squarespace allows admin to embed videos

(not upload them directly) in Video Blocs, Gallery Blocks and

Gallery Pages




3.3 Evolutionary Feasibility

At the time of this draft, no evolutionary requirements are negotiated.



4. Process Feasibility

Decision Criteria Rating Scale; 0: Very Low; 1: Low; 2: Medium; 3: High; 4: Very High

Importance Rating Scale: 1: Low; 2: Medium; 3: High

Table 7: Rationales for Selecting COTS-Based System

Criteria Importance Project Status Rationales

>30 % of NDI/NCS

features

3 4 Website creation using

Squarespace. Additional

features added with others

NDI/NCS.

Single NDI/NCS 1 0 Project cannot be completed

with a single NDI/NCS.

Unique/ inflexible business

process

1 0 Business process is common.

Need control over upgrade

/ maintenance

2 3 Squarespace

maintains/upgrades servers as

necessary.

Rapid deployment 2 2 System deployment occurs at

end of CSCI577a.

Critical on compatibility 3 4 New NDI/NCS need to be

compatible with Squarespace.

Internet connection

independence

1 0 Internet connection is needed.

Need high level of services

/ performance

3 4 Services must integrate

seamlessly and multiple users

should be able to browse,

complete application and make

payments.

Need high security 3 3 Password-protected content

should not be accessed by

unauthorized users.

Asynchronous

communication

2 2 Communication handled by

Squarespace.

Be accessed from

anywhere

1 1 VYMA website can be

accessed by anyone in the

world with a valid device and

internet connection.

Critical on mass schedule

constraints

1 2 Project should be completed by

end of CSCI577a.

Lack of personnel

capability

2 2 Although development team

has no experience using

Squarespace, it does have the

skills and experience to



complete project.

Require little upfront costs 3 3 Budget limited to $216 per

year

Require low total cost of

ownership

3 3 Budget limited to $216 per

year

Not-so-powerful local

machines

1 2 Website should be able to be

accessed from any device with

internet connection and

internet browsing capability.



5. Risk Assessment

Table 8: Risk Assessment

Risks

Risk Exposure

Risk Mitigations Potential

Magnitude

Probability

Loss

Risk

Exposure

Total dependency on Squarespace

for developing the website.

9 2 18 If a specific feature is not explicitly

supported by Squarespace, team

should be prepared to add manual

code blocks.

Team members’ inexperience

using Squarespace

1 8 8 For Squarespace features are not

fully understood team members

should read documentation, watch

tutorials and/or reach Squarespace

customer support.

Team members limited

availability

2 6 12 Set regular weekly meetings. Each

team member should inform with

reasonable time about changes in

schedule or availability.

Client Budget Cut 2 8 16 Evaluate Squarespace plans and be

prepared to select a 'secondary'

package with less functions

supported

NDI/NCS Conflicts 4 7 28 Research Squarespace supported

services when in need to implement a

new feature, and prototype desired

functionality to evaluate how new

service integrates with others

currently used.



6. NDI/NCS Interoperability Analysis

6.1 Introduction

The client requested the use of Squarespace for the creation of the VYMA website. Squarespace

is a Content Management System that provides website creation and customization tools,

hosting, and customer support. There are a variety of services that can be integrated with

Squarespace for maximizing website capabilities including a developer platform, social

integrations, Mailchimp mailing lists and payments processor.

6.1.1 COTS / GOTS / ROTS / Open Source / NCS

Table 9: NDI Products Listing

NDI/NCS Products Purposes

Squarespace Website creation and

hosting

Stripe Process tuition and

donation payments

Mailchimp Mailing list service

6.1.2 Connectors

Currently, no external connectors need to be added. Squarespace handles all aspects of client-

server communication, hosting, and maintenance. It also provides support for official

integrations of external services such as Stripe and Mailchimp.

6.1.3 Legacy System

The VYMA organization maintained multiple websites for providing information and

communicating with VYMA community: students, parents, teachers. The content on these

websites will be consolidated and migrated to Squarespace platform. No compatibility between

the old and new system is needed.

http://www.squarespace.com/



6.2 Evaluation Summary

Table 10: NDI Evaluation

NDI Usages Comments

Squarespace Create, customize

and maintain

website

Positive Points

- Responsive and mobile-

compatible quality

templates

- Opportunity for making

changes to templates and

website capabilities via a

developer platform tool

- No coding experience

needed for adding

functionalities from

Squarespace official

integrations (ready-to use

apps and widgets)

- All pricing plans offer

hosting, maintenance and

security

- 24/7 chat/email customer

support

Negative Points

- Limited support for third-

party integrations

Stripe Make payments Positive Points

- Official integration

included with Squarespace

- Recurring Payments feature

supported

Negative Points

- Squarespace could stop

support at any time



Mailchimp Maintain mailing

lists for forwarding

notifications and

reminders

Positive Points

- Client is familiar with

service

- Official integration with

Squarespace

Negative Points

- Squarespace could stop

support at any time

Feasibility Evidence Description (FED) - Spring 2018 · Feasibility Evidence Description (FED) Team...

Documents

Transcript of Feasibility Evidence Description (FED) - Spring 2018 · Feasibility Evidence Description (FED) Team...