Assignment
ER model - QRentals database system
Assumption and Business rules
1. Customers may make enquires on booking by a phone call but actually have not made booking due to some reasons. Even though the details of customers are still kept in the system.
2. If multiple people co-hire a car, only one person is recorded as a customer.
3. If a booking is cancelled, the relevant details of booking is still kept in the system but the corresponding rental activity is not executed.
4. Not all cars are rented. For example, some luxury limos may never been rented.
5. QR assumes all cars should be parked at the locations belonging to QR's property when the cars are not being rented.
6. QR requires each employee is working at one and only one location.
7. The customers only pick up and drop off the car at the QR specified locations.
8. Each car is categorized to one and only type.
9. Each booking is processed by one employee and each booking requires to specify a category of the booked car (for example, book a minivan.)
10. The database doesn't record any damage of car during a rental activity, and doesn't record the payment in this model.
Note: 1) The attribute of car photo/image is not required to implement compulsorily in assignment 2. It could be implemented optionally.
2) There may be some other business rules that can be considered in this case study. You can list them if they make sense.