FC6P01NT Final Year Project

Module Code & Module Title

FC6P01NT Final Year Project

Doctor Connect System (Web App)

Year and Semester

2019-20 Sixth Semester

Student Name: Sandipan Khadka

London Met ID: 17032104

College ID: NP05CP4S180015

Assignment Due Date: 5th June 2020

Assignment Submission Date: 5th June 2020

Internal Supervisor: Mr. Prakash Koirala

External Supervisor: Mr. Arun Acharya

FC6P01NT Final Year Project

Acknowledgement

I would like to express my sincere gratitude to the several individuals and organizations
for encouraging me, pushing me, and uplifting me throughout this whole period of study.
First of all, I would like to express my sincere gratitude to my supervisors Mr. Prakash
Koirala, primary supervisor and my secondary supervisor Mr. Arun Acharya for their
insightful comments, helpful pieces of information and proper guidance and assistance.
Their immense knowledge, profound experience, and professional expertise in Web
Development have enabled me to complete this report successfully. Without the support
and guidance from them, this report wouldn’t have been possible.

I am also thankful to the London Metropolitan University, as well as Itahari International

College for providing me such a wonderful learning platform with an adequate amount of
resources to use and apply for the completion of the project. Last but not least I would
like to thank my family members as well as friends for always supporting me, believing in
me and helping me, with their full potential, also to everyone enrolled in Computing
section in the Itahari International College, it was great sharing premises with all of you
during the last three years.
FC6P01NT Final Year Project

Abstract

A Web application is an application that is conjured with a Web program over the Internet.
Since the time 1994 when the Internet opened up to the general population and
particularly in 1995 when the World Wide Web put a usable face on the Internet, the
Internet has become a foundation of decision for an enormous number of always complex
and imaginative web applications. In an only multi-decade, the Web has advanced from
being an archive of pages utilized for getting to static, for the most part logical, data to an
incredible stage for application improvement and arrangement.

It has been right around three decades since the presentation of the administration of the
web, interim different related ideas like Service Oriented Architecture, Cloud Computing,
and the Internet of Things have been amalgamated to the area of electronic improvement.
However, the perspective on the administration of the web and the meanings of the
fundamental related ideas have not been enough refreshed. The thought behind the
conventional term "web application" and its definition doesn't cover the different kinds of
uses accessible nowadays, which use the administration of the web.

A web-based application is a system, with application components in a client-side

component that communicates with application components in a web server for preparing
information. They use the administration of the web on the client-server architecture,
request-response model, standard HTTP, and other related strategies and
advancements.

The developing system focuses on how to improve upon the efficiency and quality of
delivering a web based appointment system to reduce waiting time. Online doctor
appointment system is designed using HTML, CSS, JS & Bootstrap for the frontend,
Laravel framework for handling client-server request and MYSQL for the backend.
FC6P01NT Final Year Project

Table of Contents
CHAPTER 1: Introduction ............................................................................................... 1

1.1 Project Description ................................................................................................. 1

1.2 CURRENT SCENARIO .......................................................................................... 2

1.3 PROBLEM STATEMENT ....................................................................................... 4

1.4 PROJECT AS A SOLUTION .................................................................................. 5

1.5 AIMS AND OBJECTIVES ...................................................................................... 6

1.6 STRUCTURE OF THE REPORT ........................................................................... 7

1.6.1 BACKGROUND ............................................................................................... 7

1.6.2 DEVELOPMENT .............................................................................................. 7

1.6.3 TESTING AND ANALYSIS .............................................................................. 7

1.6.4 CONCLUSION ................................................................................................. 7

CHAPTER 2: BACKGROUND ........................................................................................ 8

2.1 ABOUT THE END USERS..................................................................................... 8

2.2 UNDERSTANDING THE SOLUTION .................................................................... 9

2.3 REVIEW OF SIMILAR SYSTEMS ....................................................................... 13

2.4 REVIEW OF SIMILAR PROJECTS ..................................................................... 18

2.5 REVIEW OF TECHNICAL ASPECTS .................................................................. 23

CHAPTER 3: DEVELOPMENT ..................................................................................... 25

3.1 CONSIDERED METHODOLOGIES .................................................................... 25

3.2 SELECTED METHODOLOGY ............................................................................. 30

3.2.1 Stages of Chosen Methodology ..................................................................... 31

3.2.2 Methodology stages ....................................................................................... 33

3.3 SURVEY RESULTS ............................................................................................. 61

3.3.1 PRE-SURVEY RESULTS .............................................................................. 61

FC6P01NT Final Year Project

3.3.2 POST-SURVEY RESULTS............................................................................ 62

3.4 CODE DEVELOPMENT....................................................................................... 63

CHAPTER 4: TESTING AND ANALYSIS...................................................................... 76

4.1: TEST PLAN ........................................................................................................ 76

4.1.1: UNIT TESTING, TEST PLAN ....................................................................... 76

4.2: UNIT TESTING ................................................................................................... 78

4.3 CRITICAL ANALYSIS ........................................................................................ 116

CHAPTER 5: CONCLUSION ...................................................................................... 117

5.1 LEGAL, SOCIAL AND ETHICAL ISSUES.......................................................... 117

5.1.1: LEGAL ISSUES .......................................................................................... 117

5.1.2: SOCIAL ISSUES ........................................................................................ 118

5.1.3 ETHICAL ISSUES ....................................................................................... 118

5.2 ADVANTAGES .................................................................................................. 119

5.3 LIMITATIONS .................................................................................................... 119

5.4 FUTURE WORK ................................................................................................ 120

CHAPTER 6: REFERENCES ...................................................................................... 121

CHAPTER 7: BIBLIOGRAPHY ................................................................................... 125

CHAPTER 8: APPENDIX ............................................................................................ 128

FC6P01NT Final Year Project

TABLE OF FIGURES

Figure 1 Online Doctor Appointment System .................................................................. 1

Figure 2 Current scenario of global appointment ............................................................ 2
Figure 3 Global appointment market ............................................................................... 3
Figure 4 Online Scheduling ............................................................................................. 5
Figure 5 Bumrungrad International Hospital .................................................................. 13
Figure 6 Hirslanden ....................................................................................................... 14
Figure 7 Nepal Mediciti.................................................................................................. 15
Figure 8 Norvic Hospital ................................................................................................ 16
Figure 9 Grande International Hospital.......................................................................... 17
Figure 10 Similar projects 1 ........................................................................................... 18
Figure 11 Similar project Mr Doc ................................................................................... 19
Figure 12 Similar project 3 ............................................................................................ 20
Figure 13 Similar project 4 ............................................................................................ 21
Figure 14 DSDM ........................................................................................................... 25
Figure 15 Scrum ............................................................................................................ 27
Figure 16 Iterative Model............................................................................................... 29
Figure 17 Use case of the doctor module...................................................................... 37
Figure 18 Use case of the admin module ...................................................................... 39
Figure 19 Use case of the patient module ..................................................................... 42
Figure 20 Installing composer ....................................................................................... 49
Figure 21 Installing Laravel ........................................................................................... 50
Figure 22 Running the project ....................................................................................... 51
Figure 23 Registration ................................................................................................... 52
Figure 24 User Login ..................................................................................................... 52
Figure 25 Admin Login .................................................................................................. 53
Figure 26 Doctor Login .................................................................................................. 53
Figure 27 Home Page ................................................................................................... 54
Figure 28 Doctors Page ................................................................................................ 54
Figure 29 Departments Page ........................................................................................ 55
FC6P01NT Final Year Project

Figure 30 News Page .................................................................................................... 55

Figure 31 Contact Page ................................................................................................ 56
Figure 32 Appointment-form.......................................................................................... 56
Figure 33 Online Payment Form ................................................................................... 57
Figure 34 Live Chat ....................................................................................................... 58
Figure 35 Live Chat of Gist ............................................................................................ 59
Figure 36 Admin Dashboard ......................................................................................... 60
Figure 37 Doctor Dashboard ......................................................................................... 60
Figure 38 Bootstrap Library ........................................................................................... 63
Figure 39 Auth Login & Registration.............................................................................. 63
Figure 40 Login-blade ................................................................................................... 64
Figure 41 Login Controller ............................................................................................. 65
Figure 42 Live Chat Integration ..................................................................................... 66
Figure 43 Online booking .............................................................................................. 66
Figure 44 Booking Controller ......................................................................................... 67
Figure 45 Online Payment............................................................................................. 68
Figure 46 Payment Integration ...................................................................................... 69
Figure 47 Appointment confirm mail .............................................................................. 70
Figure 48 Appointment Mail blade ................................................................................. 70
Figure 49 Mail Setup ..................................................................................................... 71
Figure 50 Payment & Appointment Confirmation Mail ................................................... 72
Figure 51 Payment Mail blade ....................................................................................... 72
Figure 52 Payment Mail Setup ...................................................................................... 73
Figure 53 Email Notification .......................................................................................... 74
Figure 54 Query Mail blade ........................................................................................... 74
Figure 55 Query Setup Mail .......................................................................................... 75
Figure 56 Proof of test case 1 ....................................................................................... 79
Figure 57 Proof of test case 2 ....................................................................................... 81
Figure 58 Proof of test case 3 ....................................................................................... 83
Figure 59 Proof of test case 4 ....................................................................................... 84
Figure 60 Proof of test case 4 ....................................................................................... 85
FC6P01NT Final Year Project

Figure 61 Proof of test case 4 ....................................................................................... 85

Figure 62 Proof of test case 5 ....................................................................................... 86
Figure 63 Proof of test case 5 ....................................................................................... 87
Figure 64 Proof of test case 6 ....................................................................................... 88
Figure 65 Proof of test case 6 ....................................................................................... 88
Figure 66 Proof of test case 7 ....................................................................................... 90
Figure 67 Proof of test case 7 ....................................................................................... 90
Figure 68 Proof of test case 8 ....................................................................................... 91
Figure 69 Proof of test case 9 ....................................................................................... 92
Figure 70 Proof of test case 10 ..................................................................................... 94
Figure 71 Proof of test case 11 ..................................................................................... 96
Figure 72 Proof of test case 11 ..................................................................................... 96
Figure 73 Proof of test case 11 ..................................................................................... 97
Figure 74 Proof of test case 12 ..................................................................................... 98
Figure 75 Proof of test case 12 ..................................................................................... 98
Figure 76 Proof of test case 12 ..................................................................................... 99
Figure 77 Proof of test case 12 ..................................................................................... 99
Figure 78 Proof of test case 13 ................................................................................... 101
Figure 79 Proof of test case 13 ................................................................................... 101
Figure 80 Proof of test case 13 ................................................................................... 102
Figure 81 Proof of test case 13 ................................................................................... 102
Figure 82 Proof of test case 14 ................................................................................... 103
Figure 83 Proof of test case 14 ................................................................................... 104
Figure 84 Proof of test case 14 ................................................................................... 104
Figure 85 Proof of test case 15 ................................................................................... 106
Figure 86 Proof of test case 15 ................................................................................... 106
Figure 87 Proof of test case 15 ................................................................................... 107
Figure 88 Proof of test case 16 ................................................................................... 108
Figure 89 Proof of test case 16 ................................................................................... 109
Figure 90 Proof of test case 16 ................................................................................... 109
Figure 91 Proof of test case 17 ................................................................................... 111
FC6P01NT Final Year Project

Figure 92 Proof of test case 17 ................................................................................... 111

Figure 93 Proof of test case 17 ................................................................................... 112
Figure 94 Proof of test case 17 ................................................................................... 112
Figure 95 Proof of test case 17 ................................................................................... 112
Figure 96 Proof of test case 18 ................................................................................... 113
Figure 97 Proof of test case 18 ................................................................................... 113
Figure 98 Proof of test case 18 ................................................................................... 113
Figure 99 Proof of test case 18 ................................................................................... 113
Figure 100 Proof of test case 18 ................................................................................. 113
Figure 101 Proof of test case 19 ................................................................................. 114
Figure 102 Proof of test case 19 ................................................................................. 114
Figure 103 Proof of test case 19 ................................................................................. 115
Figure 104 Proof of test case 19 ................................................................................. 115
Figure 105 Client Approval letter ................................................................................. 128
Figure 106 Context Level diagram .............................................................................. 131
Figure 107 Data flow diagram ..................................................................................... 133
Figure 108 Use Case diagram .................................................................................... 135
Figure 109 Cardinality & Ordinality .............................................................................. 137
Figure 110 ERD Diagram ............................................................................................ 137
Figure 111 Relationship types ..................................................................................... 139
Figure 112 Class diagram ........................................................................................... 140
Figure 113 Pre survey form ......................................................................................... 148
Figure 114 Pre survey form ......................................................................................... 148
Figure 115 Pre survey form ......................................................................................... 149
Figure 116 Pre survey form ......................................................................................... 149
Figure 117 Pre survey form ......................................................................................... 150
Figure 118 Pre survey form ......................................................................................... 150
Figure 119 Pre survey form ......................................................................................... 151
Figure 120 Pre survey form ......................................................................................... 151
Figure 121 Pre survey form ......................................................................................... 152
Figure 122 Pre survey form ......................................................................................... 153
FC6P01NT Final Year Project

Figure 123 Pre survey form ......................................................................................... 154

Figure 124 Pre survey form ......................................................................................... 155
Figure 125 Post survey form ....................................................................................... 156
Figure 126 Post survey form ....................................................................................... 157
Figure 127 Post survey form ....................................................................................... 158
Figure 128 Post survey form ....................................................................................... 158
Figure 129 Post survey form ....................................................................................... 159
Figure 130 Post survey form ....................................................................................... 159
Figure 131 Post survey form ....................................................................................... 160
Figure 132 Post survey form ....................................................................................... 161
Figure 133 WBS .......................................................................................................... 162
Figure 134 Gantt Chart................................................................................................ 163
Figure 135 Wireframes ................................................................................................ 167
Figure 136 Wireframes ................................................................................................ 168
Figure 137 Wireframes ................................................................................................ 168
Figure 138 Wireframes ................................................................................................ 169
Figure 139 Wireframes ................................................................................................ 169
Figure 140 Wireframes ................................................................................................ 170
Figure 141 Wireframes ................................................................................................ 170
Figure 142 Wireframes ................................................................................................ 171
Figure 143 Wireframes ................................................................................................ 171
Figure 144 Wireframes ................................................................................................ 172
Figure 145 Wireframes ................................................................................................ 172
Figure 146 Wireframes ................................................................................................ 173
Figure 147 Wireframes ................................................................................................ 173
Figure 148 Wireframes ................................................................................................ 174
Figure 149 Wireframes ................................................................................................ 174
Figure 150 Wireframes ................................................................................................ 175
Figure 151 Wireframes ................................................................................................ 175
FC6P01NT Final Year Project

TABLE OF TABLES

Table 1 Proposed System ............................................................................................. 22

Table 2 All User Stories................................................................................................. 45
Table 3 Sprint 1 ............................................................................................................. 46
Table 4 Sprint 2 ............................................................................................................. 46
Table 5 Sprint 3 ............................................................................................................. 46
Table 6 Sprint 4 ............................................................................................................. 47
Table 7 Sprint 5 ............................................................................................................. 47
Table 8 Sprint 6 ............................................................................................................. 47
Table 9 Sprint 7 ............................................................................................................. 47
Table 10 Sprint 8 ........................................................................................................... 48
Table 11 Sprint 9 ........................................................................................................... 48
Table 12 Sprint 10 ......................................................................................................... 48
Table 13 Unit Testing .................................................................................................... 77
Table 14 Test Case 1 .................................................................................................... 78
Table 15 Test Case 2 .................................................................................................... 80
Table 16 Test Case 3 .................................................................................................... 82
Table 17 Test Case 4 .................................................................................................... 84
Table 18 Test Case 5 .................................................................................................... 86
Table 19 Test Case 6 .................................................................................................... 87
Table 20 Test Case 7 .................................................................................................... 89
Table 21 Test Case 8 .................................................................................................... 91
Table 22 Test Case 9 .................................................................................................... 92
Table 23 Test Case 10 .................................................................................................. 93
Table 24 Test Case 11 .................................................................................................. 95
Table 25 Test Case 12 .................................................................................................. 97
Table 26 Test Case 13 ................................................................................................ 100
Table 27 Test Case 14 ................................................................................................ 102
Table 28 Test Case 15 ................................................................................................ 105
Table 29 Test Case 16 ................................................................................................ 107
FC6P01NT Final Year Project

Table 30 Test Case 17 ................................................................................................ 110

Table 31 Test Case 18 ................................................................................................ 112
Table 32 Test Case 19 ................................................................................................ 114
Table 33 Users Table .................................................................................................. 141
Table 34 Admins Table ............................................................................................... 141
Table 35 Doctors Table ............................................................................................... 142
Table 36 Bookings Table............................................................................................. 143
Table 37 Departments Table ....................................................................................... 143
Table 38 Payments Table ........................................................................................... 144
Table 39 Queries table ................................................................................................ 145
FC6P01NT Final Year Project

CHAPTER 1: Introduction
1.1 Project Description
A web application is a computer program that uses internet browsers and web technology
to perform undertakings over the web. A large number of organizations utilize the Internet
as a cost-effective communication channel. It lets them trade data with their objective
market and makes quick, secure exchanges. Web applications utilize a mix of server-side
contents (PHP and ASP) to deal with the capacity and recovery of the data, and customer
side contents (JavaScript and HTML) to introduce data to users. (Gibb, 2016)

An online doctor appointment system is a system through which a user or visitor or just,
patients can get to the website, and through the online website, patients can without much
of a stretch make their appointments. Other than that, patients can likewise provide extra
information to the doctor regarding his/her problems, making the doctor aware of the
patients’ situation and giving the doctor enough time to be prepared up when the patients
come to visit. This system helps people to easily & securely book an appointment with
the doctor of his/her choice online. An online doctor appointment system is a modern way
of dealing and arranging appointments over the internet. The system helps to save the
time of the patients as they don’t have to go through long queues to visit a doctor. As
compared, to the manual appointment system where the registration is done in paperwork
& the patient waiting time is not constant, online doctor appointment system provides
comfort, flexibility and promotes patient satisfaction. (Akinode John Lekan, 2017)

Figure 1 Online Doctor Appointment System

1|Page Sandipan Khadka

FC6P01NT Final Year Project

1.2 CURRENT SCENARIO

The online doctor appointment system in setting to the global market is a moderately new
idea. Medical services & health care is changing with a new emphasis on patient-
centeredness. Key to this change is the expanding acknowledgment of patients' role in
health care & medicinal services. Online doctor appointment system is going through
major changes focusing on the customer’s satisfaction and is experiencing significant
advancements towards involvement of more active patients. As internet being a medium,
patients have more choices and given more opportunities regarding the decision making
about the appointments and the improved access. Lots of positives is seen in online
scheduling system as the adoption of the system has brought massive changes in the
customer satisfaction, reduction in waiting time & flexibility. Patients satisfaction with
appointment booking is influenced by their ability to book at the right time with the right
health service providers. (David Miller, 2017)

Figure 2 Current scenario of global appointment

2|Page Sandipan Khadka
FC6P01NT Final Year Project

Figure 3 Global appointment market

3|Page Sandipan Khadka

FC6P01NT Final Year Project

1.3 PROBLEM STATEMENT

If a person is sick and if the person wants to visit a doctor for a checkup then the certain
doctor the person wants to meet, needs to be available. The person also has to wait in a
long queue while getting an appointment, and the appointment with the doctor may also
be canceled sometimes because of various reasons. Even if the person meets the doctor,
the person has to go through different kinds of unnecessary tests, even with all of these
the person isn’t fully satisfied with the services they provide. Visiting a doctor manually is
a lot of hard work and time taking, no patient wants to spend hours waiting to book an
appointment or visit a doctor. Sick patients want to be attended to as quickly as they come
into the clinic/hospital.

The survey conducted for the development of the online doctor appointment system
suggested that the end-users largely struggled in visiting the doctors manually and they
find it time costing and ineffective. End users want no compromise in the quality of health
services and they don’t want to wait in a long queue for visiting the doctor every single
time. MedArt provides quality health services and offers a good reminder of booking
appointments whenever a patient makes an appointment for a particular doctor.

The recent statistics show that the total number of population of Nepal is 28.61 million
approximately as of 2019, whereas the total number of doctors in Nepal is over 16432. In
which over 67% are male doctors and the rest of them are female. The doctor to
population ratio for the whole country is 1.1724. This demographic structure implies that
there is one doctor for every 150000 people and most of the doctors are not easily
approachable for the majority of Nepalese. (Shankar, 2017)

4|Page Sandipan Khadka

FC6P01NT Final Year Project

1.4 PROJECT AS A SOLUTION

With the system, it simplifies everything. Life is becoming too busy to get medical
appointments in person to person and to visit hospitals and hospitals for medical
checkups. MedArt contains a sorted and verified database of doctors, so the patients can
book an appointment anywhere and anytime with the doctor of his/her choice. In the
system, patients get ample options to choose from and ensures easy accessibility.

The main purpose of this system is to provide comfort and an easy environment for all
those patients while getting an appointment with the doctor and to solve the struggles
patients have to face while making an appointment. With all the features in the system,
patients don’t need to stress out for searching doctors, waiting in a queue, and going
through different kinds of tests. Patients can just choose the doctor, make an appointment
with the doctor of his/her choice with ease and any person can use this system by just
having a good internet connection.

The solutions delivered by the MedArt eliminate the gap between patients and doctors.
Users can just book an appointment from wherever and whenever they want to, with their
own choice of the doctor. Overall, the system overcomes the issues of the manual
appointment system, which every user has to go through while going through a medical
checkup.

Figure 4 Online Scheduling

5|Page Sandipan Khadka

FC6P01NT Final Year Project

1.5 AIMS AND OBJECTIVES

This project aims to simplify health care services for the user by reducing the worries of
finding a doctor. For instance, a person has to go wait for long queues of line or go through
various kinds of unnecessary tests, checkups for a particular problem. Sometimes the
doctor may not be available as per the time slots of him/her, or the doctor may not have
enough information about his/her problems. The S.M.A.R.T objectives include:

1 S:-Specific

The particular target set to meet this project aims to gather much-needed skills and
knowledge in the laravel framework to develop a fully functioning prototype of the system.
Gaining required skills in the framework and enough knowledge in HTML, CSS would
help attain the required set of objectives.

2 M:- Measurable

To keep track of the progress, the following project is divided in the form of sprints. Each
sprint lasts 10-15 days, with each sprint containing multiple tasks.

3 A: Attainable

Cost analysis and feasibility study are carried out in the earlier step, these studies are
undertaken to deliver what was promised.

4 R: Relevant

Surveys were conducted regarding the system’s features, possibilities, and market
opportunities. Positive responses were received regarding the system’s overall features
and possibilities of making a mark in the market.

5 T: Time Based

Last but not least, the project is needed to be completed in a given time. Time has been
pre-defined and the goals have been divided accordingly.

6|Page Sandipan Khadka

FC6P01NT Final Year Project

1.6 STRUCTURE OF THE REPORT

1.6.1 BACKGROUND
The background of this report gives an understanding of the end clients, data identified
with the arrangement, examinations made against similar systems and projects, and a
review of the technical aspects.

1.6.2 DEVELOPMENT
The development section gives insights regarding the considered methodologies and the
chosen methodology for the project alongside a couple of cuts of the coding.

1.6.3 TESTING AND ANALYSIS

The testing area of this report gives insights regarding the tests directed for this project.
It shows cases of the experiments and characterizes their pertinence in the project.
Though, the examination area gives a breakdown of the developed prototype concerning
user feedback.

1.6.4 CONCLUSION
The end segment of this report gives a review of the things gave before along the
legitimate, social, and moral issues that could be looked at by the online doctor
appointment system. This segment additionally examines the conceivable future options
for the online doctor appointment system.

7|Page Sandipan Khadka

FC6P01NT Final Year Project

CHAPTER 2: BACKGROUND
2.1 ABOUT THE END USERS
The focus on the gathering of end clients contains the overall population who are more
expertise in utilizing the web and who are going or enduring something and need a
superior arrangement of it, utilizing the innovation.

In a conducted survey, a retrospective study of a web-based appointment system had

been done where users were asked lots of questions about the problems they are facing
and what can be improved or what solutions can be implemented in the related field. End-
users seem to be more impressed with the facility of making an appointment with the
doctors of his/her choice whenever and wherever they want rather than waiting in a long
queue for visiting a doctor. Users were least satisfied with the waiting times.

Even though the online doctor appointment system is new in the market the fame and
development of the business have been truly elevated, among the users. On the off
chance that if a user is searching for an ophthalmologist, they simply scan for them on
the website, checks the reviews of different users, and select a perfect one appropriate
for them. The user can then simply book an appointment for a given day and time to
guarantee the least holding up time and get the administration they require. End-users
need accommodation, calm and solid condition while the need to look for a doctor/make
a meeting with a doctor.

8|Page Sandipan Khadka

FC6P01NT Final Year Project

2.2 UNDERSTANDING THE SOLUTION

The emergence of this online appointment system and its services are helpful for all
individuals to save time as well as helps in reducing human effort. The registration system
in most of the cases is the paperwork which is hard-work, inconvenient, and not a good
approach in dealing with the patients.

Waiting time

Waiting time is defined as the total time from registration until consultation with a doctor.
Patients waiting time the length of time from when the patient entered the hospital to the
time the patient contracting the doctor at OPD. A patient's experience in waiting time will
radically influence his/her perceptions of the quality of the service. Waiting can be
irritating, frustrating and a source of great uncertainty. (Melesse Belayneh, 2015)

Patients Appointment System

A patient appointment system or appointment schedule for the health care center started
a long time ago. Management of patient appointments has earlier works and has
developed simplified queuing models and fairly static scheduling conditions. Another
attempt was made to calculate the waiting time between patient and doctor using the
mathematical queuing models to minimize waiting time. However, traditionally the
appointment system has considered that the doctor's time is more important than patient
time. So an appointment system was designed to minimize the doctor idle time but current
designing of an appointment system is based on decisive factors concerning both the
patient and doctor. (Md. Maharaz Hossain, n.d.)

9|Page Sandipan Khadka

FC6P01NT Final Year Project

Appointment Delay
Past research shows that the longer the appointment delay which is defined as the time
between the day a patient requests an appointment and her actual appointment date, the
higher the chances that he/she will cancel or not show up (Gallucci et al. 2005). (Murray,
2000)

Scheduling

Scheduling can be described as the process of assigning jobs to resources for some
duration. Scheduling problems are ubiquitous, ranging from computer systems and
networks to production factories and patient appointments. (Akinode John Lekan, 2017)

Types of Appointment Scheduling

There are different types of appointment scheduling tactics, each has its pros and cons.

Open Office Hours – Patients will be seen by the physician in the order of their arrival.
This way the physician doesn’t have to worry about a patient breaking an appointment or
the office running behind the schedule. Many urgent care clinics and emergency rooms
run on this type of scheduling system.

Scheduled Appointments – This is the easiest way to schedule patients without long wait
times. Since different procedures require different amounts of time, the medical assistant
should be familiar with different types of procedures and the duration of the visit needed.

Flexible Office Hours – evening and weekend hours may be available for those that are
unable to see the physician during regular office hours. (Elley, 2017)

10 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

Overview of the system

MedArt is launched as an important component of scheduling and managing

appointments, the proposed system advances with online facilities that eliminate the
chaos of traditional appointment services.

First of all users need to login to book an appointment, users can select a particular doctor
of a particular department, and then can select a preferred date and time to book an
appointment. Users can even pay online if he/she wants to, or can also directly book an
appointment without following the payment procedure. The doctors and patients are
handled by the admin, admin allows the patient to register and search the doctors as per
the patient's criteria. Admin provides the doctor’s details and everything to the patients,
in which patients books an appointment by selecting a favorable time and schedule. The
doctor logs in and confirms the booking as this whole process is done in a quick
succession of time.

11 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

Block diagram
A block diagram is a diagram of a system in which the principal parts or functions are
represented by blocks connected by lines that show the relationships of the blocks.

Login

Doctor Admin Patient

Confirms
Reply Messages Send Messages
appointments

Add/Update &
Checks Payment Chooses a doctor
Delete

Appointment

Payment

Appointment Appointment
confirmed still pending

12 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

2.3 REVIEW OF SIMILAR SYSTEMS

1. Bumrungrad International Hospital
Founded in 1980, Bumrungrad International Hospital has been a global pioneer in
providing world-class health care services and international patient support for nearly four
decades. Bumrungrad is an internationally accredited, multi-specialty hospital listed on
the Stock Exchange of Thailand since 1989. (Bumrungrad, 2020)

Figure 5 Bumrungrad International Hospital

13 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

1. Hirslanden Swiss Hospital Group

The Hirslanden Private Hospital Group was formed in 1990 from the merger of several
private hospitals. The company is synonymous with first-class medicine. (Hirslanden,
2020)

Figure 6 Hirslanden

14 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

2. Nepal Mediciti

Nepal Mediciti is one of the largest private hospitals with super-specialty treatment
services in Nepal. Covering a huge span of land with the capacity of 700+ beds, and
the features include chat-session, best ambulance service, good quality health
services and online appointment with the doctors. (Nepalmediciti, 2020)

Figure 7 Nepal Mediciti

15 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

3. Norvic International Hospital

Norvic International Hospital is one of Nepal’s leading multi-specialty hospital and is

known as the country’s best critical care hospital with the prestigious Global Green &
Healthy Hospital(GGHH) membership certification. Norvic International Hospital
provides high-quality medical services, offers cost-effective treatment and is known
for widely experienced professionals. (Norvichospital, 2020)

Figure 8 Norvic Hospital

16 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

4. Grande International Hospital

Grande International Hospital(GIH), located in Dhapasi, Kathmandu Nepal provides

patient-centric healthcare, from acute critical care to rehabilitation to transitional care
to home healthcare services. The hospital provides best health care facility offering a
wide range of medical, surgical and diagnostic services. (Grandehospital, 2020)

Figure 9 Grande International Hospital

17 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

2.4 REVIEW OF SIMILAR PROJECTS

1) Online Patient Scheduling System by Samiha Tabassum Haque

Samiha Tabassum Haque of Asia Pacific University presented a report of an online

patient scheduling system that aims for health care institutions that would ease off the
appointment-scheduling journey for users and pave the path of a better doctor-patient
experience. The proposed system advances with online facilities that eliminate the chaos
of traditional appointment services. This system offers online appointment booking, to
view doctors list, to cancel and update appointments with an administrative portion to
manage all the sections. (Haque, 2017)

Figure 10 Similar projects 1

18 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

2) Mr. Doc A Doctor Appointment Application System by Shafaq Malik, Nargis Bibi,
Sehrish Khan, Razia Sultana, Sadaf Abdul Rauf

Shafaq Malik, Nargis Bibi, Sehrish Khan, Razia Sultana and Sadaf Abdul Rauf of Fatima
Jinnah Women University, presented a report of Mr. Doc: A Doctor Appointment
Application System whose main purpose is to provide ease and comfort to patients while
taking an appointment from doctors and it also resolves the problems that the patients
has to face while making an appointment. The android application [Link] acts as a client
whereas the database containing the doctor’s details, patient’s details, and appointment
details are maintained by a website that acts as a server. (Shafaq Malik, 2017)

Figure 11 Similar project Mr Doc

19 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

3) Secure web application for Online Doctor Appointment System by Nikith P

Nikith P presented a report of a secure web application for an online doctor appointment
system. Online Doctor Appointment is a smart web application, this provides a registration
and login for both doctors and patients. The doctor can register by giving his necessary
details like timings, fees, categories, etc. After successful registration, the doctor can log
in by giving username and password. The doctor can view the booking request by patients
and if he/she accepts the patient requests the status will be shown as booking confirmed
to the patient. He/she can also view the feedback given by the patient. The patients must
be registered and log in to book a doctor basing the category and the type of problem the
patient is facing and the location. (P, 2018)

Figure 12 Similar project 3

20 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

4) Online Polyclinic Appointment and Database management system by

Maryam Tufail

Maryam Tufail of Tampere University of Applied Sciences presented a report of online

polyclinic appointments and database management systems. The purpose of
implementing this application was to create a system through which a patient can
easily compare, choose, and make an online appointment for a doctor just by sitting
at home. Replacing manual medical file keeping system with the online database
management system. (Tufail, 2018)

Figure 13 Similar project 4

21 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

COMPARISON OF THE DEVELOPED SYSTEM WITH THE SIMILAR

SYSTEMS/PROJECTS

1) Similar Systems/Projects

These are all the features/functionalities that are included in similar systems/projects.

 Online Appointment/Booking
 Live Chat
 Asking queries/discussions
 Emergency Services
 Helipad Services
 Ambulance Services
 Emergency Services

2) Developed System/Project

Features mentioned Features Included Included Unique Remarks

above Feature
Online Appointment Online Appointment Online Payment
Live Chat Live Chat
Asking/Sending queries Asking/Sending queries
Emergency Services Emergency Services
Helipad Services
Ambulance Services Ambulance Services
Emergency Services Emergency Services
Table 1 Proposed System

22 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

2.5 REVIEW OF TECHNICAL ASPECTS

To complete the project different technical aspects were required and some of the used
resources are:

1. Programming Language

PHP 7.3 is the used programming language for the development of the proposed system.
The following programming language is selected because of its simplicity, security,
flexibility, and a large number of support of major protocols such as POP3, IMAP, and
LDAP. It’s a server-side scripting language that is embedded in HTML which is useful in
managing dynamic contents, databases, session tracking and even useful in building e-
commerce sites. (tutorialspoint, 2020)

2. Framework

The selected framework is Laravel 6.7 because of its elegant and simple syntax which
makes the development portion very much enjoyable and easy for the developers. One
of the major benefits of using the laravel framework is the implementation of
authentication very straightforward and simple. Moreover, it is an open-source PHP
framework, that is based on MVC architecture and its inbuilt functions like authentication,
routing session and caching makes this framework so popular, lightweight and elegant.
(TatvaSoft, 2016)

3. Text Editor

Sublime text is used text editor for the development of the project. It is used because it
supports many programming as well as markup languages and is a proprietary, cross-
platform text editor used widely. It is available in Windows, Mac as well as Linux. (Kinder,
2013)

23 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

4. Plugins

Some of the used plugins for the development of the project are [Link] and Counter-
Up. [Link] plugin is a JavaScript library for data visualization which supports different
varieties of graphs, charts, bars, and many more. Counter-Up is a jquery plugin that
counts up to the given targeted number when it becomes visible.

5. Classes

Classes like validator, request, controller, DB, session, etc have been used during the
development of the project. Validator is used for the validation of the incoming data from
the HTTP request. The request is used for getting an instance of the current HTTP request
with the help of dependency injection, the controller is used for request handling logic in
a class. DB is used for making a connection with the database and performs actions
related to it. A session is used for storing the related information within the requests.

6. Packages

Packages like ui and auth have been used. In laravel 6 auth command is not defined so
ui and auth will be used for generating views like login, registration, home and other
password resets blades. Based on the guard's users will be authenticated with their
respective login credentials with the help of auth.

24 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

CHAPTER 3: DEVELOPMENT
3.1 CONSIDERED METHODOLOGIES
Dynamic Systems Development technique(DSDM)

DSDM is an agile software development approach that provides a framework for building
and maintaining systems. The DSDM comprises of 5 step lifecycle activities:

(Gupta, 2019)

Figure 14 DSDM

25 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

a) Feasibility Study:
A feasibility study is carried out with certain business necessities and constraints
and making sure the application is viable following the DSDM method.
b) Business Study:
In this stage, the identification of business aspects of the project takes place.
c) Functional Model Iteration:
In this stage, the production of a prototype is done referred to as the client, client
feedbacks are collected as they exercise the paradigm.
d) Design and Build Iteration:
This stage makes sure that the designed prototype is useful and has been
designed that supply operational business prices for users.
e) Implementation:
In this stage, places the code(prototype) into operational surroundings, here the
product as a whole will get operational. ([Link], 2019)

26 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

Scrum

Scrum is a framework that helps teams work together, and implementation of agile in
which process is broken down into smaller pieces. Planning occurs at first then we build
what was planned, testing, and review is done after that a potentially shippable product
is released. This cycle repeats with the time of 1 to 3 weeks and continues, again and
again, these incremental releases are called sprints. (Drumond, 2019)

Figure 15 Scrum

27 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

In Scrum 3 key roles are needed for this framework to work.

1. Product Owner – The person who is responsible for defining the features that are
needed in the project.
2. Scrum Master – The person who is responsible for protecting the team, servant
leader of the team, and makes sure that all the things keep going.
3. Team – Team is made of developers, testers, and many more who help in building
a product.

3 artifacts are used in scrum

1. Product Backlog – Here, the product owner prioritizes the list of features known as
user stories, that could go into the product. User stories are the list of the features
that the user needs, this set of list helps the product owner to estimate everything
for the team.
2. Sprint Backlog – The highest priority of user stories goes into this sprint backlog.
3. Burndown Chart – Burndown Chart shows the progress during the sprint and the
ongoing process.

3 ceremonies make up the scrum

1. Sprint Planning – Here, product owner, scrum master, and team meet to discuss
the user stories and analyze the sizes of it.
2. Daily Scrum – It’s a meeting where the team discusses where the work is going on
and where it is heading towards and any obstacles bothering them.
3. Sprint Review and retrospective – It occurs at the end of the sprint, where the team
demonstrates the completed work to the product owner and they discuss what they
can do to improve the situation while going forward.
(Drumond, 2019)

28 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

Iterative Model

An Iterative Model, the iteration process starts from the small set of the software
requirements, and iteratively continues to evolve until the complete system is
implemented and ready to be deployed. In the iterative model, the whole system is not
built but the requirements are further enhanced in every iteration. The product is then
repeated, producing a new working software at the end of each iteration. Iterative and
Incremental development is a combination of both iterative design and incremental build
for development. (Tutorialspoint, 2019)

Figure 16 Iterative Model

(Powell-Morse, 2016)

29 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

3.2 SELECTED METHODOLOGY

After proper analysis and considerations of all the mentioned development
methodologies, scrum feels the right methodology to build up this project, as its principles
and lessons can be applied to all the kinds of the framework. This is also one of the main
reasons for scrum being popular. As an agile project management framework, scrum
describes a set of meetings, tools, and roles that work to help teams structure and
manage the work.

Development Reason

Agile methodologies(Scrum) are followed up for building this project, cause that they have
overcome the traditional methods of the waterfall model and they are considered as
flexible, fast, can be adaptable to the change and follows the method or practice that help
in getting high-quality software very quickly. (360logica, 2019)

Scrum is a lightweight, agile project management framework. It is simple to use and

allows a lot of flexibility. It is also becoming popular and most widely used methodology
nowadays. (OnGraph Technologies, 2016)

Project Analysis Reason

Traditional business tactics today are no longer beneficial as rapid changes occur in every
business, project requirements and these fast changing products need a right amount of
flexible approach. That’s the reason why software development teams are more inclined
towards flexibility that scrum methodology provides, which helps in coping up with the
changes rapidly. (OnGraph Technologies, 2016)

30 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

Result Analysis Reason

For a feature to be considered complete, it needs to be Analyzed, Designed, Coded,

Tested, Refactored, and Documented. If this life-cycle is not fully accomplished during
the sprint, perhaps due to an initial underestimation of the time required, the feature will
be pushed to a later sprint. (Adams, 2010)

3.2.1 Stages of Chosen Methodology

Here the distinct phases are explained in much detail, which can be included in the
website.

Pre-project

First of all, the project goes through the initial pre-project phase, where the most important
things are discussed before the project starts.

1) What is the problem to be solved?

2) For whom do we solve this problem?

3) How success will be measured?

31 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

Project Initiation

This is the phase where we set all the goals, requirements, and technologies used.

The teams will be formed in this phase and all the procedures related to the team meeting,
communication. The team should communicate with the client for a better understanding
of the project and to make it more effective. Sprint planning will also be done in this phase.

Iterative sprints

With the first phase of iteration, each time new things should integrate as each
iteration/sprints starts:

Sprint Planning

 A key discussion with the client is necessary before the start of the sprint.
 Having the idea of user-stories, prioritizing them and discussing them with the
client is necessary
 Based on user stories/ only the prioritized ones should be given emphasis and
should have the idea of what to develop in the next upcoming sprint.

Development

 Here we start writing codes based on user stories.

(Cara Rudnic, 2017)

Testing

 The developed function should be checked to ensure that it works properly and
developed correctly.

32 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

As with the completion of coding, the testing function will be carried out, if any errors or
bug is found in the system then the sprint plan needs to be changed to remove the bug.

At the end of each sprint whole the team discusses how the sprint went, to check whether
it has been fruitful or not, and how to improve, if certain things didn’t work out as planned.

If certain features, implementation or testing works out in the same manner as of planned
then the following is documented to the client. (Cara Rudnic, 2017)

3.2.2 Methodology stages

Pre-project

First of all, the project goes through the initial pre-project phase, where the most important
things are discussed before the project starts.
1. What is the problem to be solved?
The problem to be solved is to randomly stop waiting in a queue while making an
appointment, with the help of this proposed system.

2. For whom do we solve this problem?

For the client which is the hospital and the patients who will use this system.

3. How success will be measured?

Agile development methodology will be used and different tests will be measured at a
certain period.

33 | P a g e Sandipan Khadka
 FC6P01NT Final Year Project

Project Initiation

System Requirement analysis

For any software development, the initial phase is to conduct a demand analysis. Demand
analysis is the process of discovery, refinement, modeling, specification, and review.

Functional Requirements

Based on the research conducted for the proposed system, there are two sets of functions
for an online doctor appointment system.

Registration &
Select Department Select Doctor
Log in

Appointment Appointment Time Appointment Date

YES NO
Payment

Appointment Appointment
confirmed still pending

34 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

The next set of functions is data management that allows the database administrator to
add, delete, and modify the data.

Appointment System

Database Management

Addition Modification Deletion

The whole system is composed of 3 different modules.

1) Doctor
2) Admin
3) Patient

35 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

Doctors

Doctors need to be registered in the system and should log in to view the details and
information related to the patients and can take action regarding the patient's approval
and appointment requests.

Algorithm of the doctor module

Step 1: Start

Step 2: Login

Step 3: Manage Appointments

Step 4: Logout

Step 5: End

Flowchart of the doctor module

Start Login Manage

Appointments

Logout

End

36 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

Use case of the doctor module

Figure 17 Use case of the doctor module

37 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

Admin

Admin can view the registered details of the patients and the doctor and can modify, add,
or delete if needed. Overall, the admin has the authority to control both the patients and
doctor and can take some set of actions if needed.

Algorithm of the admin module

Step 1: Start

Step 2: Login

Step 3: Manage Patients/Doctors

Step 4: Send Notifications

Step 5: Logout

Step 6: End

Flowchart of the admin module

Start Login Manage

Patients/Doctors

Send
Notifications

End Logout

38 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

Use case of the admin module

Figure 18 Use case of the admin module

39 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

Patient

Patient – Patient needs to register and log in so that he/she can view and select the doctor
of his/her choice and make an appointment. He/she can also share the problems via the
messaging session, whereas the doctor confirms the booking request and performs the
next necessary steps of action.

Algorithm of the patient module

Step 1: Start

Step 2: Login

Step 3: Ask/Share via messaging session

Step 4: Choose the doctor

Step 5: For booking an appointment, patient can either pay and book or just simply book
without paying.

Step 6: If payment is yes, then the appointment is confirmed else the appointment is still
pending yet to be confirmed.

Step 7: End

40 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

Flowchart of the patient module

Start Login Ask/Share Via

Messaging

Choose the
doctor

Appointment

YES Payment NO

Appointment Appointment
confirmed still pending

Logout

End

41 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

Use case of the patient module

Figure 19 Use case of the patient module

42 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

Iterative sprints

With the first phase of iteration, each time new things should integrate as each
iteration/sprints starts:

Sprint Planning

User Story ID As a <type of I want to <perform so that I can

user> some task> <achieve some
goal>
1 Patient Search the doctor Select the best
based on some appropriate doctor.
criteria.
2 Patient View all the Check to ensure
upcoming whether I have to
appointments. attend a hospital.
3 Patient Share some So that I have the
problems or health better idea of health
issues to the doctor problems I am
via messaging. going through and
get proper advice.
4 Patient Make sure the So that I wont have
appointment is to call or visit.
online.
5 Patient See the results of So that I have the
past visits. basic idea to cure
my illness.
6 Patient Be notified So that I wont have
whenever to come to visit
appointment is hospital.
cancelled.

43 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

7 Patient Cancel an So that I can

appointment. reschedule it for
next day.
8 Patient, Doctor Check my personal To make sure that
information. all the provided
information is
correct.
9 Patient, Doctor Change the To make sure that
personal the information is up
information to date.
whenever needed.
10 Patient Contact the clinic. If any issues arises.

11 Doctor See the todays So that I have the

appointment. idea of patients
coming.
12 Doctor Have a view on To have the idea of
upcoming future patients who
appointments. will visit.
13 Doctor See the approval Respond and give
messages of the advices based on
patients. the health issues to
the patients.
14 Doctor To give result of the So that patients
visit have idea about
their health issues.
15 Doctor Add a holiday So that patients
cant book an
appointment on that
particular day.

44 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

16 Admin Views the pending So that confirmation

requests of booking is done.
17 Admin Can Check the So that update and
registration details deletion can be
done.
18 Admin Can register So that any
functionalities
needs to perform or
some actions to
take.
19 Admin Display the holidays So that patients
have idea of
particular day.
20 Admin Create an account To add doctors and
of patients and give the patients
doctors access to the
website
21 Admin Notify patients if So that they don’t
appointment is have to come.
cancelled
22 Admin Can add a holiday So that patients
of clinic or patients cant make an
appointment that
day
Table 2 All User Stories

45 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

Based on the project, the whole development is divided into sprints, and each sprint lasts
15 days while the last sprint is of 13 days. Sprint plan of task division and completion is
carried out in the following manner:

Sprints
Task Name Start End Days
Sprint 1 5 20 15
Installation, Setup & other 5 11 6
Understanding Framework 12 20 8
Table 3 Sprint 1

Task Name Start End Days

Sprint 2 21 5 15
Wireframes 21 26 5
System design 27 1 5
Flowchart & other 2 5 3
Table 4 Sprint 2

Task Name Start End Days

Sprint 3 6 21 15
Customize Homepage 6 11 5
UI design 12 17 5
Final design 18 21 3
Table 5 Sprint 3

46 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

Task Name Start End Days

Sprint 4 22 6 15
Login & Registration 22 29 7
Database Integration 30 3 4
Roles Setup 4 6 2
Table 6 Sprint 4

Task Name Start End Days

Sprint 5 7 22 15
Admin Login 7 13 6
Registration 14 17 3
Modification 18 22 4
Table 7 Sprint 5

Task Name Start End Days

Sprint 6 23 10 10
Live Chat 23 2 7
Appointment Form 3 6 3
Contact Form 7 10 3
Table 8 Sprint 6

Task Name Start End Days

Sprint 7 11 26 15
Admin Dashboard 11 17 6
Doctor Login 18 20 2
Doctor Dashboard 21 26 5
Table 9 Sprint 7

47 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

Task Name Start End Days

Sprint 8 27 11 15
Booking 27 1 5
Query 2 6 4
Contact Page 7 11 4
Table 10 Sprint 8

Task Name Start End Days

Sprint 9 12 27 15
Online Payment 12 17 5
Dashboard Task 18 22 4
Logical Integrations 23 27 4
Table 11 Sprint 9

Start End Days

Task Name
Sprint 10 28 10 13
Email Notifications 28 1 4
Doctor & Department Page 2 6 4
Remaining work 7 10 3
Table 12 Sprint 10

48 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

Development

INSTALLATION AND SETUP

Installing composer

Figure 20 Installing composer

49 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

Installing Laravel

Figure 21 Installing Laravel

50 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

Running the project

Figure 22 Running the project

51 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

User Registration

Figure 23 Registration

User Login

Figure 24 User Login

52 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

Admin Login

Figure 25 Admin Login

Doctor Login

Figure 26 Doctor Login

53 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

Home Page

Figure 27 Home Page

Doctors Page

Figure 28 Doctors Page

54 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

Departments Page

Figure 29 Departments Page

News Page

Figure 30 News Page

55 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

Contact Page

Figure 31 Contact Page

Appointment-form

Figure 32 Appointment-form

56 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

Online Payment Form

Figure 33 Online Payment Form

57 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

Live Chat

Figure 34 Live Chat

58 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

Figure 35 Live Chat of Gist

59 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

Admin Dashboard

Figure 36 Admin Dashboard

Doctor Dashboard

Figure 37 Doctor Dashboard

60 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

3.3 SURVEY RESULTS

Survey data is defined as the resultant data that is gathered from the number of
respondents that took a survey this is carried out for some study or research purpose
focusing on a topic.

3.3.1 PRE-SURVEY RESULTS

A survey was conducted ahead of developing the proposed system, in which several
questions were asked to the people regarding the system’s overall features/functionalities
and the problems they are facing in the related field. Questions were made, focusing on
the system’s overall features/functionalities, the problems users are facing in the related
field, and for gaining insight into the issues people are facing.

From the resultant data, the majority of the people are suffering from health-related
problems. 40.4 % of the people expressed that they are going through some kinds of
health problems, in the same way 40.4% denied that they are going through some kind
of health issues whereas 19.1% of the people are unsure about their health condition.
51.1 % of the people have faced obstacles while having a medical checkup, while the rest
of 48.9% haven’t faced any of the medical problems and the most top problem is that,
they have to go through a long queue of the line while having a medical checkup. 87.2%
of the people feel time-consuming while having to go through a long line of the queue,
66% of the people expressed messaging session would be good. 95.7% of the people
said that scheduling the doctor of their choice would be good and 97.9% of the people
feel that making an appointment by just sitting in the home would be beneficial. Overall,
positive feedbacks were received while some portion of people even expressed,
additional features/functionalities would be effective in the coming days.

61 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

3.3.2 POST-SURVEY RESULTS

A survey was conducted after developing the proposed system, in which several
questions were asked to the people about how they feel regarding the system’s overall
features/functionalities. Questions were made, focusing on the system’s overall
features/functionalities, the level of usefulness of the system among the users and the
chances of the implementation of this system in the near future.

From the resultant data, 87.5% of the people feel that this system is useful. Majority of
the people expressed that they will use this system if implemented in the hospitals. 75%
of the people have found the user interface really impressive. 31.3% of the people find
online booking feature important, 31.3 of the people find emergency services really good,
18.8% of the people feel live chat as the most important feature and 12.5% people say
online payment as a key feature in the system. 93.8% of the people are satisfied with this
system while the rest of the people don’t find it satisfying. In overall, positive feedbacks
were received regarding the system’s features/functionalities.

62 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

3.4 CODE DEVELOPMENT

Importing bootstrap library

Figure 38 Bootstrap Library

Bootstrap is a framework that helps in designing websites faster and easier. The reason
for importing bootstrap is for its responsive structure and styles which makes the website
attractive and clean.

Login & Registration

Figure 39 Auth Login & Registration

63 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

Figure 40 Login-blade

64 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

Figure 41 Login Controller

Laravel's laravel/ui package provides a quick way to scaffold all of the routes and views
needed for authentication using a few simple commands:

Similarly, admin and doctor login is configured, just by tweaking and modifying the default
authentication.

65 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

Implementation of Live Chat

Figure 42 Live Chat Integration

Gist’s live chat helps in communicating in real-time with the customers and website
visitors. Responding to visitor's queries in real-time, trigger targeted messages, and start
relevant messages with the website visitors. With the help of live chat users can share
any problems or ask anything related to the system.

Booking Feature

Figure 43 Online booking

This section of code is the view blade file of the appointment which needs to be filled up
and submitted to book an appointment. The following code displays the appointment form
which is required to book an appointment.

66 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

Figure 44 Booking Controller

This particular snip code is the controller’s section. From the controller’s section when the
appointment form is filled and submitted it gets stored in the database with the help of the
following code. When it gets stored in the database it redirects with the flash message
i.e. booking information has been sent successfully.

67 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

Payment Feature

Figure 45 Online Payment

This section of code is the view blade of the payment which needs to be filled up and
submitted to make a payment. The following code displays the payment form which is
required to make a payment.

68 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

Figure 46 Payment Integration

This particular snip code is the route section where the payment transaction for stripe is
connected so when the payment form is submitted, the transaction becomes successful,
as well as the patient gets the mail notification. Stripe is used for the payment procedure,
it supports debit cards as well as a credit card.

69 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

Email Notifications

Appointment Confirmed Mail

Figure 47 Appointment confirm mail

The following section of code is of mail notification when the doctor logs in and confirms
a booking, mail notification is sent to the user. Booking for the appropriate user with the
message and subject of the mail is being given in the code above.

Figure 48 Appointment Mail blade

This particular section of code is the view of the mail. The following code shows how the
mail should be viewed by the user when being sent. The above code is viewed by the
user when a mail notification pops up.

70 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

Figure 49 Mail Setup

The following code is of mail setup with the help of a mailable class. Laravel has a simple
way to simplify sending an email by creating mailable classes that handle setting up the
mails. All of the mailable class configurations are done in the build method.

71 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

Payment as well as appointment confirmed email notification

Figure 50 Payment & Appointment Confirmation Mail

The following section of code is of mail notification when the payment is confirmed, mail
notification is sent to the user. Payment mail for the appropriate user with the message
and subject of the mail is being given in the code above.

Figure 51 Payment Mail blade

This particular section of code is the view of the mail. The following code shows how the
mail should be viewed by the user when being sent. The above code is viewed by the
user when a mail notification pops up.

72 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

Figure 52 Payment Mail Setup

The following code is of mail setup with the help of a mailable class. Laravel has a simple
way to simplify sending an email by creating mailable classes that handle setting up the
mails. All of the mailable class configurations are done in the build method.

73 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

Message to the user with email notification

Figure 53 Email Notification

The following section of code is of mail notification, the user submits a message, and the
admin is responsible for sending a suitable message to the user. Mail for the appropriate
user with the message and subject of the mail is being given in the code above.

Figure 54 Query Mail blade

This particular section of code is the view of the mail. The following code shows how the
mail should be viewed by the user when being sent. The above code is viewed by the
user when a mail notification pops up.

74 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

Figure 55 Query Setup Mail

The following code is of mail setup with the help of a mailable class. Laravel has a simple
way to simplify sending an email by creating mailable classes that handle setting up the
mails. All of the mailable class configurations are done in the build method.

75 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

CHAPTER 4: TESTING AND ANALYSIS

Testing is defined as a procedure to check whether the actual results meet the expected
results or not. It is carried out to check the bugs and errors in the software/system.

4.1: TEST PLAN

4.1.1: UNIT TESTING, TEST PLAN
SN. Test Cases Outcome

1. Running the project Successful

2. Running the MYSQL Successful

3. Showing system database Successful.

4. User Registration Successful

5. User Login Successful.

6. Admin Login Successful.

7. Doctor Login Successful.

8. User not letting the access Successful.

when trying to access with
wrong credentials
9. Admin not getting the Successful.
access to the dashboard
with wrong credentials
10. Doctor not getting the Successful.
access to the dashboard
with wrong credentials
11. Live Chat Working Successful

12. Online booking Test Successful

76 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

13. Online payment Test Successful

14. Booking Confirmation Mail Successful

Test

15. Payment Confirmation Mail Successful

Test

16. Query Mail Test Successful

17. Add button test Successful

18. Edit button test Successful

19. Delete button test Successful

Table 13 Unit Testing

77 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

4.2: UNIT TESTING

Unit testing is a testing method where individuals units/components of a software/system
are tested. It is carried out just to make sure that each unit of the system works perfectly
as designed. Similarly, unit testing in this project is carried out just to make sure that the
defined features/functions are working in the correct order.

1. Running the project

TEST CASE 1: Running the project

Test Case 1: Unit testing

Objective Running the project

Expected Results The project should run

Actual Results Program runned successfully

Analysis

Further Notes (If

any)

Table 14 Test Case 1

78 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

Proof for test case 1:

Figure 56 Proof of test case 1

79 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

2. Running the MYSQL

TEST CASE 2: Running the MYSQL

Test Case 2: Unit testing

Objective Running MYSQL

Expected Results The MYSQL should run

Actual Results MYSQL runned successfully

Analysis

Further Notes (If

any)

Table 15 Test Case 2

80 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

Proof for test case 2:

Figure 57 Proof of test case 2

81 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

3. Showing system database

TEST CASE 3: Showing system database

Test Case 3: Unit testing

Objective To show system database

Expected Results The database should appear successfully

Actual Results Database appeared successfully

Analysis

Further Notes (If

any)

Table 16 Test Case 3

82 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

Proof for test case 3:

Figure 58 Proof of test case 3

83 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

4. User registration

TEST CASE 4: USER REGISTRATION

Test Case 4: Unit testing

Objective User registration

Expected Results The user should be registered

Actual Results User registered successfully

Analysis

Further Notes (If

any)

Table 17 Test Case 4

Proof for test 4:

Figure 59 Proof of test case 4

84 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

Figure 60 Proof of test case 4

Figure 61 Proof of test case 4

85 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

5. User Login

TEST CASE 5: USER LOGIN

Test Case 5: Unit testing

Objective User Login

Expected Results The user should be logged in

Actual Results User logged in successfully

Analysis

Further Notes (If

any)

Table 18 Test Case 5

Proof for test 5:

Figure 62 Proof of test case 5

86 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

Figure 63 Proof of test case 5

6. Admin Login

TEST CASE 6: ADMIN LOGIN

Test Case 6: Unit testing

Objective Admin Login

Expected Results The admin should be logged in

Actual Results Admin logged in successfully

Analysis

Further Notes (If

any)

Table 19 Test Case 6

87 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

Proof for test 6:

Figure 64 Proof of test case 6

Figure 65 Proof of test case 6

88 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

7. Doctor Login

TEST CASE 7: DOCTOR LOGIN

Test Case 7: Unit testing

Objective Doctor Login

Expected Results The doctor should be logged in

Actual Results Doctor logged in successfully

Analysis

Further Notes (If

any)

Table 20 Test Case 7

89 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

Proof for test 7:

Figure 66 Proof of test case 7

Figure 67 Proof of test case 7

90 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

8. User not getting the access when trying to access with wrong credentials

TEST CASE 8: USER NOT GETTING THE ACCESS WHEN TRYING TO ACCESS
WITH WRONG CREDENTIALS

Test Case 8: Unit testing

Objective User should not get access when trying to access with wrong
credentials
Expected Results User not getting access when trying to access with wrong
credentials
Actual Results User didn’t got access when trying to access with wrong
credentials
Analysis

Further Notes (If

any)

Table 21 Test Case 8

Proof for test 8:

Figure 68 Proof of test case 8

91 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

9. Admin not getting the access to the dashboard with wrong credentials

TEST CASE 9: ADMIN NOT GETTING THE ACCESS TO THE DASHBOARD WITH
WRONG CREDENTIALS

Test Case 9: Unit testing

Objective Admin should not get access to the dashboard when trying to
access with wrong credentials
Expected Results Admin not getting access to the dashboard when trying to
access with wrong credentials
Actual Results Admin didn’t got access to the dashboard when trying to access
with wrong credentials
Analysis

Further Notes (If

any)

Table 22 Test Case 9

Proof for test 9:

Figure 69 Proof of test case 9

92 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

10. Doctor not getting the access to the dashboard when trying to access with
wrong credentials

TEST CASE 10: DOCTOR NOT GETTING THE ACCESS TO THE DASHBOARD
WHEN TRYING TO ACCESS WITH WRONG CREDENTIALS

Test Case 10: Unit testing

Objective Doctor should not get access to the dashboard when trying to
access with wrong credentials
Expected Results Doctor not getting access to the dashboard when trying to
access with wrong credentials
Actual Results Doctor didn’t got access to the dashboard when trying to
access with wrong credentials
Analysis

Further Notes (If

any)

Table 23 Test Case 10

93 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

Proof for test 10:

Figure 70 Proof of test case 10

94 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

11. Live Chat Working

TEST CASE 11: LIVE CHAT WORKING

Test Case 11: Unit testing

Objective Live Chat should work properly

Expected Results Live Chat working properly

Actual Results Live Chat worked properly

Analysis

Further Notes (If

any)

Table 24 Test Case 11

95 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

Proof for test 11:

Figure 71 Proof of test case 11

Figure 72 Proof of test case 11

96 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

Figure 73 Proof of test case 11

12. Online booking Test

TEST CASE 12: ONLINE BOOKING TEST

Test Case 12: Unit testing

Objective Online booking should work properly

Expected Results Online booking working properly

Actual Results Online booking worked properly

Analysis

Further Notes (If

any)

Table 25 Test Case 12

97 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

Proof for test 12:

Figure 74 Proof of test case 12

Figure 75 Proof of test case 12

98 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

Figure 76 Proof of test case 12

Figure 77 Proof of test case 12

99 | P a g e Sandipan Khadka
FC6P01NT Final Year Project

13. Online Payment Test

TEST CASE 13: ONLINE PAYMENT TEST

Test Case 13: Unit testing

Objective Online payment should work properly

Expected Results Online payment working properly

Actual Results Online payment worked properly

Analysis

Further Notes (If

any)

Table 26 Test Case 13

100 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

Proof for test 13:

Figure 78 Proof of test case 13

Figure 79 Proof of test case 13

101 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

Figure 80 Proof of test case 13

Figure 81 Proof of test case 13

14. Booking Confirmation Mail Test

TEST CASE 14: BOOKING CONFIRMATION MAIL TEST

Test Case 14: Unit testing

Objective Booking confirmation mail working properly

Expected Results Booking confirmation mail should work properly

Actual Results Booking confirmation mail worked properly

Analysis

Further Notes (If

any)

Table 27 Test Case 14

102 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

Proof for test 14:

Figure 82 Proof of test case 14

103 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

Figure 83 Proof of test case 14

Figure 84 Proof of test case 14

104 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

15. Payment Confirmation Mail Test

TEST CASE 15: PAYMENT CONFIRMATION MAIL TEST

Test Case 15: Unit testing

Objective Payment confirmation mail working properly

Expected Results Payment confirmation mail should work properly

Actual Results Payment confirmation mail worked properly

Analysis

Further Notes (If

any)

Table 28 Test Case 15

105 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

Proof for test:15

Figure 85 Proof of test case 15

Figure 86 Proof of test case 15

106 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

Figure 87 Proof of test case 15

16. Query Mail Test

TEST CASE 16: QUERY MAIL TEST

Test Case 16: Unit testing

Objective Query mail working properly

Expected Results Query mail should work properly

Actual Results Query mail worked properly

Analysis

Further Notes (If

any)

Table 29 Test Case 16

107 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

Proof for test 16:

Figure 88 Proof of test case 16

108 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

Figure 89 Proof of test case 16

Figure 90 Proof of test case 16

109 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

17. Add button test

TEST CASE 17: Add button test

Test Case 17: Unit testing

Objective To check whether add button works or not

Expected Results Add button should work properly

Actual Results Add button worked successfully

Analysis

Further Notes (If

any)

Table 30 Test Case 17

110 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

Proof for test 17:

Figure 91 Proof of test case 17

Figure 92 Proof of test case 17

111 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

Figure 93 Proof of test case 17

Figure 94 Proof of test case 17

Figure 95 Proof of test case 17

18. Edit button test

TEST CASE 18: Edit button test

Test Case 18: Unit testing

Objective To check whether edit button works or not

Expected Results Edit button should work properly

Actual Results Edit button worked successfully

Analysis

Further Notes (If

any)

Table 31 Test Case 18

112 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

Proof for test 18:

Figure 96 Proof of test case 18

Figure 97 Proof of test case 18

Figure 98 Proof of test case 18

Figure 99 Proof of test case 18

Figure 100 Proof of test case 18

113 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

19. Delete button test

TEST CASE 19: Delete button test

Test Case 19: Unit testing

Objective To check whether delete button works or not

Expected Results Delete button should work properly

Actual Results Delete button worked successfully

Analysis

Further Notes (If

any)

Table 32 Test Case 19

Proof for test:19

Figure 101 Proof of test case 19

Figure 102 Proof of test case 19

114 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

Figure 103 Proof of test case 19

Figure 104 Proof of test case 19

115 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

4.3 CRITICAL ANALYSIS

All the self-conducted units and the system tests were successful and were properly
functioning. Just after the completion of the development phase, a survey was conducted
where the general users provided much-needed feedback regarding the system.

The feedbacks collected were very valuable and gave clear concepts regarding the
system’s positive and negative aspects. The user’s satisfaction level is high, regarding
the system’s overall features and functionalities. Most of the people showed that they are
impressed with the available services of emergency and ambulance. They also seemed
to be impressed with the feature of online payment and live chat. Users can simply book
an appointment or can pay an book an appointment with the medium of debit/credit card.
On the other hand, the feature of email notification didn’t grab as much attention as it
should have.

The concept of online payment while making an appointment is quite new in the market
as it facilitates the acceptance of electronic payment for online transactions. Online
payment services have become increasingly popular due to the widespread use of
internet-based shopping and banking. They also seemed to love the idea of email
notification whenever a booking is confirmed, booking is confirmed by the doctor as there
may be repetitive date and time while making a booking request.

116 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

CHAPTER 5: CONCLUSION
Life is becoming too busy to get medical appointments in person to person and to maintain
proper health care. MedArt is an online doctor appointment system that aims to provide
ease and comfort to patients while taking an appointment from doctors and it also resolves
the problems that the patients have to face while making an appointment. Compared with
traditional appointment methods, MedArt is more patient-centered and has many
advantages, which helps in resolving the issues patients face while having a medical
checkup.

5.1 LEGAL, SOCIAL AND ETHICAL ISSUES

5.1.1: LEGAL ISSUES
On the chosen topic, there haven’t been any patent claims for its idea and the codes,
technologies used in the project are available and free to use. The following project also
doesn’t go through any kind of legal and copyright issues. As per the Nepal Standards
(Certification-mark) rules 2046, materials processes or services should prepare the
standards under the policies provided by the council, and to get such recognition, some
modifications and changes are needed. The sale or distribution of any material is only
performed after verifying with the council.

For the manufacturing of the product, an application for a license or certificate should be
submitted to the council. After signing on the letter of agreement, the license or certificate
would be valid for the period of 3 years where the consent to the council standards needs
to be provided. An online doctor appointment system has to go through the production
process or test which needs to be ensured from the council, to be recorded in the
laboratory. The system may go through some issues as if the Government of Nepal
changes the schedule with a notice.

117 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

5.1.2: SOCIAL ISSUES

Analyzing the recent market analysis, the online doctor appointment system shows the
upward market. As per the sources, the market for an online doctor appointment is
expected to grow at an annual growth rate of 98.0% in the next 5 years. The Global Doctor
Appointment market is expected to show a growth rate of 16.56% during the same period.
The service industry has become highly demanding with consumers wanting exclusive
access to service providers. More people would be involved in the system rather than
following traditional approaches.

A good internet connection is required for booking an appointment online, either it is a

phone or computer. In the case of no internet you cannot use this system. High demand
for the system, somehow depending on the business and the market it can create a large
influx which can be overwhelming. Sometimes scheduling can create uncertainty or
confusion among the users. The type of uncertainty also depends upon the type of
services the system provides.

5.1.3 ETHICAL ISSUES

An online doctor appointment system has been developed with long term vision and
focusing on sustainability. The features included in the system are in good order and
working fine. An authentication system enables users to login, so when the wrong
credentials are provided for each authentication then the type of user cant log in. The
user provides the booking information from which the doctor confirms the booking.

The system runs on the internet, on the problematic side of the online doctor appointment
system, insufficient information to the opposite side, where the information is measured
maintaining the confidentiality of the provided information as well as the protection of the
personal information is really difficult. Gathering the patient's record by an unauthorized
person may mislead the private information and lead to misusing the data. Inaccurate and
unclear reporting also creates the miscommunication and misleading of the information.

118 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

5.2 ADVANTAGES
Some of the advantages or features, which the users will be provided in the system are
listed as under:-
1. Users can chat if they have any questions, or problems they want to share about
via messaging session.
2. Users can book an appointment by choosing a specific doctor and selecting a
particular date and time.
3. Users can also pay and book an appointment with the help of a debit/credit card.
4. Email notification after booking an appointment, paying an amount, and after
asking a query.
5. Emergency services
6. Ambulance services

5.3 LIMITATIONS
1. Internet connection is required to use this system.

2. If the website undergoes any kind of issue, the whole application will be in trouble.

3. Security is the major concern especially when users from all over the world are
accessing the same server.

4. Only a limited number of browser support is available.

119 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

5.4 FUTURE WORK

The proposed system that is an online doctor appointment system is currently limited to
a single organization or hospital with the future target to set up the system to multiple
numbers of hospitals. The future target would be to set up additional features in the
system i.e. to make it a big project, additional numbers of hospitals can be added in the
system with the additional numbers of doctors that can be based on the regional, zonal
province or even national wise. Patients history can be saved and checked if the patient
has already used a particular system. In the same way if the new patient uses the
particular system then the patient's data needs to be saved for future reference. Features
such as invoice reports, medicine suggestions, discussion forums can be implemented
and the whole concept can be broadened, turning it into a huge project.

The concept of online doctor appointment system is only supported to a limited number
of browsers, which can be extended to a bigger number of browsers and platforms like
mobile app and video calling sessions can also be implemented soon. The system
possesses a huge number of scope and the benefits of implementing this technology
touch everyone involved in the scheduling process, as administrators and staff can
conduct their tasks more efficiently and accurately, while customers and clients can book
their appointments and reservations quickly and more conveniently.

120 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

CHAPTER 6: REFERENCES
360logica, 2019. [Link]. [Online]
Available at: [Link]
proves-to-be-a-better-choice-for-your-project/
[Accessed 3 January 2020].

Adams, C., 2010. [Link]. [Online]

Available at:
[Link]
[Link]
[Accessed 16 April 2020].

Akinode John Lekan, O. S. A., 2017. Design and Implementation of a Patient

Appointment and Scheduling System. IARJSET, 4(12), pp. 16-23.

Arntz, M., 2018. [Link]. [Online]

Available at: [Link]
[Accessed 3 January 2020].

Bumrungrad, 2020. [Link]. [Online]

Available at:
[Link]
EAAYASAAEgLQ6vD_BwE
[Accessed 15 April 2020].

Cara Rudnic, O., 2017. Online Medical Appointment System, Valencia,Spain: Curso
2016-2017.

David Miller, P. Y. a. X. Z., 2017. Web-Based Medical Appointment Systems: A

Systematic Review. Journal of Medical Internet Research, 19(4).

Drumond, C., 2019. [Link]. [Online]

Available at: [Link]
[Accessed 1 November 2019].

121 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

Elley, M., 2017. [Link]. [Online]

Available at: [Link]
patient-appointments
[Accessed 14 April 2020].

[Link], 2019. [Link]. [Online]

Available at: [Link]
dsdm/
[Accessed 1 November 2019].

Gibb, R., 2016. [Link]. [Online]

Available at: [Link]
[Accessed 12 April 2020].

Grandehospital, 2020. [Link]. [Online]

Available at: [Link]
[Accessed 15 April 2020].

Gupta, S., 2019. [Link]. [Online]

Available at: [Link]
lifecycle/?fbclid=IwAR0lTLkzB3w5ceWh96Znp9QZCsb2Zkk2O_aD_8yzmGPosU9mmm
_ykd21NBY
[Accessed 1 November 2019].

Haque, S. T., 2017. Online Appointment System, s.l.: Slideshare.

Hirslanden, 2020. [Link]. [Online]

Available at:
[Link]
6AIVVJCPCh3LhAmzEAAYAiAAEgJ5LfD_BwE
[Accessed 15 April 2020].

Kinder, K., 2013. [Link]. [Online]

Available at: [Link]
[Accessed 18 April 2020].

122 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

Md. Maharaz Hossain, S. M. Z., n.d. Design and Development of Online Doctor
Appointment System, Bangladesh: Academia.

Melesse Belayneh, M. W. N. B., 2015. Patient Waiting Time and its Determinants in the
General Outpatient, Ethiopia: Scientific Research Publishing.

Nepalmediciti, 2020. [Link]. [Online]

Available at: [Link]
[Accessed 15 April 2020].

Norvichospital, 2020. [Link]. [Online]

Available at: [Link]
[Accessed 15 April 2020].

OnGraph Technologies, 2016. OnGraph [Link]. [Online]

Available at: [Link]
[Accessed 3 January 2020].

P, N., 2018. Secure Web Application for Online Doctor Appointment System, s.l.: 1000
projects.

Powell-Morse, A., 2016. [Link]. [Online]

Available at: [Link]
[Accessed 3 January 2020].

Rouse, M., 2017. [Link]. [Online]

Available at: [Link]
[Accessed 3 January 2020].

Shafaq Malik, N. B. S. K. R. S. a. S. A. R., 2017. Mr. Doc: A Doctor Appointment

Application System, Rawalpindi, Pakistan: arvix.

Shankar, P. R., 2017. Brain drain and practice locations of Nepalese medical students.
Janaki Medical College Journal of Medical Sciences, 5(2), pp. 1-4.

123 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

TatvaSoft, 2016. [Link]. [Online]

Available at: [Link]
framework/
[Accessed 18 April 2020].

TechTerms, 2014. [Link]. [Online]

Available at: [Link]
[Accessed 3 January 2020].

Tufail, M., 2018. ONLINE POLYCLINIC APPOINTMENT AND DATABASE

MANAGEMENT SYSTEM, Pakistan: TAMK.

Tutorialspoint, 2019. [Link]. [Online]

Available at: [Link]
[Accessed 3 January 2020].

tutorialspoint, 2020. tutorialspoint. [Online]

Available at: [Link]
[Accessed 18 April 2020].

W3C, 2016. [Link]. [Online]

Available at: [Link]
[Accessed 15 April 2020].

124 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

CHAPTER 7: BIBLIOGRAPHY
Agriya, 2018. Success rate & Market analysis of Doctor Appointment Booking System,
Chennai, TamilNau, India: Agriya.

appointmentplus, 2012. [Link]. [Online]

Available at: [Link]
theme/dist/img/pdf/manual_vs_automated_appointment_scheduling.pdf
[Accessed 20 April 2020].

Cynthia Onyefulu, M. P. G. L. M., 2018. Users Views on the Online Appointment

System and Services Rendered at the Health Centre of the University of Technology,
Jamaica. OALibJ, 5(10), pp. 1-15.

FATbit Chef, 2017. FATbit. [Online]

Available at: [Link]
marketplace/
[Accessed 23 April 2020].

Fullestop, 2020. fullestop. [Online]

Available at: [Link]
[Accessed 20 April 2020].

Gaul, V., 2019. Appointment Scheduling Software Market by Type (Web-based, SaaS;
Mobile App; and Others), Organization Size (Small & Medium Sized Enterprises, and
Large Enterprises), and End-User Industry (Corporate, Beauty & Wellness, Education,
Healthcare, and Others), s.l.: Avenue(Allied Market Research).

guru99, 2020. Guru99. [Online]

Available at: [Link]
[Accessed 23 April 2020].

lawcommission, 1983. Nepal Standards (Certification-mark) Rules, 2040, Nepal: Nepal

Gazette.

125 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

lucidchart, 2020. Lucidchart. [Online]

Available at: [Link]
symbols
[Accessed 25 April 2020].

lucidchart, 2020. [Link]. [Online]

Available at: [Link]
[Accessed 20 April 2020].

Lynch, A., 2020. edraw. [Online]

Available at: [Link]
[Accessed 25 April 2020].

Msc-IT Study Material, 2011. [Link]. [Online]

Available at: [Link]
[Accessed 20 April 2020].

NR Dissanayake, G. D., 2017. Web-based Applications: Extending the General

Perspective of the Service of Web, Colombo, Srilanka: University of Colombo School of
Computing.

smartdraw, 2020. [Link]. [Online]

Available at: [Link]
[Accessed 20 April 2020].

Software Testing fundamentals, 2020. [Link]. [Online]

Available at: [Link]
[Accessed 20 April 2020].

Tutorialspoint, 2020. [Link]. [Online]

Available at: [Link]
[Accessed 24 April 2020].

126 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

creately, 2019. creately. [Online]

Available at: [Link]
[Accessed 25 April 2020].

lucidchart, 2020. Lucidchart. [Online]

Available at: [Link]
[Accessed 25 April 2020].

syncfusion, 2020. Syncfusion. [Online]

Available at: [Link]
[Accessed 25 April 2020].

Brandenburg, L., 2020. Bridging the gap. [Online]

Available at: [Link]
[Accessed 26 April 2020].

Gantt, 2020. [Link]. [Online]

Available at: [Link]
[Accessed 26 April 2020].

Haas, N., 2020. Orbit Media Solutions. [Online]

Available at: [Link]
[Accessed 26 April 2020].

Visual Paradigm, 2020. visual-paradigm. [Online]

Available at: [Link]
flow-diagram/
[Accessed 26 April 2020].

Visual Paradigm, 2020. visual-paradigm. [Online]

Available at: [Link]
breakdown-structure/
[Accessed 26 April 2020].

127 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

CHAPTER 8: APPENDIX
Client Approval Letter

Figure 105 Client Approval letter

128 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

System Architecture

BROWSER WEB SERVER PUBLIC

ROUTING

CONTROLLER

DATABASE
VIEW MODEL

129 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

Context Level Diagram

A context diagram is used to show the high-level picture of the system. It is also called a
level 0 data flow diagram. It is usually drawn to define and visualize the boundaries of the
software system. It shows the most information flow between the system and the external
entities.

External Entity – It is also referred to as actors, source, and terminators, it is responsible

for consuming the data that flows between the entity and the system.

Process – An activity that changes or transforms data flows.

Data Flow – An arrow symbol shows the direction of flow. Movement of data between
external entities, processes, and data stores is represented with an arrow symbol.

130 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

Figure 106 Context Level diagram

131 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

Data flow diagram

Data flow diagrams are used to graphically represent the flow of data in a system. DFD
includes processes, data storage, inputs, and outputs, involved in a system. Clarification
of Context Diagram or 0 Level Data Flow Diagram of Online Doctor Appointment
system. This system describes the whole software that consists of three external entities
like User, Admin, and doctor. User logins into the system send messages and books an
appointment, admin is responsible for responding to the user messages as well as has
an authority to add/delete and update the records of user and doctor both whereas
doctor logins and confirms the booking request and views the payment details.

Four basic symbols are used to represent a data-flow diagram.

External entity

An external entity can be a person, organization, or another system that provides data
to the system as an input, or receives outputs from the system.

Process

A process receives input data and produces an output within a system’s boundary.

132 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

Data flow

A data-flow is used to move data from one part of the system to another.

Data Store

A datastore is used in a data-flow diagram, whenever the system must store data of one
or more processes.

Figure 107 Data flow diagram

133 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

Use Case Diagram

Use Case is a dynamic or behavior diagram in UML. The use case diagram depicts the
functionality in the form of use cases and actors. A set of use cases, actors, and a system
is what it takes to design use cases.

An Actor can be a user or a system that interacts with the given subject.

The use case is typically defining interactions between an actor and a system.

An association is a relationship between an actor and a use case.

An include relationship is a directed relationship between two use cases when required

Extending defines optional behavior that is not necessarily meaningful by itself.

134 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

Figure 108 Use Case diagram

135 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

Entity Relationship Diagram

An entity-relationship diagram is a type of flowchart that shows how the entities i.e.
(people, objects) behave and relate in a system. ERD’s illustrate the relationships
between the entities & map out the flow of information in the system.

There are three basic elements in an ER Diagram: entity, attribute, relationship.

Cardinality and ordinality are two other notations used in ER diagrams to further
define relationships.

Entity

An entity can be a person, place, event, or object that is relevant to a given system.
Entities are represented in ER diagrams by a rectangle and named using singular nouns.

Attribute

An attribute is a property, trait, or characteristic of an entity, relationship, or another

attribute.

Relationship

A relationship describes how entities interact. Relationships are represented by diamond

shapes and are labeled using verbs.

Cardinality & Ordinality

Cardinality refers to the maximum number of times an instance in one entity can relate to
instances of another entity. Ordinality, on the other hand, is the minimum number of times
an instance in one entity can be associated with an instance in the related entity.

136 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

Figure 109 Cardinality & Ordinality

Figure 110 ERD Diagram

137 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

Class Diagram

A class diagram is mainly used for describing the attributes and operations in a class, a
class diagram is a collection of classes, interfaces, associations, collaborations, and
constraints. The main purpose of making a class diagram is to model the static view of
the application.

Class

A Class is a set of objects that shares the same specifications of features, constraints,
and semantics.

Relationships

A relationship specifies the logical connections between each class.

138 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

Figure 111 Relationship types

Association

Association is a set of links that connects elements of a UML model.

Aggregation

Aggregation is a binary association between a property and one or more composite

objects which group a set of instances.

Composition

The composition is a “strong” form of “aggregation”.

Inheritance

Inheritance is similar to generalization, which shows a relationship between superclass

and subclass.

139 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

Dependency

Dependency is a relationship between some elements and or depends on other models

for specifications.

Figure 112 Class diagram

140 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

Data Dictionary

A Data Dictionary provides information about each attribute, also known as fields,
of a data model.

1) Users Table

Attributes Data Type Size Constraint Reference Example

Table
ID INT 20 1

Name STRING 30 Hari Acharya

Email STRING 30 PRIMARY KEY hari02@[Link]

Password STRING 30 *******

Table 33 Users Table

2) Admins Table

Attributes Data Type Size Constraint Reference Example

Table
ID INT 20 1

Name STRING 30 Ravi Sharma

Email STRING 30 PRIMARY KEY ravi11@[Link]

Password STRING 30 *******

Table 34 Admins Table

141 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

3) Doctors Table

Attributes Data Type Size Constraint Reference Example

Table
ID INT 20 1

Name STRING 30 [Link] Rai

Email STRING 30 PRIMARY KEY dr.bishnu1@[Link]

Qualification STRING 30 MD

Speciality STRING 30 Radiologist

Working_days STRING 30 Saturday

Shift STRING 30 8:00 AM to 5:00 PM

Password STRING 30 ********

Table 35 Doctors Table

142 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

4) Bookings Table

Attributes Data Type Size Constraint Reference Example

Table
ID INT 20 1

Name STRING 30 Adarsha Basnet

Email STRING 30 PRIMARY KEY Adarsha23@[Link]

Phone_no BIGINTEGER 30 9818467314

Address STRING 30 Itahari, 4 Sunsari

Booking_date DATE 30 2020/02/12

Booking_time STRING 30 4:00 PM

Department STRING 30 Family Physician

Doctor STRING 30 Dr Sagar Gurung

Table 36 Bookings Table

5) Departments Table

Attributes Data Type Size Constraint Reference Example

Table
ID INT 20 PRIMARY KEY 1

Name STRING 30 Cardiology

Doctor_enrolled STRING 30 Dr. Rubina Desai

Table 37 Departments Table

143 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

6) Payments Table

Attributes Data Type Size Constraint Reference Example

Table
ID INT 20 1

Name STRING 30 Susan Bhatta

Email STRING 30 PRIMARY KEY Susan10@[Link]

Phone_no BIGINTEGER 30 9824387045

Booking_date DATE 30 2020/03/05

Booking_time STRING 30 11:00 AM

Department STRING 30 Radiology

Doctor STRING 30 Dr. Niraj Dahal

Name_on_card STRING 30 Susan Bhatta

Card_no BIGINTEGER 30 4242424242424242

Cvc INTEGER 30 123

Expiration_month INTEGER 30 12

Expiration_year INTEGER 30 2022

Table 38 Payments Table

144 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

7) Queries Table

Attributes Data Type Size Constraint Reference Example

Table
ID INT 20 1

Name STRING 30 Rohan Karki

Email STRING 30 PRIMARY KEY rohan33@[Link]

Subject STRING 30 Booking Approval

Message STRING 30 Concept is well utilized

Table 39 Queries table

145 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

System Algorithm

Step 1: Start.

Step 2: Registration/Login.

Step 3: If usertype is doctor, he/she views all the pending appointment requests and
confirms the appointments.

Step 4: Checks the payment.

Step 5: Logout

Step 6: If usertype is patient, he/she sends messages.

Step 7: Chooses a doctor

Step 8: Books an appointment by paying or without payment.

Step 9: If payment is yes, then the appointment is confirmed else the appointment is still
pending, yet to be confirmed.

Step 9: Logout

Step 10: If usertype is admin, he/she sends notifications to the patient.

Step 11: He/she can add/update or delete doctor/patient.

Step 12: Logout

Step 13: End

146 | P a g e Sandipan Khadka

 FC6P01NT Final Year Project

SYSTEM FLOWCHART

Start

Registration/

Login

User
Type

Doctor Patient Admin

Send Messages

Accepts Sends
appointments notifications
Choose a doctor

Checks payment Add/Update or

Appointment Delete
Patient/ Doctor

YES NO
Payment
Logout Logout

Appointment Appointment
Confirmed Pending

Logout

End

147 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

PRE SURVEY RESULTS

Problems faced by the users in the related field

Figure 113 Pre survey form

Figure 114 Pre survey form

148 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

Figure 115 Pre survey form

Figure 116 Pre survey form

149 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

Users response on the features of the system

Figure 117 Pre survey form

Figure 118 Pre survey form

150 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

Figure 119 Pre survey form

Users suggestions/feedback regarding the system

Figure 120 Pre survey form

151 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

Figure 121 Pre survey form

152 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

Figure 122 Pre survey form

153 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

Users opinions on extra additional features that they want to see on this system

Figure 123 Pre survey form

154 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

Figure 124 Pre survey form

155 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

POST SURVEY RESULTS

Users response regarding the system

Figure 125 Post survey form

156 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

Figure 126 Post survey form

157 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

Figure 127 Post survey form

Figure 128 Post survey form

158 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

Figure 129 Post survey form

Figure 130 Post survey form

159 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

Figure 131 Post survey form

160 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

Figure 132 Post survey form

161 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

Work breakdown structure

The Work Breakdown Structure is developed to have a better understanding of project

scope. Work Breakdown Structure is referred to as a hierarchical description of the work,
to carry out the deliverables of a project.

Doctor Connect
System

Project
Analysis Design Implementation Testing Deployment Documentation
Management

Project Requirement Final report

Logical Design BuildDatabase Unit Testing User Training
Identification Gathering writing

Project Topic Feasibility Integration Final report

Physical Design Coding
Approval Study Testing review

FYP Proposal Analysis Final report

UI Design
Submission Specification submission

Project Database
Planning Design

Prototyping

Figure 133 WBS

162 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

Scheduling/Gantt Chart

A Gantt chart is used to show activities (tasks or events) displayed against time. Used in
project management.

Figure 134 Gantt Chart

163 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

Software requirements specification

Purpose

The purpose of this document is to give a detailed description of the requirements for the
project named “Doctor Connect System”. The purpose demonstrates a complete
illustration of the development of the system. It will also explain various functionalities like
system constraints, interface, and interactions with other external applications.

Scope

The Doctor Connect System is a web app, which helps the patients and the related visitors
to book an appointment with the relevant doctors with different parameters and
indications. Not only, appointment-related services but it contain various other services
like ambulance services, emergency services, messaging session if the patients need to
share some problems and ask for some health-related advice and payment integration
system if wants to play online.

The system can be accessed with the internet service and the user can access through
it, login if already created an account otherwise register first and then can search for the
relevant doctors, search for an appointment and make an appointment based on time and
schedule he/she wants to visit. Pay online if he/she wants to, and gets notified on a
particular day.

Overall description

This section describes the whole overview of the system. The system is explained in such
a way that it depicts the whole scenario of how the system interacts with other systems
and represents the basic functionality.

164 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

Product description

The system is only based on a web portal, in which all the information relating to it will be
clear and concise. The web portal will be used for managing the information about the
hospital and the doctor and the system as a whole.

Since this is a data-centric product it will need somewhere to store the data. For that
purpose a database is required. The web portal will use the database to get data as well
as to add modify and remove data.

Product functions

In the web portal, the user can search for the required information about the relevant
doctor. After login into the system, there are various types of search criteria, based on
what criteria the user wants to get involved in and take action. The user can select
particular criteria and make an appointment based on what time and schedule he/she can
visit.

User characteristics

3 types of users will be involved in the system: doctor, patient, and admin. Each of these
users has a particular role and function in the system.

Doctors need to be registered in the system and should log in to view the details and
information related to the patients and can take action regarding the patient's approval
and appointment requests.

The patient needs to register and log in so that he/she can view and select the doctor of
his/her choice and make an appointment. He/she can also share the problems via the
messaging session, whereas the doctor confirms the booking request and performs the
next necessary steps of action.

Admin can view the registered details of the doctor and user and can add, modify, or
delete the data of the user and doctor. Admin replies to the message sent by the user or
the website visitor. Overall, the admin has the authority to control both the patients and
doctor and can take some set of actions if needed.

165 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

Constraints

Database capacity and internet connection are the constraints for the system. Without an
internet connection, the system fails to load and the internet connection is vital for the
system to function. The system needs a database to fetch data, if it is shared among
multiple systems then it can increase the amount of time taken for incoming requests to
load and fetch the data.

Assumptions and dependencies

The system needs a good amount of software and hardware requirements to run, so
sometimes the user may not possess such requirements to run the system. A good
internet connection is crucial for running the system, so the user must satisfy these
requirements of a specification to run the system effectively and efficiently.

Apportioning of requirements

In case the project couldn’t be developed in time or could not satisfy the requirements as
per the plan, the requirements could be transferred to the next version of the application
and further developed in the next session or next phase.

Specific requirements

This section explains all the functional requirements of the system in much more detail. It
gives a detailed description of the system and its functionalities.

External interface requirements

This section gives detailed information on the hardware, software communication

interfaces, and basic prototypes of the user interface.

166 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

Wireframes
Wireframes are the simple black and white layouts that specify the size, placement, and
contents of the website.

Figure 135 Wireframes

167 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

Figure 136 Wireframes

Figure 137 Wireframes

168 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

Figure 138 Wireframes

Figure 139 Wireframes

169 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

Figure 140 Wireframes

Figure 141 Wireframes

170 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

Figure 142 Wireframes

Figure 143 Wireframes

171 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

Figure 144 Wireframes

Figure 145 Wireframes

172 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

Figure 146 Wireframes

Figure 147 Wireframes

173 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

Figure 148 Wireframes

Figure 149 Wireframes

174 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

Figure 150 Wireframes

Figure 151 Wireframes

175 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

Hardware interface

The system doesn’t have actual designated hardware, it doesn’t have to be connected to
hardware interfaces to manage the underlying operation.

Software interface

The system interrogates with the database to retrieve the information related to the
doctor, patients. The communication between the database and the web portal includes
the operation of adding, removing, and modifying data.

Communication interface

The existing communication between the system of different parts, databases, and the
web portal includes the operation of adding, removing, and modifying data. It is handled
by the underlying operating systems in the web portal.

176 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

Functional requirements

This section describes all the fundamental actions of the system.

 Users should be able to use, register, and log in to the system.
 Users should be notified about the update in the system and the booking requests,
payment, etc.
 Users should be able to search for doctors and select particular criteria by picking
time and schedule.
 User profiles should be created.
 Users should be able to share problems via a messaging session.
 Users should be able to pay online.
 Doctors should be able to use, login, and register into the system.
 Doctors should be able to view appointments.
 Doctors should be able to take action based on certain patients.
 The doctor should be able to confirm the booking requests of the user and can
view the payments made by the patients.
 Admin should be able to use, login, and register into the system.
 Admin should be able to register profiles of patients and doctors.
 Admin should be able to reply to messages of the patients.
 Admin should be able to add, modify and update data of the doctor and user

Non-functional requirements

Non-functional requirements describe how the system is to behave and establish

constraints of its functionality.

177 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

Usability

Usability means how the user views the overall system, based on the difficulty of the
system.
1. The efficiency of use: time taken to complete the overall user stories and sprints,
how efficient it is, i.e. less bug ratio.

2. Intuitiveness: based on the simple nature of the system.

3. Low perceived workload: attempts taken to complete a task.

Security

Security means the system should be protected from unauthorized access and its stored
data. Data privacy should exist as there contains lots of data misuse, copying, and
misleading. Security also means there should be protected against malware and virus
attacks.

Reliability

Reliable ensures how much the product is reliable, it should be bug-free and should run
smoothly without any failures. Reliability should possess an error-free, productive, and
smooth running program.

Performance

Performance is one of the quality attributes that define the system. Poor performance
creates a negative impact on the user and leads to a haphazard situation.

178 | P a g e Sandipan Khadka

FC6P01NT Final Year Project

Availability

Availability ensures that about what certain period, the system’s functionality is in use in
all the operations so the scheduled maintenance period affects these criteria. Less
amount of maintenance period should be maintained.

Scalability
Scalability includes both the hardware and software implications and describes how the
system must evolve without creating a negative influence on the performance. Increasing
memory allocations, RAM, and disk spaces have a chance of increasing scalability.

179 | P a g e Sandipan Khadka