Grading Policies

Re-grade Policy

If after discussing your question with a TA or the instructor (either in person or via email) you feel that your work was misunderstood or otherwise should be looked at again to see if an appropriate grade was given we ask that you submit a written re-grade request. If the work was graded in gradescope, you may submit your request via a gradescope regrade request. Otherwise:

• Email a written summary describing why the work should be looked at again to the cse332-staff list.
• Be sure to include your uwnetid/cseid and full name and the name of the assignment in question.
• Re-grade requests should be submitted within a week of when the assignment was returned.

Grading guidelines for programming assignments

• Program correctness, compilation -- 40% of total grade
• Architecture/design, style, commenting, documentation -- 30%
• Writeup/README -- 30%

The reason why "so few" points are allocated towards program correctness and error-free compilation is because students who have gotten past CSE 143 are smart enough to know how to get their code to compile and run against the general input (although testing "boundary conditions" is a skill which students should aim for), so program correctness and error-free compilation is neither a fair nor discriminating measurement of project quality.

The two biggest discriminating factors among CSE 332 students are program design (such as style and architecture) and analysis (the README/writeup), which is why these factors are weighed a little heavily. Also, CSE 332 is a course about data structures and the tradeoffs made during algorithm/data structure design, so putting additional weight on program design, and questions about program analysis and weighing tradeoffs is more in keeping with the course goals.