Project Report

on

Doctor Appointment Management System

Project Document

By
 Acknowledgement
The success and final outcome of this project required a lot of guidance
and assistance from many people and I am extremely privileged to have
got this all along the completion of my project. All that I have done is only
due to such supervision and assistance and I would not forget to thank
them.
I respect and thank Mr./Ms. [NAME 1], for providing me an opportunity
to do the project and giving us all support and guidance which made me
complete the project duly. I am extremely thankful to [her/him] for
providing such a nice support and guidance.

I owe my deep gratitude to our project guide [NAME 2], who took keen
interest on our project work and guided us all along, till the completion of
our project work by providing all the necessary information for
developing a good project.

I heartily thank our internal project guide, [Name 3], [Position] ,

[Department] for her/his guidance and suggestions during this project
work.

I am thankful to and fortunate enough to get constant encouragement,

support and guidance from all Teaching staffs of [Department name]
which helped us in successfully completing our project work.

----------------------
 Abstract
“Doctor Appointment Management System” is responsible for keeping all
the record of doctor appointment which is taken by users. This system
helps the patient take the appointment online and save time.

The main objective of “Doctor Appointment Management System”

project is to providing easier doctor appointment and gets appointment
online which save lots of time.
 Introduction
Introduction:-

“Doctor Appointment Management System is a web-based technology

that will manage to automate the existing manual system by the help of
computerized equipments and full-fledged computer software, so that
their valuable data/information can be stored for a longer period
with easy accessing and manipulation of the same. Basically the
project describes how to manage for good performance and better
services for the clients. This automatic system delivers data processing in
very high speed in systematic manner.

In Doctor Appointment Management System we use PHP and MySQL

Database. This project has two modules i.e., doctor and user.

Doctor Module

1. Dashboard: In this section, doctor can briefly view the total number of
the new appointment, total approved appointment and total cancelled
appointment.
2. Appointment: In this section, doctor views the appointment details
and they have also the right to change application status according to
current status.
3. Reports: In this section doctor can view the appointment details in a
particular period.
4. Search: In this section, doctor can search appointment with the help of
user appointment number/Name/Mobile Number
Doctor can also update his profile, change the password and recover the
password.
User Module(User not need to register)

1. Home Page: In this section, user can view the welcome page of the
web application.
2. Book: In this section, user can sent the appointment request.
3. Check Appointment: In this section, user can search appointment with
the help of user appointment number/Name/Mobile Number
 Purpose
The main purpose of the "Doctor Appointment Management System" is
to manage the details of Doctor and Appointment. It manages all the
information about Doctor and doctor appointments. The purpose of
the project is to build an application program to reduce the manual
work for managing the Doctor appointment. It tracks all the details about
the appointments and Doctor Schedule.

Scope
The Software design document would demonstrate how the design will
accomplish the functional and non- functional requirements captured in
the Software Requirement specification (SRS). The document will provide
a framework to the programmers through describing the high level
components and architecture, sub systems, interfaces, database design
and algorithm design. This is achieved through the use of architectural
patterns, design patterns, sequence diagrams, class diagrams, relational
models and user interfaces
 Requirement Specification
Hardware Configuration :

Client Side:
MfgdfRA RAM 512 MB

Hard disk 10 GB

Processor 1.0 GHz

Server side:
RAM 1 GB
Hard disk 20 GB
Processor 2.0 GHz

Software Requirement:

Client Side:

Google Chrome or any

Web Browser compatible browser
Operating System
Windows or any equivalent OS
Server Side:

Web Server APACHE

Server side Language PHP5.6 or above version

Database Server MYSQL

Google Chrome or any

Web Browser compatible browser

Operating System Windows or any equivalent OS

APACHE
The Apache HTTP Server Project is an effort to develop and maintain an
open-source HTTP server for modern operating systems including UNIX
and Windows. The goal of this project is to provide a secure, efficient and
extensible server that provides HTTP services in sync with the current
HTTP standards.
The Apache HTTP Server ("httpd") was launched in 1995 and it has been
the most popular web server on the Internet since April 1996. It has
celebrated its 20th birthday as a project in February 2015.
PHP
• PHP stands for PHP: Hypertext Preprocessor.

• PHP is a server-side scripting language, like

ASP.
• PHP scripts are executed on the server.
• PHP supports many databases (MYSQL, Informix, Oracle, Sybase,
Solid, Generic ODBC, etc.).

• PHP is an open source software .

• PHP is free to download and use.

MYSQL
• MYSQL is a database server
• MYSQL is ideal for both small and large applications
• MYSQL supports standard SQL
• MYSQL compiles on a number of platforms

• MYSQL is free to download and use

• How to access MySQL:

http://localhost/phpmyadmin
 Feasibility analysis

The analysis of the requirement has lead to a conclusion that the project is
feasible with respect to time and cost. The data collection from the field is
assured by the client to provide. The technology used to develop is almost
Open Source, therefore less cost for implementation and maintenance will
be involved. A feasibility study is an analysis used in measuring the ability
and likelihood to complete a project successfully including all relevant
factors. It must account for factors that affect it such as economic,
technological and time factors. It is used to assess the strengths and
weaknesses of a proposed project and present directions of activities
which will improve a project and achieve desired results.
Economic feasibility
The purpose of economic feasibility assessment is to determine the
positive economic benefits to the organization that the proposed system
will provide. The assessment typically involves a cost/benefits analysis.

Technical feasibility
Technical analysis is a trading tool employed to evaluate securities and
attempt to forecast the future movement. I am using java language and
other tools like net beans to develop the software.
Operational feasibility
Operational feasibility is a measure of how well proposed system solves
the problems, and takes advantage of the opportunities identified during
scope definition and how it satisfies the requirements analysis phase of the
system development.
 Analysis and Design

Analysis:

In present all doctor appointment work done on the paper. The whole

year data is stored in the registers. We can’t generate reports as per our

requirements because its take more time to calculate report of doctor

appointments.

Disadvantage of present system:

• Not user friendly: The present system not user friendly because

data is not stored in structure and proper format.

• Manual Control: All report calculation is done manually so there is a

chance of error.

• Lots of paper work: Visitors maintain in the register so lots of paper

require storing details.

• Time consuming
Design Introduction:
Design is the first step in the development phase for any techniques and
principles for the purpose of defining a device, a process or system in
sufficient detail to permit its physical realization.

Once the software requirements have been analyzed and specified the
software design involves three technical activities - design, coding,
implementation and testing that are required to build and verify the
software.

The design activities are of main importance in this phase, because in this
activity, decisions ultimately affecting the success of the software
implementation and its ease of maintenance are made. These decisions
have the final bearing upon reliability and maintainability of the system.
Design is the only way to accurately translate the customer’s
requirements into finished software or a system.

Design is the place where quality is fostered in development. Software

design is a process through which requirements are translated into a
representation of software. Software design is conducted in two steps.
Preliminary design is concerned with the transformation of requirements
into data
UML Diagrams:
Actor:
A coherent set of roles that users of use cases play when interacting
with the use `cases.

Use case:A description of sequence of actions, including variants, that a

system performs that yields an observable result of value of an actor.

UML stands for Unified Modeling Language. UML is a language for

specifying, visualizing and documenting the system. This is the step while
developing any product after analysis. The goal from this is to produce a
model of the entities involved in the project which later need to be built.
The representation of the entities that are to be used in the product
being developed need to be designed.

USECASE DIAGRAMS:

Use case diagrams model behavior within a system and helps the
developers understand of what the user require. The stick man
represents what’s called an actor.

Use case diagram can be useful for getting an overall view of the system
and clarifying who can do and more importantly what they can’t do.

Use case diagram consists of use cases and actors and shows the
interaction between the use case and actors.

• The purpose is to show the interactions between the use case

and actor.
• To represent the system requirements from user’s perspective.
• An actor could be the end-user of the system or an external
system.

USECASE DIAGRAM: A Use case is a description of set of sequence of

actions. Graphically it is rendered as an ellipse with solid line including
only its name. Use case diagram is a behavioral diagram that shows a set
of use cases and actors and their relationship. It is an association
between the use cases and actors. An actor represents a real-world
object. Primary Actor – Sender, Secondary Actor Receiver.
Use Case Diagrams:

Doctor

Sign In/Signup

Dashboard

Manage Appointment

Search Appointment

Generate Reports

Update Profile

Change Password

Password Recovery
User

Visit Website

Book Appointment

Check Appointment Status

View Contact

View About Us
Class Diagram:

A description of set of objects that share the same attributes operations,

relationships, and semantics.
ER Diagram:

The Entity-Relationship (ER) model was originally proposed by Peter in

1976 [Chen76] as a way to unify the network and relational database
views. Simply stated the ER model is a conceptual data model that views
the real world as entities and relationships. A basic component of the
model is the Entity-Relationship diagram which is used to visually
represent data objects. Since Chen wrote his paper the model has been
extended and today it is commonly used for database design for the
database designer, the utility of the ER model is:

• It maps well to the relational model. The constructs used in the ER

model can easily be transformed into relational tables.
• It is simple and easy to understand with a minimum of training.
Therefore, the model can be used by the database designer to
communicate the design to the end user.
• In addition, the model can be used as a design plan by the database
developer to implement a data model in specific database
management software.

ER Notation
There is no standard for representing data objects in ER diagrams. Each
modeling methodology uses its own notation. The original notation used
by Chen is widely used in academics texts and journals but rarely seen in
either CASE tools or publications by non-academics. Today, there are a
number of notations used; among the more common are Bachman,
crow's foot, and IDEFIX.

All notational styles represent entities as rectangular boxes and

relationships as lines connecting boxes. Each style uses a special set of
symbols to represent the cardinality of a connection. The notation used in
this document is from Martin. The symbols used for the basic ER
constructs are:

• Entities are represented by labeled rectangles. The label is the name

of the entity. Entity names should be singular nouns.

• Relationships are represented by a solid line connecting two

entities. The name of the relationship is written above the line.

Relationship names should be verbs

• Attributes, when included, are listed inside the entity rectangle.

Attributes which are identifiers are underlined. Attribute names

should be singular nouns.

• Cardinality of many is represented by a line ending in a crow's foot.

If the crow's foot is omitted, the cardinality is one.

Existence is represented by placing a circle or a perpendicular bar on the

line. Mandatory existence is shown by the bar (looks like a 1) next to the
entity for an instance is required. Optional existence is shown by placing a
circle next to the entity that is optional.
ER Diagram
MySQL Data Tables:
Doctor Table:(Table name is tbldoctor)

This store doctor personal and login details.

Specialization Table(Table name is tblspecialization)

This table stores the specialization of doctor.

Appointment Table: (Table name is tblappointment)

This table stores the details of appointment and doctor remark.

Data Flow Diagrams

A Data Flow Diagram (DFD) is a traditional visual representation of the

information flows within a system. A neat and clear DFD can depict the
right amount of the system requirement graphically. It can be manual,
automated, or a combination of both.

It shows how data enters and leaves the system, what changes the
information, and where data is stored.

The objective of a DFD is to show the scope and boundaries of a system as

a whole. It may be used as a communication tool between a system analyst
and any person who plays a part in the order that acts as a starting point
for redesigning a system. The DFD is also called as a data flow graph or
bubble chart.

The following observations about DFDs are essential:

1. All names should be unique. This makes it easier to refer to elements

in the DFD.
2. Remember that DFD is not a flow chart. Arrows is a flow chart that
represents the order of events; arrows in DFD represents flowing
data. A DFD does not involve any order of events.
3. Suppress logical decisions. If we ever have the urge to draw a
diamond-shaped box in a DFD, suppress that urge! A diamond-
shaped box is used in flow charts to represents decision points with
multiple exists paths of which the only one is taken. This implies an
ordering of events, which makes no sense in a DFD.
4. Do not become bogged down with details. Defer error conditions and
error handling until the end of the analysis.

Standard symbols for DFDs are derived from the electric circuit diagram
analysis and are shown in fig:
Circle: A circle (bubble) shows a process that transforms data inputs into
data outputs.

Data Flow: A curved line shows the flow of data into or out of a process or
data store.

Data Store: A set of parallel lines shows a place for the collection of data
items. A data store indicates that the data is stored which can be used at a
later stage or by the other processes in a different order. The data store
can have an element or group of elements.

Source or Sink: Source or Sink is an external entity and acts as a source of

system inputs or sink of system outputs.
Zero Level DFD

Appointment
Management

Login
Doctor
Management Management

DAMS

Specialization Password
Management Management

Webpages

Management
First Level DFD

Appointment Password
Management
Management

Doctor Password
Management
Management
DAMS

Specialization Login

Management Management

Generate
Authorization
Report
Management
Second Level DFD
Doctor Signup/ Check
Login Roles
to of
system access

Manage
Appointment

Generate Report

Forgot
Passwor Check
d Creden Search
tial Appointment

Manage Update Profile

Module
s

Change
Password
 Implementation and System Testing
After all phase have been perfectly done, the system will be implemented
to the server and the system can be used.

System Testing

The goal of the system testing process was to determine all faults in our project
.The program was subjected to a set of test inputs and many explanations were
made and based on these explanations it will be decided whether the program
behaves as expected or not. Our Project went through two levels of testing

1. Unit testing
2. Integration testing

UNIT TESTING
Unit testing is commenced when a unit has been created and effectively
reviewed .In order to test a single module we need to provide a
complete environment i.e. besides the section we would require

• The procedures belonging to other units that the unit under test
calls
• Non local data structures that module accesses
• A procedure to call the functions of the unit under test with
appropriate parameters
1. Test for the admin module

• Testing admin login form-This form is used for log in of

administrator of the system. In this form we enter the username
and password if both are correct administration page will open
otherwise if any of data is wrong it will get redirected back to the
login page and again ask the details.
• Report Generation: admin can generate report from the main
database.

INTEGRATION TESTING

In the Integration testing we test various combination of the project

module by providing the input.

The primary objective is to test the module interfaces in order to confirm

that no errors are occurring when one module invokes the other module.
 Evaluation
Project URL: http://localhost/dams

Home Page
Search Appointment

Doctor Panel

Signup
Login Page

Forgot Password
Dashboard

Doctor Profile
Change Password

New Appointment
View new appointment

Approved Appointment
View Approved Appointment

Cancelled Appointment
View Cancelled Appointment

Search Appointment

Report
View between dates reports
 Conclusion
This Application provides a computerized version of doctor appointment
which will benefit the people who wants to take appointment with
doctor online.

It makes entire process online and can generate reports. It has a facility
of doctor login where doctor can manage user appointment and
generate appointment report.

The Application was designed in such a way that future changes can be
done easily. The following conclusions can be deduced from the
development of the project.

• Automation of the entire system improves the productivity.

• It provides a friendly graphical user interface which proves to
be better when compared to the existing system.
• It gives appropriate access to the authorized users depending
on their permissions.
• It effectively overcomes the delay in communications.
• Updating of information becomes so easier.
• System security, data security and reliability are the striking
features.
• The System has adequate scope for modification in future if it
is necessary.
 Future Enhancement
I have tried to design the software in such a way that the user may not have
any difficulty in using this system and further expansion is also possible.
New requirements will be added and risk will be analyzed in every phase
until the requirement of user will not be fulfilled. The most priority will be
given to keep confidential data secure and easy and simple for use.
The further enhancements which can be made in the system are:
• Any requirement that will make system easy to use or make a system
secure, these requirement will be add using Spiral Model. Other
requirement related to government or municipality will be added when
required.
• For the identity of user and for their data integrity, digital signature can be
added to this system.
• For the identity of user and for verification, image of user can be added to
this system.
• There will be provision of filling form in multiple languages.
• A great concern will be given on frontend design which will make user to
use system easily and enjoy while using this system.
 Bibliography
For PHP

• https://www.w3schools.com/php/default.asp
• https://www.sitepoint.com/php/
• https://www.php.net/

For MySQL

• https://www.mysql.com/
• http://www.mysqltutorial.org

For XAMPP

• https://www.apachefriends.org/download.html