Insurance Management System Report

8/10/2019 Insurance Management System Report

1/11

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

fter careful analysis the system has been identified to have the following modules!

1. CEO

2. Manager

3. gen!

". Cus!omer

1. CEO module#

Page1


2/11


The C"# is the $uper user of the $ystem. The C"# is responsible for defining the

policies, policy terms and conditions, policy amounts, establishing the different

branches, registration of the branch managers. C"# will also get information about

policy details, branch details, manager details, agents details, customers details,

customers policy details

2. Manager module#

%anager is responsible for all activities at a specific branch. manager appoints

agents and interacts with customers. manager can get data about customer

policies, dues and payment details. manager can also get agent details and

commission information. manager can generate various reports.

3. gen! module#

gents 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. gents are entitled for commission for each policy they

sell. &sing the system an agent can find customer's policies details, customer's

personal details, commission collected, reports, available policy details, concerned

manager details and agent personal details.

". Cus!omer module#

"ach 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.

Page2


3/11


INTRODUCTION

Crop insurance is purchased by agricultural producers, including ar!ers, ranchers, and

others to protect the!sel"es against either the loss o their crops due to natural disasters,

such as hail, drought,and loods,or the loss o re"enue due to declines in the prices o

agricultural co!!odities# The t$o general categories o crop insurance are called crop%yieldinsurance and crop%re"enue 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..

o Multi-peril crop insurance (MC!": Coverage in this type of

insurance is not limited to #ust one ris$. %sually multi-peril crop

insurance o&ers hail' ecessive rain and drought in a combined

pac$age. )ometimes' additional ris$s such as insect or bacteria-

related diseases are also o&ered. The problem with the multi-peril

crop insurance is the possibility of a large scale event. )uch an

event can cause signi*cant losses beyond the insurer+s *nancial

capacity. To ma$e this class of insurance' the perils are often

Page,
http://en.wikipedia.org/wiki/Farmerhttp://en.wikipedia.org/wiki/Natural_disasterhttp://en.wikipedia.org/wiki/Hailhttp://en.wikipedia.org/wiki/Droughthttp://en.wikipedia.org/wiki/Floodhttp://en.wikipedia.org/wiki/Multi-peril_crop_insurancehttp://en.wikipedia.org/wiki/Farmerhttp://en.wikipedia.org/wiki/Natural_disasterhttp://en.wikipedia.org/wiki/Hailhttp://en.wikipedia.org/wiki/Droughthttp://en.wikipedia.org/wiki/Floodhttp://en.wikipedia.org/wiki/Multi-peril_crop_insurance


4/11


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

insurance (MC!" policy.

Crop-revenue insurance: Crop-yield times the crop price gives the crop-

revenues. ased 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. !t does not

cover declines that may occur from one growing season to another

Page


5/11


OVERVIEW OF THE PROJECT

SYSTEM DESCRIPTION:

The proposed system is for ma$ing easier to manage policy holder

details' agent details' policy details' claimant details and payment details. )o

this will be developed for managing the insurance management system. The

overall system is control through the main menu.

The main menu contains / parts.

1. olicy )chemes.

2. 0gent ogin.

,. Customer ogin.

. C3 or 0dministrator ogin.

4. Manager ogin

5. 0bout us.

/. Contact us.

POLICY SCHEMES:-

6arious policy schemes are:-

1. Crop-yield insurance:-2. Crop-revenue insurance:-

AGENT LOGIN

The agent login form lin$s to-

1. asic agent information li$e contact details and address which will be

shown in customer insurance information window.

2. 0ll the information related to insurances which he has made to his

clients.

,. Commission received by him for each insurance made by him

respectively.

. 3ption to create a new policy to any eisting7new client.4. 3ption to edit the contact information of its client.

Page4


6/11


5. 3ption to delete a policy of any client in case of policy lapse.

CUSTOMER LOGIN:-

The form contains the agent information li$e-1. ersonal information re8uired by insurance agency.2. 9et premium due of respective insurances by the client along

with maturity date' agent info etc.

ADMINISTRATOR LOGIN:-

0dministrator has rights to-

1. Create new agent2. dit agents information and its commission percentage.,. ;elete an agents database and all its policies respectively.. Create 7 update7 ;elete 9ew olicy4. Create 7 update7 ;elete 9ew ranch5. Create 7 update7 ;elete 9ew ranch Manager/. 0ccept 9ew policy holder and his claims re8uest.

ABOUT US:-

!t contains information about the organi


7/11


ERDIAGRAM

Page/


8/11


CONVERTING ER DIAGRAM INTO TABLES

1. Co!e"#$g %#"og e#$#& #&'e% ach entity type becomes a table ach single valued attribute becomes a column

;erived attributes are ignored

Composite attributes are represented by components

Multi-valued attributes are represented by a separate table

=ey attributes of the entity type is the rimary =ey

(. Co!e"#$g "e)a#$o%*$'% >elationships are based on cardinalities and degree of the

relation +:

+

B$a"& 1:1

1 1

,. Re)a#$o% o!e"#e

olicy 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@$ey and

PageA

3!CB 3!CB!9)%>;

B

3!CB C0!M09TC33))


9/11


pol@$ey from policy holder table and policy table

respectively 'as its composite primary $ey.

0lso 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@$ey and pol@$ey from policy

holder table and policy table respectively 'as its composite

primary $ey and agent $ey from agent table as a foreign

$ey.

NORMALISATION

O/ #a0)e o"+a)$a#$o

9ormalisation is a method for organi


10/11


!denti*cation numbers li$e ph@$ey that can be bro$en up

into parts

0 relational schema > is in *rst normal form if the domains

of all attributes of > are atomic.

0ll domains in our database are atomic since they are

indivisible.

9o ;uplication of data '!nsert 0nomaly ';elete 0nomaly

'%pdate 0nomaly found' therefore our database clears the

*rst normal form test.

(. (NF

;D!9!T!39:0 relational table is said to be in second normal form 29D if it is in19D and every non-$ey attribute is fully functionally dependentupon primary $ey.

The criteria for second normal form(29D" are:

The table must be in G9D.

very non-$ey attributes of the table must be dependent

upon the entire primary $ey.

Tables agent 'policy holder 'claimant 'insurance 'sales are

also in 29D. our database satis*es all the conditions of 29D since The

tables are in 19D and very non-$ey attributes of the table

must be dependent upon the entire primary $ey.

,. ,NF

0 relation is in ,9D if and only if'it is in 29D and there are notransitive functional dependencies.

Transitive functional dependencies arise.

Hhen one non-$ey attribute is functionally dependent on

another non-$ey attribute.

Dunctional ;ependency: non-$ey attributeInon-$ey attribute.

Hhen there is redundancy in the database.

The tables insurance 'claimant 'policy holder and sales have

been converted into ,9D.

Page1J


11/11


y de*nition transitive functional dependency can only occur ifthere is more than one non-$ey *eld'so we can say that a relationin 29D with

Documents

Insurance Management System Report