1. Existing System 2. Proposed System 3. Objective 4. SDLC 4.1. Project planning 4.2. Project Analysis 4.3. Project Development 4.4. Project Design 4.5. Implementation 4.6. Testing 4.7. System Maintenance 5. Project Schedule 6. Feasibility 6.1. Economic feasibility 6.2. Technical feasibility 6.3. Operational feasibility 6.4. Schedule feasibility 7. Context Diagram 7.1. Context diagram of the system 7.2. DFD 0 7.3. DFD 1 For Patient 7.4. DFD 1 For Doctor 7.5. DFD 2 For Patient 8. Gantt Chart 9. Use Case Diagram 10. Conclusion 11. Advantages 12. Limitation 13. Future Plan

1. ONLINE DOCTOR APPOINTMENT SYSTEM
1
SAD PROJECT
FALL SEMSETER 2019
GROUP MEMBERS
1. StudentName
2. StudentName
3. StudentName
SUBMITTED TO Teacher Name

2. ONLINE DOCTOR APPOINTMENT SYSTEM
2
Acknowledge
My sincere gratitude to my Supervisor Ms. Saira Arbab for guiding us throughout the
planning and development phase of the system. Without his strategic guideline and
counselling. I would not have reached the final stage of the development. Ms. Saira
Arbab’s sincere guidance and always cooperating nature has provided us with proper
knowledge and directions on how to prepare for the final documentation. I would like to
thank my close peers and my classmates for being supportive and encouraging
throughout my four-month journey. Finally, yet importantly, I would like to thank my
family. Their endless support has been unconditional. Their hopes and faith on me had
me keep going even when days were challenging.

3. ONLINE DOCTOR APPOINTMENT SYSTEM
3
ABSTRACT
The project entitled as “Automated Doctor Appointment and Doctor Help Management System”
is a webbased application. Itmaintains records of patient, doctor,appointment and schedule that
occur at any of the medical center. It maintains two levels of users, administrator level and user
level. User level is divided into two, patient level and the doctor level. The administrator level
encompasses the hospital staffs, whomaintain the appointment records. The user level includes
the patients, who take service from the hospital, and the doctors. The administrators are able to
perform operations on more sensitive and confidential documents /modules that contain
different information about doctors and patient to ensure confidentiality. System enables
registration of new patient at the user level. Doctors are registered by hospital staff. From the
accountof user as patient, one cantake appointment of a doctor; can see doctor details and all his
appointment date and time. Another extra facility one will get is that, he can send message to a
doctor about his sickness if he agrees prior and doctor can also reply it. The current system is
taking appointment of a doctor by phone call or taking serial directly from the hospital. The
proposed system has the following capabilities maintaining patient’s records, registering new
patients, records of appointments and easy future references. Users and administrators can
search records more easily. The project has been developed in back-end: PHP,MySQL and front-
end: HTML, CSS, and JavaScript. The main motto of my project is to facilitate the people to take
appointment easily, find doctors available schedule. It is also helpful for doctors to mange his
schedule and appointments easily.

4. ONLINE DOCTOR APPOINTMENT SYSTEM
4
TABLE CONTENTS
TITLE
ACKNOELEDGEMENT i
ABSTRACT ii
LIST OF TABLE iii
LIST OF TABLE
TOPICS
1. ExistingSystem 1
2. ProposedSystem 1
3. Objective 1
4. SDLC 2
4.1. Projectplanning 2
4.2. ProjectAnalysis 3
4.3. ProjectDevelopment 3
4.4. ProjectDesign 3
4.5. Implementation 4
4.6. Testing 4
4.7. SystemMaintenance 4
5. ProjectSchedule 5
6. Feasibility 5
6.1. Economicfeasibility 5
6.2. Technical feasibility 6
6.3. Operational feasibility 6
6.4. Schedule feasibility 6
7. ContextDiagram 7
7.1. Contextdiagramof the system 7
7.2. DFD 0 8
7.3. DFD 1 For Patient 9
7.4. DFD 1 For Doctor 10
7.5. DFD 2 For Patient 11
8. Gantt Chart 11
9. Use Case Diagram 12
10. Conclusion 12
11. Advantages 13
12. Limitation 13
13. Future Plan 13

5. ONLINE DOCTOR APPOINTMENT SYSTEM
5
EXISTING SYSTEM
Under manual Online Doctor System, you have to first wait in line to take
appointment for the doctors and wait for your time to have meet with them and discuss
on your health problems. As you have to provide your information and other reports
many times at different places such as the medicine store which is again a burden of
carryingdocuments. Youhaveto bepresentphysically at the doctor’scabin.Patients have
to visit on another day of after some hours to take their health reports which involves
extra care person with patients anytime. Under manual system, the only accepted
payment method is by cash and if patients due to some reasons are not having cash on
time may face difficulties and not able to get treatment.
PROPOSED SYSTEM
To make a truly Online Doctor System system to have meet with online
doctors, all manual process has been automated through this system. Patient have to fill
online form by which id and password created and sanded to their email and upon
accepting data, automatic login to patient panel. Through this panel, patients can select
the doctorsand haveappointment with them on their time fromtheir own place. Patients
will get all their reports and medicine prescriptions in their inbox by notification
indication just after appointment session. There is no need of cash and a secure payment
gateway hasbeenused to pay the requiredfeesusingtheir accountordebit orcredit card.
OBJECTIVE
Objectives of the Project Our modern age of technology is greatly depends on
internet. Everything is convertedto computer basedforeasierandfaster communication.
Here I tried to develop such a system, which will ensure some aspects,
 Reliability, maintainability, cost-effectiveness and a nice user-friendly
environment.
 The objective of the project is to provide an opportunity of getting doctor
appointment easily.
 Proper management of appointments, securely stores all records.
 Save money and time.

6. ONLINE DOCTOR APPOINTMENT SYSTEM
6
SDLC PHASES
PROJECT PLANNING
Proper project management is essential for the successful completion of a
software project. Software project management (responsible for project planning)
specifies activities necessary to complete the project. After this a project schedule is
prepared to accomplish the specified tasks. The purpose of planning and scheduling is to
develop the software according to the user requirements within the allocated time and
budget. Projectplanning partofproject management, which relatesto the useof schedule
such as Gantt charts to plan and subsequently report progress within the project
environment.
 Select project
 Identifying project’s aims & objectives.
 Understanding requirements & specification
 Methods of analysis, design & implementation

7. ONLINE DOCTOR APPOINTMENT SYSTEM
7
 Testing techniques
 Documentation
 Budget allocation
 Project Estimation & deliverables
 Resources Allocation
 Risk Management
PROJECT ANALYSIS
Describes the risks that can possibly arise during software developments
well as explains how to assess and reduce the effect of risks. The major risks involved in
the software development process was to locate blood banks in different places, provide
adequate knowledge among blood banks and people about blood donation. If no blood
bank is registered in the system registered users are not able to use the app properly. To
reduce the risks in software the system should be available in all blood banks and among
common people.
SYSTEM REQUIREMENTS
System needs store information about new entry of Doctor.
System needs to help the internal staff to keep information of Appointment
& find them as per various quarries. System need to maintain quantity record.
 System need to keep the record of Patient.
 System need to update & delete the record.
 System also needs a search area.
 It also needs a security system to prevent data.
SYSTEM DEVELOPMENT
In system specification I first focus is ERD (Entity Relationship Diagram),
which shows entity with their attributes, relationship with entities involving one-one, one-
many, many-one or many many. Data flow diagram, use case diagram, activity diagram,
sequence diagram are also designed to understand the system clearly and completely
SYSTEM DESIGN
Systems design is the process of defining the architecture, components, modules,
interfaces, and data for a system to satisfy specified requirements. It helps in specifying
hardware and system requirements and also helps in defining overall system architecture. The
system design specifications serve as input for the next phase of the model. It includes interface
design, data design, and process design. In user interface design I concerned with how users
interact with the system, add information to the system. And how the system will presents
information back to the users. In data design it concerned with how the data is represented and
stored within the system. Finally, Process Design is concerned with how data moves through
the system. I show this in DFD

8. ONLINE DOCTOR APPOINTMENT SYSTEM
8
IMPLEMENTATION
A software product implementation method is a systematically structured approach to
effectively integrate software based service or component into the workflow of an
organizational structure or an individual end-user. The implementation of product software, as
the final link in the deployment chain of software production, is in a financial perspective of a
major issue. The software can be able to access through the internet. I used to implement the
software using given below:
 PHP
 HTML
 JAVA SCRIPT
 MySQL
 Ajax
SYSTEM TESTING
For the sake of software quality assurance, system testing is a very
essential thing to do. It is a process by which we try to make the system error proof by
performing the program to find an error. The goal is to run the program, find errors or
bugs and then fix them. Testing is considered a very essential step in software
development and any system is not considered to be complete without this process.
Different developers follow different approaches for system testing. System testing is
followed to make sure that system is working fine and meets the requirements.
The steps involved during Unit testing are as follows:
 Preparation of the test cases.
 Preparation of the possible test data with all the validation checks.
 Complete code review of the module.
 Actual testing done manually.
 Modifications done for the errors found during testing.
 Prepared the test result scripts.

9. ONLINE DOCTOR APPOINTMENT SYSTEM
9
SYSTEM MAINTENANCE
Maintenance is really evolutionary development and that maintenance
decisions are aided by understanding what happens to systems (and software) over
time. A software system may evolve over time. As it evolves, it grows more complex.
Quite a number of actions such as code refactoring are taken to decrease the complexity.
Software maintenance in software engineering is the improvement
regarding a software product after delivery in order to repair system defects. To
enhance overall performance or other quality of the software it is very much important.
A typical perception of maintenance may be that it mainly involves repairing defects.
However, one research revealed that the majority, over 80%, of the maintenance
attempt is used for non-corrective actions. This perception is perpetuated by users
submitting problem reports that in reality are overall performance enhancements to the
system. The maintenance phase of software development has exposed immense costs,
generally it exceed the development cost. Moreover, in many cases the maintenance
data include the cost of rewriting, testing, debugging and incorporating new features
into the software. Such cost is known as modification costs.
Project Schedule
Specifies the dependencies of activities on each other. Based on this, the time
required by the project management team members to complete the project activities is
estimated. Only if the web services are developed mobile application will be able to run.
The database including tables are to be created in the beginning itself for the proper
functioning of the system. If the designing phase is completed in a small amount of time
then the total work time can be estimated.
FEASIBILITY STUDY
After doing the project Doctor Appointment System, study & 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 & infinite time.
Feasibility study includes consideration of all the possible ways to provide a
solution to provide a solution to the given problem. The proposed solution should
satisfy all the user requirements & should be flexible enough so that future changes can
be easily done based on the future upcoming requirements.
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 & software cost has to be biome by the organization.

10. ONLINE DOCTOR APPOINTMENT SYSTEM
10
Overall we have estimated that the benefits the organization is going to receive from the
proposed system will surely overcome the initial costs & the later on running cost for
system.
TECHNICAL FEASIBILITY
This is included the study of function, performance 7 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
requirements specification(SRS), & checked if everything was possible using different
type of frontend & backend platforms.
OPERATIONAL FEASIBILITY
No doubt the proposed system is fully GUI based that is very user friendly
& 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 connected the clients are comfortable
& happy as the system has cut down their loads & doing.
SCHEDULE FEASIBILITY
A project will fail if it takes too long to be completed before it is useful. Typically,
this means estimating how long the system will take to develop, and if it can be
completed in a given time period using some methods like payback period. Schedule
feasibility is a measure of how reasonable the project timetable is. Based on given
information the system will perform given tasks. Planning a project strategy and
building a project schedule to
 Complete project within time and budget.
 Resource management system.
 Increase team productivity.
 Increase project success rate.
 Realize significant time and resource savings.
I tried to complete the software within time limit. And almost I can do it. The proposed
system will easily be accessible and it will be well organized and delivered the right
information in the right place.
CONTEXT DIAGRAM
In figure it shows the context diagram of the system. Here three types of users
interact with the system patient, doctor and admin. Patient can request for
appointment. Doctor can see all of his appointments. And admin can supervise all the
activities.

11. ONLINE DOCTOR APPOINTMENT SYSTEM
11
CONTEXT DIAGRAM
Context diagram for the system

12. ONLINE DOCTOR APPOINTMENT SYSTEM
12
DFD 0
Context diagram DED 0

13. ONLINE DOCTOR APPOINTMENT SYSTEM
13
DFD 1 DOR PATIENT
Context diagram for the patient DED 1

14. ONLINE DOCTOR APPOINTMENT SYSTEM
14
DFD 1 DOR DOCYOR
Context diagram for Doctor DFD 1

15. ONLINE DOCTOR APPOINTMENT SYSTEM
15
DFD 2 DOR PATIENT
Context diagram for the patient DED 2
GANTT CHART
One of the oldest and still one of the most useful of presenting schedule
information is the Gantt chart. Gantt chart is a pioneer in the field of scientific
management. The Gantt chart show planned and actual progress for a number of tasks
displayed against horizontal time scale. In figure horizontal bars indicate time duration.
In figure it shows there are eight tasks and their time duration, start time and end time.
0 10 20 30 40 50 60 70
Specification
Design data base
Design GUI
Write User
Code data base
Code GUI
Integrate & test
Implementation
1
4
7
10
14
17
30
36
DURATION
TASKS
GANTT CHART

16. ONLINE DOCTOR APPOINTMENT SYSTEM
16
USE CASE DIAGRAM
Use case diagram (UCD) is a methodology used to describe the functionality of a
system in a horizontal way. Each use case focuses on describing how to achieve a goal or
task. The use case is made up of a set of possible sequences of interactions between
system and users or actor in a particular environment and related to a particular goal.
The user or actor might be a person or something more abstract, such as an external
software system or manual process.
Use case diagram of the system
CONCLUSION
After finishing up my project I have to state that, I tried my best in order
to develop the software in the most suitable, helpful and easiest method that can be
used by the user easily. Users can easily pick up their expected information based upon
their privilege. This is web based software and it will be going to accessible from any
computer by using internet. I have tested the system using several techniques to
determine the system flexibility. I tried to develop automated doctor appointment and
doctor help management system software which recovers as possible the drawbacks

17. ONLINE DOCTOR APPOINTMENT SYSTEM
17
and limitations compared to this types of existing software’s as well as for efficient use
for users. It will save money, time and energy to appoint a doctor. Provide safety and
security to data enable the system administrator to authenticate all of the users through
user names and password so that unauthorized users do not get access to the hospitals
data.
Advantages of the system
User of this system can be benefited by using the software in the following ways:
 It is a web based software and very easy to use.
 It will save user time and money as they need not to go to hospital or phone call.
 Patients can contact with doctor at any time.
 Update and modification of user profile is very much easy.
 Doctor, patient and admin all have to login by using username and password to
access their information.
 Doctor can see all of his appointments prior any time.
 Doctor can change or modify his time and schedule any time.
Limitation of the system
There are some limitations of the system. They are,
 System security cannot be done completely.
 Payment system is not completely secure.
 It is not fully automated.
 Admin have to delete unnecessary accounts manually.
Future Plan
Future plans are,
 Make the system fully automated.
 Implement security system for the project.
 Make the system more flexible for payment and other transaction.
 Develop mobile apps for the system.