File: hw14.txt	

Your name: 


Due Friday, April 19 by 11:59pm.

Points: 30 points total.
Extra credit: none.

Copy this file to your ~/handin/project/ directory and 
complete the following...  

(0) Who are you working with?  About how much work has each person done 
so far?

Note: points will be taken off for people who have not done anything...


(1) Make a directory in your handin folder called project, and copy your 
project files into that directory.  Include here a brief description of what 
you are doing for your project, and how to compile and run your project.

Project title:

Project description:

How to compile/run:

Who working with:


(2) You need to come and see me again in my office this week to discuss
the project once you have worked on what we talked about last week.
-5 if you don't come to talk with me.


(3) If working in a group, each person should have a copy of the project
and this file in their handin/project/ directory.


(4) Rules for your program for this checkin.
* Your program must be commented.  This means: (a) comments at the tp 
  of the file saying what it is and how to compile/run, (b) comment
  for each function saying how it is used, what the parameters are, 
  and what the return value or effect of the function is, (c) single-line
  comments throughout as needed to explain how the code works.
  -3 points if not commented.
* You must separate out your code into functions.  Generally, each function 
  should fit on 1-2 screens in putty (so 30-50 lines).  
  -3 points if no functions, or bad use of functions.
* You must use descriptive variable and function names.  Use names that 
  make sense to make it easy for me (and you) to understand your code.
  -3 points if using bad variable names.
* The code must be indented properly (press tab on each line in emacs),
  and use whitespace to make it easy to read.
  -3 points if not indented nicely.
* There should be at least one use of a loop.
  -5 points if no loops.
* There should be some user input/output.
  -5 points if no user input or output.


(5) And you should follow the plan we talked about last week.


(6) Grading.  Besides taking off for not doing those things above, the grading
    is
    15/30 - program does compile and run but doesn't really do much.  You 
    	    clearly have not put enough effort into the project.  Or, you have
	    put some effort into it, but it doesn't work (in that case, you 
	    need to keep working on your programming skills).
    23/30 - program does do some things, but has some serious problems too.
    	    You have gotten a start, but probably need to ramp things up if
	    you're going to get it done.
    27/30 - pretty good, not great.  there are still a few little things
    	    you didn't get done, but overall have made a good effort and it 
	    is heading in the right direction.
    30/30 - If the program is looking really good.  There may still be things
    	    to do, but you did finish everything we talked about the first
	    week, and it all looks good.