Database System ERD Design for A & H Boating - University Project

This assignment presents the design of an Entity-Relationship Diagram (ERD) for A & H Boating, a startup company involved in selling and lending boats. The project systematically develops the ERD in stages, beginning with business rules related to manufacturers and their codes, then expanding to include boat models and their attributes, and subsequently incorporating warehouses and customer information. The final ERD encompasses all business rules, including manufacturers, models, warehouses, customers, and boats, detailing the relationships between entities such as Manufacturer, Warehouse, Customer, Boat, and Model. The ERD design incorporates primary and foreign keys to ensure data integrity. The assignment concludes with a discussion on the ERD's role in database development, emphasizing its importance in managing business procedures and the application of key database concepts.

Running head: DATABASE SYSTEM
Database Systems
Name of the Student:
Name of the University:
Author Note

1
DATABASE SYSTEM
Overview
The A & H Boating is company a startup company and the main business procedures of
the company are sell and lend boats to the customer. The boats are also displayed in the
showrooms located across the city. The company wants to maintain a database so that the data of
the company can be stored in the system. This would improve the procedures of the company
which would help to track the activities of the business. The company has provided a set of
business rules and hence ERD are designed according to these business rules.
Task 1
The business rule of the company are:
 Every manufacturer is identified by a manufacturer code
 Each and every type is produced by only one manufacturer
With these business rules in mind the following ERD can be developed.
The main entity is the Manufacturer

2
DATABASE SYSTEM
The attributes within the entity are:
Manufacturer (ManufacturerId (primary key), ManufacturerName, Address, ManfacturerContact,
AccountNumber)
Task 2
For the next the task the business rules to be considered are:
Every model is produced as part of a type
After the consideration of the second set of business rules the developed ERD should look like
this:
The main entities of this ERD are Manufacturer and Model
The main attributes of the entity are:
Manufacturer (ManufacturerId (primary key), ManufacturerName, Address, ManfacturerContact,
AccountNumber)

3
DATABASE SYSTEM
Model (ModelId, ModelNumber, length, engine, Beam, suggestedPrice, RetailPrice, Weight,
WarehouseId (forgien key))
Task 3
For the third task the business rules to be considered are:
 Each warehouse stores the models of only one type
 The warehouse should be identified with a unique ID
 All the information about the warehouse are to be stored in the database
According to the provided business rule the developed ERD would look like this:
The main entities of the system are Manufacturer, Warehouse and Model.
The main entities of the system are:

4
DATABASE SYSTEM
Manufacturer (ManufacturerId (primary key), ManufacturerName, Address, ManfacturerContact,
AccountNumber)
Model (ModelId, ModelNumber, length, engine, Beam, suggestedPrice, RetailPrice, Weight,
WarehouseId (forgien key))
Warehouse (WarehouseId (primary key), WarehouseAddress, Postcode, WarehouseContact,
ManufacturerId (forgien key), ModelId (forgien key))
Task 4
For the fourth task the business rule defined for the company are:
 The customers should be able to book a visit to the warehouse
 The details of the customers are to be stored in the system of the warehouse
 With these business rules in mind the ERD is being constructed.

5
DATABASE SYSTEM
The main entities of the system are Manufacturer, Warehouse, Customer and Model
The main attributes present in this entities are:
Manufacturer (ManufacturerId (primary key), ManufacturerName, Address, ManfacturerContact,
AccountNumber)
Model (ModelId, ModelNumber, length, engine, Beam, suggestedPrice, RetailPrice, Weight,
WarehouseId (forgien key))
Warehouse (WarehouseId (primary key), WarehouseAddress, Postcode, WarehouseContact,
ManufacturerId (forgien key), ModelId (forgien key))

6
DATABASE SYSTEM
Customer (CustomerId (primary key), CustomerName, Dateof Birth, CustomerAddress, Email,
Contact, WarehouseId (forgien key))
Final ERD design
For the development of the final ERD the all the business rules of the company are to be
considered:
 Every manufacturer is identified by a manufacturer code
 Each and every type is produced by only one manufacturer
 Every model is produced as part of a type
 Each warehouse stores the models of only one type
 The warehouse should be identified with a unique ID
 All the information about the warehouse are to be stored in the database
 The customers should be able to book a visit to the warehouse
 The details of the customers are to be stored in the system of the warehouse
 With these business rules in mind the ERD is being constructed.
Hence, from the above set of business rules the final ERD can be constructed
The final ERD will look like this:

7
DATABASE SYSTEM
From the ERD the derived entities are Manufacturer, Warehouse, Customer, Boat and
Model
The attributes of the system are in the entities are:
Manufacturer (ManufacturerId (primary key), ManufacturerName, Address, ManfacturerContact,
AccountNumber)

8
DATABASE SYSTEM
Model (ModelId, ModelNumber, length, engine, Beam, suggestedPrice, RetailPrice, Weight,
WarehouseId (forgien key))
Warehouse (WarehouseId (primary key), WarehouseAddress, Postcode, WarehouseContact,
ManufacturerId (forgien key), ModelId (forgien key))
Customer (CustomerId (primary key), CustomerName, Dateof Birth, CustomerAddress, Email,
Contact, WarehouseId (forgien key))
Boat (BoatId (primary key), BoatClass, BoatType, ManufacturerId (forgien key), Purpose)
Conclusion
For conclusion it can be said that the ERD for the development of the databases have
been designed appropriately and this would assist the company in development the database.
This database would help the company to maintain the data resulting from the business
procedures. Additionally, the designing of the ERD helps in gaining concepts on ERD designing
and database development. The concepts of Primary keys and foreign keys are developed after
the completion of this assignment.

9
DATABASE SYSTEM
Bibliography
Ford, A. R. (2015). JMU Dining to Go.
Hingorani, K., Gittens, D., & Edwards, N. (2017). REINFORCING DATABASE CONCEPTS
BY USING ENTITY RELATIONSHIPS DIAGRAMS (ERD) AND NORMALIZATION
TOGETHER FOR DESIGNING ROBUST DATABASES. Issues in Information Systems, 18(1).