1. Application Prototype For the software application, create a working relational database prototype using SQL Server and a front-end software. Your prototype should demonstrate your implementation of the work you submitted in the previous phase (make sure you include any changes necessary based on any corrections made to the earlier work). Your application must include >10 records per tables to facilitate testing. You should demonstrate your command of tables, inserting data, writing queries, and creating reports or forms as applicable. For the software application, develop a set of queries (written in SQL Server Management Studio) and reports (developed using the front-end software) to demonstrate the capabilities of your database. UPDATE - Required queries and reports: For the software application, develop a set of queries (written in SQL Server Management Studio) and reports (developed using a front-end software such as Tableau, PowerBI, Access, C++, etc.) to demonstrate the capabilities of your database. Below are 10 reports Rise and Grind has requested to see in a prototype. Choose 7 queries from the list. Write the query for each and develop the reports to display the results in a format that is easy to read and use by Rise and Grind employees. 1. Provide information about each member, the courses they've enrolled in, and how much they paid for each course. Information should include member contact information, membership type information, the course name description, the standard course fee, and the discounted fee paid by the member for enrollment in the course. Enable search by member name. 2. Provide information about each fitness instructor's class schedule, including the instructor's name and id, information about the class itself, the number of members enrolled in each class, the room information, and how many spots are left in the room capacity. Make sure to include information about classes that do not yet have any members enrolled. Enable search by instructor name and the month the class started. 3. Provide a list of supply orders, including contact information for the vendor, the name of the clerk who submitted the order, the order date, the receipt date, the number of days since the order was placed, and whether or not all items were received in full (i.e., quantity ordered matches the qty received). Enable search by vendor and the date the order was placed.