/
File-Mate 1500 File-Mate 1500

File-Mate 1500 - PowerPoint Presentation

phoebe-click
phoebe-click . @phoebe-click
Follow
399 views
Uploaded On 2016-05-28

File-Mate 1500 - PPT Presentation

Design Review 1 November 19 2013 Keven Abbott Architect Tyler Crouse Sponsor Liason Kiana Delventhal Team Leader REcorder Liam Westby Release Manager Webmaster 1 Sponsor Form Magic Inc ID: 339214

file data user requirements data file requirements user mate database system testing application 1500 access create interface web form

Share:

Link:

Embed:

Download Presentation from below link

Download Presentation The PPT/PDF document "File-Mate 1500" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.


Presentation Transcript

Slide1

File-Mate 1500Design Review 1November 19, 2013

Keven Abbott, ArchitectTyler Crouse, Sponsor LiasonKiana Delventhal, Team Leader, REcorderLiam Westby, Release Manager, Webmaster

1Slide2

SponsorForm Magic, Inc.Located in Flagstaff, ArizonaProducer of software for automated filing of forms

Project Sponsor is Dave Schurz2Slide3

File-Mate 1500File-Mate 1500

Desktop application created to assist doctors and physicians assistants fill out the CMS 1500 Health Insurance Claim FormCMS 1500 is an industry standard form for making claims against patients’ insurance plans3Slide4

ProblemWhile the existing software is useful, the desktop client lacks:ScalabilityPortability

Accessibility4Slide5

Current Application Interface

5Slide6

SolutionCreate a web-based version of the File-Mate 1500 application, accessible from any computer with a modern web browser.

The web-based system will:Allow concurrent access to a shared data setEnable access to the system without needing to install softwareScale to support the needs of an entire practice, or even multiple practices6Slide7

System Overview

7Slide8

Requirements

8Slide9

Functional Requirements: ClientPage TypesWelcome Page

Registration PagesTrial PagesPatient Information PagesUser Account and Settings PagesContact PageCompatibility

Browser support

for leading

desktop and mobile devices

9Slide10

Functional Requirements: ServerSupport concurrent access to patient dataEnsure data availability, confidentiality, and integrity

Support multiple types of users with separate permissionsAdministrator, registered user, trial userFacilitate data import, export, and backupAllow users to add data from a file, or save it to a file for backup10Slide11

Non-Functional RequirementsSecurityData transfer between database and web service without any third-party interference

ScalabilityAllow any amount of patients per client (limitations may be imposed by purchased license level)PerformanceMust retrieve data from database in less than 2 seconds and generate PDF form in less than 10 secondsUsabilityPresent data in a concise manner in order to allow user to interpret data easily.11Slide12

Environmental RequirementsServerWeb Server: ApacheLanguage: PHP

Database: MySQLClientMarkup: HTMLStyling: CSSInteractivity: JavaScript12Slide13

Architecture

13Slide14

Current Application Interface

14Slide15

Risks15

RiskSeverity

Mitigation

Data Leaked

High

Database encryption

Ensure HIPAA

compliance

Data Corrupted

High

Backup

data

regularly

Website Inaccessible

Low

Ensure data integrity

remains when outage is overSlide16

Graphical Schedule

16

ID

Task Name

1

Project Begins

2

Requirements

3

Gather and refine requirements

4

Design

5

Establish architecture

6

Develop database schema

7

User interface mockups

8

Design Complete

9

Implementation

10

Spring Semester

11

Create database

12

Create components from architecture

13

Build out user interface pages

14

Develop business logic

15

Create documentation

16

System Implemented

17

Testing

18

Unit testing

19

Load testing

20

User testing

21

Testing Complete

22

Deployment

23

Sign off on delivered project

24

Final presentation

25

Project complete

11/17

12/20

1/13

3/3

4/18

5/9

T

F

S

S

M

T

W

T

F

S

S

M

T

W

T

F

S

S

M

T

W

T

F

S

S

M

Oct 13, '13

Nov 3, '13

Nov 24, '13

Dec 15, '13

Jan 5, '14

Jan 26, '14

Feb 16, '14

Mar 9, '14

Mar 30, '14

Apr 20, '14

May 11, '14Slide17

ConclusionProblemDesktop application inefficient, inflexibleSuitable for one user, not entire practice

SolutionWeb-based system offers scalability, flexibilityMultiple users can access reliablyComposed of three aspectsClientServerDatabase17Slide18

File-Mate 1500Design Review 1

Questions?18