Inventory program Need HELP !

I need to create this program for maintaining the inventory for a
video store. Instead of keeping a list of people and addresses for the wait list, just keep track of the number of reservations (wait number).
I need to Design and implement a class called Movie. This class should hold all of the
information required for one movie title, and have methods for all of the manipulations
on that data. Also include methods to write the information to a file and to read it back
again.
I also need to Design and implement a class template called ListL that implements a linked list for any type. Make the list an indexed list. I need to be sure to have Insert, Delete, and Retrieve methods. It will be useful to have a Retrieve method that returns a reference to the data item, not a copy of the item.
I need to Design and implement a pair of functions to read/write a ListL of Movie objects from/to a file.
I also need to Design and implement a function that reads commands from the keyboard, and calls a different function for each command.
Then I need to Design and implement functions for each of the commands:
H ( help )provides a summary of the available commands.,
I<title> (inquire) displays the information of the movie title,
L (list) list the entire information in alphabetical order,
A<title> (add) add a new title to the movie list,
M<title> (modify) modify if the stock has few movies in stock,
S<title> (sell) decrease the count for the specified movie by 1. if the movie is sold out, put a name on the wait list for the movie , and
Q (quit) save the inventory and wait numbers in a file and terminate execution.

And finally I need to Create a set of test data to verify that my program functions correctly, and Supply the test data files and an instruction file called README that describes how each of the commands was verified to be correct.

If you want us to do your homework for you, you could at least make an effort to do some of it yourself first....

There's a lot of us who'll be happy to help if you get stuck, but we ain't doing the the whole lot

Well, in that case, the best way is that you buy a book about programming and - perhaps - another one about database programming...

*** This message was posted using 100% recycled electrons ***