You will be modelling rental car booking database. You dont need to model every aspect of such an application.

Do not try to simulate a transaction, ordering process or payment process.

The database would record information about customers, locations, cars. Who rent a car from which location. It also record payment method a customer have, feedback given to rental location and some rental details. You only need to model the following, create necessary attributes (or Entities) as you see fit: Pickup locations

There are rental car locations where customers can pick up the rental cars. More specifically, a customer may pick up cars from multiple location over the years. Cars Each rental pickup location can have various kinds of cars. They may have multiple cars of the same type, e.g. multiple Honda Civics. Each car has particular attributes (brand, manufacture, model, etc.). Customers Customers who pickup rental cars from rental locations Payment methods - The Customers have payment methods (e.g. credit card which has credit card name, credit card number and credit card expiration date) Feedback - Customers can write feedback about the service of a pickup location.

You need to model what cars a pickup location rent. You need to model the pickup date, price, etc.

You need to model who picked which car from which location (This may need a relationship that is related to all three of Customers, Cars and Pickup locations.) Make sure you have at least 1 many to many relationship among the entity sets Make sure that each entity set has an appropriate set of attributes and that you also model the relationship between your entity sets. The diagram needs to be drawn in Erdplus.com and save as an image file. Upload your image file to blackboard. 1. The entity sets, attributes and relationships need to meet the requirements listed above. 2. Your diagram should include indications regarding the multiplicity of the relationships in your model. 3. An explanation of many-one and many-many relationships if any in the diagram