Rubric
| Criteria | Excellent (6) | Good (5) | OK (3-4) | Needs improvement (0-2) |
|---|---|---|---|---|
| Adequacy of tests | Good plus tests are designed and documented with respect to problem definition. Corner cases are considered. | Complete coverage. At least one extra test per “important” function. | Complete test coverage, as indicated by DrRacket | Incomplete test coverage, as indicated by DrRacket |
| Correctness | Shows evidence of deeper understanding of the assignment, or defensive programming. | Correct to the letter of the assignment. | Almost completely correct, perhaps one incorrect case / input. | Substantial problems with correctness or syntax errors. |
| Criteria | Excellent (4) | Good (3) | Needs Improvement (0-2) |
|---|---|---|---|
| Racket Coding Style | Good plus nice line width and line breaks. Careful naming and scoping of identifiers. | Meaningful identifiers. Sensible racket indentation (according to DrRacket). | Bad indentation or cryptic identifiers, |
| Assignment defined idioms | Good plus code is concise, without being cryptic | No mutation or global variables. Follows assignment specified constructs and / or library functions. | Uses mutation or global variables. |
Approximate translation of scores
- 18 - 20
- A+
- 17
- A
- 14
- B
- 11
- C
- 10
- D
- 0-9
- F