The following is the ER diagram for a typical order management process database

The following is the ER diagram for a typical order management process database model. From this, create a physical EER Database Design that includes tables, table keys, fields, and relationships/cardinalities between tables.
Order Processing Rules
An order cannot be created if a customer does not make a purchase
An order cannot be created if a product is not provided by the customer
A receipt cannot be generated if there is no order produced
A customer does not have to make a purchase of product(s)
A product does not have to be purchased by a customer
Instructions
Referencing the above ER Diagram and its respective requirements, create an EER diagram using Lucidchart:
Define each Table (Entity)
Specify Entity Primary Keys
Add the table fields (Attributes) for each table
Add appropriate cardinality connector lines, and denote their maximum and minimum cardinalities (Use the Order Processing Rules to define)
Define the Table, Foreign Keys
Define the proper data type for each table attribute
Organize the EER diagram for best readability
Submission
For this Lab, submit a single pdf file exported from Lucidchart for the EER Diagram.