Final Year Project Report

MEDICAL DIAGNOSIS SYSTEM

BS(IT) (Session: 2020-24)

Project Supervisor
Umber Noreen
Assistant Professor
University of Sahiwal

Submitted by
Sheharyar Ahmad BSIT-E1-20-09

DEPARTMENT OF INFORMATION TECHNOLOGY

 PREFACE
Accurate and timely diagnosis is the cornerstone of effective healthcare. The
purpose of this medical diagnosis system is to provide healthcare
professionals with a reliable and intuitive tool to facilitate precise diagnosis
and treatment planning. Leveraging advanced algorithms and machine
learning techniques, this system analyzes patient symptoms, medical history,
and diagnostic data to suggest potential diagnoses and recommended
courses of action. Our goal is to empower healthcare professionals with
technology that improves patient outcomes, streamlines clinical workflows,
and enhances the overall quality of care.

 Highlights the importance of accurate diagnosis

 Introduces the purpose and functionality of the system

 States the goals and benefits of the system

ACKNOWLEDGMENT
First of all, we thank Almighty Allah who gives us the strength and ability to
think, work and deliver what we are assigned to do. Secondly, we must be
grateful to our internal supervisor Miss Umber Noreen who guided us in this
project. We also acknowledge our teachers who guided, taught and helped us
during our study period. We would also like to thank all departmental staff and
university staff, who had assisted us during our stay at the university.
 UNIVERISTY OF SAHIWAL, SAHIWAL
University Online: www.uosahiwal.edu.pk

DEPARTMENT OF INFORMATION TECHNOLOGY

PROJECT APPROVAL FORM

CERTIFICATE OF COMPLETION

This is to certify that the following student

Sheharyar Ahmad BSIT-E1-20-09

have successfully completed their final year project titled

Project Title

in the partial fulfillment for the requirements of the Degree of Bachelor of

Information Technology during the academic session 2020-2024.

Signatures: Signatures:

_____________________ _____________________

Umber Noreen Dr. Umar Draz

Advisor Teacher In Charge
Department of Computer Science Department of Information
Technology
University of Sahiwal University of Sahiwal
 ABSTRACT

Medical Diagnosis System is a cutting-edge, tool that assists healthcare

professionals in accurately diagnosing diseases and developing effective
treatment plans. By integrating machine learning algorithms with vast medical
knowledge, MDS analyzes patient data, identifies patterns, and provides a list
of potential diagnoses along with recommended diagnostic tests and
treatments. With its user-friendly interface and real-time processing, IMDS
aims to enhance diagnostic accuracy, reduce errors, and improve patient
outcomes.

 Introduces the system's name and purpose

 Emphasizes its benefits, such as improved diagnostic accuracy and reduced

errors

 Provides relevant keywords for easy searching

A. PREFACE
B. ACKNOWLEDGEMENT
C. CERTIFICATE OF COMPLETION BY PROJECT ADVISOR
D. ABSTRACT
E. TABLE OF CONTENTS

All the headings above must be included in Table of Contents (TOC) according to
correct page numbers. Provided below is an exemplary TOC.
Provided After TOC is MAIN-BODY of Report.
See that all chapters get mentioned in the header
 TABLE OF CONTENTS

PREFACE
ACKNOWLEDGEMENT
CERTIFICATE OF COMPLETION
ABSTRACT
TABLE OF CONTENTS

Chapter 1 Introduction

1.1 Introduction
1.1.1 Relevance to Course Modules
1.1.2 Project Background
1.2 Literature Review
1.2.1 Analysis from Literature Review
1.2.2 Methodology and Software Lifecycle for This Project
1.3 Rationale behind Selected Methodology
1.3.1 Problem Statement
1.4 Deliverables and Development Requirements

Chapter 2 Software Requirement Specification (SRS)

2.1 Requirement Analysis

2.2 Use Cases Diagram(s)
2.2.1 Use Cases
2.2.2 Detailed Use Case
2.3 Functional Requirements
2.4 Non-Functional Requirements

Chapter 3 Design and Architecture

3.1 System Architecture
3.2 Process Flow/Representation
3.3 Data Representation [DFD]
3.4 Sequence Diagram
3.4.1 Admin Sequence Diagram
3.4.2 Doctor Sequence Diagram
3.4.3 Patient Sequence Diagram

Chapter 4 Implementation

4.1 Language, Tools and Technologies Used

4.2 User Interface

Chapter 5 Testing and Evaluation

5.1 Manual Testing

5.1.1 System testing
5.1.2 Unit Testing
5.1.1.3 Testing Objective
5.2 Functional Testing
5.3 Integration Testing

Chapter 6 Conclusion and Future Work

6.1 Conclusion
6.2 Future Work

REFRENCE
Chapter # 1
Introduction
1.1 Introduction
Medical domain is characterized, like many other domains, by an exponential
evolution of the knowledge. There are a lot of tools which try to reduce the risk of
error apparition in medical life. Diagnosis has a very important role here. It is the first
step from a set of therapeutic actions; an error at this level can have dramatic
consequences. This disease diagnosis system is an expert system which is used for
simplifying the task of doctors. It is a system that checks a patient at initial level and
suggests the possible diseases. It starts with asking about symptoms to the patient, if
the system is able to name the disease then it provide the name and the corresponding
medical prescription, If the system is not sure enough, then it redirects the patient to
provide more symptoms of the disease. On the basis of available cumulative
information, the system will display the name and the medical prescription of the
disease. This system not only simplifies task of the doctors but also helps the patients
by providing initial medicines for small diseases in emergency. The system is not
meant to replace psychologists, but rather to support them in generating hypotheses at
an early stage of diagnosis.

1.1.1 Relevance to Course Modules

This project is related to Course of Web Development, Database Management and
Human Computer Interaction. In web development course we studied how to create
web pages, how to customize them, how to create interface of system. We studied
how to create web page using PHP language, this project is also us2 PHP language for
Front end coding so this course is helpful for me.

In Database Management course studied about how to create database, how to manage
database, how to create relationships between tables. How to use SQL Server. This
project also use SQL Server for back end processing so this course is helpful in
database work.

In Human Computer Interaction Course, we studied about how to create an Interactive

design for users. Studied about different Interaction Models and Designs. So, this
course is helpful to design the interactive interface of the project.
 1.1.2 Project Background

The ideaSystems
Present
Manual Diagnosis
behind this “An Expert System in Medical Diagnosis” is
to make such system which can help the patients and doctors in
Almost
In the current
all oversystem,
the worldDoctors
still’ uses
may manual
have to spend
diagnostic
muchsystem,
time to
diagnoses process according to the provided specific symptoms. It
some countries
diagnose diseaseuse
and expert
generating
systems results.
to diagnose
In order
disease
to reduce
rapidly,
will help people more.
and following
doctor's workload
discuss
likeboth
“Analyze
the manual
the symptoms”,
and web-based
“Maintain
system.
record of treatment history”, “Completing the analysis and
diagnoses the diastase” An Expert System in Medical Diagnosis is
proposed. The proposed system will help doctor to diagnose the
disease and suggest the diseases related to symptom and will
reduce the workload of the Doctors.

Generally, in all the Hospitals or clinics doctors are using manual way to diagnose any
disease. With the usage of this system, its users are able to diagnose the disease at one
click against particular symptoms. This will make the process easier. By using this
system user will be able to diagnose the disease within the seconds. On the other
hand, this system also helps the

Hospital or clinic management to manage the record of treatment history of their

patients such as patient information in more effective and precise way.

1.2 Literature Review

1.2.1 Analysis from Literature Review (in the context of project)
Present System Components

The current system is manual analysis of the symptoms. Doctors may have to spend
much time to analyze the symptoms and to diagnose the disease.

Following Components are included in manual analyze system:

o Gather symptoms from patient

o Analyze the symptoms carefully
o Final step disease is diagnosed
o At last, record is maintained.

Shortcomings
The first problem is that analysis of symptoms and keep record of treatment history.
This brings us to the age-old discussion of keeping information in the form databases
versus keeping the same on sheets of paper. Keeping the information in the form of
hard-copied documents leads to the following problems:

Filtering is not easy

It becomes hard to filter relevant documents for their relevant ones if the count of the
same crosses a certain manageable number.

Filing poses a problem

Filing the documents categorically is a time consuming and tedious exercise.

Reviewing becomes time-consuming

All the process done manually at the centers and all the records are maintained on the
papers. So, the maintenance of the record is very difficult by the doctors and as well
as it’s very difficult for the doctor to check the record. The Existing system is paper
based, time consuming, boring, less flexible and provides a very confused working
schedule. The chance of loss of records error is high and also record searching is
difficult. Maintenance of the system is also very difficult and takes lot of time.

An Expert System in Medical Diagnosis

Now a day the expert system is getting popular with a tremendous speed. As the
technology is spreading throughout the world the automated system will also taking
 the places of the manual systems. Currently many institutes are running their expert
diagnose systems at a very successful rate. Unfortunately, In Pakistan there is no such
institute which provide that kind of services. As the time is progressing the expert
system diagnosis is making interest to the doctors and all other stakeholders. Within
the recent time this system will be taken place to this technology world. But this
system also has some lacking.

Feed Back from Current Scenario

From the previous two systems I realize to solve the problems of those systems to get
an expert diagnose system. In the previous two systems the things that are short from
a diagnosis’s process, to fix it up I design a system that work according to the web
base system. From this system we can omit the manual system’s problem criteria,
which is totally automated. It also omit the general web based system because it gives
the evaluate option for the doctor performance and feedback criteria. This will help to
remove current system’s problems.

1.2.2 Methodology and Software Lifecycle for This Project

AVAILABLE METHODOLOGIES
 Waterfall
 Cool and Fix
 Spiral
 Rapid prototyping
 Unified process (UP)
 Iterative model
CHOSEN METHODOLOGY

ITERATIVE MODEL

Software Development Life Cycle (SDLC) is extremely vast and full of various
development and testing activities, methodologies, techniques, tools, and more. It
involves intense planning and management, calculation and preparation. It is only
after combining all these efforts of the software engineers that a software or
application is successfully developed. Iterative Model is too a part of Software
Development Life Cycle.
 It is a particular implementation of a software development life cycle that focuses on
an initial, simplified implementation, which then progressively gains more complexity
and a broader feature set until the final system is complete. In short, iterative
development is a way of breaking down the software development of a large
application into smaller pieces.

FIGURE 1.1 ITERATIVE MODEL DEVELOPMENT CYCLE

Planning Phase:
This is the first stage of the iterative model, where proper planning is done by the team, which
helps them in mapping out the specifications documents, establish software or hardware
requirements and generally prepare for the upcoming stages of the cycle.

Analysis and Design Phase:

Once the planning is complete for the cycle, an analysis is performed to point out the
appropriate business logic, database models and to know any other requirements of this
Particular stage. Moreover, the design stage also occurs in this phase of iterative model, where
the technical requirements are established that will be utilized in order to meet the need of
analysis stage.
Implementation Phase:
 This is the third and the most important phase of the iterative model. Here, the actual
implementation and coding process is executed. All planning, specification, and design
documents up to this point are coded and implemented into this initial iteration of the project.

Testing Phase:

After the current build iteration is coded and implemented, testing is initiated in the cycle to
identify and locate any potential bugs or issues that may have been in the software.

Evaluation Phase:
The final phase of the Iterative life cycle is the evaluation phase, where the entire team along
with the client, examine the status of the project and validate whether it is as per the suggested
requirements.

1.3Rationale behind Selected Methodology

Iterative solves the following problems often faced in the software development projects. It is
very easy to use for changing requirements. It provides the facility to build a prototype before
the final built of project. Costs Effectiveness – Extensive and ongoing testing makes sure the
changes do not break the existing functionality. A running working system always ensures
sufficient time for accommodating changes such that the current operations are not affected.

1.3.1 Problem Statement

The project is mainly focused on medical field in expert system. Early career
psychologists often find it challenging to diagnose disorders/disease. It has also been
noticed that much time is spent in physical examination and interview of patients
before treatment commences. .The proposed system will address these problems
effectively by providing quality diagnosis in realtime.

1.4 Deliverables and Development Requirements

We will use PHP for developing our project. PHP originally stood for Personal Home Page. The
updated version of PHP scripting can be used with any combination of Web Server, operating
system and platform. PHP also allow web developers to write dynamically generated pages
quickly. Its usefulness includes the ability to read and write files, gather and process the data,
send data via email, access and manipulates database records, read and write cookies, maintain
data in session variables, facilitate user authentication, provide data encryption and much more.
2.1

Chapter # 2
Software Requirement
Specification (SRS)
Requirement Analysis
Requirements Analysis is the process of defining the expectations of the users for an
application that is to be built or modified. Requirements analysis involves all the tasks
that are conducted to identify the needs of different stakeholders. Therefore, requirements
analysis means to analyze, document, validate and manage software or system
requirements. High-quality requirements are documented, actionable, measurable,
testable, traceable, helps to identify business opportunities, and are defined to a facilitate
system design.

2.2 Use Cases Diagram(s)

Admin:
Doctor:

Figure 2.2 Doctor Use case

Patient:
 2.2.1 Detailed Use Cases

Figure 2.3 Patient use case

Table 2.1

Primary Use Cases Includes

Actors
Admin 1. Diagnosis
2. Manage Doctors Account (CRUD, Activate/deactivate)
3. Manage Patient Account (CRUD, Activate/deactivate)
4. Manage Disease Database (CRUD)
5. View Feedback
Doctor 6. Diagnose
7. Manage Disease Database (CRUD)
8. Treatment History
9. Give Feedback
Student 10. Diagnose
11. Appointment
12. Treatment History
13. Give Feedback
 Use case scenario 1

Use Case ID UC-1 Table 2.2

Use Case Diagnose

Name

Actors Admin

Description This use case describes how the Administrator diagnose

the disease by providing specific symptoms related to a
specific disease.

Pre-Conditions The Administration must logged in.

Post The registration must be done correctly.

Conditions

This use case starts when the Administrator wishes to diagnose a

Normal Course disease
1. Admin register the Disease to system. After that use must fill in all
blanks flow requirements of this page and sure that is correct
information. Once the registration is located, one of the sub flows
is executed

2. All information will save by system and admin can update or

delete if that is need.

3. System update information of symptoms or disease into

Database

If the Administrator want to diagnose any disease open

the diagnose now form. Fill all the requirements and then
click on diagnose. System will return disease according to
the selected symptoms.
Use Case Scenario 2

Use Case ID: UC-3

Use Case Scenario 3
UseUse CaseID
Case ManageUC-2
Patients Account
Name:

UseActors:
Case Admin Manage Doctors Account
Name:
Description: This use case describes how the Administrator manages Patients accounts in
expert system in medical diagnoses such as add, view, edit, delete the Course
details
Actors Admin
Preconditions: The Administration must logged in.

Post The registration must be done correctly.

Description This use case describes how the Administrator manages
conditions:

Normal This useDoctor accounts

case starts when theinAdministrator
expert system in medical
wishes to add, editdiagnoses
and delete
registration,
Course: such as add, view, edit, delete the Course details
1. Admin register the patient to system. After that use must fill in all
blanks flow requirements of this page and sure that is correct
Preconditions information.
The Administration must
Once the registration logged in.of the sub flows is
is located-one
executed
Post Conditions2. All information
The registration must be done correctly.
will save by system and admin can up-Date, change
if that is need.
This use case starts when the Administrator wishes to add, edit and
Normal Options delete registration,
3. The system requests that the Administrator specify the registration
1. Admin register the Doctor to system. After that use must fill in
needed to be changed
all blanks flow requirements of this page and sure that is correct
4. System information. Once the of
update information registration is located-one
registration into databaseof the sub flows is
executed
5. If the2.Administrator
All information selected “Delete
will save these Registration”
by system and admin canTheup-Date,
“Delete
registration”
changesubif flow is need.
that is executed.

3. The system requests that the Administrator specify the

Sub flows:
registration needed to be changed
Delete an Registrations
4. System
1. The system update
should information
be confirmed of registration into database
by the
Administration
5. If the
2. The system Administrator
removes selected “Delete
these Registrations these
from the Registration” The
Database.
“Delete registration” sub flow is executed.
Alternative None
Table 2.3
Courses: Sub flows:
Delete a Registrations
Exceptions: None. 1. The system should be confirmed by the
Administration
2. The system removes these registrations from the
Database.
 Table 2.4
Use case scenario 5
Table 2.5
 Use Case ID: UC-4 Use
Case Use Case Manage Disease database
Name:

Actors: Admin
Description: This use case describes how the Administrator manages disease database in
expert system in medical diagnoses such as add, view, edit, and delete the
Course details
Preconditions: The Administration must logged in.

Post The registration must be done correctly.

conditions:

Normal This use case starts when the Administrator wishes to add, edit and delete
Course: Disease,
1. Admin register the Disease to system. After that use must fill in all
blanks flow requirements of this page and sure That is correct information.
Once the registration is located-one of the sub flows is executed

2. All information will save by system and admin can up-Date, change if
that is need.

3. The system requests that the Administrator specify the Disease

needed to be changed

4. System update information of Disease into database

5. If the Administrator selected “Delete these Disease” The “Delete

registration” sub flow is executed.

Sub flows:
Delete an Registrations
1. The system should be confirmed by the
Administration
2. The system removes these Registrations from the Database.

Alternative None
Courses:

Exceptions: None.

Scenario 5
Use Case ID: UC-5
Use Case Scenario 6

Use Case Feedback View

Name:

Actors: Admin
Description: This use case describes how the Administrator view feedback by doctor and
given patient
Preconditions: The Administration must be logged in. Doctor and Patient must be already
registered

Use Case ID:The Allocation

UC-6 must be Saved correctly.
Post
conditions:
Use Case Diagnose
Name: This use case starts when the Administrator wishes to view the Feedback
Normal
Actors: Doctor
Course: 1. Admin will click on the feedback link. Feedback form will open.
This use case describes how the Doctor diagnose the disease by providing
2. Admin willsymptoms
specific select one related
of the feedback fromdisease.
to a specific Doctor and Patient and
Description:
able to view the feedback

Pre-conditions: The Doctor must logged in.

Post conditions: The registration must be done correctly.

Table 2.6
Normal Course: This use case starts when the doctor wishes to diagnose the disease.

1. Doctor register the Disease to system. After that use must fill in
all blanks flow requirements of this page and sure that is correct
information. Once the registration is located, one of the sub flows
is executed

2. All information will save by system and admin can update or

delete if that is need.

3. System update information of symptoms or disease into Database

Table 2.7

Use Case 4. If the Doctor want to diagnose any disease open the diagnose now
Treatment history
Name: form. Fill all the requirements and then click on diagnose. System
will return disease according to the selected symptoms.
Actors Doctor
Description: This use case describes how a Doctor add patient treatment history

Alternative None
Courses:

Exceptions: None.
 Use
Case
Preconditions: Doctor is identified and authenticated.
Scenario
8
Post The registration must be done correctly.
Conditions

Normal
Course: This use case starts when the Doctor wishes to add patient treatment history
1. Doctor will open the patient profile and click on treatment.
2. Treatment form will open, all the field in that form filled Properly
according to the requirements and then submit it.
3. That is correct information. Once the registration is located- one of the
sub flows is executed.

UC-10
Use Case ID: UC-8
Use Case Give Feedback
Name:

Actors: Doctors Table

2.10the Doctor give feedback.
is use case describes how
Description:
Preconditions The Doctor must be logged in. Doctor must be already registered.
: The Allocation must be Saved correctly.
Post
conditions:
This use case starts when the Doctor wishes to give the feedback
Normal
Course: 1. Doctor will click on the feedback link. Feedback form will Open.

2.Doctor will add feedback in the form and then submit it

Use Case ID:

Use Case Diagnose
Name:

Actors: Patient
This use case describes how the Patient diagnose the disease by providing
Description: specific symptoms related to a specific disease.

Use Case
Pre-conditions: The Patient must logged in.
Scenario
Table 2.9
10
Post conditions: The registration must be done correctly.
Normal Course: This use case starts when the Patient wishes to diagnose a
disease
Table
1. Patient register the Disease to 2.11
system. After that use
must fill in all blanks flow requirements of this page
and sure that is correct information. Once the
registration is located, one of the sub flows is executed

2. All information will save by system and Patient can

update or delete if that is need.
Use Case Scenario 11
3. System update information of symptoms or disease into Database

4. If the Patient want to diagnose any disease open the

diagnose now form. Fill all the requirements and then
click on diagnose. System will return disease according
to the selected symptoms.

Alternative None
Courses:

Exceptions: None.

Use Case ID: UC-11

Use Appointment
Case
Name:
Actors Doctors

This use case describes how the patient book appointment.

Preconditions The Patient must be logged in.

Post
conditions: The Allocation must be Saved correctly.

This use case starts when the Patient wishes to request for appointment
1. Patient will open the doctors form and click on appointment
Normal button
Course:
2. Patient fill the appointment form according to
requirements and submit it
3. If doctor approves the request then appointment will confirm

Table 2.12

Use Case Scenario 12

Use Case ID: UC-12

Use Case Treatment history
Name:
Actors Patient
Description: This use case describes how a Patient want to view his patient treatment
history

Preconditions Patient is identified and authenticated.

Post The registration must be done correctly.
conditions:
 This use case starts when the Patient wishes to add patient treatment
Normal Course
history

Patient will open the profile and click on treatment form will open
and patient will see his treatment history

Table 2.13

Use Case Scenario 13

 Use Case ID: UC-13
Use Case Give Feedback
Name:

Actors: Patient
Description: is use case describes how the Patient give feedback
Preconditions: The Patient must be logged in. Patient must be already
registered
Post The Allocation must be Saved correctly.
conditions:
This use case starts when the Patient wishes to give the feedback
Normal
Course: 1. Patient will click on the feedback link. Feedback form will open.

2.Patient will add feedback in the form and then submit it

Table 2.14

2.3 Functional Requirements

Admin
 Admin is a person or organization who has complete control over the system.
 Admin Can add doctor
 Admin can diseases with related symptoms and initial medication related to
particular disease.
 Admin Can view update and delete doctor details.
 Admin Can view update and delete patient personal information, medication details.
View feedback)

Doctor

 System allows doctor to add symptoms to diagnoses the disease.

 System suggests what kind of medication initially used for particular disease.
 System allows doctor to see his appointments.
  System allows doctor to see medication details off the patient.
 System allows doctor to edit update delete the history of patient.
 View feedback.

Patient
 System allows patient to add symptoms to diagnoses the disease.

 System suggests medication for common diseases.

 System suggests the doctor with contact details.
 Allow user to get appointment from doctor.
 Patient can view his medical details.
 Can give feedback about doctor or services provide by the organization
2.4 Non-Functional Requirements
 Software will run even with a low-bandwidth Internet connection,

such as a phone line.

 High security standards are crucial. Any kind of data disclosure or manipulation must be
prevented. SSL is the best choice, being supported by common browsers.
 Privacy. The server is responsible for not revealing any information to any symptoms
that the user is not allowed to see.
Reliability
 The system has to be working 24 hours a day, 7 days a week. There is no place for
an extended downtime.
 In case of a failure that leads to a system outrage, the MTTR (Mean Time to
Repair) should not be more than 2 hours.
Supportability
 The all system should be supportable by every browser. All the systems as well
as desktop computers, laptop, all kind of android phones and smart phones.
System Requirements
 There needs to be clearly defined roles of the users. These roles are 'User (Auctioneer and
Bidder)’ and 'administrator'. Each person that goes to the system's website will be
required to register if they want to do more than just read / browse site content.
 A secure server will be required to ensure confidentiality of user treatment history and
personal details
  Because of the different roles, passwords and user accounts must be implemented
properly. It should be difficult to gain access to the site in an illegal manner.
Usability
 The user interface of the system should be very user friendly that User can easily
browse the products and find the product of his choice and make order on it.
 It should not take more than 120 seconds for a new user to register
for an account.
Efficiency
 Any page of the application should not take more than 6 seconds to
load.
 The system may be throttled or slowed down on heavy loads to ensure service for
everybody. By throttling is meant that certain functionality may be unavailable during heavy
server load.
 The application should be able to support 100 concurrent users without any performance
degradation.
Portability
 The system should be portable to various operating environments.
 The current hosting become too restricting for the system, the system must be
portable enough to be moved over to a new server with minimal downtime.

Design Constraints
 PHP web technologies should be used for development of the website.
 XAMPP Web-Server should be used to deploy the application.
 MySQL should be used as the database.

Standards Constraints
 All the documents delivered should adhere to the IEEE standards for
software engineering.

Maintainability
 The system should be developed in such a way that changes can be made easily,
whether for bug fixes or to add new functionality.
 The system should be easy enough to maintain that someone else could do it with
a manual and a few hours training.
3.1 Design

Chapter # 3
Design and
Architecture
Approach
A design approach is a general philosophy that may or may not include a guide for specific
methods. Some are to guide the overall goal of the design. Other approaches are to guide the
tendencies of the designer. A combination of approaches may be used if they don’t conflict.
Function Oriented Design Approach:

Function Oriented Design Approach is partitioning of a design into subsystems and modules,
with each one handling one or more functions.

This web project uses function-oriented design approach. Every module and sub modules are
made, based on their functionality. These modules are designed and implemented separately and
then they are integrated together to form the desired application.

3.1System Architecture

User User Interface

Symptoms
Interface

Interface Engine Knowledgebase

of symptoms

Figure 3.1 Architecture

3.4 Data Representation [DFD]

3.1 DFD level 0

Database of
symptoms
Figure 3.3 DFD Level 0
DFD level 1

System

Figure 3.4 DFD level 1

3.5 Sequence Diagram
3.5.1 Admin Sequence Diagram

Login Login Credentials

Admin Database
Logged in Credential

Manage Symptoms
Managed Add Symptom

Manage Accounts Data Added Update Doctor Data Updated Delete Doctor
Data Deleted
 Add patient
Data Added
Update Patient
Data Updated
Exit Request

Figure 3.5 Sequence

diagram
 3.5.2 Doctor Sequence Diagram

Login Login Credentials

Logged in Credentials

Doctor System Database

Manage Database Add
Disease

Data added

Managed Data Deleted Delete disease

Diagnose Disease Select

Symptoms

Selected

Confirm Symptoms

Diagnose Complete

Manage Patient Appointment Requesst

Received Accept Request

Accepted

Treatment details Exit

Figure 3.6 sequence diagram

3.5.3 Patient Sequence Diagram

Patient System

41

Logn Login
Credentials
Figure 3.7 sequence diagram

42
 Chapter # 4

Implementation

43
4.1 Language, Tools and Technologies Used:

4.1.1 PHP:
 PHP is a very popular programming language developed by
Rasmus Lerdorf in 1994. Developed long after C and C++, PHP
incorporates many of the powerful features of those powerful
languages while addressing some of their drawbacks. Still,
programming languages are only as powerful as their libraries.
These libraries exist to help developers build applications. Some of
the PHP important core features are:

 It is easy to learn and understand.

 It’s designed to be platform-independent and secure.

 Web development relies heavily on these PHP fundamentals. The

PHP includes many standard HTML and CSS libraries (graphics
libraries, networking libraries and everything else you could want)
as well as special PHP libraries that will help you develop
awesome Web applications.

 Platform Independence Importance

4.1.2 Web Development Tools:

 Sublime PHP editor

 Xamp Server

 MySQL

Web development Tools and Xamp server:

Web provides different development environments to develop new
applications. The Web Developer Tools are based on the Application
requirements. WDT is a set of components (Plugins), which extend the
Web development capabilities. Google also supports a Server called Xamp
for creating Database for Web applications.

44
Both Sublime and Xamp contain all required functionality to create,
compile, debug and deploy Web applications. They also allow the developer
to create and start web application for testing. Both tools provide specialized
editors for Web specific files. Most of Web configuration files are based on.
PHP, Java script. In this case these editors allow you to switch between the
representation of the file and a structured user interface for entering the data.

4.2 User Interface

 Main Page Interface

Figure 4.1 Admin login id and

password

45
Figure 4.2 Registration page

46
 Figure 4.3 Admin panel
(main page)
Admin Control

Figure 4.4 Add new disease

47
Figure 4.5 Add new doctor

48
Figure 4.6 patient Information

49
Figure 4.7 Doctor Panel (main page)

50
Doctors Control

Figure 4.8Disease Information

51
Figure 4.9Treatment history

52
Patient Controls

Figure 4.10Patient panel (main page)

53
Figure 4.11 Disease Diagnose details

54
55
Figure 4.12Database View

56
Chapter # 5
Testing and
Evaluation

57
 5.1 Manual Testing

5.1.1 System testing

Once the system has been successfully developed, testing has to be

performed to ensure that the system working as intended. This is also to
check that the system meets the requirements stated earlier. Besides that,
system testing will help in finding the errors that may be hidden from the
user. There are few types of testing which includes the unit testing,
functional testing and integration testing. The testing must be completed
before it is being deploy for user to use.

5.1.2 Unit Testing

 Unit Testing 1:

 Testing Objective: To ensure the login form is working correctly

No. Test case/Test script Attribute and Expected result Result

value

1. Verify user with correct Username: Successfully log into Pass

credential Admin the main page of the
Password: system as FYP
123456 Committee member.

2. Verify with incorrect User name: Incorrect username Pass

password Ahmed or password error
Password: generated

58
 123
3. Verify user with correct User name: Successfully log into Pass
credential Ali the main page of the
Password: system as FYP
123456 Committee member.

4. Verify user with correct User name: Successfully log into Pass
credential john the main page of the
Password: system as FYP
123456 Committee member.
6. Verify with incorrect User name: Incorrect username or Pass
password usama password error
Password: generated
1234

Figure 5.1 Unit Testing

 Unit Testing 2: Creating Profile

 Testing Objective: To ensure the creating profile

form is working properly.

No. Test case/Test script Attribute Expected result Result

and value
1. Creating profile with Name All fields are filled Pass
filling all necessary fields Email
Password
Phone
Address

59
2. Creating profile with Error in that field Pass
name missing
Email
Password
Phone
Address
3. Creating profile with Name Error in that field Pass
Email missing Password Email
Phone
Address

Figure 5.2 Unit Testing

5.2 Functional Testing

The functional testing will take place after the unit testing. In this
functional testing, the functionality of each of the module is tested. This is
to ensure that the system produced meets the specifications and
requirements.

 Functional Testing 1: Login with different roles

 Objective: To ensure that the correct page with the

correct navigation bar is loaded.

No. Test case/Test script Attribute and Expected result Result

value

1. Login as a Admin Username: Main page for the Pass

Admin Admin is loaded with
Password: the Admin
123456 navigation bar

60
2. Login as a Doctor Username: Main page for the Pass
john Doctor is loaded with
Password: the Doctor
123456 navigation bar

3. Login as a Patient Username: Main page for the Pass

Ali Doctor is loaded with
Password: the Patient
123456 navigation bar

4. Admin can diagnose Click on Diagnose Admin will be able to Pass

disease Now select symptoms to
diagnose disease

5. Admin can Add or Click on Disease Admin will be able to Pass

delete disease select add or delete
disease

6. Doctor can accept Dashboard Doctor will be able to Pass

appointment request and accept appointment
add treatment history request and add
treatment history

61
7. Doctor can diagnose Click on Diagnose Doctor will be able to Pass
disease Now select symptoms to
diagnose disease

8. Patient can diagnose Click on Diagnose Patient will be able to Pass

disease Now select symptoms to
diagnose disease

9. Patient can get Click on doctor Patient will be able to Pass

appointment get appointment

10. Patient can give Click on Feedback Patient will be able to Pass
feedback give appointments

Figure 5.3 Functional Testing

5.3 Integration Testing

No. Test case/Test script Attribute and Expected result Result
value

62
1. Login as Admin Username: Login successful Pass
Admin and the Admin
Password: page with its
123456 navigation bar is
loaded and in the
view profile page

2. Upload Doctor and - File successfully Pass

Patient record for Project uploaded and return
to the upload page.
Doctor and Patient
records are updated.

3. View supervising - The list of Pass

Doctor and Patient supervisees shown
on the screen.

Figure 5.4 Integrating Testing

63
64
 Chapter # 6
Conclusion and
Future Work

65
6.1 Conclusion

There are a lot of tools which try to reduce the risk of error apparition in
medical life. Diagnosis has a very important role here. This disease
diagnosis system is an expert system which is used for simplifying the task
of doctors. It is a system that checks a patient at initial level and suggests
the possible diseases. It starts with asking about symptoms to the patient,
then it provide the name and the corresponding medical prescription. This
system not only simplifies task of the doctors but also helps the patients by
providing initial medicines for small diseases in emergency. By using this
system, we can save valuable time

 I learned a lot by doing this project.

 Languages used: PHP, HTML

 Database: MySQL

So, during this project I learned all the above things. Before this project, I
had idea about PHP and HTML for making application. Although I had
knowledge of other languages before. But now I learned a lot about PHP
and got knowledge for developing application.

If I talk about the project, an expert system in medical diagnosis has

reduced lot of hectic work. It has made Diagnosis process very easy with
no time and place restrictions.

6.2 Future Work

In Pakistan there is no as such website available to diagnose disease. So
basically, this project is imitative first step towards the modern era. This
project is at initial level maybe use by a clinical doctor. But in future I
have a plan to execute and that is to develop this on or large scale as many
as hospitals uses the services of this site and provide facility to the
patients. In future modifications this site is continue to make it more
efficient effective and easily understandable

66
 References

References to any book, journal paper or website should properly be

acknowledged. Please consistently follow the style. The following are few
examples of different resources i.e. journal article, book, and website.

 Article: “SMART HEALTH CONSULTING” Author: R. YUVARAJ.

Article: “SMART HEALTH MANAGEMENT SYSTEM USIN DATA

MINING” Author: SAYYID ABRAR

67
68