--------------------------------------------
Exams                                   40%
  Midterm                         20%
  Final                           20%
--------------------------------------------
Quizzes                                 16%
  (10 of them, drop 2 lowest, 2% each)
--------------------------------------------
Programs                                44%
  P1       1 week                  3%
  P2       1 week                  5%
  P3       2 weeks                 9%
  P4       1 week                  5%
  P5       2 weeks                 9%
  P6       3 weeks                13%
--------------------------------------------
                                       100%

Because old files are replaced by new files, you can turn in your program as often as you like. This is a nice way of backup up your program, allowing me to see you code when you come to office hours, and ensuring that something is turned in, in case a problem occurs at the last minute.

Grading of programming assignments is based upon several criteria:

Area	Percentage
Handin	5%
Report	10%
Correctness	50%
Technique	25%
Readability/Style.	10%

Handin is determined by your ability to follow directions when handing in your program. If you name your sources files correctly and include a text-only report.txt file, the grader's life is greatly simplified.

A writeup will be required for programs 2-6. For more information on that, click here.

Correctness is by far the most important criterion. Considerations are:

• Does your program compile?
• Does it produce the right output?
• Do you test for bad input (negative numbers)
• Check for division by zero
• Does your program crash for any reason?

The Technique used in a program is the means in which that particular problem was solved. A solution which is correct can still be clumsy or awkward. Considerations are:

• Good use of functions
• Breaking the program into logical pieces
• Avoiding the use of global variables whenever possible
• Avoiding redundant code

The Readability or Style of a program refers to the ease with which a human reader (such as the grader!) can read and understand the source code. The readability does not affect the execution of the program; however, poor readability can result in programming errors which make the program incorrect.

• Proper and consistent indentation of statements
• Documentation (via comments) for functions and parameters, and for non-obvious variables and pieces of code
• Use of blank lines to separate logically separate pieces of code
• Use of meaningful identifiers for variables, functions, etc.
• Correct use of constants
• Use of idioms (customary standard ways of writing logically equivalent pieces of code) discussed in class

Quizzes can be made up before the quiz date if you contact me in advance. Because you can drop 2 quizzes, no accomadation will be made for missing them.

If you know that you will miss an exam, let me know at least two weeks in advance for an exam, and I will schedule a make-up. Accomodations will also be made for people who miss an exam unexpectedly and can present a doctor's note. As with homework assignments, it is your responsibility to contact me AS SOON AS THE PROBLEM ARISES. If you know you will miss an exam or class because of a religious holiday (other than ones mentioned inside the front cover of the Fall 1997 timetable, which I already know about), you must let me know within the first three weeks of class.