Garage Database

Q1: Garage Database [40 points]We want to design a database for a local garage. For each customer, we want to record the (unique) name, the customer address, and the contact phone number. For each vehicle, we want to record the unique vehicle’s identification number (VIN), and the vehicle’s make, model and year. For each repair job we want to record the description of the job done (maximum 200 chars), the date, and the total dollar cost. A repair job may involve zero or more parts (like, e.g., “windshield wipers”, “battery”, etc.) For each part we want to record its (unique) part number, the part name and its cost. In addition, note that:• Each vehicle may have 1 or more repair jobs.• Each customer may be the primary owner of 1 or more vehicles.• Every vehicle has only one primary owner (we ignore co-owners).• No vehicle can have more than one repair job in any given day.Please answer the following questions:Q1.1. (10 points) Draw an ER diagram for this database. Make sure to indicate primary keys, cardinality constraints, weak entities (if any), and participation constraints. List any assumptions you make in the process.Q1.2. (10 points) Translate the ER diagram in Q1.1 into relational database tables (i.e. give the SQL DDL statements). Make sure that the translation captures key constraints (primary keys and foreign keys if applicable) and participation constraints in the ER diagram. Identify constraints, if any, that you are not able to capture.Q1.3. (20 points) Identify the functional dependencies that you expect should hold for the Garage Database domain. Use the dependencies to find keys and BCNF normal forms.For more information on Garage Database check on:https://no.wikipedia.org/wiki/Internet_Game_Database