A2Z Caterers (AZC) is a catering firm with twenty employees that caters to office parties with 20 to 50 people each. To keep up with the growing business owner Liz Warren wants to install a new information system for managing the ordering and buying process. AZC has a set of 15 standard menus. When potential customers call, the receptionist describes the menus to them. If the customer decides to book a party order, the receptionist records the customer information (name, address, phone number, etc.) and the information about the party (e.g., place, date, time, standard menus, their quantities and total price) on a contract. The customer is then faxed a copy of the contract. Sometimes, the customer accepts the price; other times, the customer requests some changes, which have to go back to the owner for a new cost estimate. The customer must sign and return the contract along with a deposit (often by a credit card or check) before the party order is officially booked. The remaining money is collected when the food is delivered. Each week, the owner looks through the party orders scheduled for the week and orders supplies (e.g., plates) and food (e.g., bread, chicken) needed to make them. The owner would like to use the system for marketing as well. The system should help track how customers learned about AZC and identify repeat customers so that AZC can mail special offers to them. The owner also wants to track the orders on which AZC sent a contract or actually booked the picnic order. Given the above information, please do the following: 1. Identify the main entities (min 10 entities excluding any associative entities). You should use them in steps 2 and 3. 2. Based on the business description identify all the relationships between entities and write relevant business rules that explain each relationship (As all relationships are bidirectional, make sure to articulate business rules both ways for each link in the final fully attributed data model). Make suitable assumptions for any missing details. 3. Create fully attributed data model (Entity Relationship Diagram) based on Crows foot notation in MS Visio. You should also provide correct cardinality at both ends of each relationship i.e., (0,M / 1,M / 0,1 / 1,1) using Crows foot notation. For any non-specific (M:N) relationships identified between entities, you should resolve them by adding associative entities in your data model. 4. Upload the MS Visio file (items 2 and 3 above in separate sheets) to the Moodle before the due date and time).