Scribd
Upload
415 views3 pages

Assignment Unit 1

The document describes building an entity-relationship (ER) diagram for a car insurance company database. It outlines the key entities (customers, cars, insurances, accidents), their attributes, and the relationships between entities. A figure shows the completed ER diagram, with customers having a one-to-many relationship with cars, cars having a one-to-one relationship with insurances, and customers and cars both having zero-to-many relationships with accidents. The conclusion states that ER diagrams are useful for communicating database structure and relationships to stakeholders.

Uploaded by

smn123456
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
415 views3 pages

Assignment Unit 1

The document describes building an entity-relationship (ER) diagram for a car insurance company database. It outlines the key entities (customers, cars, insurances, accidents), their attributes, and the relationships between entities. A figure shows the completed ER diagram, with customers having a one-to-many relationship with cars, cars having a one-to-one relationship with insurances, and customers and cars both having zero-to-many relationships with accidents. The conclusion states that ER diagrams are useful for communicating database structure and relationships to stakeholders.

Uploaded by

smn123456
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Running head: Unit 1

Written Assignment

CS 3306

Unit 1.

Period: Nov 18th, 2019

The University of the People (UoPeople), Term 2, 2019-2020


Running head: Unit 1

In this assignments I am going to build an E-R diagram for a car-insurance company whose customers
own one or more cars each and Each car has associated with it zero to any number of recorded accidents.
For the development of the ER- Data model of the database I am using following major components as
described by the Silberschatz, A., Korth, H.F., & Sudarshan, S. (2001)
• Rectangles: represent entity sets
• Ellipses: represent attributes
• Diamonds: represent relationship sets
• Lines: which link attributes to entity sets and entity sets to relationship sets

In the car insurance ER diagram I have used following entities and attributes:
Customer
• Customer ID (PK)
• Driving License
• Name
• Phone Number
• Address
• Date of Birth

Cars
• Car ID (PK)
• Model
• Owner Id (FK)
• Year
• Insurance ID (FK)

Insurances
• Insurance ID (PK)
• Monthly Cost
• Coverage amount
• Insurance Name

Accidents
• Accident ID (PK)
• Date
• Place
• Customer ID (FK)
• Car ID (FK)
Running head: Unit 1

In the ER diagram Customers have one to many relationship with Cars, Cars have one to one
relationship with Insurances. Customers have zero to many relationship with Accidents and Cars also
have zero to many relationship with Accidents.

Fig: ER diagram

Conclusion:
The ER diagram is the excellent ways of communication of the entire database structure with the
stakeholder. It is a very useful methodology to explain the structural relationship, attributes and constrains
graphically.

References
Silberschatz, A., Korth, H.F., & Sudarshan, S. (2001). “Database System Concepts (4th ed.).” New York,
NY: McGraw-Hill. Retrieved from
[Link]
%204th%20Edition%20By%[Link]

You might also like