Date: Tue, 05 Nov 1996 20:57:24 GMT Server: NCSA/1.5 Content-type: text/html Last-modified: Sun, 06 Oct 1996 14:01:57 GMT Content-length: 3290 Untitled

Hand-in for Project 2


Hand-in Procedure

The procedure for handing in project 2 (and the rest of the projects this semester) will be a little different than for project 1. You should follow the guidelines below:

Output Files

You should not hand in a hard copy of your output (it will use too much paper). Instead you should run the tests required by the assignment and output the results to a file. I would prefer if you could create separate files for each test (e.g.: Alg1Peterson.test, Alg2Peterson.test, Alg1Star.test, Alg2Star.test.) instead of having everything bunched together into a single typescript file. You can do this by redirecting the output. The format of the output is described in the assignment.

Comments

Comments are going to be worth at least 10% of the grade for this assignment. So if you do not want to lose any of the points, you should follow the guidelines below:

  1. You should write your name and your partner's name, the assignment number, and the hand-in date at the top of all your .java files as well as give a brief description of what the file contains.
  2. You should comment your variables so we know how they are used.
  3. Functions should be commented as to their purpose, what variables are being passed in, what value is being returned (if any), as well as any side effects.
  4. You should document segments of code and provide the purpose of each. Particularly difficult segments of code will require more commenting.

Program Structure

Program structure will also be worth at least 10%. Some guidelines follow:

  1. Your code should be correctly indented.
  2. You code should have blank lines separating different segments of code.
  3. Variable names should have meaning.
  4. Curly brackets should be correctly lined-up.