You are required to develop an ER model to represent the information requirements for given case study. Your ER model must: • show all necessary entities, attributes and relationships • show unique...

You are required to develop an ER model to represent the information requirements for given case study. Your ER model must: • show all necessary entities, attributes and relationships • show unique identifiers • show minimum and maximum cardinality. • show associative entities, if applicable Some business rules given in the case study may not be clear to you when you read the case study. You may simply make an assumption and then develop your ER model. You are required to write brief definitions for the entities and attributes in your model. For each entity and attribute in your model, write a sentence to describe the meaning of that entity or attribute. What you need to should submit You should submit a Microsoft Word document containing: • A copy of your entity-relationship model. • A list of business rules that are apparent from the case study. • A list of any assumptions that you made with justifications. 2) You must implement the entity relationship model based on Assignment 1. The recommended tool for this assignment is Microsoft Access. In implementing the ERD provided, you must complete the following tasks: • Map the ERD into a set of relations in at least Third Normal Form (3NF). You must ensure that your relations meet 3NF. Show your working. • List all the functional dependencies present in the relation • Create all the relations in a Microsoft Access database. Consider each attribute in every table and make appropriate choices regarding data types and sizes, indexes, required/not required, and validation rules. Your choices should be appropriate for each attribute and should support data integrity. • Create relationships as appropriate. Enforce referential integrity for all appropriate relationships in the database. • Populate the database with sample data. You must include sufficient sample data to test your queries and report(s). You should aim for at least 4-5 rows in every table.