1 Software Requirement Specification Document

Table of Contents
Executive Summary…………………………………………………………………………………………………………………..2
1. Introduction………………..…...………………………………………………………………………………………………….2
1.1 Purpose……………………………………………………………………………………………………………………………2
1.2 Scope of Project……………………………………………………………………………………………………………….3
1.3 Glossary of term use………………………………………………………………………………………………………..3
1.4 Definitions, Acronyms and Abbreviation………………………………………………………………………….3
1.5 References……………………………………………………………………………………………………………………….3
2. Overall Description……………………………………………………………………………………………………………..3
2.1 Product Perspective…………………………………………………………………………………………………………3
2.2 Product Functionalities…………………………………………………………………………………………………….4
2.3 Actors in HMS…………………………………………………………………………………………………………………..4
2.4 Hardware Interface ..………………………………………………………………………………………………………..4
2.5 Software Interface…………………………………………………………………………………………………………….4
2.6 Design and Implementation Constraint…………………………………………………………………………….4
2.7 User Documentation………………………………………………………………………………………………………..4
2.8 Assumption and Dependencies………………………………………………………………………………………..5
3. User Requirement……………………………………………………………………………………………………………….5
3.1 R1:Registration………………………………………………………………………………………………………………..5
3.2 R2:Attendance…………………………………………………………………………………………………………………5
3.3 R3:Room Allotment……………………………………………….………………………………………………………..5
3.4 R4: Generate Report……………………………………………………………………………………………………….5
4. Non Functional Requirements…………………………………………………………………………………………….6
4.1 Performance…………………………………………………………………………………………………………………..6
4.1.1 Response Time…………………………………………………………………………………………………………….6
4.1.2 Capacity……………………………………………………………………………………………………………………….6
4.1.3 User Interface……………………………………………………………………………………………………………..6
4.2 Safety Requirement………………………………………………………...................................................6
4.3 Security Requirement……………………………………………………………………………………………………..6
4.4 Software Quality Attributes……………………………………………………………………………………………..6
4.4.1 Availability……………………………………………………………………………………………………………..6
4.4.2 Correctness…………………………………………………………………………………………………………….6
4.4.3 Usability………………………………………………………………………………………………………………….6
4.4.4 Accessibility…………………………………………………………………………………………………………….6
5. Use-Case Diagram………………………………………………………………………………………………………….…7
6. System Scenario…………………………………………………………………………………………………………….…8
 2 Software Requirement Specification Document

Software Requirements
Specification

Hospital Management System

Desktop Application
Executive Summary
It is very significant for the hospital to keep track to every activities of hospital such
as record of every ward boy, nurses, doctors, and in-out of ever patient is compulsory for smoothly working
of every activity in the whole hospital.

On the other side keeping track of the whole hospital management with paper work is too much time
consuming, difficult, and cause such type of problems/errors which can create some serious problem in
future. From the past years population increases day by day and this directly effects that number of patient
visiting hospitals also increases. So, it is very difficult to maintain record of every patient accuracy.
Economically it is not suitable and feasible to maintain record of every patient on paper. So, keep the
working of such paper work for this management system we create an application names as “Hospital
Management System”. The main purpose of our project is to minimize the paper work up to 90%.

1. Introduction
Hospital Management system is use to manage all the records of patient in-
out, record of every doctor, nurse, ward boy is can be easily managed by using this application. This
application can minimize the use of paper work and also minimize errors of every management activity
in hospital.
1.1 Purpose
➢ This application is use to automate the maximum activities in the hospital.
➢ Basic purpose of this software is use to maintain record of every patient such as date of
coming and discharging, room fee, and other charges is stored in the database.
 3 Software Requirement Specification Document

➢ There are two level of this software.

• Management level
• User/Patient level.
➢ Providing the result of all the tests of patient accuracy and no time dely.
1.2. Scope of Project
The proposed system of library management system is used to give record from patient and
store this record at database system for future use.
This system can save a lot of time for maintaining every record and activity of every patient.
The current system is a paper-based system. It is a very slow system and if we want to update
record of any patient or doctor it requires reasonable time frame and too much effort to update this
record on paper database.
1.3. Glossary of Terms use
Database: This term is use to store data of every patient, Doctors, Ward boy, nurses in one
central place in the system.
SQL: This term is use for Structured Query Language.
Java: It is computer language.
1.4. Definitions, Acronyms and Abbreviations
IDE: Integrated Development Environment
GUI: Graphical User Interface
SQL: Structured Query Language
SRS: Software Requirement Specification.
HMS: Hospital Management System
1.5. References
1. Java the complete reference by Herbert Schildt.
2. Java how to program by Paul Deitel & Harvey Deitel.
3. Database Management System(Slides ppt) by Sir Waqar Ahmad.

2. Overall Description

2.1. Product Perspective

This software will be self-contained and fully based on windows. Also many stakeholder get involve in
HMS.
 4 Software Requirement Specification Document

2.2. Product Functionalities

Registration: When the patient is admitted to the hospital the admin officer first check he/she
already register or not by using the patient’s CNIC number. If he/she not register then register the patient
by giving some basic information from the patient. After registration assign the patient ID to the patient.
Patient discharge: After the patient check out calculate the total charges of patient and include the
bed number into available bed list in the hospital.
Date/Time: Date and time of every activity should be updated in every activity that is occur in HMS.

2.3. Actors in HMS

• Staff/Nurses
• Record System
• Doctors
• Information System

2.4. Hardware Interface

Processor: Core i5
RAM:4 GB
Hard disk :40GB or above
Input devices: Keyboard, Mouse
Output devices: Printer, LCD/Monitor

2.5. Software Interface

Operating System: Windows 10
Front End: Java
Back End: Microsoft SQL server management Studio

2.6. Design and Implementation Constraints

✓ This application is only accessible within the hospital only.
✓ Database is protected by strong password.
✓ Should use small size ram with high processing power.
✓ Every user has their own ID and password.
✓ Only admin of Hospital can access the whole system

2.7. User Documentation

User documentation includes the full description about the handling of application and
complete steps to install this application to the system easily. User can easily use this application
without any trouble. Email dress of developer also available in user manual to contact with us if
need.
 5 Software Requirement Specification Document

2.8. Assumptions and Dependencies

➢ User must have valid password and email/ID to login for this application.
➢ Server must be running successfully for fast working with HMs.
➢ To access any record user must be login with data.
➢ Only the admin of that application can delete any record of any person.

3. User Requirement

3.1 R1:Registration
Before appointment patient is firstly register by reception staff. If the patient is already register
with that hospital then login by past patient id. If the patient is first time visit the hospital then
register with all the given information which is require for registration. After registration the
patient with hospital assign the patient id to the patient it helps for appointment, timing, patient
discharge date, and give the respective medicine to respective patient and also help to avoid any
serious problem. So registration is a main subsystem for using this Hospital Management System
Successfully.

3.2 R2: Attendance

Data entry operator enter the exact attendance of all the employs that is currently working in
the hospital. This actor can also approve the leave of every employ. This subsystem also enter
the exact time of employ’s job starting time. This subsystem creates a daily worksheet of employs
attendance.

3.3 R3: Room Allotment

This subsystem gives information about the available rooms and beds from the database. If the
any patient is discharge from the hospital then the room and bed of that patient is updated and
this room number is added into the available room database.
3.4 R4: Generate report
User always want to create an updated report of patient for better treatment so this subsystem
allows admin to create reports of every patient for better treatment.
 6 Software Requirement Specification Document

4. Non-Functional Requirement

4.1. Performance
4.1.1. Response time
The response back time of system is within 1 or 2 seconds.
4.1.2. Capacity
The application or system should must be handled minimum 500 people at a time without
any server error.
4.1.3 User-Interface
The response time of user interface is must be 5-10 seconds.

4.2. Safety Requirements

If the database system is damage due to some physical issue then the data can also be
recover with the backup database.

4.3. Security Requirements

The security of the whole management must be high so only admin of this system can edit,
delete, and view the full record of application. System know who is login an admin or reception
officer.

4.4. Software Quality Attributes

4.4.1. Availability
The system must be available 24/7 when admin need it.
4.4.2. Correctness
The software is fully bug free to fulfill the requirement of the user.
4.4.3. Usability
The software is use many time when admin need it without any error or
distortion.
4.4.4. Accessibility
This software can be access by admin and other user but the accessibility level is
different for every user.
7 Software Requirement Specification Document

5. Use Case Diagram

 8 Software Requirement Specification Document

6. System Scenarios
Name Add Patient Entry

Description This function give information from

the patient and assign patient ID
number.
Actors Data Entry operator, Receptionist
Employ.
Pre-Condition At first the operator first login from this
system.
Flow of every event 1. Firstly, user of the system select “add
entry of patient ” from front page.
2. After this patient entry registration
form display.
3. Enter the require data of patient to
fill the form completely.
4. Then click on “add entry”
5. ”Patient entry added Successfully”
Message displayed.
6. System automatically create Patient
ID.
Post-Condition Patient record added to the patient
file.
9 Software Requirement Specification Document

Name Add prescription entry

Description This main function is to record

prescription detail of patient accuracy
Actors Data Entry Operator

Pre-Condition The Prescription chit must be issued by

the doctor to the patient.
Flow of every event 1. At first user select “Prescription form”
from the Patient module.
2. System force the user to enter Patient ID
at first.
3. User Enter the registration number of
system.
4. Prescription form display the relevant data
about the patient detail and patient disease.
5. User move to “test” option and select the
detail of previous test.
6. User move to medicine field and enter the
medicine detail of patient accuracy.
7. User Select “Add Prescription” from the
option.
8. After this user click on Print button to print
the prescription detail.
10 Software Requirement Specification Document

Name Calculate bill

Description This function is used to calculate the

total payment of the patient include
medicine charges, room fee and test
fee.
Actors Cashier, Receptionist employ

Pre-Condition Patient of the hospital must be register

to that system(HMS).
Flow of every event 1.User select the patient button option
2. System force the user to enter ID
number.
3.User enter ID number.
4.System force the user to date and
time for which user require total bill of
that patient.
5. User enter data and time.
6.Reciept form display with full detail
and relevant charges.
7. User click on print to print the
Receipt.
Post-Condition Detail of every payment and other fee
should updated in payment file.
11 Software Requirement Specification Document

Name Attendance of employees

Description This function is used to mark the

attendance of every worker and all
other employ regularly without any
time delay.
Actors Data Entry Operator

Pre-Condition User must be login with user account.

Flow of every event 1.User first select” Employ

Attendance” option.
2. User of the system enter date.
3. User enter the ID of employe that
employ that should not attend at
particular date.
4. User select “Update attendance”
5. System display message “ Are you
sure to want to update more record ?”
6. If no then user select “No”.
12 Software Requirement Specification Document

Name Calculate Salary of employees

Description This function is used to calculate the

salary of employees according to the
attendance.
Actors Account officer

Pre-Condition User of system must be login with

relevant user account
Flow of every event 1.Firstly user should click on “Employee
salary”
2.System force the user to enter
employee ID and time period.
3.User enter the full data about
Employee.
4. User select calculate salary.
5. The total salary of employee is
generated by the application and
displayed.
6. Then the user click on “Print”
button.

Post-Condition The payment file of the system must be

updated with payment
13 Software Requirement Specification Document

Name Schedule consoling

Description This function is used to manage the

charges detail of counsolors.
Actors Accountant

Pre-Condition User of system must be login with

relevant user account
Flow of every event 1. Use should select counseling doctor
form from the employee subsystem.
2. System ask the user to enter doctor
id.
3. User enter doctor id.
4.System should show the whole detail
of doctor.
5. User should select visiting hours
button.
6.select calculate counselor charges.
7.now the system assign to be paired
with that counselor.

Name Search for ambulance

Description This function is used to check the

available ambulance in the hospital.
Actors Receptionist

Pre-Condition User must login to the system.

Availability form of ambulance also
available.
Flow of every event 1.Click on ambulance management
system module.
2. Select search button.
14 Software Requirement Specification Document

3.System prompt the user to search by

Ambulance NO, or Ambulance list.
4.Select search by Ambulance list.
5.Enter the ID of ambulance.
6.System display the availability of that
Ambulance.

Name Generate lab report

Description This function is used to generate the

reports of tests and print the test
reports.
Actors Lab assistance

Pre-Condition The result of relevant lab test must be

available.
Flow of every event 1.User select lab report form from the
module of lab test subsystem.
2.System ask the user to enter patient
id.
3. User enter patient id.
4.Now system display the detail of
patient.
5. System ask the user to enter the
category of tests.
6.User of the system select category
and enter the test result.
7.User select add test record button.
8. System display Message
“Successfully add”.
9.User click on print button to print the
result of lab report.
15 Software Requirement Specification Document