Please, i want you to help me and explain this in detail for me, if possible a clue on how the ERD diagram or the table will look like, Thanks.

You have been tasked to design and build a database for the following restaurant scenario. For this scenario you will need to create an entity relationship diagram (ERD) detailing your design and implement this design using SQL Server. The database must be populated with fictional data, and you will need to provide SQL statements to display certain results. The ERD must include all: Tables (i.e. entities) . . Entity attributes (e.g. person name, address, account number) Entity types integer, float, char, etc.) Relationships (one-to-one, one-to-many, or many-to-many) Primary and foreign keys You will also be assessed on whether the ERD is in third normal form. The tables and entities in the ERD must also meet all the requirements specified in each scenario, additional marks will be reserved for adding functionality outside of the requirements. The SQL Server implementation must match the ERD; any deviations will result in a deduction of marks. You are also required to produce fictional data for each table, at most 20 records per table. You are required to build the database using SQL, no tools or automatic builds are allowed. Note that automatic SQL building software will use SQL traits that give away the fact that it has been automatically generated. Restaurant Scenario . 0 0 0 A local businesswoman has three restaurants around the city and is wishing to provide her business chain with an online presence. She already has a website designed and partially implemented but now needs a database for the general management of her restaurants. This database will need to be able to do tasks such as payroll for the staff and details of stock in each restaurant. You have been given the following requirements: Store individual details about each of the three restaurants Store details about the menu items Ingredients Description If it is vegetarian, vegan, contains nuts, gluten free, etc. Store stock requirements of each meal, e.g. a packet of burger contains 32 patties and some meals uses only 1 patty, but others use 2 or 3 Store a history of menus Special Offers Stock levels 0 How many bags of chips, chicken breasts, etc. Stock orders 0 What stock items have been ordered and how many When order was made Payment details for staff What shifts each staff has worked and the number of hours . . . . 0