Professional Documents
Culture Documents
Final Srs On Medical Requirement
Final Srs On Medical Requirement
Specification
for
Automatization of Medical
Reimbursement
Version 1.0 approved
Prepared by
1.Saurabh Fegade
2.Amey Bhadkamkar
3.Deepesh Bathija
V.E.S.I.T
24th JULY 2015
Copyright1999byKarlE.Wiegers.Permissionisgrantedtouse,modify,anddistributethisdocument.
TableofContents
Table of Contents...........................................................................................................................ii
1. Introduction..............................................................................................................................1
1.1 Purpose.................................................................................................................................1
1.2 Intended Audience and Reading Suggestions.......................................................................1
1.3 Product Scope......................................................................................................................1
2. Overall Description..................................................................................................................1
2.1 Product Perspective..............................................................................................................1
2.2 Product Functions................................................................................................................1
2.3 User Classes and Characteristics..........................................................................................2
2.4 Operating Environment........................................................................................................2
2.5 Design and Implementation Constraints...............................................................................2
2.6 User Documentation............................................................................................................2
2.7 Assumptions and Dependencies...........................................................................................2
3. External Interface Requirements............................................................................................2
3.1 User Interfaces.....................................................................................................................2
3.2 Hardware Interfaces.............................................................................................................3
3.3 Software Interfaces..............................................................................................................3
3.4 Communications Interfaces..................................................................................................3
4. System Features........................................................................................................................3
4.1 Login/Signup........................................................................................................................4
4.2 Fill Application Form............................................................................................................5
4.3CheckApplicationStatus.....................................................................................................6
4.4FAQ's/Help.........................................................................................................................7
5. Other Nonfunctional Requirements.......................................................................................7
5.1 Performance Requirements..................................................................................................7
5.2 Safety Requirements.............................................................................................................7
5.3 Security Requirements..........................................................................................................8
5.4 Software Quality Attributes..................................................................................................8
5.5 Business Rules......................................................................................................................8
Analysis Models.............................................................................................................................8
1.
Introduction
1.1
Purpose
Automatization of medical reimbursement facility for users using an online web service. Provides an
option for employees to apply for reimbursement of medicines and treatment who are unable to
visit/travel to a particular hospital at distant places.
1.2
IntendedAudienceandReadingSuggestions
This document is intended for developers, project managers, marketing staff, users, testers, and documentation
writers. This document contains an overview of the product, the technology used for interaction and the market
scope.
1.3
ProductScope
Theonlinewebserviceallowstheuserstoapplyforreimbursementofmedicinesandtreatmentbills
fromanydistantplacetheymightbe.Italsoallowsthemtouploadthescannedcopiesofthe
medicalbillswhenevertheywanttowithoutanyhustleandbustle.
2.
OverallDescription
2.1
ProductPerspective
Thisproduct/serviceisnewsincetheserviceisreducingthepaperwork,time,travellingcost,etc.
byallowingtheuserstoapplyforreimbursementfromanyplace.
2.2
ProductFunctions
Theproduct/serviceisdesignedinsuchawaythattheusercantheperformthefollowing
functions:
1.Login/Registertotheservice.
2.FillintheApplicationformforthereimbursement.
3.Uploadscannedcopiesofmedicalbills.
4.Checkthereimbursementstatus.
5.Checkthereimbursementhistory.
2.3
UserClassesandCharacteristics
The main user using this product will be the one who is applying for his/her reimbursement of medical bills.
The user classes can be basically of two types, i.e. employees who are presently working at an organization
and ex-employees who have been retired from an organization.
2.4
OperatingEnvironment
Thisproductbeingacompletewebbasedservicewillworkwithoperatingsystemssuchas
windows98,vista,xpandabove.AndalsobrowserssuchasGooglechrome,MozillaFirefox,
Safari,InternetExplorer.Thehardwarecanbeanythingsupportingtheseabovesoftwares.Thus,
Internetconnectivityismust.
2.5
DesignandImplementationConstraints
Therearenoconstraintstothedeveloper.Thecompletesoftwareismaintainedbythedeveloper
andmaintenanceteam.Onlytheinternetservicesandnetworkingwillbemaintainedbythe
organization.
2.6
UserDocumentation
ThewebsiteprovidesFAQ'sandhelpfunctionsfortheuserstogetfamiliarwiththesystem.Also
afterthesystemissetupattheorganization,apersonfromthedevelopersteamwillpresentademo
oftheworkingofthewebsite.
2.7
AssumptionsandDependencies
Thephysicalverificationofthedocumentistobedoneinthisreimbursementprocess.So,wehave
assumedthattheorganizationwillprovideaperiodofminimum2monthsfortheusertovisitthe
organizationandverifythedocuments.Thusitdependsontheorganizationtostipulatethisperiod.
3.
ExternalInterfaceRequirements
3.1
UserInterfaces
The user interface for the software shall be compatible to any browser such as Internet Explorer, Mozilla or
Google chrome by which user can access to the system.
The user interface shall be implemented using any tool or programmed using languages such as html, CSS,
Python, php, etc.
3.2
HardwareInterfaces
Thewebsitecanbeaccessedfromdesktop,Smartphone,laptops,ipadsandanyotherpotable
devicessupportingbrowserssuchasIE,Googlechrome,MozillaFirefox,Safari.
3.3
SoftwareInterfaces
The users browser should be HTML5 compatible for a satisfactory user experience.
3.4
CommunicationsInterfaces
The system shall use the HTTP protocol for communication over the internet and for the intranet
communication will be through TCP/IP protocol suite.
4.
SystemFeatures
The website provides with many features such as login/signup, fill application form, check status, check
history. Also it provides an extended feature such as FAQ's and Help.
4.1
g
Login/Si
nup
4.2
FillApplicationform
Thisfeatureallowstheusertofillinthedetailsofmedicinesortreatmentstobereimbursed.
4.3CheckApplicationStatus
Thisfeatureshowsthecurrentstatusofapplication.
4.4FAQ's/Help
Thisfeaturehelpstheusertounderstandtheservicemoreprecisely.
5.
OtherNonfunctionalRequirements
5.1
PerformanceRequirements
Thewebsitewillperformwithblazingspeed.Italsodependsontheuser'sinternetbandwidth.But
theoverallperformanceofthewebsitewillprovidetheuserbetterreliabilitythananyotherwebsite.
5.2
SafetyRequirements
Theuserdataandaccountdetailssuchashistoryofreimbursement,etc.willbebackeduptothe
mainserverandalsototheorganization'sserverandcanbeeasilyretrievedincaseofsystemcrash
orpowerfailures.
5.3
SecurityRequirements
Thewebsiteiscompletelysecure.Alsotheuserinformationissecuredandwillnotbedisclosedto
anythirdpartywithouttheuserconsent.
5.4
SoftwareQualityAttributes
Availability: If the internet service gets disrupted while sending information to the server, the
information can be send again for verification.
Usability: As the system is easy to handle and navigates in the most expected way with no delays. In
that case the system program reacts accordingly and transverses quickly between its states
AnalysisModels
Activity Diagram