C++ Computer Programming Rubric

Unsatisfactory [-100%] Satisfactory Good Excellent

Note: Any Unsatisfactory Must also include all Must also include all “Good”
criteria will result in a “Satisfactory” criteria, and criteria, and no
zero grade for the no “Unsatisfactory” “Unsatisfactory” criteria
assignment, and no criteria
further grading will be
done

Delivery  Completed less than 75%  Completed at least 75% of  Completed between 80-99%  Completed 100% of
of the requirements. the requirements. of the requirements. requirements
 Not delivered on time or  Delivered on time, and in
not in correct format (disk, correct format.
email, Canvas, printout
etc.)
 Does not comply with
requirements (does
something other than
requirements).

Coding  No programmer name
Standards included
 Poor use of white space
(indentation, blank lines)
making code hard to read.
 Disorganized and messy
 Uses global variable(s),
goto/continue/exit/break
(except in switch).
 Ambiguous identifiers.
 Includes name, and
assignment title.
 White space makes
program fairly easy to
read.
 Organized work.
 Good use of variables.
 Good use of white space.
 Organized work.
 Good use of variables and
constants
 Minimum line-wrap
 Excellent use of white space.
 Creatively organized work.
 Excellent use of variables and
constants.
 No magic numbers.
 Correct identifiers for constants.
 No line-wrap

Documentation  No documentation  Basic documentation has  Purpose is noted for each  Specific purpose is noted for
included. been completed including a function and control each function, control structure,
summary of requirements. structure. input requirements, and output
 Purpose is noted for each  One sample run included results.
function.
Runtime  Does not execute due to
syntax errors.
 Does not execute due to
runtime errors (endless
loop, crashes etc.)
 User prompts are
misleading or non-existent.
 No testing has been
completed.
 Executes without errors.
 User prompts contain little
information, poor design.
 Some testing has been
completed.
 Executes without errors.
 User prompts are
understandable, minimum
use of symbols or spacing in
output.
 Thorough testing has been
completed
 Executes without errors excellent
user prompts, good use of
symbols, spacing in output.
 Thorough and organized testing
has been completed and output
from test cases is included.

Efficiency  A difficult and inefficient  A logical solution that is  Solution is efficient and easy  Solution is efficient, easy to
solution. easy to follow but it is not to follow (i.e. no confusing understand, and maintain.
the most efficient. tricks).

Unsatisfactory Satisfactory Good Excellent Weight Score

Delivery x 30% 70%

Coding Standards
x 30% 85%

Documentation
x 10% 100%

Runtime
x 20% 85%

Efficiency
x 10% 0%
0% 70% 85% 100% Grade: 74%