0% found this document useful (0 votes)
64 views4 pages

Running Head: E-R DIAGRAM 1

The document describes an E-R diagram for a car insurance company with entities for Person, Car, and Accident. The diagram shows one-to-many relationships between Person and Car, and Car and Accident. An additional CAR-ACCIDENT entity was added to establish a many-to-many relationship allowing multiple accidents to be assigned to each car through a unique Accident Report ID.

Uploaded by

ayotunde oni
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
64 views4 pages

Running Head: E-R DIAGRAM 1

The document describes an E-R diagram for a car insurance company with entities for Person, Car, and Accident. The diagram shows one-to-many relationships between Person and Car, and Car and Accident. An additional CAR-ACCIDENT entity was added to establish a many-to-many relationship allowing multiple accidents to be assigned to each car through a unique Accident Report ID.

Uploaded by

ayotunde oni
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

Running head: E-R DIAGRAM 1

Written Assignment Unit 1: E-R Diagram

University of the People

CS 3306: Databases 2
E-R DIAGRAM 2

E-R Diagram for a car-insurance company

CAR_RELATION
Car_License: Interger
Person_ID: Integer
Model: String
Year: Integer

PERSON_RELATION
Person_ID: Integer
CAR-ACCIDENT
First_Name: String
Accident_ReportID: Integer
Last_Name: String
Car_License: Interger
Address_Street: String
Address_Number: Integer

ACCIDENT_RELATION
Accident_ReportID: Integer
Accident_Location: String
Accident_Date: Date
Estimated_Cost: Float

As requirements, customer (PERSON) and car, car and accident relationship is one-to-many. It

was necessary to establish a CAR-ACCIDENT and ACCIDENT buffer relationship entity. There

is a unique Accident Report ID for each unique car (by car license), which in turn has all the

information for each accident and can be assigned to the same car for multiple accidents.
E-R DIAGRAM 3

This arrangement fulfills the requirement to provide, by separating the agency, "zero or any"

number of incidents assigned to each vehicle. There is no Car License as a Foreign Key in the

Accident Entity without an Accident Report ID.


E-R DIAGRAM 4

Reference

Silberschatz, A., Korth, H.F., & Sudarshan, S. (2001). Database System Concepts (4th ed.). New

York, NY: McGraw-Hill. Available at Database System Concepts 4th Edition By

Silberschatz-Korth-Sudarshan.pdf

You might also like