Question

Complete the following ERD for this pizza order application:

The application you are hired to develop the database for must keep track of the orders for custom pizzas by customers. When customers register, they include their name and address in the registration form. A customer can order multiple different custom pizzas in a single order. Each pizza in an order has a quantity and size (Small, Medium, Large or Extra Large). Each pizza has a cheese option and crust option, which may optionally have extra cheese and/or thin crust respectively. For cheeses and crusts, we also want to indicate if the cheese is low fat and if the crust is gluten free. Furthermore, each pizza can have multiple topping options. For toppings, we’d like to indicate if the topping is organic.

Answer 1

ERD:

Explanation:
Entities: Customer:Each customer have their unique identifying customerID,Name,Address when they register.
                Order:Each Order has its own unique identifying OrderID, name of the pizza ordered, quantity of pizza ordered and size which is of 'Small','Medium','Large'. Here ENUM() is a data type where the value of size can only be 'Small','Medium','Large' indicated inside ENUM().
               Pizza: Each pizza has its own unique identifying PizzaName, Indicates whether cheese is needed or not, Indicating whether crust is needed or not. And also specifying whether cheese type is LowFat or other, also specify Crust is glutenFree or other. And also extra toppings if any.
              Toppings: Toppings has its own unique identifying ToppingsName and indicates whether the toppings are organic or not.

Relationships:Customer can make only single order so Customer-Order is 1:1 relationship
                          A single order can have multiple pizzas so Order:pizza is 1:n relationship
                          A Single pizza can have multiple toppings so pizza:toppings is 1:n relationship