INSURANCE MANAGEMENT SYSTEM

ABSTRACT

Crop insurance is purchased by agricultural producers, including farmers, ranchers,

and others to protect themselves against either the loss of their crops due to natural
disasters, such as hail, drought, and floods, or the loss of revenue due to declines
in the prices of agricultural commodities. The two general categories of crop
insurance

are

called

crop-yield

insurance

and

crop-revenue

insurance.

In existing system manual procedure is followed where records are used to

maintain data which is a time taking process and require more man power and
calculating commissions dues..etc are done manually.
In present system there is no need of human interference in calculating any details.
Total work is done using management system which will save time and less paper
work and even human resource.

MODULE DESCRIPTION
Number of Modules
After careful analysis the system has been identified to have the following modules:
1.

CEO

2.

Manager

3.

Agent

4.

Customer
1. CEO module:
Page
1

INSURANCE MANAGEMENT SYSTEM

The CEO is the Super user of the System. The CEO is responsible for defining the
policies, policy terms and conditions, policy amounts, establishing the different
branches, registration of the branch managers. CEO will also get information about
policy details, branch details, manager details, agents details, customers details,
customers policy details
2. Manager module:
Manager is responsible for all activities at a specific branch. A manager appoints
agents and interacts with customers. A manager can get data about customer
policies, dues and payment details. A manager can also get agent details and
commission information. A manager can generate various reports.
3. Agent module:
Agents are employees of the insurance company who interact with potential
customers and offer the necessary details, agents typically act as a liaison between
customers and company. Agents are entitled for commission for each policy they
sell. Using the system an agent can find customers policies details, customers
personal details, commission collected, reports, available policy details, concerned
manager details and agent personal details.
4. Customer module:
Each customer must register with the system before one can avail the services.
Customers can seek information regarding policies, register new policies, make
online payments etc.

Page
2

INSURANCE MANAGEMENT SYSTEM

INTRODUCTION
Crop insurance is purchased by agricultural producers, including farmers, ranchers, and
others to protect themselves against either the loss of their crops due to natural disasters,
such as hail, drought, and floods, or the loss of revenue due to declines in the prices of
agricultural commodities. The two general categories of crop insurance are called crop-yield
insurance and crop-revenue insurance.

Crop-yield insurance: There are two main classes of crop-yield insurance:

o

Crop-hail insurance is generally available from private insurers

because hail is a narrow peril that occurs in a limited place and its
accumulated losses tend not to overwhelm the capital reserves of
private insurers..

Multi-peril crop insurance (MPCI): Coverage in this type of

insurance is not limited to just one risk. Usually multi-peril crop
insurance offers hail, excessive rain and drought in a combined
package. Sometimes, additional risks such as insect or bacteriarelated diseases are also offered. The problem with the multi-peril
crop insurance is the possibility of a large scale event. Such an
event can cause significant losses beyond the insurer's financial
capacity. To make this class of insurance, the perils are often

Page
3

INSURANCE MANAGEMENT SYSTEM

bundled together in a single policy, called a multi-peril crop

insurance (MPCI) policy.

Crop-revenue insurance: Crop-yield times the crop price gives the croprevenues. Based on farmer's revenues, crop-revenue insurance is based
on deviation from the mean revenue Crop-revenue insurance covers the
decline in price that occurs during the crop's growing season. It does not
cover declines that may occur from one growing season to another

Page
4

INSURANCE MANAGEMENT SYSTEM

OVERVIEW OF THE PROJECT

SYSTEM DESCRIPTION:
The proposed system is for making easier to manage policy holder
details, agent details, policy details, claimant details and payment details. So
this will be developed for managing the insurance management system. The
overall system is control through the main menu.
The main menu contains 7 parts.
1. Policy Schemes.
2. Agent Login.
3. Customer Login.
4. CEO or Administrator Login.
5. Manager Login
6. About us.
7. Contact us.

POLICY SCHEMES:Various policy schemes are:1. Crop-yield insurance:2. Crop-revenue insurance:AGENT LOGIN
The agent login form links to1. Basic agent information like contact details and address which will be
shown in customer insurance information window.
2. All the information related to insurances which he has made to his
clients.
3. Commission

received

by

him

for

each

insurance

respectively.
4. Option to create a new policy to any existing/new client.
5. Option to edit the contact information of its client.
Page
5

made

by

him

INSURANCE MANAGEMENT SYSTEM

6. Option to delete a policy of any client in case of policy lapse.

CUSTOMER LOGIN:The form contains the agent information like1. Personal information required by insurance agency.
2. Next premium due of respective insurances by the client along
with maturity date, agent info etc.

ADMINISTRATOR LOGIN:Administrator has rights to1.

2.
3.
4.
5.
6.
7.

Create new agent

Edit agents information and its commission percentage.
Delete an agents database and all its policies respectively.
Create / update/ Delete New Policy
Create / update/ Delete New Branch
Create / update/ Delete New Branch Manager
Accept New policy holder and his claims request.

ABOUT US:It contains information about the organizations history and its achievements.
CONTACT US:It contains the contact details of the organizations various branches located in
different parts of a country.

REPORTS:

Sales report
Claimant information report

Agent information report

Client information report

Page
6

INSURANCE MANAGEMENT SYSTEM

ER DIAGRAM

Page
7

INSURANCE MANAGEMENT SYSTEM

CONVERTING ER DIAGRAM INTO TABLES

1. Converting strong entity types
Each entity type becomes a table
Each single valued attribute becomes a column
Derived attributes are ignored
Composite attributes are represented by components
Multi-valued attributes are represented by a separate table
Key attributes of the entity type is the Primary Key

2. Converting relationships
Relationships are based on cardinalities and degree of the
relation
m:n

POLICY
HOLDER

POLICY

CHOOS
ES

CLAIMANT

Binary 1:1

POLICY
HOLDER

INSURE
D
BY

3. Relations converted

Policy holder and policy have m:n cardinality which results

in conversion of the relation insured by into a table
named as insurance. The insurance table has ph_key and
Page
8

INSURANCE MANAGEMENT SYSTEM

pol_key

from

policy

holder

table

and

policy

table

respectively ,as its composite primary key.

Also policy and agent table have m:n cardinality resulting

in conversion of relation sales, into a table named as
sales. The table sales has ph_key and pol_key from policy
holder table and policy table respectively ,as its composite
primary key and agent key from agent table as a foreign
key.

NORMALISATION
Own table normalization

Normalisation is a method for organizing data elements in a database

into tables.
It keeps track to keep the database less vulnerable to some types of
logical inconsistencies and anomalies.Tablescan be normalized to varying
degrees like first,second,BCNF.Greater the degree of normalization more
is the protected from inconsistencies and anomalies.
The tables may be normalized under the following guideline:
1. 1NF
DEFINITION:
A relation schema is in 1NF if all of its attributes are:

Single valued
Restricted to assuming atomic values
Functionally dependent on the primary key

Domain is atomic if its elements are considered to be indivisible

units .
Examples of non-atomic domains
Set of names, composite attributes
Page
9

INSURANCE MANAGEMENT SYSTEM

Identification numbers like ph_key that can be broken up

into parts
A relational schema R is in first normal form if the domains

of all attributes of R are atomic.

All domains in our database are atomic since they are

indivisible.
No Duplication of data ,Insert Anomaly ,Delete Anomaly
,Update Anomaly found, therefore our database clears the
first normal form test.

2. 2NF
DEFINITION:
A relational table is said to be in second normal form 2NF if it is in
1NF and every non-key attribute is fully functionally dependent
upon primary key.
The criteria for second normal form(2NF) are:
The table must be in !NF.
Every non-key attributes of the table must be dependent
upon the entire primary key.
Tables agent ,policy holder ,claimant ,insurance ,sales are
also in 2NF.
our database satisfies all the conditions of 2NF since The
tables are in 1NF and Every non-key attributes of the table
must be dependent upon the entire primary key.

3. 3NF
A relation is in 3NF if and only if,it is in 2NF and there are no
transitive functional dependencies.
Transitive functional dependencies arise.
When one non-key attribute is functionally dependent on
another non-key attribute.
Functional Dependency: non-key attribute>non-key attribute.
When there is redundancy in the database.
The tables insurance ,claimant ,policy holder and sales have
been converted into 3NF.

Page
10

INSURANCE MANAGEMENT SYSTEM

By definition transitive functional dependency can only occur if

there is more than one non-key field,so we can say that a relation
in 2NF with zero or one non-key field must automatically be in 3NF.

Page
11