Question 1: You have been hired by an automotive manufacturer to design a database application for keeping track of their vehicle assembly and distribution. After consulting with their representatives, you have come up with the following requirements which need to be captured in the database design. Each vehicle is composed of hundreds of parts and assemblies, each of which we will need some information about. It also has some characteristics which are common to every vehicle of the same model, and some that are specific to the particular vehicle being built. For each vehicle model, we need to record the year, manufacturer, model, gross weight, number of axles and warranty information. We will also need to be able to list of all the parts (by part number) that make up that model when assembled. ⚫For each individual vehicle, it will be issued a VIN (vehicle identification number), and we also need to keep track of the paint colour, options installed and the assembly date. We will consider an assembly to be a group of parts that are preassembled together before being installed onto the vehicle (eg: engine). For each assembly we will need to record an identification number, the plant that it was assembled in, the day it was assembled, and a list of parts that were installed into that assembly. For each part, either directly installed on the vehicle or as part of an assembly that is then installed, we want to keep track of the part number, lot number (set by the manufacturer) and a supplier name (if applicable). ⚫ Of course, the end goal is to sell these vehicles, and once we do we want to keep track of the customers registration data in case we need to contact them regarding recalls and defects. For each customer we would like to record their name, address, phone number and date of purchase. Customers may also have more than one car registered from our company and we only want to keep their personal information recorded once regardless of how many vehicles they register. NOTE: Be sure to consider any participation and key constraints that may not be explicitly mentioned. If you find a situation where there could be a choice of different constraints that could be applied, you must include an explanation of why you choose the implementation which you did, along with your diagrams or relations. If you need further clarification regarding these requirements you are to consult with the instructor, who will act as the representative for the client. Revised: May 15, 2019 Draw the ER diagram to represent the data model for this project. Include in the data model all entities, relationships, attributes and all possible constraints. In any case where a constraint can not be identified with the ER model please include a description of it in a write-up.