Health Prediction Management System PDF

“Health Prediction Management System”
Submitted to the Department of Computer Science and Engineering

in partial fulfillment of the requirements for the award of the degree of
BACHELOR OF TECHNOLOGY
In
Computer Science and Engineering
of
Biju Patnaik University of Technology, Odisha
Submitted by
MEENAKSHI NIAL Reg.No: 1601204061

SONIA DAS Reg.No: 1601204076
TIKERAM NAIK Reg.No: 1601204075
SARAT CHANDRA NAIK Reg.No: 1601204063
Under the Guidance of
DR. RAGHUNATH KAR

Assistant / Associate Professor in
Department of Computer Science and Engineering
DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

ROLAND INSTITUTE OF TECHNOLOGY,
SURYA VIHAR, BERHAMPUR, Dist-Ganjam, (Odisha), Pin-761 008
SPRING(January-June) 2020
“Health Prediction Management System”
Submitted to the Department of Computer Science and Engineering
in partial fulfillment of the requirements for the award of the degree of
BACHELOR OF TECHNOLOGY
In
Computer Science and Engineering
of
Biju Patnaik University of Technology, Odisha
Submitted by
MEENAKSHI NIAL Reg.No: 1601204061

SONIA DAS Reg.No: 1601204076
TIKERAM NAIK Reg.No: 1601204075
SARAT CHANDRA NAIK Reg.No: 1601204063
Under the Guidance of
DR. RAGHUNATH KAR

Assistant / Associate Professor in
Department of Computer Science and Engineering
DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

ROLAND INSTITUTE OF TECHNOLOGY,
SURYA VIHAR, BERHAMPUR, Dist-Ganjam, (Odisha), Pin-761 008
SPRING(January-June) 2020
CERTIFICATE
Certified that the Major Project work entitled “HEALTH PREDICTION
MANAGEMENT SYSTEM” is carried out by Ms. Meenakshi Nial, Reg. No.
“1601204061”, Ms. Sonia Das, Reg. No. “1601204076”, Mr. Tikeram Naik,
Reg. No. “1601204075” and Mr. Sarat Chandra Naik, Reg. No. “1601204063”
are the bonafide students of Roland Institute of Technology in partial fulfillment
for the award of the degree of Bachelor of Technology in Computer Science and
Engineering of the Biju Patnaik University of Technology, Odisha during the year
2019-20. It is further certified that all corrections / suggestions indicated for
Internal Assessment has been incorporated in the said project report. The
project report has been approved as it satisfies the academic requirements in
respect of project work prescribed for the said degree.
Name of the Guide Name of the HOD

Designation Designation
(External Examiner) Dr. Tarini Charan Tripathy

Principal
College Seal
Declaration
We the following students of 8th semester B. Tech. in Computer Science
and Engineering, Roland Institute of Technology, Surya Vihar, Berhampur,
hereby declare that the project work entitled “HEALTH PREDICTION
MANAGEMENT SYSTEM” submitted to BPUT, Rourkela during the academic
year 2019-2020, is a record of an original work done by us under the guidance of
DR. RAGHUNATH KAR, Assistant / Associate Professor in Department of
Computer Science and Engineering, Roland Institute of Technology, Berhampur.
This project work is submitted in partial fulfillment of the requirements for the
award of the degree of Bachelor of Technology in Computer Science and
Engineering. The embodied content in this thesis have not been submitted to any
other university or institute for the award of any degree. The opinion and
conclusions arrived at, are our own responsibility and views expressed in this
report do not represent the views of any individual.
Ms Meenakshi Nial, Reg. No. 1601204061 Signature_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Ms. Sonia Das, Reg. No. 1601204076 Signature_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Mr Tikeram Naik, Reg. No. 1601204075 Signature_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Mr. Sarat Chandra Naik, Reg. No. 1601204063 Signature_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

ACKNOWLEDGEMENT
We would first like to thank our Guide DR. RAGHUNATH KAR who
encouraged us in every aspect of the project HEALTH PREDICTION MANAGEMENT
SYSTEM.
We also take this privilege to thank the contribution of our Head of the
Department DR. SANJIT KUMAR ACHARYA & all teaching Faculties along with
supporting staffs of the department for providing timely technical advice for
successful completion of our project work.
We are indebted to our Chairman Dr. J. Surya Rao, Director Mdm. J.
Jayalaxmi, Director Sri E. Siva Prasad Rao, Secretary Er. Pr. K. Patra, Principal Dr.
Tarini Charan Tripathy, & Training Placement Officer Mr. P. Deepak Kumar Yadav,
for providing us with the much needed support for completion of our project work.
Finally, we must express our very profound gratitude to our parents for
providing us with unfailing support and continuous encouragement throughout our
study and through the process of researching and writing this project. This
accomplishment would not have been possible without them.

Health Prediction Management System
Thank you.
Ms Meenakshi Nial, Signature_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Ms. Sonia Das, Signature_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Mr Tikeram Naik, Signature_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Mr. Sarat Chandra Naik, Signature_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

TABLE OF CONTENTS
Page
Abstract 1
1 Chapter 1
Introduction 2
1.1 Existing System 2
1.2 Proposed System 2
1.3 Modules 2
1.4 System Requirements 3
1.4.1 Hardware Requirements 3
1.4.2 Software Requirements 3
2 Chapter 2
Software Environment 4
2.1 The Study of The System 4
2.2 Input & Output Representation 5
2.3 Features of Java 7
3 Chapter 3
System Design 27
3.1 UML Diagrams 27
3.1.1 Construction of Usecase Diagrams 30
3.1.2 Sequence Diagrams 32
3.1.3 Class Diagram 34
3.1.4 Activity Diagram 35
4 Chapter 4
System Implementation 37
4.1 Web Page 37
4.2 Package 79
4.3 DataBase 79
5 Chapter 5
Health Prediction Management System
Testing &Validation 83
5.1 Levels of Testing 83
5.1.1 Black Box Testing 84
5.1.2 White Box Testing 86
6 Chapter 6
Screen Shots 90
7 Chapter 7
Conclusion 99
ABSTRACT
―Health Prediction Management System‖ is a project which is developed to

provide an easy and simple way to both users and doctors communicate with each other
directly. In this application users can search the symptoms of the diseases to the doctor
from anywhere and at anytime. User can also ask queries about their problems online
directly with the doctor. Doctors can see all the details of the users and give the answers
to their queries anytime.
1
CHAPTER 1
INTRODUCTION
1.1 EXISTING SYSTEM:
In the existing system users need to waste lot of time and effort in consulting a
doctor even for a simple medical suggestion .No proper communication is maintained
between user and doctor. Sometimes user may not be able to ask all the queries with
doctor regarding their disease. Doctors should check all the details of the users and their
appointment timings which take lot of time.
1.2 PROPOSED SYSTEM:
Proposed system provides easy way to users in consulting a doctor from anywhere
and from anytime. Doctor and user can communicate easily with each other easily. User
can ask doctor query directly and get the reply. Doctor can read all the queries from the
user and give them reply easily without any loss of communication.
1.3 MODULES:
Admin:
Admin gets logged into the application with a valid username and password.
Admin can view all the details of the user and doctor.
User:
User should give all the details in the registration form to get registered in the
application. User will be given username and password after registration. User can
consult doctor by selecting the symptoms of the disease. User can send query directly to
doctor. User can get the response in view feedback field.
2
Doctor:
Doctor should give all the details in the registration form to get registered in the
application. Doctor will be given username and password after registration. Doctor can
view users query and send them reply.
1.4 SYSTEM REQUIREMENTS
1.4.1 HARDWARE REQUIREMENTS:
 Processor : Pentium –III

 Speed : 1.1 Ghz
 RAM : 256 MB(min)
 Hard Disk : 20 GB
 Key Board : Standard Windows Keyboard
 Mouse : Standard Mouse
1.4.2 SOFTWARE REQUIREMENTS:
 Operating System : Windows7/8/10/XP

 Application Server : Tomcat6.0/7.0/8.0
 Front End : HTML, CSS
 Scripts : JavaScript.
 Server side Script : Java Server Pages.
 Database : Mysql
 Database Connectivity : JDBC.
3
CHAPTER 3
SOFTWARE ENVIRONMENT
2.1 THE STUDY OF THE SYSTEM
 To conduct studies and analyses of an operational and technological nature, and

 To promote the exchange and development of methods and tools for operational
analysis as applied to defense problems.
Logical design
The logical design of a system pertains to an abstract representation of the data

flows, inputs and outputs of the system. This is often conducted via modeling, using an
over-abstract (and sometimes graphical) model of the actual system. In the context of
systems design are included. Logical design includes ER Diagrams i.e. Entity
Relationship Diagrams
Physical design
The physical design relates to the actual input and output processes of the system.
This is laid down in terms of how data is input into a system, how it is verified /
authenticated, how it is processed, and how it is displayed as output. In Physical design,
following requirements about the system are decided.
1. Input requirement,
2. Output requirements,
3. Storage requirements,
4. Processing Requirements,
5. System control and backup or recovery.
Put another way, the physical portion of systems design can generally be broken down
into three sub-tasks:
4
1. User Interface Design
2. Data Design
3. Process Design
User Interface Design is concerned with how users add information to the system
and with how the system presents information back to them. Data Design is concerned
with how the data is represented and stored within the system. Finally, Process Design is
concerned with how data moves through the system, and with how and where it is
validated, secured and/or transformed as it flows into, through and out of the system. At
the end of the systems design phase, documentation describing the three sub-tasks is
produced and made available for use in the next phase.
Physical design, in this context, does not refer to the tangible physical design of
an information system. To use an analogy, a personal computer's physical design
involves input via a keyboard, processing within the CPU, and output via a monitor,
printer, etc. It would not concern the actual layout of the tangible hardware, which for a
PC would be a monitor, CPU, motherboard, hard drive, modems, video/graphics cards,
USB slots, etc. It involves a detailed design of a user and a product database structure
processor and a control processor. The H/S personal specification is developed for the
proposed system.
2.2 INPUT & OUTPUT REPRESENTATION
Input Design
The input design is the link between the information system and the user. It
comprises the developing specification and procedures for data preparation and those
steps are necessary to put transaction data in to a usable form for processing can be
achieved by inspecting the computer to read data from a written or printed document or it
can occur by having people keying the data directly into the system. The design of input
focuses on controlling the amount of input required, controlling the errors, avoiding
delay, avoiding extra steps and keeping the process simple. The input is designed in such
5
a way so that it provides security and ease of use with retaining the privacy. Input Design
considered the following things:
 What data should be given as input?

 How the data should be arranged or coded?
 The dialog to guide the operating personnel in providing input.
 Methods for preparing input validations and steps to follow when error occur.
Objectives
Input Design is the process of converting a user-oriented description of the input

into a computer-based system. This design is important to avoid errors in the data input
process and show the correct direction to the management for getting correct information
from the computerized system.
It is achieved by creating user-friendly screens for the data entry to handle large
volume of data. The goal of designing input is to make data entry easier and to be free
from errors. The data entry screen is designed in such a way that all the data manipulates
can be performed. It also provides record viewing facilities.
When the data is entered it will check for its validity. Data can be entered with the
help of screens. Appropriate messages are provided as when needed so that the user will
not be in maize of instant. Thus the objective of input design is to create an input layout
that is easy to follow
Output Design
A quality output is one, which meets the requirements of the end user and
presents the information clearly. In any system results of processing are communicated to
the users and to other system through outputs. In output design it is determined how the
information is to be displaced for immediate need and also the hard copy output. It is the
most important and direct source information to the user. Efficient and intelligent output
design improves the system’s relationship to help user decision-making.
6
a. Designing computer output should proceed in an organized, well thought out
manner; the right output must be developed while ensuring that each output
element is designed so that people will find the system can use easily and
effectively. When analysis design computer output, they should Identify the
specific output that is needed to meet the requirements.
b. Select methods for presenting information.
c. Create document, report, or other formats that contain information produced by
the system.
The output form of an information system should accomplish one or more of the
following objectives.
 Convey information about past activities, current status or projections of the

future.
 Signal important events, opportunities, problems, or warnings.
 Trigger an action.
 Confirm an action.
2.3 Features of Java

Java Technology
Java technology is both a programming language and a platform.
The Java Programming Language

The Java programming language is a high-level language that can be
characterized by all of the following buzzwords:
 Simple
 Architecture neutral
 Object oriented
 Portable
 Distributed
 High performance
 Interpreted
 Multithreaded
7
 Robust
 Dynamic
 Secure
With most programming languages, you either compile or interpret a program so
that you can run it on your computer. The Java programming language is unusual in that
a program is both compiled and interpreted. With the compiler, first you translate a
program into an intermediate language called Java byte codes —the platform-
independent codes interpreted by the interpreter on the Java platform. The interpreter
parses and runs each Java byte code instruction on the computer. Compilation happens
just once; interpretation occurs each time the program is executed. The following figure
illustrates how this works.
You can think of Java byte codes as the machine code instructions for the Java
Virtual Machine (Java VM). Every Java interpreter, whether it’s a development tool or a
Web browser that can run applets, is an implementation of the Java VM. Java byte codes
help make ―write once, run anywhere‖ possible. You can compile your program into byte
codes on any platform that has a Java compiler. The byte codes can then be run on any
implementation of the Java VM. That means that as long as a computer has a Java VM,
the same program written in the Java programming language can run on Windows 2000,
a Solaris workstation, or on an iMac.
8
The Java Platform
A platform is the hardware or software environment in which a program
runs. We’ve already mentioned some of the most popular platforms like Windows
2000, Linux, Solaris, and MacOS. Most platforms can be described as a
combination of the operating system and hardware. The Java platform differs
from most other platforms in that it’s a software-only platform that runs on top of
other hardware-based platforms.
The Java platform has two components:

 The Java Virtual Machine (Java VM)
 The Java Application Programming Interface (Java API)
You’ve already been introduced to the Java VM. It’s the base for the Java
platform and is ported onto various hardware-based platforms.
The Java API is a large collection of ready-made software components that

provide many useful capabilities, such as graphical user interface (GUI) widgets.
The Java API is grouped into libraries of related classes and interfaces; these
libraries are known as packages. The next section, What Can Java Technology
Do? Highlights what functionality some of the packages in the Java API provide.
The following figure depicts a program that’s running on the Java platform.
As the figure shows, the Java API and the virtual machine insulate the program
from the hardware.
9
Native code is code that after you compile it, the compiled code runs on a
specific hardware platform. As a platform-independent environment, the Java
platform can be a bit slower than native code. However, smart compilers, well-
tuned interpreters, and just-in-time byte code compilers can bring performance
close to that of native code without threatening portability.
What Can Java Technology Do?
The most common types of programs written in the Java programming language
are applets and applications. If you’ve surfed the Web, you’re probably already
familiar with applets. An applet is a program that adheres to certain conventions
that allow it to run within a Java-enabled browser.
However, the Java programming language is not just for writing cute, entertaining
applets for the Web. The general-purpose, high-level Java programming language
is also a powerful software platform. Using the generous API, you can write many
types of programs.
An application is a standalone program that runs directly on the Java platform. A
special kind of application known as a server serves and supports clients on a
network. Examples of servers are Web servers, proxy servers, mail servers, and
print servers. Another specialized program is a servlet. A servlet can almost be
thought of as an applet that runs on the server side. Java Servlets are a popular
choice for building interactive web applications, replacing the use of CGI scripts.
Servlets are similar to applets in that they are runtime extensions of applications.
Instead of working in browsers, though, servlets run within Java Web servers,
configuring or tailoring the server.
How does the API support all these kinds of programs? It does so with packages
of software components that provides a wide range of functionality. Every full
implementation of the Java platform gives you the following features:
10
 The essentials: Objects, strings, threads, numbers, input and output, data
structures, system properties, date and time, and so on.
 Applets: The set of conventions used by applets.
 Networking: URLs, TCP (Transmission Control Protocol), UDP (User
Data gram Protocol) sockets, and IP (Internet Protocol) addresses.
 Internationalization: Help for writing programs that can be localized for
users worldwide. Programs can automatically adapt to specific locales and
be displayed in the appropriate language.
 Security: Both low level and high level, including electronic signatures,
public and private key management, access control, and certificates.
 Software components: Known as JavaBeansTM, can plug into existing
component architectures.
 Object serialization: Allows lightweight persistence and communication
via Remote Method Invocation (RMI).
 Java Database Connectivity (JDBCTM): Provides uniform access to a
wide range of relational databases.
The Java platform also has APIs for 2D and 3D graphics, accessibility, servers,
collaboration, telephony, speech, animation, and more. The following figure
depicts what is included in the Java 2 SDK.
How Will Java Technology Change My Life?

We can’t promise you fame, fortune, or even a job if you learn the Java
programming language. Still, it is likely to make your programs better and
11
requires less effort than other languages. We believe that Java technology will
help you do the following:
 Get started quickly: Although the Java programming language is a
powerful object-oriented language, it’s easy to learn, especially for
programmers already familiar with C or C++.
 Write less code: Comparisons of program metrics (class counts, method
counts, and so on) suggest that a program written in the Java programming
language can be four times smaller than the same program in C++.
 Write better code: The Java programming language encourages good
coding practices, and its garbage collection helps you avoid memory leaks.
Its object orientation, its JavaBeans component architecture, and its wide-
ranging, easily extendible API let you reuse other people’s tested code and
introduce fewer bugs.
 Develop programs more quickly: Your development time may be as
much as twice as fast versus writing the same program in C++. Why? You
write fewer lines of code and it is a simpler programming language than
C++.
 Avoid platform dependencies with 100% Pure Java: You can keep
your program portable by avoiding the use of libraries written in other
languages. The 100% Pure Java TM Product Certification Program has a
repository of historical process manuals, white papers, brochures, and
similar materials online.
 Write once, run anywhere: Because 100% Pure Java programs are
compiled into machine-independent byte codes, they run consistently on
any Java platform.
 Distribute software more easily: You can upgrade applets easily from a
central server. Applets take advantage of the feature of allowing new
classes to be loaded ―on the fly,‖ without recompiling the entire program.
ODBC
Microsoft Open Database Connectivity (ODBC) is a standard programming
interface for application developers and database systems providers. Before ODBC
12
became a de facto standard for Windows programs to interface with database systems,
programmers had to use proprietary languages for each database they wanted to connect
to. Now, ODBC has made the choice of the database system almost irrelevant from a
coding perspective, which is as it should be. Application developers have much more
important things to worry about than the syntax that is needed to port their program from
one database to another when business needs suddenly change.
Through the ODBC Administrator in Control Panel, you can specify the particular
database that is associated with a data source that an ODBC application program is
written to use. Think of an ODBC data source as a door with a name on it. Each door will
lead you to a particular database. For example, the data source named Sales Figures
might be a SQL Server database, whereas the Accounts Payable data source could refer
to an Access database. The physical database referred to by a data source can reside
anywhere on the LAN.
The ODBC system files are not installed on your system by Windows 95. Rather,
they are installed when you setup a separate database application, such as SQL Server
Client or Visual Basic 4.0. When the ODBC icon is installed in Control Panel, it uses a
file called ODBCINST.DLL. It is also possible to administer your ODBC data sources
through a stand-alone program called ODBCADM.EXE. There is a 16-bit and a 32-bit
version of this program and each maintains a separate list of ODBC data sources.
From a programming perspective, the beauty of ODBC is that the application can
be written to use the same set of function calls to interface with any data source,
regardless of the database vendor. The source code of the application doesn’t change
whether it talks to Oracle or SQL Server. We only mention these two as an example.
There are ODBC drivers available for several dozen popular database systems. Even
Excel spreadsheets and plain text files can be turned into data sources. The operating
system uses the Registry information written by ODBC Administrator to determine
which low-level ODBC drivers are needed to talk to the data source (such as the interface
to Oracle or SQL Server). The loading of the ODBC drivers is transparent to the ODBC
application program. In a client/server environment, the ODBC API even handles many
of the network issues for the application programmer.
13
The advantages of this scheme are so numerous that you are probably thinking
there must be some catch. The only disadvantage of ODBC is that it isn’t as efficient as
talking directly to the native database interface. ODBC has had many detractors make the
charge that it is too slow. Microsoft has always claimed that the critical factor in
performance is the quality of the driver software that is used. In our humble opinion, this
is true. The availability of good ODBC drivers has improved a great deal recently. And
anyway, the criticism about performance is somewhat analogous to those who said that
compilers would never match the speed of pure assembly language. Maybe not, but the
compiler (or ODBC) gives you the opportunity to write cleaner programs, which means
you finish sooner. Meanwhile, computers get faster every year.
JDBC
In an effort to set an independent database standard API for Java; Sun
Microsystems developed Java Database Connectivity, or JDBC. JDBC offers a generic
SQL database access mechanism that provides a consistent interface to a variety of
RDBMSs. This consistent interface is achieved through the use of ―plug-in‖ database
connectivity modules, or drivers. If a database vendor wishes to have JDBC support, he
or she must provide the driver for each platform that the database and Java run on.
To gain a wider acceptance of JDBC, Sun based JDBC’s framework on ODBC.
As you discovered earlier in this chapter, ODBC has widespread support on a variety of
platforms. Basing JDBC on ODBC will allow vendors to bring JDBC drivers to market
much faster than developing a completely new connectivity solution.
JDBC was announced in March of 1996. It was released for a 90 day public
review that ended June 8, 1996. Because of user input, the final JDBC v1.0 specification
was released soon after.
The remainder of this section will cover enough information about JDBC for you to know
what it is about and how to use it effectively. This is by no means a complete overview of
JDBC. That would fill an entire book.
JDBC Goals
Few software packages are designed without goals in mind. JDBC is one that,
because of its many goals, drove the development of the API. These goals, in conjunction
14
with early reviewer feedback, have finalized the JDBC class library into a solid
framework for building database applications in Java.
The goals that were set for JDBC are important. They will give you some insight as to
why certain classes and functionalities behave the way they do. The eight design goals
for JDBC are as follows:
1. SQL Level API

he designers felt that their main goal was to define a SQL interface for Java.
Although not the lowest database interface level possible, it is at a low enough
level for higher-level tools and APIs to be created. Conversely, it is at a high
enough level for application programmers to use it confidently. Attaining this goal
allows for future tool vendors to ―generate‖ JDBC code and to hide many of
JDBC’s complexities from the end user.
2. SQL Conformance
SQL syntax varies as you move from database vendor to database vendor. In an
effort to support a wide variety of vendors, JDBC will allow any query statement
to be passed through it to the underlying database driver. This allows the
connectivity module to handle non-standard functionality in a manner that is
suitable for its users.
3. JDBC must be implemental on top of common database interfaces

The JDBC SQL API must ―sit‖ on top of other common SQL level APIs. This
goal allows JDBC to use existing ODBC level drivers by the use of a software
interface. This interface would translate JDBC calls to ODBC and vice versa.
4. Provide a Java interface that is consistent with the rest of the Java system
Because of Java’s acceptance in the user community thus far, the designers feel
that they should not stray from the current design of the core Java system.
15
5. Keep it simple
This goal probably appears in all software design goal listings. JDBC is no
exception. Sun felt that the design of JDBC should be very simple, allowing for
only one method of completing a task per mechanism. Allowing duplicate
functionality only serves to confuse the users of the API.
6. Use strong, static typing wherever possible

Strong typing allows for more error checking to be done at compile time; also,
less error appear at runtime.
7. Keep the common cases simple

Because more often than not, the usual SQL calls used by the programmer are
simple SELECT’s, INSERT’s, DELETE’s and UPDATE’s, these queries should
be simple to perform with JDBC. However, more complex SQL statements
should also be possible.
Finally we decided to proceed the implementation using Java Networking.
And for dynamically updating the cache table we go for MS Access database.
JAVA HA TWO THINGS: A PROGRAMMING LANGUAGE AND A PLATFORM.
JAVA IS A HIGH-LEVEL PROGRAMMING LANGUAGE THAT IS ALL OF THE

FOLLOWING
SIMPLE ARCHITECTURE-NEUTRAL
OBJECT-ORIENTED PORTABLE
DISTRIBUTED HIGH-PERFORMANCE
INTERPRETED MULTITHREADED
ROBUST DYNAMIC
SECURE
16
JAVA IS ALSO UNUSUAL IN THAT EACH JAVA PROGRAM IS BOTH COMPILED
AND INTERPRETED. WITH A COMPILE YOU TRANSLATE A JAVA PROGRAM INTO AN
INTERMEDIATE LANGUAGE CALLED JAVA BYTE CODES THE PLATFORM-
INDEPENDENT CODE INSTRUCTION IS PASSED AND RUN ON THE COMPUTER.
COMPILATION HAPPENS JUST ONCE; INTERPRETATION OCCURS EACH TIME
THE PROGRAM IS EXECUTED. THE FIGURE ILLUSTRATES HOW THIS WORKS.
Java Program Interpreter
Compilers My Program
YOU CAN THINK OF JAVA BYTE CODES AS THE MACHINE CODE INSTRUCTIONS
FOR THE JAVA VIRTUAL MACHINE (JAVA VM). EVERY JAVA INTERPRETER,
WHETHER IT’S A JAVA DEVELOPMENT TOOL OR A WEB BROWSER THAT CAN RUN
JAVA APPLETS, IS AN IMPLEMENTATION OF THE JAVA VM. THE JAVA VM CAN

ALSO BE IMPLEMENTED IN HARDWARE.
JAVA BYTE CODES HELP MAKE ―WRITE ONCE, RUN ANYWHERE‖ POSSIBLE.
YOU CAN COMPILE YOUR JAVA PROGRAM INTO BYTE CODES ON MY PLATFORM
THAT HAS A JAVA COMPILER. THE BYTE CODES CAN THEN BE RUN ANY
IMPLEMENTATION OF THE JAVA VM. FOR EXAMPLE, THE SAME JAVA PROGRAM
CAN RUN WINDOWS NT, SOLARIS, AND MACINTOSH.
17
Networking
TCP/IP stack
The TCP/IP stack is shorter than the OSI one:
TCP is a connection-oriented protocol; UDP (User Datagram Protocol) is a

connectionless protocol.
IP datagram’s
The IP layer provides a connectionless and unreliable delivery system. It

considers each datagram independently of the others. Any association between
datagram must be supplied by the higher layers. The IP layer supplies a
checksum that includes its own header. The header includes the source and
destination addresses. The IP layer handles routing through an Internet. It is also
responsible for breaking up large datagram into smaller ones for transmission
and reassembling them at the other end.
UDP
UDP is also connectionless and unreliable. What it adds to IP is a checksum

for the contents of the datagram and port numbers. These are used to give a
client/server model - see later.
18
TCP
TCP supplies logic to give a reliable connection-oriented protocol above IP.

It provides a virtual circuit that two processes can use to communicate.
Internet addresses
In order to use a service, you must be able to find it. The Internet uses an
address scheme for machines so that they can be located. The address is a 32 bit
integer which gives the IP address. This encodes a network ID and more
addressing. The network ID falls into various classes according to the size of the
network address.
Network address
Class A uses 8 bits for the network address with 24 bits left over for other
addressing. Class B uses 16 bit network addressing. Class C uses 24 bit network
addressing and class D uses all 32.
Subnet address
Internally, the UNIX network is divided into sub networks. Building 11 is

currently on one sub network and uses 10-bit addressing, allowing 1024
different hosts.
Host address
8 bits are finally used for host addresses within our subnet. This places a
limit of 256 machines that can be on the subnet.
19
Total address
The 32 bit address is usually written as 4 integers separated by dots.
Port addresses
A service exists on a host, and is identified by its port. This is a 16 bit

number. To send a message to a server, you send it to the port for that service of
the host that it is running on. This is not location transparency! Certain of these
ports are "well known".
Sockets
A socket is a data structure maintained by the system to handle network

connections. A socket is created using the call socket. It returns an integer that
is like a file descriptor. In fact, under Windows, this handle can be used with
Read File and Write File functions.
#include <sys/types.h>
#include <sys/socket.h>
int socket(int family, int type, int protocol);
Here "family" will be AF_INET for IP communications, protocol will be

zero, and type will depend on whether TCP or UDP is used. Two processes
wishing to communicate over a network create a socket each. These are similar
to two ends of a pipe - but the actual pipe does not yet exist.
20
JFree Chart
JFreeChart is a free 100% Java chart library that makes it easy for
developers to display professional quality charts in their applications. JFreeChart's
extensive feature set includes:
A consistent and well-documented API, supporting a wide range of chart

types;
A flexible design that is easy to extend, and targets both server-side and
client-side applications;
Support for many output types, including Swing components, image files
(including PNG and JPEG), and vector graphics file formats (including PDF, EPS
and SVG);
JFreeChart is "open source" or, more specifically, free software. It is

distributed under the terms of the GNU Lesser General Public Licence (LGPL),
which permits use in proprietary applications.
1. Map Visualizations
Charts showing values that relate to geographical areas. Some examples
include: (a) population density in each state of the United States, (b) income per
capita for each country in Europe, (c) life expectancy in each country of the
world. The tasks in this project include:
Sourcing freely redistributable vector outlines for the countries of the

world, states/provinces in particular countries (USA in particular, but also other
areas);
Creating an appropriate dataset interface (plus default implementation), a

rendered, and integrating this with the existing XYPlot class in JFreeChart;
Testing, documenting, testing some more, documenting some more.
21
2. Time Series Chart Interactivity
Implement a new (to JFreeChart) feature for interactive time series charts --- to
display a separate control that shows a small version of ALL the time series data, with
a sliding "view" rectangle that allows you to select the subset of the time series data
to display in the main chart.
3. Dashboards
There is currently a lot of interest in dashboard displays. Create a flexible dashboard
mechanism that supports a subset of JFreeChart chart types (dials, pies,
thermometers, bars, and lines/time series) that can be delivered easily via both Java
Web Start and an applet.
4. Property Editors
The property editor mechanism in JFreeChart only handles a small subset of the
properties that can be set for charts. Extend (or reimplement) this mechanism to
provide greater end-user control over the appearance of the charts.
J2ME (Java 2 Micro edition):-
Sun Microsystems defines J2ME as "a highly optimized Java run-time environment
targeting a wide range of consumer products, including pagers, cellular phones, screen-
phones, digital set-top boxes and car navigation systems." Announced in June 1999 at the
JavaOne Developer Conference, J2ME brings the cross-platform functionality of the Java
language to smaller devices, allowing mobile wireless devices to share applications. With
J2ME, Sun has adapted the Java platform for consumer products that incorporate or are
based on small computing devices.
22
1. General J2ME architecture
J2ME uses configurations and profiles to customize the Java Runtime Environment
(JRE). As a complete JRE, J2ME is comprised of a configuration, which determines the
JVM used, and a profile, which defines the application by adding domain-specific
classes. The configuration defines the basic run-time environment as a set of core classes
and a specific JVM that run on specific types of devices. We'll discuss configurations in
detail in the The profile defines the application; specifically, it adds domain-specific
classes to the J2ME configuration to define certain uses for devices. We'll cover profiles
in depth in the The following graphic depicts the relationship between the different
virtual machines, configurations, and profiles. It also draws a parallel with the J2SE API
and its Java virtual machine. While the J2SE virtual machine is generally referred to as a
JVM, the J2ME virtual machines, KVM and CVM, are subsets of JVM. Both KVM and
CVM can be thought of as a kind of Java virtual machine -- it's just that they are
shrunken versions of the J2SE JVM and are specific to J2ME.
2. Developing J2ME applications
Introduction In this section, we will go over some considerations you need to keep in
mind when developing applications for smaller devices. We'll take a look at the way the
compiler is invoked when using J2SE to compile J2ME applications. Finally, we'll
explore packaging and deployment and the role preverification plays in this process.
23
3. Design considerations for small devices
Developing applications for small devices requires you to keep certain strategies in mind
during the design phase. It is best to strategically design an application for a small device
before you begin coding. Correcting the code because you failed to consider all of the
"gotchas" before developing the application can be a painful process. Here are some
design strategies to consider:
* Keep it simple. Remove unnecessary features, possibly making those features a

separate, secondary application.
* Smaller is better. This consideration should be a "no brainer" for all developers.
Smaller applications use less memory on the device and require shorter installation times.
Consider packaging your Java applications as compressed Java Archive (jar) files.
* Minimize run-time memory use. To minimize the amount of memory used at run time,
use scalar types in place of object types. Also, do not depend on the garbage collector.
You should manage the memory efficiently yourself by setting object references to null
when you are finished with them. Another way to reduce run-time memory is to use lazy
instantiation, only allocating objects on an as-needed basis. Other ways of reducing
overall and peak memory use on small devices are to release resources quickly, reuse
objects, and avoid exceptions.
4. Configurations overview
The configuration defines the basic run-time environment as a set of core classes and a
specific JVM that run on specific types of devices. Currently, two configurations exist for
J2ME, though others may be defined in the future:
* Connected Limited Device Configuration (CLDC) is used specifically with the

KVM for 16-bit or 32-bit devices with limited amounts of memory. This is the
configuration (and the virtual machine) used for developing small J2ME applications. Its
size limitations make CLDC more interesting and challenging (from a development point
of view) than CDC. CLDC is also the configuration that we will use for developing our
24
drawing tool application. An example of a small wireless device running small
applications is a Palm hand-held computer.
* Connected Device Configuration (CDC) is used with the C virtual machine (CVM)
and is used for 32-bit architectures requiring more than 2 MB of memory. An example of
such a device is a Net TV box.
5. J2ME profiles
What is a J2ME profile?
As we mentioned earlier in this tutorial, a profile defines the type of device supported.
The Mobile Information Device Profile (MIDP), for example, defines classes for cellular
phones. It adds domain-specific classes to the J2ME configuration to define uses for
similar devices. Two profiles have been defined for J2ME and are built upon CLDC:
KJava and MIDP. Both KJava and MIDP are associated with CLDC and smaller devices.
Profiles are built on top of configurations. Because profiles are specific to the size of the
device (amount of memory) on which an application runs, certain profiles are associated
with certain configurations.
A skeleton profile upon which you can create your own profile, the Foundation Profile, is
available for CDC.
Profile 1: KJava
KJava is Sun's proprietary profile and contains the KJava API. The KJava profile is built
on top of the CLDC configuration. The KJava virtual machine, KVM, accepts the same
byte codes and class file format as the classic J2SE virtual machine. KJava contains a
Sun-specific API that runs on the Palm OS. The KJava API has a great deal in common
with the J2SE Abstract Windowing Toolkit (AWT). However, because it is not a standard
J2ME package, its main package is com.sun.kjava. We'll learn more about the KJava API
later in this tutorial when we develop some sample applications.
25
Profile 2: MIDP
MIDP is geared toward mobile devices such as cellular phones and pagers. The MIDP,
like KJava, is built upon CLDC and provides a standard run-time environment that allows
new applications and services to be deployed dynamically on end user devices. MIDP is a
common, industry-standard profile for mobile devices that is not dependent on a specific
vendor. It is a complete and supported foundation for mobile application
development. MIDP contains the following packages, the first three of which are core
CLDC packages, plus three MIDP-specific packages.
* java.lang
* java.io
* java.util
* javax.microedition.io
* javax.microedition.lcdui
* javax.microedition.midlet
* javax.microedition.rms
26
CHAPTER 3
SYSTEM DESIGN
System Design Introduction:
The System Design Document describes the system requirements, operating

environment, system and subsystem architecture, files and database design, input formats,
output layouts, human-machine interfaces, detailed design, processing logic, and external
interfaces.
3.1 UML DIAGRAMS
Global Use Case Diagrams:
Identification of actors:
Actor: Actor represents the role a user plays with respect to the system. An actor interacts
with, but has no control over the use cases.
Graphical representation:
Actor <<Actor name>>
An actor is someone or something that:
Interacts with or uses the system.
 Provides input to and receives information from the system.

 Is external to the system and has no control over the use cases.
Actors are discovered by examining:
 Who directly uses the system?

 Who is responsible for maintaining the system?
27
 External hardware used by the system.
 Other systems that need to interact with the system.
Questions to identify actors:
 Who is using the system? Or, who is affected by the system? Or, which
groups need help from the system to perform a task?
 Who affects the system? Or, which user groups are needed by the system to
perform its functions? These functions can be both main functions and
secondary functions such as administration.
 Which external hardware or systems (if any) use the system to perform tasks?
 What problems does this application solve (that is, for whom)?
 And, finally, how do users use the system (use case)? What are they doing
with the system?
The actors identified in this system are:
a. System Administrator
b. Customer
c. Customer Care
Identification of usecases:
Usecase: A use case can be described as a specific way of using the system from a
user’s (actor’s) perspective.
Graphical representation:
A more detailed description might characterize a use case as:
 Pattern of behavior the system exhibits

 A sequence of related transactions performed by an actor and the system
 Delivering something of value to the actor
28
Use cases provide a means to:
 capture system requirements

 communicate with the end users and domain experts
 test the system
Use cases are best discovered by examining the actors and defining what the actor will
be able to do with the system.
Guide lines for identifying use cases:
 For each actor, find the tasks and functions that the actor should be able to
perform or that the system needs the actor to perform. The use case should
represent a course of events that leads to clear goal
 Name the use cases.
 Describe the use cases briefly by applying terms with which the user is
familiar.
This makes the description less ambiguous
Questions to identify use cases:
 What are the tasks of each actor?

 Will any actor create, store, change, remove or read information in the
system?
 What use case will store, change, remove or read this information?
 Will any actor need to inform the system about sudden external changes?
 Does any actor need to inform about certain occurrences in the system?
 What usecases will support and maintains the system?
1.2 Flow of Events
A flow of events is a sequence of transactions (or events) performed by the

system. They typically contain very detailed information, written in terms of what the
system should do, not how the system accomplishes the task. Flow of events are created
as separate files or documents in your favorite text editor and then attached or linked to a
use case using the Files tab of a model element.
29
A flow of events should include:
 When and how the use case starts and ends

 Use case/actor interactions
 Data needed by the use case
 Normal sequence of events for the use case
 Alternate or exceptional flows
3.1.1 Construction of Usecase diagrams:
A use case diagram in the Unified Modeling Language (UML) is a type of

behavioral diagram defined by and created from a Use-case analysis. Its purpose is to
present a graphical overview of the functionality provided by a system in terms of actors,
their goals (represented as use cases), and any dependencies between those use cases. The
main purpose of a use case diagram is to show what system functions are performed for
which actor. Roles of the actors in the system can be depicted.
Figure 3.1.1.1 Use Case Diagram for Admin
30
Figure 3.1.1.2 Use Case Diagram for User Functionalities
Figure 3.1.1.3 Use Case Diagram for Doctor Functionalities
31
3.1.2 SEQUENCE DIAGRAMS:
A sequence diagram in Unified Modeling Language (UML) is a kind of interaction

diagram that shows how processes operate with one another and in what order. It is a
construct of a Message Sequence Chart. Sequence diagrams are sometimes called event
diagrams, event scenarios, and timing diagrams.
Figure 3.1.2: Sequence diagram to View Admin Details
32
Figure 3.1.2.3: Sequence diagram to View User Details
Figure 3.1.2.4: Sequence diagram to View Doctor Details
33
4.1.3. CLASS DIAGRAM:
In software engineering, a class diagram in the Unified Modeling Language (UML) is a

type of static structure diagram that describes the structure of a system by showing the
system's classes, their attributes, operations (or methods), and the relationships among the
classes. It explains which class contains information.
Figure 3.1.3: Class Diagram of User and Admin and Doctor
34
4.1.4 ACTIVITY DIAGRAM:
Activity diagrams are graphical representations of workflows of stepwise activities and
actions with support for choice, iteration and concurrency. In the Unified Modeling
Language, activity diagrams can be used to describe the business and operational step-by-
step workflows of components in a system. An activity diagram shows the overall flow of
control.
35
Figure 3.1.4: Activity Diagram of User and Doctor and Admin
36
CHAPTER 4
SYSTEM IMPLEMENTATION
The goal of the coding or programming phase is to translate the design of the system
produced during the design phase into code in a given programming language, which can
be executed by a computer and that performs the computation specified by the design.
The coding phase affects both testing and maintenance. The goal of coding is not
to reduce the implementation cost but the goal should be to reduce the cost of later
phases. In other words the goal is not to simplify the job of programmer. Rather the goal
should be to simplify the job of the tester and maintainer.
Coding Approach
There are two major approaches for coding any software system. They are top-
Down approach and Bottom-up approach.
Bottom-up approach can be best suitable for developing the object oriented
systems. During system design phase to reduce the complexity, we decompose the system
into an appropriate number of subsystems, for which objects can be modeled
independently. These objects exhibit the way the subsystems perform their operations.
Once objects have been modeled they are implemented by means of coding. Even
though related to the same system as the objects are independent of each other the
Bottom up approach is more suitable for coding these objects.
In this approach we first do the coding of objects independently and then we

integrate these modules into one system to which they belong.
4.1 Web Page
Index
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0
Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-
transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
37
<title>Health Management System</title>
<meta http-equiv="content-type" content="text/html;
charset=utf-8" />
<link href="style.css" rel="stylesheet" type="text/css" />
<script type="text/javascript" src="js/cufon-
yui.js"></script>
<script type="text/javascript" src="js/arial.js"></script>
<script type="text/javascript"
src="js/cuf_run.js"></script>
<script type="text/javascript" src="js/jquery-
1.3.2.min.js"></script>
<script type="text/javascript" src="js/radius.js"></script>
</head>
<body>
<div class="main">
<div class="header">
<div class="header_resize">
<div class="logo">
<h1><font color="black">Health Prediction Management
System</font></h1>
</div>
<div class="clr"></div>
<div class="menu_nav">
<ul>
<li class="active"><a
href="index.html">Home</a></li>
<li><a href="admin.jsp">Admin</a></li>
<li><a href="user.jsp">User</a></li>
<li><a href="doctor.jsp">Doctor</a></li>
</ul>
</div>
</div>
</div>
<div class="content">
<div class="content_resize"> <img src="images/doc.jpg"
width="958" height="245" alt="" class="hbg_img" />
<div class="article">
<br><br>
<center>
<p>Health Prediction management system is a web
application developed for hospitals
to manage staff data and patients data
effectively. the main aim of developing
38
“HEALTH Prediction MANAGEMENT SYSTEM” is to
computerize the Front Office
Management of Hospital. Hospital Management
System is designed for multi-specialty
hospitals, to cover a wide range of hospital
administration and management processes.
The project Hospital Management system
includes registration of patients, storing
their details into the system, and also
computerized billing in the pharmacy,
and labs. Health prediction is a field in
which accurate record keeping and communication
are critical. The software has the facility
to give a unique id for every patient
and stores the details of every patient and
the staff automatically. With the
increase of demand in hospitals, we need
effective data management system for
handling patient’s data, staff data and
treatment details in an effective way.
It deals with the collection of patient’s
information, diagnosis details, etc.
It includes a search facility to know the
current status of each room.
User can search availability of a doctor and
the details of a patient using the id.</p></center>
</div>
</div>
</div>
</div>
</body>
</html>
Admin Login
transitional.dtd">
<head>
charset=utf-8" />
yui.js"></script>
39
</head>
<body>
<div class="main">
<div class="logo">
System</font></h1>
</div>
<ul>
<li><a href="index.html">Home</a></li>
href="admin.jsp">Admin</a></li>
</ul>
</div>
</div>
</div>
<br>
<center>
<h2><font color="black">Admin
Login</font></h2>
<form action="adminact.jsp" method="post"
id="adminact" >
<table>
<tr>
<td align="right"><font size="2"
color="black"> User Name: </font>
</td><td>
40
<input type="text" align="left"
size="25" name="username" placeholder=UserName required
/></td>
</tr> <tr></tr> <tr></tr> <tr></tr>
<tr></tr> <tr></tr> <tr></tr>
<tr>
color="black">Password:</font>
</td><td>
<input type="password" align="left"
size="25" name="password" placeholder=Password required
/></td>
</tr>
<tr>
<td>
<center> <font size="2"
color="green">

<input type="submit" form="adminact"
align="right" value='Submit' />
</td>
<td>
<font size="2" color="green">
<input type="reset" align="left"
value='Reset' />
</td>
</tr>
</center>
</table></center>
</div>
</div>
</div>
</div>
</body>
</html>
Admin Home
transitional.dtd">
<head>
41
charset=utf-8" />
yui.js"></script>
</head>
<body>
<div class="main">
<div class="logo">
System</font></h1>
</div>
<ul>
href="adminhome.jsp">Home</a></li>
<li><a href="viewuser.jsp">View Users</a></li>
<li><a href="viewdoctor.jsp">View Doctors</a></li>
<li><a href="logout.jsp">Logout</a></li>
</ul>
</div>
<%
if(request.getParameter("msg")!=null){%>
<script>alert('Login Sucessful..!')</script>
<%}
%>
</div>
</div>
<marquee><h1><font color="black">Welcome
Admin</font></h1></marquee>
</div>
42
</div>
</div>
</div>
</body>
</html>
View Users
transitional.dtd">
<head>
charset=utf-8" />
yui.js"></script>
</head>
<body>
<div class="main">
<div class="logo">
System</font></h1>
</div>
<ul>
<li><a href="adminhome.jsp">Home</a></li>
<li class="active"><a href="viewuser.jsp">View
Users</a></li>
</ul>
</div>
<%
43
<%}
%>
</div>
</div>
<%@page contentType="text/html" pageEncoding="UTF-8"%>
<%@ page import ="java.sql.*" %>
<%@page import="databaseconnection.databasecon"%>
<%
Connection co = null;
try{
co = databasecon.getconnection();
PreparedStatement pst=co.prepareStatement("select *
from user");
ResultSet rs=pst.executeQuery();
%>
<style>
th{
color: black;
}
</style>
<br>
<center> <h2>User Details</h2>
<table style="width:80%" border="2"><br>
<tr>
<th style="color:red">User Name</th>
<th style="color:red">Email</th>
<th style="color:red">Mobile</th>
<th style="color:red">DOB</th>
<th style="color:red">Gender</th>
<th style="color:red">Address</th>
</tr>
<%
while(rs.next()){
%>
<tr>
<th><%=rs.getString(1)%></th>
</tr>
44
<% }
%></table></center>
<%}
catch(Exception e)
{
System.out.println(e);
}
%>
</div>
</div>
</div>
</div>
</body>
</html>
View Doctors
transitional.dtd">
<head>
charset=utf-8" />
yui.js"></script>
</head>
<body>
<div class="main">
<div class="logo">
System</font></h1>
</div>
<ul>
45
<li class="active"><a href="viewdoctor.jsp">View
Doctors</a></li>
</ul>
</div>
<%
<%}
%>
<style>
th{
color: black;
}
</style>
</div>
</div>
<%
try{
from doctor");
%>
<br>
<center> <h2>Doctor Details</h2>
<tr>
</tr>
<%
while(rs.next()){
46
%>
<tr>
</tr>
<% }
%></table></center>
<%}
catch(Exception e)
{
}
%>
</div>
</div>
</body>
</html>
Admin Logout
<%
session.invalidate();
response.sendRedirect("index.html");
%>
Doctor Registration
transitional.dtd">
<head>
charset=utf-8" />
yui.js"></script>
47
</head>
<body>
<div class="main">
<div class="logo">
System</font></h1>
</div>
<ul>
<li><a href="doctor.jsp">Home</a></li>
href="doctor.jsp">Doctor</a></li>
</ul>
</div>
<style>
td{
color: black;
}
</style>
</div>
</div>
<br><center>
<h2><font color="black">Doctor
Registration</font></h2></center>
<form action="doctorregistrationact.jsp"
method="post" ><center>
<center><table width="365"><br>
<tr>
<td width="300" height="43"><b>User
Name</b></td>
<td width="200">
48
<input id="username" name="username"
class="text" placeholder="UserName" /></td>
</tr>
<tr>
<td height="43"><b>Password</b></td>
<td>
<input type="password" id="password"
name="password" class="text" placeholder="Password"/></td>
</tr>
<tr>
<td height="43"><b>Email</b></td>
<td>
<input type="email" id="email"
name="email" class="text" placeholder="Email" /></td>
</tr>
<tr>
<td
height="43"><b>Specialization</b></td>
<td>
<input type="text" id="text"
name="specialization" class="text"
placeholder="Specialization" /></td>
</tr>
<tr>
<td height="43"><b>Mobile</b></td>
<td>
<input type="text" id="mobile"
name="mobile" class="text" placeholder="Mobile"/></td>
</tr>
<tr>
<td height="43"><b>Date of
Birth</b></td>
<td>
<input type="date" id="dob"
name="dob" class="text" placeholder="DOB"/></td>
</tr>
<tr>
<td height="43"><b>Gender</b></td>
<td><select id="gender" name="gender"
style="width:175px;" class="text">
<option>--Select--</option>
<option>Female</option>
<option>Male</option>
</select></td>
</tr>
<tr>
<td height="65"><b>Address</b></td>
49
<td>
<textarea type="text" id="address"
name="address" rows="3" cols="30" placeholder="Address">
</textarea></td>
</tr>
<tr>
<td height="65"><b> Profile
Pic</b></td>
<td>
<input type="file" name="pic"
rows="3" cols="30" >
</input></td>
</tr>
<tr>
<td height="43" rowspan="3">
<p> </p></td>
<td align="left" valign="middle">
<p>
</p>
<p>
<input name="submit" type="submit"
value="REGISTER" />
</p>
</td>
</tr>
</b>
</center>
</table>
</form>
</center>
</body>
</html>
Doctor Login
transitional.dtd">
<head>
charset=utf-8" />
yui.js"></script>
50
</head>
<body>
<div class="main">
<div class="logo">
System</font></h1>
</div>
<ul>
href="doctor.jsp">Doctor</a></li>
</ul>
</div>
</div>
</div>
<br>
<center>
<h2><font color="black">Doctor
Login</font></h2>
<form action="doctoract.jsp" method="post"
id="doctoract" >
<table>
<tr>
</td><td>
/></td>
51
<tr>
</td><td>
/></td>
</tr>
<tr>
<td>
color="black">

<input type="submit" form="doctoract"
</td>
<td>
<font size="2" color="black">
value='Reset' />

<a href="doctorregistration.jsp">
<font color="black">REGISTRATION?</font></a>
</td>
</tr>
</center>
</table></center>
</div>
</div>
</div>
</div>
</body>
</html>
Doctor Home
transitional.dtd">
<head>
52
charset=utf-8" />
yui.js"></script>
</head>
<body>
<div class="main">
<div class="logo">
System</font></h1>
</div>
<%
<%}
%>
<ul>
href="doctorhome.jsp">Home</a></li>
<li><a href="viewfeedback.jsp"> View
Feedback</a></li>
<li ><a href="logout.jsp">Logout</a></li>
</ul>
</div>
</div>
</div>
<%
String username =
session.getAttribute("username").toString();
%>
53
<marquee behaviour="scroll" scrollamount="13">
<h1><font color="black">Welcome Dr.
<%=username%></font></h1></marquee>
</div>
</div>
</div>
</div>
</body>
</html>
View Feedback
transitional.dtd">
<head>
charset=utf-8" />
yui.js"></script>
</head>
<body>
<div class="main">
<div class="logo">
System</font></h1>
</div>
<%
<%}
%>
<ul>
54
<li ><a href="doctorhome.jsp">Home</a></li>
<li class="active"><a href="viewfeedback.jsp"> View
Feedback</a></li>
</ul>
</div>
</div>
</div>
<%
String username =
try{
from query where doctor = '"+username+"'");
%>
<style>
th{
color: black;
}
</style>
<br>
<center> <h2><font color="black">User Query
Details</font></h2>
<tr>
<th>Query From</th>
<th>Query</th>
<th>Reply</th>
</tr>
<%
while(rs.next()){
%>
55
<tr>
<th><a
href="reply.jsp?username=<%=rs.getString(1)%>&query=<%=rs.g
etString(3)%>"> <font color="black">Reply</font></a>
</tr>
<% }
%></table></center>
<%}
catch(Exception e)
{
}
%>
</div>
</div>
</div>
</div>
</body>
</html>
Reply Feedback
transitional.dtd">
<head>
charset=utf-8" />
yui.js"></script>
56
</head>
<body>
<div class="main">
<div class="logo">
System</font></h1>
</div>
<%
<%}
%>
<ul>
href="doctorhome.jsp">Home</a></li>
<li><a href="viewfeedback.jsp"> View
Feedback</a></li>
</ul>
</div>
</div>
</div>
<%
String username = request.getParameter("username");
String query = request.getParameter("query");
%>
<br><center>
<h2><font color="black">Reply</font></h2></center>
<form action="replyact.jsp?query=<%=query%>"
<tr>
<td width="300"
height="43"><b>To</b></td>
<td width="200">
57
<input id="username"
name="username" value="<%=username%>" readonly=""
placeholder="UserName" /></td>
</tr>
<tr>
<td height="65"><b>Reply</b></td>
<td>
<textarea type="text" name="reply"
rows="3" cols="30" placeholder="Enter your reply">
</textarea></td>
</tr>
<tr>
<p> </p></td>
<p>
</p>
<p>
value="Reply" />
</p>
</td>
</tr>
</div>
</div>
</div>
</div>
</body>
</html>
Doctor Information
<%@page import="java.sql.PreparedStatement"%>
<%@page import="java.sql.DriverManager"%>
<%@page import="java.sql.Connection"%>
<%@page import="java.sql.ResultSet"%>
transitional.dtd">
<head>
58
charset=utf-8" />
yui.js"></script>
</head>
<body>
<div class="main">
<div class="logo">
System</font></h1>
</div>
<ul>
<li ><a href="userhome.jsp">Home</a></li>
href="search.jsp">Search</a></li>
<li><a href="userviewfeedback.jsp"> Doctor
Feedback</a></li>
</ul>
</div>
</div>
</div>
<style>
tr{
color:black;
}
</style>
<%
String name=request.getParameter("name");
59
ResultSet rs=null;
try{
from doctor where specialization = '"+name+"'");
pst.execute();
rs =pst.getResultSet();
}catch(Exception e){
e.printStackTrace();
}
%>
<center>
<table>
<% while(rs.next()){
String
username=request.getParameter("username");
String email=request.getParameter("email");
String mobile=request.getParameter("mobile");
String address=request.getParameter("address");
%>
<tr>
<td>
<%
String image=rs.getString("pic");
%>
<form
action="query.jsp?username=<%=rs.getString("username")%>"
method="post">
<tr width="100%">
<td><img src="images/<%=image%>"
width="180" height="130"></td>
<td>
<b>
         Doctor
Name </b>
<b><%=rs.getString("username")%></b><br>
60
<b>
         Email :
</b>
<b><%=rs.getString("email")%></b><br>
<b>
         Mobile :
</b>
<b><%=rs.getString("mobile")%></b><br>
<b>
         Address :
</b>
<b><%=rs.getString("address")%></b><br>
<b>
         Query :
</b>
<input type="text" name="query">
<input type="submit" value="query">
</form>
</td>
</td>
</tr>
</tr>
<%}%>
</table>
</div>
</div>
</div>
</div>
</body>
</html>
Doctor Logout
<%
%>
User Registrection
transitional.dtd">
61
<head>
charset=utf-8" />
yui.js"></script>
</head>
<body>
<div class="main">
<div class="logo">
System</font></h1>
</div>
<ul>
<li><a href="user.jsp">Home</a></li>
href="user.jsp">User</a></li>
</ul>
</div>
</div>
</div>
<style>
td{
color: black;
}
</style>
<br><center>
62
<h2><font color="black">User
Registration</font></h2></center>
<form action="userregistrationact.jsp"
<tr>
<td width="300" height="43"><b>User
Name</b></td>
<td width="200">
<input id="username" name="username"
class="text" placeholder="UserName" /></td>
</tr>
<tr>
<td height="43"><b>Password</b></td>
<td>
<input type="password" id="password"
name="password" class="text" placeholder="Password"/></td>
</tr>
<tr>
<td height="43"><b>Email</b></td>
<td>
<input type="email" id="email"
name="email" class="text" placeholder="Email" /></td>
</tr>
<tr>
<td height="43"><b>Mobile</b></td>
<td>
<input type="text" id="mobile"
name="mobile" class="text" placeholder="Mobile"/></td>
</tr>
<tr>
<td height="43"><b>Date of
Birth</b></td>
<td>
<input type="date" id="dob"
name="dob" class="text" placeholder="DOB"/></td>
</tr>
<tr>
<td height="43"><b>Gender</b></td>
<td><select id="gender" name="gender"
style="width:175px;" class="text">
<option>--Select--</option>
<option>Female</option>
<option>Male</option>
</select></td>
</tr>
<tr>
63
<td height="65"><b>Address</b></td>
<td>
<textarea type="text" id="address"
name="address" rows="3" cols="30" placeholder="Address">
</textarea></td>
</tr>
<tr>
<p> </p></td>
<p>
</p>
<p>
value="REGISTER" />
</p>
</td>
</tr>
</center>
</table>
</form>
</center>
</body>
</html>
User Login
transitional.dtd">
<head>
charset=utf-8" />
yui.js"></script>
</head>
<body>
64
<div class="main">
<div class="logo">
System</font></h1>
</div>
<ul>
href="user.jsp">User</a></li>
</ul>
</div>
</div>
</div>
<br>
<center>
Login</font></h2>
<form action="useract.jsp" method="post"
id="useract" >
<table>
<tr>
</td><td>
/></td>
<tr>
</td><td>
65
/></td>
</tr>
<tr>
<td>
color="black">

<input type="submit" form="useract"
</td>
<td>
<font size="2" color="black">
value='Reset' />

<a href="userregistration.jsp">
<font color="black">REGISTRATION?</font></a>
</td>
</tr>
</center>
</table></center>
</div>
</div>
</div>
</div>
</body>
</html>
User Home
transitional.dtd">
<head>
charset=utf-8" />
yui.js"></script>
66
</head>
<body>
<div class="main">
<div class="logo">
System</font></h1>
</div>
<%
<%}
%>
<ul>
href="userhome.jsp">Home</a></li>
<li><a href="search.jsp">Search</a></li>
<li><a href="userviewfeedback.jsp">Doctor
Feedback</a></li>
</ul>
</div>
</div>
</div>
<%
String username =
%>
<marquee behaviour="scroll" scrollamount="13">
<h1><font color="black">Welcome <%=username%>
</font></h1></marquee>
</div>
67
</div>
</div>
</div>
</body>
</html>
User View
transitional.dtd">
<head>
charset=utf-8" />
yui.js"></script>
</head>
<body>
<div class="main">
<div class="logo">
System</font></h1>
</div>
<ul>
<li class="active"><a href="viewuser.jsp">View
Users</a></li>
</ul>
</div>
<%
68
<%}
%>
</div>
</div>
<%
try{
from user");
%>
<style>
th{
color: black;
}
</style>
<br>
<center> <h2>User Details</h2>
<tr>
</tr>
<%
while(rs.next()){
%>
<tr>
69
</tr>
<% }
%></table></center>
<%}
catch(Exception e)
{
}
%>
</div>
</div>
</body>
</html>
Doctor View
transitional.dtd">
<head>
charset=utf-8" />
yui.js"></script>
</head>
<body>
<div class="main">
<div class="logo">
70
System</font></h1>
</div>
<ul>
<li class="active"><a href="viewdoctor.jsp">View
Doctors</a></li>
</ul>
</div>
<%
<%}
%>
<style>
th{
color: black;
}
</style>
</div>
</div>
<%
try{
from doctor");
%>
<br>
<center> <h2>Doctor Details</h2>
<tr>
71
</tr>
<%
while(rs.next()){
%>
<tr>
</tr>
<% }
%></table></center>
<%}
catch(Exception e)
{
}
%>
</div>
</div>
</body>
</html>
Query
<%@page import="java.sql.*"%>
<%@ page session="true" %>
<html>
<body>
72
<%
String username =
String
doctorname=request.getParameter("username");
String query=request.getParameter("query");
String reply = "Waiting";
try
{
PreparedStatement pst2=co.prepareStatement("insert
into query(username,doctor,query,reply)
values('"+username+"','"+doctorname+"','"+query+"','"+reply
+"')");
pst2.executeUpdate();
response.sendRedirect("search.jsp?msgg=success");
}
catch(SQLException e)
{
out.print(e.getMessage());
}
%>
</body>
</html>
Search
transitional.dtd">
<head>
charset=utf-8" />
yui.js"></script>
73
</head>
<body>
<div class="main">
<div class="logo">
System</font></h1>
</div>
<ul>
<li ><a href="userhome.jsp">Home</a></li>
href="search.jsp">Search</a></li>
<li ><a href="userviewfeedback.jsp"> Doctor
Feedback</a></li>
</ul>
</div>
</div>
</div>
<style>
tr{
color:black;
}
</style>
<br><center>
Search</font></h2></center>
<form action="searchact.jsp" method="post"
><center>
<tr>
<td height="43">Symptom 1</td>
<td><select id="symptom1"
name="symptom1" required="" style="width:175px;"
class="text">
74
<option value="">--Select--</option>
<option
value="Headache">Headache</option>
<option
value="Vomiting">Vomiting</option>
<option
value="Diarrhoea">Diarrhoea</option>
<option
value="Dehydration">Dehydration</option>
</select></td>
</tr>
<tr>
class="text">
<option
<option
<option
<option
</select></td>
</tr>
<tr>
class="text">
<option
<option
<option
<option
</select></td>
</tr>
<tr>
<p></p></td>
75
<p>
</p>
<p>
value="Submit" />
</p>
</td>
</tr>
</center>
</table>
</form>
</center>
</div>
</div>
</div>
</div>
</body>
</html>
Feedback
transitional.dtd">
<head>
charset=utf-8" />
yui.js"></script>
</head>
<body>
<div class="main">
<div class="logo">
76
System</font></h1>
</div>
<%
<%}
%>
<ul>
<li ><a href="doctorhome.jsp">Home</a></li>
<li class="active"><a href="viewfeedback.jsp"> View
Feedback</a></li>
</ul>
</div>
</div>
</div>
<%
String username =
try{
from query where doctor = '"+username+"'");
%>
<style>
th{
color: black;
}
</style>
<br>
<center> <h2><font color="black">User Query
Details</font></h2>
77
<tr>
<th>Query From</th>
<th>Query</th>
<th>Reply</th>
</tr>
<%
while(rs.next()){
%>
<tr>
<th><a
href="reply.jsp?username=<%=rs.getString(1)%>&query=<%=rs.g
etString(3)%>"> <font color="black">Reply</font></a>
</tr>
<% }
%></table></center>
<%}
catch(Exception e)
{
}
%>
</div>
</div>
</div>
</div>
</body>
</html>
User Logout
<%
%>
78
4.2 Package
Data Base Connection

package databaseconnection;
import java.sql.*;
public class databasecon

{
static Connection co;
public static Connection getconnection()
{
try
{
Class.forName("com.mysql.jdbc.Driver");
co =
DriverManager.getConnection("jdbc:mysql://localhost:3306/he
althprediction","root","root");
}
catch(Exception e)
{
System.out.println("Database Error"+e);
}
return co;
}
4.3 DataBase
/*
SQLyog Community Edition- MySQL GUI v7.15
MySQL - 5.5.29 : Database - healthprediction
***********************************************************
**********
*/
/*!40101 SET NAMES utf8 */;
/*!40101 SET SQL_MODE=''*/;
79
/*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS,
FOREIGN_KEY_CHECKS=0 */;
/*!40101 SET @OLD_SQL_MODE=@@SQL_MODE,
SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */;
CREATE DATABASE /*!32312 IF NOT EXISTS*/`healthprediction`

/*!40100 DEFAULT CHARACTER SET latin1 */;
USE `healthprediction`;
/*Table structure for table `doctor` */
DROP TABLE IF EXISTS `doctor`;
CREATE TABLE `doctor` (

ùsername` varchar(50) DEFAULT NULL,
`password` varchar(50) DEFAULT NULL,
èmail` varchar(60) DEFAULT NULL,
`specialization` varchar(100) DEFAULT NULL,
`mobile` varchar(50) DEFAULT NULL,
`dob` date DEFAULT NULL,
`gender` varchar(50) DEFAULT NULL,
àddress` varchar(50) DEFAULT NULL,
`pic` varchar(100) DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
/*Data for the table `doctor` */
insert into
`doctor`(ùsername`,`password`,èmail`,`specialization`,`mo
bile`,`dob`,`gender`,àddress`,`pic`) values
('shiva','shiva','shiva.1000projects@gmail.com','Typhoid','
8574125630','1990-09-17','Male','chennai \r\n
',NULL),('nikil','nikil','nikil@gmail.com','malaria','87459
63210','1991-06-14','Male','hyd \r\n
','slide2.jpg');
/*Table structure for table `query` */
DROP TABLE IF EXISTS `query`;
CREATE TABLE `query` (

`doctor` varchar(100) DEFAULT NULL,
`query` varchar(100) DEFAULT NULL,
`reply` varchar(100) DEFAULT 'Waiting'
80
/*Data for the table `query` */
insert into `query`(ùsername`,`doctor`,`query`,`reply`)

values ('ram','nikil','what are the symptoms of
malaria?','Its a fever effected by mosquito.\r\n
'),('ram','nikil','kjsgdhkfgsdv','Waiting'),(NULL,NULL,NULL
,'Waiting'),('ram','shiva','Need Your
Appointment....','Meet me at 10\r\n
');
/*Table structure for table `search` */
DROP TABLE IF EXISTS `search`;
CREATE TABLE `search` (

ìd` int(100) NOT NULL AUTO_INCREMENT,
`symptom1` varchar(100) DEFAULT NULL,
`result` varchar(100) DEFAULT NULL,
PRIMARY KEY (ìd`)
) ENGINE=InnoDB AUTO_INCREMENT=25 DEFAULT CHARSET=latin1;
/*Data for the table `search` */
insert into
`search`(ìd`,`symptom1`,`symptom2`,`symptom3`,`result`)
values
(1,'Headache','Vomiting','Dehydration','Malaria'),(2,'Heada
che','Vomiting','Diarrhoea','Typhoid'),(3,'Headache','Dehyd
ration','Diarrhoea','Dengue'),(4,'Headache','Diarrhoea','De
hydration','Dengue'),(5,'Headache','Dehydration','Vomiting'
,'Malaria'),(6,'Headache','Diarrhoea','Vomiting','Typhoid')
,(7,'Vomiting','Headache','Dehydration','Malaria'),(8,'Vomi
ting','Headache','Diarrhoea','Typhoid'),(9,'Vomiting','Diar
rhoea','Headache','Typhoid'),(10,'Vomiting','Diarrhoea','De
hydration','Dengue'),(11,'Vomiting','Dehydration','Headache
','Malaria'),(12,'Vomiting','Dehydration','Diarrhoea','Deng
ue'),(13,'Dehydration','Vomiting','Headache','Malaria'),(14
,'Dehydration','Headache','Vomiting','Malaria'),(15,'Dehydr
ation','Diarrhoea','Headache','Dengue'),(16,'Dehydration','
Headache','Diarrhoea','Dengue'),(17,'Dehydration','Headache
','Vomiting','Malaria'),(18,'Dehydration','Vomiting','Heada
che','Malaria'),(19,'Diarrhoea','Headache','Vomiting','Typh
oid'),(20,'Diarrhoea','Vomiting','Headache','Typhoid'),(21,
'Diarrhoea','Dehydration','Vomiting','Dengue'),(22,'Diarrho
81
ea','Vomiting','Dehydration','Dengue'),(23,'Diarrhoea','Hea
dache','Dehydration','Dengue'),(24,'Diarrhoea','Dehydration
','Headache','Dengue');
/*Table structure for table ùser` */
DROP TABLE IF EXISTS ùser`;
CREATE TABLE ùser` (

`password` varchar(50) DEFAULT NULL,
èmail` varchar(60) DEFAULT NULL,
`mobile` varchar(50) DEFAULT NULL,
`dob` date DEFAULT NULL,
`gender` varchar(50) DEFAULT NULL,
àddress` varchar(50) DEFAULT NULL
/*Data for the table ùser` */
insert into
ùser`(ùsername`,`password`,èmail`,`mobile`,`dob`,`gender
`,àddress`) values
('ram','ram','ramu.1000projects@gmail.com','9874125630','19
91-06-15','Male','hyd \r\n
'),(NULL,NULL,NULL,NULL,NULL,NULL,NULL);
/*!40101 SET SQL_MODE=@OLD_SQL_MODE */;

/*!40014 SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS */;
82
CHAPTER 5
TESTING &VALIDATION
INTRODUCTION:
Testing is the debugging program is one of the most critical aspects of the
computer programming triggers, without programming that works, the system would
never produce an output of which it was designed. Testing is best performed when user
development is asked to assist in identifying all errors and bugs. The sample data are used
for testing. It is not quantity but quality of the data used the matters of testing. Testing is
aimed at ensuring that the system was accurately an efficiently before live operation
commands.
Testing objectives:
The main objective of testing is to uncover a host of errors, systematically

and with minimum effort and time. Stating formally, we can say, testing is a process of
executing a program with intent of finding an error.
1 A successful test is one that uncovers an as yet undiscovered error.

2 A good test case is one that has probability of finding an error, if it exists.
3 The test is inadequate to detect possibly present errors.
4 The software more or less confirms to the quality and reliable standards.
5.1. Levels of Testing:
Code testing:
This examines the logic of the program. For example, the logic for updating
various sample data and with the sample files and directories were tested and verified.
83
Specification Testing:
Executing this specification starting what the program should do and how it
should performed under various conditions. Test cases for various situation and
combination of conditions in all the modules are tested.
Unit testing:
In the unit testing we test each module individually and integrate with the overall
system. Unit testing focuses verification efforts on the smallest unit of software design in
the module. This is also known as module testing. The module of the system is tested
separately. This testing is carried out during programming stage itself. In the testing step
each module is found to work satisfactorily as regard to expected output from the
module. There are some validation checks for fields also. For example the validation
check is done for varying the user input given by the user which validity of the data
entered. It is very easy to find error debut the system.
Each Module can be tested using the following two Strategies:
1. Black Box Testing

2. White Box Testing
BLACK BOX TESTING
What is Black Box Testing?
Black box testing is a software testing techniques in which functionality of the

software under test (SUT) is tested without looking at the internal code structure,
implementation details and knowledge of internal paths of the software. This type of
testing is based entirely on the software requirements and specifications.
In Black Box Testing we just focus on inputs and output of the software system without
bothering about internal knowledge of the software program.
84
The above Black Box can be any software system you want to test. For example :
an operating system like Windows, a website like Google ,a database like Oracle or even
your own custom application. Under Black Box Testing , you can test these applications
by just focusing on the inputs and outputs without knowing their internal code
implementation.
Black box testing - Steps
Here are the generic steps followed to carry out any type of Black Box Testing.
 Initially requirements and specifications of the system are examined.

 Tester chooses valid inputs (positive test scenario) to check whether SUT
processes them correctly. Also some invalid inputs (negative test scenario) are
chosen to verify that the SUT is able to detect them.
 Tester determines expected outputs for all those inputs.
 Software tester constructs test cases with the selected inputs.
 The test cases are executed.
 Software tester compares the actual outputs with the expected outputs.
 Defects if any are fixed and re-tested.
Types of Black Box Testing
There are many types of Black Box Testing but following are the prominent ones
 Functional testing – This black box testing type is related to functional

requirements of a system; it is done by software testers.
85
 Non-functional testing – This type of black box testing is not related to testing of
a specific functionality, but non-functional requirements such as performance,
scalability, usability.
 Regression testing – Regression testing is done after code fixes , upgrades or any
other system maintenance to check the new code has not affected the existing
code.
WHITE BOX TESTING
White Box Testing is the testing of a software solution's internal coding and
infrastructure.It focuses primarily on strengthening security, the flow of inputs and
outputs through the application, and improving design and usability.White box testing is
also known as clear, open, structural, and glass box testing.
It is one of two parts of the "box testing" approach of software testing. Its counter-
part, blackbox testing, involves testing from an external or end-user type perspective. On
the other hand, Whitebox testing is based on the inner workings of an application and
revolves around internal testing. The term "whitebox" was used because of the see-
through box concept. The clear box or whitebox name symbolizes the ability to see
through the software's outer shell (or "box") into its inner workings. Likewise, the "black
box" in "black box testing" symbolizes not being able to see the inner workings of the
software so that only the end-user experience can be tested
What do you verify in White Box Testing ?
White box testing involves the testing of the software code for the following:
 Internal security holes

 Broken or poorly structured paths in the coding processes
 The flow of specific inputs through the code
 Expected output
 The functionality of conditional loops
 Testing of each statement, object and function on an individual basis
86
The testing can be done at system, integration and unit levels of software development.
One of the basic goals of whitebox testing is to verify a working flow for an application.
It involves testing a series of predefined inputs against expected or desired outputs so that
when a specific input does not result in the expected output, you have encountered a bug.
How do you perform White Box Testing?
To give you a simplified explanation of white box testing, we have divided it into
two basic steps. This is what testers do when testing an application using the white box
testing technique:
STEP 1) UNDERSTAND THE SOURCE CODE
The first thing a tester will often do is learn and understand the source code of the
application. Since white box testing involves the testing of the inner workings of an
application, the tester must be very knowledgeable in the programming languages used in
the applications they are testing. Also, the testing person must be highly aware of secure
coding practices. Security is often one of the primary objectives of testing software. The
tester should be able to find security issues and prevent attacks from hackers and naive
users who might inject malicious code into the application either knowingly or
unknowingly.
Step 2) CREATE TEST CASES AND EXECUTE
The second basic step to white box testing involves testing the application’s
source code for proper flow and structure. One way is by writing more code to test the
application’s source code. The tester will develop little tests for each process or series of
processes in the application. This method requires that the tester must have intimate
knowledge of the code and is often done by the developer. Other methods include manual
testing, trial and error testing and the use of testing tools as we will explain further on in
this article.
87
System testing:
Once the individual module testing is completed, modules are assembled

and integrated to perform as a system. The top down testing, which began from upper
level to lower level module, was carried out to check whether the entire system is
performing satisfactorily.
There are three main kinds of System testing:
1 Alpha Testing
2 Beta Testing
3 Acceptance Testing
Alpha Testing:
This refers to the system testing that is carried out by the test team with the Organization.
Beta Testing:
This refers to the system testing that is performed by a selected group of friendly
customers
Acceptance Testing:
This refers to the system testing that is performed by the customer to determine
whether or not to accept the delivery of the system.
Integration Testing:
Data can be lost across an interface, one module can have an adverse effort on the
other sub functions, when combined, may not produce the desired major functions.
Integrated testing is the systematic testing for constructing the uncover errors within the
interface. The testing was done with sample data. The developed system has run
successfully for this sample data. The need for integrated test is to find the overall system
performance.
88
Output testing:
After performance of the validation testing, the next step is output testing. The output
displayed or generated by the system under consideration is tested by asking the user
about the format required by system. The output format on the screen is found to be
correct as format was designed in the system phase according to the user needs. Hence
the output testing does not result in any correction in the system.
Test plan:
The test-plan is basically a list of testcases that need to be run on the system. Some of the
testcases can be run independently for some components (report generation from the
database, for example, can be tested independently) and some of the testcases require the
whole system to be ready for their execution. It is better to test each component as and
when it is ready before integrating the components. It is important to note that the
testcases cover all the aspects of the system (ie, all the requirements stated in the RS
document).
89
CHAPTER 6
SCREEN SHOTS
HOME PAGE
Application main page displays main modules like Admin, User and Doctor.
90
ADMIN LOGIN PAGE
Admin login page in which admin can get logged in by entering valid username and password.
ADMIN MAIN PAGE
Admin main page displays modules like view users and view doctors.
91
VIEW USERS PAGE
Admin view all details of users in user details page.
VIEW DOCTORS PAGE
Admin view all details of doctors in doctor’s details page.
92
USER REGISTRATION PAGE
Users need to fill all the details in the registration page to get username and password.
USER LOGIN PAGE
User can get login by entering unique username and password
93
USER MAIN PAGE
User main page displays modules like search and doctor feedback.
USER SEARCH PAGE
Users search page enables users to select options and find the result.
94
USER SEARCH RESULT PAGE
USER VIEW DOCTOR INFORMATION PAGE
95
USER VIEW DOCTORS FEEDBACK PAGE
DOCTOR REGISTRATION PAGE
Doctors need to fill all the details in the registration page to get username and password.
96
DOCTOR LOGIN PAGE
Doctor can get login by entering unique username and password.
DOCTOR MAIN PAGE
Doctor main page displays modules like view feedback.
97
DOCTOR VIEW FEEDBACK PAGE
Doctor can view the details of users query in view feedback page.
DOCTOR REPLY TO USER PAGE
Doctor sends reply to user.
98
CHAPTER 7
CONCLUSION
Our project ―Health Prediction Management System‖ provides easy and simple way to
users and doctors to communicate with each other. Our project also saves lot of time and
effort to both users and doctors.
99

Health Prediction Management System PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Health Prediction Management System PDF

Uploaded by

Copyright:

Available Formats

“Health Prediction Management System”

Submitted to the Department of Computer Science and Engineering

MEENAKSHI NIAL Reg.No: 1601204061

Under the Guidance of

DR. RAGHUNATH KAR

DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

MEENAKSHI NIAL Reg.No: 1601204061

Under the Guidance of

DR. RAGHUNATH KAR

DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

MANAGEMENT SYSTEM” is carried out by Ms. Meenakshi Nial, Reg. No.

are the bonafide students of Roland Institute of Technology in partial fulfillment

2019-20. It is further certified that all corrections / suggestions indicated for

project report has been approved as it satisfies the academic requirements in

respect of project work prescribed for the said degree.

Name of the Guide Name of the HOD

(External Examiner) Dr. Tarini Charan Tripathy

and Engineering, Roland Institute of Technology, Surya Vihar, Berhampur,

hereby declare that the project work entitled “HEALTH PREDICTION

MANAGEMENT SYSTEM” submitted to BPUT, Rourkela during the academic

year 2019-2020, is a record of an original work done by us under the guidance of

DR. RAGHUNATH KAR, Assistant / Associate Professor in Department of

Computer Science and Engineering, Roland Institute of Technology, Berhampur.

award of the degree of Bachelor of Technology in Computer Science and

report do not represent the views of any individual.

Ms Meenakshi Nial, Reg. No. 1601204061 Signature_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Ms. Sonia Das, Reg. No. 1601204076 Signature_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Mr Tikeram Naik, Reg. No. 1601204075 Signature_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Mr. Sarat Chandra Naik, Reg. No. 1601204063 Signature_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

encouraged us in every aspect of the project HEALTH PREDICTION MANAGEMENT

successful completion of our project work.

We are indebted to our Chairman Dr. J. Surya Rao, Director Mdm. J.

providing us with unfailing support and continuous encouragement throughout our

accomplishment would not have been possible without them.

Ms Meenakshi Nial, Signature_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Ms. Sonia Das, Signature_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Mr Tikeram Naik, Signature_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Mr. Sarat Chandra Naik, Signature_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

―Health Prediction Management System‖ is a project which is developed to

1.2 PROPOSED SYSTEM:

1.4 SYSTEM REQUIREMENTS

1.4.1 HARDWARE REQUIREMENTS:

 Processor : Pentium –III

1.4.2 SOFTWARE REQUIREMENTS:

 Operating System : Windows7/8/10/XP

2.1 THE STUDY OF THE SYSTEM

 To conduct studies and analyses of an operational and technological nature, and

The logical design of a system pertains to an abstract representation of the data

2.2 INPUT & OUTPUT REPRESENTATION

 What data should be given as input?

Input Design is the process of converting a user-oriented description of the input

 Convey information about past activities, current status or projections of the

2.3 Features of Java

The Java Programming Language

The Java platform has two components:

The Java API is a large collection of ready-made software components that

How Will Java Technology Change My Life?

1. SQL Level API

3. JDBC must be implemental on top of common database interfaces

6. Use strong, static typing wherever possible

7. Keep the common cases simple

Finally we decided to proceed the implementation using Java Networking.

JAVA HA TWO THINGS: A PROGRAMMING LANGUAGE AND A PLATFORM.

/!40101 SET NAMES utf8 /;

/!40101 SET SQL_MODE=''/;

CREATE DATABASE /!32312 IF NOT EXISTS/`healthprediction`

/Table structure for table `doctor` /

/Data for the table `doctor` /

/Table structure for table `query` /

/Table structure for table `search` /