Database System: Case Study of A&H Boating

The assignment involves designing a database system for A&H Boating, an organization that sells boats. The database should store business-related data, including manufacturer and boat information, warehouse details, and customer bookings. The assignment requires creating entity-relationship diagrams (ERDs) to model the relationships between these entities and explaining the attributes of each entity. The ERDs should also include a bridge table for customer booking visits.

Running head: DATASET SYSTEM
Dataset System: Case Study of A&H Boating
Name of the System
Name of the University

1DATASET SYSTEM
Table of Contents
Task 1:.............................................................................................................................................2
Task 2:.............................................................................................................................................2
Task 3:.............................................................................................................................................3
Task 4:.............................................................................................................................................4
Bibliography:...................................................................................................................................6

2DATASET SYSTEM
Task 1:
Figure 1: First ERD of A&H Boating System
(Source: Created by Author)
Task 2:
Figure 2: Second ERD of A&H Boating System
(Source: Created by Author)

3DATASET SYSTEM
Task 3:
Figure 3: Third ERD of A&H Boating System
(Source: Created by Author)

4DATASET SYSTEM
Task 4:
Figure 4: Fourth ERD of A&H Boating System
(Source: Created by Author)
Description of the Diagrams:
A&H Boating is a new organization that sells boats. Currently the organization is selling
its boats in Geelong city through various showrooms. The organization has various showrooms
across the city. The database is used for storing the business related data. The figure 1 represents
that the manufacturer and boat data will be saved in the database as entities name ‘Manufacturer’
and ‘Boat’ respectively. The manufacturer entity will have seven attributes. The
manufacturer_code is the primary key of the ‘manufacturer’ entity. The ‘Boat’ entity has three

5DATASET SYSTEM
attributes. The Boat_Type is the primary key of the entity. The manufacturer_name is the foreign
key refers to the manufacturer_code attribute of the manufacturer entity. The Boat_Purpose
states for which purpose the boat is designed. The relationship between the Manufacturer and
Boat is one to many. This illustrates one manufacturer can manufacture different boats but one
boat type can be manufactured by a single manufacturer. The model is considered as the part of
the boat types. The ‘Model’ is consisting of eight attributes. In the figure 2, the model_number is
the primary key of the ‘Model’ entity. The Boat_Type is the foreign key of the Boat_Type
attribute of Boat entity. The entity stores the suggested retail price of a specific model and the
real retail price of the model. The dry weight of the model is also stored in the database. The
relation between boat and model is one to many. The relationship represents that many models
can be associated with one boat type. The boat types must have a model and a model must be
part of the model.
In figure 3, the warehouse entity has been added to the ERD diagram. As per A&H
Boating policy one warehouse can store models of only one type of boat. This entity has six
attributes. The warehouse_id is the primary key of the entity. The Boat_Type is the foreign key
of the Boat_Type attribute of Boat entity. The address and postcode is for storing the address of
the warehouse. For communication purpose, the contact number will be stored within the system.
The figure 4 states that booking_visit eneity serves as the bridge table between customer and
warehouse entity.

6DATASET SYSTEM
Bibliography:
Carmel, D., Chang, M.W., Gabrilovich, E., Hsu, B.J.P. and Wang, K., 2014, December. ERD'14:
entity recognition and disambiguation challenge. In ACM SIGIR Forum (Vol. 48, No. 2, pp. 63-
77). ACM.
Habel, J., 2016. The idea of database for recording intermediate states of rotary parts for CAPP
use. Czasopismo Techniczne, 2015(Mechanika Zeszyt 2-M (7) 2015), pp.91-100.
Habel, J., 2016. The idea of database for recording intermediate states of rotary parts for CAPP
use. Czasopismo Techniczne, 2015(Mechanika Zeszyt 2-M (7) 2015), pp.91-100.
Suranauwarat, S., 2017. An Approach to Solving Technical Difficulties Facing Non-CS Students
in a Database Class. International Journal of Modern Education and Computer Science, 9(2),
p.14.