ITC556 - Database Systems: Assessment 2 - Modelling

ITC556 - Database Systems
Assessment 2- Modelling
Student Name: Jagjeet Singh Tiwana
Student ID: 11661567

Table of Contents
Task 1..........................................................................................................................................................2
Task 2..........................................................................................................................................................4
Task 3..........................................................................................................................................................5
Task 4..........................................................................................................................................................6
References...................................................................................................................................................8
1

Task 1
In task 1, according to the case study, two entities were created which are Manufacturer and Boat_Type.
Manufacturer’s Attributes
1. Manu_Code
2. Manufacturer_CompanyName
3. Company_Street
4. Company_City
5. Company_State
6. Company_Postcode
7. Manufacturer_PhoneNumber
8. Manufacturer_AccountNumber.
Boat_Type’s attributes
1. BoatType_ID
2. TypeName
3. TypePurpose (Holowczak.com Tutorials, 2018)
From the entity Manufacturer to the entity Boat_Type, the relationship is One to Many, the cardinality is 1:
M in this relationship and the optionality being 1: M (many sides is optional) in this relationship (Thomas,
2005). From the entity Boat_Type to the entity Manufacturer, the relationship is One to One, the
cardinality is 1: 1 in this relationship and the optionality being 1: 1 (one is mandatory on the right side) in
this relationship.
2

Figure 1- Task1
3

Task 2
In task 2, there was an addition of an entity named Model to the existing ER diagram.
Model’s attributes
1. Model_ID
2. Boat_Model_Number
3. Model_Engine
4. Model_Length
5. Model_Beam
6. Suggested_retail_price
7. Model_retail_price
8. Model_dry_weight
From the entity Boat_Type to the Entity Model, the relationship is One to Many, the cardinality is 1: M in
this relationship and the optionality being 1: M (many sides is optional) in this relationship.
Figure 2- Task 2
4

Task 3
In task 3, according to the case study, there was an addition of an entity named Warehouse to the
existing ER diagram.
Warehouse’s attributes
1. Warehouse_ID
2. W_Address
3. W_phone_number
4. W_postcode
From the entity Warehouse to the Entity Model, the relationship is One to One, the cardinality is 1: 1 in
this relationship and the optionality being 1: 1 (one is mandatory on the right side) in this relationship.
Figure 3- Task 3
5

Task 4
In task 4, according to the case study, two entities were created which are Customers and Booking and
added to the existing diagram.
Customers’ attributes
1. Cust_Id
2. Cust_Name
3. Cust_DOB
4. Cust_Phone_Number
5. Cust_Email
6. Cust_Address
Booking’s attributes
1. Booking_ID
2. Booking_Date
3. Booking_Amount
From the entity Customer to the entity Booking, the relationship is One to Many, the cardinality is 1: M in
this relationship and the optionality being 1: M (many sides is optional) in this relationship.
From the entity Warehouse to the entity Booking, the relationship is One to Many, the cardinality is 1: M in
this relationship and the optionality being 1: M (many sides is optional) in this relationship.
6

Figure 4- Task 4
7

References
 Holowczak.com Tutorials. (2018). E-R Diagrams. Retrieved from http://holowczak.com/entity-
relationship-modeling-in-database-management-systems/3/
 Thomas. (2005). Relationship degree, cardinality and optionality [Blog comment]. Retrieved from
http://n12503.blogspot.in/2005/11/relationship-degree-cardinality-and.html
8