|
|
|
|
|
Overall course grade
Grades will be computed approximately as follows
(weights may
be
modified):
- 60% Assignments (Written Exercises and Programming
Projects)
- 15% Midterm Exam
- 25% Final Exam
We will have 6 assignments. If you find an
error in our grading, please bring it to our attention within one week
of that item being returned.
Late policy
ALL parts of an assignment must be received by the stated deadline in
order for the assignment to be counted as on time. Each student in the
class will be given a total of two "late days" (a late day is 24 hours
of lateness) for the quarter. There are no partial days, so assignments
are either
on time, 1 day late, 2 days late, etc. Once a student has used up all
of his or her late days, each successive late day will result in a
loss of 20% on the assignment. You may not submit any portion
of any
assignment more than 3 days after its original due date.
- All assignments will be turned in electronically (at
a
time announced for each assignment). If you choose to handwrite the
paper assignments, please scan them so they can be turned in
electronically.
- We may have a few written assignments that we will
submit
only on
paper (not electronically). These are due promptly at the
beginning of
lecture. If you cannot attend lecture please arrange to turn
in your
homework earlier to the instructor or have a classmate turn it in for
you during lecture.
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.
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:
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.
See also the Programming
Guidelines. While the exact breakdown will vary from project to
project, the approximate grade breakdown is:
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
Box 352350
Seattle, WA 98195-2350
|
|
CSE Home 
