Bakery Entity Relationship Model

This diagram and description are meant to explain the structure of our bakery database.

Entity-Relationship Diagram

Entity-Relationship Dictionary

ITEM Entity

This entity represents the different bakery treats that are offered on this website. This entity is involved in the following relationships:

  1. An item is requested by zero or more orders, but an individual order only requests one particular item.
Attributes:

CUSTOMER Entity

This entity represents a person using the website to make a purchase. The customer purchase relationship can be defined as a customer can place zero or more purchases, while a purchase is placed by exactly one customer. A customer can have zero purchases because it is possible to register for the site but not complete any requests.

Attributes:

PAYMENT Entity

This entity holds the details of the way in which the bill for a purchase is paid. A payment is required by one particular purchase, but a purchase can require one or more payments. This allows customers to pay for purchases in multiple installments.

Attributes:

PURCHASE Entity

This entity connects a customer, their orders, and any payments made. PickUp and Delivery are sub-entities of this super-entity.

Attributes:

ORDER Entity

This entity specifies the quantity of an item needed for a purchase.

Attributes:

WHOLESALE Entity

This is a subentity of Order. It provides the option for a discount when a large quantity of a particular item is ordered.

Attributes:

PICKUP Entity

This is a subentity of Purchase. It specifies that the customer will be coming to retrieve their purchase.

Attributes:

DELIVERY Entity

This is a subentity of Purchase. It specifies that a purchase will be brought to the customer.

Attributes: