Project Description

All previous projects were centered on the calculations of rental and insurance charges. In project 2, there was just one generic car so one set of functions was sufficient. Project 3 expanded the car rental system to have multiple types of cars, but each car type used the same calculations for rental and insurance charges, so again, one set of functions was enough. In this project, we again expand the functionality of the car rental system by adding the concept of car maintenance - washing, waxing, changing the oil, rotating the cars, etc. As you'll see, all cars have some common type of maintenance, but different types of cars also have different types of maintenance. So unlike projects 2 and 3, you will not able to use the same functions for different car types. Given the need for different functions for different cars and the possibility or more car types in the future, the best design and implementation for this project must use inheritance and polymorphism.

To implement this project, you will create a hierarchy of cars as shown in the figure below. Each car subclass will override the necessary function(s) to perform the required car maintenance. Car maintenance in this project will be "performed" by simply printing an appropriate message indicating what kind of maintenance was performed.

The car rental system

1. Add a new car to the rental system -- self explanatory.
   All cars added to the rental system come directly from the car dealer with no mileage recorded on the odometer
2. Add a new customer to the rental system - self explanatory
3. Rent a car to a customer -- associate the car and the customer.
4. Return a car.
   When a renter returns a car, the number of days and mileage driven are specified. The total rental cost is calculated and added to the customer's balance due to the company. A "receipt" is printed for the renter which contains all car rental information, all renter information and the breakdown of the rental cost. Required car maintenance is performed on the car.
5. Print a list of all cars.
   All available information about each car is printed. If a car is currently rented, all customer information for the renter is also printed.
6. Print a list of customers
   All information about each customer (including balance due and the license tag numbers of cars currently rented) is printed.
7. Remove a customer -- self explanatory
   It is an error to attempt to remove a customer who is currently renting a car.
8. Remove a car -- self explanatory
   It is an error to attempt to remove a car that is currently rented.

1. You must be 18 years old to rent a car.
2. PLATINUM car holders may rent multiple cars simultaneously. GOLD card members may rent just one car at a time.

Cars

Program Output

1. Customer membership card numbers must be displayed in the form 12-3456.
2. All monetary values must be displayed with 2 decimal places.
3. When displaying a list of cars or customers, data must be aligned in columns.
4. Renter names must be displayed last name first.

1. The renter's first and last name total no more than 20 characters.
2. The car's model is no more than 20 characters.
3. The car's license tag number is no more than 8 characters.
4. Days rented and miles driven are less than 10000.
5. The total rental charge is less than $100000.
6. A customer will not rent more than 2 cars at a time.

The Command File

Sample Output

For 10 points of extra credit, add the following functionality to your program.

1. Design and implement a class to model car maintenance data. Use good OO principles and remember that less can be more. It's not necessary (and usually undesirable) to provide a mutator and an accessor for every data member of your class.
2. Make whatever changes are necessary to existing classes to model the maintenance log.
3. Implement the modified PRINT command as shown above that directs your program to print the maintenance log for a specified car. The output from this new command should include all data that is printed in a the maintenance message, in a reasonable tabular format.

Free Advice and Information

1. Carefully consider your class design. In general, a minimal class interface is best. Consider how best to reuse code. Plan for the future reuse of code you write in this project.
2. Consider using the overloaded operator<< to output your classes. Even if not necessary in your code, you may find it helpful when debugging.
3. Functions called from main( ) that are not part of any class are permitted. If you create new functions, their prototypes must be found in Proj4Aux.h and they must be implemented in Proj4Aux.cpp.
4. Your program must provide adequate error checking as described above.
5. Think carefully about the proper use of const for parameters and member functions. Doing const correctly from the beginning can save lots of effort and frustration later.
6. Review the class notes on the different methods of passing parameters. Each is best for a different situation.
7. Be sure your function header comments list the pre- and post-conditions and handle each pre-condition that is not met.
8. Your program will be tested with a variety of conditions.
9. Use incremental development.
10. Expect to use/modify code from this project in project 5. Design and code accordingly.

Project Design Assignment

Project Makefile

You must provide the makefile for this project. Use the makefile you submitted for project 3 and modify it appropriately. If you don't change the names of the files from project 3, the changes will be minimal.

The graders will be typing the command make Proj4 when they grade your project. This command must cause all .cpp files to be compiled and the executable named Proj4 to be created.

The make utility can also be used for compiling a single program without linking. For example, to compile Box.cpp, type make Box.o.

In addition to compiling and linking your files, make can be used for maintaining your directory. Typing make clean will remove any extraneous files in your directory, such as .o files and core files. Typing make cleanest will remove all .o files, core, Proj4, and backup files created by the editor. More information about these commands can be found at the bottom of the makefile.

Grading

The grade for this project will be broken down as follows. A more detailed breakdown will be provided in the grade form you receive with your project grade.

85% - Correctness

• Command line error checking is provided
• Your project produces all required output
• The output produced is correct
• The output is in an acceptable format.
• All function parameters are passed using the appropriate method
• const is used wherever appropriate
• All unmet function pre-conditions are handled.
• All project requirements are met
• No project restrictions have been violated
• Your class designs and implementations follow good OO principles.

15% - Coding Standards