DBMS Mini Project Report on

DOCTOR APPOINTMENT SYSTEM

Submitted in partial fulfilment of the

MASTER OF COMPUTER APPLICATION

By

Sabita Murmu
Enrolment No: AJU/210799

Under the esteemed guidance of

Dr. Arvind Kumar Pandey

(HEAD OF DEARTMENTS)
&
Ms. Alka Singh
(INTERNAL GUIDE)

DEPARTMENT OF COMPUTER SCIENCE & INFORMATION TECHNOLOGY

ARKA JAIN UNIVERSITY, JHARKHAND

JAMSHEDPUR

2021-2023
 ARKA JAIN UNIVERSITY

DBMS MINI

PROJECT REPORT

ON

DOCTOR APPOINTMENT SYSTEM

IN PARTIAL FULFILLMENT OF REQUIREMENT

DEPARTMENT OF COMPUTER SCIENCE

BATCH 2021-2023

GUIDED BY: PREPARED BY:

Dr. Arvind Kumar Pandey

& Sabita Murmu

Ms. Alka Singh

SUBMITTED TO
DEPARTMENT OF COMPUTER SCIENCE & IT 2|P age

ARKA JAIN UNIVERSITY

3
 ABSTRACT

The purpose of Doctor Appointment System is to automate the existing manual system by the help of
computerized equipment’s and full-fledged computer software, fulfilling their requirements, so that their
valuable data/information can be stored for a longer period with easy accessing and manipulation of the same.
The required software and hardware are easily available and easy to work with.

Doctor Appointment System, as described above, can lead to error free, secure, reliable and fast management
system. It can assist the user to concentrate on their other activities rather to concentrate on the record keeping. That
means that one need not be distracted by information that is not relevant, while being able to reach the information.

The aim is to automate its existing manual system by the help of computerized equipment’s and full-fledged computer
software, fulfilling their requirements, 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.

4
 ACKNOWLEDGEMENT

It is a genuine pleasure to express my profound gratitude and deep regards to my Internal Guide MS. ALKA
SINGH and our HOD DR. ARVIND KUMAR PANDEY for their exemplary guidance, monitoring and
constant encouragement. I would like to express my special thanks to ARKA JAIN UNIVERSITY who gave
me the golden opportunity to do this wonderful project on the topic Doctor Appointment System, which helped
me in doing a lot of Research and I came to know about so many new things.

With Regards

Sabita Murmu (AJU/210799)

Roll no. 14 (MCA)

5
 DECLARATION

We hereby declare that the project entitled, “DOCTOR APPOINTMENT SYSTEM” done at Arka Jain
University, has not been in any case duplicated to submit to any other university for the award of any degree. To
the best of my knowledge other than me, no one has submitted to any other university.
The project is done in partial fulfillment of the requirements for the award of degree of MASTERS OF
COMPUTER APPLICATIONS to be submitted as final semester project as part of our curriculum.

Sabita Murmu
Signature of the Student

6
 Table of Contents

Chapter 1 Introduction ........................................................................................................................................... 8

1.1 Introduction ......................................................................................................................................................................8
1.2 Objective ..........................................................................................................................................................................8
1.3 Scope and Feasibility .......................................................................................................................................................8
Chapter 2: Software and Hardware Requirements ............................................................................................. 9
2.1 Software Requirements ....................................................................................................................................................9
2.2 Hardware Requirements ...................................................................................................................................................9
Chapter 3: System Design ..................................................................................................................................... 10
3.1 Data Flow Diagrams ......................................................................................................................................................12
3.1.1 Zero Level DFD .................................................................................................................................................12
3.1.2 First Level DFD .................................................................................................................................................13
3.1.3 Second Level DFD .............................................................................................................................................14
3.2 ER Diagram....................................................................................................................................................................15
3.3 Normalization.................................................................................................................................................................16
3.3.1 Normalization level 0 .........................................................................................................................................16
3.3.2 Normalization level 1 .........................................................................................................................................17
3.3.3 Normalization level 2 .........................................................................................................................................18
Chapter 4: Screenshots ......................................................................................................................................... 19
Chapter 5: Implementation and Testing ............................................................................................................. 26
5.1 Implementation ..............................................................................................................................................................26
5.2 Testing ............................................................................................................................................................................26
5.2.1 Testing Generation .............................................................................................................................................26
5.2.2 Software Testing ................................................................................................................................................26
5.3 Code...............................................................................................................................................................................27
Chapter 6: Conclusion...............................................................................................................................................
6.1 Future Scope...................................................................................................................................................................52

7
 Ch 1: Introduction
1.1 Introduction
This project is a web based management system for a doctor appointment. The project objective is to deliver the
online shopping application into platform.

Doctor appointment is the process whereby consumers directly buy goods or services from a seller in real-time,
without an intermediary service, over the Internet. It is a form of electronic commerce. This project is an attempt
to provide the advantages of online shopping to customers of a real shop. It helps buying the products in the shop
anywhere through internet by using an android device. Thus the customer will get the service of online shopping
and home delivery from his favorite shop.

1.2 Objective
The objective of the project is to make an application in android platform to purchase items in an existing shop.
In order to build such an application complete web support need to be provided. A complete and efficient web
application which can provide the online shopping experience is the basic objective of the project. The web
application can be implemented in the form of an android application with web view.

1.3 Scope and Feasibility

This system can be implemented to any shop in the locality or to multinational branded shops having retail outlet
chains. The system recommends a facility to accept the orders 24*7 and a home delivery system which can make
customers happy.
If shops are providing an online portal where their customers can enjoy easy shopping from anywhere, the shops
won’t be losing any more customers to the trending online shops such as flipchart or eBay. Since the application
is available in the Smartphone it is easily accessible and always available.

8
 Ch 2: Software & Hardware Requirements

2.1 Software Requirements

Technology Tools

Front End HTML, CSS, JavaScript

Back End PHP, MySQL

Framework Bootstrap

Software XAMPP, Visual Studio Code

2.2 Hardware Requirements

RAM 2GB or above.

Processor Intel Dual Core or above.

Operating System Windows 7 or above, Ubuntu or any Linux

based system.

Hosting Amazon AWS, Go Daddy, HostGator,

Bluehostetc.

CMS Word Press etc.

Domain .com, .in etc.

Browser Google Chrome, Mozilla Firefox etc.

9
 Ch 3: System Design
3.1 Data Flow Diagrams
A data flow diagram is a graphical technique that depicts the information flow and transformation that are
applied as a data move from input to the output source in the system.it is used to represent any software or
system at any level of abstraction. To construct data flow diagram, we used:

Arrows:

2. Circle :

3. Rectangle :

4. Open-ended boxes:

An arrow identifies data flow diagram in motion .It is a pipeline through which information flows. Circle stand
for process that convert data into information. Square define a source for destination of the system data. Open-
ended boxes represent a data/store a data at rest.
1. Arrows should not cross each other.
2. Squares, circles and files must bear name.
3. Decomposed data flow must be balanced.
4. No two data flows, square or circle can have the same name.5. Draw all data flows around the outside of the
diagram.

10
3.1.1 Zero Level DFD

3.1.2 First Level DFD

11
3.1.3 Second Level DFD

12
 3.3 ER Diagrams

Login_username
Login_role_id

User_password

#login_id
Login
Role_name

#Role_id
User_name #User_id
Role_desc

User_mobile
Has Roles
User
#per_id
User_email

Permission Per_role_id

User_address

Per_name Per_module

Doc_name Manage

Doc_mobile
Do_sch_desc

#doc_id
Do_sch_date
Schedules
Doctor
Doc_email Do_fee_amt
Do_sch_time
#do_sch_id
Doc_pass

#do_fee_i
Doc_add Has Fees d
Do_sch_type

Do_fee_toti Do_fee_pay

Booking

Do_fee_type
13
Book_desc
#book_id
Book_type
3.4 Normalization

3.4.1 Normalization Raw Ratabase

Colunm name Data type Key contraints

Id int(11) NOT NULL

Specialization_name varchar(40) NULL

Doctor_id Int(11) NOT NULL

Specialization_Id Int(11) NOT NULL

Qualification_name Varchar(100) NULL

Institute_name Varchar(100) NULL

Procurement_year Varchar(100) NULL

First_name Varchar(50) NULL

Last_name Varchar(50) NULL

Professional_statement Varchar(4000) NULL

Practicing_from Varchar(100) NULL

Hospital_name Varchar(100) NULL

City Varchar(100) NULL

Country Varchar(100) NULL

Start_date Varchar(100) NULL

End_date Varchar(100) NULL

Day_of_the_weak Varchar(100) NULL

Is_available Varchar(40) NULL

Reason_of_unavailability Varchar(100) NULL

Is_review_anonymous Varchar(40) NULL

is_doctor_recommended Varchar(40) NULL

App_booking_channel_name Varchar(40) NULL

14
3.4.2 Normalisation level 1 (1NF)

Specification

id int(11) NOT
NULL
Specification_name varchar(100) NULL

Doctor Specification

id int(11) NOT NULL

Doctor_id int(11) NOT NULL

Specification_id int(11) NOT NULL

Qualification

id int(11) NOT NULL

Doctor_id int(11) NULL

Qualification_name varchar(100) NULL

Institute_name varchar(100) NULL

Procurement_year Varchar(100) NULL

Doctor

id int(11) NULL

First_name varchar(50) NULL

Last_name varchar(50) NULL

Professional_statement varchar(4000) NULL

Practicing_from varchar(100) NNULL

15
Hospital affiliation
id int(11) NULL

Doctor_id Int(11) NULL

Hospital_name varchar(100) NULL

City varchar(100) NULL

Country varchar(100) NULL

Start_date varchar(100) NULL

End_date varchar(100) NULL

16
3.4.3 Normalisation level 2 (2NF)

Client Review

id int(11) NOT NULL

User_account_id int(11) NOT NULL

Doctor_id int(11) NOT NULL

Is_review_anonymous char(50) NULL

Wait_time_rating int(11) NULL

Bedside_manner_rating int(11) NULL

Overall_rating int(11) NULL

Client Account

id int(11) NOT NULL

First_name Varchar2(100) NULL

Last_name Varchar2(100) NULL

Contact_number int(11) NULL

email Varchar2(100) NULL

17
Chapter 4: Screenshots

18
19
20
21
22
23
 Chapter 5: Implementation and Testing

5.1 Implementation

This activity includes programming, testing and integration of modules into a progressively
more complete system. Implementation is the process of collect all the required parts and
assembles them into a major product.

5.2 Testing

5.2.1 Test Generation

This activity generates a set of test data, which can be used to test the new system
before accepting it. In the test generation phase, all the parts are come which are to be
tested to ensure that system does not produce any error. If there are some errors then
we remove them and further it goes for accepting.

5.2.2 Software Testing

Software testing is a critical element of software quality assurance and moments the
ultimate reviews of specification, design and coding. Testing presents an interesting
anomaly for the software engineer.

Testing objectives include:

1. Testing is a process of executing a program with the intent of finding an error.

2. A good test case is one that has probability of finding an as yet undiscovered
error.
3. A successful test is one that uncovers an undiscovered error.

Testing Principles:

1. All tests should be traceable to end user requirements.

2. Test should be planned long before testing begins.
3. Testing should begin on a small scale and progress towards testing in large.
4. Exhaustive testing is not possible.
5. To be most effective testing should be conducted by an independent third.

24
5.3 Code

about.php

<!-- Masthead-->
<header class="masthead">
<div class="container h-100">
<div class="row h-100 align-items-center justify-content-center text-center">
<div class="col-lg-10 align-self-end mb-4" style="background: #0000002e;">
<h1 class="text-uppercase text-white font-weight-bold">About Us</h1>
<hr class="divider my-4" />
</div>

</div>
</div>
</header>

<section class="page-section">
<div class="container">
<?php echo html_entity_decode($_SESSION['setting_about_content']) ?>

</div>
</section>

doctor.php

<!-- Masthead-->
<header class="masthead">
<div class="container h-100">
<div class="row h-100 align-items-center justify-content-center text-center">
<div class="col-lg-10 align-self-end mb-4" style="background: #0000002e;">
<h1 class="text-uppercase text-white font-weight-bold">About Us</h1>
<hr class="divider my-4" />
</div>

</div>
</div>
</header>

<section class="page-section">
<div class="container">
<?php echo html_entity_decode($_SESSION['setting_about_content']) ?>

</div>
</section>

25
home.php

<?php
include 'admin/db_connect.php';
?>
<style>
#portfolio .img-fluid{
width:100%
}
</style>
<header class="masthead">
<div class="container h-100">
<div class="row h-100 align-items-center justify-content-center text-center">
<div class="col-lg-10 align-self-end mb-4 page-title">
<h3 class="text-white">Welcome to <?php echo $_SESSION['setting_name'];
?></h3>
<hr class="divider my-4" />
<a class="btn btn-primary btn-xl js-scroll-trigger"
href="index.php?page=doctors">Find a Doctor</a>

</div>

</div>
</div>
</header>
<section class="page-section" id="menu">

</section>
<div id="portfolio" class="container">
<div class="container-fluid p-0">
<div class="row">
<div class="col-lg-12 text-center">
<h2 class="mb-4">Medical Specialties</h2>
<hr class="divider">

</div>
</div>
<div class="row no-gutters">
<?php
$cats = $conn->query("SELECT * FROM medical_specialty order by id asc");
while($row=$cats->fetch_assoc()):
?>
<div class="col-lg-4 col-sm-6">
<a class="portfolio-box" href="index.php?page=doctors&sid=<?php echo
$row['id'] ?>">
<img class="img-fluid" src="assets/img/<?php echo $row['img_path'] ?>"
alt="" />

26
 <div class="portfolio-box-caption">
<div class="project-name"><?php echo $row['name'] ?></div>
<div class="project-category text-white">Find Doctor</div>
</div>
</a>
</div>
<?php endwhile; ?>

</div>
</div>
</div>
<script>

$('.view_prod').click(function(){
uni_modal_right('Product','view_prod.php?id='+$(this).attr('data-id'))
})
</script>

set_appointment.php

<?php
include ('admin/db_connect.php')
?>
<style>
#uni_modal .modal-footer{
display: none
}
</style>
<div class="container-fluid">
<div class="col-lg-12">
<div id="msg"></div>
<form action="" id="manage-appointment">
<input type="hidden" name="doctor_id" value="<?php echo
$_GET['id'] ?>">
<div class="form-group">
<label for="" class="control-label">Date</label>
<input type="date" value="" name="date" class="form-control"
required>
</div>

<div class="form-group">
<label for="" class="control-label">Time</label>
<input type="time" value="" name="time" class="form-
control" required>
</div>

<hr>
<div class="col-md-12 text-center">

27
 <button class="btn-primary btn btn-sm col-md-
4">Request</button>
<button class="btn btn-secondary btn-sm col-md-4 "
type="button" data-dismiss="modal" id="">Close</button>
</div>
</form>
</div>
</div>

<script>

$("#manage-appointment").submit(function(e){
e.preventDefault()
start_load()
$.ajax({
url:'admin/ajax.php?action=set_appointment',
method:'POST',
data:$(this).serialize(),
success:function(resp){
resp = JSON.parse(resp)
if(resp.status == 1){
alert_toast("Request submitted successfully");
end_load();
$('.modal').modal("hide");
}else{
$('#msg').html('<div class="alert alert-
danger">'+resp.msg+'</div>')
end_load();
}
}
})
})
</script>

signup.php

<?php session_start() ?>

<div class="container-fluid">
<form action="" id="signup-frm">
<div class="form-group">
<label for="" class="control-label">Name</label>
<input type="text" name="name" required="" class="form-control">
</div>
<div class="form-group">
<label for="" class="control-label">Contact</label>
<input type="text" name="contact" required="" class="form-control">
</div>
<div class="form-group">

28
 <label for="" class="control-label">Address</label>
<textarea cols="30" rows="3" name="address" required=""
class="form-control"></textarea>
</div>
<div class="form-group">
<label for="" class="control-label">Email</label>
<input type="email" name="email" required="" class="form-control">
</div>
<div class="form-group">
<label for="" class="control-label">Password</label>
<input type="password" name="password" required="" class="form-
control">
</div>
<button class="button btn btn-info btn-sm">Create</button>
</form>
</div>

<style>
#uni_modal .modal-footer{
display:none;
}
</style>
<script>
$('#signup-frm').submit(function(e){
e.preventDefault()
$('#signup-frm button[type="submit"]').attr('disabled',true).html('Saving...');
if($(this).find('.alert-danger').length > 0 )
$(this).find('.alert-danger').remove();
$.ajax({
url:'admin/ajax.php?action=signup',
method:'POST',
data:$(this).serialize(),
error:err=>{
console.log(err)
$('#signup-frm button[type="submit"]').removeAttr('disabled').html('Create');

},
success:function(resp){
if(resp == 1){
location.reload();
}else{
$('#signup-frm').prepend('<div class="alert alert-
danger">Email already exist.</div>')
$('#signup-frm
button[type="submit"]').removeAttr('disabled').html('Create');
}
}
})
})

29
</script>

view_doctor_schedule.php

<style>
#uni_modal .modal-footer{
display: none;
}
</style>
<?php
include'admin/db_connect.php';
$qry = $conn->query("SELECT * FROM doctors_schedule where
doctor_id=".$_GET['id']);
?>
<div class="container-fluid">
<div class="col-lg-12">
<div class="row">
<table class="table table-striped table-bordered">
<thead>
<tr>
<th class="text-center">Day</th>
<th class="text-center">Schedule</th>
</tr>
</thead>
<tbody>
<?php while($row=$qry->fetch_assoc()): ?>
<tr>
<th class="text-center"><?php echo $row['day']
?></th>
<th class="text-center"><?php echo date("h:i
A",strtotime($row['time_from'])).' - '.date("h:i A",strtotime($row['time_to'])) ?></th>
</tr>
<?php endwhile; ?>
</tbody>
</table>
</div>
<hr>
<div class="row">
<button class="btn btn-secondary btn-sm col-md-4 offset-md-4 "
type="button" data-dismiss="modal" id="">Close</button>
</div>
</div>
</div>
<script>
$('#edit').click(function(){
uni_modal("Edit "+$('#uni_modal .modal-
title').html(),'manage_doctor_schedule.php?did=<?php echo $_GET['id'] ?>','mid-large');
})</script>

30
 Chapter 6: Conclusion
6.1 Future Scope

The project entitled Doctor Appointment system was completed successfully. The
system has been developed with much care and free of errors and at the same time it is
efficient and less time consuming. The purpose of this project was to develop a web
application and an android application for purchasing items from a shop.

This project helped us in gaining valuable information and practical knowledge on

several topics like designing web pages using html & css, usage of responsive
templates, designing of android applications, and management of database using
MySQL. The entire system is secured. Also the project helped us understanding
about the development phases of a project and software development life cycle. We
learned how to test different features of a project.
This project has given us great satisfaction in having designed an application which
can be implemented to any nearby shops or branded shops selling various kinds of
products by simple modifications. There is a scope for further development in our
project to a great extent.A number of features can be added to this system in future
like providing moderator more control over products so that each moderator can
maintain their own products. Another feature we wished to implement was providing
classes for customers so that different offers can be given to each class. System may
keep track of history of purchases of each customer and provide suggestions based on
their history. These features could have implemented unless the time did not limited
us.

31