Database Design and Development Report: CQ Insurance Company

This report presents a comprehensive database design and development plan for the CQ Insurance Company. It begins with an Entity Relationship (ER) diagram illustrating the relationships between entities such as properties, customers, home contents, policy registration, policies, insurance agents, and policy claims. The report outlines key assumptions, including multiple property ownership and the categorization of items for insurance. It then details the business rules governing the insurance processes, such as unique policy IDs, separate virtual memory for item descriptions and customer details, and unique policy enrollment numbers. The logical design section provides a detailed breakdown of the entities and attributes, ensuring they are in the third normal form. Finally, the report lists the logical designs for each entity, including their attributes and primary/foreign keys, providing a structured approach to database implementation, with a bibliography of relevant sources.

Running head: DATABASE DESIGN AND DEVELOPMENT
Database Design and Development
CQ Insurance Company
Name of the Student
Name of the University
Author Note

DATABASE DESIGN AND DEVELOPMENT2
Table of Contents
ER Diagram................................................................................................................................3
Assumptions...............................................................................................................................5
Business rules.............................................................................................................................5
Logical Designs..........................................................................................................................7
Logical Design...........................................................................................................................7
Bibliography...............................................................................................................................9

Running head: DATABASE DESIGN AND DEVELOPMENT
ER Diagram
Figure 1: Entity relationship diagram of CQ Insurance Company
Source: (created by Author)

Running head: DATABASE DESIGN AND DEVELOPMENT

5DATABASE DESIGN AND DEVELOPMENT
Assumptions
The above diagram presents the entity relationship between the identified attributes
related to the CQ Insurance Company as per the case study provided. It is a considerable
factor to make some assumptions for the development of the diagram so; following
assumptions have been considered:
 Primary assumption is that the individuals might own more than one property and
those property would have more than one entity or items
 All the items would be categorized in the sector of the applicable for insurance
policies and would be eligible for the recovery in future as per the base value of the
property
 There must be some policies implemented by the CQ insurance companies in manner
to value the property and the amount that will be paid in future. The customers will
have to enroll and comply with the policies and rules followed by the insurance
company in manner to be eligible for the future recovery or claims on the property.
 Additional employees will be needed for the accomplishment of the activities related
to the communication between the insurance company and the eligible customer and
further negotiation over the claimed value.
 A mediator insurance agent, will be needed for the claims recovery and claim
registration by the customers to the CQ Insurance company
 Last but not the least, it was assumed that an agent will be handling more than one
customer for the negotiations related to the claims and recovered amount of the
valued product

6DATABASE DESIGN AND DEVELOPMENT
Business rules
The business rules have been identified from the provided case study and based on
that the ER diagram have been presented in manner to demonstrate the functioning and
activities involved in the whole process. Further, the assumed assumptions are capable of
altering the previous business rules thus; necessity has been developed to bring up with new
set of business rules in manner to accomplish the objective of the project in efficient and
effective manner. The new set of business rules as per the assumptions made in the overall
process of the CQ Insurance company:
 Based on the set of the policies organized by the CQ Insurance company and the
related data will be saved into the database under the unique policy Id. The system
will allow the user to access the implemented policies through entering those unique
policy ids and thus, there will be certain transparency in the further operational
activities relate to the insurance and claiming processes.
 Separate virtual memory will be allocated to the items description and customers
details provided in the database in manner to operate them separately. This section
will be storing the personal information of the customers that will include the
customers’ name, the items being registered for the insurance, and the claiming value
of the property considering the base value of the items.
 It is a considerable fact for the insurance company to provide unique policy
enrollment numbers for the identification of the claims and registration separately.
This section will be capturing the details related to the enrollment details of the date
on which the enrollment was made, customer identification number, and the policy
number and these data will be fed into the database for further access during the time
of claiming. It will be combination of the unique ids and thus, will be easy for the

7DATABASE DESIGN AND DEVELOPMENT
access of the required file and signoffs made by the customer and the CQ Insurance
company.
 The proposed system should also be capable of capturing the mediating agents who is
communicating with the customers and the company. Unique identification ids will be
provided to the agents and their details will be saved in the system and all the
information will be linked to the unique agent number. This will be helpful in
identifying the agents’ details through entering the unique ids of the agents. The entity
namely, agent details will be capturing the data related to the personal information of
the agents including their phone number, name, address, and contact details.
Logical Designs
The set of entities and attributes have been included in the above ER diagram those
have been already in the third normal form. The incorporated set of entities within the ER
Diagram can be listed as follows:
 Properties
 Customers
 Home contents
 Policy registration
 Policies
 Insurance Agent
 Policy Claims
Logical Design
Following is the list of logical design for the developed ER diagram:
Properties (Property_Id (primary key), Details, Location, Customer_Number (foreign
key))

8DATABASE DESIGN AND DEVELOPMENT
Customers (Customer_Id (primary key), customer_Name, customer_Address,
customer_Email)
Home contents (content_Id (primary key), Details, Market_Value, Property_Id (foreign
key) )
Policy registration (Policy_Id (primary key), Policy_Number (foreign key), Item_Id
(foreign key), Policy_date, Property_Id (foreign key), Customer_Id (foreign key)
Policies (Policy_Number (primary key), Policy_Details, registration_date,
validty_Duration)
Insurance Agent (Employee_Id (primary key), Net_Salary, Agent_Name,
Contact_Details, Agent_Mail)
Policy Claims (Claim_Id (primary key), Policy_Id (foreign key), Customer_Id (foreign
key), Aget_Id (foreign key), Claim_date

9DATABASE DESIGN AND DEVELOPMENT
Bibliography
Coronel, C., & Morris, S. (2016). Database systems: design, implementation, & management.
Cengage Learning.
Di Mascio, D., Magro-Malosso, E. R., Saccone, G., Marhefka, G. D., & Berghella, V. (2016).
Exercise during pregnancy in normal-weight women and risk of preterm birth: a
systematic review and meta-analysis of randomized controlled trials. American
Journal of Obstetrics & Gynecology, 215(5), 561-571.
Harrington, J. L. (2016). Relational database design and implementation. Morgan Kaufmann.
Jukić, N., Sharma, A., Nestorov, S., & Jukić, B. (2015). Augmenting data warehouses with
big data. Information Systems Management, 32(3), 200-209.
Martinez, A. (2017). Ceating the foundation for a startup: design and implementation of a
database system for an electrical bicycle rental company.