Insurance Management DBMS
Insurance Management DBMS
MySQL
A PROJECT REPORT
Submitted by
NOVEMBER, 2018
CERTIFICATE
This is to certify that the project work entitled “Insurance Policy Data
Management by MySQL” that is being submitted by “CHAITANYA ANAND
SHARMA (17BCE0720), DEVAM SHETH (17BCE2162), ABHISHEK
BANSAL (17BCE0101) AND NAMAN GUPTA (17BCE0853)” for CSE2004
DATABASE MANAGEMENT SYSTEM is a record of bonafide work done under
my supervision. The contents of this Project work, in full or in parts, have neither
been taken from any other source nor have been submitted for any other CAL
course.
Place: Vellore
Date:
Signature of Students:
Signature of Faculty:
INDEX
Our proposed project aims to build and manage a database that can be very
beneficial for an insurance company. The insurance company needs to keep track
of all the details of its target companies, agents, policyholders, their premium
payments and the various products they offer. In the project, we intend to use the
concepts involved in handling the data acquired from insurance companies, agents,
and employees using MySQL and PHP. The database will include multiple tables
which will be managed efficiently. Some functions will run which would classify
the policies based on their status that whether they are active, lapsed, matured, etc.
According to those classifications, different tables are created in database and
according to functions, records are grouped in respective tables.
2. INTRODUCTION
1
insurance policy. The main objective of the developed system is to allow admin
users to register insured persons with their name, date of birth, residence address,
medical history and also policy details.
3. PROBLEM DESCRIPTION
The problem tackled in the project is to handle the policy data using database
management system. This project would focus on both front-end as well as back-
end for systematic working.
Data input would be given from the front-end by users. The front-end would be a
HTML form.
• Relation between client and his policies is a one to many relationship, but policy
type to clients is a many to many relationship.
• Data would be handled at the back-end using different tables and relations using
MySQL.
• A policy taken by a client has attributes like premium, sum assured, date of
commencement, etc.
• A client has attributes including personal details as well as details about the policy
he/she has taken.
• A policy type contains attributes describing the type of policies like premium based
on the mode, risk cover.
• There would be many other tables where records of policies taken by different
clients would be present depending on its status like active, lapsed, etc.
The developed system should allow admin users to register insured persons with
their name, date of birth, residence address, medical history and also policy details.
After registering all the insured persons, website should provide management
facilities like delete unwanted persons’ data. And also should provide awareness to
the visitors about micro insurance through articles.
2
4. SYSTEM SPECIFICATIONS
5. PROBLEM FORMULATION
In the existing Life Insurance Management System, the work is done by hand. All
the details for the insurance such as cash information or age related important
information was collected into the hard copy and by chance if any of the document
get missed up or get harmed then whole of the information will be missed, resulted
into the major loss for the user.
Also adding all the details manually will take a lot of time and also a lot more
chances of entering the information wrong. And also sending details from one place
to another will not be any task because in case while sending one important
3
document from one place to another, it get lost, then also it will proved to a great
loss both for the user as well as for the organization.
In current system any customer who wants to buy any life insurance policy has to
contact Insurance Agent or visit the company directly. It will takes lots of extra time
of customer. If customer wants to compare two policies than he has to one by one
compare the details of policy manually and then decide which policy to buy.
Customer has to maintain record of each and every policy owned by him manually
or enter the details in excel sheet. It is very tedious task for the customer to
remember on which month he has to pay policy premium and on which date his
policy ends. Life Insurance Company also has to give advertisement about new
policy plans either in News Paper or in TV channels. So it is very costly for the Life
Insurance Company. Customer has to pay policy premium by visiting branch office
or contacting insurance agent.
4
Following are disadvantages of Existing System after studying existing system
we found following problems and weaknesses in the system:
5.2 Objectives
The main objective of the developed system is to allow admin users to register
insured persons with their name, date of birth, residence address, medical history
and also policy details. It also helps the customer to view their own insurance status
information. The web pages provide easy links for easy navigation in the system. A
visitor with minimum knowledge of web browsing/surfing can access the site very
easily. The developed system should allow admin users to register insured persons
with their name, date of birth, residence address, medical history and also policy
details. Due to dynamic nature of features, the members, admin members should be
able to understand the provided facilities. After getting details of all the insured
people, system should be able to delete unwanted persons’ data. If the policy holder
wants to view the information about their own policy details, he/she can login to
policy status page by using the necessary details already given by insurance
company and view their own details and also they give feedback to the insurance
5
company. An online help documentation will be provided to help the users and
visitors in using the facilities.
In the proposed Life Insurance Management System, all the work will be digitalized
and is done via computers and internet. All the details regarding the insurance
holder and schemes will be added via computer and the information data is being
saved in servers. Backup should be there in case if by chance any of the information
will be lost.
Time consume will be reduced and users will get any easy way to access their
insurance related information and new upcoming schemes. Users just have to click
on the button and just have to wait for some moments and they get an easy access
to their information.
The proposed system is for making easier to manage policy holder details, agent
details, policy details, claimant details and payment details. The proposed system
is designed to eliminate the drawbacks of the existing system. It is designed by
keeping to eliminate the drawbacks of the present system in order to provide a
permanent solution to the problems. The primary aim of the new system is to
speedup transactions. This insurance management system will be developed for
6
managing the insurance management system. The overall system is control through
the main menu. The report is prepared for the schemes and implemented by the
concerned officials.
7
5.4 IMPLEMENTATION
(a)Home Page
The home page contains the links to data and registration pages. Clicking on any
one of the link as per the requirement of the user will direct the user to the required
data or registration page.
This page takes the details of the agents employed in the company and stores the
data in agent table of database.
This page takes the details of the customers/clients of the company and stores the
data in the customer table of database.
This page takes the details of the policies registered by the customer and stores the
data in the ‘policy_data’ table of the database
This page takes the Policy Number as input and enables the admin to make premium
payment of the customer and makes changes between ‘paid_premium’ and
‘unpaid_premium’ tables of the database.
8
(f)Agent data
This shows the data of agents employed in the company from the agent table.
This shows the data of customers/clients of the company from the customer table.
Customer number in the table is primary key.
This shows the policies registered by the clients and their policy details from the
‘policy_data’ table.
This shows the details of the Paid and Unpaid premium of all the policies of all the
customers.
This shows a very detailed information about the selected policy registered along
with the details of the client in ‘policy_data’ table.
1) connection.php – This file is common for all and included in all the other
pages used in this project. This file is to connect the database to the page in
which query is going to be run making changes in the database.
9
2) input.php – Each file used for inserting the data in the database includes this
file. It is used to insert data in the database. It includes the connection.php
file to connect to database, fetches inputs from the file where user (admin)
gives the input and runs the insert query.
3) modified.php – This file is used to display the contents of the database. For
each table, there is different modified.php file. This connects to database
and shows the data fetched from the database.
4) delete.php – This file is used to run delete query in database. The link is
provided in the modified.php with each tuple to delete that entry.
This page consists of links reaching all the other pages for registration and showing
the data stored of agents, customers, their policies and their premiums.
10
5.3.2 Agent Registration Page
This page is the form for entering the data of Agents employed in the company. The
data is inserted into agent table.
This page inserts the data of customers who have taken policies in customer table.
Customer Number is generated automatically in auto-increment.
11
5.3.4 Policy Registration Page
This form inserts the data of policies taken by customers and stores in policy_data
table. Calculation of premium is happens in backend based on the mode.
This form leads to another page showing the details of the policy and asking for
payment of premium or not.
12
Figure 5.8 Premium payment Form-2
This page shows the data stored in the table of Agent. It shows details of every
agent of company and can be deleted also.
13
5.3.7 Customer Data Storage
This page shows the data stored in the table of customer. It shows details of every
customer who took the policies and it can be deleted also.
This page shows the data stored in the table of policy_data. It shows details of all
the policies and it can be deleted also. The link of ‘Policy_data’ in a column leads
to page showing every details of that specific policy.
14
5.3.9 Detailed Policy data for each Policy
This page shows all the details of a specific policy selected in previous page.
This page shows the data stored in the table of premiums, paid_premiums and
unpaid_premiums.
15
6. APPLICATIONS
The application of our project ‘Insurance Policy Data Management’ is like any
other conventional management system i.e. we can store the details for the
employees working in the company, clients of the company and also check the
details of the policies registered. The user can also view a detailed policy data view.
Our project can be implemented in daily life since mail is commonly used.
For future of this project, we can the same thing for separating policies which are
running and which are lapsed. The login for admin and customer can be created to
protect the data.
16
8. REFERENCES
i. https://www.researchgate.net/publication/274642647_Coverage_Criteria_f
or_Testing_SQL_Queries
ii. https://www.acko.com/articles/general-info/types-of-insurance/
iii. https://www.ey.com/Publication/vwLUAssets/EY_-
_Global_insurance_industry_trends_-_policy_management/$FILE/ey-global-
insurance-industry-trends.pdf
iv. https://stackoverflow.com/questions/32379038/how-to-generate-entity-
relationship-er-diagram-of-a-database-using-microsoft-s
v. https://www.youtube.com/watch?v=rn8T1bWBXcE
vi. https://www.youtube.com/watch?v=kBy-La7DXpg
vii. http://services.lovelycoding.org/insurance-agency-management-system-
project/
viii. https://dl.acm.org/citation.cfm?id=1083734
ix. http://ilpubs.stanford.edu:8090/404/
x. https://lagunita.stanford.edu/courses/DB/SQL/SelfPaced/info
xi. https://www.c-sharpcorner.com/UploadFile/52bd60/create-an-html-form-
and-insert-data-into-database162/
xii. https://www.coursehero.com/file/22258687/Insurance-Management-
System-report/
xiii. https://www.slideshare.net/sangeethavasan/insurance-database-
management-system
17
9. APPENDIX
connection.php
<?php
$servername = "localhost";
$username = "root";
$password = "";
?>
<html>
<head>
<title>Registration Form</title>
</head>
<body>
<h2>Agent</h2>
<label>Agent Code:</label>
</div>
18
<div class = "form_group">
<label>Name:</label>
</div>
</div>
<label>Address:</label>
</div>
<label>Pincode: </label>
</div>
<label>Branch: </label>
</div>
</div>
19
<div class = "form_group">
</div>
</div>
</div>
</div>
</form>
</body>
</html>
<?php
include "../connection.php";
if(isset($_GET['id'])){
$result = mysqli_query($conn,$sql);
header('Location:modified1.php');
?>
<?php
20
include "../connection.php";
$result = mysqli_query($conn,$sql);
?>
<html>
<body>
<h1><center>Agents Data</center></h1>
<tr>
<td>Agent Code</td>
<td>Agent Name</td>
<td>DOB</td>
<td>Address</td>
<td>Pincode</td>
<td>Branch</td>
<td>Contact Number</td>
</tr>
<?php
while($row = mysqli_fetch_object($result)){
?>
21
<tr>
<td>
</td>
<td>
</td>
<td>
</td>
<td>
</td>
<td>
</td>
<td>
</td>
<td>
</td>
22
</a>
</td>
</tr>
<?php } ?>
</table>
</body>
</html>
Delete.php, input.php and modified.php is for agent, customer, policies and premiums.
Connection.php is common file for all
The given code is for agent only, but customer, premiums and policies have similar
code.
There are some other codes which are given in the link below:
https://github.com/devamsheth0806/insurancemanagement
23