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:
- Bring a hard copy of all your .java
files to class on the day the program
is due (if you do not want to lose late days).
- Submit an electronic version of all you files
(.java, makefile, output files, etc.) to the hand-in directory
of either you or your partner. Your hand-in directory
for project 2 is in: ~cs537-1/public/handin/project2.
If you are programming at home using the Windows
95 version of Java, you will still need to hand in your code
on-line (and you should make sure it works in the Solaris environment
- which will entail adding the ThreadScheduler code).
- Add a README file to your electronic
hand-in directory that contains the following:
- Name of you and your partner.
- Project information (project number, date, etc.).
- Information on how to run your program.
- A brief map of the classes you have written and what they
do.
- Any other information you feel is important for the ta to
know.
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:
- 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.
- You should comment your variables so we know how they are
used.
- 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.
- 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:
- Your code should be correctly indented.
- You code should have blank lines separating different segments
of code.
- Variable names should have meaning.
- Curly brackets should be correctly lined-up.