Jordan university of science and technology

Faculty of Computer and Information Technology

Software Engineering Department

Project Management (SE491)

DR . health
Group member names

:Project members: ID
Mays Alreem Samer Al-Khasawneh 20130176032-1

2-Hadeel Jamal Al-Azzeh. 20130176078

3- Manar Jaradat. 20130176066

4- Haneen Rawasheda. 20130176071

5-Maisara Mohammad Aljarah. 20130171066

6- Lyth Basem Hishmeh. 20122175023

7-Laith Tahseen Othman. 20130174073

8- Mjd Abedullah Al-Attari. 20130176093

9-Hamza Kamel Almahameed. 20122175053

10- Sirhan Manhal Abdelqader. 20122175003

11-Mohammad Jamal Al-Khateeb. 20130176014

12-Saja Zaid Al-Omari 20130176067

 Part I
Planning and Analysis

Introduction

1.1 Abstract…………………………………………………………….
1.2 Motivation……………………………………………………………
1.3 Objective……………………………………………………………..
1.4 Problem definition………………………………………………………..
Methodology used – 1.5
..……………………………………………SDLC
Project Initiation & planning

2.1 Project Organization…………………………………………….

2.2 Scope…………………………………………………………………..
2.3 Feasibility…………………………………………………………….
2.4 Assumptions………………………………………………………...
2.5 Risks………………………………………………………………………
2.6 Constraints…………………………………………………………….
2.7 Project scheduling………………………………………………….
2.7 Gant Chart……………………………………………………………..
2.8 Estimation scheduling for the project…………………….
 Analysis

3.1 Techniques used to collect requirements…………………………

3.2 Business requirements……………………………………………………
3.3 User Requirements…………………………………………………………
3.4 Required Hardware and Infrastructure Devices……………..
3.5 System Requirements…………………………………………………….
3.6 Functional requirements………………………………………………..
3.7 Non Functional Requirements…………………………………………
3.8 Project Requirement Analysis…………………………………………

3.9 Process modeling

3.9.1 Data Flow Diagram (DFD)…………………………………….
3.9.2 Use Cases…………………………………………………………….

3.10 Logic Modeling

3.10.1 Structure English……………………………………
3.10.2 Decision table………………………………………..
3.10.3 Decision tree…………………………………………..
3.10.4 STD
3.11 Data Model
3.11.1 The ER Diagram of the Database…………….
3.11.2 The Relation of the Database…………………
 Part II
Technical Design and Implementation

Conceptual Design

1.1 System Components

Architecture Design

2.1 Architectural Design Strategy…………………………

2.2
2.3
Database Design

1.1 Infrastructure Logical Design

1.2 Infrastructure Physical Design
1.3 Detailed Description of the Database
1.4 Tables
1.5 Views
1.6 Stored Procedures

Interface Design

1.7 Forms
1.8 Reports
Tools and Technologies

2.1 Coding
2.2 Testing
Installation 2.3

Introduction
 Abstract 1.1

Dr. Health is a system for medical institutions that integrate the

pharmacy, opponents, financial, hospital system in one system to
serve the patient and physician monitor. And computerizes a large part
of patient-hospital interactions. It allows patients to schedule
appointments with physician monitor, submit their symptoms, and
receive prescriptions and medical bills.

It will take all personal and health information and record it, The
patients can access their electronic records free, views their
information, inquires about their conditions, the physician monitor
could access to patient record to diagnose the patient state and take
the decision ,and to keeps track of patient medical histories, Also,
keeps track of pharmaceutical supplies to help patient to know in
which pharmacy he/she could get the drug , allows pharmacies to
issue medication with received prescriptions and logs patient’s
.medical bills along with pharmaceutical ones

1.2 Motivation
 What actually motivate and inspire us to build Dr.health is this story

My name is Ahmad and I am a software engineer, I’ve worked for 30

.years in the US with a professional team

A few months ago, I’d decided to visit Jordan for the summer. I hadn’t
been home for a while and I’d been missing my family. A few days after
arriving, I caught a cold and decided to go to a hospital to get it
checked out. I didn’t have a file in the hospital I was visiting so I was
told I needed to make one. This took more than two hours, in between
waiting for managers’ approvals and having staff look for necessary
.forms and documents

During my next visit to the same hospital for a follow up, I arrived, told
the receptionist why I was there and gave her my name, only to be told
that they knew they had my file, but couldn’t find it. After waiting for
two hours, she came back and told me that they had found it, but that
they couldn’t give me an appointment because they were having
trouble with the appointment system and all the physician monitor’s
appointments had been mixed up, leaving more than 20 patients
.waiting in the lobby

After the initial disappointment wore off, I decided to ask the

receptionist a few questions about their management system and was
shocked at their paper system’s inefficiency. As a software engineer, I
.decided I would propose a solution to their problem

So, I decided to use my team to develop an improved, computerized

.system that integrated all of the procedures I had trouble with
1.3 Problem definition
There are many systems that were built to take care of the
patients and help the physician monitor to manage the treatment
process, until now when you go to the hospital you often waste a
lot of time waiting your turn to see your physician monitor, or in
receiving your medicine from the pharmacy, also The difficulty of
reaching cretin information's about the patience, Information's
and medical records of the patience not protected and does not
have any security authorization which means no privacy on it,
so that anyone can access it and could manipulate them, The
huge demand on paper and other tools which needs a big budget
.to cover the expenditures

Dr Heath will save your time and help physician monitors to diagnosis
their patient and give them a precise appointments for their condition
based on their description, also it allow the patients to view their
record and use them in other hospitals and clinics, and its facilities the
commutation between physician monitors and patients, allow the
patients to know the appropriate clinic so that he/she can find the
appropriate cure from his home.

1.4 Objective
The main objectives of this application is to reduce the effort and -1
time for patients to diagnose his/her health status without going to
..hospital and waiting for seeing physician monitor

Scheduling the appointment of patient with physician monitor to -2

.make it convenient for both easily

Facilitate the following up of the patient's status based on his/her -3

health records

Provide the ability to contact with doctor to describe what you -4

.are suffering

.Facilitate the medicine payment process -5

.Protecting the confidentiality of patient information -6

Educate members of the healthcare team in the use of -7

.technology

Providing consistent, high quality care to our diverse patient mix -8

.at any time

Improving the reliability and efficiency of practice operations and -9

.communication among clinicians and staff

Methodology used –SDLC

We used SDLC methodology- incremental model to develop our
project, this methodology is flexible and less costly to choose
scope and requirements, and so it would be very easy if you
want to add a new feature on the system during the
implementation phase, but the delivery of this new feature will
.be in the next iteration

:Another advantage for using incremental model is

1- very easy to manage risk because risky pieces are identified

and handled during its iteration.
2- it needs less number of people and adding quality is easy.

:So SDLC consist of

.Planning-1
.Analysis-2
.Design-3
.Implementation-4
.Maintenance-5
 Project Initiation & planning
Project Organization

. Our Project is done by a team content from 12 member

.We divide our group to 4 sub groups ,each group have 3 members

Each sub group should work together ,After that we gather all sub group work together
and extract the main and common idea . This technique to ensure the all group member
. involvement

. We have two activity in our project

The first one is development an desktop application named DR.Health ,So the system *
: consists of a series of steps

Planing-1

Analysis-2

Design-3

.Implementation-4

Testing-5

. Maintance-6
Project Organization chart
 Scope

The project consists of a main system which is divided into three subsystems:

Appointment & Patient Details Management system

Manages patient medical records, medical history, physician monitor
schedules, patient appointments, patient symptoms. Also allows physician
monitor to enter procedures done on patients and prescribed meds.

Financial System
Receives entries from the APDM System, Financial System, and Pharmacy
System, and produces a medical bill to be delivered to the patient and
insurance agencies (if applicable). Also tracks pharmacy stock and cash spent
on procurement of pharmaceuticals.

Pharmacy System
Prescribes meds to patients according to received electronic prescriptions.
Responsible for basic contraindications management between meds. Also
tracks available meds, prescribed meds and issues re-stock orders.

Scope Chart

This is a general overview of the interactions between the subsystems and of

the people who would routinely interact with the system
Scope Dimensions:

1. The Why dimension: A patient record management system that will

simplify the process of appointment scheduling, diagnosis, record
management and ease medication dispension.

2. The Who dimension: Defining those who will interact with the system:
a. Patients
b. General Practitioner Medical physician monitors
c. Specialized Medical Doctors
d. Financial administrators
e. Pharmacists

3. The What dimension: A system that will perform the following

functions:
a. Allow patients to schedule appointments
b. Keep track of physician monitors’ schedules
c. Allow simple and fast entry of patient procedures and prescribed
medication into the system
d. Keep track of patient's medical history
e. Keep track of available medications
f. Deliver restock required notifications
g. Issue restock requests
h. Issue medical bills to patients and insurance agencies
i. Issue printed reports with each dispensed medication indicating
usage, contraindications and side-effects
j. Allow patients to enter their symptoms into the system to be
reviewed by physician monitors
 Feasibility

Economic feasibility-1

In this project we weight the cost and the benefits associated with the
candidate system and if it suits the basic purpose of the organization i.e. profit
making, the financial and the economic questions during the preliminary
:investigation are verified to estimate the following

 The cost to conduct a full system investigation.

 The cost of hardware and software for the class of application being
considered.
 The benefits in the form of reduced cost.

So the system does not require enormous amount of money to be developed.

this can be done economically if planned well , so it is economically feasible.
.The cost of project depends upon the number of man hours required

Operational feasibility -2

we concern to make all requirement adorable and reachable to

solving the problem with least cost ,so the system is operationally
feasible as it very easy for the end users to operate it. It only needs basic
.information about Windows platform

Technical Feasibility-3

The project was developed in C# with windows form application. It provides the
high level of reliability, availability and compatibility. All these make C# an
.appropriate language for this project

Schedule study-4

Time evaluation is the most important consideration in the development of

project. The time schedule required for the developed of this project is very
important since more development time effect machine time, cost and cause
delay in the development of other systems. So the system can be developed in
.the considerable amount of time

Legal Feasibility -5
Our application complies with all laws and regulations and all information is
under the authority of the system administrator. So all the information is
.secured

Behavioal Feasibility-6

The system working is quite easy to use and learn due to its simple and
.attractive interfaces

Assumptions

 We assume that the patient has a SSN or password number.

 We assume that the patient have an internet connection.
 We assume that the patient insert a correct information.
 We assume that the patient follow up his account to receive the feedback from his
physician monitor.
 We assume that the physician monitor will respond to the patient within one
hour.
 We assume that the physician monitor will diagnose the patient based on his\her
information correctly.
 We assume that the each physician monitor have a username and password to
access the system.
 We assume that the physician monitor will choose the closer appointment to the
patient.
We assume that patience have computer , tablet, or any device support .
.Microsoft windows Macintosh operating system

 We assume that patience / physician monitor connected to the internet.

 We assume the user have email address and phone number and password.
 We assume that the application Running 24 hours in the day.
 We assume the patience can write a comment to the specialist physician monitor
describing any issues he she faced.
 We assume that the patience have identifying card such as passport , driving
license, family document .
 We assume that the application covered all pharmacy's that running in
computerized system.
 We assume that the application have backup or recovery system for certain
circumstance like system failure or system hacking.
 We assume that physician monitor well respond to the patience within 1 hour as a
maximum.
 We assume that the patience follow up his account to receive any feedback from
his physician monitor.
 Risks

How to manage and avoid the Probability Impact Risk

risk
low =1 (

)high =5

Make the application 1 High

.interfaces more interactive
Lack of users

3 High

Manage an expanding and Requirement change

changing set of
requirements, organize
requirements definitions for
each part of the project, and
more sophisticated
requirements management
.system

4 .Medium Difficulties with usage

The system shall be easy to

use, support a user friendly
GUI, and has a clear
.navigation

2 .High

Increase times of working Time underestimate

 Constraints

 Some departments in medical center is not supported in our system.

 Slow adoption of new technology by consumers.

 Lack of ownership and transportability by the consumer.

 Privacy and security issues.

 Poor application of health literacy principles in consumer interfaces.

 Lack of research in the utility and features that engage consumers.

 Low ease of use with low level of intuitive and personalized features.

 Lack of interoperability with medical records and use by health providers.

 the lack of use of the computer by 80 percent of the patients became an issue as
implementation progressed.

 No patient can be assigned to more the one physician monitor at the same time.

 Every physician monitor must present his/her schedule appointments

 Login and password is used for identification of user and there is no facility for
guests.
 Project scheduling

Gant Chart
 Estimation scheduling for the project

Time and cost estimates based on Function Points

To provide a rough estimate of the time and cost of the project,

we will provide figures detailing the time and cost of each
function point in the project.

Rough estimates for each subsystem

Man-hours required Cost (as a Function / Subsystem

percentag
e of total
project
cost in
time and
currency)

400 40% Appointment & Patient Detail

Management System

100 10% Login and sign up

100 10% Appointment entry and management

62.5 6.25% Symptoms management and tracking

62.5 6.25% Medical record management and

tracking

25 2.5% Cost calculation and transmission to

financial system

25 2.5% Medication calculation and

transmission to pharmaceutical system

25 2.5% Appointment slip generation and

transmission

300 30% Pharmacy System

70 7% Medication tracking

70 7% Prescription management and tracking

for each patient

70 7% Medication stock management

40 4% Medication procurement operations

20 2% Contraindication management

10 1% Error and exception handling and

management

20 2% Medication bill generation, processing

and transmission to financial
department

300 30% Financial System

50 5% Received medication and procedure

data processing and management

100 10% Patient finances tracking and

management

50 5% Bill generation, tracking and

management

33 3.3% Medication stock procurement

management and tracking

33 3.3% Report generation, tracking and

management

33 3.3% Procedure data tracking

1000 100% Total

Man-hours analysis

Our educated guess for the man-hours required to implement the

system, calculated as a sum of the estimated time required to
implement each function point after subtracting necessary
periods of inactivity and allowing for unexpected delays, are
about 1000 man hours. Each function point’s estimate is based on
imagined complexity and system-wide interactions.
 Time estimate in calendar months
Dividing the total man-hours over 3 groups of 4 people each, we
arrive at an estimate of 55 days after taking all factors into
consideration. Below is the work schedule.

Function / Group 1 Group 2 Group 3 Group 4 Number Period

Subsystem of hours of time
Appointment 100 100 100 100 400 15 Feb
& Patient -8 Mar
Detail (20
Management days)
System
Login and sign 20 20 20 20 100 15 Feb –
up 20 Feb
Appointment 20 20 20 20 100 21 Feb –
entry and 25 Feb
management

Symptoms 15.5 15.5 15.5 15.5 62.5 26 Feb –

management 1 Mar
and tracking
Medical record 15.5 15.5 15.5 15.5 62.5 2 Mar –
management 5 Mar
and tracking
Cost 6 6 6 6 25 6 Mar- 7
calculation and Mar
transmission to
financial
system
Medication 6 6 6 6 25 7 Mar – 8
calculation and Mar
transmission to
pharmaceutical
system
Appointment 6 6 6 6 25 8 Mar
slip generation
and
transmission
Pharmacy 75 75 75 75 300 9 Mar –
System 26 Mar
(17.5
days)
Medication 17.5 17.5 17.5 17.5 70 9 Mar
tracking -12 Mar
Prescription 17.5 17.5 17.5 17.5 70 12 Mar -
management 15 Mar
and tracking
for each
patient
Medication 17.5 17.5 17.5 17.5 70 15 Mar –
stock 18 Mar
management
Medication 10 10 10 10 40 19 Mar-
procurement 21 Mar
operations
Contraindicatio 5 5 5 5 20 22 Mar
n management
Error and 2.5 2.5 2.5 2.5 10 23 Mar
exception
handling and
management
Medication bill 10 10 10 10 20 24 Mar-
generation, 26 Mar
processing and
transmission to
financial
department
Financial 75 75 75 75 300 26 Mar-
System 10 April
(17.5da
ys)
Received 12.5 12.5 12.5 12.5 50 26 Mar-
medication and 28 Mar
procedure data
processing and
management
Patient 25 25 25 25 100 28 Mar-2
finances April
tracking and
management
Bill generation, 12.5 12.5 12.5 12.5 50 3 April -6
tracking and April
management
Medication 8.25 8.25 8.25 8.25 33 7 April-8
stock April
procurement
management
and tracking
Report 8.25 8.25 8.25 8.25 33 7 April-9
generation, April
tracking and
management
Procedure data 8.25 8.25 8.25 8.25 33 9 April
tracking -10 April
Total 250 250 250 250 1000 55 Days

Project monetary cost estimation in US dollars

At a rate of $70 per hour for each programmer, this totals out to $70,000.
Taking into consideration other expenses which would amount to about
$30,000, the final cost is calculated as $100,000.

Analysis

Techniques used to collect requirements

1- Brain storming

2- Search engine

3- Questioner
 Feedback form
Patient form

Thank you for taking the time to consider our questions ,your opinion is very important to
.us

Q1 )Do
you want to have system save your money
?and time
yes No

Q2 ) Does
your PHR system provide any protective
measures of patients information privacy and
?confidentiality
yes No

Q3 ) do
you want to have system help you
?getting your needed information
yes No

Q4 ) Does
our system facilitate appointment
? reservation

yes No

Q5 ) What
level of communication with the
medical stuff ?
High Good Low

Feedback form
physician monitor form

Thank you for taking the time to consider our questions ,your opinion is very important to
.us

?Q1 ) Do you want to have system help you to understand the patient correctly

yes No

Q2 ) Do you want to have system reduce the time it takes to diagnose and prescribe
?treatment

yes No

Q3 ) Does
the current system facilitate your
?business
yes No

Q4 ) What
level of communication with the
? medical patients
High Good Low

Patient form physician monitor

Sample=40 form
Sample=20

Question 1 yes No yes No

34 6 16 4
Question 2 yes No yes No
32 8 18 2
Question 3 yes No yes No
28 12 19 1
Question 4 yes No High 14
38 2
Moderate 3

Law 3
Question 5 High 26
Moderate 6
Law 8 X

: In conclusion
Our questioner s target physician monitors and Patients , We choose samples from each
.scales

. The first sample was include 40 Patients

We detect that 85% from patient see that the system will save their money and *
time ,80% from patients see that PHR system provide security Keys ,70% get their
. information and 65% see that communication with physician monitors get easier

.The last sample was include 20 physician monitors whose

we detect 80% from physician monitors need to have system help them to understand *
patient state correctly ,and 90% of them see that system reduce the time it takes to
. diagnose and prescribe treatment

Also,95% of them see that system facilitate their business and 70% see
. that make the communication with patients more easier

Based on the study we see that is need to develop system support physician monitors and
. patients need , so we start develop " DR.Health" system

Functional requirement

User Requirements
the patient shall be able to reserve an appointment for specific physician -1
. monitor

the patient shall be able to describe his/her status to the general physician -2
. monitors

the patient shall be able to buy the medicine -3

the patient shall be able to view the physician monitors' leisure time continuously -4
.

. the patient shall be able to see all alternative medicine and their affect -5

. the physician monitors shall be able to contact with his patient -6

the physician monitors shall be able to response to all patients questions -7

.immediately

the physician monitors shall be able to access to all his patients -8

.historical health record

The physician monitors will be able to categorize patients into various -9

risk levels so that the patient can have different priority-based
.treatments when an emergency occurs
 System Requirements
1- The system shall keep track of patient appointments.

2- The system shall allow the attending administrator to view

physician monitors’ schedules.

3- The system shall allow patients and physician monitors to

create accounts .

4- The system shall allow physician monitors to create

accounts.

5- The system shall verify patients’ identities by Verify

their
ID and password and allow them to access their accounts.

6- The system shall verify physician monitors’ identities by

Verify their ID and password and allow them to access their
accounts.

7- The system shall keep track of patients’ medical histories.

8- The system shall allow patients to enter their symptoms.

9- The system shall allow physician monitors to add each visit

to patients’ accounts.

10-The system will track will then track and store those
symptoms internally.

11-The system shall display available times and allow patients

to request appointments.

12- The system shall issue appointment slips.

13- The system shall allow the physician monitor to view

appointment requests and submitted symptoms.

14- The system shall allow the physician monitor to choose

from a list of specialists to forward the patient to.

15- The system shall allow physician monitors to input

procedures performed on the patients and prescribed
medications.
16- The system shall allow pharmaceuticals to be dispensed to the
patient based on physician input.

17-The system shall calculate the final bill and present it to the
patient.

18- The system shall keep track of available medication and issue
restock requests when stocks are below a certain threshold.

19- The system shall notify physicians if there are

contraindications in prescribed medications.

Required software and hardware

There is no need for any hardware for our application but for the software we need to
use the visual studio to programming through c# language and it should run under
. Windows 7

Non Functional Requirements

 Reliability:
-Availability: the system shall be available all the time.

 Usability:
.User- interface: the system interface shall be friendly -
.the system shall be able easy to use -
.the system shall be able easy to learn-
 Security:
patient identification: the patient shall identify his\her self using SSN -
Modification: any modification (insert, delete, and update) for the patient record -
.must done only by the physician monitors
 Performance:
response time: the system shall be able to give a response in 1 second after the -
.patient insert his\her information’s
.Capacity: the system must support 1000 patient at a time -
.User-interface: the user interface screen shall response within 5 second -
 Maintainability:
.Backup: the system shall provide the capability to back up the system -
.Error: the system shall keep a log of all the errors -

Process modeling
:Context Diagram
:Dataflow Diagram
 Use Cases

:Use case for the patient

:Use case for the physician monitors
Use case for financial System
Use Case for Pharmacy system