Hospital Management System
EXERCISE 1: SOFTWARE REQUIREMENT SPECIFICATION
OBJECTIVE:
To design a software requirement specification for the Hospital Management System.
INTRODUCTION:
The motivation behind developing the Hospital Management System (HMS) stems from the
need to streamline healthcare services, enhance patient care, and improve hospital
operational efficiency. Traditional hospital management methods involve cumbersome
paperwork, manual record-keeping, and delays in retrieving patient information. An
advanced digital solution can alleviate these issues by integrating patient records, doctor
schedules, billing, pharmacy, and diagnostics into a unified system.
PROBLEM STATEMENT:
Modern hospitals face challenges such as inefficient patient record management, time-
consuming administrative processes, and lack of real-time doctor-patient coordination.
Without a proper system, scheduling appointments, handling medical records, and
managing billing operations can become chaotic. A well-integrated Hospital Management
System is essential for ensuring smooth operations and better healthcare services.
OBJECTIVES:
The primary objective of this project is to develop a Hospital Management System that
automates hospital workflows, improves patient data handling, and enhances
communication between doctors, staff, and patients. The application will provide modules
for patient registration, doctor scheduling, medical record maintenance, billing, pharmacy
management, and laboratory diagnostics.
SYSTEM DESIGN
The system is structured to provide a user-friendly interface with seamless integration
across various hospital departments. The architecture follows a microservices model where
each service (patient management, appointment scheduling, billing, pharmacy, and
diagnostics) operates independently but communicates efficiently.
SYSTEM TESTING
Testing will include functional and non-functional tests to validate different modules:
Functional Testing: Registration, login, appointment booking, billing, and report generation
Non-functional Testing: Load testing to ensure system performance under peak hospital
hours
EXERCISE 2: CLASS DIAGRAM
OBJECTIVE:
To create a class diagram for the Hospital Management System, identifying key entities and
their relationships.
PROBLEM STATEMENT:
The class diagram represents the static structure of the system, including key entities like
Patient, Doctor, Appointment, Billing, Pharmacy, and Diagnostic Report. These classes
interact to manage hospital workflows efficiently.
RELATIONSHIPS:
- Inheritance: Specialist doctors inherit attributes from the general Doctor class.
- Association: Patients are associated with doctors through appointments.
- Composition: A billing entry is composed of multiple service charges and medicine
purchases.
- Aggregation: A hospital consists of multiple departments, each with its own facilities.
EXERCISE 3: USE CASE DIAGRAM
OBJECTIVE:
To create a use case diagram for the Hospital Management System, identifying user roles
and interactions.
PROBLEM STATEMENT:
The Use Case Diagram illustrates system functionalities such as patient registration,
appointment booking, medical record access, pharmacy management, and billing. The
diagram captures interactions between users, including patients, doctors, administrators,
and pharmacists.
BENEFITS OF USE CASE DIAGRAM:
- Provides a clear overview of system functionalities.
- Helps in understanding user interactions with the system.
- Facilitates system design and validation.
