Abstract

Health insurance is an web application, it provides the health insurance policies according to the require-
ment.While we are in the situation where new dangerous diseases are evolving ,accidents and heartattacks
are common nowdays . Health issue that result in emergency care or an expensive treatment which may not
be affordable leads to death of individual.
To overcome this problem , we have come up with the web Application Health insurance that covers the
cost of an insured individual’s medical diagnosis and surgical expenses, this product is related to Health
insurance domain, which involves the making new Policy for different age groups of patients admitted to
the hospital, and settlement done by the Members of the Policy Providers etc. Health insurance helps people
pay a nominal fee for insurance policy for health care by combining the risk of high health care costs across
many people, Thus, health insurance makes the cost of health care affordable for most people.
Contents

1 Introduction 1
1.1 Project Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1
1.1.1 Problem Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1
1.1.2 Proposed Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1
1.1.3 Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2
1.1.4 Scope and Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2

2 Literature Survey 3
2.1 Domain Study . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3

2.1.1 Existing Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3

2.1.2 Drawbacks of Existing Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
2.2 Tools and Technologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
2.3 Feasibility Study . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4

3 Hardware and Software Requirements 5

3.1 Hardware Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
3.1.1 Production . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
3.1.2 Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
3.2 Software Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

4 Software Requirements Specification 6

4.1 Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
4.2 Functional Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
4.2.1 Admin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
4.2.2 Customer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
4.3 Non-Functional Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8

5 System Design 9
5.1 Architecture Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
5.2 Data Flow Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
5.2.1 Context Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
5.2.2 Level 1 Data Flow Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

6 Detailed Design 12
6.1 Use Case Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12
6.2 Activity Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
6.2.1 ADMIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
6.2.2 CUSTOMER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14
 6.3 Document Structure......................................................................................................................15

7 Implementation 16
7.1 Sample Code / Pseudo Code.........................................................................................................16
7.1.1 ADMIN............................................................................................................................16
7.1.2 CUSTOMER....................................................................................................................18
7.2 Screenshots...................................................................................................................................20

8 Testing 24

9 Conclusion 29

10 Future Work 30

Appendix A :References 31

Appendix B : User Manual 32

Appendix C: Plagarism Report 39

Appendix D: Poster 40
List of Tables
2.1 Drawbacks of Existing Systems...................................................................................................3
2.2 Tools and Technologies.................................................................................................................4

3.1 Hardware Specification(Production)............................................................................................5

3.2 Hardware Specification(Deployment)..........................................................................................5
3.3 Software Specification..................................................................................................................5

8.1 Test Case : Customer registration.................................................................................................24

8.2 Test Case : Customer Login..........................................................................................................24
8.3 Test Case : Admin login................................................................................................................25
8.4 Test Case : Policy addition............................................................................................................25
8.5 Test Case : View policy................................................................................................................26
8.6 Test Case : View transaction.........................................................................................................26
8.7 Test Case :Search policy...............................................................................................................27
8.8 Test Case :Buy policy...................................................................................................................27
8.9 Test Case :Make payment.............................................................................................................28
8.10 Test Case : Get notification...........................................................................................................28
List of Figures
5.1 Architecture Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
5.2 context diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
5.3 DFD lvl-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

6.1 Use Case diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

6.2 Activity Diagram - Admin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
6.3 Activity Diagram - Customer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14
6.4 Structure Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

7.1 Admin - Policy addition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16

7.2 Admin - view policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
7.3 Admin - view transaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
7.4 Customer - Policy search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
7.5 Customer -Transaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
7.6 Customer -Payment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
7.7 Customer -get notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
7.8 Insurance policy addition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20
7.9 view policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20
7.10 view transaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
7.11 Search policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
7.12 Transaction page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
7.13 Payment page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
7.14 confirmation mail page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

-
Chapter 1
Introduction

1.1 Project Description

1.1.1 Problem Statement
Without Health Insurance coverage ,a serious accident or health issue that result in emergency care or an
expensive treatment which may not be affordable leads to death of individual.Uninsured people live with
illness and die at a younger age than those who are insured. They stop preventive care and seek health care
in the most advanced stages of the disease. The community then incurs these costs through lower
productivity, rising rates of infectious diseases, and higher insurance premiums.

1.1.2 Proposed Solution

Health insurance application process the data starting from collecting patient record to processing
prescription of individuals insured , checking medical diagnosis, surgical details and settling the claim. The
application provides wide selection of plans that offer a range of benefits suitable to your health. admin will
login with his credentials and manage all requirement in the application and add the policy to the
application with all the required details and also he can also view policies and remove which is not required
and admin will view all the transaction done in the application.
user will register with all the required details and login with credentials to the application where he will
search the policies with the name and go through the details of the policy and click on buy and he will
provide name and details and make a payment through upi and card get insured.
HEALTH INSURANCE January - May 2022

1.1.3 Purpose
The main purpose of medical insurance application is to provide insurance for the people based on the
requirements and have a complete information of it.The main purpose of medical insurance is to get the best
medical care without any stress on your finances. Health insurance plans provide protection against high
medical costs. It covers the cost of hospitalization, day care procedures, house expenses, and ambulance
costs, among many others.

1.1.4 Scope and Limitations

Health insurance will be used by the members of health insurance company.Only the person who registers
with complete details can only have access to the application.
-

Department of Computer Applications - PES University 1

HEALTH INSURANCE January - May 2022

Chapter 2
Literature Survey

2.1 Domain Study

2.1.1 Existing Systems
Title :- A Study of Health Insurance in India
Developers:Abhishek Singh, Rana Rohit Singh
Feature :This research paper says large portion of india are not insured and it says by providing large
facilities and benifits can make people get Insured.

Title :- A Study on Health Insurance Premium, Claims, Commission

Developers: M. Vinoth Muthu, S p Mathiraj Subramanian
Feature :This research paper says that by providing affordable premium according to requirement for all
ages can make people insured.

2.1.2 Drawbacks of Existing Systems

Existing Systems Drawbacks
Care-Health Insur- Increase in premimum with age.
ance
Waiting period for existing health prob-
lems.
Not applicable in some domestic hospitals.

Star health insur- Increase in premimum with age.

ance
Not applicable in some domestic hospitals.
Niva Bupa Waiting period for existing health prob-
lems.
Not applicable in some domestic hospitals.

Table 2.1: Drawbacks of Existing Systems

Department of Computer Applications - PES University 2

HEALTH INSURANCE January - May 2022

2.2 Tools and Technologies

Purpose Tools and Technology
Frontend HTML,CSS,JSP
Backend J2EE(Java)
Database MySQL 8.0)
Server Apache tomcat 7.0.304
Table 2.2: Tools and Technologies

2.3 Feasibility Study

Technical Feasibility
Assessed that it is feasible to implement an efficient automated mechanism for to trouble shooting end to
end. Few tools also exist but not integrated to make a complete solution.health insurance is technically
possible with the latest libraries built in JS ,it provides many ways to build a complete solution,these new
libraries and frameworks provide security and standard ways to build a product.

Economic Feasibility
Efforts that are required to implement this project are assessed and found within the desired budgetary
limits. No other external constraints found. Health insurance application is cost effective and can be build
within certian cost and time frame.

Operational Feasibility
Existing system has the required operations in place to facilitate this functionality. Also, version control
system is available to ensure that there is proper tracking of the code written, health insurance has
functionality to solve problem faced during health issues process efficiently and saves lifes,the application
delivers all the functionalities required to solve the issues faced during the health issues.
-

Department of Computer Applications - PES University 3

HEALTH INSURANCE January - May 2022

Chapter 3
Hardware and Software Requirements

3.1 Hardware Specification

3.1.1 Production
Hardware Specification
Processor Intel I3 processor or higher
Hard Disk 256GB or higher
RAM 4GB or higher
Table 3.1: Hardware Specification(Production)

3.1.2 Deployment
Hardware Specification
Processor Intel Atom Processor Z2520 1.2GHz
Hard Disk 1GB or higher
RAM 512mb or higher
Table 3.2: Hardware Specification(Deployment)

3.2 Software Specification

Software Specification
IDE NetBeans IDE(7.3.1).
Frontend HTML,CSS,JSP.
Backend J2EE(Java).
Database MySQL (8.0)
Server Apache tomcat (7.0.304)
Table 3.3: Software Specification
-

Department of Computer Applications - PES University 4

HEALTH INSURANCE January - May 2022

Chapter 4
Software Requirements Specification

4.1 Users
ˆ ADMIN
The Admin who adds the policies to the application with all the required details. He
can view all the policies in the application and remove policies .
He can also view all the details of the user and transactions of the user.//[0.1cm]

ˆ USER
The user who registers to the application with all the required details and logins with the credentials
and searches the insurance with the name and buys the insurance by making payment using UPI or
card and he gets insured.

4.2 Functional Requirements

4.2.1 Admin
FR1. SIGN-IN :
In this module the admin can login to the application with credentials

FR2. Policy addition :

In this module admin will add the policies with the all the required details to the
application.

FR3. View policies :

In this module admin can view all the details of the policy in the application.

FR4. View transactions :

In this module admin can view all the details of the insured individual and details of the
transactions.

Department of Computer Applications - PES University 5

HEALTH INSURANCE January - May 2022

4.2.2 Customer
FR1. SIGN-UP :
In this module the user can register to the application.

FR2. SIGN-IN :
In this module the user can login into the application by Email and password.

FR3. SEARCH POLICY :

In this module the user searches the policies by name and gets the list of the policies and
chooses one.

FR4. PAYMENT :
User after selecting required insurance policy he can buy the policy by making payment
through by giving card or UPI details.

FR5. GET NOTIFICATION :

User after making payment he will get confirmation mail with all the payment details .

Department of Computer Applications - PES University 6

 HEALTH INSURANCE January - May 2022

4.3 Non-Functional Requirements

NFR1. USABILITY
The application is easy to use with user friendly interface and user with basic knowledge
on computer can get insured.

NFR2. PERFORMANCE
The application loads the pages quickly and it responds to user for quick and easy
interaction .

NFR3. SECURITY
Allows only Authorized access to the application.

NFR4. SCALABILITY
The application can be updated in the future without impacting the performance of the
existing system.

Department of Computer Applications - PES University 7

HEALTH INSURANCE January - May 2022

Chapter 5
System Design

5.1 Architecture Diagram

Figure 5.1: Architecture Diagram

In the above architecture diagram the presentation layer contains the user interface,business layer has 2
diffrent users called admin,customer.The service layer has services that should be provided by the system
like search policy,policy addition and so on.The data are stored inside respectieve database inside database
layer.

Department of Computer Applications - PES University 8

HEALTH INSURANCE January - May 2022

5.2 Data Flow Diagram

5.2.1 Context Diagram

Figure 5.2: context diagram

The above diagram is an overview of the entire system.It mainly consist of 2 users called ad-
min,customer.Admin can add policy to the system.user will buy the policy.

Department of Computer Applications - PES University 9

HEALTH INSURANCE January - May 2022

5.2.2 Level 1 Data Flow Diagram

Figure 5.3: DFD lvl-1

The above diagram shows the main functions of the system.Each user will be involved in diffrent func-
tionalities like customer can search policy,make payment,view policies,view transactions.
-

Department of Computer Applications - PES University 10

 HEALTH INSURANCE January - May 2022

Chapter 6
Detailed Design

6.1 Use Case Diagram

Figure 6.1: Use Case diagram

The above use case shows the diffrent users involved in diffrent functionalities so that it gives a clear idea about
which user is intended to do what functionality thereby enabling the implementation easy.

Department of Computer Applications - PES University 11

HEALTH INSURANCE January - May 2022

6.2 Activity Diagram

6.2.1 ADMIN

Figure 6.2: Activity Diagram - Admin

The above activity diagram shows the activities supported for admin.Intially,admin should login to the
system by providing credentials.After authentication homepage will be displayed, there he can select any
among the available options.

Department of Computer Applications - PES University 12

HEALTH INSURANCE January - May 2022

6.2.2 CUSTOMER

Figure 6.3: Activity Diagram - Customer

The above activity diagram shows the activities supported for customer.Intially,customer should login to the
system by providing credentials.After authentication homepage will be displayed, there he can select any
among the available options.

Department of Computer Applications - PES University 13

6.3 Document Structure

Figure 6.4: Structure Diagram

There are 4 document structures reg,upload,transaction,payment which helps to store the data.user
registration details store in reg, admin policies will be added to the upload ,user transaction details will be
added to transaction, user payment will be added to the payment.
-

14
 Chapter 7
Implementation

7.1 Sample Code / Pseudo Code

7.1.1 ADMIN
Policy addition

Figure 7.1: Admin - Policy addition

The above code which contains logic for the admin adds the policy to the applicaion it stores in the database by
giving policy name and description.

15
 view policies

Figure 7.2: Admin - view policies

The above code which contains logic for view policies which fetches data from database and displayes all
the policies added by the admin.

view transaction

Figure 7.3: Admin - view transaction

16
 The above code which contains logic for view transaction which fetches data from database and displayes all
the transaction done by the customer in the applicaion.

7.1.2 CUSTOMER
Policy search

Figure 7.4: Customer - Policy search

The above code which contains logic for search policy which fetches data from the database according to
the name given from the user in list .

Transaction

Figure 7.5: Customer -Transaction

17
The above code which contains logic for transaction which contains the details of the transaction needed
by the customer gives policy holder name , address and suitable premium for him.

Payment

Figure 7.6: Customer -Payment

The above code which contains logic for payment where it collects the payment details from user to buy
insurance where user fills the details for the payment.

Mail

Figure 7.7: Customer -get notification

18
 The above code which contains logic to send notification for the user with all details of transaction from
database through mail for the confirmation.

7.2 Screenshots
ADMIN

Figure 7.8: Insurance policy addition

The above page is where admin will add the policies to the application by giving policy name and policy
description.

Figure 7.9: view policies

The above page is where admin will view policies in the application where it contains list of all the policies
available on the application.

19
 Figure 7.10: view transaction
The above page is where admin will view transaction in the application where he will have list of all the
transaction done in the application.

CUSTOMER

Figure 7.11: Search policy

The above is the page where user will search the insurance policy by name and get list insurance or user
will press enter button to get list of all the insurance.

20
 Figure 7.12: Transaction page
The above is the page where the user starts the transaction by giving required details like policy holder
name , address and select the premium.

Figure 7.13: Payment page

The above is the page where the user makes the payment using UPI or card by giving the details and completes
the payment.

21
 Figure 7.14: confirmation mail page
The above is the page where the user get the notification mail after the successfull transaction which contains
all transaction related information.
-

22
Chapter 8
Testing

Test Case : Registering the Customer to the application.

This is the first step.Customer need to register himself to the application.

MANUAL TESTING
CUSTOMER
TEST ID 1
TEST NAME Customer Registration
TEST DESCRIPTION Validating the details given by the customer during registration.
STEP# TEST STEPS TEST DATA EXPECTED RESULT ACTUAL RESULT STATUS
TC01 Navigate to registration page Page should appear Page is appearing Pass
TC02 Click the Login and click register click register register page should appear. page opened. Pass
TC03 Fill details Name, Email, Mob and more form should be submitted . page is redirected to login page . pass

Table 8.1: Test Case : Customer registration

Test Case : Customer loging in to the application

If the customer already registered himself with the application then he can directly login to the application.

MANUAL TESTING
CUSTOMER
TEST ID 2
TEST NAME Customer Login
TEST DESCRIPTION Validating the details given by the customer during login.
STEP# TEST STEPS TEST DATA EXPECTED RESULT ACTUAL RESULT STATUS
TC01 Navigate to login page Page should appear Page is appearing Pass
TC02 Enter Credentials Email and password Should user home page. Logged in and home page opened. Pass
TC03 Enter Credentials Enter wrong Email and password Wrong Credentials page should open opened successfully pass

Table 8.2: Test Case : Customer Login

23
 Test Case : Admin login and functionality
Admin logs in with the credentials and adds the policies with required details.

MANUAL TESTING
ADMIN
TEST ID 3
TEST NAME ADMIN LOGIN
TEST DESCRIPTION Admin logins with credentials.
STEP# TEST STEPS TEST DATA EXPECTED RESULT ACTUAL RESULT STATUS
TC01 Navigate to login page Page should appear Page is appearing Pass
TC02 Enter credentials username and password admin home page should open. admin home page. pass
TC03 Enter wrong credentials username and password wrong page should open. opened successfully. Pass
Table 8.3: Test Case : Admin login

MANUAL TESTING
ADMIN
TEST ID 4
TEST NAME Policy addition
TEST DESCRIPTION Admin adds the policy with required details .
STEP# TEST STEPS TEST DATA EXPECTED RESULT ACTUAL RESULT STATUS
TC01 Navigate to policy addition page Page should appear Page is appearing Pass
TC02 Enter details Policy name and DESCRIPTION Should submit all the details . The details added successfully. pass
Table 8.4: Test Case : Policy addition

24
 MANUAL TESTING
ADMIN
TEST ID 5
TEST NAME View policy
TEST DESCRIPTION Admin views all the details of the policies .
STEP# TEST STEPS TEST DATA EXPECTED RESULT ACTUAL RESULT STATUS
TC01 Navigate to view policy page Page should appear Page is appearing Pass
TC02 Click on view policy Should display all the policies added . Displays all the policies pass
successfully.
Table 8.5: Test Case : View policy

MANUAL TESTING
ADMIN
TEST ID 6
TEST NAME View Transaction
TEST DESCRIPTION Admin views all the details of the transaction .
STEP# TEST STEPS TEST DATA EXPECTED RESULT ACTUAL RESULT STATUS
TC01 Navigate to view transaction page Page should appear Page is appearing Pass
TC02 Click on view transaction Should display all the transaction . Displays all the transactions with user details. pass
Table 8.6: Test Case : View transaction

25
 Test Case : User functionality
User searches the policy and selects the one of them and makes payment.

MANUAL TESTING
USER
TEST ID 7
TEST NAME Search policy
TEST DESCRIPTION User searches insurance with name.
STEP# TEST STEPS TEST DATA EXPECTED RESULT ACTUAL RESULT STATUS
TC01 Navigate to Search page Page should appear Page is appearing Pass
TC02 Search policy Search with names Display all the insurance according to name Displayed all the insurance according to the name search. Pass
TC03 Press enter button Display all the insurance Displayed all the insurance. Pass

Table 8.7: Test Case :Search policy

MANUAL TESTING
USER
TEST ID 8
TEST NAME Buy policy
TEST DESCRIPTION User clicks on Buy.
STEP# TEST STEPS TEST DATA EXPECTED RESULT ACTUAL RESULT STATUS
TC01 Click on buy Transaction page should appear Page is appearing Pass
TC02 User clicks on Buy It should redirect to the transaction page It successfully redirects to transaction page Pass

Table 8.8: Test Case :Buy policy

26
 MANUAL TESTING
USER
TEST ID 9
TEST NAME Make payment
TEST DESCRIPTION User makes payment.
STEP# TEST STEPS TEST DATA EXPECTED RESULT ACTUAL RESULT STATUS
TC01 Navigate to payment page payment page should appear Page is appearing Pass
TC02 User enters card or upi details UPI or card It should display transaction details Displays transaction details successfully Pass

Table 8.9: Test Case :Make payment

MANUAL TESTING
USER
TEST ID 9
TEST NAME Get notification
TEST DESCRIPTION User gets mail after payment.
STEP# TEST STEPS TEST DATA EXPECTED RESULT ACTUAL RESULT STATUS
TC01 Check mail User should receive transaction confirmation mail Mail received successfully Pass
Table 8.10: Test Case : Get notification

27
Chapter 9
Conclusion
Health insurance application which provides the insurance policies to the user according their require-
ments online. Admin who provides different kind of policies to the user .The health insurance application
makes people to get insured easier and makes treatment affordable for all type of emergencies . we have
come up with the web Application Health insurance that covers the cost of an insured individual’s med- ical
diagnosis and surgical expenses, this product is related to Health insurance domain, which involves the
making new Policy for different age groups of patients admitted to the hospital, and settlement done by the
Members of the Policy Providers etc.

28
Chapter 10
Future Work
ˆ Integrating different insurance policies like bike, car, mobile etc:In the future we can also provide
different insurance policies for bike, car , mobile and much more so that user can get insured
in all aspects in one application.
ˆ Document verifications can be made online:In the future we can make document verifications in
the application itself when the user wants to claim the policy by providing all the required
document.
ˆ Can enhance the application for the employees of the insurance policy company:we can develop
the application for the employees working in the insurance company for maintaining profiles ,for
applying leaves and for much more.

29
References
Book
[1]Herbert Schildt written book entitled ”Java - The Complete Reference”.
[2]MySQL Database Design and Tuning by Robert D Schneider .

Web References
[3]https://www.policybazaar.com/health-insurance/health-insurance-india/
[4]https://uiic.co.in/
[5]https://www.w3schools.com/
[6]https://app.diagrams.net/
[7]https://www.javatpoint.com/

30
User Manual
This sections describes how a user can register and buy insurance policy

ˆ User registeration

Step 1 - open application

Step 2 - click on login Step
3 - click on register Step 4 -
fill the details Step 5 - click
on submit

31
ˆ User login

Step 1 - click on Login

Step 2 - Enter mail and password
Step 3 - Click on login

32
ˆ Search insurance

Step 1 - search with names

Step 2 - displays the policies available with names
Step 3 - press enter to display all the policies. step 4
- click on buy

33
ˆ Transaction page

Step 1 - give policy holder name , address and select premium

Step 2 - click on submit

34
ˆ Payment page

Step 1 - select Payment mode

Step 2 - Give details of the payment required
Step 2 - click on submit

35
ˆ View Transaction

Step 1 - click on Home page

Step 2 - click on view transaction

36
ˆ View policies

Step 1 - Click on Home page Step

2 - click on view transaction

37