Tribhuvan University

Faculty of Humanities and Social Sciences

A Project Report on

Doctor Appointment System

Submitted to
Department of Computer Application
Ratna Rajyalaxmi Campus

In partial fulfillment of the requirements for Bachelors in

Computer Application

Submitted by
Diwakar Awasthi (6-2-40-20-2022)
Binod Kimadi (6-2-40-12-2022)

February, 2025

Under the Supervision of

Mr. Bhupendra Ram Luhar
 Tribhuvan University
Faculty of Humanities and Social Sciences
Ratna Rajyalaxmi Campus

SUPERVISOR’S RECOMMENDATION

I hereby recommended that this project prepared under my supervision by Diwakar

Awasthi and Binod Kimadi entitled “Doctor Appointment System” in partial
fulfillment of the requirements for the degree of Bachelor of Computer Application is
recommended for the final evaluation.

Mr. Bhupendra Ram Luhar

SUPERVISOR
Bachelor of Computer Applications
Exhibition Road, Kathmandu
Ratna Rajyalaxmi Campus
 Tribhuvan University
Faculty of Humanities and Social Sciences
Ratna Rajyalaxmi Campus

LETTER OF APPROVAL

This is to verify that this project prepared by Diwakar Awasthi and Binod Kimadi
entitled “DOCTOR APPOINTMENT SYSTEM” in partial fulfillment of the
requirements for the degree of Bachelor of Computer Application has been evaluated. In
our opinion it is satisfactory in the scope and quality as a project for the required degree.

Mr. Bhupendra Ram Luhar Mr. Ananda K.C

Supervisor Director
BCA, Ratna Rajyalaxmi Campus BCA, Ratna Rajyalaxmi Campus
Exhibition Road, Kathmandu Exhibition Road, Kathmandu

Internal Examiner External Examiner

 ABSTRACT
The Doctor Appointment System is a user-friendly web-based application designed to
facilitate efficient appointment scheduling and management for patients. Developed using
the Waterfall Model, this system ensures a structured and reliable approach to
development, providing smooth experience for both patients and doctors.
The system allows patients to effortlessly browse available doctors based on
specialization, availability, and book appointments online. Users can register and manage
their profiles. For doctors, the system enables efficient management of patient’s
appointment schedules whereas the doctors are verified by admin. By providing an
intuitive interface and robust functionality, the platform delivers a smooth experience to
patients while minimizing errors and improving the processes. This system reduces
manual workload, saves time and effort, and enhances satisfaction for both doctors and
patients.
Keywords: Appointment, CRUD operation, User friendly

i
 ACKNOWLEDGEMENT

The project work presented in this report has been carried out and presented at Ratna
Rajya Laxmi Campus, Faculty of Humanities and Social Sciences Tribhuvan University
of Technology as a part of Bachelors in Computer Application. Project is a test of not
only technical skills but also teamwork and performance under various constraints. This
journey cannot be successfully accomplished without help from experts.

We take this opportunity to acknowledge our sincere gratitude to our supervisor Mr.
Bhupendra Ram Luhar for providing us this type of quality of education, guidance and
suggestions which has helped us throughout the completion of this project.

In addition, we would like to give a word of thanks to Mr. Ananda K.C., director, and
rest of the entire department member who encouraged us to successfully develop the
system.

ii
 Table of Contents
ABSTRACT.......................................................................................................................... i
ACKNOWLEDGEMENT ...................................................................................................ii
LIST OF ABBREVIATIONS .............................................................................................. v
LIST OF FIGURES ............................................................................................................ vi
LIST OF TABLES .............................................................................................................vii
CHAPTER 1: INTRODUCTION ........................................................................................ 1
1.1 Introduction ................................................................................................................ 1
1.2 Problem Statement ..................................................................................................... 1
1.3 Objectives .................................................................................................................. 1
1.4 Scope and limitations ................................................................................................. 2
1.4.1 Scopes of the System ....................................................................................................... 2
1.4.2 Limitations of the System ................................................................................................ 2
1.5 Report Organization ................................................................................................... 2
CHAPTER 2: BACKGROUND STUDY AND LITERATURE REVIEW ........................ 3
2.1 Background Study...................................................................................................... 3
2.2 Literature Review ...................................................................................................... 3
CHAPTER 3: SYSTEM ANALYSIS AND DESIGN ........................................................ 5
3.1 System Analysis ......................................................................................................... 5
3.1.1 Requirement Analysis ..................................................................................................... 5
3.1.2 Feasibility Analysis ......................................................................................................... 6
3.1.3 Data Modeling ................................................................................................................. 8
3.1.4 Process Modeling ............................................................................................................ 9
3.2 System Design ......................................................................................................... 11
3.2.1 Architectural Design ...................................................................................................... 11
3.2.2 Database Schema Design: ............................................................................................. 11
3.2.3 Interface Design: ........................................................................................................... 12
3.2.4 Physical DFD: ....................................................................................................... 22
CHAPTER 4: IMPLEMENTATION AND TESTING ..................................................... 24
4.1 Implementation ........................................................................................................ 24
4.1.1 Tools Used ..................................................................................................................... 24
4.1.2 Implementation Details of Modules .............................................................................. 24
4.2 Testing ..................................................................................................................... 25
4.2.1 Test Case for Unit Testing ............................................................................................. 25
4.2.2 Test Case for System Testing ........................................................................................ 32
CHAPTER 5: CONCLUSION AND FUTURE RECOMMENDATION ......................... 34
5.1 Conclusion ............................................................................................................... 34
iii
 5.2 Future Recommendations ........................................................................................ 34
APPENDICES ................................................................................................................... 35
REFERENCE ..................................................................................................................... 41

iv
 LIST OF ABBREVIATIONS

CASE Computer Aided Software Design

CSS Cascading Style Sheet
DFD Data Flow Diagram
ER Entity Relationship
FR Functional Requirement
HTML Hyper Text Markup Language
JS JavaScript
MySQL My Structured Query Language
PHP Hypertext Preprocessor
UI User Interface
UX User Experience

v
 LIST OF FIGURES
Figure 3. 1: Use Case Diagram Of Doctor Appointment System .................................. 5
Figure 3. 2:Gantt Chart of Doctor Appointment System ............................................... 7
Figure 3. 3:E-R Diagram of Doctor Appointment System ............................................. 8
Figure 3. 4: Context level diagram of Doctor Appointment System ............................. 9
Figure 3. 5:Level 1 DFD .................................................................................................. 10
Figure 3. 6: Architectural Design of Doctor Appointment System ............................. 11
Figure 3. 7:Database Schema Design of Doctor Appointment System ....................... 12
Figure 3. 8:Wireframe of Home page ............................................................................ 12
Figure 3. 9:Wireframe of sign up for patient ................................................................ 13
Figure 3. 10:Wireframe of signup for doctor ................................................................ 13
Figure 3. 11:Wireframe of login form for doctor and patient ..................................... 14
Figure 3. 12: Wireframe of patient dashboard ............................................................. 14
Figure 3. 13:Wireframe of patient appointment ........................................................... 15
Figure 3. 14:Patient Profile ............................................................................................. 15
Figure 3. 15 :Doctor Dashboard ..................................................................................... 16
Figure 3. 16 :Doctors create appointment ..................................................................... 16
Figure 3. 17: My Appointment ....................................................................................... 17
Figure 3. 18: Appointment Request ............................................................................... 17
Figure 3. 19: Doctor Appointment History.................................................................... 18
Figure 3. 20: Profile of Doctor ........................................................................................ 18
Figure 3. 21: Admin Login .............................................................................................. 19
Figure 3. 22: Admin Dashboard ..................................................................................... 19
Figure 3. 23: Create Speciality ........................................................................................ 20
Figure 3. 24:Pending doctors .......................................................................................... 20
Figure 3. 25:Verified Doctors.......................................................................................... 21
Figure 3. 26:Rejected Doctor .......................................................................................... 21
Figure 3. 27: Physical DFD of Hospital Management System ..................................... 22

vi
 LIST OF TABLES
Table 4. 1 Test case for sign up ....................................................................................... 25
Table 4. 2 Testing Login Form........................................................................................ 28
Table 4. 3 Testing Verification of Doctor....................................................................... 29
Table 4. 4 Testing Doctor Deletion ................................................................................. 29
Table 4. 5 Schedule Appointment ................................................................................... 30
Table 4. 6 Book Appointment ......................................................................................... 30
Table 4. 7 Testing Confirmation of Appointment ......................................................... 30
Table 4. 8:Test Case for Appointment Deletion ............................................................ 31
Table 4. 9:Test Case for Speciality ................................................................................. 31
Table 4. 10:Profile Update .............................................................................................. 31
Table 4. 11:Test Case for System Testing ...................................................................... 32

vii
 CHAPTER 1: INTRODUCTION

1.1 Introduction
In today’s rapidly evolving healthcare landscape, efficient appointment management is
essential for ensuring seamless and timely delivery of patient care. The primary objective
of this project is to provide patients with a convenient and hassle-free way to book
appointments with doctors. It addresses common challenges faced by patients during the
appointment process and aims to simplify scheduling for both patients and healthcare
providers.
The system is designed to streamline the appointment scheduling process by enabling
doctors to manage their booking slots online. Patients can easily view and reserve
available slots, which are then confirmed in their names. This ensures organized and
efficient scheduling experience.
Patients in rural areas often face significant difficulties when booking appointments due
to the time required to reach hospitals. They may miss preferred appointment times or
experience long waits in queues, leading to discomfort and inconvenience. By offering an
online booking option, this system empowers patients to plan their visits better, saving
time and ensuring they can see doctors at their convenience.
The Doctor Appointment System is a modern and user-friendly solution that enhances the
scheduling and management of medical appointments. It improves accessibility, reduces
waiting times, and creates a more efficient healthcare experience for patients and
providers alike.

1.2 Problem Statement

In the rapidly evolving healthcare sector, managing medical appointments efficiently

remains a significant challenge. Inability to secure appointments at desired times leads to
missed opportunities for timely medical care. Managing appointments manually or
through outdated systems often results in disorganized scheduling, overbooked slots, and
underutilization of resources. These inefficiencies not only impact operational workflows
but also diminish the overall patient experience.

1.3 Objectives
The objectives of the Doctor Appointment System are:

1
 ➢ To enable admin to login so they can set specialty and manage doctors.
➢ To enable patients to register and log in so they can book the appointments.
➢ To enable doctors to register and log in so they can schedule they appointments
and manage appointments.

1.4 Scope and limitations

1.4.1 Scopes of the System

➢ Managing patient and doctor registration and authentication.
➢ Manage appointment scheduling.
➢ Booking and canceling appointments.

1.4.2 Limitations of the System

➢ This system can be accessed via the web only.
➢ Only the registered doctors and patients can access the system.
➢ Need internet access to use the system.

1.5 Report Organization

The report can be organized into 5 chapters which are given below:
Chapter 1 includes a brief introduction of the system, statement of problem, objectives,
scope and limitation.
Chapter 2 includes background study and literature review.
Chapter 3 includes system analysis and design, different feasibility analysis and design
system architecture, entity relationship diagram and data flow diagram.
Chapter 4 includes implementation and testing of the current system.
Chapter 5 includes conclusions, outcomes of the system and future recommendations.

2
 CHAPTER 2: BACKGROUND STUDY AND LITERATURE
REVIEW

2.1 Background Study

In the 1970s, basic hospital management software was developed, mainly for
administrative tasks such as billing and scheduling. However, it wasn’t until the 1990s
that more integrated systems began to emerge, enabling hospitals to centralize patient
data, medical records, and healthcare information. With the advent of Electronic Health
Records (EHR) and Electronic Medical Records (EMR) systems, hospital management
evolved into a more holistic approach, aiming to improve healthcare outcomes through
better data management and coordination.
The recent studies focus on integrated systems that combine EHR, patient scheduling,
billing, pharmacy management, and other hospital operations into a single platform.
Cloud-based systems have also gained popularity, offering flexibility and scalability to
accommodate the growing demands of hospitals. Systems like Epic Systems and Cerner
are widely used, with features that enable real-time data sharing among healthcare
professionals, improving collaboration and patient care. [1]
The Doctor Appointment System provides functionality for patients to register, log in and
take appointments from doctor. It also provides functionality for doctors to manage
appointments. And ass for admin, it manages the doctor. The system ensures
transparency, reduces manual effort, and creates a smooth experience for all users.

2.2 Literature Review

Doctor management systems are tailored solutions developed to optimize administrative
and operational processes in healthcare environments. These platforms focus on
efficiently managing doctors’ schedules, facilitating patient interactions, and streamlining
hospital workflows. By minimizing manual tasks, improving communication, and
boosting overall efficiency, these systems address the increasing complexity of hospital
operations and meet the growing demand for enhanced patient care. There are several
well-known car rental systems used globally. Some existing systems are studied below:
Zocdoc is a New York City-based healthcare marketplace that simplifies finding and
booking medical and dental appointments. The platform offers features like user reviews
and ratings, insurance verification, real-time availability, and telehealth options. It

3
connects patients with healthcare providers, making it easier to access care. The service is
free for patients, while doctors pay to advertise their appointment slots. [2]
Examining a comprehensive Hospital Management System (HMS), this abstract examines
its complex structure, which aims to transform healthcare facility operations and improve
patient care outcomes has been successful. The HMS integrates state-of-the-art
technology with holistic operational, clinical, and financial functions, improving
operational efficiency and organizational efficiency in health care systems. At its core, the
performance module acts as a hub, streamlining patient referrals, appointments, and bed
allocation through automated processes and real-time data analytics. At the same time, it
optimizes resource allocation through efficient staffing, payroll, and inventory
management, thus empowering hospital administrators to provide performance is closely
monitored. In addition, the clinical module integrates electronic health records (EHRs),
decision support systems, and telemedicine capabilities to enhance patient care quality
and enhance interdisciplinary collaboration among healthcare providers. By leveraging
centralized patient data and advanced analytics, this module enables harnessing the power
of personalized treatment strategies, enabling improved diagnostic accuracy and treatment
outcomes. Supporting these clinical and operational functions, the finance module
automates revenue cycle management, payment, and insurance management, facilitating
financial transparency and compliance. Through seamless integration with external
payment systems and insurance networks, the HMS promotes efficiency and ensures
timely reimbursement, thus promoting the financial health of healthcare organizations in
the dense. [3]
HealthPlix is a comprehensive Electronic Medical Record (EMR) software designed for
doctors and healthcare providers in India. Key features include patient registration,
appointment scheduling, electronic medical records (EMR), billing and invoicing,
prescription management, lab integration, inventory management, patient portal,
telemedicine, analytics and reporting, SMS and email notifications, doctor dashboard,
multi-location support, role-based access control, customizable templates, clinical
decision support, document management, referral management, queue management, and a
mobile app. HealthPlix is known for its user-friendly interface and robust functionality,
making it a popular choice among healthcare professionals. [4]

4
 CHAPTER 3: SYSTEM ANALYSIS AND DESIGN

3.1 System Analysis

3.1.1 Requirement Analysis

For the doctor appointment system, the requirement analysis involves identifying and
defining both functional and non-functional requirements to ensure that the system meets
user needs and business goals. Here’s a detailed analysis:
i. Functional Requirements:

Figure 3. 1: Use Case Diagram of Doctor Appointment System

5
Patient Module:
• Patient can Sign up into the system.
• Patient can Login and Logout into the system.
• Patients can view the doctors.
• Patients can choose appointments.
Admin Module:
• Admin can Login and Logout into the system.
• Admin can manage doctors.
Doctor Module:
• Doctors can Sign up into the system.
• Doctors can Login and Logout into the system.
• Doctors can schedule appointments.
• Doctors can manage appointments.

ii. Non-Functional Requirements

• The Doctor Management System is easy to maintain and update as clear
documentation and well-commented code enables developers to easily understand
and modify it without difficulty.
• This system works across different devices and platforms. As it follows
responsive web design principles, ensuring accessibility and a user-friendly
expensive across desktops.
• This system is easy to use with a simple interface for doctors, patients and admin.
A simple design with clear navigation and easy to use features ensuring a smooth
experience.

3.1.2 Feasibility Analysis

A feasibility study for doctor appointment system assesses its viability and worthiness. It
evaluates technical, economic, and operational aspects to determine if investing time and
resources in developing the system is justified.
i. Technical Feasibility
The technical feasibility of the system is guaranteed by using reliable, scalable
hardware and software that can handle large amounts of data. This system is built
with HTML, CSS and java script for frontend and Php for backend that are ideal

6
 for web applications. It works consistently across different devices and operating
systems. Furthermore, there are technical support and maintenance plans to
resolve any issues and ensure that the system operates effectively.

ii. Operational Feasibility

This system is operationally feasible because it is designed user-friendly for
individuals with basic computer skills, requiring no additional training. The
interface of this system is designed simple and intuitive, making it easy to
navigate. Furthermore, comprehensive support and documentation are available to
assist users with any questions or issues they might have.
iii. Economic Feasibility
The system is economically feasible because it doesn’t require any substantial
finance to build and maintain. The system does not generate revenue for those
who host the system, as the maintenance and operation cost must be supplied by
those who wish to host the system.
iv. Scheduled Feasibility
A Gantt Chart is used to track progress and ensures that the project is completed
within the given time frame.

Figure 3. 2:Gantt Chart of Doctor Appointment System

7
3.1.3 Data Modeling

An Entity-Relationship (E-R) Diagram visually shows the entities, their attributes and the
relationships between them in a database. It helps with designing and understanding the
structure of a database. The E-R Diagram of Doctor Appointment System is shown
below:

Figure 3. 3:E-R Diagram of Doctor Appointment System

8
3.1.4 Process Modeling

Figure 3. 4: Context level diagram of Doctor Appointment System

The context level diagram overviews the entire system. The above figure shows the
overviews of the Doctor Appointment System. It shows how the external entities (doctor,
patient, admin) interact with the system. The arrows pointed to and from the external
entities indicate the flow of data. The diagram shows that doctor and patient must sign up.
All the external entities have to login to enter the system. The admin can verify and
manage the doctor. The doctor can schedule the appointment, confirm or cancel the
appointment request from the patient. The patient can book the appointment scheduled by
the doctor.

9
 Figure 3. 5:Level 1 DFD
DFD is an abstract description of the system. DFDs are in levels which represent
increasing information flow and functional details. Users can either sign up as a patient or
as a doctor. The details provided by the users will be stored in corresponding database
according to their user type. Admin verifies the doctors after the doctor signup in the
system. If the doctor is verified by the admin, then the doctor can schedule the
appointments. The patient can book the appointment, and the doctor can either accept or
reject the appointment which is then stored in database.

10
3.2 System Design
To realize the different functional requirements of the system, different diagrams of the
system have been prepared which are as follows:

3.2.1 Architectural Design

Figure 3. 6: Architectural Design of Doctor Appointment System

The Architectural Design of Doctor Appointment System is as above. This diagram

shows the three-tier architecture used in the system along with different tools/languages
used in each layer along with some of the functions of the users. This system uses
MYSQL as the main database in the database layer. It also uses PHP as the principal
language to facilitate communication between the presentation layer and the database
layer. The use of HTML and CSS alongside JavaScript in the presentation layer helps the
system to be faster.

3.2.2 Database Schema Design:

The database schema design of the Doctor Appointment System describes the tables used
in the system along with their columns, data types and the length of the datatypes. This
shows the relationship between the various tables used in the database ‘Project’.

11
 Figure 3. 7:Database Schema Design of Doctor Appointment System

3.2.3 Interface Design:

The tools and technologies like HTML, CSS, JS, PHP are used for interface design. Here
are some images of wireframes of the system interfaces:

Figure 3. 8:Wireframe of Home page

12
The Home Page is the gateway of the system. This allows the users to log in, sign up, into
the system.

Figure 3. 9:Wireframe of sign up for patient

The signup for patient allows the patient to sign up in the system with details of full
name, email, contact, password and must confirm the password. If the details are valid
then the patient successfully registered.

Figure 3. 10:Wireframe of signup for doctor

13
The signup for the doctor allows the doctor to sign up with details like full name, email,
contact, password , qualification, specialty, experience letter and necessary documents. If
the details provided are valid then the doctor is registered in the system

Figure 3. 11:Wireframe of login form for doctor and patient

The login form allows the doctor and patient to enter in the system if the email and
password provided by them are correct.

Figure 3. 12: Wireframe of patient dashboard

The patient dashboard shows the doctor details according to their specialties. Patient can

14
look after doctors according to different specialties. They can book the appointment of
doctors accordingly.

Figure 3. 13:Wireframe of patient appointment

The patient can see whether the doctor has approved the appointment or not. The patient
can cancel the appointment if the doctor has not confirmed the appointment.

Figure 3. 14:Patient Profile

The patient can update the email, contact and password if necessary.

15
 Figure 3. 15 :Doctor Dashboard
The doctors will be able to look after today’s appointments. They can confirm whether
there is any appointment or not for today.

Figure 3. 16 :Doctors create appointment

The doctor can create the appointments. S/he can create the appointment for the duration
of one week.

16
 Figure 3. 17: My Appointment

The doctor will be able to see his/her appointments of different dates and time.

Figure 3. 18: Appointment Request

The doctor can respond to the requests of the patients whether to accept or reject.

17
 Figure 3. 19: Doctor Appointment History

The doctor will be able to see the past appointments. S/he will be able to delete the past
appointments.

Figure 3. 20: Profile of Doctor

The doctor can update his/her email, contact , password and profile picture.

18
 Figure 3. 21: Admin Login

The admin will be able to login if the email and password are valid. This section is only
for admins.

Figure 3. 22: Admin Dashboard

The admin can see the numbers of pending doctors, verified doctors, rejected doctors and
different specialties.

19
 Figure 3. 23: Create Speciality

The admin can add different specialties of doctors.

Figure 3. 24:Pending doctors

The admin can either accept or reject the doctor requests according to their documents
and experience letter.

20
 Figure 3. 25:Verified Doctors

The verified doctors will be visible to the admins. The admin can delete the doctors if
necessary.

Figure 3. 26:Rejected Doctor

The admin can see the doctors who were rejected.

21
3.2.4 Physical DFD:

Figure 3. 27: Physical DFD of Hospital Management System

22
The above figure shows the physical DFD of the Doctor Appointment System. The
registration is implemented by making a signup form in PHP which accepts the details of
doctors and patients and stores the data in their respective databases. If the user is doctor
then the data will be stored in doctor table and if the user is patient then the data will be
stored in patient table. If the required fields are not filled then the registration is not
submitted. During the login process, the doctor or patient fills the login credentials. If the
login credentials match the data stored in table then the access is granted. Similarly,
Admin fills the login credentials in the login form, if it matches with the data stored in the
admin table then access is granted. The admin verifies the doctors according to their
documents submitted i.e. experience letter and either license image or others that help to
determine s/he is a doctor. If the doctor is approved by the admin then only the doctor is
allowed to schedule the appointments. The scheduled appointments will be visible to the
patients in their dashboard. The patients can choose the appointment accordingly. The
detail of the appointment chose by the patient will be visible to the doctor who has
scheduled that appointment. The doctor has to either accept or reject the appointment. If
doctor approves the appointment then the appointment will not be visible to the other
patients. If the appointment is rejected then the appointment will be visible to other
patients also. The doctor and patient are not allowed to cancel the appointment after its
confirmation.

23
 CHAPTER 4: IMPLEMENTATION AND TESTING

4.1 Implementation

4.1.1 Tools Used

Various CASE tools, font-end and back-end tools are used to make Doctor Appointment
System. The technologies used in this project are described below:
i. CASE Tools
Tools like draw.io, dbdiagram.io, Lucidchart.io and Excel are used to make
various diagrams to illustrate the design.
ii. Frontend Technologies
HTML, CSS and JavaScript are used as they are fundamental technologies to
be used for applications to be developed on the web.
iii. Backend Technologies
PHP and Apache web servers are used to develop this system.
iv. Development Tools
VS-Code with various extensions is used to aid the development of this
system.

4.1.2 Implementation Details of Modules

The different implementation modules are described below:

• Login Module
The Login module facilitates process for registered patients, doctors and admin.
The user provides their email and password which lead them to the respective
dashboard if the information supplied is correct. If not, the user is redirected to
login page.
• Signup Module
The Signup module facilitates the registration process for new doctors and
students. The user should choose their role. The registration form will vary
according to their roles. If the user supplied correct information with validation
then the user is registered to the system.
• Booking Module
This module helps the patient to view the desired doctor information along with
their appointments. The patient can book the appointment of the certain doctor.

24
 The patient can cancel the appointment if the appointment is not confirmed by the
doctor.
• Schedule Module
This module helps the doctor to schedule the appointment. The doctor cannot
schedule the previous day’s appointment. The doctor must choose current day or
future days appointments. The doctor can accept or reject the appointment request
from patient. The doctor can cancel the appointment until the appointment is
confirmed.
• Approve Module
This module helps the admin either verify or reject the doctors. The admin can
delete the verified doctors.

4.2 Testing
4.2.1 Test Case for Unit Testing
Table 4. 1 Test case for sign up

Pre-Conditions: The doctor and patient has

Dependencies: Signup Module

S Test Test Name Test Case Step Expected Actual Test

N Cas Description Result Result Cas
e ID e
Stat
us
0 01 Role Choose your Choosing Patient Successfull Pass
1 role the patient should be y chose
role chose

0 02 Signup form Full Name Input two No error No error Pass

2 Full Name Validation words in message message
validation full name

0 03 Signup form Full Name Input a Display Message Pass

3 Full Name Validation single message displayed”
Validation word ”Enter a Enter a
valid full valid full
name” name”

25
0 04 Signup form Email Input an No error No error Pass
4 Email Validation email message message
Validation address
with ‘@’

0 05 Signup form Email Input an Display Message Pass

5 Email Validation email message displayed
Validation address “please “please
without include include @”
‘@’ @”

0 06 Signup form Contact Input a 10 No error No error Pass

6 contact Validation digit message message
validation contact
starts with
97/98

0 07 Signup form Contact Input less Display Message Pass

7 contact Validation than 10 message displayed
validation digits “Contact “Contact
number number
should be should be
10 digits 10 digits or
or starts starts with
with 97/98”
97/98”
0 08 Signup form Password Input No error No error Pass
8 Password Validation more than message Message
Validation 8
characters
including
uppercase,
lowercase,
character
and a
number
0 09 Signup form Password Input less Display Message Pass
9 Password Validation than 8 message displayed “
Validation characters “Passwor Password
d must must
include8 include 8
characters characters
including including
uppercase, uppercase,
lowercase, lowercase,
character character
and a and a
number” number”

26
1 10 Signup form Password Input No error No error Pass
0 Password Validation matched message message
Validation password

1 11 Signup form Password Input Display Message Pass

1 Password Validation unmatche message displayed
Validation d “Passwor “Password
password d do not do not
match” match”

1 12 Signup form License Input No error No error Pass

2 License no Validation numbers message Message
Validation

1 13 Signup form License Input 5 Display Message Pass

3 License no Validation numbers Message displayed
Validation “Must be “Must be at
at least 6 least 6
characters characters
and and contain
contain letters,
letters, numbers”
numbers”
1 14 Signup form Qualificatio Input No error No error Pass
4 Qualificatio n Validation value message message
n

1 15 Signup form Experience Uploaded No error No error Pass

5 Experience Validation file of message message
Validation extension
.pdf, .jpg,

1 16 Signup form Experience Uploaded Display Message Pass

6 Experience Validation file size message displayed
Validation more than “File “File
2 MB exceeds 2 exceeds 2
MB” MB”

1 17 Signup form Document Uploaded No error No error Pass

7 Document Validation file of message message
Validation extension
.pdf, .jpg,

27
1 18 Signup form Document Uploaded Display Message Pass
8 Document Validation file size message displayed
Validation more than “File “File
2 MB exceeds 2 exceeds 2
MB” MB”

1 19 Signup form Profile Uploaded No error No error Pass

9 Profile Validation file of message message
Validation extension
.jpg, .jpeg,
.png

2 20 Signup form Profile Uploaded Display Message Pass

0 Profile Validation file size message displayed
Validation more than “File “File
2 MB exceeds 2 exceeds 2
MB” MB”

Table 4. 2 Testing Login Form

Pre-Conditions: The doctor, patient and admin has a valid email and password

Dependencies: Signup Module

S Test Test Test Case Step Expected Result Actual Result Test
N Cas Name Descriptio Cas
e ID n e
Stat
us
1 21 Choose Choose the Choose Either of the User chose Pass
User type of the type user chose
Type user of user

2 22 Validat Enter valid Enter Login Success Successful Pass

e Login email and email, or error login and
password passwor message directed to
d and “Invalid correspondenc
click email/Password e dashboard
login ”
button

28
 Table 4. 3 Testing Verification of Doctor

Pre-Conditions: The doctor should be registered and admin has to be logged in

Dependencies: signup module and login module

SN Test Test Name Test Case Step Expected Actual Test

Case Description Result Result Case
ID Status
1 23 Doctor Verify the View the Doctor Doctor Pass
Verification doctor document should verified
and be
verify verified

2 24 Doctor Reject the View the Doctor Doctor Pass

Verification doctor document rejected rejected
and reject

Table 4. 4 Testing Doctor Deletion

Pre-Conditions: The doctor should be verified and admin should have login

Dependencies: Login Module

SN Test Test Test Case Step Expected Actual Test

Case Name Description Result Result Case
ID Status
1 25 Doctor Delete the Doctors Doctors Pass
deletion doctor detail detail
should deleted
be
deleted

29
 Table 4. 5 Schedule Appointment

Pre-Conditions: The doctor should be verified and login

Dependencies: Admin and login

SN Test Test Name Test Case Step Expected ActualTest

Case Description Result ResultCase
ID Status
1 26 Schedule Cannot Choose Appointment Appointment Pass
Appointment choose the the Scheduled scheduled
previous valid
day and date
schedule and
up to 7 time
days

Table 4. 6 Book Appointment

Pre-Conditions: The patient should be login

Dependencies: Login

S Test Test Name Test Case Step Expected Actual Test

N Cas Description Result Result Cas
e ID e
Stat
us
1 27 Book Choose and Choose and The chosen Booked and Pas
Appointme book the book the appointme waiting for s
nt appointme appointme nt should confirmatio
nt nt be booked n from
doctor

Table 4. 7 Testing Confirmation of Appointment

Pre-Conditions: The doctor has scheduled the appointment and patient has
booked
Dependencies: Doctor and Patient

SN Test Test Name Test Case Step Expected Actual Test

Case Description Result Result Case
ID Status

30
1 28 Appointment The doctor Either Either Confirmed Pass
Confirmation has confirm confirmed
scheduled or reject or
the Rejected
appointment
and the
patient has
booked it

Table 4. 8:Test Case for Appointment Deletion

Pre-Conditions: The doctor has scheduled the appointment and patient has
booked and the appointment should of past date
Dependencies: Doctor and Patient should have logined
S Test Test Name Test Case Step Expected Actual
Test
N Cas Description Result Result
Cas
e ID e
Stat
us
1 29 Appointmen Delete the Delete the The The Pas
t Deletion appointmen appointmen appointmen appointmen s
t t t should be t deleted
deleted.

Table 4. 9:Test Case for Speciality

Pre-Conditions: The admin should have log in

Dependencies: admin login
SN Test Test Test Case Step Expected Actual Test
Case Name Description Result Result Case
ID Status
1 30 Adding Adding Add The The Pass
Specialty Specialty specialty specialty specialty
and the with the with the
maximum maximum maximum
numbers number number
of doctors of doctors of doctors
for that should be is added.
specialty. added.

Table 4. 10:Profile Update

Pre-Conditions: The doctor and patient should have signed up

Dependencies: Doctor and patient should have login
SN Test Test Test Case Step Expected Actual Test

31
 Case ID Name Description Result Result Case
Status
1 31 Profile Doctor Fill the The The Pass
Update profile email, profile profile
of updation contact, should is
Doctor password be updated.
and updated
profile
picture.
2 32 Profile Patient Fill the The The Pass
update profile email, profile profile
of updation contact detail detail is
patient and should updated
password be
updated.

4.2.2 Test Case for System Testing

Table 4. 11:Test Case for System Testing

S Test Test Test Case Step Expected Actual Result Test

Case
N Name Description Result Case
ID
Statu
s
1 33 Security Checking Login with Successful Successful Pass
Testing Security to registered login and login and
access email and directed to directed to
system password correspondi corresponding
ng dashboard
dashboard
2 33 Security Checking Login with Error Error message Pass
Testing Security to unauthorize message “Invalid email
access d email and “Invalid or password”
system password email or
password”

32
3 34 Usabilit Eliminate Signing up Message Message Pass
y Test duplicate with displayed displayed
email data already “Email “Email
on signup existing already already
email exists” exists”

4 35 Usabilit Appointme Schedule Appointme Appointment Pass

y Test nt Schedule Appointme nt should scheduled
nt be
Scheduled
5 36 Usabilit Appointme Appointme Appointme Appointment Pass
y Test nt Booking nt Booking nt should booked
be booked
6 37 Usabilit Appointme Appointme Appointme Appointment Pass
y Test nt cancel or nt cancel or nt should either
reject by reject by be either accepted or
doctor doctor accepted or rejected
rejected
7 38 Usabilit Admin Admin Doctor Doctor Pass
y Test approving approving should be approved or
or rejecting or rejecting approved rejected
doctors doctors or rejected
8 39 Load Testing Added System System Pass
Testing load of multiple should performs well
system numbers of perform
doctors, well
patients
and
appointmen
ts for demo
test

33
 CHAPTER 5: CONCLUSION AND FUTURE
RECOMMENDATION

5.1 Conclusion
The Doctor Appointment System is a free online tool that makes it easy to schedule
appointments with doctors. Since it works on any web browser, it is convenient to use.
The patients and doctors can easily signup in the system. The doctors need to be verified
by the admin so that they can schedule the appointments. The appointments scheduled by
the doctor are visible to the patients. The patients can choose the appointments. The
appointments that are chose by the patients are sent to the doctor who scheduled that
appointment for his/ her approval. The doctor has to either approve or reject the
appointments. The doctor can delete the past appointments. The admin is allowed to
delete the doctors. In this way the appointment scheduled, appointment booked,
appointment deleted and manage doctors are done which meets the objective of this
project.

5.2 Future Recommendations

Some of the features that can be implemented in the future are:
• Adding a variety of features for both doctors and patients.
• Adding payment gateway options.
• Making this system as a mobile application.

34
 APPENDICES
Home page:

Admin Dashboard:

Set Speciality:

35
After Setting Speciality:

Pending Doctor Request:

Verifying Doctors By Admin:

36
Admin Rejecting Doctor:

Doctor Dashboard:

Appointment Create:

37
Doctor Appointment Details:

Appointment Confirmation By Doctor:

History View By Doctor:

38
Doctor Profile:

Patient Dashboard:

39
Choose Appointment:

Confirmed Appointments:

Patient Profile

40
REFERENCE

[1] "Net Health," 16 September 2021. [Online]. Available: https://www.nethealth.com.

[Accessed 10 December 2024].
[2] "Online medical care appointment booking service," [Online]. Available:
https://www.wikiwand.com. [Accessed 10 12 2024].
[3] S. J. M. S. Akshaya KV, "Empowering Hospitals for Better Patient Care Through
Smart Management," Multidisciplinary Research, no. 06, 2024.
[4] "HealthPlix Review, Pros and Cons | ITQlilck," 06 2024. [Online]. Available:
https://www.itqlick.com/healthplix. [Accessed 10 12 2024].

41