CSE logo University of Washington Computer Science & Engineering
 CSE326 Winter 2006
  CSE Home    326 Home   About Us    Search    Contact Info 

 Project 1
 Project 2 - phase A
 Project 2 - phase B
 Project 3
 Homework 1
 Homework 2
 Homework 3
 Message Board
 Annoucement ArchiveCSE only
 Class List ArchiveCSE only
 Anonymous Feedback
 Mail Instructor & TAs
 Calendar & Slides
 First Day Handout
 General Guidelines
 Grading Policies
 Programming Guidelines
 Writeup Guidelines
 Unix Basics

Overall course grade

Your overall grade will be determined as follows (approximate):

  • Written Homework Assignments: 20%
  • Programming Assignments: 25%
  • Midterm Exam: 20%
  • Final Exam: 25%
  • Best of above three: 10%

If you find an error in our grading, please bring it to our attention within one week of that item being returned.

Late policy

  • Written assignments: Due promptly at the beginning of class, late assignments will not be accepted.
  • Programming assignments: Programming assignments will be turned in both electronically (at a time announced for each assignment), followed by hardcopy turnin at the next class or section. Once per quarter you may use your "late day" to buy an extra 24 hours for the electronic turnin, with hardcopy turnin at the following class or section. You must email your TA before the deadline to specify that you will be using your late day so he or she can make appropriate arrangements. If working with a partner, BOTH partners must have their late day available in order to take the late day.
Occasionally exceptional circumstances occur. If you contact the instructor well in advance of the deadline, we may be able to show more flexibility in some cases.

Re-grade Policy

If 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:

  • Along with the original paper version of the assignment you wish to have re-graded, you must also include a written summary (which can be neatly handwritten) describing why the work should be looked at again.
  • Submit it to the instructor or to a TA.
  • Re-grade requests should be submitted within a week of when the assignment was returned.
Note that when a written assignment, programming assignment, or test is re-graded, the entire work will be re-graded. This means that while it is possible to regain some points, it is also possible to lose points.

Computing environment

The course labs are Allen 002, 006 and 022. Labs have Windows machines with X servers to access the instructional Unix server attu.cs.

Grading guidelines for programming assignments

See also the "Programming Guidelines" at left. Approximate grade breakdown:
  • 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 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 326 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, 326 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.

CSE logo Computer Science & Engineering
University of Washington
Box 352350
Seattle, WA  98195-2350
(206) 543-1695 voice, (206) 543-2969 FAX
[comments to cary]