Database Design with Entity-Relationship Model E-R Diagram

Show all entity sets, relationship sets, and attributes (including primary keys for entity sets) in the diagram. Then translate these diagrams into relational database schema.

Hot Restaurant Automation: Design a database containing the following information for the HOT RESTAURANT, whose all meals are hot:

1. Every waiter had a name, telephone, and a salary. ( Also, waiters have to like hot spicy.)
2. Tables have numbers and capacities, namely the number of chairs (There are hot peppers on the tables)
3. There is no table unattended by waiters. A waiter can look at more than one table. The restaurant has at least one table and at least one waiter. There is no waiter who does not look at the table.
4. Meals have name, type ('main course', 'dessert', ...), serving price, and serving calories.
5. Food orders have date, time, table, waiter and ordered dishes. (Example: 2 portions of dried beans, 2 portions of rice, 1 bowl of yogurt, 1 bottle of water, etc.). The meal order includes at least one meal. A meal can be filled in many orders. Each order is charged 10 $ for bread even though it is not eaten, and 5 $ for water if it is not drunk. It is forbidden to sit at the table without ordering a meal. Hot pepper is rubbed into the mouths of those who do not order.
6. An invoice is created for each order. Invoices have numbers and dates.