Software Requirements

Specification
for

<Online Health Care

Management>
Version 1.0 approved

Prepared by <Amna

Sidrah kaleem

Sara amin>

<international Islamic university islamabad>

<11-May-19>

Copyright © 1999 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document.
Software Requirements Specification for <Project> Page ii

Table of Contents
Table of Contents .......................................................................................................................... ii
Revision History ............................................................................................................................ ii
1. Introduction ..............................................................................................................................1
1.1 Purpose............................................................................................................................................. 1
1.2 Document Conventions .................................................................................................................... 1
1.3 Intended Audience and Reading Suggestions .................................................................................. 1
1.4 Product Scope .................................................................................................................................. 1
1.5 References ........................................................................................................................................ 2
2. Overall Description ..................................................................................................................2
2.1 Product Perspective.......................................................................................................................... 2
2.2 Product Functions ............................................................................................................................ 2
2.3 User Classes and Characteristics ..................................................................................................... 3
2.4 Operating Environment .................................................................................................................... 3
2.5 Design and Implementation Constraints .......................................................................................... 4
2.6 User Documentation ........................................................................................................................ 4
2.7 Assumptions and Dependencies ...................................................................................................... 4
3. External Interface Requirements ............................................. Error! Bookmark not defined.
3.1 User Interfaces ................................................................................................................................. 5
3.2 Hardware Interfaces ......................................................................................................................... 8
3.3 Software Interfaces .......................................................................................................................... 8
3.4 Communications Interfaces ............................................................................................................. 8
4. System Features .......................................................................................................................9
4.1 System Feature 1 .............................................................................Error! Bookmark not defined.
4.2 System Feature 2 (and so on) ..........................................................Error! Bookmark not defined.
5. Other Nonfunctional Requirements .....................................................................................10
5.1 Performance Requirements .............................................................Error! Bookmark not defined.
5.2 Safety Requirements .......................................................................Error! Bookmark not defined.
5.3 Security Requirements ....................................................................Error! Bookmark not defined.
5.4 Software Quality Attributes ............................................................Error! Bookmark not defined.
5.5 Business Rules ................................................................................Error! Bookmark not defined.
6. Other Requirements .................................................................. Error! Bookmark not defined.
Appendix A: Glossary..................................................................................................................11
Appendix B: Analysis Models ......................................................... Error! Bookmark not defined.
Appendix C: To Be Determined List .............................................. Error! Bookmark not defined.

Revision History
Name Date Reason For Changes Version
Software Requirements Specification for <Project> Page 1

1. Introduction
1.1 Purpose
The purpose of the Online Health Care Management System is to create a Free and Open Source Software .
This project is being developed mainly for user to get guidance on their health issues through an online
health care system., contain web interface through which a user can access a personal account, directly
communicate with doctor, online treatment and getting prescription/healthcare advices ,Receptionist who
handles online appointments, and the constraints that must be satisfied for security purposes.

1.2 Document Conventions

The document is prepared using Microsoft Word 2016 and has used the font type 'Times
New Roman'. The fixed font size that has been used to type this document is 12pt with 1.5 line
spacing. It has used the bold property to set the headings of the document. Document was created based on
the IEEE template for System Requirement. Used this template to organize the appearance of the document
and its flow.

1.3 Intended Audience and Reading Suggestions

The intended audience of this document would be the patient, doctor and specific employees like
Receptionist, consultants and /Professional Users like System developers, the document would final provide
a clear idea about the system.
 Typical Users, such as patient and doctor, who want to use online health care system for health care
purpose and Receptionist who handles online appointments
 System developers who are interested in working on the project by further developing it
or fix existing bugs

1.4 Product Scope

In today’s world where changes are rapidly performed, human being needs to cope up with those changes to
survive and live better. Everybody is in race with other people for moving ahead and tries to achieve more.in
this race human has ignored one of the important part that is Human life. in such situations healthcare system
comes in. The Health management system is an end user support and online consultation project. Here we
propose a system that allows user to get guidance on their health issues through an online health care system.
The Health management system is an end user support and online consultation project. Here we propose a
system that allows user to get guidance on their health issues through an online health care system. The
system is fed with many symptoms and diseases. The system allow user to share their symptoms and issues
in doctor module when doctor login to the system doctor can view his patient details and the report of that
patient. Doctor can also views his personal details.Admin can add new disease detail by specifying the type
of and symptoms of disease in database. The system will provide proper guidance when the user specifies the
symptoms of his illness.The smart health system focused for optimally reducing the healthcare costs.
Software Requirements Specification for <Project> Page 2

1.5 References
http://docshare01.docshare.tips/files/5973/59736721.pdf

http://groups.umd.umich.edu/cis/course.des/cis375/active/class7/EM-SRS-
ReviewSoftRightHospitalManagementSystemSRS.pdf

https://www.academia.edu/28734143/HOSPITAL_MANAGEMENT_SYSTEM_Software_Requirem
ent_Specification

2. Overall Description
2.1 Product Perspective
In manual procedure it’s hard for people for making appointments, mostly there is less trained staff, which
creates problem for guiding patient and do mistakes in appointments. patients also facing problems in visit as
there are less number of doctors in premises and patient cannot wait or make regular visits. Doctors visits are
inconvenient for far residence and also no service for persons with disability.
The fully functional automated online health care management system which will be developed
through this project will eliminate the disadvantages caused by the manual system by improving the
reliability, efficiency and performance. The usage of a database to store patient, staff and doctor details etc.
will accommodate easy access, retrieval, search . The access limitations provided will enhance the
security of the system. The system will facilitate concurrent access and convenient management of activities
of the medical facilities.

2.2 Product Functions

Registration: When a user opens online forum he have to register himself on the forum. The user’s
information such as name, date of birth, address ,email and telephone number is required. After registration a
unique ID will be assigned to the user.
Treatment: After registration the user search for his disease find specialist and send request to doctor for
treatment. The doctor accepts the request and start treatment.
Report Generation: After observing the patient the doctor give him the prescription and healthcare advice
the system generate the prescription and health care advice report for the user . if the patient needs a proper
checkup doctor asks him for visit.
Appointment: in case of appointment the user ask the online receptionist for making appointment for the
specific doctor. The system generate the report related to appointment contain name and id of patient the
name of specific doctor and day and time of appointment.
Software Requirements Specification for <Project> Page 3

2.3 User Classes and Characteristics

● Admin
Admin has the full access to the system which means he is able to manage any activity with regard to the
system. He is the highest privileged user who can access to the system.
Key functions
o Manage doctor, staff and patient
o Generate reports
o Manage doctors
o Manage staff
o Manage salaries
● doctor
Interacts with the systems most often to supply service to patients
Key functions
o Keep track of patient details
o Keep tract of test details
o Keep track of progress of patients
o Maintain bill details
o Manage his personal details
o Manange prescription generation

 Receptionist
Interacts with the systems most often to supply service to users
Key functions
o Keep track of patient details
o Make ambulance reservations
o Maintain bill details
o Manage Appointments
o Manage report generation

2.4 Operating Environment

Software requirements

● Windows 7 or above operating system

● MySQL server
 be written in C#, using Microsoft Visual Studio 2010
 The program will be GUI-based
Software Requirements Specification for <Project> Page 4

Hardware Requirements

● Core i5 processor

● 4GB Ram

2.5 Design and Implementation Constraints

● System is only accessible to authenticate users.
● Database is password protected.
● Should use less RAM and processing power.
● Each user should have individual ID and password.
● Only administrator can access the whole system

2.6 User Documentation

The application will come with an “About” tab, which will allow users to access the offline and online Help.
This manual will be updated with each new service pack. Other user documentation includes one user
manual for lowest level users, one technical document describing the functionality in detail for use of
technicians, Tasks are listed alphabetically or logically grouped often using cross referenced indexes
which helps the users to know exactly what sort of information they are looking for. one copy of
documentation and link to current source for future contributors

2.7 Assumptions and Dependencies

 Each user must have a valid user id and password
 Server must be running for the system to function
 Users must log in to the system to access any record.
 Only the Administrator can delete record
 The server assumes it will be installed with a high-speed Internet connection to communicate with
users.
 The web version assumes that the user has a computer with an Internet connection and a web
browser to access the online version of online health care management.
Software Requirements Specification for <Project> Page 5

3. External Interface Requirement

3.1 User Interfaces

Login Form

Add Patient:
Software Requirements Specification for <Project> Page 6

Patient Disease/ Symptoms

Doctor Prescription:
Software Requirements Specification for <Project> Page 7

Book Appointment

Admin Work
Software Requirements Specification for <Project> Page 8

3.2 Hardware Interfaces

Laptop/Mobile which have at least 3MB space in storage to install and maintain the application.

Laptop/Desktop PC
o core i5 processor

o 4GB RAM
o 500GB HDD
Purpose of this pc is to give information when Patients ask information about doctors for booking
appointments. To perform such Action it need very efficient computer otherwise due to that reason
patients have to wait for a long time to get what they ask for.

Wi-Fi router
Wi-Fi router is used to for internetwork operations inside of a clinic and simply data transmission from
pc’s to sever.

3.3 Software Interfaces

From Developing end JDK 1.8 – Java language is used for handling data because it is fast, secure, and
reliable. NetBeans 8.1 - IDE used for Designing user interface with standard Windows API and GUI. Data
that will be shared between computers and instance of the software being run will be pushed and pulled
from the patient database as needed/requested.

Software will include standard TCP/IP interfaces with network devices, and software drivers for USB
devices. The database will be accessed through standard SQL scripts, which will be native to the system and
included as packages.

3.4 Communications Interfaces

Communication interfaces will use TCP/IP for data transmission and SMTP/HTTP for generating
emails of reports from the software.
Ubiquitous used for data transmission. its easy to set up and easy to use. Low cost and high data
transmission rates. All offline and online access will be monitored, for transparency purposes, and in order
to reduce abuse and unauthorized access of the system.
Software Requirements Specification for <Project> Page 9

4. System Features
4.1 Use Case Diagram

Description and Priority

The online health care management system is maintain information about doctors and patients.
Firstly, Patient and doctor must login in order to use the software. Patient can send request to the
doctor and communicate with the doctor and told him about disease or symptoms. The doctor can
accept the request and after chat with patient he send prescription. A doctor also edit his personal
information. If the doctor suggest, patient can send request for booking appointments. The
receptionist allot appointment time.
Software Requirements Specification for <Project> Page 10

Of course, this project has a high priority because it is very difficult to manage each patient , doctor
record and their appointments. It also keep track their prescription.
Stimulus/response Sequences

 Patient request for login the system, and searches for doctors.
 Displays a detailed list of available doctors and can make an appointment if needed.
 Doctors login the system and check patients detail and give them prescription or health
advice.
Functional Requirements
 System shall allow front-desk staff to add new patients and doctors to the system.
 The administrative staff shall be allowed to delete the patient and doctor account from the
system.
 The system show patients record about the following information: patient’s name, diseases
or symptoms and the doctor’s name which was assigned. It also displays doctor prescription.
The system shall allow the user to update any of the doctor/patient’s information

5. Other Nonfunctional Requirements

5.1 Performance Requirements

 Response time-The system will give responses within 1 second after checking the patient
information and other information.
 Capacity-The system must support 1000 people at a time
 User interface- User interface screen will response within 5 seconds.
 Conformity –The system must conform to the Microsoft accessibility
5.2 Safety Requirements
If there is extensive damage to a wide portion of the database due to catastrophic failure, such as
a disk crash, the recovery method restores a past copy of the database that was backed up to
archival storage and reconstructs a more current state by reapplying or redoing the operations of
committed transactions from the backed up log, up to the time of failure.

5.3 Security Requirements

All the administrative and data entry operators have unique logins so system can understand who is
login in to system right now no intruders allowed except system administrative nobody cannot
change record and valuable data.

5.4 Software Quality Attributes

AVAILABILITY: The system shall be available all the time.
CORRECTNESS: A bug free software which fulfill the correct need/requirements of the patients
Software Requirements Specification for <Project> Page 11

MAINTAINABILITY: The ability to maintain ,modify information and update fix problems of the
system
USABILITY: software can be used again and again without distortion.
ACCESSIBILITY: Administrator and many other users can access the system but the access level is
controlled for each user according to their work scope.
ACCURACY: The reliability on the information/output. Can depend/be sure of the outcome.
STABILITY: The system output won’t change time to time. Same output will be given always for a
given input.
5.5 Business Rules
Want take the responsibility of failures due to hardware malfunctioning.
Warranty period of maintaining the software would be one year.
Additional payments will be analysed and charged for further maintenance
If any error occur due to a user’s improper use. Warranty will not be allocated to it.
No money back returns for the software.
Trust bond placement should be done before designing and coding. An advance or an Agreement.

Other Requirements
A degraded mode of operation should be possible in which each system can operate independently
of central scheduling. The software shall have failure and error recognition codes acting as a safety
net, thus keeping the software from performing any major catastrophic functions.

Appendix A: Glossary

Report - an account of patients

Front-desk staff - administrative staff that work at reception desk
Web-based application - an application that runs on the Internet
MySQL - a query language to interrogate the system
GUI - Graphical User Interface
Database - A Big memory address block which contains large set of data.
Intranet - A network that is local to a geographical location or particular institution’s network
Windows API - Windows Application Programming Interface
TCP/IP –
a) Transfer Control Protocol/Internet Protocol - A protocol for transferring data to/from the
internet
b) Internet Protocol - A protocol for allowing computers/devices with this to connect to the
internet
Software Requirements Specification for <Project> Page 12

HTTP – Hyper Text transfer protocol

JDK – Java Development Kit , used for java programming language
NetBeans- It is an open-source integrated development environment (IDE) for developing with
Java,