The required functionality of the Rental System is described in the project description. You must design the public methods (full function prototypes, pre- and post-conditions) required to support that functionality. You will also decide on the private data members for this class. Remember that as you design your classes - you should focus on each class representing ONE THING like a DVD. Then each object corresponds to an instance of that class - a physical DVD that you can hold in your hand. It is, however, appropriate to also have classes that represent a collection of objects. Remember to use aggregation whenever appropriate.
There are no restrictions on what the test cases can be, so all 5 can test one method if you like, or each can test a different method. However, you MUST include at least one valid and one invalid test. Again, you should use the categories:
Description
Input (this will be parameter values this time...)
Expected Output
Your p2design.txt file will be compared to the header file or files that you submit when Project 2 is due. Minor changes to the design are allowed. A minor change might be the addition of another function or two or changing the way in which one or two parameters are passed.
If there are major changes between the design document and the header files that are part of the final project, you will lose 5 points. This would indicate that you didn't give sufficient thought to your design before beginning the implementation.
A template for your design document, p2design.txt, is provided in Ms. Wortman's public directory. Copy that file