Smart Online Physician: Submitted by

Smart Online Physician
BS(CS) Session: 2014–2018
Submitted by
Hamza Javed
(Reg. No: 2014-BSCS-172)
Roll No: 48
Hamza Zulfiqar
(Reg. No: 2014-BSCS-1)
Roll No: 56
Project Supervisor
Dr. Zahid Mahmood
(Assistant Professor)
Department of Computer Science & Information Technology

University of the Poonch Rawalakot (UPR)
University of the Poonch Rawalakot
Department of Computer Science and
Information Technology
FINAL APPROVAL
This is to certify that we have read the project report submitted by Hamza Javed (Reg. No:
2014-BSCS-172) & Hamza Zulfiqar (Reg. No: 2014-BSCS-179). It is our judgment that this
report is of sufficient standard to warrant its acceptance by The University of Poonch
Rawalakot, Faculty of Basic & Applied Sciences for BS in Computer Sciences.
COMMITTEE:
1. External Examiner ___________________________
Mr.Muhammad Yasir Shabir
Lecturer,
Department of CS & IT
University of Kotli AJK
2. Supervisor ___________________________
Dr. Zahid Mahmood
Assistant Professor,
3. Chairman ___________________________
Dr. Adnan Idris
Chairman,
DECLARATION
We hereby declare that this application is not as a whole a part of any existing system. This
system is neither copied from any source. It is further declared that, we have developed this
application entirely on the basis of our personal efforts made under the sincere guidance of
my teachers and supervisor. No code based portion of the project is presented in this report
has been submitted in support of any other degree or qualification of this or any other
university or institute of learning. If any part of this application proved to be copied or found
to a report of some other, we shall stand by the consequences. Some API portion of the work
presented in this report has also been submitted in support of another application of some
universities. We further declare that this application and all associated documents, reports,
and records are submitted as partial requirement for the degree of BS(CS).
Member’s Signature
Hamza Javed: Hamza Zulfiqar:
Smart Online Physician Roll Number 48 & 56 BSCS 2014-2018 III

ACKNOWLEDGEMENT
First of all, we would like to extend our sincere and humble gratitude to Almighty Allah for
giving us the Insight and Intellect to carry out this project. It is indeed with the blessings of
ALMIGHTY ALLAH that we have been able to successfully complete this work, for which
we shall always remain humbly grateful.
We are grateful to our all teachers for their continuous assistance, inspiration and patience.
Their ability of management and foresightedness taught us a lot of things, which will be more
helpful for us in our practical life. They always remained a source of learning for us.
It is our bounden duty to pay tributes to our worthy teachers and staff members of
‘Department of Computer Science Rawalakot for paying us right guidance throughout our
project and prompted us to finish the job in time.
We are indebted to our parents, brothers and other family members for their deep prayers and
moral & financial support during our studies.
At the end how can we forget to thank all of our class fellows for their cooperation and help.
Their enjoyable company was really a great source of pleasure for us at university campus
and we always feel the presence of their well wishes for us.
Hamza Javed
&
Hamza Zulfiqar
Smart Online Physician Roll Number 48 & 56 BSCS 2014-2018 IV

Project Description
Project Title Smart Online Physician
Objective The project “Smart Online Physician” is like online doctor

application. This system will help the people know about their
diseases and will provide them proper medicines. Basically this
application will be helpful for those people who faces
difficulties to reach hospitals.
Developed By Hamza Javed Roll No: 48

Hamza Zulfiqar Roll No : 56
Supervised By Dr.Zahid Mahmood (Assistant Professor)
Tool Used Java

XML
JDK
Android Studio
SQLite
Php MySQL
Apache server
Adobe Illustrator
Adobe Photoshop
Operating system Microsoft Windows 10.
System Used Core i5, 6 GB RAM , 500 GB HD.
Smart Online Physician Roll Number 48 & 56 BSCS 2014-2018 V

ABSTRACT
Smart Online Physician is an android application to enable the patients living in remotely
areas such as Azad Jammu and Kashmir where lack of road infrastructure and mountainous
geography can quickly take the physical exam using proposed application.
Through this application, patients can get help using mobile computing technology for their
health issues. A system admin can verify, manage, and forward request to related physician.
The system also leverages user security by providing system logins. The system is developed
using state of the art dynamic technologies like Java, XML, JDK, Android Studio, Firebase
SQL database etc.
Smart Online Physician Roll Number 48 & 56 BSCS 2014-2018 VI

Table of Contents
CHAPTER 1 INTRODUCTION ......................................................................................... XI

1. Introduction .................................................................................................................................................... 2
1.1 Brief Introduction..................................................................................................................................... 2
1.2 Problem Definition................................................................................................................................... 2
1.3 Proposed Solution .................................................................................................................................... 3
1.4 Scope ........................................................................................................................................................ 4
1.5 Purpose .................................................................................................................................................... 5
CHAPTER 2 SYSTEM ANALYSIS ................................................................................... VI

2. System Analysis ............................................................................................................................................. 5
2.1 Introduction ............................................................................................................................................. 5
2.2 Requirements Analysis ............................................................................................................................. 5
2.3 Functional Requirements: ........................................................................................................................ 5
2.3 Non-Functional Requirements ................................................................................................................. 6
2.4 Software and Hardware Requirements .................................................................................................... 7
2.5 Use case Diagram .................................................................................................................................... 8
2.5 Use Case Description .............................................................................................................................. 9
2.6 Activity diagram: ................................................................................................................................... 20
CHAPTER 3 SYSTEM DESIGN ...................................................................................XXIV

3. System Design .............................................................................................................................................. 25
3.1 System Design ........................................................................................................................................ 25
3.2 Sequence Diagram ................................................................................................................................. 25
3.2 Class diagram ........................................................................................................................................ 33
3.3 Entity Relation Diagram ........................................................................................................................ 34
CHAPTER 4 IMPLEMENTATION ............................................................................ XXXV

4. Implementation ............................................................................................................................................ 36
4.1 Operating System Selection ................................................................................................................... 36
4.2 Programing Language Selection ........................................................................................................... 36
4.3 Commenting Code.................................................................................................................................. 37
4.4 Naming Convention ............................................................................................................................... 37
CHAPTER 5 SYSTEM TESTING ...........................................................................XXXVIII

5. Testing .......................................................................................................................................................... 39
5.1 Unit Testing............................................................................................................................................ 39
5.2 Interface Testing .................................................................................................................................... 39
5.3 Module testing........................................................................................................................................ 40
5.4 Integration testing .................................................................................................................................. 40
5.5 Evaluation .............................................................................................................................................. 40
5.6 Achievements ......................................................................................................................................... 40
CHAPTER 6 CONCLUSION ............................................................................................... 46

6. Conclusion.................................................................................................................................................... 47
CHAPTER 7. APPENDIX .................................................................................................... 48

7. Screen Shots ................................................................................................................................................. 49
Smart Online Physician Roll Number 48 & 56 BSCS 2014-2018 VII

Table of Contents
CHAPTER 8. REFERENCES .............................................................................................. 55

8. References: ................................................................................................................................................... 56
Smart Online Physician Roll Number 48 & 56 BSCS 2014-2018 VIII

List of Figures
FIG 1.2 PROPOSE SOLUTION SCENARIO .................................................................................................. 4

FIG 2.5 USE CASE DIAGRAM .......................................................................................................................... 8
FIGURE 2.6.1 SIGNUP ACTIVITY: ............................................................................................................... 20
FIGURE 2.6.2 LOGIN ACTIVITY................................................................................................................... 21
FIGURE 6.3 CHECKUP ACTIVITY ............................................................................................................... 22
FIGURE 2.6.4 DELETE PATIENT ACTIVITY ............................................................................................. 23
FIG 3.1.1 SIGN UP ............................................................................................................................................. 26
FIG 3.1.2 LOGIN ................................................................................................................................................ 27
FIG 3.1.3 CHECKUP ......................................................................................................................................... 28
FIG 3.1.5 ACTIVE DOCTOR ........................................................................................................................... 29
FIG 3.1.5 DE ACTIVE DOCTOR ..................................................................................................................... 30
FIG 3.1.6 VIEW USERS .................................................................................................................................... 31
FIG 3.1.7 VIEW POSTS .................................................................................................................................... 32
FIG 3.2 CLASS DIAGRAM .............................................................................................................................. 33
FIG 3.3 ENTITY RELATION DIAGRAM ...................................................................................................... 34
FIG 7.1 HOME PAGE ....................................................................................................................................... 49
FIG 7.2 PATIENT HOME ................................................................................................................................. 49
FIG 7.3 DOCTOE HOME ................................................................................................................................. 50
FIG 7.4 ADMIN HOME..................................................................................................................................... 50
FIG 7.5 SYMTOM FORM................................................................................................................................. 51
FIG 7.6 REPORTS ............................................................................................................................................. 51
FIG 7.7 POSTS ................................................................................................................................................... 52
FIG 7.8 ADD POST ............................................................................................................................................ 52
FIG 7.9 UPDATE POST .................................................................................................................................... 53
FIG 7.10 DELETE POST................................................................................................................................... 53
FIG 7.11 DOCTOR LIST................................................................................................................................... 54
FIG 7.12 PATIENT LIST .................................................................................................................................. 54
Smart Online Physician Roll Number 48 & 56 BSCS 2014-2018 IX

List of Tables
TABLE 2.5.1 USE CASE - 01 (ADMIN LOGIN) .............................................................................................. 9

TABLE 2.5.2 USE CASE - 02 (USER SIGN UP) ............................................................................................. 10
TABLE 2.5.3 USE CASE - 03 (USER LOGIN) ................................................................................................ 11
TABLE 2.5.4 USE CASE-04(UPDATE PASSWORD) .................................................................................... 12
TABLE 2.5.5 USE CASE-05 (DELETE USER) ............................................................................................... 12
TABLE 2.5.6 USE CASE-06 (LOG OUT) ........................................................................................................ 14
TABLE 2.5.7 USE CASE -07 (FILL FORM) ................................................................................................... 15
TABLE 2.5.8 USE CASE - 08 (COMMENTS)................................................................................................. 16
TABLE 5.6.1 TC-01 (USER AUTHENTICATION)........................................................................................ 41
TABLE 5.6.2 TC-02 (UPDATE USER) ............................................................................................................ 41
TABLE 5.6.3 TC-03 (USER SIGNUP) .............................................................................................................. 41
TABLE 5.6.4 TC-04 (ACTIVE DOCTOR) ...................................................................................................... 41
TABLE 5.6.5 TC-05 (DE-ACTIVE DOCTOR) ............................................................................................... 41
Smart Online Physician Roll Number 48 & 56 BSCS 2014-2018 X

Chapter 1 Introduction
1. Introduction
1.1 Brief Introduction

Mobile computing is an emerging and more interactive technology with respect to advance
functionalities based on end users requirements. The system aims to provide the basic health
facilities to patient in emergency situation. In mountainous areas like Kashmir people where
residential are facing many problems while consulting doctors, there are lack of hospitals
with very few facilities, bad road conditions and patient have to travel long distance and
reach the hospital which is wastage of time, expensive and risky in emergency cases. In the
cities people having very busy life and due to many other issues the health consultation is
became major problem.
At that time every system switches to automation. We take a first step toward the automation
of health consultation system. In the future it may be possible that this system will completely
replace the need of doctor with the involvement of artificial intelligence. The system’s user
must have registered as a member of this system and filling a symptom form and other
measures like (BP level, Sugar level) send it to the system and got response from medical
data set and doctor, this system will also provide a proper medicine for that disease.
1.2 Problem Definition

In remote areas like Kashmir people have to face many problems while consulting doctors,
there are lacks of hospitals with very few facilities, bad road conditions and patient have to
travel too large to reach the hospital which is wastage of time, expensive and risky in
emergency cases. In the cities people having very busy life and due to many other issues the
health consultation is became major problem.
1.2.1 Problem Scenario

In manual system there are many problems, traveling problem, financial problem,
appointment problem, traffic problem and many more. There can be emergency situation and
due to these problems, patient can die. Following fig shows some problems in manual
system. This figure shows that there is heavy traffic jam patient have to wait too long,
Smart Online Physician Roll Number 48 & 56 BSCS 2014-2018 2

condition of road is not good, Patient have to wait in long queues, high doctor fee and lot
more problems.
Fig 1.1 Problem scenario
1.3 Proposed Solution

We design an android application to facilitate people which will get symptoms from people,
application will compare data with database and generate a report and forward to specialist
for authentication. Doctor authenticates it and patient can receive report about disease and
proper medicine and take the medicines suggested by system.
1.3.1 Proposed Solution Scenario

We developed an android app that manages all this process. In figure 3.1 we graphically
presented a solution for this problem. The patient having medical devices for measuring
different levels e.g. blood pressure level, sugar level and lot more. The user must have our
app “Smart Online Physician” in his smart device. The user first registered into the system
by filling some basics information then he can login by entering email id and password.

This app provides a form for entering symptoms and different levels. After measuring
symptoms with medical devices user fill the form provided by app and click on send button,
this record is then send to the database compare with medical data set. Database then generate
a report and send this report and patient form to the registered doctor for further
authentication. Doctor then authenticate the report and can give more suggestion,
recommendation, some other test and medicines. The database gets learning for next time.
The patient can then follow the advice. The patient can give feedback about the performance
of our app and new user can check the top rated solutions and try that.
Fig 1.2 Propose Solution scenario
1.4 Scope
The system user must have registered as member. The Patient get login to the system and can
enter their symptoms (blood pressure, sugar level, blood pressure, temperature etc.) and
submit. App can compare patient record with database and generate report and furthermore
send patient symptom’s report and database report to registered Doctor and then doctor can
authenticate this database’s medical report and generate own. Doctor can also refer case to
another specialist doctor.

1.5 Purpose
Purpose of this app is to facilitate people living in cities or in mountain areas who face many
difficulties in health consultation. People can get medical help at door step. Facilitate poor
people who cannot pay doctor fee and cannot afford other expenses. Also to get fast results
about diseases.

Chapter 2 System Analysis
2. System Analysis
2.1 Introduction
In the life of the software development, problem analysis provides a base line for design and
development phase. The problem is analyzed so that sufficient matter is provided to design a
new system. Large problems are sub-divided into smaller one to make more understandable
units, which are easy for finding solutions. Similarly, in this project all the tasks are sub-
divided and categorized into sub-units and tasks.
2.2 Requirements Analysis

The following section presents the complete set of functional and non-functional
requirements identified for smart move. Functional requirements are listed first, according to
the relationship to the overall system. The non-functional requirements that pertain to safety,
security, accuracy, reliability, accessibility, usability, maintenance and performance are also
considered.
2.3 Functional Requirements:

The functional requirements of the system describe the functionality or services that the
system is expected as provide.
ID Requirement Description
Admin
REQ-1 Login Admin will be login.
REQ-2 Logout Admin will be logout
REQ-3 Approve/disapprove doctors Admin can change status of doctors.
REQ-4 View Users Admin can view users.
REQ-5 Delete Users Admin can delete selected users
REQ-11 Update medical Admin can update medical data.
REQ-12 Manage posts Add and delete posts.
Patient
REQ-13 Signup User can sign up.
REQ-14 Log in / Logout User can log in and logout.
REQ-15 View/give comment User can view and send comments.
REQ-16 Contact doctor User can contact doctor.
REQ-17 Feedback User can give feedback about doctor.
REQ-18 View Notifications User can view notifications

ID Requirement Description
Doctor
REQ-19 Log in / Logout Doctor can login and logout.
REQ-20 View/update report Doctor can View/update report
REQ-21 Comment Doctor can view and give comment .
REQ-22 View Notifications User can view notifications
2.3 Non-Functional Requirements

Non-functional requirements are the quality requirements that stipulate how well a software
does what it has to do. These are Quality attributes of any system; these can be seen at the
execution of the system and they can also be the part of the system architecture.
2.3.1 Accuracy:
The system will be accurate and reliable based on the design architecture. If there is any
problem in the accuracy, then the system will provide alternative ways to solve the problem.
2.3.2 Usability:
The proposed system will be simple and easy to use by the users. The users will comfort in
order to communicate with the system. The user will be provided with an easy interface of
the system.
2.3.3 Accessibility:
The system will be accessible through internet.
2.3.4 Performance:
The system performance will be at its best when performing the functionality of the system.
2.3.5 Reliability:
The system will be reliable in all circumstances and if there is any problem that will be
affectively handle in the design.
2.3.5 Security:
The proposed system will be highly secured; every user will be required registration to use
the system. The system will do the proper authorization and authentication of the users based

on their types and their requirements. The proposed system will be designed persistently to
avoid any misuse of the application. There is no restriction on read access.
2.4 Software and Hardware Requirements
2.4.1 Software Requirements

Following software are used in development of Smart Move application.
 Android Studio
 Google API’s
 Java 1.6 runtime
 Android Emulator
 Adobe Photoshop CS7
2.4.1 Hardware Requirements

The recommended hardware specified by the respective software would suffice the needs.
The estimated hardware requirements are as specified.
 Processing speed of 1.6 GHz
 2GB of RAM
 Android OS based Smartphone and tab

2.5 Use case Diagram

Use Case Diagram is a graphical representation that describes how users will interact with the
system.
Fig 2.5 Use case Diagram

2.5 Use Case Description

Table 2.5.1 Use Case - 01 (Admin Login)
Use Case ID UC-01
Use Case Name Admin Login
Scope Smart Online Physician
Level Admin Goal
Primary Actors Admin
Pre-Condition Actors should have accessed the system.
Post-Condition Actors successfully perform their operations.
Main success-scenarios Actor Action System Action
Scenario-01 The user has the ability to login to the system to be

able to use it.
1) Admin presses login
to the system 2) System asks for
3) Admin provides following information
asked information  Username
4) Admin hits the  Password
“Login” button 5) System successfully
login the admin
2a) If Username or Password is incorrect.

Extension and Alternatives
2a.1) Re-enter username/ password.
Frequency Frequent.

Table 2.5.2 Use Case - 02 (User Sign Up)
Use Case ID UC-02
Use Case Name User Sign Up
Level User Goal
Primary Actors Patient
Actors successfully perform their

Post-Condition
operations.
Scenario-01 The Patient has ability to join the system as

a new user.
2) System asks for the
1) Patient requests following information
the system to create  CNIC
new account as  Name
new User.  Age
3) Patient provides  Address
asked information.  Username
4) Patient presses  Password
“Create”. 5) System creates
new account for User
6) User is now
activated
2a) If User already exits.
2a.1) Re-enter different username.
Frequency Frequent.

Table 2.5.3 Use Case - 03 (User Login)
Use Case ID UC-03
Use Case Name User Login
Level User Goal
Primary Actors User
Scenario-01 The user has the ability to login to the system to be

able to use it.
1) User presses login to
the system. 2) System asks for
3) User provides asked following information
information.  Username
4) User hits the “Login”  Password
button. 5) System successfully
login the admin
2a) If Username or Password is incorrect.

2a.1) Re-enter username/ password.
Frequency Frequent.

Table 2.5.4 Use Case-04(Update Password)
Use Case ID UC-04

Use Case Name Update Password
Level Admin Goal /User Goal
Primary Actors Admin / User
Post-Condition Actors successfully perform their

operations.
Scenario-01 The user will have the ability to Update

his/her Profile
1) User presses Edit 2) System shows
button to the system. various information
3) User UPDATE fields like: -
required values.  Username
4) User hits the  Old Password
“Update” button.  New Password
 Confirm
Password
5) System update
profile
Extension and Alternatives Not Applied
Frequency Frequent.

Table 2.5.5 Use Case-05 (Delete User)
Use Case ID UC-05
Use Case Name Delete User
Level Admin Goal
Scenario-01
The admin can delete user profile
1) Admin selects the

user and & presses
Delete to the 2) System delete the
system. record.
Frequency Frequent.

Table 2.5.6 Use Case-06 (Log Out)
Use Case ID UC-06
Use Case Name Logout
Level Admin / User Goal
Primary Actors Admin / User

Post-Condition
operations.
Scenario-01 System provides opportunity of sign out

from system.
1) Admin requests
3) System
the system for log
successfully
out by pressing
performs the
button “Logout”.
action to logout.
Extension and Alternatives Not Applied.
Frequency Frequent.

Table 2.5.7 Use Case -07 (Fill Form)
Use Case ID UC-07
Use Case Name Fill Form
Level Patient Goal
Primary Actors Patient
Pre-Condition Actors should have logged in.

Post-Condition
operations.
Scenario-01 System allows patient to fill form for

exam.
2) System asks for
1) Patient requests
the various
the system to take
information i.e.
physical exam.
 BP
3) Patient provides
 HB
asked information.
 Symptoms
4) Patient presses
 etc.
“Add” button.
5) System matches
it with database and
give result.
Frequency Frequent.

Table 2.5.8 Use Case - 08 (Feedback)
UC-08
Use Case Name Feedback
Level User / Admin Goal
Primary Actors Patient/ Doctor
Pre-Condition User must logged in.

Post-Condition
operations.
System allows user to add comments /

Scenario-01
feedback and allow admin to replay on
specific comment or question
1) User enter the
desired comments
3) User presses 2) System adds
“Add” button. comments or reply
Frequency Frequent.

Table 2.5.5 Use Case-09 (Active Doctor)
Use Case ID UC-09
Use Case Name Active Doctor
Level Admin Goal
Scenario-01
The admin can Active Doctor
4) Admin selects the

doctor and &
presses Active 5) System make the
button. doctor Active.
Frequency Frequent.

Table 2.5.5 Use Case-10 (De-Active Doctor)
Use Case ID UC-10
Use Case Name De-Active Doctor
Level Admin Goal
Scenario-01 The admin can De-Active the Doctor.
6) Admin selects the 7) System de-active

Doctor and & the doctor.
presses de-active
button.
Frequency Frequent.

Table 2.5.5 Use Case-11 (Update report)
Use Case ID UC-11
Use Case Name Active Doctor
Level Admin Goal
Primary Actors Doctor
Scenario-01 The Doctor can Update the Report
8) Doctor selects the 9) System updated

report and make the report and
changes. send it to the
patient.
Frequency Frequent.

2.6 Activity diagram:

Activity diagram is another important diagram in UML to describe dynamic aspects of the
system. Activity diagram is basically a flow chart to represent the flow form one activity to
another activity. The activity can be described as an operation of the system.
So the control flow is drawn from one operation to another. This flow can be sequential,
branched or concurrent. Activity diagrams deals with all type of flow control by using
different elements like fork, join etc.
2.6.1 Signup Activity:
Figure 2.6.1 Signup Activity:

2.6.2 Login Activity
Figure 2.6.2 Login Activity

2.6.3 Checkup Activity
Figure 6.3 Checkup Activity

2.6.4 Delete Patient Activity
Figure 2.6.4 Delete Patient Activity

Chapter 3 System Design
3. System Design
3.1 System Design

System design is the process of expanding what was learned during domain analysis into a
working implementation. Design implementation that will carry out the system charter and
lead to reuse among many systems.
In design mode we give shape to our components of implementation. In structure analysis
these are the entities of our system. The design phase is most important part of any software
development. Any error at this stage may lead to system failure at the end. Designers have
developed a set of design rules that can be reapplied during the design of new applications.
3.2 Sequence Diagram

UML sequence diagrams are used to show how objects interact in a given situation. An
important characteristic of a sequence diagram is that time passes from top to bottom: the
interaction starts near the top of the diagram and ends at the bottom (i.e. Lower equals later).
Sequence Diagram (SD) is one of the key notations of UML and serves as a well-accepted
media among software developers, stakeholders, and tool builders. The appeal can be
attributed to the intuitive nature of its graphical representation and its capability to capture
scenarios of how the system might be used or how entities interact by transmitting sequences
of Messages.
Smart Online Physician Roll Number 48 & 56 BSCS 2014-2018

25
3.1.1 Sign Up:
Fig 3.1.1 Sign Up

26
3.1.2 Login:
Fig 3.1.2 Login

27
3.1.3 Checkup:
Fig 3.1.3 Checkup

28
3.1.4 Active Doctor:
Fig 3.1.5 Active Doctor

29
3.1.5 De Active Doctor:
Fig 3.1.5 De Active Doctor

30
3.1.6 View Users:
Fig 3.1.6 View Users

31
3.1.7 View Posts:
Fig 3.1.7 View Posts

32
3.2 Class diagram

The class diagram is a static diagram. It represents the static view of an application. Class
diagram is not only used for visualizing, describing and documenting different aspects of a
system but also for constructing executable code of the software application.
The class diagram describes the attributes and operations of a class and also the constraints
imposed on the system. The class diagrams are widely used in the modelling of object
oriented systems because they are the only UML diagrams which can be mapped directly
with object oriented languages.The class diagram shows a collection of classes, interfaces,
associations, collaborations and constraints. It is also known as a structural diagram.
Fig 3.2 Class Diagram

33
3.3 Entity Relation 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.
At first glance an entity relationship diagram looks very much like a flowchart. It is the
specialized symbols, and the meanings of those symbols, that make it unique.
Fig 3.3 Entity Relation Diagram

34
Chapter 4 Implementation
4. Implementation
The implementation phase of a project starts after design phase. During this phase a design is
converted into working software. The software is developed in such a way so that it can meet
the requirements and specifications of the users. The implementation of any system is
converted with the tool used in the development work and the component used to implement
the system.
The process of assuring that the system is operational and then allowing users to take over its
operation for the use and evaluation is called implementation. Here, system means new
system, which is going to be implemented. The new system needs to be implemented because
the old system was manual therefore there is always room for improvement of the system.
System implementation involves following key features:
 Operating system selection

 Tool selection
 Language selection
 Commenting code
 Naming conventions
4.1 Operating System Selection

Windows 7 selected as development platform as it is University’s standard and later the
system will be implemented on the same operating system. So, it is better to use it at
development time for ease enhancement and later compatibility.
Microsoft Windows 7 is a powerful multitasking operating system. Its ease of use, flexibility
and communication services increase its demand. Microsoft Windows 7 delivers seamless
integration with one platform for communication. It is the most flexible operating system
working with wide variety of client operating systems.
4.2 Programing Language Selection

With places API we are able to explore the world around the particular point. The places API
provide the comprehensive location data all over the globe but this data is not in a readable

36
format for an android device we have converted this raw data into JSON format and then
separated different places data. After separating the different places data, we have converted
data into place data and URL data then display the data of particular interested places around
the particular point.
4.3 Commenting Code

Understanding of where and how to comment your code is important. Commenting code
describe the functions and statements properly that help others to understand the concept of
statements for further enhancements. Comments help us to understand what is to be done. It
is also very backward to write the code and then try to explain what it does. So, most of the
point is tired to make clear by explaining it in comments.
4.4 Naming Convention

It is necessary to follow a standard naming convention throughout the whole project during
the development, to make the code readable. The approach that is used is as follow:
4.4.1 Variable:
First letter of variable name represents the name of value or data it holds and first letter is
small and ‘_’ for each word in variable name.
4.4.2 Functions:
Function name start with the type of functionality it is doing and first letter of each word in
function name is small and ‘_’ for each word in function name.
4.4.3 Text Boxes:

The name of all text boxes represents the name of value or data it holds and first letter is
small and ‘_’ for each word in text box name.

37
Chapter 5 System Testing
5. Testing
Software testing is an empirical technical investigation conducted to provide stakeholders

with information about the quality of the product or service under test, with respect to the
context in which it is intended to operate.
System testing is an essentials step for the development of the reliable and error free system.
Testing is the process executing a problem with the explicit intention of finding errors i.e.
making the problem fail and test cases are devised with the purpose in mind. A test case is a
set of data items that the system processes as normal input. A successful test is one that has a
high probability of finding an as-yet undiscovered error. Testing involves exercising the
program using data like the real processed by the program.
Testing may be carried out during the implementation phase, to verify if the software behaves
as intended by its designer, or after the completion of its implementation phase. There are
many approaches to software testing.
 Unit testing
 Interface testing
 Integration testing
 Module testing
5.1 Unit Testing

Each and every module of the system was tested at individual component level to ensure that
system operates correctly. Testing of these modules involved various steps:
Validation checks were confirmed on each item after the data was entered.
Functionality of each button was successfully tested.
5.2 Interface Testing

Interface testing ensures that proper links are operational and everything is displayed
according to the requirement of the system. Interface testing involved many steps:
Fonts size and font name were checked against the guidelines laid by the University.

It was checked that every meaningful word in prompt/any alert message displayed started
with a capital letter.
5.3 Module testing

A module is a collection of dependent components. In module testing, related units are
integrated in a module and tested for their proper functionality together. Various modules
were tested, by passing data/signal between them.
5.4 Integration testing

All the components module of the system was put to integrated testing and were found
working successfully.
5.5 Evaluation
Evaluation of the system means to examine what goals are achieved by the system and what
are the weaknesses and the deficiencies left behind. Evaluation is the final step in the
development by any system. This phase is for the purpose of reviewing whether objectives
and functional requirements of the Univ. are fulfilled or not.
5.6 Achievements
 Software provides the password protected GUI to facilitate the user to use the system.
 In all modules of the system, data is properly adding, delete and update.
 All verification and validation checks work properly.
 System is satisfying almost all of its major specifications and functionality and it can
be concluded that system is satisfying its more than 90% scope.

Table 5.6.1TC-01 (Login)
Test Case ID: TC- SOP-001 Test Item: User authentication

Author: Hamza Doc-Date:10 Dec 2018
Test Type: Manual-black box. Test Case Name: Login
Component: User authentication facility Release Version:1.0
Test Case Description: The test case will determine the current functionality of user authentication
Pre-Condition Post Condition
User should have his own email and password. System successfully authorized the user to use system.
Input Data/Event Expected output Data
Enter email and password. User should be login successfully.
Actual Input Data/Event Actual Output Data/Event
Enter “hamza5656@gmail.com” as email

And “12345” as password. Successfully login.
Click on “Sign in” button.
Enter “ahmad5593@yahoo.com” as email

And “123456” as password. Successfully login.
Enter “hamza” as email and “12345” as password. Login Failed.

Enter “ahmad” as phone no and “ahmad123” as

password. Login Failed.
Test Case Result

Test is performed successfully.

Table 5.6.2 TC-02 (Update user name and password)
Test Item: User update his/her

Test Case ID: TC- SOP-002 username & password
Author: Hamza Doc-Date: 10 Dec 2018
Test Type: Manual-black box. Test Case Name: Update Username/
Component: User authentication facility Password
Release Version: 1.0
Test Case Description: The test case will determine the correct functionality of user
authentication and update his/her username and password.
System successfully authorized the user

User should have sign in successfully.
to use system.

In case of User page Successfully Update his/her Username
Login to system and Password
Test Case Result
Click on “Edit” button. Successfully Update Username and

Click on “Save” button. Password
Test Case Result

Table 5.6.3 TC-03 (User Signup)
Test Case ID: TC- SOP-003 Test Item: User Signup

Author: Hamza Doc-Date: 10 Dec 2018
Test Type: Manual-black box. Test Case Name: User Signup
Component:
Test User authentication
Case Description: facility
The test case Release
will determine Version:
the correct 1.0
functionality of
login
Operation Procedure: In case of User Signup
Enter Full Name, email, username, password ,weight, age
Click on Save button
Admin authorized to add the user record User is successfully added in the
system.
In case of User Signup
Enter email, username, password, weight
Successfully Created User Profile
and age
Test Case Result
Enter email, username, password, weight and

User Account Successfully
age
Created
Enter username, password, weight and age System shows the error message
Click on Save button that email must be entered
Enter username, email, weight and age System shows the error message
Click on Save button that password must be entered

Table 5.6.4 TC-04 (Active Doctor)
Test Case ID: TC- SOP-004 Test Item: Doctor Activation

Test Type: Manual-black box. Test Case Name: Active Doctor
Component: Doctor Activation facility Release Version: 1.0
Test Case Description: The test case will determine the current functionality of Doctor Activation
Admin should choose which doctor to active.
System successfully active the doctor.
Choose the doctor and click on active button. Doctor should be activated successfully.

Choose the doctor Dr. Sajid and
Click on “Active” button. Successfully Activated.
Choose the doctor Dr. Amjad and Successfully Activated.

Click on “Active” button.
Choose the doctor Dr. Iqbal and Already Active.

Click on “Active” button.
Test Case Result

Table 5.6.5 TC-05 (De-Active Doctor)
Test Case ID: TC- SOP-005 Test Item: Doctor deactivation

Test Type: Manual-black box. Test Case Name: De-Active Doctor
Component: Doctor deactivation facility Release Version: 1.0
Test Case Description: The test case will determine the current functionality of Doctor deactivation
Admin should choose which doctor to de-active.
System successfully de-active the doctor.
Choose the doctor and click on de-active button.

Doctor should be de- activated successfully.
Choose the doctor Dr. Mumtaz and
Click on “De-Active” button. Successfully De-Activated.
Choose the doctor Dr. Kabeer and Successfully De-Activated.

Click on “De-Active” button.
Choose the doctor Dr. Shafique and Already De-Active.

Click on “De-Active” button.
Test Case Result

Chapter 6 Conclusion
Chapter 6 Conclusion
6. Conclusion
In remote areas like Kashmir people have to face many problems while consulting doctors,
there are lack of hospitals with very few facilities, bad road conditions and patient have to
travel too large to reach the hospital which is wastage of time, expensive and risky in
emergency cases. In cities people having very busy life and due to many other issues the
health consultation is became major problem. Our aim is to provide the basic facility to
patient in these situations. We are developing an android app that will remotely check the
patient at their homes. The patients don’t have to travel to long to hospital for checkup he or
she just fill the form provided by app and then send it to the specialist and receive doctor
report and recommendations for him. This app is totally free so any one can use it.

Chapter 7 Appendix
Chapter 7 Appendix
7. Screen Shots
Fig 7.1 Home page Fig 7.2 Patient home

Chapter 7 Appendix
Fig 7.3 Doctor home Fig 7.4 Admin home

Chapter 7 Appendix
Fig 7.5 Symtoms form Fig 7.6 Reports

Chapter 7 Appendix
Fig 7.7 Posts Fig 7.8 Add Post

Chapter 7 Appendix
Fig 7.9 Update Posts Fig 7.10 Delete Posts

Chapter 7 Appendix
Fig 7.11 Doctor list Fig 7.12 Patient list

Chapter 8 References
Chapter 8 References
8. References:
1. Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and
Iterative Development (3rd Edition)
2. https://developer.android.com/studio/index.html
3. https://stackoverflow.com
4. https://github.com
5. http://www.coreservlets.com/android-tutorial/
6. http://www.symtomchecker.com
7. http:/www.apache.org/
8. http:/www.php.net
9. http:/www.webdesign.com
10. http://json.org/
11. [IAN98] Richter Charles, “Software Engineering”, Tec media, 1998.
12. The Complete Android Guide. Geo Visualizer - Geographic Data Visualized on 30+
Maps.
13. The Complete Android Guide; Author(s) Kevin … Java.
14. The Complete Reference, 8th Edition. Java. The Complete Reference, 8th Edition. Home;
Categories. Adobe; Algorithms and Cryptography. In Java The Download Complete
Reference C++ eBook PDF.
15. [ROG00] Pressman Roger S., “Software Engineering a practitioner’s Approach, IEEE
Software, 2000.

Smart Online Physician: Submitted by

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Smart Online Physician: Submitted by

Hochgeladen von

Copyright:

Verfügbare Formate

Smart Online Physician

BS(CS) Session: 2014–2018

Department of Computer Science & Information Technology

Hamza Javed: Hamza Zulfiqar:

Smart Online Physician Roll Number 48 & 56 BSCS 2014-2018 III

Smart Online Physician Roll Number 48 & 56 BSCS 2014-2018 IV

Project Title Smart Online Physician

Objective The project “Smart Online Physician” is like online doctor

Developed By Hamza Javed Roll No: 48

Supervised By Dr.Zahid Mahmood (Assistant Professor)

Tool Used Java

System Used Core i5, 6 GB RAM , 500 GB HD.

Smart Online Physician Roll Number 48 & 56 BSCS 2014-2018 V

Smart Online Physician Roll Number 48 & 56 BSCS 2014-2018 VI

CHAPTER 1 INTRODUCTION ......................................................................................... XI

CHAPTER 2 SYSTEM ANALYSIS ................................................................................... VI

CHAPTER 3 SYSTEM DESIGN ...................................................................................XXIV

CHAPTER 4 IMPLEMENTATION ............................................................................ XXXV

CHAPTER 5 SYSTEM TESTING ...........................................................................XXXVIII

CHAPTER 6 CONCLUSION ............................................................................................... 46

CHAPTER 7. APPENDIX .................................................................................................... 48

Smart Online Physician Roll Number 48 & 56 BSCS 2014-2018 VII

CHAPTER 8. REFERENCES .............................................................................................. 55

Smart Online Physician Roll Number 48 & 56 BSCS 2014-2018 VIII

FIG 1.2 PROPOSE SOLUTION SCENARIO .................................................................................................. 4

Smart Online Physician Roll Number 48 & 56 BSCS 2014-2018 IX

TABLE 2.5.1 USE CASE - 01 (ADMIN LOGIN) .............................................................................................. 9

Smart Online Physician Roll Number 48 & 56 BSCS 2014-2018 X

1.1 Brief Introduction

1.2 Problem Definition

1.2.1 Problem Scenario

Smart Online Physician Roll Number 48 & 56 BSCS 2014-2018 2

Fig 1.1 Problem scenario

1.3 Proposed Solution

1.3.1 Proposed Solution Scenario

Smart Online Physician Roll Number 48 & 56 BSCS 2014-2018 3

Fig 1.2 Propose Solution scenario

Smart Online Physician Roll Number 48 & 56 BSCS 2014-2018 4

Smart Online Physician Roll Number 48 & 56 BSCS 2014-2018 5

2.2 Requirements Analysis

2.3 Functional Requirements:

Smart Online Physician Roll Number 48 & 56 BSCS 2014-2018 5

2.3 Non-Functional Requirements

Smart Online Physician Roll Number 48 & 56 BSCS 2014-2018 6

2.4 Software and Hardware Requirements

2.4.1 Software Requirements

2.4.1 Hardware Requirements

Smart Online Physician Roll Number 48 & 56 BSCS 2014-2018 7

2.5 Use case Diagram

Fig 2.5 Use case Diagram

Smart Online Physician Roll Number 48 & 56 BSCS 2014-2018 8

2.5 Use Case Description

Use Case ID UC-01

Use Case Name Admin Login

Scope Smart Online Physician

Level Admin Goal

Primary Actors Admin

Pre-Condition Actors should have accessed the system.

Post-Condition Actors successfully perform their operations.

Main success-scenarios Actor Action System Action

Scenario-01 The user has the ability to login to the system to be

2a) If Username or Password is incorrect.