Abstract of Project

The purpose of Doctor Appointment System is to automate the existing manual system
by the help of computerized equipments 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. Thus it will help organization in better utilization of resources.

The organization can maintain computerized records without redundant entries. That
means that one need not be distracted by information that is not relevant, while being able to
reach the information.

Basically the project describes how to manage for good performance and better
services for the patients.

Page | 1
 Objective & Requirement of Project

Objective to develop this project is to reduce manual work in terms of using system
and by doing that it will also helps in reducing time of waiting for patient in Government
hospitals and to the places where a large amount of patient visits daily.

Also by implementing this system, data of both patients and doctors can be managed,
manipulate and save for future reference easily.

The main objective of the Project on Doctor Appointment System is to manage the
details of Doctor, Appointment, Patient, Booking, Doctor Schedule. It manages all the
information about Doctor, Doctor Fees, Doctor Schedule, Doctor.

The project is totally built at administrative end and thus only the administrator is
guaranteed the access. The purpose of the project is to build an application program to reduce
the manual work for managing the Doctor, Appointment, Doctor Fees, Patient. It tracks all the
details about the Patient, Booking, Doctor Schedule.

Functionalities provided by Doctor Appointment System:

 To reduce manual entry task at government hospital and other health organizations.
 Provides the searching facilities based on various factors. Such as Doctor, Patient,
Booking, Doctor Schedule
 Manage records/data of Patient and Doctor
 Automate manual system
 Manage the information of Appointment
 Shows the information and description of the Doctor, Patient
 To increase efficiency of managing the Doctor, Appointment
 Minimize waiting time for patient visit by assigning time-slots etc.

Page | 2
 Software and Hardware Requirements

Basic requirement to install and run any Project on any system will need a computer
that meets these minimum requirements:

Software Requirements:

Component Specification

Language Python 2.7

Database MySQL Server

Operating System Windows 10 (worked on), Windows 7

Web Framework Django 1.11

Browser Chrome, IE, Mozilla etc.

Database JDBC Driver mysql-connector-python-py2.7

Hardware Requirements:

Component Specification

Ram 512 MB

Processor Intel core i5 (worked on)

Hard Disk 20 GB

Monitor 15” color monitor

Keyboard 122 Keys

Page | 3
 Feasibility Study

After doing the project Doctor Appointment System, study and analyzing all the
existing or required functionalities of the system, the next task is to do the feasibility study for
the project. All projects are feasible - given unlimited resources and infinite time.
Feasibility study includes consideration of all the possible ways to provide a solution to the
given problem. The proposed solution should satisfy all the user requirements and should be
flexible enough so that future changes can be easily done based on the future upcoming
requirements.

A. Economical Feasibility

This is a very important aspect to be considered while developing a project. We

decided the technology based on minimum possible cost factor.
All hardware and software cost has to be borne by the organization.
Overall we have estimated that the benefits the organization is going to receive from the
proposed system will surely overcome the initial costs and the later on running cost for
system.

B. Technical Feasibility

This included the study of function, performance and constraints that may affect the
ability to achieve an acceptable system. For this feasibility study, we studied complete
functionality to be provided in the system, as described in the System Requirement
Specification (SRS), and checked if everything was possible using different type of frontend
and backend platforms.

C. Operational Feasibility

No doubt the proposed system is fully GUI based that is very user friendly and all
inputs to be taken all self-explanatory even to a layman. Besides, a proper training has been
conducted to let know the essence of the system to the users so that they feel comfortable with
new system. As far our study is concerned the clients are comfortable and happy as the system
has cut down their loads and doing

Page | 4
 Analysis of Proposed System and System Requirements

System Analysis:

System analysis is a process of gathering and interpreting facts/data, diagnosing

problems and the information about the Doctor Appointment System to recommend
improvements on the system. It is a phase which contains problem solving activity that
requires communication/research on or between the system users and system developers.

This process contains study of minutest detail and analysis based on that. The system is
viewed as a whole and the input to the system are identified. System analysis is concerned
with becoming aware of the problem, identifying the relevant and decisional variables,
analyzing and synthesizing the various factors and determining an optimal or at least a
satisfactory solution or program of action.

A detailed study of the process must be made by various techniques like interviews,
questionnaires etc. which in terms helps to arrive to a conclusion on the basis of data collected
by these sources. The conclusion is an understanding of how the system functions. This
system is called the existing system. Now the existing system is subjected to close study and
problem areas are identified.

The designer now functions as a problem solver and tries to sort out the difficulties that
the enterprise faces. The solutions are given as proposals. The proposal is then weighed with
the existing system analytically and the best one is selected. The proposal is presented to the
user for an endorsement by the user.

The proposal is reviewed on user request and suitable changes are made. This is loop
that ends as soon as the user is satisfied with proposal. Preliminary study is the process of
gathering and interpreting facts, using the information for further studies on the system.
Preliminary study is problem solving activity that requires intensive communication between
the system users and system developers.

It does various feasibility studies. In these studies a rough figure of the system
activities can be obtained, from which the decision about the strategies to be followed for
effective system study and analysis can be taken.

Page | 5
Existing System of Doctor Appointment System:

In the existing system Appointments usually managed manually or on a few places where it is
managed by computer system, it is not very user friendly and reachable to users. But in
proposed system this difficulty can be overcome by user friendly, easy, cost efficient
management.

 Human power/resource required.

 Time consuming.
 Costly (To maintain records as well as Human power)
 Manual Management Required etc.

Proposed System of Doctor Appointment System:

The aim of proposed system is to develop a system of improved facilities with less human
efforts and long term management facility with less storage space and less cost. The proposed
system is designed accordingly so that it can overcome reasonably good amount of limitations
of the existing system. The system provides proper security and reduces the manual work.

 Security of data.
 Ensure data accuracy’s.
 Structural process.
 Minimize manual task.
 Minimum time needed for the various processing.
 Greater efficiency.
 Better service.
 User friendliness and interactive.
 Minimum time required.

Page | 6
Software Analysis:

The Software Analysis is produced at the culmination of the analysis task.

The function and performance allocated to software as part of system engineering are
refined by establishing a complete information description, a detailed functional and
behavioral description, an indication of performance requirements and design constraints,
appropriate validation criteria, and other data pertinent to requirements.

The proposed system has the following requirements:

 System needs store information about new entry of Doctor.

 System needs to help the internal staff to keep information of Appointment and find
them as per various queries.
 System need to maintain quantity record.
 System need to keep the record of Patient.
 System need to update and delete the record.
 It also needs a security system to prevent data theft.

Page | 7
Data Dictionary

This is normally represented as the data about data. It is also termed as metadata some
times which gives the data about the data stored in the database. It defines each data term
encountered during the analysis and design of a new system. Data elements can describe files
or the processes.

User:

Field Data Type Size Constraints

user_id int 11 Primary Key
user_level_id int 11 -
user_username varchar 255 -
user_password varchar 255 -
user_name varchar 255 -
user_add1 varchar 255 -
user_add2 varchar 255 -
user_city int 11 -
user_state int 11 -
user_country int 11 -
user_email varchar 255 -
user_mobile varchar 255 -
user_gender varchar 255 -
user_dob varchar 255 -
user_image varchar 255 -

Appointment:

Field Data Type Size Constraints

appointment_id int 11 Primary Key
appointment_patient_id varchar 255 -
appointment_doctor_id varchar 255 -
appointment_timeslot_id varchar 255 -
appointment_date varchar 255 -
appointment_fees varchar 255 -
appointment_contact varchar 255 -
appointment_address varchar 255 -
appointment_status varchar 255 -
appointment_description text - -

Page | 8
Appointment Status:

Field Data Type Size Constraints

as_id int 11 Primary Key
as_title varchar 255 -
as_description text - -

Appointment Time Slot:

Field Data Type Size Constraints

timeslot_id int 11 Primary Key
timeslot_name varchar 255 -
timeslot_description varchar 255 -

User Authentication:

Field Data Type Size Constraints

Id Int 11 Primary Key
password Varchar 128 -
last_login Datetime - -
is_superuser Tinyint 1 -
Username Varchar 150 Index
first_name Varchar 30 -
last_name Varchar 30 -
Email Varchar 250 -
is_staff Tinyint 1 -
is_active Tinyint 1 -
date_joined Datetime - -

Page | 9
Data Flow Diagram

Data flow diagram is the starting point of the design phase that functionally
decomposes the requirements specification. A DFD consists of a series of bubbles joined by
lines. The bubbles represent data transformation and the lines represent data flows in the
system. A DFD describes what data flow rather than how they are processed, so it does not
hardware, software and data structure.

A data-flow diagram (DFD) is a graphical representation of the "flow" of data through

an information system. DFDs can also be used for the visualization of data processing
(structured design).

A data flow diagram (DFD) is a significant modeling technique for analyzing and
constructing information processes. DFD literally means an illustration that explains the
course or movement of information in a process. DFD illustrates this flow of information in a
process based on the inputs and outputs. A DFD can be referred to as a Process Model.

There are seven rules for construct a data flow diagram.

 Arrows should not cross each other.

 Squares, circles and files must wears names.
 Decomposed data flows must be balanced.
 No two data flows, squares or circles can be the same names.
 Draw all data flows around the outside of the diagram.
 Choose meaningful names for data flows, processes & data stores.
 Control information such as record units, password and validation requirements are not
penitent to a data flow diagram.

Additionally, a DFD can be utilized to visualize data processing or a structured design.

This basic DFD can be then disintegrated to a lower level diagram demonstrating
smaller steps exhibiting details of the system that is being modeled.

On a DFD, data items flow from an external data source or an internal data store to an
internal data store or an external data sink, via an internal process.

It is common practice to draw a context-level data flow diagram first, which shows the
interaction between the system and external agents, which act as data sources and data sinks.
On the context diagram (also known as the Level 0 DFD’), the system's interactions with the
outside world are modeled purely in terms of data flows across the system boundary.

Page | 10
 The context diagram shows the entire system as a single process, and gives no clues as
to its internal organization.

This context-level DFD is next "exploded", to produce a Level 1 DFD that shows some
of the detail of the system being modeled. The Level 1 DFD shows how the system is divided
into sub-systems (processes), each of which deals with one or more of the data flows to or
from an external agent, and which together provide all of the functionality of the system as a
whole.

The level 1 DFD is further spread and split into more descriptive and detailed
description about the project as level 2 DFD. The level 2 DFD can be a number of data flows
which will finally show the entire description of the software project.

Zero Level Data Flow Diagram

Page | 11
 First Level Data Flow Diagram

Page | 12
 Second Level Data Flow Diagram

Page | 13
Entity Relationship Diagrams

E-R Model is a popular high level conceptual data model. This model and its variations
are frequently used for the conceptual design of database application and many database
design tools employ its concept.

A database that confirms to an E-R diagram can be represented by a collection of

tables in the relational system. The mapping of E-R diagram to the entities are:

 Attributes
 Relations
o Many-to-many
o Many-to-one
o One-to-many
o One-to-one
 Weak entities
 Sub-type and super-type

The entities and their relationships between them are shown using the following
conventions.

 An entity is shown in rectangle.

 A diamond represents the relationship among number of entities.
 The attributes shown as ovals are connected to the entities or relationship by lines.
 Diamond, oval and relationships are labeled.
 Model is an abstraction process that hides super details while highlighting details
relation to application at end.
 A data model is a mechanism that provides this abstraction for database application.
 Data modeling is used for representing entities and their relationship in the database.
 Entities are the basic units used in modeling database entities can have concrete
existence or constitute ideas or concepts.
 Entity type or entity set is a group of similar objects concern to an organization for
which it maintain data,
 Properties are characteristics of an entity also called as attributes.
 A key is a single attribute or combination of 2 or more attributes of an entity set is used
to identify one or more instances of the set.

Page | 14
 In relational model we represent the entity by a relation and use tuples to represent an
instance of the entity.
 Relationship is used in data modeling to represent in association between an entity set.
 An association between two attributes indicates that the values of the associated
attributes are independent.

Page | 15
 Entity Relationship Diagram

Page | 16
 Logical and Physical Design of System

Database Design

Doctor Appointment System helps by simplifying the entire process.

Database design is the process of producing a detailed data model of a database. This
data model contains all the needed logical and physical design choices and physical storage
parameters etc.

Database Design is a collection of processes that facilitate the designing, development,

implementation and maintenance of enterprise data management systems.

The term database design can be used to describe many different parts of the design of
an overall database system.

Principally, and most correctly, it can be thought of as the logical design of the base
data structures used to store the data.

In the relational model these are the tables and views. In an object database the entities
and relationships map directly to object classes and named relationships.

Page | 17
 Database Design

Page | 18
Layout/Snapshot
Home Page

Page | 19
About Us

Page | 20
Contact Us

Page | 21
Login

Page | 22
Admin- Add New User

Page | 23
Admin-Add New Appointment

Page | 24
Admin-Doctor Report

Page | 25
Admin-Patient Report

Page | 26
Admin-Appointment Report

Page | 27
Sub System Design

During sub-system development, the sub-systems identified are implemented. This

may involve starting another system engineering process for individual sub-systems or, if the
sub-system is software, a software process involving requirements, design, implement and
testing.

Usually all sub-systems of the system are designed and developed during the development
process.

Doctor Appointment System

Add New User Doctor Report

Add New Appointment Patient Report

My Account (Edit/View) Appointment Report

Page | 28
 Database / Data Security Model

Database/Data security concerns the use of a broad range of information security

controls to protect databases (potentially including the data, the database applications or stored
functions, the database systems, the database servers and the associated network links) against
compromises of their confidentiality, integrity etc.

It refers to the collective measures used to protect and secure a database or database
management software from illegitimate use and malicious threats and attacks.

Security risks to database systems include, for example:

 Unauthorized or unintended activity or misuse by authorized database users, database

administrators, or network/systems managers, or by unauthorized users or hackers (e.g.
inappropriate access to sensitive data, metadata or functions within databases, or
inappropriate changes to the database programs, structures or security configurations);
 Malware infections causing incidents such as unauthorized access, leakage or
disclosure of personal or proprietary data, deletion of or damage to the data or
programs, interruption or denial of authorized access to the database, attacks on other
systems and the unanticipated failure of database services;
 Overloads, performance constraints and capacity issues resulting in the inability of
authorized users to use databases as intended.
 Design flaws and programming bugs in databases and the associated programs and
systems, creating various security vulnerabilities (e.g. unauthorized privilege
escalation), data loss/corruption, performance degradation etc.
 Data corruption and/or loss caused by the entry of invalid data or commands, mistakes
in database or system administration processes, sabotage/criminal damage etc.

Page | 29
 To achieve the security of Database in this system, some of the following approaches
used:

 Using Post Method to hide data

 Password Controls
 Data access based on roles and profiles
 Ensuring that data has been edited by an authorized source by password restriction
 Auditing capabilities of who has run what reports
 Security logging

Page | 30
 Test Case
Test Case ID DAS_01 Test Login Functionality in Doctor Appointment System
Description
Phalguni
Created By Reviewed By Phalguni Pathak
Pathak

Test Case
Phalguni
Tester's Name Date Tested 5-Apr-2018 (Pass/Fail/Not Pass
Pathak
Executed)

S. No. Prerequisites: S# Test Data

1 Access to Chrome Browser/IE/Firefox 1 User ID=admin

2 2 Pass=test

Test
Verify on entering valid user id and password, the user can login
Scenario

Pass / Fail / Not

Step # Step Details Expected Results Actual Results
executed / Suspended

1 Navigate to 127.0.0.1:8000 Site should open As expected Pass

2 Enter User id and Password Wait till click submit As expected Pass

3 Click Submit User Logged in As expected Pass

System Testing and Implementation

Page | 31
Test Case Design

Test cases for software help guide the tester through a sequence of steps to validate
whether a software application is free of bugs and working as required by the end user.

Check User Login:

Check Add New User:

Test Case Test Add User Functionality in Doctor Appointment

Test Case ID DAS_02
Description System
Phalguni
Created By Reviewed By Phalguni Pathak
Pathak

Test Case
Phalguni
Tester's Name Date Tested 5-Apr-2018 (Pass/Fail/Not Pass
Pathak
Executed)

S. No. Prerequisites: S# Test Data

1 Access to Chrome Browser/IE/Firefox 1 User ID=admin

2 2 Pass=test

Test
Verify on entering valid user details, the user added.
Scenario

Page | 32
 Pass / Fail /
Step # Step Details Expected Results Actual Results Not executed
/ Suspended

1 Navigate to 127.0.0.1:8000 Site should open As expected Pass

2 Enter User id and Password User Logged in As expected Pass

3 Go to Administration->Add User Add User Form Open As expected Pass

4 Fill Valid Details then Submit User Added As expected Pass

Check Add New Appointment:

Test Case Test Add Appointment Functionality in Doctor Appointment

Test Case ID DAS_03
Description System
Phalguni
Created By Reviewed By Phalguni Pathak
Pathak

Page | 33
 Test Case
Phalguni
Tester's Name Date Tested 5-Apr-2018 (Pass/Fail/Not Pass
Pathak
Executed)

S. No. Prerequisites: S# Test Data

1 Access to Chrome Browser/IE/Firefox 1 User ID=admin

2 2 Pass=test

Test
Verify on entering valid details, appointment added.
Scenario

Pass / Fail /
Step # Step Details Expected Results Actual Results Not executed /
Suspended

1 Navigate to 127.0.0.1:8000 Site should open As expected Pass

2 Enter User id and Password User Logged in As expected Pass

Go to Administration->Add Add Appointment
3 As expected Pass
Appointment Form Open
4 Fill Valid Details then Submit Appointment Added As expected Pass

Check Report:

Page | 34
 Test Case
Test Case ID DAS_04 Check Report/Records in Doctor Appointment System
Description
Phalguni
Created By Reviewed By Phalguni Pathak
Pathak

Test Case
Phalguni
Tester's Name Date Tested 5-Apr-2018 (Pass/Fail/Not Pass
Pathak
Executed)

S. No. Prerequisites: S# Test Data

1 Access to Chrome Browser/IE/Firefox 1 User ID=admin

2 2 Pass=test

Test
Verify on entering valid user details, the manage reports.
Scenario

Pass / Fail /
Step # Step Details Expected Results Actual Results Not executed /
Suspended

1 Navigate to 127.0.0.1:8000 Site should open As expected Pass

2 Enter User id and Password User Logged in As expected Pass

Go to Report-
3 Open Desired Report As expected Pass
>Admin/Doctor/Patient
4 Edit/View/Update Report Done As expected Pass

Black Box Testing

Page | 35
 This method enables the software engineer to device sets of input techniques that fully
exercise all functional requirements for a program. black box testing tests the input, the output
and the external data. it checks whether the input data is correct and whether we are getting the
desired output.

White Box Testing

In this technique, the close examination of the logical parts through the software is
tested by cases that exercise species sets of conditions or loops. all logical parts of the
software checked once. Errors that can be corrected using this technique are typographical
errors, logical expressions which should be executed once may be getting executed more than
once and error resulting by using wrong controls and loops.

When the box testing tests all the independent part within a module a logical decisions
on their true and the false side are exercised , all loops and bounds within their operational
bounds were exercised and internal data structure to ensure their validity were exercised once.

Test execution:

(a) Unit Testing

Each module is considered independently. it focuses on each unit of software as

implemented in the source code. it is white box testing.

(b) Integration Testing

Integration testing aims at constructing the program structure while at the same
constructing tests to uncover errors associated with interfacing the modules. modules are
integrated by using the top down approach.

(c) Validation Testing

Validation testing was performed to ensure that all the functional and performance
requirements are met.

(d) System Testing

Page | 36
 It is executing programs to check logical changes made in it with intention of finding
errors. A system is tested for response, volume of transaction, recovery from failure etc.
System testing is done to ensure that the system satisfies all the user requirements.

Conclusion

Page | 37
 This project is only an attempt to satisfy the needs of Hospital in managing Doctor’s
Appointment, by changing manual things with the help of well organized system.

The approach is opted user friendly in both phases, coding and front-end/interactive
panel for user. Doctor Appointment System provides safety and security of data as well as
time saving facility.

This system shall prove to be a powerful enough in satisfying the doctor appointment
scheduling requirements of the hospital.

The objective of software planning is to provide a frame work that enables the manger
to make reasonable estimates made within a limited time frame at the beginning of the
software project and should be updated regularly as the project progresses.

Future Scope

This field has a vast scope of growth and additions. Medical/Health is an area which
affects every human, so there is high possibility for the system. Some of them:

 Make this system automated (allow manual tasks to done by machine with precision
and less time consumption).
 Medical facility in everyone’s reach (internet can be very helpful for that)
 Improve existing system (reduce complexity)
 Make medical facility easy to acquire
 Easy to manage system, so a commoner (with no technical knowledge) can also
operate it and many more.

The above mentioned points are the enhancements which can be done to increase the
applicability and usage of this project. Here we can maintain the records of Doctor and
Appointment. Also, enhancements can be done to maintain all the Doctor, Appointment,
Patient, Booking, Doctor Schedule etc.

I hope that the project will serve its purpose for which it is develop there by
underlining success of process.

Limitations

Page | 38
 Although I have put my best efforts to make the software flexible, easy to operate but
limitations cannot be ruled out even by me. Like Excel export has not been developed for
Doctor, Appointment and patients, due to some criticality and some more.

The proposed system is an attempt to overcome all the limitations of the existing
system. But that will be possible only with continuous progress, attempts and growth in terms
of replacing, all the manual and difficult to manage task, with system (computer) based full
fledge software and applications.

Although with some extensive time and more efforts maximum limitations can be
overcome.

Page | 39