CS 1112 Fall 2008 Grading Guide: Project 3
The coded items below (e.g., c1e, s2a) indicate what a student’s solution should accomplish. Codes that
begin with the letter ‘c’ deals with correctness; codes that begin with ‘s’ deals with style.
Grader: If a student’s solution does not accomplish task c1a, for example, then write the task
code ‘c1a’ along with any diagnostic remarks you can give. Count the number of correctness and
style errors separately.
Items marked with ** count as two errors. In the table below, the top row lists the possible scores (1 to 5).
The next row lists the number of correctness errors corresponding to every score category. The style score
is determined similarly. Enter the total score (maximum of 10) in CMS as the project score. If there are
bonus questions, enter any bonus points separately in the “Bonus Bucket,” separate from the project score.
Student: Read the grading guide for every project, even if you get a perfect score! Notice from the
table below that we often give one or two “freebies,” i.e., mistakes that don’t cost you any points.
Learn from working on the project, and learn from any mistakes.
Scores
c and s stand for correctness and style; see table below
parts with ** next to them means that they are double the value, *** for triple, etc.
Score 0 1 2 3 4 5
#correctness errors >=16 11-15 6-10 4-5 2-3 0-1
#style errors >=6 5 4 3 2 0-1
General
(s0a) Use meaningful variable names
(s0b) Appropriate indentation
(s0c) Appropriate comment header in each script/function file
(s0d) Use semi-colons as needed; not for use after if condition or else keyword
(s0e) Appropriate and concise comments throughout
(s0f) Reasonable line lengths; no horizontal scrolling
(s0g) [2* max] No superfluous code. This includes having an empty else block as part of an if
statement. However, do not penalize inefficiency unless it is excessive.
(s0h) No debugging output.
