final srs on medical requirement

7/25/2019 final srs on medical requirement

1/11

Software RequirementsSpecification

for

Automatization of MedicalReimbursement

Version 1.0 approved

Prepared by

1.Saurab !e"ade

#.Amey $ad%am%ar

&.'eepes $ati(a

V.).S.*.+

#,

t

-/ #01

Copyright 1999 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document.


2/11

Software Requirements Specification for Automatization of Medical Reimbursement

Page ii

Table of Contents

Table of Contents...........................................................................................................................ii

1. Introduction..............................................................................................................................11.1 Purpose.................................................................................................................................11.2 Intended Audience and Reading Suggestions.......................................................................11.3 Product Scope......................................................................................................................1

2. Overall Description..................................................................................................................12.1 Product Perspective..............................................................................................................12.2 Product Functions................................................................................................................12.3 User Classes and Characteristics..........................................................................................22.4 Operating nviron!ent........................................................................................................22." #esign and I!ple!entation Constraints...............................................................................22.$ User #ocu!entation............................................................................................................22.% Assu!ptions and #ependencies...........................................................................................2

3. External Interface Requirements............................................................................................23.1 User Inter&aces.....................................................................................................................23.2 'ard(are Inter&aces.............................................................................................................33.3 So&t(are Inter&aces..............................................................................................................33.4 Co!!unications Inter&aces..................................................................................................3

. !"stem #eatures........................................................................................................................34.1 )ogin*Signup........................................................................................................................44.2 Fill Application For!............................................................................................................"

4.3 Check Application Status.....................................................................................................6 4.4 FAQ's/Help......................................................................................................................... 7

$. Ot%er &onfunctional Requirements.......................................................................................'".1 Per&or!ance Re+uire!ents..................................................................................................%".2 Sa&et, Re+uire!ents.............................................................................................................%".3 Securit, Re+uire!ents..........................................................................................................-".4 So&t(are ualit, Attri/utes..................................................................................................-"." 0usiness Rules......................................................................................................................-

(nal"sis )odels.............................................................................................................................*


3/11


Page 1

1. Introduction

1.1 Purpose

Auto!atiation o& !edical rei!/urse!ent &acilit, &or users using an online (e/ service. Provides anoption &or e!plo,ees to appl, &or rei!/urse!ent o& !edicines and treat!ent (ho are una/le tovisit*travel to a particular hospital at distant places.

1.2 Intended Audience and Reading Suggestions

his docu!ent is intended &or developers proect !anagers !ar5eting sta&& users testers and docu!entation(riters. his docu!ent contains an overvie( o& the product the technolog, used &or interaction and the !ar5et

scope.

1.3 Product Scope

The online web service allows the users to apply for reimbursement of medicines and treatment billsfrom any distant place they might be. It also allows them to upload the scanned copies of themedical bills whenever they want to without any hustle and bustle.

2. Overall Description

2.1 Product Perspective

This product/service is new since the service is reducing the paper work, time, travelling cost, etc.by allowing the users to apply for reimbursement from any place.

2.2 Product Functions

The product/service is designed in such a way that the user can the perform the followingfunctions:-1.Login/Register to the service.

2.Fill in the Application form for the reimbursement.3.Upload scanned copies of medical bills.4.Check the reimbursement status.5.Check the reimbursement history.


4/11


Page 2

2.3 User Classes and Characteristics

he !ain user using this product (ill /e the one (ho is appl,ing &or his*her rei!/urse!ent o& !edical /ills.he user classes can /e /asicall, o& t(o t,pes i.e. e!plo,ees (ho are presentl, (or5ing at an organiationand e67e!plo,ees (ho have /een retired &ro! an organiation.

2.4 Operating Environment

This product being a complete web based service will work with operating systems such aswindows 98, vista, xp and above. And also browsers such as Google chrome, Mozilla Firefox,Safari, Internet Explorer. The hardware can be anything supporting these above softwares. Thus,Internet connectivity is must.

2.5 Design and Implementation Constraints

There are no constraints to the developer. The complete software is maintained by the developerand maintenance team. Only the internet services and networking will be maintained by theorganization.

2.6 User Documentation

The website provides FAQ's and help functions for the users to get familiar with the system. Alsoafter the system is setup at the organization, a person from the developers team will present a demoof the working of the website.

2.7 Assumptions and Dependencies

The physical verification of the document is to be done in this reimbursement process. So, we haveassumed that the organization will provide a period of minimum 2 months for the user to visit theorganization and verify the documents. Thus it depends on the organization to stipulate this period.

3. External Interface Requirements

3.1 User Interfaces

he user inter&ace &or the so&t(are shall /e co!pati/le to an, /ro(ser such as Internet 6plorer 8oilla or9oogle chro!e /, (hich user can access to the s,ste!.

he user inter&ace shall /e i!ple!ented using an, tool or progra!!ed using languages such as ht!l CSSP,thon php etc.


5/11


Page 3

3.2 Hardware Interfaces

The website can be accessed from desktop, Smartphone, laptops, ipads and any other potabledevices supporting browsers such as IE, Google chrome, Mozilla Firefox, Safari.

3.3 Software Interfaces

he user:s /ro(ser should /e '8)" co!pati/le &or a satis&actor, user e6perience.

3.4 Communications Interfaces

he s,ste! shall use the 'P protocol &or co!!unication over the internet and &or the intranetco!!unication (ill /e through CP*IP protocol suite.

4. System Features

he (e/site provides (ith !an, &eatures such as login*signup &ill application &or! chec5 status chec5histor,. Also it provides an e6tended &eature such as FA;s and 'elp.


6/11


Page 4

4.1 Login/Si

g nup


7/11


Page 5

4.2 Fill Application form

This feature allows the user to fill in the details of medicines or treatments to be reimbursed.


8/11


Page 6

4.3 Check Application Status

This feature shows the current status of application.

4.4 FAQ's/Help

This feature helps the user to understand the service more precisely.


9/11


Page 7

5. Other Nonfunctional Requirements

5.1 Performance Requirements

The website will perform with blazing speed. It also depends on the user's internet bandwidth. Butthe overall performance of the website will provide the user better reliability than any other website.

5.2 Safety Requirements

The user data and account details such as history of reimbursement, etc. will be backed up to themain server and also to the organization's server and can be easily retrieved in case of system crashor power failures.


10/11


Page 8

5.3 Security Requirements

The website is completely secure. Also the user information is secured and will not be disclosed toany third party without the user consent.

5.4 Software Quality Attributes

Availa/ilit,< I& the internet service gets disrupted (hile sending in&or!ation to the server thein&or!ation can /e send again &or veri&ication.Usa/ilit,< As the s,ste! is eas, to handle and navigates in the !ost e6pected (a, (ith no dela,s. Inthat case the s,ste! progra! reacts accordingl, and transverses +uic5l, /et(een its states

Analysis Models(ctivit" Dia+ram


11/11

Documents

final srs on medical requirement