Feasibility Evidence Description (FED)

hamburgerfensuckedSecurity

Nov 20, 2013 (3 years and 11 months ago)

144 views

Feasibility Evidence Description

Version 2.1

Feasibility Evidence Description
(FED)




MedFRS Device Diagnostic Software






Team 16








Misha Dowd

Project Manager

Delnaz Gundevia

Life Cycle Planner

Anfal Abdul Jaleel

System

Architect

Nanda Kishore Kolleje
Rao

System Requirements
Engineer

Anupam Kumar

Feasibility Analyst

Jackie Cheng

IIV & V






10.16.2013



Feasibility Evidence Description

Version 2.1

Version History


Date

Author

Version

Changes made

Rationale

09/2
6
/13

AAJ

1.0



Original for CSCI577a; Tailored from

ICSM OCD Template
; Removed
Section 4: NDI/NCS Feasibility
Analysis
; Changed Section 3 : Risk
Assessment
; Changed Section 1 :
Introduction



To fit CS577a course content
, and
include only the content that is to
be submitted for VCR

09/27/13

MD

1.1



Removed
Section 2: Business Analysis



To remove the sections not filled

9/27/13

MD

1.2



Changed Formatting



To make it more aesthetically
pleasing

10/11/13

AK

2.0



Added Business Case Analysis,
Architecture Feasibility, Process
Feasibility, NDI/NCS
Interoperability
Analysis,



Updated Risk Analysis



FC package

10/16/2013

AAJ

2.1



Formatting



To make it uniform


























Feasibility Evidence Description

Version 2.1

Table of Contents

Feasibility Evidence Description (FED)

................................
................................
.......................

1

Version History

................................
................................
................................
................................
...................

2

Table of Contents

................................
................................
................................
................................
.............

3

Table of Tables

................................
................................
................................
................................
...................

4

Table of Figures

................................
................................
................................
................................
.................

5

1.

Introduction

................................
................................
................................
................................
..........................

6

1.1

Purpose of the FED Document

................................
................................
................................
.....................

6

1.2

Status of the FED Document

................................
................................
................................
........................

6

2.

Business Case Analysis

................................
................................
................................
................................
.........

7

2.1

Cost Analysis

................................
................................
................................
................................
..................

8

2.2

Benefits Analysis

................................
................................
................................
................................
............

9

3.

Risk
Assessment

................................
................................
................................
................................
..................

11

4.

NDI/NCS Interoperability Analysis

................................
................................
................................
..................

12

4.1

Introduction

................................
................................
................................
................................
.................

12

4.2

COTS /
GOTS / ROTS / Open Source / NCS

................................
................................
............................

12

4.3

Connectors

................................
................................
................................
................................
...................

12

4.4

Legacy System

................................
................................
................................
................................
.............

12

4.5

Evalua
tion Summary

................................
................................
................................
................................
..

13


Feasibility Evidence Description

Version 2.1

Table of Tables


Table 1 : Program Model

................................
................................
................................
................................
..............

7

Table 2: Personnel Costs

................................
................................
................................
................................
...............

8

Table 3: Hardware and Software Costs

................................
................................
................................
........................

8

Table 4: Benefits of MedFRS System

................................
................................
................................
.............................

9

Table 5: ROI Analysis (Time saved)

................................
................................
................................
..............................

9

Table 6: ROI Analy
sis (Money saved)

................................
................................
................................
.........................

10

Table 7: Risk Assessment

................................
................................
................................
................................
.......

11

Table 8: NDI Products Listing

................................
................................
................................
................................
....

12

Table 9 : Evaluation Summary

................................
................................
................................
................................
....

13



































Feasibility Evidence Description

Version 2.1

Table of
Figures


Figure 1 : ROI
Analysis (Time Saved)

................................
................................
................................
...........................

9

Figure 2 : ROI Analysis (Money Saved)

................................
................................
................................
......................

10

Feasibility Evidence Description

Version 2.1

1.

Introduction

1.1

Purpose of the FED Document

This document aims to validate the feasibility of
the
Med
ical

First Response
System
Device Diagnostic Software
project. This is achieved by identifying
potential risks that the project has and then mitigate
those risks
by creating a
workaround for
the obstacles. This will give the development team and
stakeholders

a clear
er

picture of the project

s state, benefits
and rate of
interest
; thus, aiding the development team in creating a clear workflow for the
project
.

1.2

Status of the FED Document

The status of the FED is currently at the
Foundation

Commitment Package
phase (version
2.1
)
.

This version created
states 6 risks along with the risk
exposure and how to mitigate those risks.
Feasibility Evidence Description

Version 2.1

2.

Business Case Analysis

Table
1

: Program Model

Assumptions



Network infrastructure and cloud infrastructure are always available



Apt funding is available
for the deployment of the system



EMT would use the system




Stakeholders

Initiatives

Value

Beneficiaries



Developers



Client



Volunteers



Transport
Coordinators



Supervisors



Create preliminary
da
tabase
management system
for
Volunteers/First
Responders to use



Client will train
volunteers and EMTs
on the system



Developer team will
train the client on
the system



Existing standard
operating procedures
will be modified by
digitizing it (Business
Process)



Maintain order in
chaotic medical
situation



Expedite time for

triage



Increase the number
of lives saved



Empower the
community to cope
with disaster
situations




Victims



Volunteers



EMS



Client



Supervisors

Costs



Development Cost



Training Cost



Hardware & Network Infrastructure cost



Device and utilities Cost
(iPhone/iPad,
paper barcodes)



Volunteer Medical Kit Cost

Benefits



Faster Response in state of emergency



Organized and structured approach towards
helping out in times of emergency



Impart training and knowledge of emergency
response procedures to volunteer
s



Save lives



Collect data for planning for future emergencies
and improving existing operating procedures




Feasibility Evidence Description

Version 2.1


2.1

Cost Analysis

2.1.1

Personnel Costs

Table
2
: Personnel Costs

Activities

Time Spent (Hours)

Exploration, Valuation and
Foundations Phase: (CSCI
577a 12 Weeks)


WinWin Negotiation Meeting Cost

2 times * 2 hours/each
* 5 people

20

Total Effort

: VC package

12

Client Meetings 2 meetings *
30

minutes/each * 5 people

5

Total Effort : FC package

35

Team Meetings

40

Prototype development time:

2
0

Maintenance Time (Bugzilla, Project website, PR, MPP)

5

Total Time

13
7


2.1.2

Hardware and Software Costs

Table
3
: Hardware and Software Costs

Type

Cost

Rationale

iOS developer License

$100/year

Necessary if the app is to be made
available to
volunteers/EMTs/Supervisors to use

Sever Host
i
ng

Free

USC will provide hosting space

Software / GIMP

Free

For drawing icons/images/artwork
used in app/website

Software / Google Maps
API

Free

For Mapping
out locations for
enabling easily finding locations of
victims

Software / Xcode

Free

Integrated Development Environment
to Develop iOS applications

Software / Eclipse

Free

Integrated Development Environment
to Develop Server
Side Code


Software / MySQL
workbench

Free

Integrated Development Environment
to Develop Database Schema

Software / Visual
Paradigm

Free

Software
Modeling

tool to model the
system

Printed Barcodes/Bands

$
10
0

For 100
0

plastic barcode tags


Feasibility Evidence Description

Version 2.1

Blood pressure cuffs

$4000
*

One time
purchase 100 units

Total yearly cost

$
4
200



2.2

Benefits Analysis

Table
4
: Benefits of
MedFRS

System

Current activities & resources
used

% Reduce

Time Saved (Hours/
Disaster/per 1000
victims
)

Victim Processing

EMT victim’s condition

identification and location
time

40

3
5
.
55556

Supervisor

lead
-
in

time

96.1

8
.
3333

Time taken by
Volunteer

tag
victim

81

2
5
.
5666


Current activities & resources
used

% Reduce

Money

Saved (
Dollars
/
Disaster/per 100
victims
)

Triage Tags

Using a cheaper

tags

92

115


2.2

ROI Analysis

Table
5
: ROI Analysis

(Time saved)

Year

Cost

Benefit

(Effort Saved)

Cumulative
Cost

Cumulative
Benefit

ROI

2013

137

69.4

137

20.4

-
0
.49314

2014

12

69.4

149

138.88

-
0
.06792

2015

12

69.4

161

208.32

0
.293913

2016

12

69.4

173

277.76

0
.605549


Figure
1

: ROI Analysis (Time Saved)

Feasibility Evidence Description

Version 2.1

Table
6
: ROI Analysis (Money saved)

Year

Cost

Benefit

(Effort Saved)

Cumulative
Cost

Cumulative
Benefit

ROI

2013

4130

375

4130

375

-
0.909200969

2014

31.5

393.75

4161.5

768.75

-
0.815270936

2015

32.03

413.4375

4193.53

1182.1875

-
0.718092514

2016

33.63

434.11125

4227.16

1616.29875

-
0.617639562



Figure
2

: ROI Analysis (Money Saved)

Assumptions:



3
disaster per year

(
www.seismolab.caltech.edu/earthquakes.html

)



5% increase in cost of plastic tags per year



5% increase in cost of paper tags per year




-1.5
-1
-0.5
0
0.5
1
1.5
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
2027
2028
2029
2030
ROI

ROI
Feasibility Evidence Description

Version 2.1

3.

Risk Assessment

Table
7
: Risk Assessment

Risks

Risk Exposure

Risk Mitigations

Potential
Magnitude

Probability
Loss

Risk
Exposure

The system we create
may not interface with
the existing system that
the EMS currently uses

9

2

18

If needed, enable the EMT
to access the data outside
the current system that
they use.

The standard operating
procedure details may
not be complete

3

2

6

We go back to the client
with our understanding of
the SOP and ask for more
information if present.

The wireless network
may not be available

9

3

27

Set up the possibility of
using a wired connection if
needed.

Unauthorized
individuals may be able
to access the data
collected

7

4

28

Set up authentication and
authorization mechanisms
for users of the

system

Low levels of experience
in software engineering
among the team
members

6

5

30

Each member of the team
should identify areas they
need to improve upon and
learn the required skills

The scope may be too
wide to implement in the
timeframe given (1
semester)

8

8

64

Negotiate the scope or the
outcome for the semester

Triage Time might
increase due to
lack of
familiarity


5

6

30

Conduct regular training
sessions

Add a
short
tutorial video

in the app



Feasibility Evidence Description

Version 2.1

4.

NDI/NCS Interoperability Analysis

4.1

Introduction

The system will be using a wide array of NDI/NCI for its development. The
exhaustive list of all the candidate
software, libraries, net
-
centric services
components is described below.

4.2

COTS / GOTS / ROTS / Open Source / NCS

Table
8
:
NDI Products Listing

NDI
/NCS

Products

Purposes

Apache
HTTP
server

Potential server

Glassfish HTTP server

Potential server

MySQL

Database

Java security library (javax.crypto
package)

Potential
System Security
library

PHP security library (phpseclib)

Potential
System Security

library

iOS
Development
platform

Mobile
Client UI

alternative

Android development platform

Mobile Client UI alternative

Java server side development
platform

Potential Server side
development platform

PHP server side
development
platform

Potential Server side
development platform

Ruby on rails server side
development platform

Potential Server side
development platform

Python server side development
platform

Potential Server side
development platform

4.3

Connectors



HTTP



MySQL Protocol



PHP


MySQL connector
/
Java


MySQL connector
/Ruby
-
MySQL Connector
/Python
-
MySQL Connector

4.4

Legacy System

This is a brand new system and does not require any legacy system interfacing

Feasibility Evidence Description

Version 2.1

4.5

Evaluation Summary


Table
9

: Evaluation Summary

NDI

Usages

Comments

Apache HTTP
Server

Potential server

Supports almost every
server side development
platforms
(PHP/Python/Ruby)

Glassfish HTTP
Server

Potential server

Made specifically to
support java based
server side
development,
but can support every
major development
platform language

MySQL

Database

High performance
database to store and
retrieve data, free and
community test, highly
rated

Java security
library

Security package

Public key encryption,
certification
mechanism,
checksums; will be
default choice if java is
server side development
platform

PHP security
library

Security package

Public key encryption,
certification mechanism,
checksum; will be
default choice if PHP is
server side development
platform

Rub
y security
library

Security package

Public key encryption,
certification mechanism,
checksum; will be
default choice if Ruby is
server side development
platform

iOS development

platform

Mobile client UI

Allows for rapid
prototyping; easy to
develop on
;
team
-
members are familiar
with this platform

Feasibility Evidence Description

Version 2.1

Android
development
platform

Mobile client UI

Also allows for rapid
prototyping; java based;
easier deployment cycle;
team
-
member are not
familiar with this
platform

Java server side
development
platform

Java
server side
development
platform

Lots of frameworks
available; easy to use;
team
-
members not
familiar with many
frameworks

PHP server side
development
platform

PHP server side
development
platform

Lots of frameworks
available; easy to use;
team
-
member a l
ittle
familiar with a few
frameworks

Ruby on rails
server side
development
platform

Ruby on rails
server side
development
platform

Short development cycle;
team members familiar
with development

Python server side
development
platform

Python server side
development
platform

Lots of frameworks
available; easy to use;
team
-
members not
familiar with frameworks