CSE 332 - Data Abstractions - Winter 2012

CSE Home

332 Home

About Us

Search

Contact Info

CSE 332  Home  Calendar  Lectures  Section Assignments & Exams  Homeworks and Projects  Submission  Grades Communication  Anonymous Feedback  Discussion Board  Mail to Course Staff  Announcement Archive Policies  Collaboration Policy  Grading Policies  Programming Guidelines  Written HW Guidelines

Grading Policies Overall Course Grade Your overall grade will be determined as follows (approximate): Written Homework Assignments: 20% Programming Projects: 30% Midterm Exam: 20% Final Exam: 25% Best of the four items above: 5% We will have 3 programming project (each with phases) and 7 written homework assignments. Expect each written homework to contribute equally to the course grade. The first project will count approximately half as much as the subsequent two projects. When calculating final grades, we will drop your lowest written homework score. Late Policy Written assignments are due promptly at the BEGINNING of lecture, and late assignments will not be accepted. If you cannot attend lecture, please arrange to submit your homework earlier to the instructor or have a classmate submit it for you during lecture. Programming projects will be submitted electronically by the deadline announced for each project milestone. Once per quarter you may use a "late day" to obtain an extra 24 hours. For the last two projects, if working with a partner, BOTH partners must have a late day available. You should email cse332-staff before the deadline to let us know you intend to use your late day. If you are late more than once throughout the quarter, the staff will apply your "late day" to whichever missed deadline is most advantageous to your final grade. 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. After discussing your question with a TA or the instructor, if you feel that your work was misunderstood or otherwise should be looked at again to see if an appropriate grade was given, then 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, 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 it is possible to regain some points, but it is also possible to lose points. Grading Guidelines for Programming Assignments Also the course Programming Guidelines. For each project the, approximate and subject-to-change grade breakdown is: Program compilation and correctness: 40% Architecture/design, style, commenting, and documentation: 30% Writeup/README: 30% The reason "so few" points are allocated to error-free compilation and program correctness is because CSE 332 students 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). Program correctness and error-free compilation is therefore 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 heavily weighted. CSE 332 is also a course about data structures and the tradeoffs made during algorithm and 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 does not penalize students who "have the right idea" but could not get their code to compile because of a last-minute code change. Extra Credit: We will track any extra features you implement (the Above and Beyond parts). You will not 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 Box 352350 Seattle, WA  98195-2350 (206) 543-1695 voice, (206) 543-2969 FAX