Overall course grade
Grades will be computed approximately as follows (weights may be modified):
We will have approximately one assignment per week. If you find an error in our grading, please bring it to our attention within one week of that item being returned.
Late policyLate work will be accepted but at a penalty of 20% off per 24 hours late. Note that ALL parts of the assignment must be received by the stated deadline. In the case of written assignments that are due at 2:30pm on Friday, you would need to create an electronic version and email it to us in order to submit by 2:30pm on Saturday to be considered 24hrs late.
Re-grade PolicyIf you have a question about an assignment or exam that was returned to you, please don't hesitate to ask a TA or the instructor about it during their office hours. Learning from our mistakes is often one of the most memorable ways of learning!
If after discussing your question with a TA or the instructor 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 as follows:
Grading guidelines for programming assignmentsSee also the "Programming Guidelines" at left. Approximate grade breakdown:
The reason why "so few" points are allocated towards program correctness and error-free compilation is because students who have gotten past 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 373 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, 373 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.
Putting weight on the design and writeup aspects for projects is also useful because it doesn't penalize students who "have the right idea" but couldn't get their code to compile because of a last-minute code change.
Extra Credit: We will keep track of any extra features you implement (the Above and Beyond parts). You won't see these affecting your grades for individual projects, but they will be accumulated over all projects and used to bump up borderline grades at the end of the quarter.
Computer Science & Engineering|
University of Washington
Seattle, WA 98195-2350
(206) 543-1695 voice, (206) 543-2969 FAX
[comments to rea]