MCS-044

Online Appointment System

TEAM MEMBERS

SERIAL NO. NAME ENROLMENT NO.

1. Deepak Kumar 157769776

2. Robin Singh Bisht 157769744

3. Preeti Mishra 157779800

4. Prachi Mishra 157779817

STUDY CENTRE CODE: 07121P

Submitted to the School of Computer and Information Sciences
in partial fulfillment of the requirements
for the degree of

Masters
Of
Computer Applications

Indira Gandhi National Open University, Maidan Garhi.

1
TABLE OF CONTENTS

1. INTRODUCTION 4

1.1 Background 4

1.2 Objectives 4

1.3 Purpose and Scope 5

1.3.1 Purpose 5

1.3.2 Scope 5

2. SURVEY OF TECHNOLOGIES 6-7

3. REQUIRMENT AND ANALYSIS 8-16

• Problem Definition 8

• Planning and Scheduling 9-10

• Software and Hardware Requirements 11

• Preliminary Product Description 12

• Conceptual Models 12-16

4. REFERENCES 17

2
Title of Project: Online Appointment System

1. INTRODUCTION

1.1 BACKGROUND:
“Online Appointment System” facilitates effective scheduling of
appointment of patients with the doctors. This system allows doctors and
nurses to view available time slots and allocate appointments accordingly. The
registration and appointment management system is an efficient for patient to
ease capturing of pertinent information of the patients. The patient
administration functionalities of the hospital can be automated to provide
proficient patient care. The scheduling of patient and doctor appointment can
be done from this system. The details about schedule of a doctor slots available
in his schedule, schedule slots, tracking of patient and their visits, scheduling
appointments for unregistered patients and emergency patients can be viewed
effortlessly. It prevents the system from creating an appointment if the doctor
is on leave or absent or busy in another place. The appointments are given with
date time department doctor and the type of visit of the patient.

1.2 OBJECTIVES:
The main objective is to make the online appointment system is more
efficient than the existing system. An online appointment system is a web-
based application that allows individuals to conveniently and securely book
their appointments online through any web connected device, such as
computer, laptop smartphone.

3
 1.3 PURPOSE AND SCOPE

1.3.1 PURPOSE:
Our purpose of proposed website is to ensure the booking is
reserved once a date and time are selected, the system will automatically
confirm the booking and instantly record the system, without any staff action
needed.

1.3.2 SCOPE:
This project is covering the problems related to appointment
delay. It can be used in any appointment related system after adding or by
upgrading some more useful modules in the project for which the company are
providing services.

4
 2. SURVEY OF TECHNOLOGIES:
As our proposed website is about client server interaction, so it can be
either 2-Tier, 3-Tier. Our website is going to use 3-Tier Architecture, so the
required technologies can be from 3 types:

1. Front End

2. Middle Tier

3. Back End

• Front End: Very first tier that is front tier, we’ll made this using “JSP
(Java Server Pages)” which is the extension of Servlets. Since to perform
dynamic operation we have to use any dynamic language that’s why we’ll
use JSP.

• Middle Tier: We’ll use “JavaBeans” as a middle tier because of creating

middle tier we have only 2 options either EJB (Enterprise Java Beans)
and JavaBeans but our proposed website is not distributed so we have to
use JavaBeans as a middle tier.

• Back End: The “Oracle Database 10G” will be our backend option
because this is the only database available which is fully compatible with
JAVA related technologies and have more features than others.

OTHER REQUIRED TECHNOLOGIES:

• Scripting languages: JavaScript and we’ll also use its extension that is
JQuery.

• AJAX (Asynchronous JavaScript and XML): AJAX means that the user
is not left waiting for the server respond to a request but can continue
using the web page.

• Servlets: A Java servlet is a Java program that extends the capabilities

of a server. Although servlets can respond to any types of requests, they
most commonly implement applications hosted on Web servers.

Servlets are most often used to process or store a Java class in Java
EE that conforms to the Java Servlet API, a standard for implementing
Java classes which respond to requests. Servlets could in principle
communicate over any client–server protocol, but they are most often
used with the HTTP protocol. Thus "servlet" is often used as shorthand

5
 for "HTTP servlet". Thus, a software developer may use a servlet to
add dynamic content to a web server using the Java platform. The
generated content is commonly HTML, but may be other data such
as XML. Servlets can maintain state in session variables across many
server transactions by using HTTP cookies, or rewriting URLs.

The Servlet API, contained in the Java package hierarchy javax.servlet,

defines the expected interactions of the web container and a servlet.
A Servlet is an object that receives a request and generates a response
based on that request. The basic Servlet package defines Java objects to
represent servlet requests and responses, as well as objects to reflect the
servlet's configuration parameters and execution environment. The
package javax.servlet.http defines HTTP-specific subclasses of the
generic servlet elements, including session management objects that
track multiple requests and responses between the web server and a
client. Servlets may be packaged in a WAR file as a web application.

• JSP (Java Server Pages): JSP may be viewed as a high-

level abstraction of Java servlets. JSPs are translated into servlets at
runtime; each JSP servlet is cached and re-used until the original JSP is
modified.

JSP can be used independently or as the view component of a server-

side model–view–controller design, normally with JavaBeans as the
model and Java servlets (or a framework such as Apache Struts) as the
controller.
• JavaBeans: JavaBeans are classes that encapsulate many objects into a
single object (the bean). They are serializable, have a zero-argument
constructor, and allow access to properties using getter and setter
methods. The name "Bean" was given to encompass this standard, which
aims to create reusable software components for Java.

6
 3. REQUIREMENT AND ANALYSIS

• PROBLEM DEFINITION:

Problems in existing system:

o Data duplication and redundancy

o Existing system is expensive and complex

o Fixed booking time

Solution through our proposed website:

Our proposed website will solve the long waiting times for appointment
with available doctor. This will be easier to book an appointment without
taking any kind of stress because this will be available online means you can
access or book an appointment from any device and will be available 24x7
means anytime & any day. Our proposed website will allow new as well old
patients to take appointment of the doctors. New patients first fill up an online
registration form giving all the details of their illness, they are called for
physical examination by the doctor on a specified date. After going through all
the details, the doctor either confirms the registration of the patient or rejects
it. All registered patients can book the appointments of the doctors. Doctors are
available for consultation only on specific days. The appointments are booked
for a time slot of 15 minutes on specific dates.

Long waiting times for treatment in the hospital followed by short consultations
has long been a complaint. Nowadays, customers use waiting time as a decisive
factor in choosing a service provider. Therefore, idle time of both parties must
be considered in developing an appointment system although these two
objectives are contradicted to each other.

7
 • PLANNING AND SCHEDULING:

Gantt chart
We used Gantt chart for the time estimation of the project. A
tabular form is maintained where rows indicate the task and column indicates
duration. The horizontal bar that spans across column indicates duration of
the task. When multiple bars occur at the same time on the calendar, task
concurrency is implied.

Phase Task 1st Week 2nd Week 3rd Week 4th Week

I Requirement analysis

II Database Design

III Web Design

IV Coding

V Quality assurance

VI Test cases

VII Testing

VIII System security

IX Implementation

8
 Pert Chart

A PERT chart is a project management tool used to schedule,

organize, and coordinate tasks within a project. PERT stands for Program
Evaluation Review Technique. Here we have developed a pert chart related to
planning of our project. A PERT chart displays the tasks in a project along with
the dependencies between these tasks. Using a PERT chart is a great way to
define and display the dependency relationships that exist between tasks. The
order in which tasks occur is an important part of project planning and PERT
Chart simplifies the process of creating dependencies and displaying
dependencies in an easy to follow diagram.

9
 • SOFTWARE AND HARDWARE REQUIREMENTS:

Hardware Requirements:

Processor : Intel dual core

Processor Speed : 2.1GHz

RAM : 2GB

Hard Disk : 250GB

Monitor : 15.6” color

Software Requirements:

Operating System : Windows 7

Front End : JSP (Java Server Pages)

Back End : Oracle Database 10g

Server : Oracle Weblogic 12c

10
• PRELIMINARY PRODUCT DESCRIPTION:
Our proposed website has the following functions and operations:

o Taking advantage of last-minute opening

o Reduce waiting time
o No phone enquiry is needed
o Easy to book
o Cost effective
o Stress free
o Book appointment 24x7, on the go from any device

• CONCEPTUAL MODELS:

MODULES:

o Appointment Management: Status of any doctor or patient can

be queried from this module.

o Doctor Management: It keep all the doctor’s information

according to their specialty and also with the information that
particular doctor is already appointed or not. It also provides
time deals with the time slots of appointment of the doctor

o Patient Management: It deals with the patient data and their

visits with date & time.

o Query Management: Any kind of query related to “feedback”,

“complaint” and “enquiry” can be done through this module.

11
 DFD
0th level DFD

MANAGEMENT PATIENT

REQUEST ABOUT TOTAL

RESPONSE GIVEN

RESPONSE GIVEN
REQUEST ABOUT
TYPES OF
APPOINTMENTS

DISEASES YOU
TAKE CARE
0.0
ABOUT

Online
Appointment
-
System
RESPONSE GIVEN

REQUEST ABOUT
AAPOINTMENT
TIME SLOTS

DOCTOR

12
 1st level DFD
PATIENT

REQUEST FOR

CONFIRMATION
BOOKING AN
APPOINTMENT

PROVIDED
1.0

Appointment

STORE APPOINTMENT
Management
DETAILS PROVIDED

QUERY ABOUT RETRIVE

TOTAL RCORDS

REPORT
APPOINTMENTS

MANAGEMENT APPOINTMENT FILE

MANAGEMENT DOCTOR
INFORMATION PROVIDED

INFORMATION DETAILS ABOUT

DETAILS PROVIDED
ABOUT THE BOOKED
DOCTOR APPOINTMENTS
APPOINTMENTS ON EACH DAY
AND WHEN THEY WITH DISEASES
2.0
TOOK LEAVE

Doctor
REQUEST FOR DOCTOR

Management

DOCTOR
RECORDS

RECORDS
PROVIDED

DOCTOR FILE

13
 PATIENT

DETAILS ABOUT
DETAILS PROVIDED

BOOKED
APPOINTMENT’S
DATE & TIME OF
REQUESTED PATIENT 3.0

Patient

REQUEST FOR PATIENT

Management
DETAILS PROVIDED

DETAILS ABOUT PATIENT RECORDS

RECORDS
REGISTERED PROVIDED
PATIENTS

MANAGEMENT PATIENT FILE

MANAGEMENT

REQUEST ABOUT
TOTAL
REPORT PROVIDED

COMPLAINTS,
ENQUIRIES,
FEEBACKS
4.0

Query
REQUEST FOR QUERY
QUERY SUBMITTED

Management
SUBMIT MY QUERY
(OF TYPE
REPORT

COMPLAINT, QUERY REPORT

FEEDBACK, PROVIDED
ENQUIRY)

PATIENT QUERY FILE

14
 E-R Diagram

SEX

ADDRESS
PHONE
PATIENT ID

DOCTOR ID SPECIALITY

PATIENT TAKE AN
DOB APPOINTMENT

NAME PASSWORD

DOCTOR
NAME

SCHEDULES
LIST OF DOCTORS EMAIL
AVAILABLE
PHONE

ADDRESS

APPOINTMENTS
BOOKED FOR A DOCTOR
IS ACCEPTED or REJECTED
BY
NAME

PHONE
EMAIL ADMIN

15
 • FUTURE SCOPE:
This project can be used in any appointment system after adding or by
upgrading some more useful modules in the project for which the company are
providing services.

The company also has a plan to develop payment gateway system, SMS based
system in future to increase the productivity and to enhance the growth of
company. It is also planning to make mobile based app to book appointments.

4. REFERENCES:

https://docs.oracle.com/javase/tutorial/javabeans

https://docs.oracle.com/javase/tutorial/javabeans/index.html

https://docs.oracle.com/javaee/5/tutorial/doc/bnagx.htm

https://en.wikipedia.org/wiki/Model–view–controller

16