CSCI 1321 (Principles of Algorithm Design II), Spring 2003:
Homework 8

Due:

May 12, at noon. Not accepted late.

Credit:

80 points.

What you are to do

Briefly review Dr. Lewis's Project Description and read the specific instructions for Assignment 8. In this assignment you are to do the following.

• Make your game as functional, playable, and pretty as you can in the time available to you.

• Fix any known bugs and/or unusually messy code. This includes correcting any problems I pointed out in grading your other assignments.

• Make the documentation consistent with the current state of the code and reasonably complete. I will grade the HTML version of your documentation, so be sure it includes everything you want me to read. If you haven't already done so, at this point you should do the following.
  • Be sure every class, and every public method or variable, has at least a brief comment describing what it is and how it fits into your game. (Exception: You do not need to describe how your list and priority queue classes fit into the game.) For methods, also describe parameters and return values if their meaning and purpose isn't clear from the overall comment about the method.

  • Be sure comments are consistent with the final state of the game and no longer include any of Dr. Lewis's instructions. (For example, his version of GameSetup includes this: ``Students will be given this class and the various interfaces in code format. My implmentations of all the other classes will only be distributed in compiled, .jar format.'' Your version should not.)

• Undo the changes made for Homework 7 that would make the game less playable -- the command-line arguments that allow you to test performance and the code in your player class that prints out performance data. It's up to you which of your two implementations of the priority queue you use in this final version.

The goal is a game that would look equally polished to someone playing it and to someone reading the code.

For this assignment, it would probably be best to start with the version of your game you turned in for Homework 6, since most of the additions required for Homework 7 should be removed for this final version.

Turning in your documentation and code

For this assignment there is no separate design step; you are to turn in everything together. As with previous assignments, use Together to generate HTML documentation for your classes. For this assignment, it should go in subdirectory Local/HTML-Documents/PAD2Project/Assn8/Final of your Linux home directory. I will assume that it is ready to be graded when I receive your code. E-mail all your source code (.java files), and any additional files needed for your game (e.g., files created by the screen editor) to me at bmassing@cs.trinity.edu. You may use either of the following methods.

• Use your favorite mail program and attach each file as an attachment.

• From Linux/Unix, cd to the directory containing your project and type the following command.

  /users/bmassing/Pgms/cs1321/sendfiles assignment

  where assignment is some text that indicates which assignment this is (e.g., ``hw8'' or ``homework 8'').

  This script will e-mail all files in the current directory except the ones that I don't need or will recreate. It also sends a copy of the e-mail to your Trinity account, so you can be sure about what was sent.