ITC556 Database Systems: ER Diagram Modelling Assignment Solution

This document presents a solution to a database systems modelling assignment. The solution involves creating entity-relationship (ER) diagrams for a boat manufacturing scenario. It starts with two entities, Manufacturer and Boat Type, and progressively adds more entities such as Model, Warehouse, Customer, and Bookings, illustrating the relationships between them. The ER diagrams depict the cardinality and optionality of these relationships, providing a clear representation of the database structure. The assignment covers tasks involving one-to-many and one-to-one relationships, showcasing how different entities interact within the database. Desklib offers a platform for students to access this and other solved assignments.

ITC556
Database Systems
Assessment 2
Modelling
Student Name: Karunakar Burugula Student ID: 11613503

Karunakar Burugula 11613503
Task 1
In task 1, there are two entities namely Manufacturer and Boat Type.
The attributes of the Manufacturer entity are Manufacturer_code, Company_name, Street, City, State,
Postcode, Phone_number, and Account_number (Creately Blog, 2017).
The attributes of Boat Type are Type_id, Type_name, and Type_purpose.
The manufacturer can produce one or more types of boats leading to the one to many optional type of
relationship from manufacturer to boat type. The cardinality of this relationship is 1:M. The optionality is
1:M, many being optional (Db.grussell.org, 2018).
Each boat type can be manufactured by one and only one manufacturer leading to one to one only
relationship from boat type to manufacturer. The cardinality of this relationship is 1:1. The optionality is
1:1 (mandatory).
Figure 1- Task1
1

Karunakar Burugula 11613503
Task 2
In task 2, additional entity known as Model is created. The attributes are Model_id, Model_number,
Engine, Length, Beam, Suggested_retail_price, Retail_price and Dry_weight.
Each boat type has one or more models leading to one to many relationships from boat type to model.
The cardinality in this relationship is one to many (1: M).
The optionality in this relationship is 1: M, many being optional.
Figure 2- Task 2
2

Karunakar Burugula 11613503
Task 3
In task 3, an additional entity known as Warehouse has been added. The attributes are Warehouse_id,
Warehouse_address, Warehouse_postcode, and Warehouse_phone_number.
Each warehouse can house only one type of model leading to one to one relationship from warehouse
to model. The cardinality is 1:1. The optionality is 1:1 (mandatory).
Figure 3- Task 3
3

Karunakar Burugula 11613503
Task 4
In task 4, two additional entities Customer and Bookings have been added.
The attributes of Customer are Customer_id, Customer_first_name, Customer_last_name, DOB,
Customer_address, Customer_email_address, and Customer_contact.
The attributes of Bookings are Booking_id, Date_of_booking and Date_of_visit. This entity has been
created to show the relationship between Customer and Warehouse.
There is one-to-many relationship from customer to bookings and one-to-many relationship from
warehouse to bookings. The cardinality of both the relationships is 1: M and the optionality of both is 1:
M, many being optional.
Figure 4- Task 4
4

Karunakar Burugula 11613503
References
 Creately Blog. (2017). Ultimate Guide to ER Diagrams (Entity Relationship Diagrams). Retrieved
from https://creately.com/blog/diagrams/er-diagrams-tutorial/
 Db.grussell.org. (2018). Database Analysis. Retrieved from
https://db.grussell.org/section004.html
5