Draw an Entity Relationship Diagram (ERD) based on the following information. Please be careful with any detail. 
Please draw in the form like this: 
You are working as a consultant for a rental car agency, and have been asked to design a database to manage rentals. You have been given the following requirements statement: "We capture information on our customers. Customers are identified by a unique customer number. For each customer, we record first name, last name, birthdate, and address. We need to know a customer's age to determine rental rates and eligibility, but we can figure that out once we know the birthdate. For the purpose of formatting mailings, we like to break the address out by street, city, state, and zip A customer may sign a rental agreement, but we will record a prospective customer in our database before they ever sign an agreement. We never record a rental agreement without an associated customer. There will be at most one customer per agreement. There could be many agreements for a single customer. A rental agreement is identified by a unique agreement id, and for each agreement, we record a start date and an end date A single agreement can cover multiple cars, and we'll never have an agreement unless it covers at least one car. We will record cars in our database before anybody has agreed to rent them. Over time, there could be many agreements per car. A car is uniquely identified by its VIN. For each car, we record the number of miles that are on it. Every rental agreement is always prepared by a single employee. The employee is uniquely identified by an EmployeeNumber, and we also record the employee's last name. An employee could prepare many rental agreements, but some employees will never prepare any agreements Every car represents exactly one model. Each model has a unique model id, and we will also capture its name and make. We can't have a car without an associated model, and we won't record a model in our database until we have at least one associated car. However, a model can have many associated cars A customer may sponsor one or more alternate drivers, but doesn't have to sponsor any other drivers. For each alternative driver, we record a full name and a driver id. The driver id counts upward for each customer-the first alternate driver for a given customer will be assigned a driver id of 1, the second will be assigned a driver id of 2, and so on. Every alternate driverl be associated with exactly one customer." mgrStartDate bonus Supervises 0..1 0..10 Manages Branch branchNo 1..1 Staff 0..1 Has staffNo 0..1 1..1 1..1 1..1 dateJoined Registers Oversees Offers Lease Client Preference Holds States leaseNo 1..1 clientNo 1..1 You are working as a consultant for a rental car agency, and have been asked to design a database to manage rentals. You have been given the following requirements statement: "We capture information on our customers. Customers are identified by a unique customer number. For each customer, we record first name, last name, birthdate, and address. We need to know a customer's age to determine rental rates and eligibility, but we can figure that out once we know the birthdate. For the purpose of formatting mailings, we like to break the address out by street, city, state, and zip A customer may sign a rental agreement, but we will record a prospective customer in our database before they ever sign an agreement. We never record a rental agreement without an associated customer. There will be at most one customer per agreement. There could be many agreements for a single customer. A rental agreement is identified by a unique agreement id, and for each agreement, we record a start date and an end date A single agreement can cover multiple cars, and we'll never have an agreement unless it covers at least one car. We will record cars in our database before anybody has agreed to rent them. Over time, there could be many agreements per car. A car is uniquely identified by its VIN. For each car, we record the number of miles that are on it. Every rental agreement is always prepared by a single employee. The employee is uniquely identified by an EmployeeNumber, and we also record the employee's last name. An employee could prepare many rental agreements, but some employees will never prepare any agreements Every car represents exactly one model. Each model has a unique model id, and we will also capture its name and make. We can't have a car without an associated model, and we won't record a model in our database until we have at least one associated car. However, a model can have many associated cars A customer may sponsor one or more alternate drivers, but doesn't have to sponsor any other drivers. For each alternative driver, we record a full name and a driver id. The driver id counts upward for each customer-the first alternate driver for a given customer will be assigned a driver id of 1, the second will be assigned a driver id of 2, and so on. Every alternate driverl be associated with exactly one customer." mgrStartDate bonus Supervises 0..1 0..10 Manages Branch branchNo 1..1 Staff 0..1 Has staffNo 0..1 1..1 1..1 1..1 dateJoined Registers Oversees Offers Lease Client Preference Holds States leaseNo 1..1 clientNo 1..1
