Database Design of CQ Insurance

Running head: Database Design of CQ Insurance
Database Design of CQ Insurance
Name of Student-
Name of University-
Author’s Note-

Running head: Database Design of CQ Insurance
1. ER Diagram
Figure 1: Database Design of CQ Insurance
2. Assumptions and Business Rules
Business Rules taken for the ERD:
Entities Relationship
agentsDetails - customerAgent One - one relationship
agentsDetails - customerDetails One - many relationship
customerDetails - propertyDetails One - many relationship
customerDetails - accidentsRecord One - many relationship
customerDetails - policyDetails One - many relationship
customerDetails - paymentDetails One - many relationship

Running head: Database Design of CQ Insurance
propertyDetails - policyDetails One - one relationship
accidentsRecord - policyDetails One - one relationship
policyDetails - paymentDetails One - one relationship
Assumptions made for the ERD:
All total there are seven entities in the ER Diagram. The assumptions that are taken
for the ERD are:
In agentsDetails entity, agentID is assumed as a primary key.
The customerAgent has a connection with agentsDetails entity, which has agentID
and customerID as foreign key. The relation between agentsDetails and the customerAgent
has a one to one relationship.
In customerDetails entity, customerID is assumed as the primary key and policyID,
agentID, and accidentID is assumed as a foreign key.
In accidentsRecord entity, the accidentID is primary key and customerID is assumed
as a foreign key.
In policyDetails entity, the policyID is a primary key and accidentID and propertyID
is foreign key.
In propertyDetails, the customerID is assumed as the foreign key, and the propertyID
is assumed as primary key.
In paymentDetails entity, the Payment_ID is primary key, and customerID and
policyID is the foreign key.