• To gain experience designing and implementing a generic class
• To gain experience with text file input/output
• To gain experience with try/catch blocks and throwing exceptions
• To gain experience using command line arguments

Your project will instantiate exactly three delivery trucks -- one that carries boxes, one that carries cans, and one that carries sacks. Your trucks will load boxes/cans/sacks, drive from one destination to another, deliver boxes/cans/sacks, and print an inventory their contents. Commands read from a command file direct your trucks. Output from your project will be displayed on the screen and output to a file.

This project will get its input from the command line rather than from a GUI.
The command linewill have three arguments

1. The maximum number of boxes/cans/sacks a truck can carry regardless of their size or weight.
2. The name of the command file.
3. The name of the output file.

The Generic Truck Class

Our truck has the following attributes. Other private attributes may be added if you find them helpful in your implementation

1. Its capacity (max number of packages) as read from the command line.
2. Its current location
3. The total number of miles driven
4. A list of the current contents of the truck

1. Construction of an empty truck. Creates an empty truck with the user specified capacity which has been driven zero miles and begins its journey at a location specified as "Warehouse".
2. Load an item onto the truck. Duplicate items are permitted.
3. Deliver an item. Unloads the specified item from the truck. If the item to be unloaded is one of a set of duplicates, unload any one of the duplicate items.
4. Drive the truck a specified number of miles to a new location.
5. Other necessary methods such as equals, toString, etc.

The Sack Class

The Box Class

The Can Class

1. An attempt to load a box/can/sack into a truck that is full
2. An attempt to deliver a box/can/sack from a truck that is empty
3. An attempt to deliver a non-existent box/can/sack

• COMMENT <remainder of the text on the line>
  This is a comment line which should be read and ignored.
• DRIVE BOX|CAN|SACK <destination> <miles>
  Tells the box, can, or sack truck to drive to the given "destination" (a string). The distance to the destination is given by "miles", which is a positive integer. For example: DRIVE BOX Boston 120 or DRIVE SACK Washington 42
• LOAD BOX|CAN|SACK <attributes>
  Tells the truck to load a box, can, or sack onto the appropriate truck. If the truck is full, an appropriate error message is displayed.
• DELIVER BOX|CAN|SACK <attributes>
  Tells the appropriate truck to deliver a box, can, or sack to the addressee at the current location. If the box, can, or sack is not on the truck or the truck is empty, an appropriate error message should be displayed.
• PRINT
  Tells all trucks to print their current inventory, current location and the total number of miles driven so far.

The attributes of the BOX for the LOAD and DELIVER commands are separated by white space and occur in the following order:
contents (a string with no spaces), length, width, height, weight, and the name of the person to whom the box should be delivered (a string which may contain spaces)

The attributes of the SACK for the LOAD and DELIVER commands are separated by white space and occur in the following order:
contents (a string with no spaces), material (a string with no spaces), weight, and the name of person to whom the box should be delivered (a string which may contain spaces).

The attributes of the CAN for the LOAD and DELIVER commands are separated by white space and occur in the following order:
contents (a string with no spaces), diameter, height, weight, and the name of the person to whom the box should be delivered (a string which may contain spaces).

1. Each time a command (other than COMMENT) is read from the command file the command and its parameters must be displayed.
2. Each time the PRINT command is encountered, the current location, current mileage and list of current contents of all trucks must be printed. All attributes of each box, can, and sack must be displayed.

linux1[5]% proj5.Project5 40 commands.dat
Processing File: commands.dat

Cmd: PRINT
     BOX TRUCK
     The truck's current locations is: Warehouse
     The truck has driven 0 miles so far
     The truck is empty

     SACK TRUCK
     The truck's current locations is: Warehouse
     The truck has driven 0 miles so far
     The truck is empty

     CAN TRUCK
     The truck's current locations is: Warehouse
     The truck has driven 0 miles so far
     The truck is empty

Cmd: LOAD BOX oranges 2 3 4 9 Bob Smith
Cmd: LOAD BOX Toys 2 4 5 12 Santa
Cmd: LOAD CAN Soup 4 3 1 Bob's Big Boy Restaurant
Cmd: LOAD SACK corn paper 50 Tommy Jones
Cmd: DRIVE BOX Catonsville 20
Cmd: PRINT
     BOX TRUCK
     The truck's current locations is: Catonsville
     The truck has driven 20 miles so far
     The truck's contents
     -------
	 L x W x H: 2 x 3 x 4
	 Contents: oranges
	 Weight: 9 lbs
	 Addressed to: Bob Smith
     --------
	 L x W x H: 2 x 4 x 5
	 Contents: Toys
	 Weight: 12 lbs
	 Addressed to: Santa

     SACK TRUCK
     The truck's current locations is: Warehouse
     The truck has driven 0 miles so far
     The truck's contents
	 ------
	 Material: paper
	 Contents: corn
	 Weight: 50 lbs
	 Addressed to: Tommy Jones

	 CAN TRUCK
     The truck's current locations is: Warehouse
     The truck has driven 0 miles so far
     The truck's contents
	 ------
     D x H: 4 x 3
	 Contents: Soup
	 Weight: 1 lbs
	 Addressed to: Bob's Big Boy Restaurant
    

1. Mr. Frey's public directory for this project is
   /afs/umbc.edu/users/f/r/frey/pub/CMSC202/Proj5
2. The Truck, Box, Can, and Sack classes must be defined in a Java package named "trucks".
3. Other classes you may create (e.g. exception classes) should also be part of the "trucks" package.
4. The Project5 class that contains main must be defined in a Java package named "project5"
5. Keep your classes simple and self-contained. Do not write unnecessary methods. Make sure each class is doing its own work.
6. Make appropriate use of helper methods, especially for main.
7. Don't use arrays
8. If your Truck requires that the Box, Can, and Sack support specific methods other than those they inherit from Object, you must define and implement an appropriate interface for those methods.

For 10 points of extra credit

1. Define the class hierarchy of packages described above
2. Implement the Sack, Box, and Can as derived classes of Package
3. Instantiate just one Truck for loading, delivering, and moving all kinds of Packages. (Yes, the Truck must still be implemented using generics).
4. In the command file, BOX|CAN|SACK in the LOAD and DELIVER commands will now specify what kind of package to LOAD onto/DELIVER from the one and only Truck, rather than which truck to LOAD onto/DELIVER from.
5. In the command file, all DRIVE commands apply to the one and only truck. The second parameter of the DRIVE command (BOX|CAN|SACK) should be ignored.
6. When PRINTing the truck contents, print each package's type in addition to its attributes.
7. Submit a README file with your project telling the grader that you are seeking extra credit.

1. You should try as much as possible to complete the project by yourself.
2. You may get assistance only from the TAs or instructors
3. You must document all outside help you get as part of your file header comment.

1. copy anyone else's code
2. have someone else write your code for you
3. submit someone else's code as your own
4. look at someone else's code
5. have someone else's code in your possession at any time

10% - Design Assignment

80% - Correctness

1. Have you verified the command line and its parameters?
2. Does your output meet all output requirements? Is all output produced by the appropriate class' method?
3. Do all methods have the proper PreConditions? If so, are all PreConditions handled?
4. Are you throwing exceptions wherever required?
5. Are all exceptions being caught and handled properly? I.e. being thrown by the appropriate methods, caught by the caller and dealt with appropriately?
6. Are your classes implemented using appropriate OOP principles -- encapsulation and abstraction?
7. Does your Truck load/unload/print duplicate items correctly?

10% - Coding Standards

Submit as follows:

           submit cs202 Proj5 <list of files>

More complete documentation for submit and related commands can be found here.

Remember -- if you make any change to your program, no matter how insignificant it may seem, you should recompile and retest your program before submitting it. Even the smallest typo can cause compiler errors and a reduction in your grade.