Programming Rubric
Here is how I will grade programming projects. Note that the value of particular items changes (and typically increases) as the weeks progress.
The entries in each cell are the number of points I will potentially take off if the item is missed. Note that these may, and do, total to more than 100 points. That is because I do not expect to see many of these problems, especially after the first project.
|
Project # |
1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 |
|
Item |
||||||||
| Testing | ||||||||
| No tests | 10 | 20 | 40 | 80 | 100 | 100 | 100 | 100 |
| Do not test boundary conditions | 3 | 5 | 10 | 20 | 30 | 30 | 30 | 30 |
| Comments for methods, variables, logic | 3 | 5 | 10 | 20 | 30 | 30 | 30 | 30 |
| Clarity of code | ||||||||
| Indenting | 3 | 5 | 10 | 20 | 40 | 40 | 40 | 40 |
| Clear variable names | 3 | 5 | 10 | 20 | 40 | 40 | 40 | 40 |
| Clear logic and structure | 3 | 5 | 10 | 20 | 30 | 30 | 30 | 30 |
| Missing functionality or not done according to the requirements | Determined per project. For example, each item may be 15 points. | |||||||
| Program does not check for boundary conditions. | 3 | 5 | 10 | 20 | 30 | 30 | 30 | 30 |
| Bugs in functionality | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 |
| Run time analysis (DS only) | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 |