Can someone help me to make EER (Enhanced Entity Relation) and RDS (Relational Database Schema).

Thanks in Advance.

INTRODUCTION MUC is a national company specializing in used cars. Customers buy cars from or sell cars to MUC, or they take their cars to MUC for repairs. The managers of MUC have hired you to design and implement a relationa database schema according to the following requirements. REQUIREMENTS 1. Customers and Transactions For each customer, the following information is required: a unique customer number, first n name, address, two phone numbers (cell and other), and a list of possible transactions. A transacti recorded when a customer takes his/her car to MUC for repair. For each transaction, the following information needs to be stored: a unique transaction number, amount the customer was charged, of the transaction, and the car that was repaired on is 2. Employees MUC wants to keep detailed information about its employees, including those who worke the past. Each employee is con Moreover, the SIN, start date, and job description of each employee are required. If an employee is no longer with MUC, the termination date of the employee should be stored. Dependingo there are UC in be d for M sidered a customer and, therefore, is assigned a unique customer num two kinds of employees: those paid on an hourly pay-rate basis (HR-Employees) and those paid on an annual salary basis (AS-Employees). For each AS-Employee, MUC wants to keep track of his/her current and past salaries. The salary of an AS-Employee is fixed within Employee, the following information is required: a year. For each HR- the number of hours he/she has worked in each day for the current and past years the current hourly pay-rate of the employee, as w corresponding time periods (e.g., an employee's hourly pay-rates could be: S5.50 from Janua 1997 to December 1997; S6.00 from January 1998 to March 1998, etc.) ell as his/her past hourly pay-rates and the o ry 3. Cars For each car, the following data need to be stored: a unique id number, plate number, province, color make, model, year of manufacture, and type (e.g, sedan, van, etc.). Each car has a unique combination of values for plate number and province. Some of the cars are owned by MUC and are available for sal to customers. For each of those cars, the following information is required: serial number, pri ilometers, the customer from whom the car was last bought, the price it was bought for, and the date on hich it was bought., Moreover, certain repairs are required before such a car becomes available for sal The cost of these repairs needs to be recorded, as well as the date on which the cost was recorde 4. Parts, Suppliers, Orders MUC wants to keep information about parts, suppliers, and orders. Each part has a unique part id, a price, a description, and a quantity in stock. The id, name, email address, and list of telephone numbers of each supplier are required. The id of a supplier is unique. For each order, the following information i needed: a unique order id, date, supplier id, and a list of parts together with their prices and quantities 5. Monthly Expenses MUC wants to keep track of the following monthly expenses: cost of electricity, heat, water, and the rent. The rent is fixed within the same year INTRODUCTION MUC is a national company specializing in used cars. Customers buy cars from or sell cars to MUC, or they take their cars to MUC for repairs. The managers of MUC have hired you to design and implement a relationa database schema according to the following requirements. REQUIREMENTS 1. Customers and Transactions For each customer, the following information is required: a unique customer number, first n name, address, two phone numbers (cell and other), and a list of possible transactions. A transacti recorded when a customer takes his/her car to MUC for repair. For each transaction, the following information needs to be stored: a unique transaction number, amount the customer was charged, of the transaction, and the car that was repaired on is 2. Employees MUC wants to keep detailed information about its employees, including those who worke the past. Each employee is con Moreover, the SIN, start date, and job description of each employee are required. If an employee is no longer with MUC, the termination date of the employee should be stored. Dependingo there are UC in be d for M sidered a customer and, therefore, is assigned a unique customer num two kinds of employees: those paid on an hourly pay-rate basis (HR-Employees) and those paid on an annual salary basis (AS-Employees). For each AS-Employee, MUC wants to keep track of his/her current and past salaries. The salary of an AS-Employee is fixed within Employee, the following information is required: a year. For each HR- the number of hours he/she has worked in each day for the current and past years the current hourly pay-rate of the employee, as w corresponding time periods (e.g., an employee's hourly pay-rates could be: S5.50 from Janua 1997 to December 1997; S6.00 from January 1998 to March 1998, etc.) ell as his/her past hourly pay-rates and the o ry 3. Cars For each car, the following data need to be stored: a unique id number, plate number, province, color make, model, year of manufacture, and type (e.g, sedan, van, etc.). Each car has a unique combination of values for plate number and province. Some of the cars are owned by MUC and are available for sal to customers. For each of those cars, the following information is required: serial number, pri ilometers, the customer from whom the car was last bought, the price it was bought for, and the date on hich it was bought., Moreover, certain repairs are required before such a car becomes available for sal The cost of these repairs needs to be recorded, as well as the date on which the cost was recorde 4. Parts, Suppliers, Orders MUC wants to keep information about parts, suppliers, and orders. Each part has a unique part id, a price, a description, and a quantity in stock. The id, name, email address, and list of telephone numbers of each supplier are required. The id of a supplier is unique. For each order, the following information i needed: a unique order id, date, supplier id, and a list of parts together with their prices and quantities 5. Monthly Expenses MUC wants to keep track of the following monthly expenses: cost of electricity, heat, water, and the rent. The rent is fixed within the same year