Life Insurance management Introduction

CHAPTER 1

INTRODUCTION

The project ‘Life Insurance Management System’ deals with the maintenance of large
number of records of the different clients to be maintained by the agent. The proposed system
makes it easier to search these records and edit them. This system has a very user-friendly
interface and all the operations that can be performed in the project are self-explanatory. It
reduces the effort required to manually maintain all these records.

Life Insurance management system is a web application which is developed for tracking
the details of the insurance policy, client details, payments. This web site is an online insurance
analysis and information management system that provides easy access of information
regarding the people and resources of insurance. client can view their own personal details
when login into the Policy holder module. This project is useful for any kind of insurance
company to manage the insurance details, to sanctioned the insurance for customer, process the
insurance policy details and all kind of insurance process through online.

The main objective of the developed system is to allow client users to register insured
persons with their name, date of birth, residence address and also policy details. In this process
contains the user registration form which is used to apply for insurance policy.It also helps the
client to view their own insurance status information. After submission of registration form the
agent will process to verify that particular details registered by the customer and sanctioned the
insurance policy. 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. Then
the agent send the permanent policy holder ID and password to the client and also send status
information about insurance policy to the corresponding policy holder.
Payment module contains information related to payments. It will provide details such as
paid amount date, due amount etc.

Department of CSE, UVCE March 2022 Page |1

Life Insurance management Introduction

1.1 Database Management System (DBMS)

DBMS is a collection of programs that enables users to create and maintain a
database The DBMS is a general-purpose software system that facilitates the processes
of defining, constructing, manipulating and sharing databases among various users and
applications.
A Relational database is a database that has a collection of tables of data items, all of
which is formally described and organized according to the relational model. Data in a
single table represents a relation, from which the name of the database type comes. In
typical solutions, tables may have additionally defined relationships with each other. In
the relational model, each table schema must identify a column or group of columns,
called the primary key, to uniquely identify each row. A relationship can then be
established between each row in the table and a row in another table by creating a
foreign key, a column or group of columns in one table that points to the primary key
of another table.
1.1.1 Characteristics of Database Management Systems
• Self-describing nature.
• Keeps a tight control on data redundancy.
• Enforces user defined rules to ensure that integrity of table data.
• Provides insulation between Programs and data, Data abstraction.
• Supports multiple views of the data.
• Helps sharing of data and Multi-user transaction processing.
1.1.2 Advantages of using the DBMS approach
• Controlling the redundancy.
• Restricting unauthorized access.
• Providing persistent storage for program objects.
• Providing storage structures for efficient query processing.
• Providing backup and recovery.
• Providing multiple users interfaces.
• Enforcing Integrity Constraints.
• Representing Complex Relationships among Data.

Department of CSE, UVCE March 2022 Page |2

Life Insurance management Introduction

1.2 ENTITIES AND ATTRIBUTES

An entity may be an object with a physical existence (for e.g. A particular
person, car or employee) or it may be an object with a conceptual existence (e.g.,
company, university).
Each entity has attributes i.e., the particular properties that describe it. The attribute
values that describe each entity become a major part of the data store in the database.
Whenever an attribute of one entity type refers to another entity type, a relationship
exists. In the initial design of entity types, relationships are typically captured in the
form of attributes. As the design is refined these attributes get converted into
relationships between entity types. In the ER diagrams, the emphasis is on representing
the schemas rather than the instances. This is more useful in the database design because
a database schema changes rarely, whereas contents of the entity sets change frequently.
1.2.1 Types of Attributes
1. Simple attribute: - An attribute is classified as a simple attribute if it cannot be
partitioned into smaller components. For example, age and sex of a person. A
simple attribute is represented by an oval.
2. Composite attribute: - A composite attribute can be subdivided into smaller
components which further form attributes. For example, ‘name’ attribute of an
entity “person” can be broken down into first name and last name which further
form attributes. Grouping of these related attributes forms a composite attribute.
3. Single valued attribute: - If an attribute of a particular entity represents single
value for each instance, then it is called a single-valued attribute. For example,
Ramesh, Kamal and Suraj are the instances of entity ‘student’ and each of them
is issued a separate roll number. A single oval is used to represent this attribute.
4. Multi valued attribute: – An attribute which can hold more than one value, it
is then termed as multi-valued attribute. For example, phone number of a
person. Symbol of multi- valued attribute is shown below

Phone
number

Symbol of Multivalued attribute

5. Derived attribute: A derived attribute calculates its value from another

Department of CSE, UVCE March 2022 Page |3

Life Insurance management Introduction

attribute. For example, ‘age’ is a derived attribute if it calculates its value from
‘current date’ & ‘birth date’ attributes. A derived attribute is represented by a
dashed oval.
6. Stored attribute: In some cases, two or more attribute values are related for example,
the Age and Birth_date attributes of a person. For a particular person entity, the value
of Age can be determined from the current date and the value of the person’s
Birth_date. The Age attribute hence called derived attribute and is said to be derivable
from the Birth_date attribute, which is called a Stored attribute.
7. Complex attribute: is a Composite and Multivalued attribute.

1.3 RELATIONSHIPS
A relationship is defined as bond or attachment between 2 or more entities.
Normally,a verb in a sentence signifies a relationship. For example,
• An employee assigned a project.
• Teacher teaches a student.
• Author writes a book.
A diamond is used to symbolically represent a relationship in the ER diagram.

Relationship connecting two Entities.

Various terms related to relationships

1.3.1 Degree of relationship: - It signifies the number of entities involved in a
relationship. Degree of a relationship can be classified into following types:

• Unary relationship: - If only single entity is involved in a relationship then it is

a unary relationship. For example, an employee (manager) supervises another
employee.
• Binary relationships: - when two entities are associated to form a relation, then
it is known as a binary relationship. For example, A person works in a company.
Most of the times we use only binary relationship in an e-r diagram.
• Other types of relationships are ternary and quaternary. As the name signifies,
a ternary relationship is associated with three entities and a quaternary
relationship is associated with four entities.

Department of CSE, UVCE March 2022 Page |4

Life Insurance management Introduction

1.3.2 Connectivity of a relationship: - Connectivity of a relationship describes, how

many instances of one entity type are linked to how many instances of another entity type.
Various categories of connectivity of a relationship are:

• One to One (1:1) – “Customer gets Bill” signifies a one-to-one relationship

because only one instance of an entity is related with exactly one instance of
another entity type
. GETS
CUSTOMER BILL
1 1
One to One Relationship

• One to Many (1:M) – “Employee manage Customer” is a one-to-many

relationship because a Customer can place more than one order, but a order is
related to only one Customer.

EMPLOYEE MANAGE
CUSTOMER
1 M
One to Many Relationship

• Many to One (M:1) – “Employee has role” is a many-to-one relationship.

EMPLOYEE HAS ROLE

M 1
Many to One Relationship

• Many to Many (M: N) – “Customer buys Product” is a many-to-many

relationshipbecause an author can write many books and a book can be written
by many authors.

CUSTOMER BUYS PRODUCT

M M
Many to Many Relationship

1.3.3 Total Participation and Partial Participation

➢ Total Participation: It specifies that each entity in entity set must
compulsorily participate in at least one relationship instance in that
relationship set. It is also called as Mandatory Participation. The total
participation is represented using a double line between the entity set and the
relationship set.

Department of CSE, UVCE March 2022 Page |5

Life Insurance management Introduction

➢ Partial Participation: It specifies that each entity in entity set may or may not
participate in the relationship instance in that relationship set. It is also called
as Optional Participation. The partial participation is represented using a
single line between the entity set and the relationship set.

Total and Partial Participations

1.3.4 Types of Entities

Strong entity: A strong entity has a primary key attribute which uniquely identifieseach
entity. Symbol of strong entity is same as an entity.

Strong Entity

Weak entity: A weak entity does not have a primary key attribute and depends onother entity
via a foreign key attribute.

Weak Entity

1.4 ER DIAGRAM
An Entity–relationship model (ER model) describes the structure of a databasewith the
help of a diagram, which is known as Entity Relationship Diagram (ER Diagram). An ER
model is a design or blueprint of a database that can later be implemented as a database. The
main components of E-R model are: entity set and relationship set.
An ER diagram shows the relationship among entity sets. An entity set is a group of
similar entities and these entities can have attributes. In terms of DBMS, anentity is a table

Department of CSE, UVCE March 2022 Page |6

Life Insurance management Introduction

or attribute of a table in database, so by showing relationship amongtables and their

attributes, ER diagram shows the complete logical structure of a database. An Entity-
Relationship (ER) model is an abstract way to describe a database. It is a popular high-level
conceptual data model. Entity relationship diagrams (ER diagrams) are used to present the
diagrammatic notations associatedwith ER model.
1.4.1 Notations for ER diagram

Notations for ER diagram

Department of CSE, UVCE March 2022 Page |7

Life Insurance management Introduction

1.5 Structured Query Language (SQL)

SQL is a comprehensive database language. SQL is a standard language for
storing, manipulating and retrieving data in databases. The ANSI standard SQL
provides basic functions for data manipulation, transaction control, and record retrieval
from the database. However, most end users interact with Oracle through application
that provides an interface that hides the underlying SQL and its complexity. SQL uses
the terms table, row, and column for relation, tuple, and attribute, respectively.
1.5.1 Applications of SQL
SQL is one of the most widely used query language over the databases that:

• Allows users to access data in the relational database management systems.

• Allows users to describe the data.
• Allows users to define the data in a database and manipulate that data.
• Allows to embed within other languages using SQL modules, libraries & pre-
compilers.
• Allows users to create and drop databases and tables.
• Allows users to create view, stored procedure, functions in a database.
• Allows users to set permissions on tables, procedures and views.

1.5.2 SQL Commands

The standard SQL commands to interact with relational databases are CREATE,
SELECT, INSERT, UPDATE, DELETE and DROP. These commands can be
classified into the following groups based on their nature –

DDL - Data Definition Language

SL.No. Command & Description

1 CREATE
Creates a new table, a view of a table, or other object in the database.

ALTER
2
Modifies an existing database object, such as a table.

DROP
3
Deletes an entire table, a view of a table or other objects in the database.

Department of CSE, UVCE March 2022 Page |8

Life Insurance management Introduction

DML - Data Manipulation Language

SL.No. Command &

Description

1 SELECT
Retrieves certain records from one or more tables.

INSERT
2
Creates a record.

UPDATE
3
Modifies records.

DELETE
4
Deletes records.

DCL - Data Control Language

SL.No. Command &
Description

1 GRANT
Gives a privilege to user.

REVOKE
2
Takes back privileges granted from user.

1.5.3 SQL Data Type

SQL Data Type is an attribute that specifies the type of data of any object. Each
column, variable and expression have a related data type in SQL. You can use these
data types while creating your tables. You can choose a data type for a table column
based on your requirement.

Numeric data types:

1. INT(size) - A medium integer. Signed range is from -2147483648 to
2147483647. Unsigned range is from 0 to 4294967295.

Department of CSE, UVCE March 2022 Page |9

Life Insurance management Introduction
2. INTEGER(size) - Equal to INT(size).

3. SMALLINT(size) - A small integer. Signed range is from -32768 to 32767.

Unsigned range is from 0 to 65535.
4. FLOAT(size, d) - A floating point number. The total number of digits is
specified in size. The number of digits after the decimal point is specified in
the d parameter.
5. DOUBLE(size, d) - A normal-size floating point number. The total number of
digits is specified in size. The number of digits after the decimal point is
specified in the d parameter.
6. DECIMAL(size, d) - An exact fixed-point number. The total number of digits
is specified in size. The number of digits after the decimal point is specified in
the d parameter.
Character-String data types:
1. CHAR(size) - A FIXED length string (can contain letters, numbers, and special
characters). The size parameter specifies the column length in characters - can
be from 0 to 255. Default is 1.
2. VARCHAR(size) - A VARIABLE length string (can contain letters, numbers,
and special characters). The size parameter specifies the maximum column
length in characters - can be from 0 to 65535.
3. CHAR VARYING(n) – similar to VARCHAR(size).
Bit-String data types:
1. BIT(size) - A bit-value type. The number of bits per value is specified in size.
The size parameter can hold a value from 1 to 64. The default value for size is
1.
2. BIT VARYING(n) - similar to BIT(size) where n is the maximum number of
bits. The default for n ,the length of a character string or bit string is 1.
3. BINARY(size) - Equal to CHAR(), but stores binary byte strings.
The size parameter specifies the column length in bytes. Default is 1.

Boolean data types:

1. BOOL - Zero is considered as false, nonzero values are considered as true.

2. BOOLEAN - Equal to BOOL.

Department of CSE, UVCE March 2022 P a g e | 10

Life Insurance management Introduction

Date and Time data types:

1. DATE - A date. Format: YYYY-MM-DD. The supported range is from '1000-
01-01' to '9999-12-31'.

2. DATETIME - A date and time combination. Format: YYYY-MM-DD

hh:mm:ss. The supported range is from '1000-01-01 00:00:00' to '9999-12-31
23:59:59'.
3. TIME - A time. Format: hh:mm:ss. The supported range is from '- 838:59:59'
to '838:59:59'.
4. TIMESTAMP - TIMESTAMP values are stored as the number of seconds
since the Unix epoch ('1970-01-01 00:00:00' UTC). Format: YYYY-MM-DD
hh:mm:ss.
1.5.4 Aggregate Functions in SQL
Following aggregate functions are provided by the SQL.
1. COUNT - Returns number of tuples.
2. SUM - Returns sum of entries in a column.
3. MAX - Returns Maximum value from an entire column.
4. MIN - Returns Minimum value from an entire column.
5. AVG - Returns Average of all the entries in a column.
1.5.5 Constraints in SQL
Following constraints are provided by the SQL.
1. NOT NULL - Column should contain some value.
2. PRIMARY KEY - Should not allow duplicate and null values to a column.
3. UNIQUE - Each value of a column should be unique.
4. DEFAULT - Provides a default value for a column when none is specified.
5. FOREIGN Key - Uniquely identifies a row/record in any of the given databasetable.
6. CHECK - The CHECK constraint ensures that all the values in a column satisfies certain
conditions.
7. INDEX - Used to create and retrieve data from the database very quickly.

1.5.6 Triggers in SQL

A trigger is a special type of stored procedure that automatically runs when
an event occurs in the database server. DML triggers run when a user tries to
modify data through a data manipulation language (DML) event. DML events are
INSERT, UPDATE, or DELETE statements on a table or view.

Department of CSE, UVCE March 2022 P a g e | 11

CHAPTER 2

LITERATURE REVIEW

2.1 Analysis of the Existing System

The current system uses a manual life insurance management system, from clients, nominees,
policy and payments etc. recorded in a book. This is faced with errors, incompleteness, and
insufficient data for analysis. Information regarding clients, policy, nominees and payments
are still in black and white which is not properly organized and managed. From the clients to
clients status , receipt of payments are recorded in a book but further operations are not being
properly handled. As a result it is difficult in processing, updating and managing.

2.2 Proposed System

The proposed system (phase-1) provides easy solution for the above and some other problems
by providing a common and centralized database structure for all members. The developed
website provides the following facilities to the admin users.

1. Common Database system with common data structure

2. Registrations of insured persons
3. Insured Person search
4. Manage insured/Registered persons
5. Content Management (Articles)

This project is useful for any kind of insurance company to manage the insurance details, to
sanctioned the insurance for customer, process the insurance policy details and all kind of
insurance process through online. Payment module contains information related to payments.
It will provide details such as paid amount date, due amount etc

Department of CSE, UVCE March 2022 P a g e | 12

Life Insurance management Literature Review

2.3 Analysis of the New System

To reduce the shortcomings of the existing system there is a need to develop a

new system that could upgrade the status of the current system which is manual and
slow to the system that will be automatic and fast. The new system should be concern
with offering the requirements of the customer and the workers, the system should be
reliable, easier, fast, and more informative. The new system should possess the
qualities stated below.

2.3.1 Qualities of the new System

• Reduction in processing cost.

• Error reduction
• Automatic posting.
• Improve reporting.
• Automatic production of bills.
• Faster response time.
• Ability to meet user requirements.
• Flexibility.
• Reduced dependency.
• Improve resource use.
• Reduction on use of manpower.
• Reduction in use of paper
2.4 Software Used

2.4.1 Software Requirements

• Operating System: Platform independent. Windows used.

• Software: Xampp (for apache server)

• Database: MariaDB.

• Front-End: HTML, CSS, JavaScript.

• CSS and JavaScript to create attractive layouts and animations.

• Back-end: PHP.
Department of CSE, UVCE March 2022 P a g e | 13
Life Insurance management Literature Review

2.4.2 Overview of Tools/Software

❖ MySQL
MYSQL is an open-source relational database management
system (RDBMS). Its name is a combination of "My", the name of co-
founder Michael Widenius's daughter, and "SQL", the abbreviation for
Structured Query Language. A relational database organizes data into one or
more data tables in which data types may be related to each other; these
relations help structure the data. SQL is a language programmer use to
create, modify and extract data from the relational database, as well as
control user access to the database. In addition to relational databases and
SQL, an RDBMS like MySQL works with an operating system to implement
a relational database in a computer's storage system, manages users, allows
for network access and facilitates testing database integrity and creation of
backups

Screenshot of the default MySQL command-line banner and prompt

MySQL’s Logical Architecture:

The topmost layer contains the services that aren’t unique to MySQL. They’re
services most network-based client/server tools or servers need: connection
handling, authentication, security, and so fourth.

Department of CSE, UVCE March 2022 P a g e | 14

Life Insurance management Literature Review

MySQL’s Logical Architecture

The third layer contains the storage engines. They are responsible for storing and
retrieving all data stored “in” MySQL. Like the various file systems
available for GNU/Linux, each storage engine has its own benefits and
drawbacks. The server communicates with them through the storage engine API.
This interface hides differences between storage engines and makes them largely
transparent at the query layer. The API contains a couple of dozen low- level
functions that perform operations such as begin a transaction” or “fetch the row
that has this primary key. The storage engines don’t parse SQL or communicate
with each other; they simply respond to requests from the server.
PHP:
Hypertext Pre-processor (or simply PHP) is a general-purpose programming
language originally designed for web development. It was originally created by
Rasmus Lerdorf in 1994 the PHP reference implementation is now produced by
The PHP Group.
PHP code may be executed with a command line interface (CLI), embedded into
HTML code, or used in combination with various web template systems, web
content management systems, and web frameworks. PHP code is usually

Department of CSE, UVCE March 2022 P a g e | 15

Life Insurance management Literature Review

processed by a PHP interpreter implemented as a module in a web server or as a

Common Gateway Interface (CGI) executable.
The web server outputs the results of the interpreted and executed PHP code,
which may be any type of data, such as generated HTML code or binary image
data. PHP can be used for many programming tasks outside of the web context,
such as standalone graphical applications and robotic drone control.
The standard PHP interpreter, powered by the Zend Engine, is free software
released under the PHP License. PHP has been widely ported and can be
deployed on most web servers on almost every operating system and platform,
free of charge.
The PHP language evolved without a written formal specification or standard
until 2014, with the original implementation acting as the de facto standard which
other implementations aimed to follow. Since 2014, work has gone on to create a
formal PHP specification.
• PHP can generate dynamic page content
• PHP can create, open, read, write, delete, and close files on the server
• PHP can collect form data
• PHP can send and receive cookies
• PHP can add, delete, modify data in your database
• PHP can be used to control user-access
• PHP can encrypt data
PHP is a serverside scripting language that is embedded in HTML. It is
used to manage dynamic content, databases, session tracking, even build entire e-
commerce sites. It is integrated with a number of popular databases, including
MySQL, PostgreSQL, Oracle, Sybase, Informix, and Microsoft SQL Server.
PHP supports a large number of major protocols such as POP3, IMAP, and
LDAP. PHP4 added support for Java and distributed object architectures (COM
and CORBA), making n-tier development a possibility for the first time.
• PHP is forgiving: PHP language tries to be as forgiving as possible.
• PHP Syntax is C-Like.

Department of CSE, UVCE March 2022 P a g e | 16

 CHAPTER 3

PROPOSED WORK
3.1 ER Diagram for Life Insurance Management System

Figure 3.1:ER Diagram for Life Insurance management System

3.1.1 ER Diagram for Life Insurance Management System Explanation

The system that we have implemented has 5 entities. They are as follows:

• Agent entity: Attributes of agent are agent _id, agent_password, name, branch
• Client entity: Attributes of client are client_id, client_password, name, sex, birth_date,
address, nid, matrial_status
• Policy entity: Attributes of policy are policy_id, term, coverage, health_status, sytem,
age_limit, payement_method

Department of CSE, UVCE March 2022 P a g e | 17

Life Insurance management Proposed Work

• Payment entity: Attributes of payment are receipt_no, due, fine, month, amount
• Nominee entity: Attributes of nominee are nominee_id, name, sex, relationship,
birth_date, phone, priority
➢ All attributes are atomic attributes. With those underlined are primary key of the entities.
➢ The relationship “has” has a cardinality ratio of 1: 1 with respect to nominees and 1: N with
respect to clients.
➢ The relationship “Provides” has a cardinality ratio of 1: N with respect to policy.
➢ The relationship “Buy” has a cardinality ratio of 1: N with respect to policy.
➢ The relationship “Makes” has a cardinality ratio of 1: N with respect to payments.

3.2 RELATIONAL DATABASE SCHEMA

Figure 3.2 : Relational Database Schema for Life Insurance Management System

Department of CSE, UVCE March 2022 P a g e | 18

Life Insurance management Proposed Work

3.2.1 Relational Mapping

A relational schema for a database is an outline of how data is organized. It can be a graphic
illustration or another kind of chart used by programmers to understand how each table is laid out,
including the columns and the types of data they hold and how tables connect. A database schema
usually specifies which columns are primary keys in tables and which other columns have special
constraints such as being required to have unique values in each record. In this section we describe the
steps of an algorithm for ER to relational mapping. The above ER diagram is used to derive the
respective relational schema. The mapping will create tables with simple single valued attributes.
The steps are:
1. Mapping of Regular Entity Types.
2. Mapping of Weak Entity Types.
3. Mapping of Binary 1: 1 Relationship Types.
4. Mapping of Binary 1: N Relationship Types.
5. Mapping of Binary M : N Relationship Types.
6. Mapping of Multivalued Attributes.
7. Mapping of N-ary Relationship Types.

❖ Mapping of 1: N Relationship type: For each regular binary 1: n relationship type R, identify
the relation S that represents the participating entity type at the N-side of the relationship type.
Include as the foreign key in S the primary key of relation T that represents other entity type in
R. We have to do this because each entity instance on n side is related to at most one entity
instance on 1-side of relationship type.

❖ Mapping of M: N Relationship type: For each m:n relationship type R, create a new relation S
to represent R. Include as foreign key attributes in S the primary keys of the relations that
represent the participating entity type, their combination will form the primary key of S. Also
include any simple attributesof m: n relationship type.

• Mapping of 1:1 Relationship type: For each 1:1 relationship type R can be migrated to any
participating entity types. This relationship type ensures that each user in the database can lodge
one complaint

Department of CSE, UVCE March 2022 P a g e | 19

Life Insurance management Proposed Work

3.3 Database Tables/Relations

• AGENTS TABLE

• NOMINEES TABLE

• PAYMENTS TABLE

Department of CSE, UVCE March 2022 P a g e | 20

Life Insurance management Proposed Work

• TRANSACTIONS TABLE

• POLICY TABLE

Department of CSE, UVCE March 2022 P a g e | 21

Life Insurance management Proposed Work

3.4 NORMALIZATION OF RELATIONS

3.4.1 Functional Dependency
The Functional Dependency denoted by X →Y, between two sets of attributes
X and Y that are subsets of R species a constraint on the possible tuples that can form
a relation stare r of R. The constraints is that for any two tuples t1 and t2 in r that have
t1[X] = t2[X]. This means that the values of the Y component of a tuple in r depend
on, or determined by the values of the X components. Alternatively, the values of the
X component of a tuple uniquely determine the values of the Y component. Consider
the following schema,

Example of Functional Dependency

In the above schema the functional dependencies are:

1. SSN → ENAME The value of an employee’s social security number (SSN) uniquely
determines the employee name (ENAME).
2. PNUMBER → {PNAME, PLOCATION} These values of project’s number
uniquely determine the project name (PNAME) and project locations (PLOCATIONS).
3.4.2 Normalization
The normalization process was proposed by Codd, it takes a relation schema through a
series of tests to certify whether if satisfies a certain normal form. The process proceeds
in a top-down fashion by evaluating each relation against the criteria for normal forms
and decomposing relations as necessary can thus be considered a relational design by
analysis. Normalization of data can be looked upon as a process of analysing the given
relation schemas based on their Functional Dependencies and primary keys to achieve
the desirable properties of:
• Minimizing redundancy.
• Minimizing the insertion, deletion, and update anomalies.
Normal form of a relation refers to the highest normal form condition that meets, and
hence indicates the degree to which it has been normalized.

Department of CSE, UVCE March 2022 P a g e | 22

Life Insurance management Proposed Work

3.4.3 Definitions of keys and Attributes Participating in Keys

❖ Super Key: A super key of a relation schema R= {A1, A2… An} is asset of
attributes S C R with the property that no two tuples t1 and t2 in any legal
relation state r of R will have t1[S] = t2[S]. A key K is a super key with the
additional property that removal of any attribute from K will cause K not to be
a super key anymore.
❖ Candidate Key: If a relation schema has more than one key, each key is called
candidate key.
❖ Prime Attribute: An attribute of relation schema R is called a prime attribute
of R if it is a member of some candidate key of R.
❖ Non-Prime Attribute: An attribute is called nonprime if it is not a prime
attribute or it is not a member of any candidate.
3.4.4 Normal Forms
There are three normal forms
• First normal form
• Second normal form
• Third normal form
These were proposed by Codd as a sequence to achieve the desirable state of 3NF
relations by progressing through the intermediate states of 1Nf and 2NF if needed.
• First Normal Form (1NF): It states that the domain of attribute must include only
atomic be values and that the value of any attribute in a tuple must be a single value
from the domain of the attribute. Hence 1NF disallows having a set of values a tuple of
values or a combination of both as an attribute value for a single tuple. In other words,
1NF disallows relations within relations or relations as attribute values within tuples.

Department of CSE, UVCE March 2022 P a g e | 23

Life Insurance management Proposed Work

• Second Normal Form (2NF): This normal form is based on the full functional
dependency. A functional dependency X →Y is full functional dependency if removal
for any attribute A from X means that dependency does not hold any more.
A relation schema R is in 2NF if every nonprime attribute A in R is fully functionally
dependent on the primary key of R
If a relation schema is not in 2NF, it can be second normalized or 2NF normalized
into number of 2NF relations in which nonprime attributes are associated only with the
part of the primary key on which they are fully functionally dependent. The test for
2NF involves testing for functional dependencies whose left-hand side attributes are
part of the primary key.
1. The passenger table is in 1NF and based on the functional dependencies, there is
no partial dependencies. Hence the table is in 2NF.
2. The train table is in 1NF and based on the functional dependencies, there is no
partial dependencies. Hence the table is in 2NF.
3. The coach table is in 1NF and based on the functional dependencies, there is no
partial dependencies. Hence the table is in 2NF.
4. The route table is in 1NF and based on the functional dependencies, there is no
partial dependencies. Hence the table is in 2NF.
5. The station table is in 1NF and based on the functional dependencies, there is no
partial dependencies. Hence the table is in 2NF.
6. The distance table is in 1NF and based on the functional dependencies, there is no
partial dependencies. Hence the table is in 2NF.
7. The transaction table is in 1NF and based on the functional dependencies, there is
no partial dependencies. Hence the table is in 2NF.
8. The shows table is in 1NF and based on the functionally dependencies, there is no
partial dependencies. Hence the table is in 2NF.
9. The show_time table is in 1NF and based on the functional dependencies, there is
no partial dependencies. Hence the table is in 2NF.
Therefore all the tables are in 2NF.

Department of CSE, UVCE March 2022 P a g e | 24

Life Insurance management Proposed Work

The nominee is not in 2NF because to known the relationship and to known the
priority we need to now the client_id.

Decompositions of Nominee is:

Normalizing Nominees into 2NF

• Third Normal Form: Third normal form (3NF) is based on the concept of
transitive dependency. A functional dependency X→Y in a relation schema R is a
transitive dependency if there is a set of attributes Z that is neither a candidate key nor
a subset of any key of R and both X→Z and Z→Y hold.
A relation schema R is in 3NF if it satisfies 2NF and no nonprime attribute of R is
transitively dependent on the primary key.

Department of CSE, UVCE March 2022 P a g e | 25

Chapter 4

RESULTS

Fig 4.1: Welcome page

Fig 4.2 Sign-up page

Department of CSE, UVCE March 2022 P a g e | 26

Life Insurance Management Results

Fig 4.3 Home page

Fig 4.4: Client registration page

Department of CSE, UVCE March 2022 P a g e | 27

Life Insurance Management Results

Fig 4.5: Payment page

Fig 4.6: Policy Information page

Department of CSE, UVCE March 2022 P a g e | 28

 CHAPTER 5

CONCLUSION AND FUTURE WORK

5.1 CONCLUSION

This project is carried out to analyse the internet applications on database management
through the use of MySQL and the features of JavaScript and the way it can be used
and interfaced with MySQL as a standalone database application.

This project is useful for any kind of insurance company to manage the insurance
details, to sanctioned the insurance for customer, process the insurance policy details
and all kind of insurance process through online.

5.2 FUTURE WORK

Our project has wide scope of further improvements such as addition of online payment
gateway, add delivery option, large scale deployment, containerization. We hope to create
master and slave database structure to reduce the overload of the database queries. We also
hope to implement combo offers to encourage the customers to buy more products.

Department of CSE, UVCE March 2022 P a g e | 29

 Chapter 6

REFERENCES

➢ Ramez Elmasri and Shamkant B Navathe, Fundamentals of Database

Systems, 5th Edition, Addison Wesley, 2012.
➢ Database System Concepts, Sixth Edition, Abraham Silberschatz, Henry
F. Korth,S. Sudarshan : Tata McGraw-Hill, 2010.
➢ An Introduction to Database Systems by C.J. Date, A. Kannan, S.
Swamynathan,8th Edition, Pearson Education, 2006.
➢ Database Systems: The Complete Book, Second Edition, Hector Garcia-
Molina,Jeffrey D. Ullman, Jennifer Widom, Pearson Education, 2001.
➢ https://www.w3schools.com/html/
➢ https://www.w3schools.com/css/
➢ https://www.tutorialspoint.com/mysql/
➢ https://tutorial.djangogirls.org/en/
➢ http://getbootstrap.com/
➢ https://cs.uwaterloo.ca/~tozsu/courses/CS338/lectures/4%20Basic%20SQL.pdf
➢ www.cis.gsu.edu/dmcdonald/cis3730/SQL.pdf
➢ https://www.academia.edu/.../Ramakrishnan_Raghu.

Department of CSE, UVCE March 2022 P a g e | 30