SOFTWARE REQUIREMENT SPECIFICATION

ON
GOODHEALTH HOSPITAL MANAGEMENT SYSTEM

Prepared by:
Shyam Narayan Gupta

TABLE OF CONTENTS

ER Diagram for the Hospital Management System

1. INTRODUCTION

1.1. Current System

1.2. Envisioned System
1.3. Scope

2. OVERALL DESCRIPTION

2.1. Functional Requirements

2.2. Non-Functional Requirements
2.3. Hardware
2.4. Software

3. UML DIAGRAMS

3.1. Use case diagram

3.2. Class diagram
3.3. Object diagram
3.4. Sequence diagram
3.5. Activity diagram
3.6. Component diagram

4. TEST CASE

5. E-R DIAGRAM AND NORMALIZATION

1.3. Scope:
This application will enable the Desk Officers to check the availability of the
doctor, register the patients and generate bills of outpatients according to the
services utilized by them.

ER Diagram for the Hospital Management System

Will facilitate administrators to modify, create and delete the doctor’s and
medicines information available.

2. OVERALL DESCRIPTION

ER Diagram for the Hospital Management System

2.1. Functional Requirements:

LOGIN PAGE:

 Name: Login page

 Description: Displays a user interface for logging onto the system.

 Actors: Administrators and Desk Officers

 Functions available:

a. Logon: Fires the logon routine with the user name and password,
assigns the required rights, and updates the relevant session
variables.
b. Exit: Closes the web page.

 Preconditions: Administrator/Desk Officer enters the correct username

and password.

 Post conditions: After entering correct username and password, it

shows relevant page.

 Non-functional requirements: The software system should not take

more time for logging the page.

ADMINISTRATION PAGES:

 Name: Medical Staff

 Description: Displays a user interface to maintain the list of doctors and

allows the addition/deletion/modification of data for medical staff.
Medical staff can include doctors, junior/resident doctors, nurses, ward
boys/assistants.

 Actors: Administrators

 Functions available:

a. ListAll: List all medical staff grouped by type.

b. Search: Allows searching for a medical staff by name.

ER Diagram for the Hospital Management System

 c. Add a New Staff Member: Allows addition of a new staff member.
d. Delete a Staff Member: Deletes a staff member from the database.
e. Edit Staff Member Details: Edits a staff member details.

 Preconditions: Administrations would get a list of medical staff.

 Post conditions: According to the requirement the administrator can
add, edit or delete the list.

 Non-functional requirements: The software system should not take

more time to load the list of medical staff.

 Name: Pharmacy

 Description: Displays a list of medicines in the pharmacy.

 Actors: Administrators

 Functions available:

a. ListAll: List all the medicines offered by the laboratory.

b. Add a New Medicine: Add a new medicine to the pharmacy.
c. Delete an Existing Medicine: Deletes an existing medicine from
the pharmacy
d. Modify Medicine Details: Allows modification of a medicine in
the pharmacy.

 Preconditions: Administrations would get a list of medical staff.

 Post conditions: According to the requirement the administrator can
add, edit or delete the list.

 Non-functional requirements: The software system should not take

more time to load the list of medical staff.

DESK OFFICER PAGES:

 Name: Outpatient

 Description: Provides various functions for an out-patient.

 Actors: Desk Officer

ER Diagram for the Hospital Management System

  Functions available:

a. Availability: Check the availability of a doctor on a particular

and of a specific type(like dentist/child specialist)
b. Register: Register the out-patients by taking the required details.
c. Visit: Creates an appointment with a doctor.
d. Search: Search the patient id if the existing patient fails to
provide the patient id.
e. Pharmacy: List the medicines that can be purchased by an
out- patient.
e. Billing: Generates a bill for a patient according to the medicines
purchased by him and doctor’s fee.

 Preconditions: Desk officer can check the availability of the doctor.

 Post conditions: Would register the patients and provide them the
unique patient id and appointment number.
 Non-functional requirements: The software system should not take
more time to load the list of medicines that can be purchased by an out-
patient.

2.2.Non-Functional Requirements:

 Performance:

 The response time of the application for the user(i.e., for the
administrator or the desk officer) should not be more than a minute.

 Security:

 The system would not allow any sort of unauthorized access attempts by
machine ID, user ID, date, and time.
 Systems with data element level security access are preferred.

 The system will include a fully functional, fully operational security

component to monitor access to the system, tables, files and databases.

ER Diagram for the Hospital Management System

2.3.Hardware Requirements:

 Network :
HP/Compaq Intel-based Server or NT/2000 – HP/Compaq Intel-
based Server.
 Workstations:
At a minimum, the system will function within the parameters of
the all Desktop configuration(s) Pentium 4, 3.2GHz, 512 MB RAM.

2.4. Software Requirements:

Operating system : Windows XP

Back end : Microsoft SQL Server 2005
Front end : NetBeans IDE 6.1
Browser : Internet explorer

ER Diagram for the Hospital Management System

 3. UML DIAGRAMS

3.1. Use case diagrams:

Use case for administrator:

ER Diagram for the Hospital Management System

Use case for Desk officer:

ER Diagram for the Hospital Management System

3.2.Class diagrams:

Class diagram of administrator:

ER Diagram for the Hospital Management System

Class diagram of Desk officer:

ER Diagram for the Hospital Management System

 4. TEST CASE

Test case for administrator:

S.NO TEST CASE ACTUAL TEST RESULT EXPECTED TEST

RESULT
1. Login: Administrators with a user Valid Username & password Will lead the
name and password will access the administrators to their
site. personal page.

Invalid Login Will get an error message

(Either invalid username, That the login is
invalid password or both unsuccessful and will ask
invalid username and invalid to enter it again.
password)

2. Clicking “Doctors and staff” tab Administrator moves to List all doctor’s and staff
doctors and staff tab details which allows
addition, deletion and
modification.

3. Clicking “Medicines” tab Administrator moves to Lists all Medicines

Medicines page. details which allows
administrator to add,
delete and edit the
medicines details.

Test case for Desk Officer:

S.NO TEST CASE ACTUAL TEST RESULT EXPECTED TEST

RESULT
1 Login ID: Only Desk Officer Valid Login ID Will be allowed to access
with a login ID and password the site.
can enter

Invalid Login ID Message to be displayed

(Either invalid username, Invalid username.
invalid password or both

ER Diagram for the Hospital Management System

 invalid username and invalid
password)

2. Desk Officer takes patient Enters the patient id. If Generates appointment
id(unique code) from the Unique Code is valid. number depending on the
existing patients. availability of the doctor
and type of doctor selected.

3. Desk Officer registers the patient Enters the name, age, height If all the details are entered
if he/she is a new patient. and other details. with out any errors the
application should generate
a unique patient id number.
Also, the patients are given
the appointment number
depending upon the
availability of the doctor
and type of doctor selected.

Patient Value
Time Zone

Code Location Normal Range Service Availed

Name
Site Address
Emergency Contact
HasReport
a {1:n}
Working Hours
Avails{1:n Type (Doctor/Junior Has a[1:N]
Doctor?Nurse)
In patient visit Charges
Code

ER Diagram for the Hospital Management

Patient LabSystem Description

Login Name
 Time Zone

Visits[1:1] Avail [1:n]

Charges
Is Raised By {1:1} Avail [1:n]

Paid By{1:n}

Pharmacy
Medicine

Is Raised By[1:n}
Admitted To{1:1}

Paid By{1:n}
Code
An Assigned To[1:n]
Description
Wards
Daily Charges

Belong To[1:n]

Type (Doctor/Junior
Doctor?Nurse)

S.NO TOPIC DATE TEAM MEMBERS

1.  INTRODUCTION
 Existing System 19-10-2009 Shyam Narayan Gupta
 Proposed System
 Scope

ER Diagram for the Hospital Management System

2.  OVERALL DESCRIPTION
 Functional requirements
 Non-Functional 21-10-2009
requirements
 Hardware
 Software

3.  UML DIAGRAMS
 Use case Diagram
 Class Diagram 21-10-2009
 Object Diagram to
 Sequence Diagram 25-10-2009
 Activity Diagram
 Component Diagram

4.  TEST CASE 26-10-2009

5.  E-R DIAGRAM 28-10-2009

ER Diagram for the Hospital Management System