Syllabus

Course Goals

CSE 417 is a non-major student's introduction to algorithms. By the end of this course, you will be able to: Communication is a key aspect of this course. It is not enough to write code that works, you will also need to convince others that your code will work!

The Pandemic Reality

We are still in the middle of a health emergency! The course is being offered in a new format. We intend to stick to this syllabus as closely as possible. If we do make changes, it will always be to your benefit. We may propose changes if there are significant changes to the public health situation. In return, we ask that you do not suffer in silence. If unforeseen circumstances arise during the quarter, you should let us know. The sooner we are made aware, the more options we will have for designing accommodations.

If you have ideas to improve the course, you can send us anonymous feedback. Please note, however, that we cannot respond to you via the anonymous feedback form.

Assessment

This quarter we are offering the course in a format loosely based off of mastery grading. The goals of this mode are three-fold:
  1. The concepts in an algorithms course often take a little bit of time to click, and are somewhat independent. We care more about whether you understand a topic by the end of the quarter than in the middle. We hope the format will allow you to return to questions and topics you missed the first time.
  2. We hope to give you some flexibility in which problems you do, allowing you to focus on the aspects of the course that are more important to you.
  3. Despite our return to in-person classes, we are still in a pandemic; this format is more flexible to emergencies (either individual or university-wide)
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) Main idea and edge cases are all correct. Would have gotten full credit (or extremely close) with points-based grading.
Satisfactory (S) Main idea is correct, but some edge cases or follow-up questions are wrong or missing. Would have gotten about 80-90% on points-based grading.
Not Satisfactory (N) Some important error is made, but substantial progress toward a solution. Would have gotten above 50% on points-based grading.
Ungradable (U) Directions not followed (e.g., used a library or approach that isn’t permitted) or otherwise shows no substantial progress.

The main goal with this grading system is to change the focus (and time investment) of grading -- instead of spending significant time focusing on differentiating 1 point mistakes from 2 point mistakes, TAs can spend time generating helpful feedback, and then spend some additional time on grading resubmissions.

We will release 8 homeworks during the quarter. The assignments will often have more problems on them than we expect you to answer, allowing you to choose which fits better with your interests.

Problem Types

There are two types of problems on homeworks: mechanical and long-form.

Mechanical problems usually ask you to execute an algorithm or give short answers, like an input that causes bad-behavior. These problems are usually shorter and require a surface-level understanding of what was discussed in lectures.

Long-form problems generally involve designing an algorithm -- either by-hand (in pseudocode) or in actual code. Long-form problems also might ask you to consider real-world effects of using algorithms or to prove facts about algorithms. These problems usually require applying the contents of lectures to new scenarios.

Logistics

On the day a homework is due, the gradescope submission boxes will close (except for the coding problems). The TAs will grade every problem you submit. Until the deadline, you are free to submit any number of problems on the assignment. Each homework will have the maximum number of problems that count -- we will give you the highest scores among your submissions in those categories. Starting with homework 2, we will give you a chance to resubmit a problem from an earlier homework (whether you initially submitted that problem or not). We will add that score to the appropriate category on the homework on which the problem originally appeared. If you already submitted that problem, we will count the higher of the scores between your submissions.

For example, if on homework 1, you got Es on the two long-form problems and then submit a new problem from HW1 long-form problem with HW3 that gets an E, you will then have 3 Es on long-form problems on homework 1.

If on homework 1, you got one E and two S on long-form problems and then resubmit a problem scored S with HW3 and it gets an E, then your score for homework 1 long-form problems will be 2 E's and 1 S.

If on homework 1, you got one E and two S on long-form problems and then resubmit the problem scored S with HW3 and it gets an N, then your score for homework 1 long-form problems will still be 1 E and 2 S's (i.e., your grade cannot go down from resubmission).

The gradescope submission boxes for all coding questions will close with the due date of the last homework assignment. Since we don't have to grade these by hand, you can submit these assignments whenever you'd like during the quarter (though we strongly recommend you remain on pace throughout the quarter). For coding questions, your score is based on:

  1. the tests in gradescope
  2. following any problem specific directions (e.g., if we say you cannot use recursion then your final code cannot use recursion).
If you violate point 2, your score for the problem will be a U. Otherwise, your score will be calculated as follows:
Score requirement
E all tests pass.
S at least 80% of the points from tests on gradescope.
N at least 50% of the points from tests on gradescope.

We do not have hidden tests (other than manually verifying the problem-specific directions.

We will verify requirement 2 for all problems at the end of the quarter -- the directions should leave no ambiguity as to whether you are following them or not; please ask us during the quarter for clarification if you aren't sure whether you're violating one.

Grade Guarantees

We will have these minimum guarantees when we convert from course submissions to final grades. That is, if you meet the conditions in the table, your final grade can be no lower than the grade shown in that row.
Grade Mechanical Problems Long-Form Problems
3.5 6E and 1S 18E and 4S
3.0 5E and 1S 14E and 3S
2.5 4E and 1S 8E and 8S
2.0 2E and 2S 6E and 7S
0.7 none 10S, with at least one on five different HWs.

To meet the guarantee you must meet every requirement in the list. So, for example, if you never submit a mechanical problem, you could only meet the 0.7 guarantee.

In the chart “extra” E grades count as S grades. So if you have 22 E grades on long form problems, you meet the long-form requirement for a 3.5.

You must meet every requirement to get the grade guarantee, but when we interpolate we'll focus on the long-form problems (for example, if you have only 7 E grades for mechanical problems, but you have 24 E grades for long-form problems, you don't have a guarantee of a 3.5 from the chart, but you would end up with a grade of 3.5 or above, since you were well above the requirement for long-form problems).

We will use the full 4.0 grade scale (it is possible to get a 3.7 or 3.3, for example, even though those rows aren't in the table). We will interpolate between the grade breaks, with a focus on the long-form problems.

Lecture Activities

In lecture, we will ask you to respond to polling questions. These activities are not graded -- they help you catch common misconceptions, and help me adjust how fast I'm going during lecture, but do not affect your grade.

Academic Integrity

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

Collaboration

You are allowed (and encouraged!) to discuss homework problems with other students. With algorithms problems, it's very common to need one or two key insights that are much easier to discover talking out loud with others. But, to make sure you are learning the content while collaborating, we require that you: Programming problems must also be written up individually. That means you may discuss plans 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 student's code. If you are confused as to whether or not some collaboration is allowed, ask us! No set of rules will be completely exhaustive. If something weird happens, please tell us too! We will not penalize you if you tell us about it before turning in the assignment.

Resources Outside of CSE 417

You are strongly encouraged to seek out resources beyond official course resources -- very often it takes two or three different explanations for a concept to click, so finding different explanations is a good thing -- with the following caveats:

Scenarios

What happened? Is it a violation?
When searching for general information, you accidentally find the exact question we asked. You tell the staff, and provide a link to what you found. Not a violation!
We’ll say “thanks for letting us know!” and make sure you didn't plagiarize. There won’t be a penalty but only a warm, fuzzy feeling.
You and a friend separately write up solutions, then compare. Your friend suggests that your conclusion is a little unclear. You formulate a new conclusion on the Zoom call together. Violation!
That is no longer your individual writeup.
You and a friend separately write up solutions, then compare. Your friend suggests that your algorithm runs in time O(m+n) not O(m^2). You wait 30 minutes, then return to your writeup, decide your friend was right, and update your writeup. Not a violation!
Bug fixes and minor rewordings done by you at another's suggestion are fine. The writeup is still substantially yours.
You find a textbook with sample solutions to similar problems. You see that they like to introduce variables with “Consider” and use “hence” instead of “because.” You copy these words, because they seem cooler. Not a violation!
Single words or stock phrases are things you can learn from. It is not a violation to emulate style (but "hence" is a little archaic).

Late Policy

Since we allow for resubmissions of one problem every week and arbitrary submissions for coding problems, we do not have late days. We have separate submission boxes for every problem, so you are encouraged to turn in problems as you finish them (rather than turning them all in at once). Resubmissions are intended to handle the "normal" difficulties during a quarter (midterms in another class, family birthday party to attend, bad colds). If you have a more extreme situation (e.g., an extended illness or a family emergency) contact Robbie (via email or Ed post) for accommodations.

Course Tools

Zoom

While we hope to run the course primarily in-person, some office hours will be held online. If we have a synchronous lecture as part of our contingency plans, we will use zoom. Zoom meetings will be restricted to accounts logged in with @uw.edu email addresses. If you have trouble joining a meeting, make sure you choose the "Sign in with SSO" option.

Ed

Ed is our discussion board and the right place to ask any questions about the course. It works like Piazza, but Piazza is moving to an ad-supported model, so we paid for an alternative. We will happily answer questions from lecture or about general concepts. We also will answer clarifications about homework (e.g. correcting typos). You are most encouraged to answer each other’s questions on the message board as well. If you have a question that might reveal your approach to a homework problem, you must ask the question privately. For accommodations and other private questions, you can ask privately on Ed or email the instructor directly. Only you and the course staff can see a private question on Ed.

Gradescope

Gradescope is the tool to turn in completed assignments. After grading, you can also find our feedback there and submit regrade requests if needed. You will get an automatic email with account setup instructions before HW1 is due.

Canvas

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

Java

Homeworks frequently contain a small programming portion. Because this course assumes knowledge from CSE 373, these programming questions are given in Java. If you do not already have Java from prior quarters, you can grab it from AdoptOpenJDK. We expect any JDK above 8 would work.

Accommodations

If you have, or think you may have, a temporary health condition or permanent disability, contact to get started with accommodations. Accommodations for faith or conscience reasons must be requested within the first two weeks using the Registrar’s request form. The UW’s religious accommodations policy is available here. Your performance in this course should not be affected by circumstances beyond your control. We can still work with you for situations other than the university-wide accommodations. If anything does come up, you should contact the course staff( as early as you can.
1. Some CSE instructors have previously recommended watching an episode of Gilligan’s Island for that break, but Gilligan’s Island isn’t on Netflix. Robbie recommends The Office. [go back]