Database ERD Project: Drive2Impress Business Rules and ERD

This project focuses on creating an Entity Relationship Diagram (ERD) for the Drive2Impress business. It begins by outlining business rules related to suppliers, car types, and their relationships, including supplier codes, company information, and car type specifications. The project then extends to include car models, detailing model names, engine capacity, and pricing, adding these entities and their relationships to the ERD. Further, the project incorporates showroom information, including showroom IDs and addresses, and their relationship with car types. Finally, the project integrates customer data, such as customer codes, names, and arrival information, and their relationships with showrooms. The ERD is constructed to visually represent these entities, their attributes, and the cardinality and optionality of their relationships, providing a comprehensive database design based on the provided business rules.

RUNNING HEAD: DATABASE 1
DATABASE
Student’s Name:
Course title:
Date of submission:

RUNNING HEAD: DATABASE 2
Drive2Impress business rules and instructions for creating your ERD:
1. Each supplier supplies one or more different types of cars. Each car type is supplied by only one
supplier. Every supplier is identified by a supplier code. The company name, street, city, state,
postcode, phone number, and account number are also kept in the system for every supplier. For car
type, the type name (i.e. Sedan, SUV, ute, etc.) and market segment (i.e. small family, large family,
etc.) are kept in the system.
 Create an ERD that represents the entities, attributes, the relationships between entities, and
the cardinality and optionality of each relationship that are described by this business rule.
2. Each car type has one or more models. Each model is supplied as part of a car type. For each
model, the model name, engine capacity, seating capacity, year manufactured, and Drive2Impress
retail price must be kept in the system.
 Add the entities, attributes, the relationships between entities, and the cardinality and
optionality of each relationship that are described by this business rule to the same ERD that
you created for business rule 1.
3. Each car type is kept in more than one showroom. Each showroom keeps one or more car types.
Each showroom is identified by a showroom ID. For each showroom address, postcode, phone
number are kept in the system.

RUNNING HEAD: DATABASE 3
 Add the entities, attributes, the relationships between entities, and the cardinality and
optionality of each relationship that are described by this business rule to the same ERD that
you created for business rule 1 and business rule 2.
4. Each customer can visit one or more showrooms. Each showroom can be visited by more than one
customer. Each customer is identified by a customer code. For each customer the name, mobile
phone, address and the expected date and time of arrival are kept in the system.
 Add the entities, attributes, the relationships between entities, and the cardinality and
optionality of each relationship that are described by this business rule to the same ERD that
you created for business rule 1, business rule 2 and business rule 3.

RUNNING HEAD: DATABASE 4
REFERENCES
Yeslam A. (2017). How to draw an ERD from business rules. Retrieved 4th October 2017
from https://www.youtube.com/watch?v=YvJ4t9_2SWk