0% found this document useful (0 votes)
11 views

ELAVOO

The Hospital Management System (HMS) project aims to streamline patient registration, appointment booking, and data management for healthcare facilities. It features modules for user authentication, patient and doctor management, and an admin dashboard, ensuring secure and efficient operations. The project includes detailed planning, cost estimation, and a comprehensive testing strategy to ensure functionality and reliability.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
11 views

ELAVOO

The Hospital Management System (HMS) project aims to streamline patient registration, appointment booking, and data management for healthcare facilities. It features modules for user authentication, patient and doctor management, and an admin dashboard, ensuring secure and efficient operations. The project includes detailed planning, cost estimation, and a comprehensive testing strategy to ensure functionality and reliability.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 18

SOFTWARE REQUIREMENTS SPECIFICATION

SRS

ABSTRACT-
Our project Hospital Management system includes registration of patients, storing their
details into the system, and also booking their appointments with doctors. Our software
has the facility to give a unique id for every patient and stores the details of every
patient and the staff automatically. User can search availability of a doctor and the
details of a patient using the id. The Hospital Management System can be entered using
a username and password. It is accessible either by an administrator or receptionist.
Only they can add data into the database. The data can be retrieved easily. The interface
is very user-friendly. The data are well protected for personal use and makes the data
processing very fast.

LITERACY SURVEY-

It is having mainly two modules. One is at Administration Level and other one is of
user I.e. of patients and doctors. The Application maintains authentication in order to
access the application. Administrator task includes managing doctors information,
patient’s information. To achieve this aim a database was designed one for the patient
and other for the doctors which the admin can access. The complaints which are given
by user will be referred by authorities. The Patient modules include checking
appointments, prescription. User can also pay doctor’s Fee online.

https://www.apollohospitals.com

https://tnhealth.tn.gov.in

https://www.kauveryhospital.com

http://www.medindiahospitals.com
ISSUES :

In this busy world we don’t have the time to wait in infamously long hospital
queues. The problem is, queuing at hospital is often managed manually by
administrative staff, then take a token there and then wait for our turn then ask
for the doctor and the most frustrating thing - we went there by traveling a long
distance and then we come to know the doctor is on leave or the doctor can’t
take appointments.

SOLUTIONS :

HMS will help us overcome all these problems because now patients can book
their appointments at home, they can check whether the doctor they want to
meet is available or not. Doctors can also confirm or decline appointments, this
help both patient and the doctor because if the doctor declines’ appointment
then patient will know this in advance and patient will visit hospital only when
the doctor confirms’ the appointment this will save time and money of the
patient. Patients can also pay the doctor’s consultant fee online to save their
time. HMS is essential for all healthcare establishments, be it hospitals, nursing
homes, health clinics, rehabilitation centers, dispensaries, or clinics. The main
goal is to computerize all the details regarding the patient and the hospital. The
installation of this healthcare software results in improvement in administrative
functions and hence better patient care, which is the prime focus of any
healthcare unit.
HIGH LEVEL ARCHITECTURE :

Input: User inputs through the web interface, such as login credentials, appointment details,
patient and doctor information.
Modules:
Login System Module: Provides authentication and authorization functionality for users.
Includes the Login API.
Appointment Booking Module: Allows patients to schedule appointments with doctors.
Includes the Appointment Booking API.
Patient Management Module: Enables the management of patient information. Includes the
Patient API.
Doctor Management Module: Enables the management of doctor information. Includes the
Doctor Management API.
Admin Dashboard Module: Provides administrators with access to system information and
management tools. Includes the Admin Dashboard API.
Database: Stores and retrieves information for all modules.
Output: The web interface displays information retrieved from the database and the output of
various API calls. Users can view their appointment history, patients and doctors can manage
their information, and administrators can manage the system as a whole.
ER DIAGRAM:
HARDWARE AND SOFTWARE REQUIEREMENTS :

HARDWARE REQUIEREMENTS:

Laptop / computer with-


 Processor:3.20GHz 2.50GHz
 Ram: 16GB
 Harddisk:512GB

SOFTWARE REQUIEREMENTS:

 Language used: PHP


 Database: MySQL
 User interface design: HTML,CSS
 Web browser: google chrome,Microsoft

NON-FUNCTIONALITY REQUIEREMENTS:

 Security- It will secure all the data of admin and patient details.
 Performance-
 Maintainability- The maintenance should be proper to avoid server
problem
 Reliability-
 Flexibility
 Performance- the performance should be
 Portability
SOFTWARE DESIGN SPECIFICATION
SDS
DECOMPOSITION OF MODULES:
Module 1: Login System Module

START

Patient Login Doctor Login Admin Login

STOP

Module 2 : Appointment Booking Module

START

View appointment
Book Appointment history

STOP

Module 3 : Patient Management Module

START

Edit patient View patient


Add Patient Delete Patient
information information

STOP
Module 4 : Doctor Management Module

START

Edit doctor View doctor


Add doctor Add doctor Add doctor
information information

STOP

Module 5 : Admin Dashboard Module

START

View Doctor’s and


Manage Patients Manage Doctors Patient’s Session
Logs

STOP

Module 6 : Doctor Appointment Module

START

Manage Patients
View appointments
Records

STOP
TIME SCHEDULING:

Task Start Date End Date Duration (Days)


Project Planning and Requirements 01/10/2023 01/16/2023 7
Database Design and Setup 01/17/2023 01/23/2023 7
Login System Module Development 01/24/2023 02/06/2023 14
Appointment Booking Module Development 02/07/2023 02/20/2023 14
Patient Management Module Development 02/21/2023 03/06/2023 14
Doctor Management Module Development 03/07/2023 03/20/2023 14
Admin Dashboard Module Development 03/21/2023 04/02/2023 13
Doctor Appointment Module Development 04/03/2023 04/16/2023 14
Testing and Bug Fixing 04/17/2023 04/23/2023 7
Deployment and Finalization 04/24/2023 04/30/2023 7
COST ESTIMATION:
1. Personnel Costs:
 Assuming 2 persons will be working on the project for 8 hours per day, 5 days a
week, for 100 days, the total number of person-hours would be 2 * 8 * 5 * 100 =
8,000 hours.
 Assuming an average hourly rate of 500 rupees for each person, the total personnel
cost would be 8,000 * 500 * 2 = 8,00,000 rupees.
2. Software and Hardware Costs:
 Assuming the project will require a standard development environment, the software
and hardware costs would include the cost of the development tools, licenses, and any
necessary hardware.
 Assuming a total cost of 70,000 rupees for software and hardware, which includes:
 Laptop with Windows 11 operating system: 60,000 rupees
 XAMPP, Visual Studio Code, and MySQL Workbench (free to download and
use)
 Strong internet with MySQL Workbench: 2,000 rupees per month for 3
months = 6,000 rupees
3. Maintenance Costs:
 Assuming a yearly maintenance cost of 10% of the development cost, the
maintenance cost for this project would be 8,00,000 * 10% = 80,000 rupees per year.
Total Cost Estimate:
 Personnel Costs: 8,00,000 rupees
 Software and Hardware Costs: 70,000 rupees
 Maintenance Costs: 80,000 rupees per year
 Total: 8,50,000 rupees

ACTIVITY CHART:
1. Project Planning and Requirements (Duration: 7 days)
 Define project scope and objectives
 Identify stakeholders and their requirements
 Develop project schedule and budget
 Create project plan and timeline
2. Database Design and Setup (Duration: 7 days)
 Design database schema and ER diagram
 Identify required tables and fields
 Create database and tables
 Configure MySQL Workbench and XAMPP
3. Login System Module Development (Duration: 14 days)
 Develop user login interface and functionality
 Implement user authentication and authorization
 Develop session management
 Integrate with database
4. Appointment Booking Module Development (Duration: 14 days)
 Develop appointment booking interface and functionality
 Implement appointment scheduling and availability management
 Develop email and SMS notification system
 Integrate with database
5. Patient Management Module Development (Duration: 14 days)
 Develop patient management interface and functionality
 Implement patient registration and profile management
 Develop medical history tracking system
 Integrate with database
6. Doctor Management Module Development (Duration: 14 days)
 Develop doctor management interface and functionality
 Implement doctor registration and profile management
 Develop specialization tracking system
 Integrate with database
7. Admin Dashboard Module Development (Duration: 13 days)
 Develop admin dashboard interface and functionality
 Implement user and appointment management
 Develop system logs tracking system
 Integrate with database
8. Doctor Appointment Module Development (Duration: 14 days)
 Develop doctor appointment interface and functionality
 Implement doctor appointment management
 Develop prescription management system
 Integrate with database
9. Testing and Bug Fixing (Duration: 7 days)
 Conduct system and user acceptance testing
 Identify and fix bugs and errors
 Test system reliability and performance
 Optimize system for efficiency
10. Deployment and Finalization (Duration: 7 days)
 Deploy system on server and configure
 Finalize system documentation and user manual
 Conduct user training and orientation
 Close out project and hand over to operations team
Activity Name Week No Duration (Days)
Project Planning and Requirements 1-2 7
Database Design and Setup 3-4 7
Login System Module Development 5-8 14
Appointment Booking Module Development 9-12 14
Patient Management Module Development 13-16 14
Doctor Management Module Development 17-20 14
Admin Dashboard Module Development 21-24 13
Doctor Appointment Module Development 25-28 14
Testing and Bug Fixing 29-30 7
Deployment and Finalization 31-32 7
TASK DEPENDENCY:
Duration Effort (person-
Task Dependencies
(days) days)
Project Planning and
Requirements 7 None 14

Project Planning and


Database Design and Setup 7 14
Requirements
Login System Module
14 Database Design and Setup 28
Development
Appointment Booking Module Login System Module
14 28
Development Development
Patient Management Module Appointment Booking Module
14 28
Development Development
Doctor Management Module Patient Management Module
14 28
Development Development
Admin Dashboard Module Doctor Management Module
13 26
Development Development
Doctor Appointment Module Admin Dashboard Module
14 28
Development Development
Doctor Appointment Module
Testing and Bug Fixing 7 14
Development
Deployment and Finalization 7 Testing and Bug Fixing 14

CRITICAL PATH:
Early Early Late Late
Activity Name Duration Float
Start Finish Start Finish
Project Planning and
1 7 7 1 0 7
Requirements
Database Design and Setup 8 7 14 8 0 14
Login System Module
15 14 28 15 0 28
Development
Appointment Booking Module
29 14 43 29 0 43
Development
Patient Management Module
44 14 58 44 0 58
Development
Doctor Management Module
59 14 73 59 0 73
Development
Admin Dashboard Module 74 13 87 74 0 87
Development
Doctor Appointment Module
88 14 102 88 0 102
Development
Testing and Bug Fixing 103 7 110 103 0 110
Deployment and Finalization 111 7 118 111 0 118

The critical path for this project is:


Project Planning and Requirements -> Database Design and Setup -> Login System Module
Development -> Appointment Booking Module Development -> Patient Management
Module Development -> Doctor Management Module Development -> Admin Dashboard
Module Development -> Doctor Appointment Module Development -> Testing and Bug
Fixing -> Deployment and Finalization.
All activities in the critical path have zero float.
TESTING REPORT

Whitebox Testing:
Whitebox testing is a software testing method in which the internal structure of the software
or code is tested. It focuses on verifying the correctness of the code and ensuring that all the
paths of the code are executed properly. For this project, whitebox testing can be performed
by testing the login module, appointment booking module, patient management module,
doctor management module, admin dashboard module, and doctor appointment module by
checking the code paths and ensuring that the data is handled properly.
Blackbox Testing:
Blackbox testing is a software testing method in which the internal structure of the software
or code is not known to the tester. The focus is on the functionality of the software, testing
whether it meets the requirements specified in the project. For this project, blackbox testing
can be performed by testing the login module, appointment booking module, patient
management module, doctor management module, admin dashboard module, and doctor
appointment module by verifying the input-output functionality and ensuring that the
software is functioning as expected.
Unit Testing:
Unit testing is a software testing method in which individual units or components of the
software are tested. It helps to ensure that each unit of the software is working as expected.
For this project, unit testing can be performed on the individual modules like login module,
appointment booking module, patient management module, doctor management module,
admin dashboard module, and doctor appointment module.
Integrated Testing:
Integrated testing is a software testing method in which individual modules are combined and
tested as a group. It helps to ensure that the modules are functioning properly when integrated
together. For this project, top-down approach, bottom-up approach, and big bang approach
can be used to perform integrated testing. In the top-down approach, the higher-level modules
are tested first followed by the lower-level modules. In the bottom-up approach, the lower-
level modules are tested first followed by the higher-level modules. In the big bang approach,
all the modules are integrated and tested together.
System Testing:
System testing is a software testing method in which the entire system is tested as a whole. It
helps to ensure that the system meets the requirements specified in the project. For this
project, system testing can be performed on the entire system after the individual modules
have been integrated and tested. The focus will be on testing the functionality of the entire
system, verifying the input-output functionality, and ensuring that the system is functioning
as expected.
Alpha Testing:
Alpha testing is a software testing method in which the software is tested in a controlled
environment by the in-house development team or users. It helps to ensure that the software
is functioning as expected and to identify any issues or bugs before releasing it to the public.
For this project, alpha testing can be performed by the in-house development team on each
module and on the entire system.
Regression Testing:
Regression testing is a software testing method in which the software is retested after changes
have been made to ensure that the changes have not affected the existing functionality. For
this project, regression testing can be performed on each module and on the entire system
after changes have been made.
Smoke Testing:
Smoke testing is a software testing method in which a quick and simple test is performed to
ensure that the system is stable enough for further testing. For this project, smoke testing can
be performed on each module and on the entire system before performing further testing.

CONCLUSION-

Working on the project was an excellent experience. It helped us to understand


the importance of planning, designing and implementation so far we have learnt in
our theory books. It helped us unleashing our creativity while working in a team. It
also realized the importance of team working, communication as a part of this
project. Finally, we like to conclude that we put all our efforts throughout the
development of our project and tried to fulfill most of the requirements of the user.

REFERENCES :

https://www.apollohospitals.com

https://tnhealth.tn.gov.in

https://www.kauveryhospital.com

http://www.medindiahospitals.com

You might also like