Correctness, design, and style are the three axes along which CSCI E-33a assesses student work.
Guidelines on Awarding Design Points
Design points are not subtractive—that is, a baseline grade is not a 5 and earning a 3 does not mean that a student has “lost two points” on an assignment or “earned a 60%” (two common interpretations we hear from students). Rather, points are used to characterize the extent to which a student has met, exceeded, or fallen short of the course’s expectations.
The course expects that most students on average will be earning a score of 3 or 4 on the Design axis, with perhaps a 2 serving as the low end. Reserve awarding a 5 only to those submissions that are exceptional, for which you can find absolutely no room for improvement. If you can propose even one modification that would improve efficiency, it’s not a 5 and should not be scored as such.
3’s and 4’s should be awarded to work that demonstrates a good to great mastery of the given week’s concepts and problem set. A student’s benchmark for success is considered a 3.
1’s and 2’s should be awarded to work that demonstrates a poor to fair understanding of the given week’s concepts and problem set. Awarding a 1 or a 2 indicates that there are substantial improvements to be made to the design of a student’s solution.
What if a student asks for an extension?
If a student asks for an extension, you should respond by directing the student to the lateness and extension policies in the syllabus.
How should I grade incomplete work?
If a student has submitted an incomplete solution, it is best to approach grading design in response to the question, “Given what the student has submitted, what evidence do I have that they have understood a good design approach to the problem?”. It’s best to avoid a scenario where a student is double-penalized for incompleteness on both correctness and design, but it’s also best not to extrapolate from a single function that a student has understood all of the week’s concepts.
How long should I spend grading?
This depends on the week! On average, aim to spend about 10 minutes per student in your section. Set a timer if it’s helpful!
Grading deadlines for problem sets are in the respective pages on this site, but are also summarized below:
|Quiz A Grading Deadline||2023-09-14T23:59:00-04:00||Glenn|
|Quiz B Grading Deadline||2023-09-21T23:59:00-04:00||Logan|
|Project 0 Grading Deadline||2023-09-28T23:59:00-04:00||TFs grade for their students|
|Quiz C Grading Deadline||2023-09-28T23:59:00-04:00||Glenn|
|Project 1 Grading Deadline||2023-10-12T23:59:00-04:00||TFs grade for their students|
|Quiz D Grading Deadline||2023-10-12T23:59:00-04:00||Logan|
|Project 2 Grading Deadline||2023-10-26T23:59:00-04:00||TFs grade for their students|
|Quiz E Grading Deadline||2023-10-26T23:59:00-04:00||Glenn|
|Project 3 Grading Deadline||2023-11-09T23:59:00-05:00||TFs grade for their students|
|Quiz F Grading Deadline||2023-11-09T23:59:00-05:00||Logan|
|Project 4 Grading Deadline||2023-11-23T23:59:00-05:00||TFs grade for their students|
|Quiz G Grading Deadline||2023-11-23T23:59:00-05:00||Glenn|
|Proposal Grading Deadline||2023-11-26T23:59:00-05:00||TFs grade for their students|
|Quiz H Grading Deadline||2023-12-07T23:59:00-05:00||Logan|
|Status Report Grading Deadline||2023-12-14T23:59:00-05:00||TFs grade for their students|
|Implementation Grading Deadline||2023-12-21T23:59:00-05:00||TFs grade for their students|
Project-Specific Grading Guidelines
The below pages include project specific guidelines, as well as links to staff solutions on Vault50.