Overview
This page describes the rubrics (i.e., grading rules) for a given assignment.
The terms assignment, drill, problems, and challenge are used interchangeably on this page.
The rules implicitly apply to the given assignment write-up.
Grading Rules
- Program elements (e.g., directories, files, classes, methods) should be named exactly as specified -- this includes case -- in other words "Rectangle.java" would not match "rectangle.java" -- the reason is for this is that program compilers and runners (e.g. Java) require exact matches (i.e. are picky)
- ZIP file names should also be named exactly as specified (like above)
- Here is a page that describes how to prepare a ZIP file
- All programs should compile cleanly (no compile errors)
- All programs should run cleanly (no runtime errors)
- All programs should produce actual output that matches expected output
- The previous rule should be true for all input data scenarios
Tips:
- It is yes required that you fix compiler errors. It is not required that you fix compiler warnings. However, it will greatly benefit you if you do fix (eliminate) compiler warnings from your program.
- When testing your program, remember to test boundary cases. For example, if you have a program that will sum a list of numbers, a boundary case may be for an empty list (we would expect a sum of zero).
- The rules about a clean compile and clean run are the most important -- the reason is that if either of those fail this will "block" the remainder of the grading (e.g., checking output) so would generally produce a very low score, possibly a zero
Rubrics