BUBT Demo Report

Android Application “PSDV System in BD”
DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING
BANGLADESH UNIVERSITY OF BUSINESS AND TECHNOLOGY

(BUBT) DHAKA-1216
November 20, 2019

ii
Android Application “PSDV System in BD”
A Project Report
Submitted by
Name ID
Md. Nayan Sarder 15161203060

Rashed Khan Arif 15161203089
Shaikh Rubayat Hossen 15161203081
A Project
Submitted to the Department of Computer Science and Engineering

Bangladesh University of Business and Technology (BUBT). Dhaka
in Partial fulfillment of the requirements for the degree
Of
BACHELOR OF SCIENCE
IN
COMPUTER SCIENCE AND ENGINEERING
November 20, 2019

ABSTRACT
This is an android based application for reducing antibiotic resistance and identifying
fake doctor in Bangladesh. In Bangladesh, huge people are take general medication from
drug seller shop and They people are give illegally antibiotic medicine without prescrip-
tion. But the problem is they don’t give full dosage of antibiotic medicine. Also, patient
not complete full dosage of antibiotic. When patient not complete antibiotic medicine
dosages he will probably attack in antibiotic resistance. So we made this system to make
awareness about antibiotic resistance issues and preventing pharmacy guy’s to give an-
tibiotic medicine without prescription. Through the use of mobile technologies. User get
information about antibiotic resistance and antibiotic medicine. So that user can easily
understand about antibiotic resistance. Moreover, the system can help user to prevent
the antibiotic resistance problem in Bangladesh.
The another core feature of our system is here user can verify a doctor easily. If a user
want to know is his doctor is fake or not. Then he can verify this doctor to use our
system. Also, a user can get free medication from an authorized doctor. In our country
Bangladesh there are too much problem in fake doctor. Our system can also identify
fake doctor easily by using doctor verification feature. Using the system a user can easily
identify a fake doctor. If doctor is fake then user can complain about the doctor to proper
authority.
i
DECLARATION
We hereby declare that the project entitled “Prevent Superbug and Doctor Verification
(PSDV) System in BD” submitted for the degree of Bachelor of Science Engineering in
Computer Science and Engineering in the faculty of Computer Science and Engineering
of Bangladesh University of Business and Technology (BUBT), is our original work and
that it contains no material which has been accepted for the award to the candidates of
any other degree or diploma,except where due reference is made in the next of the project
to the best of our knowledge, it contains no materials previously published or written by
any other person except where due reference is made in this project.
————————— ————————– —————————–

Md. Nayan Sarder Rashed Khan Arif Shaikh Rubayat Hossen
ID: 15161203060 ID: 15151203089 ID: 15161203081
Intake: 22 Intake: 22 Intake: 22
Section: 02 Section: 02 Section: 02
ii
CERTIFICATE
TO WHOM IT MAY CONCERN
This is to certify that this project “Prevent Superbug and Doctor Verification (PSDV)
System in BD” report submitted by Md. Nayan Sarder, Rashed Khan Arif and Shaikh
Rubayat Hossen students of Department of Computer Science and Engineering, Bangladesh
University of Business and Technology(BUBT), under the supervision of M.M. Fazle
Rabbi, Assistant Professor, Department of Computer Science and Engineering has been
accepted as satisfactory for the partial requirements for the degree of Bachelor of Science
Engineering in Computer Science and Engineering.
———————————
(Project Supervisor)
M. M Fazle Rabbi
Assistant Professor
Department of Computer Science and Engineering(CSE)
Bangladesh University of Business and Technology(BUBT)
———————————-
Chairman
Prof. Dr. M. Ameer Ali
Department of Computer Science and Engineering (CSE)
iii
DEDICATION
Dedicated to our Parents for their love and inspiration
iv
ACKNOWLEDGEMENT
First of all, we want to thank our Allah Almighty and then we are thankful to our parents
who supported me in this whole study and always pray for our success and good health.
We would like to express our sincere gratitude and profound indebtedness to my super-
visor M. M. Fazle Rabbi for his guidance, valuable suggestions, commendable support
and endless patience towards the completion of this project. We feel very proud to have
worked with him. Without the inspiring enthusiasm and encouragement of our supervi-
sor, this work could not have been completed.
We thank all the staffs and graduate students at Bangladesh University of Business and
Technology (BUBT) and all the friends for their support and encouragement. We would
also like to extend our elder and younger brothers.
Finally, I wish to express my gratitude to Bangladesh University of Business and Tech-

nology (BUBT) for providing an excellent environment for research and all the other
facilities to complete the project successfully.
With Best Regards,

PSDV Team
v
APPROVAL
The Project Designing and Implementation of “Prevent Superbug and Doctor Verifica-
tion (PSDV) System in BD” report is submitted by Md. Nayan Sarder ID-15161203060,
Rashed Khan Arif ID-15161203089, Shaikh Rubayat Hossen ID-15161203081 Department
of Computer Science and Engineering, Bangladesh University of Business and Technology
under the supervision of M. M. Fazle Rabbi, Assistant Professor, Department of Com-
puter Science and Engineering has been accepted as satisfactory for the partial fulfillment
of the requirements for degree of Bachelor of Science (B.Sc.Engg.) in Computer Science
and Engineering and approved as to its style and contents.
Approved
————————
Supervisor
M. M. Fazle Rabbi
Assistant Professor
Department of Computer Science and Engineering(CSE)
————————
Chairman
Prof. Dr. M. Ameer Ali
Department of Computer Science and Engineering (CSE)
vi
vii
©
Copyright by Md. Nayan Sarder (ID: 15161203060), Rashed Khan Arif (ID:
15161203089) and Shaikh Rubayat Hossen(ID: 15161203081)
All Right Reserved

Contents
Abstract i
Declaration ii
Certificate iii
Dedication iv
Acknowledgement v
Aproval vi
List of Figures xii
List of Tables xiv
1 Introduction 1
1.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.2 Existing System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.3 Problem of Existing System . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.3.1 Difficulties in Doctor verification . . . . . . . . . . . . . . . . . . 3
1.3.2 Difficulties of Superbug and Complain . . . . . . . . . . . . . . . 3
1.3.3 Difficulties to get doctor mentorship . . . . . . . . . . . . . . . . 4
1.4 Motivations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.5 Project Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.6 Contribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.6.1 Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.6.2 Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
viii
CONTENTS ix
1.6.3 Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.7 Organization of Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.8 Conclusions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2 Literature Review 9
2.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.2 Existing System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.2.1 DIMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.2.2 BMDC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.2.3 Doctorola . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.2.4 Patient Aid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.2.5 Pulse Healthcare Services . . . . . . . . . . . . . . . . . . . . . . 21
2.3 Supporting Theory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.3.1 Used Technology . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.3.2 Java . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.3.3 XML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.3.4 MySQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
2.3.5 SQLite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
2.3.6 JSON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
2.3.7 Retrofit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2.4 Entity Relationship Diagram (E-R Diagram) . . . . . . . . . . . . . . . . 28
2.4.1 General Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
2.5 Data Flow Diagram (DFD) . . . . . . . . . . . . . . . . . . . . . . . . . 35
2.6 Use Case Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
2.7 Conclusions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
3 Proposed System 40
3.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
3.2 Feasibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
3.2.1 Objective of Feasibility Study . . . . . . . . . . . . . . . . . . . . 42
3.2.2 Technical Feasibility . . . . . . . . . . . . . . . . . . . . . . . . . 42
3.2.3 Operational Feasibility . . . . . . . . . . . . . . . . . . . . . . . . 43
3.2.4 Schedule Feasibility . . . . . . . . . . . . . . . . . . . . . . . . . . 44
CONTENTS x
3.2.5 Financial Feasibility . . . . . . . . . . . . . . . . . . . . . . . . . 44

3.3 Methodology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
3.3.1 Use of Agile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
3.3.2 Exploration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
3.3.3 Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
3.3.4 Iteration to the first release . . . . . . . . . . . . . . . . . . . . . 47
3.3.5 Productionizing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
3.3.6 Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
3.3.7 Track Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
3.4 System Requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
3.4.1 Functional Requirement . . . . . . . . . . . . . . . . . . . . . . . 49
3.4.2 Non Functional Requirement . . . . . . . . . . . . . . . . . . . . . 50
3.5 Entity Relationship Diagram (E-R diagram) . . . . . . . . . . . . . . . . 51
3.6 Data Flow Diagram (DFD) . . . . . . . . . . . . . . . . . . . . . . . . . 52
3.7 Use Case Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
3.8 Database Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
3.9 Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
3.10 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
3.11 Result Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
3.12 Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
3.13 Conclusions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
4 User Manual 68
4.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
4.2 System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
4.2.1 Developer Requirements . . . . . . . . . . . . . . . . . . . . . . . 69
4.2.2 Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . 69
4.2.3 Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . 70
4.2.4 User Requirements for Using PSDV System . . . . . . . . . . . . 71
4.3 User Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
4.3.1 Dashboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
4.3.2 Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
4.3.3 Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
CONTENTS xi
4.3.4 Complain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
4.3.5 Complain View Page . . . . . . . . . . . . . . . . . . . . . . . . . 76
4.3.6 Antibiotic List . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
4.3.7 Antibiotic Medicine Item Details . . . . . . . . . . . . . . . . . . 78
4.3.8 Mentorship Page . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
4.3.9 Doctor Verification Page . . . . . . . . . . . . . . . . . . . . . . . 80
4.3.10 Doctor Confirmation Message Page . . . . . . . . . . . . . . . . . 81
4.3.11 Article Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
4.3.12 Article Add Page . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
4.3.13 Superbug Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
4.3.14 Superbug News List Page . . . . . . . . . . . . . . . . . . . . . . 85
4.3.15 User Information . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
4.4 Conclusions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
5 Conclutions 88
5.1 Conclusions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
5.2 Future Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
References 90
Appendices 95
A Objective Of Java 96
B XAMPP Control Panel 97

List of Figures
2.1 DIMS App . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

2.2 BMDC system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.3 Doctorola Web App . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2.4 Doctorola Android App . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.5 Patient Aid Android App . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.6 Pulse Healthcare Services Android App . . . . . . . . . . . . . . . . . . . 23
2.7 Server Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
2.8 Entity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
2.9 Week Entity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
2.10 Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
2.11 Multi valued attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
2.12 Relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
2.13 One to One . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
2.14 One to Many . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
2.15 Many to One . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
2.16 Many to Many . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
2.17 E-R Diagram of Blog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
2.18 Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
2.19 Data Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
2.20 Data Store . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
2.21 Online Shopping DFD . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
2.22 Use Case Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
3.1 The Agile Development Methodologies . . . . . . . . . . . . . . . . . . . 47

3.2 E-R Diagram for PSDV System . . . . . . . . . . . . . . . . . . . . . . . 52
xii
LIST OF FIGURES xiii
3.3 Context Diagram of PSDV System . . . . . . . . . . . . . . . . . . . . . 53

3.4 One Level DFD Diagram of PSDV System . . . . . . . . . . . . . . . . . 54
3.5 Use Case Diagram of PSDV System . . . . . . . . . . . . . . . . . . . . . 56
3.6 Dashboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
3.7 Complain about pharmacy . . . . . . . . . . . . . . . . . . . . . . . . . . 65
3.8 Doctor Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
4.1 Dashboard of PSDV System . . . . . . . . . . . . . . . . . . . . . . . . . 73

4.2 Signup Page of PSDV System . . . . . . . . . . . . . . . . . . . . . . . . 74
4.3 Login page of PSDV System . . . . . . . . . . . . . . . . . . . . . . . . . 75
4.4 Complain Page of PSDV System . . . . . . . . . . . . . . . . . . . . . . . 76
4.5 Complain View Page of PSDV System . . . . . . . . . . . . . . . . . . . 77
4.6 Antibiotic Medicine List Page of PSDV System . . . . . . . . . . . . . . 78
4.7 Antibiotic Medicine Details Page of PSDV System . . . . . . . . . . . . . 79
4.8 Mentorship Page of PSDV System . . . . . . . . . . . . . . . . . . . . . . 80
4.9 Doctor Verification Page of PSDV System . . . . . . . . . . . . . . . . . 81
4.10 Doctor Confirmation Message Page of PSDV System . . . . . . . . . . . 82
4.11 Article Page of PSDV Syste . . . . . . . . . . . . . . . . . . . . . . . . . 83
4.12 Article Add Page of PSDV System . . . . . . . . . . . . . . . . . . . . . 84
4.13 Superbug Page of PSDV System . . . . . . . . . . . . . . . . . . . . . . . 85
4.14 Superbug News List Page of PSDV System . . . . . . . . . . . . . . . . . 86
4.15 User Information page of PSDV System . . . . . . . . . . . . . . . . . . . 87
A.1 Objective of Java . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
B.1 XAMPP Control Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

List of Tables
3.1 Complain Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

3.2 Medicine List Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
3.3 User Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
3.4 User Role Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
3.5 Doctor Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
3.6 Article Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
3.7 Mentorship Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
3.8 Superbug Details Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
3.9 Medicine Company Table . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
4.1 Desktop Specification for Android Studio . . . . . . . . . . . . . . . . . . 69

4.2 Mobile Specification for Test App . . . . . . . . . . . . . . . . . . . . . . 70
4.3 Mobile Specification for Use PSDV System . . . . . . . . . . . . . . . . . 72
xiv
Chapter 1
Introduction
1.1 Introduction
The “Prevent Superbug and Doctor Verification (PSDV)” is a system sets up for superbug
related document, antibiotic list, complain that a user can easily know about antibiotic
medicine in mother language. Also a user can complain with doctor to the government or
government authorized authority. Prevent superbug can help all kind of people how don’t
have any medical knowledge even first-aid knowledge. It can help awareness about su-
perbug, Antibiotic dosages. Also a user can help or mentorship from a doctor for his/her
general problem. Another important feature is doctor verification. Using this feature a
user can verify a doctor is this this doctor is real or fake. There various facility provided
so that the user and doctor both get well facility from this system. The government can
reduce superbug problem in Bangladesh using this service system. For different kind of
perspective, we motivate to build this system. We motivate form the virtual medical
service system. [1]
With the rapid development of information technology, Android application has been
increasing in recent years. The advantage of the Android application
– Mobile application is convenient to carry.
– Global partnerships and large install base.
– Powerful development framework.
1
CHAPTER 1. INTRODUCTION 2
– Open marketplace for distributing apps.
– Open source and Any Android user can use it without any cost.
Based on the advantages of both applications, we motivated to develop an android ap-

plication.
“Prevent Superbug and Doctor Verification (PSDV)” System can help all type of people
to known about Superbug problem and why Superbug grow. Using “Prevent Superbug”
System all people can help to reduce superbug problem in Bangladesh. A user can also
verify a doctor that is this doctor is real or fake doctor. Now a day many fake doctor
is arrested in police. But there is no system in Bangladesh to verify a doctor. So we
propose a sub system to verify a doctor using BMDC services in Bangladesh. Also a user
can get mentorship from well-known doctor using our system. [2]
“Prevent Superbug and Doctor Verification (PSDV)” Application is the key to solve the
problem. Using this application, the user or people in Bangladesh need not go to the
police or anywhere to verify a doctor and to know about antibiotic doges, work, group. [2]
“Prevent Superbug and Doctor Verification (PSDV)” system I am proposing here, greatly
simplifies the superbug problem to reduce superbug problem, Doctor verification, Doctor
mentorship, Pharmacy problem in Bangladesh. The System has two moods one is User/
General User and Another one is Doctor mode. A doctor can login here and can give
mentorship to all general user also can add an antibiotic group and medicine, can help
to general user for first aid and general medication. [4]
1.2 Existing System

Under manual system, if a person wants to know about superbug or want to know about
details of an antibiotic medicine. User need to search on Internet then search a suit-
able detail to know about it. But it is time consuming and sometimes the user not
get the perfect result. Also, when a user wants to complain pharmacy user need to go
police or authorized authority to do this. So all above system user done by manually. [42]
The project works is aimed for developing an efficient application to solve superbug re-
lated problem in Bangladesh. In Bangladesh there is no system exist to reduce superbug
problem. But there is a system available for doctor verification that provided by BMDC
(Bangladesh Medical and Dental Council). Also, there are many systems available for
mentorship and doctor medication. But for doctor verification use traditional method in
our country. By using the traditional method, it arises lot of fraud doctor in our country
and this issue is a great impact in health of Bangladeshis people. Thus, this project is to
purpose of a suitable doctor verification system. [52]
1.3 Problem of Existing System

As describe above there is no existing system to reduce superbug problem in Bangladesh.
But for doctor verification and get doctor medication there is some system available.
1.3.1 Difficulties in Doctor verification
In Bangladesh there is only one system available for doctor verification. The system
name is BMDC (Bangladesh Medical Dental Council) provide doctor verification system
by using doctor registration number that provided from BMDC. The main problem is
this system is a doctor get registration number from BMDC is manually and tradition
wise. Also, the BMDC only have a website there is no mobile application available. So
we propose the system to reduce this kind of problem and make and efficient doctor
verification system. [43]
1.3.2 Difficulties of Superbug and Complain
In the existing system, a user can’t not easily know about antibiotic resistance problem.
The problem is too much increase day by day. But in existing system the user can’t
know about superbug. For knowing about superbug some time news paper are help
to write a column about superbug. But our prposed system can help to easily known
about superbg and antibiotic. After awareness all user can complian about pharmacy. In
existing system less than people are complain about pharmacy. For complain they need
to go to the authority and this is a big problem of existing system.
1.3.3 Difficulties to get doctor mentorship
In existing system, mentorship is a biggest problem. There is no suitable way to get men-
torship from authorized doctor. It’s also difficult for doctor to get mentorship medication
to patient according to their problem. In our system we try to reduce the problem by
requesting medication and mentorship to doctor by using request mentorship. [52]
1.4 Motivations
The motivation for designing this application came because I see the use of antibiotic
without any authorized prescription and people they cannot complete their course of
antibiotic medicine [7]. Also, the fraud doctor in Bangladesh [54]. There are too many
fraud doctor in Bangladesh and there is no way to get mentorship from authorized doctor
[53]. According to the problem we motivate to build this system. Moreover, I am recent
learning about the Java and JSP Programming languages as well as seeing how powerful
and dynamic they are when it comes to web designing and applications. The languages
used to build this application are Java, XML, Spring Boot and MySQL at I found them
to be extremely useful while working on the technologies. [48]
1. We want to reduce superbug problem in Bangladesh.
2. I personally do not like to eat any kind of medicine without any prescription, So
our goal is to awareness all kind people to do this.
3. We know pharmacist in Bangladesh are given antibiotic medicine for simple health
issues. So trying to reduce this by using complain system about pharmacy.
4. People can now get health related mentorship form authorized doctor easily and
also can learn about superbug and antibiotic medicine.
So, we make an app that people can reduce superbug, general health issues and can verify
a doctor by using our system. [5]
1.5 Project Objectives

The following project objectives are:
1. To develop an online system to reduce superbug problem in Bangladesh.
2. To develop use interface for superbug problem reduce by using online system.
3. To provide online doctor verification system.
4. To get online medication and mentorship from authorized doctor.
5. Get better health prescription from authorized doctor.
6. Reduce antibiotic medicine sell without any authorized prescription.
7. Increase people health safe.
Specific objective:
1. Access this system by role wise.
2. Maximize effectiveness record of health data of patient and reduce superbug related
problem.
1.6 Contribution
After the system was successfully developed, it will bring lots of convenience to the
user and doctor when they know about antibiotic resistance, antibiotic medicine details,
dosages. Then they all try to reduce the superbug through the application. Also a user
can verify a doctor easily through this application. [35]
1.6.1 Analysis
For developing the system we first analysis to existing system and manual system. Also,
analysis the positive and negative site of this application. After details analysis for this
system Prevent Superbug and Doctor Verification (PSDV) we design this application.
[35]
1.6.2 Design
After analysis we design this application. In designing section select which module need
for this system. After selecting the module we design all module. We choose android based
system, because nowadays every people have use smart phone. So we design our system
for operating system based mobile. Then we design all module for mobile application.
[35]
1.6.3 Implementation
After designing all module. Then start to build this application. The designing module
are implement here. [35]
1. Login Page
Login page has two modes such as seller mode and buyer mode. All user’s must
give their user id and password for login to complain about a pharmacy and get
mentorship.
2. Dashboard
Here user can see all item such as complain view, verification item, mentorship item
user info, Antibiotic item and about application.
3. Login as Doctor Role

A doctor can Login as Doctor role. If login with doctor role then some features will
be active for doctor like mentorship adding, antibiotic adding give antibiotic details
and many more.
4. Complain Page
Using this page a user can complain about a pharmacy. User provide all details
about pharmacy and proved image like purchasing invoice.
5. Antibiotic Page
Here user find all antibiotic list and when click a list user can view all details about
this antibiotic.
6. Mentorship
Using mentorship user can get mentorship of medication from authorized doctor.
Also, user can request for a medication.
7. Doctor Verification
Useing this service user can verify a doctor easily by providing there registration
number or full details. So user can detect fraud doctor easily.
8. Article
Here user get different types of article like superbug related article, mentorship
related article, suggetion, antibiotic related article and many more.
9. Superbug
Here user can know about superbug.
10. User Info

User can his information from here.
1.7 Organization of Report

In second chapter, introduces existing system, existing/supporting literature, analysis of
existing system. It helps to identify problem that occurred in existing system. Besides
that, it also helps to identify the best approach to achieve the project goal based on the
study.
In third chapter, proposed system introduces feasibility study, requirement analysis, sys-
tem design, data model, DFD, ER diagram, Use Case diagram, system tools, project
planning, implementation, features and result analysis.
In fourth chapter, we give server requirement, client requirement and user manual which
covered the functionalities provided by this project.
Finally, Fifth Chapter, we introduce conclusion and prospective future scopes.
1.8 Conclusions
This chapter will be discussing about the difficulties issues come together with the tra-
ditional approach for doctor verification system. In addition, it also mentions that those
people who will be facing the problem. Lastly, the project objective and project scope
have been listed and discussed. The overall structure of the proposed system has been
justified and project contribution is stated. Next, will be further discussing about the
concept of existing system that help to reduce health related problem in Bangladesh.
Chapter 2
Literature Review
2.1 Introduction
This chapter discuss on the literature review and background study of the project. Litera-
ture review is important to achieve successful system because it helps to identify problem
that occurred in existing system. Besides that, it also helps to identify the best approach
to achieve the project goal based on the study. By defining, analyzing, and redesigning an
organization’s resources and operations, workflow management systems ensure that the
right information reaches the right person or computer application at the right time. A
medical services system is referred to as a set of detail methods that is being used in han-
dling the system. Doctor verification are manually and we try to make it online system. []
Those helps the people or user to get knowledge about superbug, antibiotic medicine,
verify doctor. The book includes a chapter of case studies, review exercises, and a glossary.
A special Web site developed by the authors, features animation, interactive examples,
lecture materials, exercises and solutions, relevant links, and other valuable resources for
the classroom. This chapter focuses on the study of portal usability and comparison
of existing system. The prevention of superbug and doctor verify can be defined as
a computerized system that is being used by general people to get better health, can
reduce superbug problem, know about antibiotic and many more by using computerized
system. []
9
CHAPTER 2. LITERATURE REVIEW 10
2.2 Existing System

The related works and the theory literature are detailed below. There is no other available
computerized system to reduce superbug problem in Bangladesh.
2.2.1 DIMS
Evolution is the matter of the fittest. Evolution happens when the need to look for
a solution for the existing problem. The solution for the problems faced by the man-
ual system is nothing but have huge time processing and problems the online system
can reduce this. This prevent superbug and doctor verification system app helps the user
to maintain a better health without unauthorized antibiotic and detect fraud doctor. [47]
The DIMS (Drug Information Management System) is an existing system for known
about all type of medicine and drugs details in Bangladesh. DIMS (Drug Information
Management System) is the premier mobile drug index apps of Bangladesh for instant
clinical drug information references. It is developed by ”ITmedicus”. DIMS is the most
comprehensive, advanced and up-to-date information source on available and recent drug
products to serve the healthcare pharmaceutical professionals in the country. [47]
DIMS (Drug Information Management System) gives all type of medicine details in
Bangladesh but not specific antibiotic detail. It gives all details. Also this app has
awesome searching system to find any medicine details.DIMS offers you a long and de-
tails list of drug and medicine. You will find all details here about any kind of medicine
in Bangladesh. [47]
DIMS (Drug Information Management System) is an mobile drug index apps, to be used
only as a reference aid and educational purpose and is not intended for medical advice,
diagnosis or treatment; neither intended to be a substitute for the exercise of professional
judgment and should not be relied upon solely for final treatment decisions. The clini-
cal information contained in the information is intended as a supplement to, and not a
substitute for, the knowledge, expertise, skill, and judgment of physicians, pharmacists,
nurses, or other healthcare professionals involved in patient care. [47]
The DIMS (Drug Information Management System) reliable authentic data sources and
company literature’s. Although great effort has been made in compiling and checking
the information contained in this apps to ensure that it is accurate, the publisher, the
authors, editors and their servants or agents shall not be responsible or in any way liable
for the continued currency of the information or for any errors, omissions or inaccuracies
in this website whether arising from negligence or otherwise howsoever, or for any conse-
quences arising there from. [47]
Features of DIMS:
• Drugs details (Indications, Dosage administrations, Contraindications, Side ef-

fects, Precautions warnings, FDA pregnancy category, Therapeutic class, Pack
size price).
• Search Drugs (Search by Brand name, Generic name or Condition).
• Drugs by Brands (A-Z brands).
• Drugs by Generics (A-Z generics).
• Drugs by Classes.
• Drugs by Conditions.
• Favourite Drugs (Bookmark any brand names).
• Medical events (Information of international medical events).
• Feedback (Can directly post your valuable suggestion, advice comments).
• Advance search (Can choose different search categories).
We analysis the existing system of DIMS Android App. We notice that it takes more
time to search Antibiotic and a general user can not differ between antibiotic and non-
antibiotic medicine. This app is not user friendly for antibiotic medicine. [47]
Figure 2.1: DIMS App
2.2.2 BMDC
Bangladesh Medical and Dental Council (BMDC) is a register council for doctor in
Bangladesh. Here all doctor are come take registration form and apply for a register
doctor. After Registration BMDC give a registration number. Also, BMDC is an unity
of Doctors and dental services in Bangladesh. BMDC have an authority or member and
post. They maintain the service. Bangladesh Medical and Dental Council also provide
doctor safety. [42]
Bangladesh Medical Council was first formed under Bangladesh Medical Council Act. in
1973. Subsequently the Act. of 1973 was repealed in 1980. Bangladesh Medical and
Dental Council Act. was passed by the Parliament on 09-04-1980 to provide for the
constitution of Bangladesh Medical and Dental Council. This Council has its office only
in Dhaka. The Council is headed by a President who is elected by the members of the
Council from amongst themselves. [42]
Bangladesh Medical and Dental Council (BMDC) is an web based based online services
to verify a doctor. When a user want to verify a doctor user need to go their website and
also the most important need is registration number. But when a user not know a doctor
registration no he can not verify the doctor. Also BMDC provide many more services. [43]
Bangladesh Medical and Dental Council (BMDC) is an existing system for verify a doctor
in Bangladesh. But It’s not mandatory for doctor to take a registration number from
them. If doctor not register on their service then user can not verify him. [43]
Features of BMDC [44]
• It registers doctors to practice in Bangladesh, in order to protect and promote the

health and safety of the public by ensuring proper standards in the practice of
medicine.
• Give Different kind of registration facility like provisional and full time MBBS.
• Verify a doctor using doctor registration number.
• Recognition of Medical and Dental Qualifications granted by Medical and Dental

Institutions in Bangladesh.
• Recognition of Medical and Dental Qualification granted by Institutes outside Bangladesh.
• Setting of scheme of reciprocity with foreign Medical and Dental Councils for recog-
nition of Medical and Dental Qualifications.
• Amendment of Schedules.
• Registration of Medical and Dental Practitioners.
• Registration of Medical Assistants.
• Inspection of Medical and Dental Intuitions.
• Withdrawal of recognition of Medical and Dental Institutions.
• Maintenance of Registers of Medical Dental Practitioners.

• Maintenance of Registers of Medical Assistants.
• Publications of Registered Medical Practitioners.
• Penalty for fraudulent representations of registration.
• Action against use of false title, etc. by registered Medical and Dental Practitioners.
• Removal of names from registers of Medical Dental Practitioners.
• Action against persons not registered under the Act.
• Approval of Journals published by different organisations/ Association.
• The management of the property of the Council and the maintenance and audit of
its accounts.
• Prescribing a uniform minimum standard of courses of training for obtaining grad-

uate and post-graduate medical and dental qualifications to be included or included
respectively in the First, Third and Fifth Schedules.
• Prescribing minimum requirements for the content and duration of courses of study
as aforesaid.
• Prescribing the conditions for admission to courses of training as aforesaid.
• Prescribing minimum qualifications and experience required of teachers for appoint-

ment in medical and dental institutions.
• Prescribing the standards of examinations, methods of conducting the examinations

and other requirements to be satisfied for securing recognition of medical and dental
qualifications under Medical Dental Council Act. 1980.
• Prescribing the qualifications and experience required of examiners for professional

examinations in medicine and dentistry antecedent to the granting of recognised
medical and dental qualifications and Registrations of medical or dental students
at any medical or dental college or school or any University and the fees payable in
respect of such registration.
We analysis the existing system of BMDC Web based services.We notice that it give
more hastel to the user to verify a doctor. A general user don’t know the registration
number then how to verify. So they don’t have any optionl option. This service is not
user friendly for a user.
Figure 2.2: BMDC system
The Council is a supreme body and takes all policy decisions, it meets at least twice in
a year or as and when there are sufficient items for the agenda, which needs policy deci-
sions. It acts through various Committees and office of the Registrar. The meetings of
the Council are presided over by the President and in his absence by the Vice President.
[46]
The Council has an office headed by the Registrar. The Building of the Council is located
at 203, Shaheed Syed Nazrul Islam Sarani, Dhaka-1000. The Registrar is the Chief Ex-
ecutive of the Council and is responsible for all official work including implementation of
the decision of the Council. The Registrar office keeps a close liaison with the Ministry of
Health, Universities, Medical Colleges and allied agencies for speedy implementation and
execution of the decision of the Council. It also keeps a liaison with Council and licensing
bodies in other countries to establish close contacts and develop mutual cooperation and
understanding. [46]
The Standing Recognition Committee Consist of five Members headed by the Chairmen
of the Committee. The Chairman members of the Committee elected from among the
Members of the Council. Function of the Standing Recognition Committee are [45]
1. To Recommend prescribing a uniform minimum standard of courses of training

for obtaining graduate and post-graduate medical and dental qualifications to be
included or included respectively in the First. Third and Fifth Schedules.
2. To Recommend prescribing minimum requirements for the content and duration of

courses of study as aforesaid.
3. To Recommend prescribing the conditions for admission to courses of training as

aforesaid.
4. To Recommend prescribing minimum qualifications and experience required of

teachers for appointment in medical and dental institutions.
5. To Recommend prescribing the standards of examinations, methods of conducting

the examinations and other requirements to be satisfied for securing recognition of
medical and dental qualifications under this Act.
6. To Recommend prescribing the qualifications and experience required of examiners

for professional examinations in medicine and dentistry antecedent to the granting
of recognised medical and dental qualifications.
2.2.3 Doctorola
Doctorola is an android app based medical service in Bangladesh. Doctorola is a dream

that turned into a tech based startup, a business with a great purpose to create positive
impacts in peoples’ lives. It is the first online doctor appointment service platform in
Bangladesh, providing real time doctor information and appointments through a fully
integrated system. Doctorola is missioned to bring convenience in the healthcare service
delivery for the general people in Bangladesh. [40]
Docotrola is an existing system to get medication from doctor easily. But it needs money
to get doctor suggetion from authorized doctor. A doctor can sign up here and give
medication to a patienbt using android app services. This system also provide doctor
appointment services. But there don’t have any doctor verification services [40]
Doctorola aims to drive two very important behavioral changes that can make approach-
ing treatment faster and better. In general, a common person in our country is quite
unwilling to see a proper physician for his or her illness, until it gets too bad. People
try out different suggestions from friends around them or conduct a self treatment based
on other’s experiences. This is mainly due to serious lack of awareness about the signs,
symptoms, consequences of diseases and lack of proper guidance. [41]
Secondly, when people want to approach treatment, they commonly get into the trouble
of finding a right doctor. In most cases, they head to Dhaka or other big cities and ask
their relatives or friends for help. Unfortunately, those relatives or friends typically know
only a few doctor names. Those are generally the busiest doctors who are well known at
the national level. Certainly, taking an appointment of those doctors are quite a hassle.
One may need to wait even two-three months to consult the doctor. [41]
This is again mainly because, there is not enough awareness about the availability of
many qualified doctors across the country who could give attention and treat the patient
earlier than the time he/she will wait for. These result in unnecessary delays aggravating
the condition of the disease. Doctorola through its social network platform and many
other means is continuously engaging to build the awareness among people to help these
improve. [41]
Features of Doctorola [41]
• Search for the right doctor by specialty and location.

• See doctor’s available time slots and click to book instantly.
• Find your doctor’s chamber on the map.
• Get reminded of your appointment prior to the schedule
We analysis the existing system of Doctorola Android App based services.We notice that
it take more time to the user to get a doctor. Also uit’s don’t give any free medication
services.
Doctorola have both web and android system. The below figure of doctorola Web app
screen shoot
Figure 2.3: Doctorola Web App
And The below figure of doctorola Android App screen shoot.

Figure 2.4: Doctorola Android App
2.2.4 Patient Aid
Patient Aid is the first offline and free healthcare delivery app of Bangladesh. [50]
Patient Aid is backed with the most medicine healthcare data source for general public
and patients from the house of ITmedicus. This app is dedicated to help you find complete
detail information about Medicines, Diseases, Health Tips, Doctor Hospital Directory,
Doctor’s Finder, Medicine Reminder, Medicine Cost Calculator and many more. [50]
Features of Patient Aid [50]
• MEDICINE SEARCH
Complete medicine listings with fast search and quick access to a huge medicine
database both in English Bangla. The most comprehensive database of medicine in-
formation available for different medicine brands including the generic name, form,
strength, company and price.
• MEDICINE DETAILS
Provides you with easy language the concise but pertinent information such as Uses,
Side Effects, Warnings on all the common prescribed medicines.
• MEDICINE REMINDER COST CALCULATOR

Give medicine remainder Medicine and price calculator can be very useful to cal-
culate your daily, weekly or monthly expenditure on different medicine costs.
• DOCOTR SELECTOR
This doctor selector feature, this will help to find appropriate doctor for specific
problems.
• CHAMBER DETAILS APPOINTMENT

Find the specialist doctor’s chamber details in your area call instantly for an
appointment.
• DIRECTORY
Find the nearest doctor, hospital, ambulance pharmacy. Gives you quick access to
an extensive healthcare medical database in your pocket.
• HEALTH TIPS
Provides most comprehensive and medically reviewed health awareness tips for
healthy life from authentic medical sources.
Figure 2.5: Patient Aid Android App
2.2.5 Pulse Healthcare Services
Pulse Healthcare services is a virtual telemedicine platform and application offering video
consultation with physicians through fully encrypted video calls on web and smart de-
vices from anytime, anywhere. [49]
• Simply open the application
• Select a doctor
• Choose an available time slot
• Make online payment(consultation fee) to book an appointment.
• Begin secure video consultation and get primary diagnosis
• Receive e-prescription
• Store and share medical records (if required)
The main Features of Pulse Healthcare Services [49]
• Appointment Booking For Online Consultation

User can easily request for an appointment with your preferred doctor/health-care
provider using the appointment scheduling system. Choose a doctor and the pre-
ferred timing, and then once confirmed, appointment reminders will be sent to user
until the time of consultation.
• Online Video Consultation

Consult anytime, anywhere at user convenience using end-to-end encrypted video
consultation service. User can also chat and send medical files tab instantly during
a consultation.
• Instant Diagnosis and E-Prescription

Get Primary Diagnosis and Prescription upon completion of consultation with your
doctor/healthcare provider. This enables user to keep a record of the consultation
for future reference.
• Electronic Medical Record (EMR)

Upload user health records/medical files to the secure server. Any e-prescription
you receive through the app will be stored automatically. User can share these
health records during a consultation with any doctor on the Pulse platform. [49]
Figure 2.6: Pulse Healthcare Services Android App
2.3 Supporting Theory

Our whole system is Mobile based. We have implemented our system by the following
supporting various web technology and tools for both frontend and backend. We have
make our app is an online platform. This paper will explores how the technology and
tools used to make this online platform. [35]
2.3.1 Used Technology
For developing this system used many technology. As we make a android based system.
So we use all android technology to build this system.
2.3.2 Java
Java is a programming language, designed to be concurrent, class-based and object-

oriented, as well as a computing platform first released by Sun Microsystems in 1995.
Java programming Language is advertised and esteemed for its fast performance, security,
and reliability. It’s programming language expressly designed for use in the distributed
environment of the Internet. It was designed to have the like of the C++ programming
language, but it is simpler to use than C++ and enforces an object-oriented programming
model. Java Programming language can be used to create full applications that may run
on a single computer or be distributed among servers and clients in a network. It can
also be used to create basic apps distributed all servers and clients in a network. This
programming language is designed to enable development of portable, high-performance
applications for the widest range of computing platforms possible, hence enabling the
fundamental tenets of overarching accessibility as well as cross-platform interaction. [23]
Java is the most widely used programming language. It is present everywhere. It really
doesn’t matter in whichever domain you work in; you will surely come across Java sooner
or later. So let us see what are the factors that contributed in making java so important.
[23]
As we can see in the above image, Java is an ocean of opportunities having various
benefits. If you are still wondering how Java stands out, then you should take a look at
different domains in which Java is widely used. [24]
• Banking
To deal with transaction management.
• Retail
Billing applications that use in a store and super shop are written in Java.
• Information Technology
Java is designed to solve implementation dependencies.
• Android
Applications are either written in java API.java or uses.
• Financial services
It is used in server side applications.
• Stock market
To write algorithms as to which company they should invest in.
• Big Data
Hadoop mainly uses.
• Scientific and Research Community

To deal with huge amount of data
2.3.3 XML
XML stands for Extensible Mark-up Language.XML is a very popular format and com-
monly used for sharing data on the internet. XML helps organize and visualize the layouts
very nicely.XML uses XML elements or tags to define document structure. [25]
All the UI and layout of our app is designed using XML. XML helps us to design our
apps, how it will look, how components like buttons, text-view, etc. Will be placed and
their styling. In Android XML is used to define layouts, colors, fonts, styles, strings,
arrays, shapes and app configuration manifest file. We can define our app configuration
in XML and read it from or data from remote service can be in XML format if our data
has complex structure. [11]
Advantages of Using XML are [26]
• Truly Portable Data.
• Easily readable by human users.
• Very expressive (semantics near data).

• Very flexible and customizable (no finite tag set).
• Easy to use from programs (libs available).
• Easy to convert into other representations.
• Many additional standards and tools.
• Widely used and supported.
2.3.4 MySQL
MySQL is an open source relational database management system (RDBMS) based on

Structured Query Language (SQL). MySQL runs on virtually all platforms, including
Linux, UNIX, and Windows. Although it can be used in a wide range of applications,
MySQL is most often associated with web-based applications and online publishing and
is an important component of an open source enterprise stack called LAMP. LAMP is
a Web development platform that uses Linux as the operating system, Apache as the
Web server, and MySQL as the relational database management system and PHP as the
object-oriented scripting language. [28]
MySQL is a freely available open source Relational Database Management System (RDBMS)
that uses Structured Query Language (SQL).SQL is the most popular language for
adding, accessing and managing content in a database. It is most noted for its quick
processing, proven reliability, ease and flexibility of use. [27]
Figure 2.7: Server Connection
2.3.5 SQLite
SQLite is a relational database management system contained in a C programming

library. In contrast to many other database management systems, SQLite is not a
client–server database engine. Rather, it is embedded into the end program. [29]
2.3.6 JSON
A collection of name-value pairs. In various languages, this is realizing as an object,

record, struck, dictionary, hash table, keyed list, or associative array. An ordered list of
values. In most languages, this is realized as an array, vector, list, or sequence. When-
exchanging data between a browser and a server, the data can only be text. JSON is
text, and we can convert any JavaScript object into JSON, and send JSON to the server.
We can also convert any JSON received from the server into JavaScript objects. This
way we can work with the data as JavaScript objects, with no complicated parsing and
translations. When exchanging data between a browser and a server, the data can only be
text. JSON is text, and we can convert any JavaScript object into JSON, and send JSON
to the server. We can also convert any JSON received from the server into JavaScript
objects. This way we can work with the data as JavaScript objects, with no complicated
parsing and translations. Data stored in a JavaScript object, you can convert the object
into JSON, and send it to a server. [30]
2.3.7 Retrofit
Retrofit is a REST Client for Android and Java by Square. It makes it moderately sim-
ple to recover and transfer JSON (or other organized information) by means of a REST
based web benefit. In Retrofit we design which converter is utilized for the information
serialization. Ordinarily for JSON you utilize GSon, yet you can add custom converters
to process XML or different conventions. Retrofit utilizes the OkHttp library for HTTP
asks. [31]
To work with Retrofit you require essentially three classes [31]
• Model class which is utilized to delineate JSON information to
• Interfaces which characterizes the conceivable HTTP tasks
• Retrofit. Builder class - Instance which utilizes the interface and the Builder API
which permits.
characterizing the URL endpoint for the HTTP task For this UHS app we have used
retrofit version 2.3.0
2.4 Entity Relationship Diagram (E-R Diagram)

An entity relationship diagram (ERD) shows the relationships of entity sets stored in a
database. An entity in this context is a component of data. In other words, ER diagrams
illustrate the logical structure of databases. [32]
2.4.1 General Overview
An entity relationship diagram consists of several components. Components those are

frequently used to represent an e-r diagram are [32]
1. Entity
2. Weak entity
3. Attribute
4. Multi value attribute
5. Derived attribute
6. Relationship
Entity
An entity can be a person, place, event, or object that is relevant to a given system. For
example, a school system may include students, teachers, major courses, subjects, fees,
and other items. Entities are represented in ER diagrams by a rectangle and named using
singular nouns. It is represented by rectangle. [33]
Figure 2.8: Entity
Weak Entity
A weak entity is an entity that depends on the existence of another entity. In more
technical terms it can defined as an entity that cannot be identified by its own attributes.
It uses a foreign key combined with its attributed to form the primary key. An entity
like order item is a good example for this. The order item will be meaningless without
an order so it depends on the existence of order. It is represented by double rectangle.

[33]
Figure 2.9: Week Entity
Attribute
An attribute is a property, trait, or characteristic of an entity, relationship, or another

attribute. It is represented by an ellipse. [33]
Figure 2.10: Attribute
Multi valued attribute
If an attribute can have more than one value it is called a multi valued attribute. It is
important to note that this is different to an attribute having its own attributes. For
example, a teacher entity can have multiple subject values. It is represented by a double
ellipse. [33]
Figure 2.11: Multi valued attribute
Relationship
How entities act upon each other or are associated with each other. Think of relationships
as verbs. For example, the named student might register for a course. The two entities
would be the student and the course, and the relationship depicted is the act of enrolling,
connecting the two entities in that way. Relationships are typically shown as diamonds
or labels directly on the connecting lines. [33]
Figure 2.12: Relationship
Mapping Cardinality
Cardinality refers to the number of entity objects on each side of the relationship. In
e-r diagram there are four types of mapping cardinalities. For example: a customer can
order products one after another. [33]
1. One-to-One
2. One-to-Many
3. Many-to-One
4. Many-to-Many
One to One
A one-to-one relationship is the simplest relationship between two beans. One entity
bean relates only to one other entity bean. For example: a customer can be kept only in
one word/cell at a time. [33]
Figure 2.13: One to One
One to Many
In a one-to-many relationship, one object can reference several instances of another. [33]
Figure 2.14: One to Many
Many to One
In a many-to-one relationship, many objects can reference one instance of another. [33]
Figure 2.15: Many to One
Many to Many
A many-to-many relationship is complex. In a many-to-many relationship, many objects

can reference many objects. This cardinality is the most difficult to manage. [33]
Figure 2.16: Many to Many
Example of E-R Diagram
To create a database, a developer must know what information needs to be stored, what
tables are needed to store that information, and how each table is related to other tables.
For example, take a database for a blog. A simple database may include two tables:
users and articles. The users table may hold the user id, name, and email. The arti-
cles table may store the article id, timestamp, title, and textbody. For simplicity, let’s
say one article can only be written by one user and One user can write many articles. [34]
An entity relationship diagram is a graphical representation of the relationships of a

database. Using ER diagrams help facilitate discussion and are especially useful when a
database’s schema includes many tables. Given the blog example, an entity relationship
diagram would look something like this [34]
Figure 2.17: E-R Diagram of Blog
2.5 Data Flow Diagram (DFD)

Data flow diagram (DFD) represents the flows of data between different processes in a
business. It is a graphical technique that depicts information flow and the transforms
that are applied as data move form input to output. [35]
DFDs only involve four symbols. They are
• Process
• Data Object
• Data Store
• External Entity
Process
A process shows transformation or manipulation of data flow within the system. The
symbol used is an oval shape
Figure 2.18: Process
Data Flow
The data flow shows the flow of information from a source to its destination. Data flow
is represented by a line, with arrowheads showing the direction of flow
Figure 2.19: Data Flow
Data Store
A data store holding place for information within the systems. It is represented by an
open ended narrow rectangle.
Figure 2.20: Data Store
Example of Data Flow Diagram
Figure 2.21: Online Shopping DFD
2.6 Use Case Diagram

A use case diagram at its simplest is a representation of a user’s interaction with the sys-
tem that shows the relationship between the user and the different use cases in which the
user is involved. A use case diagram can identify the different types of users of a system
and the different use cases and will often be accompanied by other types of diagrams as
well. [36]
Use case diagrams are considered for high level requirement analysis of a system. So
when the requirements of a system are analyzed the functionalities are captured in use
cases. So we can say that uses cases are nothing but the system functionalities written in
an organized manner. Now the second things which are relevant to the use cases are the
actors. Actors can be defined as something that interacts with the system. The actors
can be human user, some internal applications or may be some external applications. [36]
Use case diagrams are typically developing in early stage of development and people often
apply use case modeling for the following purposes [36]
• Specify the context of a system
• Capture the requirements of a system
• Validate a systems architecture
• Drive implementation and generate test cases
• Developed by analysts together with domain experts
Example of Use Case Diagram
can be human user, some internal applications or may be some external applications. So
in a brief when we are planning to draw an use case diagram we should have the following
items identified. [36]
• Admin Register Login, and store the student Records details in database.
• Student Register from the login Process.
• Then the database is searched for details and verified.
• Database stores the details and returns acknowledgement.
Use case diagrams are drawn to capture the functional requirements of a system. So after
identifying the above items we have to follow the following guidelines to draw an efficient
use case diagram [36]
Figure 2.22: Use Case Example
2.7 Conclusions
As a conclusion, this chapter had pointed out the strength, weakness and limitation for
each existing system that have been reviewed. Next, the strength of the proposed solution
will be combining the strength of each reviewed existing system. Proposed solution is
provided to solve the limitation and weaknesses of the existing system, thus it can be
applying in small-medium restaurant enterprise.
Chapter 3
Proposed System
3.1 Introduction
Requirements analysis in systems engineering and software engineering, encompasses
those tasks that go into determining the needs or conditions to meet for a new or al-
tered product, taking account of the possibly conflicting requirements of the various
stakeholders, such as beneficiaries or users. Another requirement you need to have to be
a software manager you need to know how to pleasure your boss. But in financing you
also need to pleasure your boss. [4]
To overcome the limitations of above system, a superbug reduces and doctor verification
system based on Internet and android operating system based is proposed. It’s totally
use android devices. Android devices have gained immense popularity and have rev-
olutionized the use of mobile technology in the automation of routine task in wireless
environment. Android is a Linux based operating system for mobile devices such as
smartphones and tablets. To develop a reliable, convenient and accurate for reduce su-
perbug and easily verify doctor system is considered as a general Objective of the study.
To develop a system that will surely satisfied the user service will be considered as an
objective. One of the Objectives is to design a system that is able to verify a doctor.
That means a patient can verify his doctor is the doctor is real or fraud. To evaluate
its performance and acceptability in terms of security, user-friendliness, accuracy and
reliability is an important objective. To improve the communication between the patient
40
CHAPTER 3. PROPOSED SYSTEM 41
or general user and doctor is one of the objectives. [42]
Requirements analysis is critical to the success of a development project. Requirements

must be documented, actionable, measurable, testable, related to identified business needs
or opportunities, and defined to a level of detail sufficient for system design. Require-
ments can be architectural, structural, behavioral, functional, and non-functional. [8]
3.2 Feasibility
Android Studio is the official Integrated Development Environment (IDE) for Android
app development, based on IntelliJ IDEA. On top of IntelliJ’s powerful code editor and
developer tools, Android Studio offers even more features that enhance your productivity
when building Android apps, such as [37]
1. A flexible Gradle-based build system.
2. A fast and feature-rich emulator.
3. A unified environment where you can develop for all Android devices.
4. Instant Run to push changes to your running app without building a new APK.
5. Code templates and GitHub integration to help you build common app features
and import sample code.
6. Extensive testing tools and frameworks.
7. Lint tools to catch performance, usability, version compatibility, and other prob-
lems.
8. C++ and NDK support.
Built-in support for Google Cloud Platform, making it easy to integrate Google Cloud
Messaging and App Engine. [38]
3.2.1 Objective of Feasibility Study
There are four main feasibility assessments for technology projects are customer facing,
as opposed to just internal to the organization, it is essential to add market feasibility. [38]
The three feasibility studies are
• Technical feasibility
• Operational feasibility
• Schedule feasibility
• Financial feasibility
3.2.2 Technical Feasibility
Technology projects are notorious for running late, over budget or failing completely. The
good news is that mobile projects fair a lot better. According to compared with only 29
percent in non-android projects. [39]
This success rate is probably helped by the fact that mobile projects for large organiza-
tions tend to be smaller and involve less integration (sometimes – alas – no integration
at all) with existing company IT infrastructure. The bad news is that 26% of mobile
projects are delivered late, over budget or with an unsatisfactory result and an additional
5% fail (canceled or not used). To avoid your project joining the unsuccessful third, you
need to undertake a comprehensive technology feasibility study. [39]
Two notes on the Standish research

• Standish measures the success rate for large US organizations like Bank of America,
Home Depot, or the IRS, not start ups producing $1.99 mobile apps
• This is a success from a technology standpoint. A successful technology project will

not guarantee commercial success, but will help prevent a commercial flop assuming
all other viability studies documented in this column and the previous column are
carried out properly.
The evaluation should include available technologies; required skills; deployment; ongo-
ing management and support; integration into back-end systems; scalability and future
proofing. Start by appointing a suitably qualified, independent person to conduct the
feasibility study. Ideally this will be someone who understands both the technology –
mobile, web, integration etc. and the business and user goals behind the program, as well
as having the appropriate assessment and reporting skills. Avoid anyone with a vested
interest in making the project happen or likely to steer it in a particular direction. [39]
3.2.3 Operational Feasibility
Operational feasibility is the measure of how well a proposed system solves the problems,
and takes advantage of the opportunities identified during scope definition and how it
satisfies the requirements identified in the requirements analysis phase of system devel-
opment. [39]
To ensure success, desired operational outcomes must be imparted during design and de-
velopment. These include such design-dependent parameters as reliability, maintainabil-
ity, supportability, usability, disposability, sustainability, affordability and others. These
parameters are required to be considered at the early stages of design if desired operational
behaviors are to be realized. A system design and development requires appropriate and
timely application of engineering and management efforts to meet the previously men-
tioned parameters. A system may serve its intended purpose most effectively when its
technical and operating characteristics are engineered into the design. Therefore, opera-
tional feasibility is a critical aspect of systems engineering that needs to be an integral
part of the early design phases. [39]
3.2.4 Schedule Feasibility
A project will fail if it takes too long to be completed before it is useful. Typically, this
means estimating how long the system will take to develop, and if it can be completed
in a given time period using some methods like payback period. Schedule feasibility is
a measure of how reasonable the project timetable is. Given our technical expertise, are
the project deadlines reasonable? Some projects are initiated with specific deadlines. It
is necessary to determine whether the deadlines are mandatory or desirable. [39]
3.2.5 Financial Feasibility
In case of a new project, financial viability can be judged on the following parameters
[39]
• Total estimated cost of the project
• Financing of the project in terms of its capital structure, debt to equity ratio and
promoter’s share of total cost
• Existing investment by the promoter in any other business projected cash flow and
probability.
3.3 Methodology
The methodology is the general research strategy that outlines the way in which research
is to be undertaken and, among other things, identifies the methods to be used in it.
These methods, described in the methodology, define the means or modes of data collec-
tion or, sometimes, how a specific result is to be calculated. Methodology does not define
specific methods, even though much attention is given to the nature and kinds of pro-
cesses to be followed in a particular procedure or to attain an objective. When proper to
a study of methodology, such processes constitute a constructive generic framework, and

may therefore be broken down into sub-processes, combined, or their sequence changed.
A paradigm is similar to a methodology in that it is also a constructive frame-work. In
theoretical work, the development of paradigms satisfies most or all of the criteria for
methodology. An algorithm, like a paradigm, is also a type of constructive framework,
meaning that the construction is a logical, rather than a physical, array of connected
elements. Any description of a means of calculation of a specific result is always a de-
scription of a method and never a description of a methodology. It is thus important to
avoid using methodology as a synonym for method or body of methods. Doing this shifts
it away from its true epidemiological meaning and reduces it to being the procedure itself,
or the set of tools, or the instruments that should have been its outcome. A methodology
is the design process for carrying out research or the development of a procedure and is
not in itself an instrument, or method, or procedure for doing things [8]
3.3.1 Use of Agile
The software methodology that chosen to develop this System is Agile.The agile approach
is a software development approach based on values, principles, and core practices. The
four values are communication, simplicity, feedback, and courage. We recommend that
systems analysts adopt these values in all projects they undertake, not just when adopting
the agile approach. In order to finish a project, adjustments often need to be made in
project management [17]
3.3.2 Exploration
During exploration, you will explore your environment, asserting your conviction that the
problem can and should be approached with agile development, assemble the team, and
assess team member skills. This stage will take anywhere from a few weeks (if you already
know your team members and technology) to a few months (if everything is new). You
also will be actively examining potential technologies needed to build the new system.
During this stage you should practice estimating the time needed for a variety of tasks.
In exploration, customers also are experimenting with writing user stories. The point is
to get the customer to rene a story enough so that you can competently estimate the
amount of time it will take to build the solution into the system you are planning. This
stage is all about adopting a playful and curious attitude toward the work environment,
its problems, technologies, and people. [18]
3.3.3 Planning
The next stage of the agile development process is called planning. In contrast to the
first stage, planning may only take a few days to accomplish. In this stage you and your
customers agree on a date anywhere from two months to half a year from the current
date to deliver solutions to their most pressing business problems (you will be addressing
the smallest, most valuable set of stories). If your exploration activities were succinct,
this stage should be very short. The entire agile planning process has been character-
ized using the idea of a planning game as devised by Beck. The planning game spells
out rules that can help formulate the agile development teams relationship with their
business customers. Although the rules form an idea of how you want each party to
act during development, they are not meant as a replacement for a relationship. They
are a basis for building and maintaining a relationship. So, we use the metaphor of a
game. To that end we talk in terms of the goal of the game, the strategy to pursue,
the pieces to move, and the players involved. The goal of the game is to maximize the
value of the system produced by the agile team. In order to figure the value, you have to
deduct costs of development, and the time, expense, and uncertainty taken on so that the
development project could go forward. The strategy pursued by the agile development
team is always one of limiting uncertainty (downplaying risk). To do that they design
the simplest solution possible, put the system into production as soon as possible, get
feedback from the business customer about whats working, and adapt their design from
there. Story cards become the pieces in the planning game that briefly describe the task,
provide notes, and provide an area for task tracking. [18]
Figure 3.1: The Agile Development Methodologies
There are two main players in the planning game: the development team and the business
customer. Deciding which business group in particular will be the business customer is
not always easy, because the agile process is an unusually demanding role for the cus-
tomer to play. Customers decide what the development team should tackle first. Their
decisions will set priorities and check functionalists throughout the process. [16]
3.3.4 Iteration to the first release
The third stage in the agile development process is composed of iterations to the first
release. Typically these are iterations (cycles of testing, feedback, and change) of about
three weeks in duration. You will be pushing yourself to sketch out the entire architec-
ture of the system, even though it is just in outline or skeletal form. One goal is to run
customer-written functional tests at the end of each iteration. During the iterations stage
you should also question whether the schedule needs to be altered or whether you are
tackling too many stories. Make small rituals out of each successful iteration, involving
customers as well as developers. Always celebrate your progress, even if it is small, be-
cause this is part of the culture of motivating everyone to work extremely hard on the
project. [18]
3.3.5 Productionizing
Several activities occur during this phase. In this phase the feedback cycle speeds up so
that rather than receiving feedback for an iteration every three weeks, soft-ware revisions
are being turned around in one week. You may institute daily brings so everyone knows
what everyone else is doing. The product is released in this phase, but may be improved
by adding other features. Getting a system into production is an exciting event. Make
time to celebrate with your teammates and mark the occasion. One of the watchwords
of the agile approach, with which we heartily agree, is that it is supposed to be fun to
develop systems. [18]
3.3.6 Maintenance
Once the system has been released, it needs to be kept running smoothly. New features
may be added, riskier customer suggestions may be considered, and team members may
be rotated on or o the team. The attitude you take at this point in the developmental
process is more conservative than at any other time. You are now in a keeper of the mode
rather than the playful one you experienced during exploration. [18]
3.3.7 Track Monitor
Operation and maintenance has been neglected in the past, or been discussed and in-
troduced only after a project was completed. This neglect or delay in applying proper
operation and maintenance has adversely acted the credibility of the investments made,
the functioning of the services, the well-being of rural populations, and the development
of further projects. However, the importance of OM has gained considerable visibility
over the past few years, and it appears that policy-makers and project designers are now
more conscious of the direct links between improved OM practices and the sustainability
of water supply and sanitation services. There is also greater recognition of the need to
approach these projects in a comprehensive way, emphasizing not only the design and
construction but also post construction activities. [18]
3.4 System Requirement

System requirement is the requirement core functionalities of the system and system se-
curity. They are two part. [35]
3.4.1 Functional Requirement
Complain Management
1. The system shall lete user to complain about a pharmacy.
2. Befor Submitting a Complain user verify is must.
3. User can track his complain
Medicine Management
1. From the system use get all antibiotic medicine details.
2. User also search medicine using generic of medicine
3. User also serch medicine using medicine name.

Doctor Management
1. The system can verify a doctor
2. The system also can check doctor details.
3. Using the system a doctor can help people for medication.
4. A doctor can register here and help people for medication
Mentorship Management
1. The system have a list of mentorship article about general health.
2. Using the system a user can request a doctor for medication or mentrship
Article Management
1. The system have article about medicine, superbug, general; health etc.
2. The system also have mentorship article.
Superbug Management
1. The system have superbug related all news and article.
2. Also have article about reducing superbug.
3.4.2 Non Functional Requirement
Operational Requirement
1. The system should operate in Window platform environment.
2. The system should prompt user to make a backup at the end of the operational
day.
Performance Requirements
1. The system should let user to known about superbug and antibiotic medicine in a
short period of time.
2. The system should let user to verify a doctor easily in a short period of time.
3. The system should complete a complain about a pharmacy in a short period of

time.
Security Requirements
1. The system should validate the username and password in order to login and make
changes to the system.
2. The system should request the current password of the user in order to let them
change to a new password.
Usability Requirement
1. The system should have an easy understand graphic user interface that deal with
the user.
2. The system should let user easy to understand the functionality of each modules
3.5 Entity Relationship Diagram (E-R diagram)

Preventing superbug and Doctor verification is a process of to get better health medi-
cation. User using their authentication he can contribute to solve of future problem in
Bangladesh. A user can frequently complain about a pharmacy, can know about antibi-
otic resistance, antibiotic details, can verify a doctor, get superbug related news article
and alsoi get free medication from authorized doctor. [32]
In here, we show our system E-R diagram.

Figure 3.2: E-R Diagram for PSDV System
3.6 Data Flow Diagram (DFD)

Prevent Superbug and Doctor Delivery System Data flow diagram is often used as a
preliminary step to create an overview of the prevent superbug without going into great
detail, which can later be elaborated.it normally, consists of overall application dataflow
and processes of the prevent superbug and doctor verification. It contains all of the user
flow and their entities such all the flow of Complains, Medicine, Mentorship, Doctor ver-
ify, Article Item. All of the below diagrams has been used for the visualization of data
processing and structured design of the Preventing Superbug and Doctor verify process
and working flow. [35]
Figure 3.3: Context Diagram of PSDV System
This is the Zero Level DFD of Prevent Superbug and Doctor Verification System, where
we have elaborated the high level process of preventing superbug and doctor verify. It’s
a basic overview of the whole PSDV System or process being analyzed or modeled. It’s
designed to be an at-a-glance view of Delivery, Category and Item showing the system as
a single high-level process, with its relationship to external entities of Complain, Doctor
Data, Medicine. It should be easily understood by a wide audience, including Complain,
Doctor, Medicine and Article Delivery In zero level DFD of PSDV System, and we have
described the high level flow of the PSDV system. [37]
High Level Entities and process flow of PSDV System
• Managing all Medicine
• Managing all Complain
• Managing all User

• Managing all Doctor
• Managing all Article
• Managing all Mentorship
• Managing all Doctor data
• Managing all user Role
Figure 3.4: One Level DFD Diagram of PSDV System
DFD Level 2 then goes one step deeper into parts of Level 1 of Prevent Superbug and
Doctor Verification System. It may require more functionalities of Prevent Superbug
and Doctor Verification System to reach the necessary level of detail about the Prevent
Superbug and Doctor Verification functioning. First Level DFD (1st Level) of Prevent Su-
perbug and Doctor Verification System shows how the system is divided into sub-systems
(processes). The 2nd Level DFD contains more details of Medicine, Doctor, Complain,
Article, Mentorship, User and News. [38]
Low level functionalities of Prevent Superbug and Doctor Verification (PSDV) System
• Admin logins to the system and manage all the functionalities of Prevent Superbug
and Doctor Verification System
• Admin can add, edit, delete and view the records of Complain, Medicine, Article,
Doctor Information
• Admin can manage all the details of Complain, Medicine, Article, Doctor Informa-
tion
• Admin can also generate reports of Complain, Medicine, Article, Doctor Informa-
tion
• Admin can search the details of Complain, Medicine, Article, Doctor Information
• Admin can apply different level of filters on report of Complain, Medicine, Article,
Doctor Information
• Admin can tracks the detailed information of Complain and Mentorship.
3.7 Use Case Diagram

can be human user, some internal applications or may be some external applications. [39]
Figure 3.5: Use Case Diagram of PSDV System
3.8 Database Design

The standard user and application program interface to a relational database is the struc-
tured query language (SQL). SQL statements are used both for interactive queries for
information from a relational database and for gathering data for reports. [28]
This section will describe how the system’s database is deigned. Database design is an
important part of software design. The database design is directly related to the merits
of the program to achieve the efficiency and simplicity of data access. [28]
Databases are the storehouses of data used in the software systems. The data is stored
in tables inside the database. Several tables are created for the manipulation of the data
for the system. Two essential settings for a database are [28]
• Primary Key - the field that is unique for all the record occurrences.
• Foreign Key - the field used to set relation between tables.
Complain Table
Complain table have the user complain data about pharmacy. The table have 8 Attribute.
SL No. Name Type Description

1 Complain Id Int Primary Key
2 Provider Name Text
3 Pharmacy Name Text
4 Address Text
5 Details Text
6 Is prescribed Boolean
7 Prescription image
Text
8 User Id Int Foreign Key
(User)
Table 3.1: Complain Table
Medicine List Table
Medicine table have all antibiotic medicine and medicine details. The table have 7 At-
tribute.

1 Medicine Id Int Primary Key
2 Name Text
3 Dosages From Text
4 Strength Text
5 Price Text
6 group Id Int
7 company id Int Foreign Key
(Company)
Table 3.2: Medicine List Table
User Table
User table have all data about user information. The table have 12 Attribute.

1 User Id Int
2 Email Text Primary Key
3 Full Name Text
4 Qualification Text
5 Hospital Text
6 Speciality Int
7 Password Int
8 reg no Int
9 Address Int
10 Contact Number Int
11 Country Int
12 Role id Int Foreign Key
(Company)
Table 3.3: User Table
User Role Table
User role table have details about user role. The table have 3 Attribute.

1 User Id Int Foreign Key
2 Role id Text Primary Key
3 email Text
Table 3.4: User Role Table
Doctor Table
Doctor table have all data about doctor information for doctor verification and others.
The table have 8 Attribute.

1 doctor reg no Int Primary Key
2 name Text
3 email Text
4 Qualification Text
5 Hospital Text
6 Speciality Int
7 Medical College Int
8 Degree Int
Table 3.5: Doctor Table
Article Table
Article table have all Article details about medicine, doctor article and superbug article.
The table have 5 Attribute.

1 Article Id Int Primary Key
2 Title Text
3 Short desc Text
4 Long desc Text
5 useri d Text Foreign Key
Table 3.6: Article Table

Mentorship Table
Mentorship table have all medication details of user request mentorship to doctor. The
table have 6 Attribute.

1 Mentorship Id Int Primary Key
2 Doctor id Text Foreign Key
3 User desc Text Foreign Key
4 Subject Text
5 Description Text
6 Status Text
Table 3.7: Mentorship Table
Superbug Table
Superbug table have all details article news about superbug. The table have 6 Attribute.

1 superbug Id Int Primary Key
2 title Text
3 link Text
4 details Text
5 Description Text
6 Status Text
Table 3.8: Superbug Details Table
Medicine Details
Medicine details table have all antibiotic medicine details. The table have 5 Attribute.

1 medicine Id Int Primary Key
2 company name Text
3 Medicine Name Text
4 Details Text
3 Medicine Image Text
Table 3.9: Medicine Company Table
3.9 Implementation
After gather the user requirements from JAD session and observation. Will starts make
analysis, design and implement each and every module base on the user requirements
that gathered. [8]
Before development, the team does a final verification of the concepts from the designs
within an environment that mirrors production as closely as possible.Typically, the proof
of concept is a continuation of some initial development work (the preliminary proof
of concept) that occurred during the Planning Phase. The proof of concept tests key
elements of the solution on a non-production simulation of the proposed operational
environment. The team walks operations staff and users through the solution to vali-
date their requirements.There may be some solution code or documentation that carries
through to the eventual solution development deliverable however, the proof of concept
is not meant to be production-ready. The proof of concept is considered throw away
development that gives the team a final chance to verify functional specification content
and to address any more issues prior to transitioning into development. [17]
The team develops the solution using the core components and extending them to the
specific needs of the solution. The team also develops and conducts unit functional tests
to ensure that individual
features perform according to specification.MSF recommends that project teams follow

a best practice of performing daily builds with their solution. Building a solution in a
form that is executable on a daily basis provides a number of valuable benefits simply
by putting different pieces of the code together. A daily build exposes unanticipated
design defects and makes diagnosing defects easier.The daily build should be subjected
to as much of the full suite of tests as can be run during the available time. This build
validation test pass helps expose integration defects as early as possible. It also allows
the team to validate their testing approach and testing infrastructure. [37][0.5cm]
The team develops a testing infrastructure and populates it with test cases that help
ensure the entire solution performs according to specification. This solution test suite
typically incorporates, as a subset, the individual feature tests used by developers in
building the solution components.MSF advocates preparing frequent builds of all the
components of the solution for testing and review. This approach is recommended for
developing code as well as for builds of hardware and software components. The process
of creating in-term builds allows a team to find issues early in the development process,
which shortens the development cycle and lowers the cost of the project. Daily builds are
the practice of assembling all the components working toward the final goal of a solution.
This enables the team to determine earlier rather than later that all components will work
together. This method also allows the team to add functionality onto a stable build. The
idea is to have a shippable product ready at any point in time. In this way, the stability
of the total solution is well understood and has ample test data prior to being released
into production. [18]
3.10 Features
The system caters to a wide variety of applications and quite a few of its stand out fea-
tures enable its worldwide use. The features include
1. First of all, its number one feature is the ability to store data in tables. The fact that
the very storage of data is in a structured form can significantly reduce iteration
time.
2. Data persists in the form of rows and columns and allows for a facility primary key
to define unique identification of rows.
3. It creates indexes for quicker data retrieval.
4. Allows for various types of data integrity like (i) Entity Integrity; wherein no du-
plicate rows in a table exist, (ii) Domain Integrity; that enforces valid entries for
a given column by filtering the type, the format, or the wide use of values, (iii)
Referential Integrity; which disables the deletion of rows that are in use by other
records and (iv) User Defined Integrity; providing some specific business rules that
do not fall into the above three.
5. Also allows for the virtual table creation which provides a safe means to store and
secure sensitive content.
6. Common column implementation and also multi user accessibility is included in the
RDBMS features.
3.11 Result Analysis

Prevent Superbug and Doctor Verification system provide online solution for reducing
superbug problem in Bangladesh. User can complain about illegal antibiotic distribu-
tion. So when a pharmacy give antibiotic without any prescription. Then any user can
complain about the pharmacy using our complain page. Also, user can known about an-
tibiotic using medicine pages. Also, user can know about superbug using superbg page.
Also, user get free medication using our mentorship page. [48]
The following results are given below

If anyone wants to complain then he/she must complain item.Then give all information
about the pharmacy and click submit button. Then the complain is register to our server.
• Complain, Submit
• Medicine, Medicine List and Medicine Details
• Mentorship, Seletc doctor, get article, request for medication.

• Article, Article list and detail article.
• Doctor Verification, give registration number or full info and verify
• superbug, list, get all superbug details.
Figure 3.6: Dashboard

Figure 3.7: Complain about pharmacy
Figure 3.8: Doctor Verification

3.12 Applications
There are certain requirements the proposed application must fulfill to meet the objec-
tives of the project.
The requirements to be achieved
In Background Management Platform
• Administrator can add and modify Doctor Information.
• Administrator can add, modify and query Medicine.
• Administrator can add, modify and query user information.
• Administrator can manage complain list, superbug article.
In the Website Public Page and Android Application
• User can view doctor information, Medicine details, Article
• User can Complain about Pharmacy.
• User can their information.
The requirements that should be achieved
• The project supports all type of user can get help to our system and reducing
superbug and fake doctor.
The requirements nice to be achieved
• Permission Management in Background Management Platform
• Manage Superbug in Website Public Page

3.13 Conclusions
This chapter deals with the user module design of our project. In this chapter the details
about how to use the application are included. Table design details we can consider this
chapter as the user manual or user guide of this application we developed. As all the
details of the every module and as well as their use are included in this chapter.
Chapter 4
User Manual
4.1 Introduction
At the end of the system requirements collection, several relevant diagrams have been
generated in order for the preparation of system model design. The design phase ac-
tivities include the design of project architecture and graphical user interfaces, develop
relational databases, business logic and file specifications. [55]
The sole task of a Web Server is to accept incoming. The first thing Android studio does
when a request comes in is to decide how to handle the request. Its decision is based
upon the requested file’s extensible markup Language. Android Studio makes it easy to
create a new image asset for every density size. With Vector Asset Studio, you can select
from Google-provided material design icons or import an SVG or PSD file. Vector Asset
Studio can also generate bitmap files for each screen density to support older versions of
Android that don’t support the Android vector draw able format. [55]
4.2 System Requirements

Our system required some hardware specification and software specification. We also
need a server to maintain our database and an android device to test our application.
[38]
68
CHAPTER 4. USER MANUAL 69
4.2.1 Developer Requirements
The hardware, software and server requirements are listed below for developing the sys-
tem. [38]
4.2.2 Hardware Requirements
The following are the minimum hardware specifications to run the Android Studio IDE
[12]
Computer Specification
Processor Type Intel i3 Processor Minimum

Operating Syatem Microsoft® Windows® 7/8/10
(32- or 64-bit) or Mac® OS
X® 10.10 or Linux on
Ubuntu® 14.04 LTS
Main Board Any Compatible Motherboard
with Processor
Monitor 1280 x 800 minimum screen
resolution
RAM 4 GB RAM minimum, 8 GB
RAM recommended
Hard Disk 2 GB of available disk space
minimum, 4 GB Recommended
Disk Type HDD
Graphics Card Intel HD Graphics
Optical Drive DVD Writer Drive
Audio/Speaker On Board
Keyboard Any Compatible Keyboard
Mouse Any Compatible Mouse
Table 4.1: Desktop Specification for Android Studio
Mobile Specifications
As we developed mobile apps, so we need a mobile device to test our app. Below the
minimum specification of a mobile device to test our app [12]
Model Any Android Phone

Operating System Android
API Version Minimum API Level 16
Processor Octa-core or quad core
RAM 1 GB
Hard Disk 8 GB
Display Size and Resolution Any Size and Pixel
Display Type Touchscreen
Camera Resolution (Back) 8 Megapixel
Wireless LAN Yes, dual-band, Wi-Fi Direct,
Wi-Fi hotspot
Network Scope 2G, 3G, 4G
Table 4.2: Mobile Specification for Test App
4.2.3 Software Requirements
The software is a set of procedures of coded information or a program when fed into the
computer hardware enables the computer to perform various tasks. Software is like a
current inside the wire, which cannot be seen but its effect can be felt. Below are the
minimum software requirement for build the system. [13]
Computer Software Requirements
The uses of software for our computer side to development the PSDV system.
• Operating System: Windows 7/8/10 (32 - or 64 bit)
• IDE: Android Studio
• IDE for API Building: Intellij IDEA Community Edition
• DB Browser for SQLite
• Other Software: Photoshop CC 2015

Server Software Requirements
The uses of software for server side development.
• Postman (For Api testing)
• XAMPP Server (Maintain database)
• Windows 7/8/10 (32 - or 64 bit)
• Google Chrome (Browser)
Mobile Software Requirement
Below is a list of mobile applications which use in our development environment
• Android API Version Minimum 16
• Developer Options
• PSDV System App
• Google chrome (Browser)
4.2.4 User Requirements for Using PSDV System
As our system is android based. So when a user want to use it User must have an android
operating system phone [12]. The minimum user mobile requirements are below. [38]
Model Any Android Phone

Operating System Android
API Version Minimum API Level 16
API Version Name Jelly Bean Minimum
Processor Octa-core or quad core
RAM 1 GB
Hard Disk 2 GB
Display Size and Resolution Any Size and Pixel
Display Type Touchscreen
Camera Resolution (Back) 8 Megapixel
Wireless LAN Yes, dual-band, Wi-Fi Direct,
Wi-Fi hotspot
Network Scope 2G, 3G, 4G
Table 4.3: Mobile Specification for Use PSDV System
4.3 User Interfaces

This illustrates the graphical user interface of our project. by following this chapter, a
user can come to know how all the modules of this project works and how to use this
application in a user friendly way. [11]
4.3.1 Dashboard
This is the home page of our apps. Here we can see the item of our app. which you need
just click on it and go inside for work. Without login a you cannot use all item. From
dashboard user can go any module and use any module to click it. Figure 4.1 describe
the dashboard of PSDV system.
Figure 4.1: Dashboard of PSDV System
4.3.2 Register
Register has two roles. The roles are
• User / Patient Register
• Doctor
For doctor registration doctor give his proper information and registration number or
full information to register the doctor. After Sign up or login user directly go to the
dashboard. Figure 4.2 describe the sign up page of PSDV System.
Figure 4.2: Signup Page of PSDV System
4.3.3 Login
This is the Login page of our apps. Here you can login our app. If you login then you
will use all service of our app. After Sign up or login user directly go to the dashboard.
Figure 4.3 describe the Login page of PSDV System.
Figure 4.3: Login page of PSDV System
4.3.4 Complain
This is the Complain page of our apps. Using the complain page you can complain about
a pharmacy for illegal distribution of antibiotic. After complain user get an confirmation
message and redirect to the dashboard page. Figure 4.4 describe the Complain page of
PSDV System.
Figure 4.4: Complain Page of PSDV System
4.3.5 Complain View Page
This is the Complain view page of our apps. Using the complain view page an admin can
view complain about a pharmacy for illegal distribution of antibiotic. Using this section
a admin can see all complains. After clicking an item can see all details about complain.
Figure 4.5 describe the Complain view page of PSDV System.
Figure 4.5: Complain View Page of PSDV System
4.3.6 Antibiotic List
Using this page a user can see all antibiotic medicine list. After click a list item, user will
see all details about the antibiotic medicine. User can back to dashboard by using back
button. Figure 4.6 describe the antibiotic medicine list page.
Figure 4.6: Antibiotic Medicine List Page of PSDV System
4.3.7 Antibiotic Medicine Item Details
Using this page a user can know about a antibiotic medicine details. After click a list
item, user will see all details about the antibiotic medicine. User can back to dashboard
by using back button. Figure 4.7 describe the antibiotic medicine details page.
Figure 4.7: Antibiotic Medicine Details Page of PSDV System
4.3.8 Mentorship Page
This is the mentorship page of our apps. Using the mentorship page you can view all
doctor list for mentor who will agree to give you free medication. You can request for
free medication to a doctor. Figure 4.8 describe the doctor List for mentorship. After
Click a Doctor User see the medication article of the doctor. Also user can request for
medication to the doctor.
Figure 4.8: Mentorship Page of PSDV System
4.3.9 Doctor Verification Page
This is the doctor verification page of our apps. If you want to verify a doctor go here
and using the information you can verify a doctor easily. For verify a doctor you need to
login or register of our system. After clicking the submit button user will see the doctor
information. If doctor data are not available user get fake doctor message. Figure 4.9
describe the doctor verification page of PSDV System.
Figure 4.9: Doctor Verification Page of PSDV System
4.3.10 Doctor Confirmation Message Page
If user submitted registration number or information are have on database then user get
verify meassage. Otherwise give a fake doctor message. Figure 4.9 describe the doctor
verification message page of PSDV System.Figure 4.10 describe the Doctor Confirmation
Message of PSDV System
Figure 4.10: Doctor Confirmation Message Page of PSDV System
4.3.11 Article Page
This is the Article page of our apps PSDV System. Here you will find all article for
general health, superbug, medicine and antibiotic. Only a doctor can add article. when
a doctor add an article he will see my article list here. he can update the article from
my article. after click an article item user will show details of the article. Figure 4.11
describe the Article page of PSDV System.
Figure 4.11: Article Page of PSDV Syste
4.3.12 Article Add Page
This is the Article Add page of our apps PSDV System. If you are login with doctor
role.The you can add article using this page. Also can update and delete his article. After
submit a article the article will add to the article list. Figure 4.12 describe about article
add page of PSDV System.
Figure 4.12: Article Add Page of PSDV System
4.3.13 Superbug Page
This is the Superbug page of our apps. Here you will find all superbug related news,
blog, doctor article and antibiotic resistance details. You don’t need login or registration
for use superbug page. Using the superbug page user will be know about superbug in
mother language. Figure 4.13 describe the superbug page of PSDV System.
Figure 4.13: Superbug Page of PSDV System
4.3.14 Superbug News List Page
This is the Superbug News List Page of our apps PSDV System. Here you will find all
superbug related news that are publish in news paper and others. You don’t need login
or registration for use superbug page news page.Here user will get a list of news. After
click a item the news load from the site and showing in our app PSDV System. Figure
4.14 describe the Superbug News page of PSDV System.
Figure 4.14: Superbug News List Page of PSDV System
4.3.15 User Information
Using this page user can see their information and their credential. Also a user can can
update or delete his information using this module. If user are loged in user can see this
page. Otherwise user can not see the page. Figure 4.15 describe the User Information
page of PSDV System.
Figure 4.15: User Information page of PSDV System
4.4 Conclusions
This chapter deals with the details of the technologies we used to develop our project.
We needed a hardware configuration with core i7 processor, 8 GB of RAM, 20 GB hard
disk allocation. We also needed a software configuration of windows 10, 64-bit operating
system, Android Studio to implement the application. We also used net beans IDE for
the coding purpose. And the way we used these technologies are briefly described above.
Chapter 5
Conclutions
5.1 Conclusions
In Bangladesh people health problem is big issue. Many pharmacy people like medicine
seller and fake doctor problem are to much in our country. So we make this system to
reducing this problem.
Obviously, the propose system can help to reduce antibiotic resistance problem in
Bangladesh and Also can identify the doctor fake or not. Also using this system the
poor people can get free medication from authorized doctor. User can get superbug re-
lated news, article, antibiotic medicine related article and many more to using this system.
On the other hand, the technology nowadays allows the portability requirement easy
to achieve. Therefore, portability has become one of the factor that have to take into
consideration in the system development process. Because portability bring a lot of ben-
efit to user while they using the system such as it provide convenience, accessibility, easy
to communicate and etc. Hence, portability has done an impact to the social that every-
body is much more preferable to complete their task with portable device.
The system is not make for business . We make this system for people help without
any money. That mean our system is non profit system and absolutely free for all kind
88
CHAPTER 5. CONCLUTIONS 89
of people.
In order to fulfill these all requirement, our proposed method can an e-health system
of mobile platform. Here user can get free medication using mentor ship request option.
User don’t need any money for this service. Also user can verify his doctor easily to use
this system.
5.2 Future Works

We also want to modify our application for the Future Work .We hope this work will help
us in our future work.
• The system can implement a feature which is a doctor can add patient details using
patient information. Doctor can update and delete it. When need previous patient
info doctor easily search it and can find it.
• The system can implement a feature which is real time notification from the mobile
phone application to the service desk.
• In addition, the mobile application also can implement a feature that allow User to
review a doctor.
• We will make it iOS version
• Last but not lease, implement a online chatting system where user can directly
contact with a doctor.
References
[1] Superbug https://en.wikipedia.org/wiki/Super Bug [accessed January 11, 2019]
[2] Antimicrobial resistance https://en.wikipedia.org/wiki/Antimicrobial resistance [ac-

cessed January 11, 2019]
[3] About Antimicrobial Resistance: https://www.cdc.gov/drugresistance/about.html

[accessed January 15, 2019]
[4] Global action plan on antimicrobial resistance: https://www.who.int/antimicrobial-

resistance/publications/global-action-plan/en/ [accessed January 15, 2019]
[5] Superbugs linked to 80% of deaths in Bangladeshi ICUs:

https://www.dhakatribune.com/health/2019/04/24/superbugs-linked-to-80-of-
deaths-in-bangladeshi-icus [accessed January 22, 2019]
[6] A Review of Superbug: A Global Threat in Health Care System

https://www.banglajol.info/index.php/BJID/article/view/37678 [accessed Jan-
uary 22, 2019]
[7] Finding the superbug, the invincible bacteria: https://www.thedailystar.net/star-

weekend/spotlight/antibiotic-resistance-real-and-we-caused-it-1429225 [accessed Jan-
uary 25, 2019]
[8] Wiki books available at

https://en.wikibooks.org/wiki/Introduction to Software Engineering/Planning/Re-
quirements [accessed January 31, 2019]
[9] Hardware for android studio. https://www.quora.com/What-are-the-recommended-

hardware-for-Android-Studio [accessed February 12, 2019]
90
REFERENCES 91
[10] Android Studio.https://en.wikipedia.org/wiki/Android Studio [accessed February

12, 2019]
[11] Udacity https://www.udacity.com/course/android-basics-user-interface–ud834 [ac-

cessed February 20, 2019]
[12] Android Studio Official Doc https://developer.android.com/docs [accessed February

25, 2019]
[13] Java Spring Framework https://en.wikipedia.org/wiki/Spring Framework [accessed

March 05, 2019]
[14] Java Spring Boot https://spring.io/projects/spring-boot [accessed March 05, 2019]
[15] XAMPP.https://en.wikipedia.org/wiki/XAMPP [accessed March 19, 2019]
[16] AgileTraiblazer http://www.agiletrailblazers.com [accessed March 25, 2019]
[17] Agile software development https://en.wikipedia.org/wiki/Agile software development

[accessed March 26, 2019]
[18] Agile Methodology Model Guide for Software Development Testing

https://www.guru99.com/agile-scrum-extreme-testing.html [accessed April 03, 2019]
[19] Adobe Photoshop https://en.wikipedia.org/wiki/Adobe Photoshop [accessed April

10, 2019]
[20] Using Photoshop https://www.creativelive.com/blog/why-photographers-use-

photoshop/ [accessed April 11, 2019]
[21] Visual Studio Code: https://code.visualstudio.com/docs [accessed April 15, 2019]
[22] Udemy.https://blog.udemy.com/xampp-tutorial/ [accessed April 18, 2019]
[23] Java https://en.wikipedia.org/wiki/Java( programmingl anguage)
[24] Important of Java.http://www.allaboutweb.biz/importance-java-todays-world/ [ac-

cessed April 24, 2019]
REFERENCES 92
[25] XML for Beginners Ralf Schenkel. http://resources.mpi-

inf.mpg.de/d5/teaching/ss03/xml-seminar/talks/xml%20for%20beginners.pdf
[accessed April 28, 2019]
[26] Hastac.https://www.hastac.org/blogs/deven/2017/01/19/xml-importance-
applications [accessed May 09, 2019]
[27] Official phpMyAdmin website, http://www.phpmyadmin.net/ [accessed May 11,

2019]
[28] MySQL Explained by Andrew Comeau. https://leanpub.com/mysqlexplained [ac-

cessed May 16, 2019]
[29] SQLite https://en.wikipedia.org/wiki/SQLite
[30] JSON.https://en.wikipedia.org/wiki/JSON [accessed May 18, 2019]
[31] Retrofit https://en.wikipedia.org/wiki/Retrofitting
[32] Overview of ERD https://en.wikipedia.org/wiki/Entity%E2%80%93relationship model

[Accessed May 21, 2019]
[33] Details in ERD https://www.tutorialspoint.com/dbms/er diagram representation.htm

[Accessed May 21, 2019]
[34] Example of ERD https://medium.com/david.tsai/a-quick-look-at-entity-

relationship-diagrams-edbb9c3be569
[35] Software Engineering 10th Edition by Ian Sommerville’s book website

http://iansommerville.com/software-engineering-book/web/feasibility-study [ac-
cessed May 23, 2019]
[36] Abran, Alain; Moore, James W.; Bourque, Pierre; Dupuis, Robert; Tripp, Leonard
L. (2004). Guide to the Software Engineering Body of Knowledge. IEEE. [accessed
May 27, 2019]
[37] Sommerville, Ian (2008). Software Engineering (7 ed.). Pearson Education
[38] Somerville Software Engineering book available at:https://edisciplinas.usp.br/

pluginfile.php/2150022/modr esource/content/1/1429431[accessedJune03, 2019]
REFERENCES 93
[39] Campbell-Kelly, Martin; Aspray, William (1996). Computer: A

History of the Information Machine. New York: Basic Books.
https://en.wikipedia.org/wiki/Applications of tware[accessedJune08, 2019]
[40] Doctorola exiting app: https://doctorola.com [accessed June 14, 2019]
[41] About Doctorola https://doctorola.com/about
[42] Bangladesh Medical and Dental Council (BMDC) Existing services:

https://web.bmdc.org.bd/ [accessed June 14, 2019]
[43] Bangladesh Medical and Dental Council (BMDC) existing doctor search
https://web.bmdc.org.bd/search-doctor [accessed June 26, 2019]
[44] How BMDC Works https://web.bmdc.org.bd/about-howitworks [accessed June 26,

2019]
[45] What BMDC does https://web.bmdc.org.bd/about-whatit [accessed June 26, 2019]
[46] BMDC Introduction: https://web.bmdc.org.bd/about-introduction [accessed June

26, 2019]
[47] Drug Information Management System (DIMS) existing service

https://play.google.com/store/apps/details?id=com.twgbd.dimshl=en [accessed
June 26, 2019]
[48] e-Health in Bangladesh: Current Status, Challenges, and Fu-

ture Direction https://www.researchgate.net/publication/287435516 e-
Health in Bangladesh Current Status Challenges and Future Direction [accessed
July 17, 2019]
[49] Pulse Healthcare Services https://play.google.com/store/apps/details?id=com.bs.pulse

[accessed July 18, 2019]
[50] Patient Aid https://play.google.com/store/apps/details?id=com.itmedicus.patientaid&

hl=en US [accessed July 18, 2019]
[51] Bangladesh health call center: http://www.dghs.gov.bd/index.php/en/home/2551-

government-and-non-government-ambulance-enlist-notice [accessed July 23, 2019]
REFERENCES 94
[52] Health System in Bangladesh: Challenges and Opportunities:

https://www.researchgate.net/publication/276105127 Health System in Bangladesh
Challenges and Opportunities [accessed August 11, 2019]
[53] Private hospital shut down for employing fake doctors:

https://www.dhakatribune.com/bangladesh/nation/2019/04/30/private-hospital-
shut-down-for-employing-fake-doctors [accessed September 04, 2019]
[54] Fake doctors: https://www.banglanews24.com/national/article/78478/Two-fake-

doctors-jailed-in-Dhaka [accessed September 06, 2019]
[55] User guide: https://en.wikipedia.org/wiki/User guide [accessed October 08, 2019]

Appendices
95
Appendix A
Objective Of Java
Figure A.1: Objective of Java
96
Appendix B
XAMPP Control Panel
Figure B.1: XAMPP Control Panel
97

BUBT Demo Report

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

BUBT Demo Report

Uploaded by

Copyright:

Available Formats

Android Application “PSDV System in BD”

DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

BANGLADESH UNIVERSITY OF BUSINESS AND TECHNOLOGY

November 20, 2019

Android Application “PSDV System in BD”

Md. Nayan Sarder 15161203060

Submitted to the Department of Computer Science and Engineering

COMPUTER SCIENCE AND ENGINEERING

November 20, 2019

————————— ————————– —————————–

TO WHOM IT MAY CONCERN

Dedicated to our Parents for their love and inspiration

Finally, I wish to express my gratitude to Bangladesh University of Business and Tech-

With Best Regards,

All Right Reserved

List of Figures xii

List of Tables xiv

3.2.5 Financial Feasibility . . . . . . . . . . . . . . . . . . . . . . . . . 44

B XAMPP Control Panel 97

2.1 DIMS App . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

3.1 The Agile Development Methodologies . . . . . . . . . . . . . . . . . . . 47

3.3 Context Diagram of PSDV System . . . . . . . . . . . . . . . . . . . . . 53

4.1 Dashboard of PSDV System . . . . . . . . . . . . . . . . . . . . . . . . . 73

A.1 Objective of Java . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

B.1 XAMPP Control Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

3.1 Complain Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

4.1 Desktop Specification for Android Studio . . . . . . . . . . . . . . . . . . 69

– Mobile application is convenient to carry.

– Global partnerships and large install base.

– Powerful development framework.

– Open marketplace for distributing apps.

Based on the advantages of both applications, we motivated to develop an android ap-

1.2 Existing System

1.3 Problem of Existing System

1.3.1 Difficulties in Doctor verification

1.3.2 Difficulties of Superbug and Complain

1.3.3 Difficulties to get doctor mentorship

1. We want to reduce superbug problem in Bangladesh.

1.5 Project Objectives

1. To develop an online system to reduce superbug problem in Bangladesh.

3. To provide online doctor verification system.

4. To get online medication and mentorship from authorized doctor.

5. Get better health prescription from authorized doctor.

6. Reduce antibiotic medicine sell without any authorized prescription.

7. Increase people health safe.

1. Access this system by role wise.

3. Login as Doctor Role

10. User Info

1.7 Organization of Report

Finally, Fifth Chapter, we introduce conclusion and prospective future scopes.

2.2 Existing System

• Drugs details (Indications, Dosage administrations, Contraindications, Side ef-

• Search Drugs (Search by Brand name, Generic name or Condition).

• Drugs by Brands (A-Z brands).

• Drugs by Generics (A-Z generics).

• Favourite Drugs (Bookmark any brand names).

• Medical events (Information of international medical events).

• Feedback (Can directly post your valuable suggestion, advice comments).

• Advance search (Can choose different search categories).

Figure 2.1: DIMS App

Features of BMDC [44]

• It registers doctors to practice in Bangladesh, in order to protect and promote the

• Verify a doctor using doctor registration number.

• Recognition of Medical and Dental Qualifications granted by Medical and Dental