Welcome To
SOFTWARE REQUIREMENTS SPECIFICATION (SRS) OF
HOSPITAL MANAGEMENT SYSTEM PROJECT
POWERPOINT SALID
North Western University , Khulna
software requirements specification (SRS)
On
Hospital Management System Project
Course Title : Software Engineering Laboratory
Course Code :CSE-3104
SUBMITTED BY SUBMITTED TO
NAME :MD . KHAIRUZZAMAN NAME:TAJUL ISLAM
ID :20221086010 DESIGNATION:ASSISTANT PROFESSOR
DEPARTMENT:COMPUTER SCIENCE AND ENGINEERING [Link] COMPUTER SCIENCE AND ENGINEERING
SEMESTER:3.1 NORTH WESTERN UNIVERSITY,KHULNA
SUBMITTED BY
SUBMITTED TO
A Software Requirements Specification (SRS) document for a
Hospital Management System (HMS) outlines the
requirements and design specifications for the software,
serving as a reference for the development team. Below is a
basic outline of an SRS document for a Hospital Management
System project, assuming the system will be developed using
Java in NetBeans IDE.
Software Requirements Specification (SRS) for
Hospital Management System
[Link]
1.1 Purpose
The purpose of this document is to outline the requirements
for a Hospital Management System (HMS). The system is
designed to improve hospital administration by automating
processes such as patient management, doctor scheduling,
billing, and medical records.
1.2 Scope
The HMS will manage the hospital's core operations, including
patient registration, appointment scheduling, inpatient and
outpatient records, billing, and inventory management. It will
be used by doctors, nurses, administrative staff, and patients.
1.3 Definitions, Acronyms, and Abbreviations
HMS: Hospital Management System
UI: User Interface
Admin: Administrative user with full system privileges
1.4 References
Java Development Documentation
NetBeans IDE Documentation
MySQL Database Documentation (if using MySQL)
2. Overall Description
2.1 Product Perspective
The HMS will be a standalone application running on local servers, with a
client-server architecture. The system will have modules for different
functionalities such as patient registration, appointment management,
billing, and inventory tracking.
2.2 Product Functions
[Link] Management: Registration, medical history, and records.
[Link] Scheduling: Schedule appointments for doctors.
[Link]: Generate and manage patient bills.
[Link] Management: Track medical supplies.
[Link]: Generate reports for administrative use.
[Link] Management: Manage different user roles and permissions.
2.3 User Classes and Characteristics
[Link]: Full access to all modules.
[Link]: Access to patient records and appointment management.
[Link]/Medical Staff: Limited access to patient records.
[Link]: Access to patient registration and billing.
[Link]: Limited access to their own records and appointment scheduling.
2.4 Operating Environment
Software: Java (JDK 8 or higher), NetBeans IDE, MySQL (if
using for database)
Hardware: PC with minimum 4 GB RAM, 500 GB HDD
2.5 Design and Implementation Constraints
The system must be built using Java and NetBeans IDE.
It should support integration with MySQL or any relational
database.
It must adhere to data protection and privacy standards.
2.6 User Documentation
User manuals and help files will be provided for different user
roles.
2.7 Assumptions and Dependencies
The system will be deployed on a local server.
Users are familiar with basic computer operations.
3. Specific Requirements
3.1 Functional Requirements
3.1.1 Patient Management
Register a new patient.
Update patient details.
View and search for patient records.
3.1.2 Appointment Management
Schedule an appointment with a doctor.
Update or cancel an appointment.
Send reminders to patients.
3.1.3 Billing Module
Generate bills for inpatient and outpatient services.
Process payments.
Maintain payment history.
3.1.4 User Management
Add, edit, or remove users.
Assign roles and permissions.
3.1.5 Inventory Management
Add and track inventory items.
Set alerts for low-stock items.
3.1.6 Reporting Module
Generate reports on patient visits, billing, and
inventory.
3.2 Non-Functional Requirements
3.2.1 Performance Requirements
The system should handle at least 100 concurrent users.
3.2.2 Security Requirements
User authentication and role-based access control are
mandatory.
Data encryption for sensitive information.
3.2.3 Usability Requirements
The UI should be user-friendly and accessible to all staff
members.
3.2.4 Reliability Requirements
The system should be available 99.9% of the time.
3.2.5 Supportability Requirements
The system should be modular, allowing easy updates and
maintenance.
4. External Interface Requirements
4.1 User Interfaces
The system should provide a graphical user interface using Java
Swing or JavaFX.
4.2 Hardware Interfaces
Integration with barcode scanners for inventory management.
Printer support for generating bills and reports.
4.3 Software Interfaces
Database connectivity using JDBC for MySQL.
Integration with email service for sending notifications.
4.4 Communication Interfaces
Local area network (LAN) connectivity for accessing the
system.
5. Other Requirements
5.1 Database Requirements
The system should use MySQL for data storage, with properly
normalized database tables.
5.2 Logging and Monitoring Requirements
System logs should record user activities for security auditing.
6. Appendices
6.1 Glossary
JDBC: Java Database Connectivity
LAN: Local Area Network
6.2 Diagrams
Use case diagrams, ER diagrams, and sequence diagrams can
be added here.
ER-Diagram Of Hospital Management System
Project
Data Flow Diagram (DFD) Of Hospital Management System
project Level-0
Data Flow Diagram (DFD) Of Hospital Management System
Project Level-1
Data Flow Diagram(DFD) Of Hospital Management System
Project Level-2
Use Case Diagram Of Hospital Management System Project
Thank You
To All
