BAHHAUDDIN ZAKARIYA UNIVERSITY (LAHORE CAMPUS)

Advance Software
Engineering
A Report on Hospital Management System
Arslan Hamid
MSCS14F005
4/10/2015

Hospital Management System

1. Project Description:
This is a software system that integrates various factors needed for smooth
working and management of a hospital. The main objectives of the system is
which shows and help us to collect most of the information about Hospitality and
Medical services, the system is very simple in design and to implement it. At
the same time, the correct use of it will reduce system complexity and improve
software development efficiency and compactness.
The project is developed to eliminate human efforts in managing hospital
records and data manually. It includes registration of patients storing their
details into the system. It also maintains all doctors/Staff/Nurse information
working in the hospital. Hospital Management System enables you to develop
your organization and improve its effectiveness and quality of work.

2. Functional Requirements:
i.
ii.
iii.
iv.
v.
vi.
vii.
viii.
ix.
x.
xi.
xii.
xiii.
xiv.
xv.

Patient takes appointment.

Patient gets registered by the receptionist.
Patient meets the doctor for checkup.
Doctor reviews the health of patient.
Doctor gives prescription to the patient.
Performing operations.
Beds/Wards Allotment.
Payment of bills.
Ward wise bed status.
Monitoring of Patients health all the time.
Maintenance of all beds and rooms of hospital.
Patients Information.
Receptionist login to view the appointments status and admin login to
view and update all the records.
Edit Doctor/Staff/Nurse Information.(Add, Delete, Edit)
Admission and Discharge reports.

xvi.
xvii.

Patients payment and billing information.

Salaries distribution of Doctors/Staff/Nurses.

3. Actors:
i.
ii.
iii.
iv.
v.
vi.

Receptionist
Patient
Doctor
Nurse
Staff
Admin

4. Design Goals(Non-functional Requirements):

i.

Planned approach towards working:

The working in the organization will be well planned and organized. The data
of patients, doctors, nurses and all staff will be stored properly, which will
help in retrieval of information.

ii.

Accuracy:

iii.

Reliability:

iv.

Efficiency:

The level of accuracy in the proposed system will be higher.

The reliability of the proposed system will also be higher.

The project should be efficient so that whenever a new patient is admitted, a

bed is assigned and also a doctor is assigned to the patient according to the
patients disease.

v.

No Redundancy:

vi.

Easy to Operate:

vii.

In the proposed system utmost care would be that no information is repeated

anywhere, in storage or otherwise.

The system should be easy to operate and should be such that it can be
developed within a short period of time and fit in the limited budget of the
user.

User Friendly:

The proposed system aims at providing a user friendly system with the user
doing the least work and the system providing all the related information for
updating.

5. Use Case Diagram:

6. Complexities of System Design:

1. System Decomposition:
I.

Layers:

Interface Layer
End User

Patient, Doctor, Nurse, Staff, Admin

Middleware Layer
Authentication Login

Patient data management, Staff,Doctors

Data Managment, Reporting managment

Data base Layer

Patient Data Stored

II.

Staff, Doctors, Nurse Data

Stored

Billing data and other

reporting data stored

Coupling:
Coupling is defined as the degree of interdependence between two or more
classes, modules, or components. Low or minimize coupling between
modules is a better option in software design as modules dont need to know
much about one another to interact and it will make future change easier in
our system. As in our hospital management system the doctor, nurse and
patient do not the login module which is a low coupling.

III.

Cohesion:
Cohesion is defined as the degree to which all elements of a module, class, or
component work together as a functional unit. High cohesion is good, and
low cohesion is bad. In our case admin login and receptionist login are two
modules which work together to view the records or reports and they have
high cohesion.

2. Concurrency:
The system supports multiple concurrent users which can execute
simultaneously and interacts with each other. Like in this system patient and
receptionist can execute simultaneously and interact with each other similarly
receptionist and admin can execute simultaneously for login purpose.

3. Hardware/Software Mapping:
I.

Connectivity:
In Hardware/Software mapping we are concerned with connectivity of our
system which can be physical connectivity and logical connectivity of the
system.

4. Data Management:
Data management is a really important factor in our design like the data and
records of patient treatments, medicines given to patients all this data
needed to be maintained. Similarly data of doctors, nurse or staff is also
stored and maintained in our data base. Likewise file management of files
like reports that are being generated after the inspection of patients will also
be stored.

5. Global Resource Handling:

I.

Security:
Security is the main criteria for the proposed system. Since illegal access
may corrupt the database. So security has to be given in this project. The
entire System shall be deemed to be running within a corporate firewalled
environment.

6. Boundary Condition:
Boundary conditions are based on initialization, termination and failures of
our system. The system is 1st brought from a non-initialized state to a steady
state, then Resources are cleaned up and other systems are notified upon
termination.

Good system design anticipates fatal failures and provides mechanisms to

deal with them because possible failures in our system like bugs, errors, and
other external problems can harm our system which we have to deal with.

7. Overall System Architecture High Level:

The system is divided into two layers:
1. Business Services Layer contains the business components of the system
which comprise the business logic of the application.
2. Framework Services Layer contains the services that the business layer
needs. These are common functions like security, email notification etc. that are
needed by all other business module.

System Architecture
Business Service Layer

Hospital
Management

Patient
Registration
Management

Staff
Management

Patient
Admission
Management

Accounts
Management

Reports/Files
Management

Framework Services Layer

Logging

Security

System
Administration

Business Service Layer

Patient
Registration
Management

Inpatient
Registration
Outpatient
Registration

Appointment
Scheduling
(Patient/Doctor)
Patient
Admission
Management

Admission
Granted
Admission
Rejected

Hospital
Managem
ent

Patient Bed
Allotment/Mgmt.

Billing and
Receipt
Accounts
Management

Insurance and
Sponsors
Payments

Staff
Management

Staff
Attendance
Assigning
Duties to Staff
etc

Records/Report
s/Files
Management

Reports Results
of Patients
Medical Record
Files

Beds/Ward
s
Maintenanc
e

Framework Services Layer:

1. Logging
This component logs information about user accesses, transactions. All other
components will log their information through this component. It will also
provide customize logging facilities.
2. Security
This component will handle all security related issues of system. It will provide
authentication, and authority management.
3. System Administration
System Administration component will provide user management.

8. Architecture Styles:
An architectural style also called architecture patterns is a particular
pattern that focuses on the large-scale of a system. An architectural
style is constrained by a particular principle of how to build systems
how components are organized, how data is manipulated, how
components communicate. E.g. a hierarchy of components, sequential
processing of data, asynchronous communication.
There are many architecture styles such as:

Client/Server
Peer-To-Peer
Layered Architecture
N-Tier / 3-Tier
Pipes and Filters
Object-Oriented

In this project the architecture styles that is used is known as Layered architecture
in which it partitions the concerned application into stacked groups (layers) like
interface layer, middleware layer and database layer which is already explained
above.