Project Description

For accounting and tax purposes, each different type of vehicle will be handled by a different rental system. However, your application must perform the same functions (such as calculating rental/mileage/insurance cost, printing customer list, printing vehicle list, printing rental reciepts, and perfoming vehicle maintenance) regardless of what kind of vehicle is being rented.

Your software company has correctly decided that the best way to implement this "one size fits all" rental system is to use a C++ class template. This decision is based on the observation that the functionality of the rental system is the same regardless of the vehicle being rented.

Project 5 is the pilot program for this new concept. In project 5 you will be implementing the rental system class template and testing it by creating rental systems for cars and for motorcycles.

1. Add a new vehicle to the rental system -- self explanatory.
   All vehicles added to the rental system come directly from the dealer with no mileage recorded on the odometer.
2. Add a new customer to the rental system - self explanatory.
3. Rent a vehicle to a customer -- associate the vehicle and the customer.
4. Return a vehicle.
   When a renter returns a vehicle, 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 the vehcicle tag number, all renter information and the breakdown of the rental cost. Required vehichle maintenance is performed.
   Note that only the vehicle tag number must be printed in the receipt. This is less information than in project 4.
5. Print a list of all vehicles.
   Each vehicle tag number is printed (this is less information than project 4). If a vehicle 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 vehicles 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 vehicle.
8. Remove a vehicle -- self explanatory
   It is an error to attempt to remove a vehicle that is currently rented.

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

Cars

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 vehicles 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. All vehicle license tag numbers are 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 vehicles at a time.

The Command File

Each command and all of its parameters appear on one line. You may assume that valid commands are properly formatted and all data elements are the appropriate type. You may not assume all commands are valid. Blank lines may be found anywhere in the file and should be ignored.

• JUNK <tag number> -- removes the specified vehicle from the rental system where
  <tag number> is a string with no spaces

• REVOKE <card number> -- removes the specified customer from the rental system where
  <card number> is an integer between 1 and 999999, inclusive

• CAR <type> <license tag> <model> -- adds a new car to the reservation system where
  <type> is one of "ECONOMY", "MIDSIZE" or "LUXURY" (without the quotes)
  <license tag> is a string with no spaces
  <model> is a string which may contain spaces
  This command is only valid for car rental systems

• CUSTOMER <first name> <last name> <age> <card type> <card number> -- adds a new customer to the reservation system where
  <first name> and <last name> are strings with no spaces
  <age> is an integer
  <card type> is one of "GOLD" or "PLATINUM" (without the quotes)
  <card number> is an integer between 1 and 999999, inclusive.

• RENT <tag number><card number> -- rents the specified vehicle to the specified customer with this membership card number where
  <tag number> is a string with no spaces
  <card number> is an integer between 1 and 999999, inclusive

• RETURN <tag number> <number of days> <number of miles driven> -- specified vehicle is returned
  <tag number> is a string with no spaces
  <number of days> and <number of miles driven> are positive integers

• PRINT <what> -- Prints the specified list where
  <what> is one of "VEHICLES" or "CUSTOMERS" or "MAINTENANCE".
  If "what" is "MAINTENANCE" then there will be an additional string parameter which is the tag number of the car whose maintenance log should be printed.
  "MAINTENANCE" was for project 3 extra credit only. If you did not seeking extra credit in project 3, or you removed your extra credit code, then "PRINT MAINTENANCE <tag number>" should be considered an invalid command and an appropriate error message should be produced. Test files will contain these commands.

• MOTORCYCLE <manufacturer> <tag number> <motor size> where
  <manufacturer> and <tag number> are strings with no spaces
  <motor size> is a positive integer
  This command is only valid for motorcycle rental systems

Sample Output

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 Proj5Aux.h and they must be implemented in Proj5Aux.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.

Project Design Assignment

Project Makefile

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

Note that it is not necessary to compile your rental system class template. That code will get compiled as part of Proj5.cpp when rental system classes are used.

The graders will be typing the command make Proj5 when they grade your project. This command must cause all .cpp files to be compiled and the executable named Proj5 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, Proj5 executable 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