image University of Washington Computer Science & Engineering
  CSE 417Wi '22:  Grading, Late Policy, Integrity, ...
  CSE Home   About Us    Search    Contact Info 

Assessment

This quarter we are offering the course in a format loosely based on "mastery grading," since:

  1. The algorithmic concepts often take time to click. We care more about whether you understand a topic by the end of the quarter than in the middle. We hope this format will allow you to return to questions and topics you missed the first time around.
  2. We are still in a pandemic; this format is more flexible to (individual or university-wide) emergencies.

We will not score your submissions for exact points (i.e., you won't get 18/20 on a problem). Instead, every problem will get one of the following scores:

Grade Description
Excellent (E) Would have gotten (nearly) full credit with points-based grading. Main idea and edge cases are all correct.
Satisfactory (S) Would have gotten about 80-90% on points-based grading. Main idea is correct, but some edge cases or follow-up questions are wrong or missing.
Not Satisfactory (N) Would have gotten above 50% on points-based grading, and substantial progress toward a solution, but important omissions/errors.
Ungradable (U) No substantial progress, directions not followed (e.g., used a library or approach that isn’t permitted), etc.

The main goal is to change the focus of grading to a crisp assessment of whether you have mastered the material. Hopefully it will also give the TAs more time to generate helpful feedback.

Logistics

On the day a homework is due, the Gradescope submission boxes (plural --- one per problem) will close at 11:59PM. Additionally, you will have a chance to revise and resubmit problems --- ones that you didn't finish by the original deadline or on which your original submission didn't get as good a score as you desired. TA resources permitting, we intend to regrade and give you feedback on all of your resubmissions, but (a) you may only resubmit a given problem once, and (b) only a limited number (10, i.e. an average of about 1 per week) of them will count in your final grade. You may resubmit at any time, but I strongly recommend against waiting until the last minute. (In particular, I may need to modulate this at the end of the quarter, and e.g., there may be no time to resubmit/regrade the last 1 or 2 assignments.)

We will release 7-9 homeworks during the quarter, typically with 5-10 problems each. As will be obvious, some problems will be more challenging than others. We will weigh these somewhat more heavily in final grade calculations, but the bottom line is that if you get "E"'s on the bulk of your work, say 75-80% of problems, with the rest mostly "S"'s, you will get a good grade (say, 3.5 or better). Your "10 best" resubmitted problem grades will replace the original grades for those problems, and if you resubmit more than 10 problems, we will choose the "10 best" to be those that boost your (weighted) score the most.

Late Policy

Resubmissions are in part intended to handle the "normal" difficulties during a quarter (midterms in another class, family event, bad colds). If you have a more extreme situation (e.g., an extended illness or a family emergency) contact ruzzo at uw for accommodations.

Extra Credit

I will provide occasional "extra credit" homework problems. I always set my grade scale before factoring in EC, so they don't just "raise the curve." But OTOH, they will not substantially raise your grade, so you should certainly not do them in lieu of regular homework problems. Attack them for your growth, for curiousity, for the self-satisfaction of conquering them.

Academic Integrity

The goal of our exercises is for you to fully understand and internalize the materials. To that end, we take academic integrity very seriously. We refer violations of departmental policies to the Office of Academic Affairs.

Key insights often emerge in discussion with others; you are allowed (encouraged!) to discuss homework problems with classmates. But, to make sure you really internalize the content while collaborating, you must:

Programming problems must also be coded/written up individually. You may discuss strategy with others (e.g., which data structures you plan to use) and you may help each other debug, but you may not write code while looking at another's code or being coached by anyone else.

If you are confused as to whether or not some collaboration is allowed, ask us before submitting, not after!

Outside Resources

You are encouraged to look beyond official course resources -- alternate explanations help concepts click -- with the following caveats:

Canvas

We will only use Canvas for gradebook syncing (at the end of the quarter). We will not communicate through Canvas -- monitor this website and Ed instead.

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