INTRODUCTION

CHAPTER-I INTRODUCTION

SBIT-CSE-KHAMMAM 1

INTRODUCTION

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. This all 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 y The Administrator enters into the web site by entering the user Id and password into the Administrator login screen. When the Administrator clicks the ok button in the login screen after entering the username and password then username and password is checked with the database for validity. When the Administrator enters wrong password then a message box is displayed When Administrator clicks the new user in Administrator home screen new user screen is displayed. 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. User Id is automatically generated by Clicking the ok button data will

y y y y y y y y

Manager:
When the Manger clicks the ok button in the login screen after entering the username then username and password is checked with the database for validity. When the manager enters wrong password then a message box is displayed. He can view the list of users in this application based specific type He can view the list of diseases and their remedies.

SBIT-CSE-KHAMMAM

INTRODUCTION

Official:
y y y y y y y y y Official enters into the site after login through Official login screen, by entering user name and password. The official authentication is checked by verifying user Id and password from the data base. After entering into the site Official home screen is displayed. When the official clicks on the Diseases link then Disease details screen will be displayed to add the details of a new disease. This consists of fields like Disease no, name, symptoms, precaution, medicine, hospital and doctor details. Disease no field contains number of each disease which are in the database. By clicking a particular Disease on the details of that disease is displayed. The official can modify, and delete the user records. He can update the doctor availability dates information. He can send a mail to the client.

Doctor:
y y y y y Doctor enters into the web site by Entering his User Id and password by checking his authentication. After entering through Doctor login screen Doctor gets the Client query list screen , which contains list of query details He can view the list of queries posted by different customers. He can click on a specific query and send the reply. 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 more awareness 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. Home: When the client clicks Home link the information regarding the web site is displayed. How to use: when the client goes for clicking this link then the information regarding the usage of the site is displayed.

y y

SBIT-CSE-KHAMMAM 3

INTRODUCTION

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 y y y Every patient needs to go to the clinic physically for taking the doctor appointments. Every doctor needs to intimate the clinic through phone/mail for his unavailability. Every doctor needs store the patient decease details and medicine details. 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 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.

SBIT-CSE-KHAMMAM 4

REQUIREMENTS

CHAPTER-III REQUIREMENTS

SBIT-CSE-KHAMMAM 8

REQUIREMENTS

3 Hardware and software specifications: 3.1 Software specifications:

Operating system Front end Back end IDE Web server 3.2 Hardware specifications: RAM Hard disk I/O Devices : : : 256MB Minimum20 GB Key board, Mouse : : : : : Windows XP Java, HTML Oracle Net Beans 5.5 Apache Tomcat 5.5

SBIT-CSE-KHAMMAM 9

SYSTEM DESIGN

CHAPTER-IV SYSTEM DESIGN

SBIT-CSE-KHAMMAM 10

SYSTEM DESIGN

4 UML DIAGRAMS: 4.1 Class diagrams:

Class diagram for administrator:
Login login() create() Admin Page Create action()

Class diagram for manager:

Login login()

Manager Page get disease() view user()

View users get()

Get disease get()

SBIT-CSE-KHAMMAM 11

SYSTEM DESIGN

Class diagram for doctor:

Login login() Doctor page get queries() schedule() Getquery send reply()

Doctor schedule prepare()

Class diagram for client:

Client page services()

Login login()

Send query send()

See reply view()

View FAQ view()

Take appointment get()

SBIT-CSE-KHAMMAM 12

SYSTEM DESIGN

4.2 Sequence diagrams:

Sequence diagram for administrator:
Login: login() Admin page: Create:

create()

Sequence diagram for manager:

Login: Manager page: View all users: View disease:

login()

view user()

view disease()

13

SBIT-CSE-KHAMMAM

SYSTEM DESIGN

Sequence diagram for doctor:

Login: Doctor page: login() View query: Send reply: Create schedule

view()

reply()

create()

14

SBIT-CSE-KHAMMAM

SYSTEM DESIGN

Sequence diagram for client:

Login: Client page: Post query: Check reply: Appointment :

login()

post()

view()

take()

SBIT-CSE-KHAMMAM 15

SYSTEM DESIGN

Sequence diagram for officeal:

Login:

Officer page: Login ()

Modify user:

Delete user:

Add disease:

Doctor schedule:

Send message

Update ()

Delete ()

New ()

create ()

Send ()

16

SBIT-CSE-KHAMMAM

SYSTEM DESIGN

4.3 Collaboration diagrams:

Collaboration diagram for administrator:
login () Login: Admin page: create() Create:

Collaboration diagram for manager:

Login: login () Manager page: view() View all users:

view disease() View disease:

Collaboration diagram for doctor:

Login: login() Doctor page: view() View query:

send()

create()

Send reply:

Create schedule:

SBIT-CSE-KHAMMAM 17

SYSTEM DESIGN

Collaboration diagram for client:

login () post()

Login:

Client page:

Post query:

view ()

take ()

Check reply:

Appointment :

Collaboration diagram for official:

login () modify()

Login:

Officer page:

Modify user:

delete()

add()

create()

send()

Delete user:

Add disease:

Doctor schedule:

Send messages:

SBIT-CSE-KHAMMAM 18

SYSTEM DESIGN

4.4Use case diagrams:

Use case diagram for administrator:

Create user

Administrator

Use case diagram for manager:

View users

View diseases

Manager

SBIT-CSE-KHAMMAM 19

SYSTEM DESIGN

Use case diagram for doctor:

View posted Queries

Reply queries

Create schedule

Doctor

Use case diagram for client:

Send queries

See reply

View FAQ

Client
Take appointment

SBIT-CSE-KHAMMAM 20

SYSTEM DESIGN

Use case diagram for official:

Modify user

Delete user

Create Schedule

Official

Send messages

Add diseases

21

SBIT-CSE-KHAMMAM

SYSTEM DESIGN

4.5 ER diagrams:
E-R diagram for Administrator:

User-id

Username

Password

Administrator

User-id

Password User-id Password

Doctor

1: nprovides User-id to

Manager

User-id

Password

User-id

Password Client Official

SBIT-CSE-KHAMMAM 22

SYSTEM DESIGN

E-R diagram for Manager:

User-id

Password User-id Manager Username

Password

m:1 Design

Administrator

Dname

Bal

no

Remedy

User-id Reports

Password

m:m

Official

SBIT-CSE-KHAMMAM 23

SYSTEM DESIGN

E-R diagram for doctor:

User-id Password User-id Password

Doctor

m:m

Client

Remedy

Disease name

password

Precaution

User-id

Password User-id Username Password

Official

M:1 Design

Administrator

User-id Database

Password

m:m

Manager

1:m

24

SBIT-CSE-KHAMMAM

SYSTEM DESIGN

E-R diagram for client:

User-id

Password User-id Client Username

Password

m:m Design

Doctor

Disease name

Symptoms

User-id Remedy

Password

m:1

Administrator

SBIT-CSE-KHAMMAM 25

SYSTEM DESIGN

E-R diagram for official:

User-id

Password User-id Official Username

Password

M:1 Design

Administrator

User-id Database

Password

m:m

Manager

SBIT-CSE-KHAMMAM 26

SYSTEM DESIGN

4.6 Dataflow Diagrams (DFDs):

Online clinic

Administrator

Manager

Doctor

Client

Official

Report all users View all diseases

View posted queries and reply Available dates

See reply Posting queries

Take appointment

Modify user

Doctor schedule Delete user Add disease

Create user

Database

SBIT-CSE-KHAMMAM 27

SYSTEM DESIGN

4.7 Database tables:

Login table:
Name Sno NAME PASSWORD TYPE EID Null? NOT NULL Type NUMBER(38) VARCHAR2(40) VARCHAR2(20) VARCHAR2(2) VARCHAR2(5)

Posted query:
Name NO PQUERY EID CID RQUERY FAQ Null? NOT NULL Type NUMBER(38) VARCHAR2(300) NUMBER(38) NUMBER(38) VARCHAR2(300) VARCHAR2(2)

Disease:
Name DID DNAME STATE REMEDY Null? NOT NULL Type NUMBER VARCHAR2(30) VARCHAR2(2) VARCHAR2(300)

SBIT-CSE-KHAMMAM 28

SYSTEM DESIGN

Today schedule:
Name ANO DID Null? NOT NULL NOT NULL Type NUMBER(38) NUMBER(38) VARCHAR(30) VARCHAR2(12) NUMBER(38) VARCHAR2(2)

DNAME ADATE NOT NULL CFEE STATE

Creating dates:
Name RNO DID DNAME ADATE NOT NULL Null? NOT NULL NOTNULL Type NUMBER(38) NUMBER(38) VARCHAR2(30) VARCHAR2(12)

Client apps table:

Name ANO DID ADATE CCNO CID CFEE NOT NULL Null? NOT NULL NOT NULL Type NUMBER(38) NUMBER(38) VARCHAR2(30) VARCHAR2(12) NUMBER(38) NUMBER(38) NUMBER(38)

DNAME NOT NULL

SBIT-CSE-KHAMMAM 29

PROJECT LIFE CYCLE

CHAPTER-II PROJECT LIFECYCLE

SBIT-CSE-KHAMMAM 5

PROJECT LIFE CYCLE

2.1 Analysis model:

Fig: Waterfall Model

SBIT-CSE-KHAMMAM 6

PROJECT LIFE CYCLE

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 it does not allow for much revision. The waterfall model is made up of 7 steps: y Analysis y Design y Implementation y Testing y Documentation y Evaluation y Maintenance

SBIT-CSE-KHAMMAM 7

IMPLEMENTATIONDETAILS

CHAPTER-V IMPLEMENTATION DETAILS

30

SBIT-CSE-KHAMMAM

SCREEN SHOTS

CHAPTER-VI SCREEN SHOTS

SBIT-CSE-KHAMMAM 35

TESTING RESULTS

CHAPTER-VII TESTING RESULTS

SBIT-CSE-KHAMMAM 58

TESTING RESULTS

7.1 SOFTWARE TESTING:

1. Software Testing is the process used to identify the correctness, completeness, security and quality 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.

59

SBIT-CSE-KHAMMAM

TESTING RESULTS

7.3 Test case table:

Unit testing:
Serial no 1 Test case Login page Input Name: admin Password: **** Entering all values except last name Mentioning the date which has already given Trying to add already existing disease. Trying to get report of all users at a time. Input Trying to take appointment at which doctor is not available. Trying to take appointment at a date at which the client already taken appointment on that day. Expected output You are login successfully New use is created. Date has been mentioned as available. You have added a disease. Reports of all users. Observed output User name or password is wrong Enter the last name Status Fail

Create new user Mentioning available dates by doctor Adding a disease by officer. Getting report by manager.

Fail

Already Fail mentioned this date as available date Sorry, disease Fail already exists.

Sorry, you have to select one type of user. Observed output Sorry, doctor is not available.

Fail

Integration testing:
Serial no 1 Test case Taking appointment by client. Expected output You have taken an appointment. Status Fail

2.

Taking appointment by client.

You have taken an appointment

Sorry, you have already taken appointment.

Fail

60

SBIT-CSE-KHAMMAM

LIMITATIONS

CHAPTER-VIII LIMITATIONS

61

SBIT-CSE-KHAMMAM

LIMITATIONS

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.

SBIT-CSE-KHAMMAM 62

CONCLUSION

CHAPTER-IX CONCLUSION

63

SBIT-CSE-KHAMMAM

CONCLUSION

CONCLUSION:
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.

SBIT-CSE-KHAMMAM 64

BIBILIOGRAPHY

CHAPTER-X BIBLIOGRAPHY

65

SBIT-CSE-KHAMMAM

BIBILIOGRAPHY

WEBSITES:
y y y

www.w3schools.com www.oracle.com www.softwaretestingnow.com

BOOKS:
y y y y

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

66

SBIT-CSE-KHAMMAM