You are on page 1of 80

A

Project Report
On
Life Care
Submitted in the Partial Fulfillment of the Requirement
for the Award of Degree of
Master of Computer Applications
(Session: 2018-2020)

Supervised By: Submitted By:


Dr. Rajender Nath Rahul
Professor Class Roll No. 154
Univ Roll No.6465527

Department of Computer Science & Applications


Kurukshetra University, Kurukshetra-136119
Declaration
I, Rahul, student of Master of Computer Applications (MCA), VI semester
in the Department of Computer Science & Applications, Kurukshetra
University, Kurukshetra, under class Roll No. 154, for the Session 2018-
2020, hereby, declare that the project entitled “Life Care” has been
completed by me at Appworx IT Solutions Private Limited, Netsmartz
House, Plot No - 10, Chandigarh After the theory examination of V
semester.

The matter embodied in this project work has not been submitted earlier for
award of any degree or diploma to the best of my knowledge and belief.

Date: 22-07-2020 (Rahul)

i
Department of Computer Science & Applications
Kurukshetra University, Kurukshetra

Dr. Rajender Nath

(Professor)

Certificate

It is certified that Mr. Rahul, a student of Master of Computer Applications


(MCA), under class Roll No.154 for the session 2018-2020, has completed
the project entitled “Life Care” undertaken at Appworx IT Solutions under
my supervision. He has attended the Department of Computer Science &
Applications, Kurukshetra University, Kurukshetra and Appworx IT
Solutions for required number of days after the theory examination of Vth
semester.

I wish him all success in his all endeavors.

Dr. Rajender Nath

ii
Department of Computer Science & Applications
Kurukshetra University, Kurukshetra

Dr. Rajender Nath Date: 22-07-2020


(Professor & Chairman)

Certificate

It is certified that Mr. Rahul, a student of Master of Computer Applications


(MCA), under class Roll No.154. He has undertaken the project entitled
“Life Care” at Appworx IT Solutions under the supervision of Dr. Rajender
Nath.

I wish him all success in his all endeavors.

Dr. Rajender Nath

iii
Company Certificate

TO WHOM IT MAY CONCERN

This is to certify that Mr. Rahul Baniwal a student of Department of Computer Science
and Application, Kurukshetra University is under training/Internship from 28th January
2020 to 30th July 2020. During this Training/Internship, he is working under the guidance
of Ms. Seema Chauhan. His overall performance during the training/internship period is
Excellent. Other details related to his training are as below:

i. Name of the Organization: Appworx IT Solutions Pvt. Ltd.


ii. Place of work: Chandigarh
iii. Address of the Employer: Plot No. 10, 4th Floor, Rajiv Gandhi IT Park,
Chandigarh, 160101

Name : Deepti

Designation : Centre Manager

Appworx IT Solutions Pvt Ltd., Corporate and Reg. Office Address: Netsmartz House, Plot No 10, I.T. Park,
Chandigarh-160101, India Phone No: 91-172-5055200, Website: www.appworx.in,

iv
Acknowledgement
It gives me immense pleasure to the implied help I received while developing this project
at its various stages. It would not have been possible without the contribution and great
deal of encouragement on parts of numerous individuals.

I express profound gratitude to Dr. Rajender Nath my project guide for his guidance,
motivation and assistance throughout the project.

Expressing my sincere and heartfelt gratitude to Mrs. Seema Chauhan (Team Leader) for
his valuable guidance and encouragement, who look from interest on my project work
and guided me all along till the completion of my project by providing me all the
necessary information for developing a good system. His prompt inspirations, timely
suggestion with kindness, enthusiasm and dynamism have enabled me to complete the
project successfully.

I would also like to thank all the other people who were directly or indirectly involved in
the success of the project.

Finally, I would like to thank my family for their love and continuous encouragement
during the entire duration of the project.

(Rahul)

v
List of Figures

Figure no. Name of figure Page no.


1.4.1 SDLC Phases………………………………... 3
4.3.1 DFD Notation Diagram………………….….. 23
4.3.2 DFD Level 0 Diagram…….………………… 24
4.3.3 DFD Level 1Diagram…………..…………… 25
4.4.1 ER Diagram…………………………………. 27
5.1.1 Screenshot For Homepage…………………... 29
5.1.2 Screenshot For Admin Login…….………….. 30
5.2.1.1 Admin Module………………………………. 30
5.2.1.2 Appointment Booking …………..…………... 45
5.2.2.1 Doctor Module………………………………. 46
5.2.2.2 Doctor Login………………………………… 46
5.2.2.3 Screenshot For Doctor Login ………………. 49
5.2.3.1 Appointment Book Module…………………. 50
5.2.3.2 Appointment Module Screenshot…………… 50
5.2.4.1 Patient Login Screenshot……………………. 52
5.2.4.2 Patient Module………………………………. 52
5.2.4.3 Patient Module Screenshot………………….. 60
5.2.4.4 Blogs Screenshot…………………………….. 60
6.3.1 Testing Hierarchy……………………………. 64

vi
List of Tables

Table no. Name of table Page no.


3.1.1 Hardware specification………………... 12
3.2.1 Software specification………………… 13
4.2.1 Patient…………………………………. 19
4.2.2 Blogspot……………………………….. 19
4.2.3 Doctor_list……………………………... 20
4.2.4 Appointment…………………………... 20
4.2.5 Prescription……………………………. 21
4.2.6 Tbl_logindetails……………………….. 21
4.2.7 Tbl_feedback…………………………... 22
4.2.8 Clinics…………………………………. 22
6.4.1.1 Login form…………………………….. 65
6.4.1.2 Appointment booking form……………. 65

vii
Index
Sr. no. Topic name Page no.
Declaration…………………………………………… i
Supervisor Certificate………………………………... ii
Chairperson Certificate………………………………. iii
Company Certificate…………………………………. iv
Acknowledgement…………………………………… v
List of Figures………………………………………... vi
List of Tables………………………………………… vii
1 INTRODUCTION…………………………………… 1-6
1.1 Introduction of the Project……………………... 1
1.1.1 Scope of the Project…………………….. 1
1.1.2 Technologies Used……………………... 2
1.2 Objectives of the Project………………………. 2
1.3 About the Company……………………………. 3
1.4 Methodology of the Developing of Project…… 4-5
1.5 Organization of the Project Report…………….. 6
2 SYSTEM ANALYSIS……………………………….. 7-11
2.1 Introduction…………………………………….. 7-9
2.1.1 Functional Requirements……………….. 7
2.1.2 System Objectives……………………… 9
2.2 Existing System………………………………... 9
2.3 Proposed System………………………………. 10
2.4 Feasibility Analysis……………………………. 10-11
3 REQUIREMENT SPECIFICATION………………... 12-16
3.1 Hardware Specification………………………… 12

viii
3.2 Software Specification…………………………. 13
3.3 Performance Specification……………………... 13
3.4 Tools And Language Specification……………. 14-16
3.4.1 Front End……………………………….. 14
3.4.2 Back End……………………………….. 16
4 SYSTEM DESIGN…………………………………... 17-28
4.1 Introduction…………………………………… 17-18
4.1.1 Input Design………………………….. 18
4.1.2 Output Design………………………… 18
4.2 Table Design…………………………………... 19-22
4.3 Data Flow Diagram…………………………… 23-25
4.4 ER Diagram…………………………………… 26-27
4.5 Summary………………………………………. 28
5 SYSTEM IMPLEMENTATION…………………….. 29-61
5.1 Coding & Screenshots………………………… 29-60
5.2 Module Description…………………………… 30
5.2.1 Admin Module………………………... 30
5.2.2 Appointment book Module …………... 46
5.2.3 Doctor Module………………………... 50
5.2.4 Patient Module………………………... 52
5.3 Summary………………………………………. 61
6 SYSTEM TESTING…………………………………. 62-67
6.1 Introduction…………………………………… 62
6.2 Testing Strategies……………………………... 63
6.3 Software Testing Hierarchy…………………… 64
6.4 Test Case For Life Care……………………….. 66

ix
6.4.1 Login Form…………………………... 66

6.4.2 Appointment Booking form………….. 66


7 CONCLUSION………………………………………. 67
7.1 Conclusion..…………………………………… 67
7.2 Future Scope…………………………………... 68
8 BIBLIOGRAPHY……………………………………. 69
8.1 Reference Books………………………………. 69
8.2 URLs………………………………………….. 69

x
CHAPTER 1: INTRODUCTION

1.1 Introduction of the Project


This website is basically for doctors and their patients. The users of the website will be
either doctors/medical groups or patients. Doctors can view their patients and take
consent from their patients online after giving them access. Doctor can also ask the
patients to submit a feedback after they review the procedure and before signing the
consent form online. The purpose of this document is to layout in detail the functional
and other requirements. This document contains the necessary information to meet the
requirements set forth for the completion of this application. The target audience of
this document is Stake holders, Project Managers, Developers, Designers, and QA
Engineers. Now onwards, this document will act as a portal of information during the
whole development cycle and any change in the functional or other requirements will
be communicated through this document.

Life Care is a project which aims in developing a computerized system to maintain all
the information of hospital entities. It has a facility of admin login through which the
admin can monitor the whole system. Admin modules are managing patients, manage
doctors, and manage appointments. Patient modules are find doctors and applied for
appointment, view appointment and view prescription. Doctor modules are view our
appointments, write prescriptions, and view patient details. Overall this project of ours
is being developed to help the hospital administration, maintain the hospital
management in the best way possible and also reduce the human efforts.

1.1.1 Scope of the Project


The project has a wide scope, as it is not intended to a particular organization. This
project is going to develop generic software, which can be applied by any businesses
organization. More over it provides facility to its users. Also the software is going to
provide a huge amount of summary data. This system can be enhanced by combining
several hospitals.

1
1.1.2 Technologies Used:
I had used many technologies in the development of Life Care portal such as PHP
MYSQL, database. Hyper Text Markup Language is very effective language to
develop the site. Our project is prepared in HTML. It is as popular as it can use any
text editor for coding purposes, and developing web pages is an easy task here. HTML
is the language interpreted by browsers. CSS stands for Cascading Style Sheet. It is
used to give designer look to HTML using the external file. JavaScript is powerful
client side scripting language which is mainly used for Validations. It is a Dynamic
programming language.

1.2 Objectives of the Project


The main objective of this project is to manage the records of patients, doctors and
appointments. Reduce the paper work and provide the 24/7 accessible website with
user-friendly GUI (Graphical User Interface) to manage the records.

Our objective is by using this website patient can search and view doctors profiles and
also apply for appointment. This website project is also become useful for doctors for
viewing patient’s details and write prescriptions to patients.

Project is discussed in this subchapter. The aims and objectives are as follows:

• The main objective of this project is to link and bring all major private medical
clinics of the city to a single platform. So that patients can easily get access to the
doctor's profile and make online appointments.

• The system allows doctors to manage their booking slots online. Patients are
allowed to book empty slots online and those slots are reserved in their name

• The system manages the appointment data for multiple doctors for various date
and times.

• Each time a user visits a doctor his/her medical entry is stored in the database by
doctor. Next time a user logs in he may view his/her entire medical history as and
when needed.

• The aim of the project is to create a platform where patients and doctors can

2
access/interact efficiently with each other and provides ease and comfort to the
patients.

1.3 About the Company

Appworx is a joint venture of Sebiz and WeExcel. The company was formed with the
mission to bridge the gap between antiquated college syllabi and the demands of a fast
changing IT environment. To make the workforce industry-ready, Appworx initiated
programs like Skill India Mission, Skill Malls and Technology Excellence Centers and
TISS. Appworx came in to existence as a social entrepreneurial initiative in skill
training, working largely in the underdeveloped regions of the country. The company
is committed towards providing young people with high quality vocational education
& skill training with relevant & recognized certifications that result in meaningful
employment and successful careers in the organized sector.

Company History:
Appworx IT Solutions Private Limited is a Non-govt company, incorporated on 06
Aug, 2012. It's a private unlisted company and is classified as'company limited by
shares'.Company's authorized capital stands at Rs 200.0 lakhs and has 62.926% paid-
up capital which is Rs 125.85 lakhs.Company is registered in Chandigarh
(Chandigarh) Registrar Office. Appworx IT Solutions Private Limited registered
address is Netsmartz House, Plot No. 10, Rajiv Gandhi Chandigarh Technology Park.

Goal:
To be a catalyst in enriching and empowering businesses through sustainable
technology in accordance with the highest professional standards continuously
challenging ourselves while maintaining team spirit, integrity and happiness.

The Company

Founded in 2012, Appworx, headquarter in Chandigarh, India. The activity is focused


on the following major activity likes: Web Development, Web Designing, Project
Management, Digital Marketing.

3
1.4 Methodology of the Development of Project

The Software Development Life Cycle (SDLC) provides a systematic process for
building and delivering software applications from inception to completion.

There are a number of different SDLC methodologies that can be used to deliver
projects. SDLC is a framework defining tasks performed at each step in the software
development process. The life cycle defines a methodology for improving the quality
of software and the overall development process.

The following figure is a graphical representation of the various stages of a typical


SDLC.

Figure 1.4.1 (SDLC Phases)

In the above figure, I have defined the steps used in designing the Life Care Software
Development Life Cycle consists of the following stages –

Stage 1Problem Statement and Planning


The purpose of this first stage is to find out the scope of the problem and determine
solutions. Resources, costs, benefits, time and other items should be considered here.

Stage 2 Defining Requirements

4
Once the requirement analysis is done the second step is to clearly define and
document the product requirements and get them approved from the customer or the
market analysts. This is done through an SRS (Software Requirement
Specification) document which consists of all the product requirements to be designed
and developed during the project life cycle.

Stage 3 Designing the System

The third stage describes, in detail, the necessary specifications, features and
operations that will satisfy the functional requirements of the proposed portal which
will be in place. A design approach clearly defines all the architectural modules of the
product along with its communication and data flow representation with the external
and third party modules (if any). The internal design of all the modules of the
proposed architecture should be clearly defined with the minutes of the details in DDS.

Stage 4 Building or Developing the Product

In this stage of SDLC the actual development starts and the portal is built. The
programming code is generated as per DDS during this stage. If the design is
performed in a detailed and organized manner, code generation can be accomplished
without much hassle.

Stage 5 Testing the Product


This stage is usually a subset of all the stages as in the modern SDLC models, the
testing activities are mostly involved in all the stages of SDLC. However, this stage
refers to the testing only stage of the product where product defects are reported,
tracked, fixed and retested, until the product reaches the quality standards in SRS.

Stage 6 Deployment and Maintenance

Once the portal is tested and ready to be deployed it is released formally in the
appropriate market. The last stage is when end users can fine tune the system to boost
performance and add new capabilities or meet additional user requirements.
Sometimes system deployment happens in stages as per the business strategy of that
organization.

5
1.5 Organization of the Project Report

As model of SDLC is selected to be followed for development of the software or the


portal serving purpose of Life Care, there are some phases defining purpose which
serves the effective development of Life Care. Organization is done in the following
chapters including chapter 1.

Chapter 2: System Analysis


Requirements analysis is the process which phase includes the identification of the
problem, in order to identify the problem,

Chapter 3: Requirement Specification


Requirements specification is the process of defining what the user requires from the
system and defining the requirements clearly and in an unambiguous state.

Chapter 4: System Design


Design is the first step into the development phase for any engineered product or
system. Design is a creative process. A good design is the key to effective system.

Chapter 5: System Implementation

Implementation is the carrying out, execution or practice of a plan, a method, or any


design, idea, model, specification, standard, or policy for doing something.

Chapter 6: Testing
Testing is used at key checkpoints in the overall process to determine whether
objectives are being met.

Chapter 7: Conclusion
A conclusion is the last part of something, its end or results. When we write a paper,
we always end by summing up your arguments and drawing a conclusion.

Chapter 8: Bibliography
Bibliography is a list of sources like books and URLs that are used in making of project.

6
CHAPTER 2: SYSTEM ANALYSIS

2.1 Introduction
In this chapter, we will discuss and analyze about the developing process of the project
entitled Life Care including software requirement specification (SRS) and comparison
between existing and proposed system. The functional and non functional requirements
are included in SRS part to provide complete description and overview of system
requirement before the developing process is carried out.

Besides that, existing versus proposed provides a view of how the proposed system will
be more efficient than the existing one.

2.1.1 Functional Requirements


Functional requirements specify which output should be produced from the given inputs.
They describe the relationship between the input and the output of the system. For each
functional requirement, the detailed description of all the data inputs and their source.
The unit of measure and range of valid inputs must be specified.

All the operations to be performed on the input data to obtain the output should be
specified. This includes specifying the validity check on output and output data,
parameters affected by the operations and the equations or the other logical operations
that must be used to transform the inputs into corresponding outputs. The functions must
be clearly said what the system should do in abnormal situations like invalid input or
error during computation.

We will focus on the following set of requirements while designing the Life Care:

a) Any patient should be able to search doctors by their name, location.

b) Doctor category as well by doctor name.

c) Each doctor will have a unique identification number and other details.

d) The system should be able to retrieve information like who took an appointment or
what are the details checked-out by a specific doctor.

7
e) The system should be able to collect information of appointments related to the
patient.

f) Patients should be able to check the doctor’s details.

We have three main actors in our system:

a) Administrator
Administrator is authorized to have its own unique login- Id & password. The Admin
section will be managed by an administrator account. Administrator will login to the
Admin account by entering his login details on “ADMIN LOGIN” option that is on
Home Page and then he will be directed to the admin section.

1) The administrator is the one who has the overall control of the web application.

b) Doctor:
Doctor can perform the following functions:-

1) Login to site: Doctor can login to the site from Doctorlogin form, link to which is
available on site’s Home Page.
2) Edit Profile: doctor can edit his/her name, username, password, phone number
whenever he/she wants.
3) View patient: doctor can only view of various patients in the site.
4) View appointment: doctor can view appointment, and delete appointment from
site’s database

c) Patient
Patient can perform the following functions:-
1) Login to site: patient can login to the site from User login form, link to which is
available on site’s Home Page.
2) Edit Profile: patient can edit his/her name, username, password, phone number
whenever he/she wants.
3) Search Different Categories of doctors: - patient can search different categories of
doctors regarding us diseases.

8
4) View doctors and book appointment on that particular search: - patient can view
all the doctors of our site and after login patient can book appointment.

2.1.2 System objectives


Improvement in control and performance-The system is developed to cope up with the
current issues and problems of hospitals. The system can add user, validate user and is
also bug free.
Save cost -After computerized system is implemented less human force will be required
to maintain the library thus reducing the overall cost.

Save time- Patient is able to search doctors by using few clicks of mouse and few search
keywords thus saving his valuable time.

Option of online blogs- Patient will be able to see a detailed description of news going in
the hospitals.

2.2 Existing System


The existing system is very complex as every work is done manually. By using the
present system, work is done manually. So each and every work takes much time to
complete. Whenever the doctor needs the information it is very difficult for the employee
to search for that particular option no details and the drug information to be diagnosed.
The people can’t get the correct information about doctors, their details. The only way is
to contact directly.

Disadvantages
a) The work is done manually so that it takes much time to recognize the patient at the
registration office.
b) Booking appointments.
c) We can’t asses the calculations accurately.
d) Amount of time is more needed when the more patients come to registration counter.
It counts time factor.
e) As there are thousands of patients records; Searching process is a difficult task.
f) Time consuming.
g) Getting clinic details.

h) Doctor patient interaction.

9
2.3 Proposed System

The present system has obvious problems, inhibiting growth and more usage of man
power. The present system which has been proposed is very easy to work .The
computerization of the every department in the health center will reduce the work that is
done manually. The man power is reduced to the maximum extent. The patients at the
registration office are registered within no time, because every time there is no need
search for the particular option no in the shelf’s .The drugs information are maintained
without any complexity and all the calculations are made automatically by this system
there is no need for the calculations

Advantages:
a) A fast and more efficient service to all patients. As there are thousands of patients
records; Searching process is an easy task.
b) Saving in staff time in entering and manipulating data.
c) Easy input, deletion and manipulation of lot, patient details.
d) Making appointments.

e) Put clinic information at user’s finger tips.

2.4 Feasibility Analysis


A feasibility study is conducted to select the best system that meets performance
requirement. This entails an identification description, an evaluation of candidate system
and the selection of best system for the job. The system required performance is defined
by a statement of constraints, the identification of specific system objective and a
description of outputs.

The key consideration in feasibility analysis are-

a) Economic Feasibility

b) Technical Feasibility

c) Operational Feasibility

d) Behavioral Feasibility

10
a) Economic Feasibility

Economic analysis determines the benefits and the saving that are expressed from a
candidate system and compare those costs. It benefits outweigh costs. Otherwise, further
justification or alterations in the proposed system will have to be made if it is to have a
chance of being approved. This is an ongoing effort that improves in accuracy at each
phase of the system life cycle. It looks at the financial aspects of the project.

b) Technical Feasibility

It is a measure of the practically of a specific technical solution and the availability of


technical resources and expertise. When we develop any project it should be made clear
what type of software and hardware support will be required and will it is required and
will it be available.

Technical feasibility centers on the existing computer system. (Hardware/software) and


to what extent it can support the proposed addition also the organization already has
sufficient high-end machines to serve the processing requirements of the proposed
system.

c) Operational Feasibility

It is common knowledge that computer installations have something to do with turnover,


transfers, retraining and changes in employee job status. Therefore, it is understandable
that the introduction of a candidate system requires special efforts to educate, sell, and
train the staff on new ways of conducting business.

d) Behavioral Feasibility

People are inherent to change and computers have been known to facilitate change. An
estimate should be made about the reaction of user staff towards the development of a
computerized system. Computer installations have something to do with turnover,
transfers and change in job status. In this type of feasibility check, we come to know if
the newly developed system will be taken and accepted by the working force i.e. the
people who will use it.

11
CHAPTER 3: REQUIREMENT SPECIFICATION

3.1 Hardware Specification

Hardware Environment (Deployment Server)


PC Windows Server

Processor Intel Pentium Processor 4, 2.4GHz


or above.

RAM 512 MB RAM

HDD 40 GB

Hardware Environment (End user’s PC)

PC PC (Windows 7/8)

Processor Intel Pentium Processor, 233 MHz


or equivalent.

RAM 512 RAM

HDD 500 MB of free HDD space for


Internet Cache

Internet Connection 512K

Table 3.1.1 (Hardware Specification)

12
3.2 Software Specification

Software Environment (Deployment Server)

Operating System Windows

Other software My SQL, PHP

Web Server Apache 2.4.4

Software Environment (End User)

Operating System Win 2000 / Win XP or higher,


Windows

Browser Firefox ,Chrome

ActiveX/Plugin
Flash Player 9 or above

Table 3.2.1 (Software Specification)

3.3 Performance Specification:


Performance is measured in terms of the output provided by the application.

Requirement specification plays an important part in the analysis of a system. Only when
the requirement specifications are properly given, it is possible to design a system, which
will fit into required environment. It rests largely in the part of the users of the existing
system to give the requirement specifications because they are the people who finally use
the system. The requirement specification for any system can be broadly stated as given
below:

• The system should be able to interface with the existing system

• The system should be accurate

13
3.4 : SYSTEM TOOLS AND TECHNOLOGY SPECIFICATION

3.4.1 Front end


a) SUBLIME TEXT: Sublime Text is a text editor for code, HTML, and prose. It
features rich selection of editing commands, including indenting or un-indenting,
paragraph reformatting, line joining, multiple selections, regular expression search
and replace, incremental find as you type, and preserve case on replace.

b) HTML: Hyper Text Markup Language is very effective language to develop the site.
Our project is prepared in HTML. It also includes the important codes that are used
while we coding a site. It supports the d-html and script languages like VB-Script and
Java Script; here in this project we have used the later one.

c) CSS: CSS stands for Cascading Style Sheet. It is used to give designer look to HTML
using the external file. Cascading Style Sheets (CSS) is a style sheet language used
for describing the presentation semantics (the look and formatting) of a document
written in a markup language.

d) PHP: PHP is an acronym for “Hypertext Preprocessor”. It is widely used open


source scripting language. PHP is a server scripting language, and a powerful tool for
making dynamic and interactive Web pages.PHP is a widely-used, free, and efficient
alternative to competitors such as Microsoft's ASP.

e) JQUERY: jQuery is a fast, small, and feature-rich JavaScript library. It makes things
like HTML document traversal and manipulation, event handling, animation, and
Ajax much simpler with an easy-to-use API that works across a multitude of
browsers. With a combination of versatility and extensibility, jQuery has changed the
way that millions of people write

f) JavaScript:- It is powerful client side scripting language which is mainly used for
Validations. It is a Dynamic programming language. It is most commonly used as part
of web browsers, whose implementations allow client-side to interact with the user,
control the browser, communicate asynchronously.

14
WHAT EXACTLY IS PHP?

PHP is an intuitive server side scripting language. Like any other scripting language it
allows developers to build logic into the creation of web page content and handle data
returned from a web browser. PHP also contains a number of extensions that make it easy
to interact with databases, extracting data to be displayed on a web page and storing
information entered by a web site visitor back into the database. Web forms and create
content. PHP provides developers and administrators with a flexible and efficient set of
security safeguards. These safeguards can be divided into two frames of reference:
system level and application level.

HOW DOES PHP WORK?

To develop an understanding of how PHP works it is helpful to first explore what


happens when a web page is served to a user's browser. When a user visits a web site or
clicks on a link on a page the browser sends a request to the web server hosting the site
asking for a copy of the web page. The web server receives the request, finds the
corresponding web page file on the file system and sends it back over the internet to the
user's browser. Programmers from many backgrounds will find themselves already
accustomed to the PHP language.

CHARACTERISTICS OF PHP

PHP is about providing the programmer with the necessary tools to get the job done in a
quick and efficient fashion. Five important characteristics make PHP’s practical nature
possible:

a) Familiarity

b) Simplicity

c) Efficiency

d) Security

e) Flexibility

f) One final characteristic makes PHP particularly interesting: it’s free!

15
3.4.2 Back End

a) MYSQL: MySQL is a relational database. MySQL is a powerful database. It's very


good and free of charge. Many developers in the world selected Mysql and php for
developing their website.

b) What is a Database?

A database is a structure that comes in two flavors: a flat database and a relational
database. A relational database is much more oriented to the human mind and is often
preferred over the gabble-de-gook flat databases that are just stored on hard drives like a
text file. MySQL is a relational database. .

a) MySQL is developed, marketed, and supported by MySQL AB, which is a Swedish


company.
b) MySQL is released under an open-source license. So you have nothing to pay to use
it.
c) MySQL is a very powerful program in its own right. It handles a large subset of the
functionality of the most expensive and powerful database packages.
d) MySQL uses a standard form of the well-known SQL data language.
e) MySQL works on many operating systems and with many languages including PHP,
PERL, C, C++, JAVA etc.
f) MySQL works very quickly and works well even with large data sets.
g) MySQL is customizable. The open source GPL license allows programmers to
modify the MySQL software to fit their own specific environments.

c) XAMPP: XAMPP is the most famous PHP and Perl development environment. It
helps developers to setup a local server which is fully equipped with all necessary tools
and helps them to work at high speed. It is a totally free, very simple in installing Apache
distribution containing Maria DB (MySQL), PHP, and Perl. The set up of the the package
is extremely easy for multiple operating systems like Windows, Linux, Mac OS X and
Solaris.

16
CHAPTER 4: SYSTEM DESIGN

4.1 Introduction
Design is the first step into the development phase for any engineered product or system.
Design is a creative process. A good design is the key to effective system. The term
“design” is defined as “the process of applying various techniques and principles for the
purpose of defining a process or a system in sufficient detail to permit its physical
realization”. It can be defined as a process of applying various principles and techniques
for the defining a device, a system or a process to permit its physical realization with
sufficient detail. Software design is at the technical kernel of the software engineering
process and is applied whatever development paradigm is used.

The system design develops the architectural detail required to build a system or product.
While using systematic approach, software too has pass through the best possible design
phase fine with efficiency, performance and accuracy. The design phase is a transition
from a user oriented document to the programmer documents. System design passes
through two phases of development: Logical and Physical Design.

Logical Design
Logical Design defines the logical flow of a system and the boundaries of a system. It
includes the following steps:

a) Reviews the current physical system – its file content, data flows,
volumes, Frequencies etc.
b) Prepares input specifications – format, content and most of the input functions.
c) Prepares output specifications – it determines the format, content and Frequency of
reports.
d) Prepares edit, security and control specifications.
e) Specifies the implementation plan.
f) Reviews benefits, costs, target dates and system constraints.
g) Design the database.

17
Physical Design
Physical Design produces the Physical working systems and defines the design
specification that tells exactly what the candidate system must do to the programmer. It
includes the following steps.

a) Design the physical system.


b) Design the database.
c) Specify backup procedures.
d) Design physical information flow through the system.
e) Specify input and output media.

4.1.1 Input Design


The input design is the link between the information system and the user. It contains the
creating determination and strategies for information arrangement and those means are
important to put exchange information in to a usable frame for preparing can be
accomplished by assessing the PC to peruse information from a composed or printed
record or it can happen by having individuals entering the information straightforwardly
into the framework. The plan of info centers around controlling the measure of
information required, controlling the mistakes, maintaining a strategic distance from
delay, dodging additional means and keeping the procedure straightforward. The input is
designed in such a way so that it provides security and ease of use with retaining the
privacy. Input Design considered the following things:

• What data should be given as input?

• How the data should be arranged or coded?

4.1.2 Output Design


In output design, emphasis is given on producing a hard copy of the information required
as the output on the CRT screen in some predefined manner. Computer output is the most
important and direct source of information to the use. Output design is a process that
involves designing necessary outputs that should be given to various users according to
their requirements. Efficient, intelligible output design should improve the system’s
relationship with the user and help in decision making.

18
4.2 Table Design
1. patient

Field Name Data Type Size Key Description

id int 5 Primary Key Patient id

patientname varChar 50 Name of the patient

emailid varchar 50 Email of the patient

contact varchar 15 Contact of the patient

password varchar 10 Password of the patient

gender varchar 20 Gender of the patient

address varchar 100 Address of the patient

image longtext Image of the patient

Table 4.2.1 (Patient)

2. blogspot

Field Name Data Type Size Key Description

Id int 5 Primary Key Patient id

posttitle varchar 50 Title of the post

postdetail varchar 50 Detail of the post

Image varchar 200 Image of the post

postdate varchar 10 Date of the post

Table 4.2.2 (Blogspot)

19
3. doctor_list

Field Name Data Type Size Key Description

Did int 11 Primary Key Patient id

Name varChar 50 Name of the doctor

emailid varchar 50 Email of the doctor

contact varchar 15 Contact of the doctor

password varchar 11 Password of the doctor

description varchar 150 Gender of the doctor

address varchar 100 Address of the doctor

image varchar 50 Image of the doctor

fees varchar 10 Fees of the doctor

speciality varchar 100 Speciality of the doctor

Table 4.2.3 (Doctor_list)


4. prescription

Field Name Data Type Size Key Description

Id Int 5 Primary Key Patient id

Patient Varchar 50 Name of the patient

Doctor Varchar 50 Name of the doctor

Symptoms Varchar 200 Symptoms of the patient

Prescriptionmsg Varchar 10 Prescription of the patient

pdate Varchar 20 Prescription date of the


patient

Table 4.2.4 (Prescription)

20
5. appointment

Field Name Data Type Size Key Description

id int 5 Primary Key Patient id

patientemail varChar 50 Email of the patient

doctoremail varchar 50 Email of the doctor

disease varchar 40 Disease of the patient

description varchar 200 Description of the patient

apptime varchar 50 Appointment time of the


patient

appdate varchar 50 Appointment date of the


patient

status longtext 30 Status of the appointment

Table 4.2.5 (Appointment)


6. tbl_logindetails

Field Name Data Type Size Key Description

user_id int 5 Primary Key User’s id

did int 11 id of the doctor

user_email varchar 50 Email of the user

user_name varchar 50 name of the user

user_pass varchar 20 Password of the user

user_type int 1 Type of the user

status int 1 Status

createDate timestamp Date of creation

Table 4.2.6 (Tbl_login details)

21
7. tbl_feedback

Field Name Data Type Size Key Description

Fbid int 5 Primary Key Feedback id

fbname varchar 50 Feedback name

fbphone varchar 50 Feedback phone

fbemail varchar 50 Feedback email

fbsubject varchar 150 Feedback subject

fbmessage varchar 50 Feedback message

fbproductid varchar 50 Feedback product id

fbtime timestamp Feedback time

Table 4.2.7 (Tbl_feedback)


8. clinics

Field Name Data Type Size Key Description

clinic_d Int 10 Primary Key Clinic id

d_id int 10 Id of the doctor

name varchar 200 Name of the doctor

address varchar 200 Address of the doctor

location varchar 150 location of the doctor

timing_ms varchar 200 Timing of the doctor

timing_sun varchar 200 Timing of Sunday of doctor

contact_no varchar 200 Contact of the doctor

mobile_no varchar 200 Mobile no of contact

Table 4.2.8 (Clinics)

22
4.3 Data Flow Diagram
A Data Flow Diagram (DFD) is a graphical representation of the "flow" of data through
an Information System. A data flow diagram can also be used for the visualization of
Data Processing. It is common practice for a designer to draw a context-level DFD first
which shows the interaction between the system and outside entities. This context-level
DFD is then "exploded" to show more detail of the system being modeled.

A DFD represents flow of data through a system. Data flow diagrams are commonly used
during problem analysis. It views a system as a function that transforms the input into
desired output. A DFD shows movement of data through the different transformations or
processes in the system.

Dataflow diagrams can be used to provide the end user with a physical idea of where the
data they input ultimately has an effect upon the structure of the whole system from order
to dispatch to restock how any system is developed can be determined through a dataflow
diagram. The appropriate register saved in database and maintained by appropriate
authorities.
Data Flow Diagram Notation

Function

File/Database

Input/output

Flow

Figure 4.3.1 (DFD Diagram Notation)


23
DFD Level 0 Diagram

Figure 4.3.2 (DFD Level 0 Diagram)

24
DFD Level 1 Diagram

Figure 4.3.3 (DFD Level 1 Diagram)

25
4.4 Entity Relationship Diagrams (ER-Diagrams):

An entity-relationship (ER) diagram is a specialized graphic that illustrates the


interrelationships between entities in a database. ER diagrams often use symbols to
represent three different types of information. Boxes are commonly used to represent
entities. Diamonds are normally used to represent relationships and ovals are used to
represent attributes

An entity-relationship model (ERM) in software engineering is an abstract and


conceptual representation of data. Entity-relationship modeling is a relational schema
database modeling method, used to produce a type of conceptual schema or semantic data
model of a system, often a relational database, and its requirements in a top-down
fashion.

Symbols used in this E-R Diagram:


Entity: Entity is a “thing” in the real world with an independent existence. An entity may
be an object with a physical existence such as person, car or employee. Entity symbol is
as follows

Attribute: Attribute is a particular property that describes the entity. Attribute symbol is
below

Relationship: Relationship will be several implicit relationships among various entity


types whenever an attribute of one entity refers to another entity type some relationship
exits. Relationship symbol is:
Key attributes: An entity type usually has an attribute whose values are distinct for each
individual entity in the collection. Such an attribute is called key attribute. Key attribute
symbol is as follows

26
ENTITY RELATIONSHIP(ER) DIAGRAM

Figure 4.4.1 (ER Diagram)

27
4.5 Summary

It is a process of planning a new business system or replacing an existing system by


defining its components or modules to satisfy the specific requirements. Before planning,
you need to understand the old system thoroughly and determine how computers can best
be used in order to operate efficiently.

System Design focuses on how to accomplish the objective of the system.

System Analysis and Design (SAD) mainly focuses on −

• Systems

• Processes

• Technology

a) Organization
Organization implies structure and order. It is the arrangement of components that helps
to achieve predetermined objectives.

b) Interaction
It is defined by the manner in which the components operate with each other.

For example, in an organization, purchasing department must interact with production


department and payroll with personnel department.

c) Interdependence
Interdependence means how the components of a system depend on one another. For
proper functioning, the components are coordinated and linked together according to a
specified plan. The output of one subsystem is the required by other subsystem as input.

d) Integration
Integration is concerned with how the system components are connected together. It
means that the parts of the system work together within the system even if each part
performs a unique function.

28
CHAPTER 5: SYSTEM IMPLEMENTATON

5.1 Coding & Screenshots


In coding structured programming is a data flow based methodology. The approach
begins with a system specification that identifies inputs and outputs and describes the
functional aspects of the system. The system specifications then are used as a basis for
the graphic representation data flow diagram of the data flows and processes. The next
step is the definition of modules and their relationships to one another in a form called a
structure chart, using a data dictionary and other structured tools. Structured
programming partitions a program into small, independent modules. They are arranged
in a hierarchy that approximates a model of the business area and is organized in a top-
down manner with the details in bottom-up manner.

• Screenshot For Homepage

Figure 5.1.1 (Screenshot For Homepage)

29
Figure 5.1.2 (Screenshot For Admin Login)

5.2 Module Description


For Life Care it is divided into the following Modules:

5.2.1 Admin Module


The following module contains various facilities like doctors registration, patient
registration, book appointment, and post generation and user query.

ADMIN

POST
DOCTOR HANDLING
REGISTRATIO
N AND
INFORMATIO
CLINIC
N PATIENT REGISTRATION USER
REGISTRATION APPOINTMENTS AND
STATUS QUERY
AND INFORMATION
INFORMATION HANDLING

Figure 5.2.1.1 (Admin Module)

30
• Code for Admin module

<!DOCTYPE html>

<?php

include "dbconfigure.php";

session_start();

if(!isset($_SESSION['user_id']) OR $_SESSION['user_type']!=3)

header('Location:login.php?error=invalidUser');

?>

<html lang="en">

<head>

<meta charset="utf-8">

<meta name="viewport" content="width=device-width, initial-scale=1.0">

<meta name="description" content="Creative - Bootstrap 3 Responsive


Admin Template">

<meta name="author" content="GeeksLabs">

<meta name="keyword" content="Creative, Dashboard, Admin, Template,


Theme, Bootstrap, Responsive, Retina, Minimal">

<link rel="shortcut icon" href="img/favicon.png">

<title> Admin Panel

</title>

<!-- Bootstrap CSS -->

<link href="css/bootstrap.min.css" rel="stylesheet">

<!-- bootstrap theme -->

<link href="css/bootstrap-theme.css" rel="stylesheet">

<!--external css-->

<!-- font icon -->

31
<link href="css/elegant-icons-style.css" rel="stylesheet" />

<link href="css/font-awesome.min.css" rel="stylesheet" />

<!-- full calendar css-->

<link href="assets/fullcalendar/fullcalendar/bootstrap-
fullcalendar.css" rel="stylesheet" />

<link href="assets/fullcalendar/fullcalendar/fullcalendar.css"
rel="stylesheet" />

<!-- easy pie chart-->

<link href="assets/jquery-easy-pie-chart/jquery.easy-pie-chart.css"
rel="stylesheet" type="text/css" media="screen"/>

<!-- owl carousel -->

<link rel="stylesheet" href="css/owl.carousel.css" type="text/css">

<link href="css/jquery-jvectormap-1.2.2.css" rel="stylesheet">

<!-- Custom styles -->

<link rel="stylesheet" href="css/fullcalendar.css">

<link href="css/widgets.css" rel="stylesheet">

<link href="css/style.css" rel="stylesheet">

<link href="css/style-responsive.css" rel="stylesheet" />

<link href="css/xcharts.min.css" rel=" stylesheet">

<link href="css/jquery-ui-1.10.4.min.css" rel="stylesheet">

</head>

<body>

<!-- container section start -->

<section id="container" class="">

<!--header Start-->

<?php require('./comnpages/header.php'); ?>

<!--header end-->

<!--sidebar start-->

<?php require('./comnpages/side.php'); ?>

32
<!--sidebar end-->

<!--main content start-->

<section id="main-content">

<section class="wrapper">

<!--overview start-->

<div class="row">

<div class="col-lg-12">

<h3 class="page-header"><i class="fa fa-laptop"></i> Dashboard</h3>

<ol class="breadcrumb">

<li><i class="fa fa-home"></i><a href="index.php">Home</a></li>

<li><i class="fa fa-laptop"></i>Dashboard</li>

</ol>

</div>

</div>

<div class="row">

<div class="col-lg-4 col-md-4 col-sm-12 col-xs-12">

<div class="info-box blue-bg">

<i class="fa fa-database"></i>

<div class="count"><?=totaldoctor()?></div>

<div class="title">Doctors</div>

</div><!--/.info-box-->

</div><!--/.col-->

<div class="col-lg-4 col-md-4 col-sm-12 col-xs-12">

<div class="info-box green-bg">

<i class="fa fa-cubes"></i>

<div class="count"><?=totalappointment()?></div>

<div class="title">Appoinments</div>

</div><!--/.info-box-->

33
</div><!--/.col-->

<div class="col-lg-4 col-md-4 col-sm-12 col-xs-12">

<div class="info-box dark-bg">

<i class="fa fa-credit-card"></i>

<div class="count"><?=totalpatient()?></div>

<div class="title">Patient</div>

</div><!--/.info-box-->

</div><!--/.col-->

</div><!--/.row-->

</section>

<!-----Credit Start------->

<?php #include("./comnpages/credit.php");?>

<!-----Credit End------->

</section>

<!--main content end-->

</section>

<!-- container section start -->

• Code for checking of admin username and password information

<?php

if(isset($_POST['btn_login']))

require('./comnpages/config.php');

$email=$_POST['email'];

$password=$_POST['pass'];

//$user_id=$_POST['user_id'];

echo $sql="SELECT * FROM tbl_logindetails WHERE user_email='$email' AND


user_pass='$password' AND user_type=3 ";

$data=mysqli_query($conn,$sql);

34
if(mysqli_num_rows($data)>0)

session_start();

$row=mysqli_fetch_array($data);

$_SESSION['user_id']=$row['user_id'];

$_SESSION['user_type']=3;

header('Location:index.php');

//}

//else

//{

//header('Location:testlogin.php?error=invalidUSER');

}else{

echo '<script type="text/javascript">

window.location="./login.php?user_name_password_do_not_match";

</script>';

}else{

echo '<script type="text/javascript">

window.location="../index.php?invalidUSER";

</script>';

?>

• Code for appointment booking

<!DOCTYPE html>

<!--[if lt IE 7]><html class="no-js lt-ie9 lt-ie8 lt-ie7"> <![endif]--


>

<!--[if IE 7]><html class="no-js lt-ie9 lt-ie8"> <![endif]-->

<!--[if IE 8]><html class="no-js lt-ie9"> <![endif]-->

35
<!--[if gt IE 8]><!-->

<html class="no-js">

<!--<![endif]-->

<head>

<title>Book Appoinment</title>

<meta charset="utf-8">

<!-- <?php

($_GET);

?> -->

<!--[if IE]>

<meta http-equiv="X-UA-Compatible" content="IE=edge">

<![endif]-->

<meta name="description" content="">

<meta name="viewport" content="width=device-width, initial-scale=1">

<!-- Place favicon.ico and apple-touch-icon.png in the root directory


-->

<link rel="stylesheet" href="css/bootstrap.min.css">

<link rel="stylesheet" href="css/animations.css">

<link rel="stylesheet" href="css/fonts.css">

<link rel="stylesheet" href="css/main.css" class="color-switcher-


link">

<link rel="stylesheet" href="css/shop.css">

<link rel="stylesheet" type="text/css" href="./css/inbox.css">

<script src="js/vendor/modernizr-2.6.2.min.js"></script>

<style

.inpbox

border:1px solid #ddd;

</style>

36
<!--[if lt IE 9]>

<script src="js/vendor/html5shiv.min.js"></script>

<script src="js/vendor/respond.min.js"></script>

<script src="js/vendor/jquery-1.12.4.min.js"></script>

<![endif]-->

</head>

<body>

<!--[if lt IE 9]>

<div class="bg-danger text-center">You are using an


<strong>outdated</strong> browser. Please <a
href="http://browsehappy.com/" class="highlight">upgrade your
browser</a> to improve your experience.</div>

<![endif]-->

<div class="preloader">

<div class="preloader_image"></div>

</div>

<!-- search modal -->

<div class="modal" tabindex="-1" role="dialog" aria-


labelledby="search_modal" id="search_modal">

<button type="button" class="close" data-dismiss="modal" aria-


label="Close">

<span aria-hidden="true">

<i class="rt-icon2-cross2"></i>

</span>

</button>

<div class="widget widget_search">

<form method="get" class="searchform search-form form-inline"


action="./">

<div class="form-group bottommargin_0"> <input type="text" value=""


name="search" class="form-control" placeholder="Search keyword"
id="modal-search-input"> </div> <button type="submit"
class="theme_button">Search</button> </form>

37
</div>

</div>

<!-- Unyson messages modal -->

<div class="modal fade" tabindex="-1" role="dialog"


id="messages_modal">

<div class="fw-messages-wrap ls with_padding">

<!-- Uncomment this UL with LI to show messages in modal popup to your


user: -->

<!--

<ul class="list-unstyled">

<li>Message To User</li>

</ul>

-->

</div>

</div>

<!-- eof .modal -->

<!-- wrappers for visual page editor and boxed version of template -->

<div id="canvas">

<div id="box_wrapper">

<!-- Header Start -->

<?php include('./comnpages/header.php'); ?>

<!--Header End -->

<section class="page_breadcrumbs ls ms section_padding_25 bg_image">

<div class="container">

<div class="row">

<div class="col-sm-12 text-center">

<h2 class="small">Book Appointment</h2>

</div>

</div>

38
<ol class="breadcrumb bottom_breadcrumbs">

<li> <a href="./">

Home

</a> </li>

<li class="active">Book Appointment</li>

</ol>

</div>

</section>

<section class="ls columns_padding_25 section_padding_top_100


section_padding_bottom_100">

<div class="container">

<div class="row">

<div class="col-sm-12">

<h3 class="module-header">Book Appoinment </h3>

</div>

</div>

<div class="row">

<div class="col-md-8 to_animate" data-animation="scaleAppear">

<form method="post" action="appoinmentadd.php">

<div class="row">

<div class="col-sm-12">

<div class="inpbox" >

<!--<label>Full Name</label>-->

&nbsp <i class="fa fa-user highlight2"></i>

<input type="text" style="border:none" size="30" name="name"


placeholder="Full Name">

</div>

</div>

<div class="col-sm-6">

39
<div class="inpbox" >

<!--<label for="phone">Phone Number<span


class="required">*</span></label> -->

&nbsp <i class="fa fa-phone highlight2" aria-hidden="true"></i>

<input type="Number" style="border:none;" name="phone"


placeholder="Phone Number">

</div>

</div>

<div class="col-sm-6">

<div class="inpbox" >

<!--<label for="email">Email address<span


class="required">*</span></label>-->

&nbsp <i class="fa fa-envelope highlight2" aria-hidden="true"></i>

<input type="email" style="border:none;" name="email"


placeholder="Email Address">

</div>

</div>

<div class="col-sm-6">

<div class="inpbox" >

<!--<label for="subject">Subject<span
class="required">*</span></label>-->

&nbsp <i class="fa fa-flag highlight2" aria-hidden="true"></i>

<input type="date" size="30" style="border:none;" name="date"


placeholder="date">

</div>

</div>

<div class="col-sm-6">

<div>

<select name="app_time" class="col-sm-12" style="margin: 0px;padding:


0px;border:1px solid #ddd;border-radius: 0px" >

<option disabled>Select Preferred Time</option>

40
<option>11:00 - 11:15 AM </option>

<option>11:15 - 11:30 AM </option>

<option>11:30 - 11:45 AM </option>

<option>11:45 - 12:00 PM </option>

<option>12:00 - 12:15 PM </option>

<option>12:15 - 12:30 PM </option>

<option>12:30 - 12:45 PM </option>

<option>12:45 - 01:00 PM </option>

<option>01:00 - 01:15 PM </option>

<option>01:15 - 01:30 PM </option>

<option>01:30 - 01:45 PM </option>

<option>01:45 - 02:00 PM </option>

<option>02:00 - 02:15 PM </option>

<option>02:15 - 02:30 PM </option>

<option>02:30 - 02:45 PM </option>

<option>02:45 - 03:00 PM </option>

<option>03:00 - 03:15 PM </option>

<option>03:15 - 03:30 PM </option>

<option>03:30 - 03:45 PM </option>

<option>03:45 - 04:00 PM </option>

<option disabled>Booking After 4:00 PM Not Applicable on


Sunday</option>

<option>04:00 - 04:15 PM </option>

<option>04:15 - 04:30 PM </option>

<option>04:30 - 04:45 PM </option>

<option>04:45 - 05:00 PM </option>

<option>05:00 - 05:15 PM </option>

<option>05:15 - 05:30 PM </option>

<option>05:30 - 05:45 PM </option>

41
<option>05:45 - 05:00 PM </option>

<option>06:00 - 06:15 PM </option>

<option>06:15 - 06:30 PM </option>

<option>06:30 - 06:45 PM </option>

<option>06:45 - 07:00 PM </option>

<option>07:00 - 07:15 PM </option>

<option>07:15 - 07:30 PM </option>

<option>07:30 - 07:45 PM </option>

<option>07:45 - 08:00 PM </option>

<option>08:00 - 08:15 PM </option>

<option>08:15 - 08:30 PM </option>

<option>08:30 - 08:45 PM </option>

<option>08:45 - 09:00 PM </option>

<option>09:00 - 09:15 PM </option>

<option>09:15 - 09:30 PM </option>

<option>09:30 - 09:45 PM </option>

<option>09:45 - 10:00 PM </option>

<option>10:00 - 10:15 PM </option>

<option>10:15 - 10:30 PM </option>

<option>10:30 - 10:45 PM </option>

<option>10:45 - 11:00 PM </option>

</select>

</div>

</div>

<div class="col-sm-12">

<div class="contact-form-message form-group bottommargin_0 inpbox" >

<!--<label for="message">Message</label>-->

<!--&nbsp <i class="fa fa-comment highlight2" aria-hidden="true"></i>-


->

42
<textarea rows="3" cols="45"
style="width:100%;background:url(images.png)no-repeat;border:none;"
name="message" placeholder="Message"></textarea>

</div>

</div>

<div class="col-sm-12 bottommargin_0 ">

<div>

<!-- <input type="hidden" name="uid" > -->

<input type="hidden" name="cid" value="<?php echo $_GET['cid'] ?>" >

<button type="submit" id="contact_form_submit" name="btn_reg"


class="theme_button color2 wide_button margin_0">Book Appoinment
</button> </div>

</div>

</div>

</form>

</div>

<div class="col-md-4 to_animate" data-animation="scaleAppear">

<ul class="list1 no-bullets no-top-border no-bottom-border">

<li>

<div class="media">

<div class="media-left"> <i class="rt-icon2-shop highlight2


fontsize_18"></i> </div>

<div class="media-body">

<h5 class="media-heading grey">Postal Address:</h5> PO Box 97845 Some


str. 567, Los Angeles, California, United States </div>

</div>

</li>

<li>

<div class="media">

<div class="media-left"> <i class="rt-icon2-phone5 highlight2


fontsize_18"></i> </div>

43
<div class="media-body">

<h5 class="media-heading grey">Phone:</h5> 8(800) 123-12345 </div>

</div>

</li>

<li>

<div class="media">

<div class="media-left"> <i class="rt-icon2-stack4 highlight2


fontsize_18"></i> </div>

<div class="media-body">

<h5 class="media-heading grey">Fax:</h5> 8(800) 123-12345 </div>

</div>

</li>

<li>

<div class="media">

<div class="media-left"> <i class="rt-icon2-mail highlight2


fontsize_18"></i> </div>

<div class="media-body greylinks">

<h5 class="media-heading grey">Email:</h5> <a


href="mailto:your@mail.com">pharmacom@example.com</a> </div>

</div>

</li>

</ul>

</div>

</div>

</div>

</section>

<!-- Start Footer -->

<?php include('./comnpages/footer.php'); ?>

<!-- End Footer -->

44
</div>

<!-- eof #box_wrapper -->

</div>

<!-- eof #canvas -->

<script src="js/compressed.js"></script>

<script src="js/main.js"></script>

<!-- Google Map Script -->

<script type="text/javascript"
src="https://maps.googleapis.com/maps/api/js?key=AIzaSyDTwYSMRGuTsmfl2
z_zZDStYqMlKtrybxo"></script>

</body>

</html>

• Screenshot for Appointment Booking

Figure 5.2.1.2 (Appointment Booking)

45
5.2.2 Doctor Module
The following module contains various facilities like doctor registration, doctor login,
online book appointment, and edit profile. Any doctor if at any moment forgets his
password he can retrieve it from forgot password option.

DOCTOR MODULE

Appointment
Doctor Login Status
Doctor
Registration

Username Forgot
and password password
authentication

Figure 5.2.2.1 (Doctor Module)

Screenshot for Doctor module

Figure 5.2.2.2 (Doctor Login)

46
• Code For Doctor Login
<?php
if(isset($_REQUEST['sucess']))
{
echo"<script>
alert('Your Password Change Success');
</script>";

}
?>
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-
scale=1.0">
<meta name="description" content="Creative - Bootstrap 3 Responsive
Admin Template">
<meta name="author" content="GeeksLabs">
<meta name="keyword" content="Creative, Dashboard, Admin, Template,
Theme, Bootstrap, Responsive, Retina, Minimal">
<link rel="shortcut icon" href="img/favicon.png">
<title>Doctor Login</title>
<!-- Bootstrap CSS -->
<link href="css/bootstrap.min.css" rel="stylesheet">
<!-- bootstrap theme -->
<link href="css/bootstrap-theme.css" rel="stylesheet">
<!--external css-->
<!-- font icon -->
<link href="css/elegant-icons-style.css" rel="stylesheet" />
<link href="css/font-awesome.css" rel="stylesheet" />
<!-- Custom styles -->
<link href="css/style.css" rel="stylesheet">
<link href="css/style-responsive.css" rel="stylesheet" />
</head>

<body class="login-img3-body">
<div class="container">

47
<form class="login-form" method="post" >
<input type="hidden" name="ldtype" value='2'>
<div class="login-wrap">
<p class="login-img">Doctor Login<i class="icon_lock_alt"></i></p>
<div class="input-group">
<span class="input-group-addon"><i class="icon_profile"></i></span>
<input type="text" class="form-control" name="emailid"
placeholder="Username" autofocus>
</div>
<div class="input-group">
<span class="input-group-addon"><i class="icon_key_alt"></i></span>
<input type="password" name="password" class="form-control"
placeholder="Password">
</div>
<label class="checkbox">
<input type="checkbox" name="rem" value="remember-me"> Remember me
<span class="pull-right"> <a href="#"> Forgot Password?</a></span>
</label>
<button class="btn btn-primary btn-lg btn-block" name="submit"
type="submit">Login</button>
<!-- <button class="btn btn-info btn-lg btn-block"
type="submit">Signup</button> -->
</div>
</form>
<div class="text-right">
<div class="credits">
</div>
</div>
</div>
</body>
</html>
<?php
session_start();
include "dbconfigure.php";
if(isset($_POST['submit']))
{
$emailid = $_POST['emailid'];
$password = $_POST['password'];

48
$query = "select count(*) from doctor_list where emailid='$emailid'
and password='$password'";
$n = my_one($query);
if($n==1)
{
echo $_SESSION['semailid']=$emailid;
echo $_SESSION['spassword']=$password;
echo '<script>
window.location="index.php";
</script>';
}
else
{
echo '<script>alert("Invalid Login Credentials.")</script>';
}
}
?>

• Screenshot for Appointment module

Figure 5.2.2.3 (Screnshot For Doctor Module)

49
5.2.3 Appointment Book Module
The following module contains various facilities like add new appointment and search
appointment. If any new appointment comes in the database then the admin can check/set
status. On the basis of appointment slot available admin allocates slot to patients and then
patients can check their booking status by login using their credentials.

APPOINTMENT

PENDING ACCEPTED REJECTED


APPOINTMENTS APPOINTMENTS APPOINTMENTS STATUS
STATUS

Figure 5.2.3.1 (Appointment Module)

• Screenshot for Appointment module

Figure 5.2.3.2 (Screenshot For Appointment Module)

50
• Code For Adding New Appoinment

<?php

if (isset($_POST['btn_reg'])) {

$name=$_POST['name'];

$phone=$_POST['phone'];

$email=$_POST['email'];

$date=$_POST['date'];

$apptime=$_POST['app_time'];

$message=$_POST['message'];

$cid=$_POST['cid'];

require './comnpages/config.php';

$appins="INSERT INTO
appoinment(app_name,app_email,app_phone,app_doctor,app_date,app_time,ap
p_msg) VALUES

('$name','$email','$phone','$cid','$date','$apptime','$message') ";

$result=mysqli_query($conn,$appins);

$ticketno = mysqli_insert_id($conn);

if($ticketno){

echo '<script>alert("Your Appointment is booked \n ");

window.location="./appoinment.php"</script>';

}else{

echo '<script>alert("Your Appointment Registration Is Failed Please Try


Again.");

window.location="./appoinment.php"</script>';

}else{

echo '<script>

window.location="./index.php?error_invalid"</script>';

}?>

51
5.2.4 Patient Module
The following module contains various facilities like patient registration, patient login,
online book appointment, and edit profile. Any doctor if at any moment forgets his
password he can retrieve it from forgot password option.

PATIENT MODULE

Patient Patient Login Book


Registration Appointment

Username Forgot
and password password
authentication

Figure 5.2.4.1 (Patient Module)

• Screenshot for Patient module

Figure 5.2.4.2 (Patient Login)

52
• Code For Patient login
<?php

ob_start();

?>

<!DOCTYPE html>

<html class="no-js">

<head>

<title>Patient Login</title>

<meta charset="utf-8">

<link rel="stylesheet"
href="https://use.fontawesome.com/releases/v5.7.0/css/all.css"
integrity="sha384-
lZN37f5QGtY3VHgisS14W3ExzMWZxybE1SJSEsQp9S+oqd12jhcu+A56Ebc1zFSJ"
crossorigin="anonymous">

<meta name="description" content="">

<meta name="viewport" content="width=device-width, initial-scale=1">

<!-- Place favicon.ico and apple-touch-icon.png in the root directory -


->

<link rel="stylesheet" href="css/bootstrap.min.css">

<link rel="stylesheet" href="css/animations.css">

<link rel="stylesheet" href="css/fonts.css">

<link rel="stylesheet" href="css/main.css" class="color-switcher-link">

<link rel="stylesheet" href="css/shop.css">

<link rel="stylesheet" type="text/css" href="./css/inbox.css">

<script src="js/vendor/modernizr-2.6.2.min.js"></script>

<style>

53
.inpbox{

border:1px solid #ddd;

</style>

</head>

<body>

<div class="preloader">

<div class="preloader_image"></div>

</div>

<!-- search modal -->

<div class="modal" tabindex="-1" role="dialog" aria-


labelledby="search_modal" id="search_modal">

<button type="button" class="close" data-dismiss="modal" aria-


label="Close">

<span aria-hidden="true">

<i class="rt-icon2-cross2"></i>

</span>

</button>

<div class="widget widget_search">

<form method="get" class="searchform search-form form-inline"


action="./">

<div class="form-group bottommargin_0"> <input type="text" value=""


name="search" class="form-control" placeholder="Search keyword"
id="modal-search-input"> </div> <button type="submit"
class="theme_button">Search</button> </form>

</div>

54
</div>

<!-- Unyson messages modal -->

<div class="modal fade" tabindex="-1" role="dialog"


id="messages_modal">

<div class="fw-messages-wrap ls with_padding">

</div>

</div>

<div id="canvas">

<div id="box_wrapper">

<!-- Header Start -->

<?php include('./comnpages/header.php'); ?>

<!--Header End -->

<section class="page_breadcrumbs ls ms section_padding_25 bg_image">

<div class="container">

<div class="row">

<div class="col-sm-12 text-center">

<h2 class="small">Patient Login</h2>

</div>

</div>

<ol class="breadcrumb bottom_breadcrumbs">

<li> <a href="./">

Home

</a> </li>

<li class="active">Patient Login</li>

55
</ol>

</div>

</section>

<section class="ls columns_padding_25 section_padding_top_100


section_padding_bottom_100">

<div class="container">

<div class="row">

<div class="col-sm-12">

<h3 class="module-header">Login</h3>

</div>

</div>

<div class="row">

<div class="col-md-8 to_animate" data-animation="scaleAppear">

<form method="post" enctype="multipart/form-data">

<div class="row">

<div class="col-sm-12">

<div class="inpbox">

<!--<label for="email">Email address<span


class="required">*</span></label>-->

&nbsp <i class="fa fa-envelope highlight2" aria-hidden="true"></i>

<input type="email" style="border:none;" name="emailid"


placeholder="Email Address">

</div>

</div>

<div class="col-sm-12">

56
<div class="inpbox" >

&nbsp <i class="fas fa-key highlight2" aria-hidden="true"></i>

<input type="password" size="30" style="border:none;" name="password"


placeholder="Password">

</div>

</div>

<div class="col-sm-6 bottommargin_0 ">

<div>

<button type="submit" id="contact_form_submit" name="submit"


class="theme_button color2 wide_button margin_0">Login</button> </div>

</div>

<div class="col-sm-6 bottommargin_0 ">

<div >

<a href= "patientsignup.php" id="contact_form_submit"


class="theme_button color2 wide_button margin_0">SignUp</a> </div>

</div>

</div>

</form>

</div>

<div class="col-md-4 to_animate" data-animation="scaleAppear">

<img src="images/patientlogin.jpg" style = "height : 300px">

</div>

</div>

</div>

</section>

57
<!-- Start Footer -->

<?php include('./comnpages/footer.php'); ?>

<!-- End Footer -->

</div>

<!-- eof #box_wrapper -->

</div>

<!-- eof #canvas -->

<script src="js/compressed.js"></script>

<script src="js/main.js"></script>

<!-- Google Map Script -->

<script type="text/javascript"
src="https://maps.googleapis.com/maps/api/js?key=AIzaSyDTwYSMRGuTsmfl2z
_zZDStYqMlKtrybxo"></script>

</body>

</html>

<?php

session_start();

include "dbconfigure.php";

if(isset($_POST['submit']))

$emailid = $_POST['emailid'];

$password = $_POST['password'];

$query = "select count(*) from patient where emailid='$emailid' and


password='$password'";

$n = my_one($query);

58
if($n==1)

echo $_SESSION['semailid']=$emailid;

echo $_SESSION['spassword']=$password;\

if(isset($_GET['id']))

/*echo '<script>

window.location="patient/patienthome.php";

</script>';*/

header("location:patient/bookappointment.php?id=".$_GET['id']);

else

header("location:patient/patienthome.php");

else

echo '<script>alert("Invalid Login Credentials.")</script>';

?>

59
Figure 5.2.4.3 (Patient Module)

• Screenshot for Blogs

Figure 5.2.4.4 (Blogs)

60
5.3 Summary
Implementation is a process of ensuring that the information system is operational. It
involves −

a) Constructing a new system from scratch

b) Constructing a new system from the existing one.

Implementation allows the users to take over its operation for use and evaluation. It
involves training the users to handle the system and plan for a smooth conversion.

Training
The personnel in the system must know in detail what their roles will be, how they can
use the system, and what the system will or will not do. The success or failure of
welldesigned and technically elegant systems can depend on the way they are operated
and used.

Training Systems Operators


Systems operators must be trained properly such that they can handle all possible
operations, both routine and extraordinary. The operators should be trained in what
common malfunctions may occur, how to recognize them, and what steps to take when
they come.

Training involves creating troubleshooting lists to identify possible problems and


remedies for them, as well as the names and telephone numbers of individuals to contact
when unexpected or unusual problems arise.

Training Guidelines
a) Establishing measurable objectives

b) Using appropriate training methods

c) Selecting suitable training sites

Employing understandable training materials

61
CHAPTER 6: SYSTEM TESTING

6.1 Introduction
The purpose of system testing is to identify and correct errors in the candidate system.
Testing is an important element of software quality assurance ad represents the ultimate
review of specification, design and coding. The increasing visibility of the software as a
system element and the cost associated with a software failure are motivated forces for
well planned, through testing. System testing was conducted in order to detect errors and
for comparing then the final system with the requirement specification reports, i.e.
whether the system meets requirements. During testing the software was executed with
the set of test cases and the output of programs for the test cases was evaluated to
determine if the program is performing as it was expected to.

Testing presents an interesting challenge for the software engineers attempt to build
software from an abstract concept to an acceptable implementation. In testing engineer
create a series of test cases that occurs when errors are uncovered. Testing is the process
of executing a program for finding errors. A good test is one that has the high probability
of finding an uncovered error. A successful error is one that uncovers undiscovered
errors.

The term error is used to refer the difference between actual output of the software and
the current output. Fault is a condition that causes the software to fail to perform its
required function. Software reliability is defined as a required function. Software
reliability is defined as the probability that the software will not undergoes failures for a
specified times under specified condition. Failure is the inability of a system or a
component to perform a required function according to its specification. Different levels
of testing were employed for software to make it error free, fault free and reliable.

There are two major type of testing they are

a) White box testing


b) Black box testing

62
6.2 Testing Strategies
a) White box testing

White box testing is performed to reveal problems with the internal structure of a
program. This requires the tester to have detailed knowledge of the internal structure. A
common goal of white box testing is to ensure a test case exercises every path through a
program. A fundamental strength that all white box strategies share is that the entire
software implementation is taken into account during testing, which facilitates error
detection even when software specification is vague or incomplete. The effectiveness or
thoroughness of white box testing is commonly expressed in terms of test or code
coverage metrics, which measure the fraction of code exercised by test cases.

1) All independent paths within a module have been exercised once. In our system,
ensuring that case was selected and executed checked all case structures. The bugs that
were prevailing in some part of code where fixed.

2) All logical decisions were checked for the truth and falsify of the values.

b) Black Box Testing

Black box tests are performed to access how well a program meets its requirements,
looking for incorrect or missing functionality. Functional tests typically exercise code
with valid or nearly valid input for which the expected output is known. This includes
concepts such as ‘boundary values’. Performance tests evaluate response time, memory
usage, throughput, device utilization and execution time. Stress tests push the system to
or beyond its specified limits to evaluate its robustness and error handling capabilities.

Black box testing uncovers the following types of errors

1) Incorrect or missing functions

2) Interface errors

3) External database access

4) Performance errors

5) Initialization and termination errors

63
6.3 SOFTWARE TESTING HIERARCHY

Figure 6.3.1 (Testing Hierarchy)


As with almost any software engineering process, software testing has a prescribed order
in which things should be done. These are the steps taken to fully test new software in
preparation for marketing it:

1. Unit Testing:

Unit testing is essentially for the verification of the code produced during the coding
phase and the goal is test the internal logic of the module/program. Unit testing is
normally done by the programmer who writes the code.

Test For the admin module


a) Testing admin login form-This form is used for log in of administrator of the
system. In this 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 for username and password.

b) Doctor account addition - In this section the admin can verify doctor details and then

64
only add doctor details to main database it contains add and delete buttons if user click add
button data will be added to doctor database and if he clicks delete button the doctor data
will be deleted.

c) Book Appointment - Admin can check details of appointments and can add the
details to the main appointment table also he can view the appointments requests.

Test for Doctor login module


a) Test for doctor login form-This form is used for log in of doctors .In this we enter
username and password if all these are correct doctor login page will open other wise if
any of data is wrong it will get redirected back to the login page and again ask for username
and password.

b) Test for account creation- This form is used for new account creation when doctor
does not fill the form completely it asks again to fill the whole form when he fill the form
fully it gets redirected to page to fill all details.

Test for patient login module

a) Test for patient login form- This form is used for login of patient.In this we enter the
username and password if all these are correct patient login page will open other wise if
any of data is wrong it will get redirected back to the login page and again ask for username
and password.

b) Test for account creation- This form is used for new account creation when patient
does not fill the form completely it asks again to fill the whole form when he fill the form
fully it gets redirected to page to fill all details.

2. Integration Testing:

All the tested modules are combined into sub systems, which are then tested. The goal is
to see if the modules are properly integrated, and the emphasis being on the testing
interfaces between the modules. On this project integration testing is done mainly while
implementing menus in a sample application such as Browser for Mobiles. In this type of
testing we test various integration of the project module by providing the input.

65
6.4 Test Cases for Life Care
6.4.1 Login Form:

S.No Test Case Excepted Result Test


Result

1 Enter valid name and password & Software should display main Successful
click on login button window

2 Enter invalid Software should not display successful


main window

Table 6.4.1.1 (Login Form)

6.4.2 Appointment Booking form:

SL.No Test Case Excepted Result Test


Result
1 On the click of This shows the status of pending Successful
pending appointments,based on schedule admin can
appointments menu accept appointments.

2. On the Click of This shows the status of accepted Successful


accepted appointments,patient can login using their
appointments menu credentials and know about their booking
status.

3. On the Click of This shows the status of rejected Successful


rejected appointments,based on schedule admin can
appointments menu reject appointments.

Table 6.4.2.2 (Appointment booking form)

66
CHAPTER 7: CONCLUSION

7.1 Conclusion
The system has been developed with much care that it is free of errors and at the same
time it is efficient and less time consuming. The important thing is that the system is
robust. Avoid malfunction from outsiders. It goes through all phases of software
development cycle. So product is accurate. Also provision is provided for future
developments in the system.

Completion of the development process resulted in a software package that provide user
friendly environment which is very easy to work with, even for people with very little
knowledge of computer. Management of various tasks is incorporated in the package and
will deliver the required information in a very easy to use and easy to access manner.
This package will provide accuracy, efficiency, speed and easiness to the end user. Paper
work will be subjugated and come to an appropriate level. This web application involves
almost all the basic features of the online searching of doctors and appointment
management. The future implementation will be online help for the users and chatting
with website administrator.

Life Care provides various features, which complement the information system
and increase the productivity of the system. These features make the system easily usable
and convenient. Some of the important features included are listed as follows:

a) Intelligent User Forms Design

b) Data access and manipulation through same forms


c) Access to most required information

d) Data Security

e) Restrictive data access, as per login assigned only.

f) Organized and structured storage of facts.

67
7.2 Future Scope
Our Life care system currently focuses on the relationships between patients and
doctors. We plan to extend the system to other healthcare facilities and professionals,
such as laboratory technicians who perform and report tests and analyses requested by
physicians. We also plan to investigate whether our Clinic modules can be interfaced to
applications supplied by pharmaceutical companies that provide information on
medications and dosages and warn of interactions between medications. In addition, we
plan to investigate drug delivery devices, such as e-pillboxes, that prompt and monitor
the regular and timely consumption of medications.

68
CHAPTER 8: BIBLIOGRAPHY

8.1 Reference Books


● PHP and MYSQL Web Development (Developer's Library) Import, 1 Oct 200by
Luke Welling (Author), Laura Thomson (Author)
● PHP Advanced and Object-Oriented Programming: Visual Quick Pro Guide –
Import, 13 Sep 2012 by Larry Ullman (Author)

8.2 URLs
● www.phpmanual.net
● www.w3schools.com
● https://en.wikipedia.org/wiki/PHP
● https://www.codecademy.com/learn/php
● https://www.javascript.com/
● https://www.mysql.com/

69

You might also like