Online Clinic

8/3/2019 Online Clinic

1/40

CHAPTER-I

INTRODUCTION

INTRODUCTION

SBIT-CSE-KHAMMAM

1


2/40

1.1 Introduction of project:

Provide a website where a client directly goes for

online consulting a doctoring case of urgency. This should respond automatically for small

questions from clients where he will find better suggestions when any health problems occur. Thisall suggestion, which come from online where the client will be charged for each consultation.

1.2 Problem definition:

In the modern world people are aware of so many Sciences like computer science,

Electronics, commerce, political sciences etc. But they did not know about medical sciences and

its related features much, because usage of scientific words which are difficult to remember and

also difficult to pronounce. At this juncture there is a need for creating awareness in the public

about the general topics of health sciences.

On-line clinic is the one, which provides direct communication with the client

where he gets a remedy for his problem automatically by responding to small combination of

queries. The client can also consult a doctor online, where he is charged for each consultation.

1.3 Module description:

Administrator:

y The Administrator enters into the web site by entering the user Id and password into theAdministrator login screen.

y When the Administrator clicks the ok button in the login screen after entering theusername and password then username and password is checked with the database forvalidity.

y When the Administrator enters wrong password then a message box is displayedy When Administrator clicks the new user in Administrator home screen new user screen is

displayed.

y The Administrator enters the details of newly appointed users of Doctor on-line.com ,the details may be user name , password , Empno, Type of user.

y User Id is automatically generated by Clicking the ok button data willManager:

y When the Manger clicks the ok button in the login screen after entering the username thenusername and password is checked with the database for validity.

y When the manager enters wrong password then a message box is displayed.y He can view the list of users in this application based specific typey He can view the list of diseases and their remedies.

INTRODUCTION

SBIT-CSE-KHAMMAM2


3/40

Official:

y Official enters into the site after login through Official login screen, by entering username and password.

y The official authentication is checked by verifying user Id and password from the data base.y After entering into the site Official home screen is displayed.y When the official clicks on the Diseases link then Disease details screen will be displayed

to add the details of a new disease.

y This consists of fields like Disease no, name, symptoms, precaution, medicine, hospital anddoctor details.

y Disease no field contains number of each disease which are in the database. By clicking aparticular Disease on the details of that disease is displayed.

y The official can modify, and delete the user records.y He can update the doctor availability dates information.y He can send a mail to the client.

Doctor:

y Doctor enters into the web site by Entering his User Id and password by checking hisauthentication.

y After entering through Doctor login screen Doctor gets the Client query list screen ,which contains list of query details

y He can view the list of queries posted by different customers.y He can click on a specific query and send the reply.y

He can set his available dates for patient appointments

Client:

y The client visits the web site to get remedy for his health problems or for getting moreawareness regarding health. The home screen consists of different links like Home, How to

use, Health Awareness, Registration, and login. The clients can go for any link.

y Home: When the client clicks Home link the information regarding the web site isdisplayed.

y How to use: when the client goes for clicking this link then the information regarding theusage of the site is displayed.

INTRODUCTION

SBIT-CSE-KHAMMAM3


4/40

1.4 Existing system:

Here the existing system is a manual system using which the patient needs to

go the clinic manually, he needs to check the doctor list, doctor availability and book the

appointment. The doctor also needs to needs to tell the clinic management to cancel his OP on a

particular date. If the patient wants to contact the doctor for some confirmation then he needs to

come to the clinic again. By following this approach the clinic management people needs to store

the customer information, further consultations and payment details.

y Every patient needs to go to the clinic physically for taking the doctor appointments.y Every doctor needs to intimate the clinic through phone/mail for his unavailability.y Every doctor needs store the patient decease details and medicine details.y Generating appointment reports or patient record report is not possible.

1.5 Proposed system:

In the modern world people are aware of so many Sciences Like computer

sciences, Electronics, commerce, political sciences etc. But they did not know about medical

sciences and its related features much, because usage of scientific words which are difficult toremember and also difficult to pronounce. At this juncture there is a need for creating awareness

in the public about the general topics of health sciences.




INTRODUCTION

SBIT-CSE-KHAMMAM4


5/40

CHAPTER-III

REQUIREMENTS

REQUIREMENTS

SBIT-CSE-KHAMMAM8


6/40

3 Hardware and software specifications:

3.1 Software specifications:

Operating system :W

indows XPFront end : Java, HTML

Back end : Oracle

IDE : Net Beans 5.5

Web server : Apache Tomcat 5.5

3.2Hardware specifications:

RAM : 256MB

Hard disk : Minimum20GB

I/O Devices : Key board, Mouse

REQUIREMENTS

SBIT-CSE-KHAMMAM

9


7/40

CHAPTER-IV

SYSTEM DESIGN

SYSTEM DESIGN

SBIT-CSE-KHAMMAM10


8/40

4 UML DIAGRAMS:

4.1 Class diagrams:

Class diagram for administrator:

Class diagram for manager:

SYSTEM DESIGN

Login

login()

Admin

Page

create()

Create

action()

Login

login()

Manager

Page

get disease()

view user()

View

users

get()

Get

disease

get()

SBIT-CSE-KHAMMAM11


9/40

Class diagram for doctor:

Class diagram for client:

Login

login()

Doctor page

get queries()schedule()

Getquery

sendreply()

Doctor

schedule

prepare()

Login

login()

Client

page

services()

Send

query

send()

View

FAQ

view()

Take

appointment

get()

See

reply

view()

SYSTEM DESIGN

SBIT-CSE-KHAMMAM12


10/40

4.2 Sequence diagrams:

Sequence diagram for administrator:

login()

create()

Sequence diagram for manager:

login()

view user()

view disease()

Admin

page:

Login: Create:

Login: Manager

page:

View all

users:

View

disease:

SYSTEM DESIGN

SBIT-CSE-KHAMMAM13


11/40

Sequence diagram for doctor:

login()

view()

reply()

create()

Create

schedule

Send reply:View

query:

Doctor

page:

Login:

SYSTEM DESIGN

SBIT-CSE-KHAMMAM14


12/40

Sequence diagram for client:

login()

post()

view()

take()

Appointment

:

Check

reply:Post

query:

Client

page:

Login:

SYSTEM DESIGN

SBIT-CSE-KHAMMAM15


13/40

Sequence diagram for officeal:

Login ()

Update ()

Delete ()

New ()

create ()

Send ()

Add

disease:

Delete

user:

Modify

user:

Officer

page:

Login: Doctor

schedule:

Send

message

SYSTEM DESIGN

SBIT-CSE-KHAMMAM16


14/40

4.3 Collaboration diagrams:

Collaboration diagram for administrator:

login () create()

Collaboration diagram for manager:

login () view()

view disease()

Collaboration diagram for doctor:login() view()

send() create()

Admin

page:

Login: Create:

Login: Managerpage:

View allusers:

View

disease:

Create

schedule:

Send reply:

View

query:

Doctor

page:

Login:

SYSTEM DESIGN

SBIT-CSE-KHAMMAM17


15/40

Collaboration diagram for client:

login () post()

view () take ()

Collaboration diagram for official:

login () modify()

delete() add() create() send()

Appointment

:

Check

reply:

Post

query:

Client

page:

Login:

Add

disease:

Delete

user:

Modify

user:

Officer

page:

Login:

Doctor

schedule:

Send

messages:

SYSTEM DESIGN

SBIT-CSE-KHAMMAM

18


16/40

4.4Use case diagrams:

Use case diagram for administrator:

Administrator

Use case diagram for manager:

Manager

Create user

View users

View diseases

SYSTEM DESIGN

SBIT-CSE-KHAMMAM

19


17/40

Use case diagram for doctor:

Doctor

Use case diagram for client:

View postedQueries

Reply queries

Create

schedule

Send

queries

View FAQ

Take

appointment

See reply

Client

SYSTEM DESIGN

SBIT-CSE-KHAMMAM20


18/40

Use case diagram for official:

Official

Modify user

Delete user

Create

Schedule

Add diseases

Send messages

SYSTEM DESIGN

SBIT-CSE-KHAMMAM21


19/40

4.5 ER diagrams:

E-R diagram for Administrator:

Administrator

Doctor Manager

Official

Client

User-idUsername Password

User-id Pa w rd

User-id

User-id

User-id

Pa w rd

Password

Password

1: nprovides

User-id to

SYSTEM DESIGN

SBIT-CSE-KHAMMAM

22


20/40

E-R diagram for Manager:

User-id

User-idPa w rd

PasswordUsername

Mana er

Official

Reports

User-id Password

m:1

Design

m:m

Dname Bal no Remedy

SYSTEM DESIGN

SBIT-CSE-KHAMMAM

23


21/40

E-R diagram for doctor:

User-id

User-idPa w rd

Pa w rdUsername

Admini trat r

Official

Manager

Database

User-id Pa w rd

M:1Design

m:m

1:m

Doctor Clientm:m

User-idUser-id

PasswordPassword

Remed

passwordDisease name Precaution

SYSTEM DESIGN

SBIT-CSE-KHAMMAM24


22/40

E-R diagram for client:

User-id

User-idPa w rd

Pa w rdUsername

Doctor

Client

Administrator

Remedy

User-id Password

m:m

Design

m:1

Disease

nameSymptoms

SYSTEM DESIGN

SBIT-CSE-KHAMMAM

25


23/40

E-R diagram for official:

User-id

User-idPa w rd

Pa w rdUsername

Administrator

Official

Manager

Database

User-id Password

M:1

Design

m:m

SYSTEM DESIGN

SBIT-CSE-KHAMMAM

26


24/40

4.6 Dataflow Diagrams (DFDs):

Administrator Manager Doctor Client Official

Online clinic

Report all

users

View all

di ea e

View

posted

queries

and

reply

Available

dates

Create

u er

See

reply

Posting

queries

Take

appointment

Modify

user

Delete

user

Add

di ea e

Doctor

schedule

Database

SYSTEM DESIGN

SBIT-CSE-KHAMMAM27


25/40

4.7 Database tables:

Login table:

Name Null? Type

Sno NOT NULL NUMBER(38)

NAME

PASSWORD VARCHAR2(20)

TYPE VARCHAR2(2)

EID VARCHAR2(5)

Posted query:

Name Null? Type

NO NOT NULL NUMBER(38)

PQUERY VARCHAR2(300)

EID NUMBER(38)

CID NUMBER(38)

RQUERY VARCHAR2(300)

FAQ VARCHAR2(2)

Disease:

Name Null? Type

DID NOT NULL NUMBER

DNAME VARCHAR2(30)

STATE VARCHAR2(2)

REMEDY VARCHAR2(300)

SYSTEM DESIGN

SBIT-CSE-KHAMMAM28


26/40

Today schedule:

Name Null? Type

ANO NOT NULL NUMBER(38)

DID NOT NULL NUMBER(38)

DNAME VARCHAR(30)

ADATE NOT NULL VARCHAR2(12)

CFEE NUMBER(38)

STATE VARCHAR2(2)

Creating dates:

Name Null? Type

RNO NOT NULL NUMBER(38)

DID NOTNULL NUMBER(38)

DNAME VARCHAR2(30)

ADATE NOT NULL VARCHAR2(12)

Client apps table:

Name Null? Type

ANO NOT NULL NUMBER(38)

DID NOT NULL NUMBER(38)

DNAME NOT NULL VARCHAR2(30)

ADATE VARCHAR2(12)

CCNO NUMBER(38)

CID NOT NULL NUMBER(38)

CFEE NUMBER(38)

SYSTEM DESIGN

SBIT-CSE-KHAMMAM29


27/40

CHAPTER-II

PROJECT LIFECYCLE

PROJECT LIFE CYCLE

SBIT-CSE-KHAMMAM5


28/40

2.1 Analysis model:

Fig: Waterfall Model

PROJECT LIFE CYCLE

SBIT-CSE-KHAMMAM6


29/40

The Waterfall Model:

A classic SDLC model, with a linear and sequential method

that has goals for each development phase. The waterfall model simplifies task scheduling,

because there are no iterative or overlapping steps. One drawback of the waterfall model is that itdoes not allow for much revision.

The waterfall model is made up of 7 steps:

y Analysisy Designy Implementationy Testingy Documentationy Evaluationy Maintenance

PROJECT LIFE CYCLE

SBIT-CSE-KHAMMAM

7


30/40

CHAPTER-V

IMPLEMENTATION DETAILS

IMPLEMENTATIONDETAILS

SBIT-CSE-KHAMMAM30


31/40

CHAPTER-VI

SCREEN SHOTS

SCREEN SHOTS

SBIT-CSE-KHAMMAM35


32/40

CHAPTER-VII

TESTING RESULTS

TESTING RESULTS

SBIT-CSE-KHAMMAM58


33/40

7.1 SOFTWARE TESTING:

1. Software Testing is the process used to identify the correctness, completeness, security andquality of computer software.

2. Software Testing is an investigation conducted to provide stakeholders with information about

the quality of the product or service under test.

3. Software Testing also provides an objective, independent view of the software to allow the

business to appreciate and understood the risks at implementation of the software.

7.2 TYPES OF TESTING:

Black box testing- Internal system design is not considered in this type of testing. Tests are

based on requirements and functionality.

White box testing- This testing is based on knowledge of the internal logic of an applications

code. Also known as Glass box testing. Internal software and code working should be known for

this type of testing. Tests are based on coverage of code statements, branches, paths, conditions.

Unit testing- In which each unit (basic component) of the software is tested to verify that the

detailed design for the unit has been correctly implemented.

Integration testing- In which progressively larger groups of tested software components

corresponding to elements of the architectural design are integrated and tests until the software

works as a whole.

System testing- in which the software is integrated to the overall product and tested to show

that all requirements are met.

59SBIT-CSE-KHAMMAM

TESTING RESULTS


34/40

7.3Test case table:

Unit testing:

Serial no Test case Input Expected

output

Observed

output

Status

1 Login page Name: admin

Password:****

You are login

successfully

User name or

password iswrong

Fail

2 Create new

user

Entering all

values exceptlast name

New use is

created.

Enter the last

name

Fail

3 Mentioning

availabledates by

doctor

Mentioning

the datewhich has

already given

Date has been

mentioned asavailable.

Already

mentioned thisdate as

available date

Fail

4 Adding a

disease byofficer.

Trying to add

alreadyexisting

disease.

You have

added adisease.

Sorry, disease

already exists.

Fail

5 Getting report

by manager.

Trying to get

report of all

users at atime.

Reports of all

users.

Sorry, you

have to select

one type ofuser.

Fail

Integration testing:

Serial no Test case Input Expectedoutput

Observedoutput

Status

1 Taking

appointmentby client.

Trying to

takeappointment

at whichdoctor is not

available.

You have

taken anappointment.

Sorry, doctor

is notavailable.

Fail

2. Taking

appointmentby client.

Trying to

takeappointment

at a date atwhich the

client alreadytaken

appointmenton that day.

You have

taken anappointment

Sorry, you

have alreadytaken

appointment.

Fail

TESTING RESULTS

SBIT-CSE-KHAMMAM60


35/40

CHAPTER-VIII

LIMITATIONS

LIMITATIONS

SBIT-CSE-KHAMMAM61


36/40

LIMITATIONS:

In our proposed system we cant pay the registration bills using credit cards & debit cards.We have to pay the bills manually by going to hospital.

If the complexity of the query increases, the patient has to visit the hospital manually. Though we use this system the patients have to bring some of the reports by hand .later by

using cloud computing we will eliminate this.

The system needs more elaborative technicality for its inception and evolution.

LIMITATIONS

SBIT-CSE-KHAMMAM

62


37/40

CHAPTER-IX

CONCLUSION

CONCLUSION

SBIT-CSE-KHAMMAM63


38/40

CONCLUSION:




CONCLUSION

SBIT-CSE-KHAMMAM

64


39/40

CHAPTER-X

BIBLIOGRAPHY

BIBILIOGRAPHY

SBIT-CSE-KHAMMAM65


40/40

WEBSITES:

y www.w3schools.comy www.oracle.comy www.softwaretestingnow.com

BOOKS:

y Core JavaTM2volume I-Fundamentals 7th Edition (Cay S.Hortsman).y Core JavaTM2volume II-Advanced.y Pearson Education-sun Microsystems (Gray Cornell)y Head First Servlets & JSP(Eric Freeman)

BIBILIOGRAPHY

Documents

Online Clinic