Please make sure you've reviewed the following policies:
Note: unless otherwise noted, all assessments are due at 11:59pm PT PT. If you have trouble submitting an assessment and the deadline is approaching, you should email all the files to the instructors and your TA before the deadline so we have your submission on record. Submissions received after the due date may not be accepted even if there were technical difficulties turning in the assessment if you did not email us your solution before the cutoff.
All assessments will be submitted and graded via Ed.
Initial submission due Monday, August 15, 11:59pm PT
Initial submission due Tuesday, August 9, 11:59pm PT
Initial submission due Tuesday, August 2, 11:59pm PT
Initial submission due Tuesday, July 26, 11:59pm PT
Initial submission due Tuesday, July 19, 11:59pm PT
Initial submission due Tuesday, July 12, 11:59pm PT
Initial submission due Wednesday, July 6, 11:59pm PT
Initial submission due Wed, June 29, 11:59pm PT
Once per week, you may revise and resubmit a previous take-home assessment to demonstrate improved mastery. Your resubmission will be graded and the new grades will fully replace your previous grades. (Note that this means your grades may go down.) See the full policy in the syllabus for more details.
While feedback from your previous submissions is an important starting point for improving your work, addressing the feedback you receive does not guarantee any particular result on your resubmission. We will make every effort to provide feedback on all areas that could be improved, but oversights may occur. In addition, changes to address one area of feedback may introduce new errors or concerns in other areas. It is your responsibility to ensure that your work meets all expectations. Be sure to consult not only your feedback, but also the assignment specification, code quality guide, and other course resources and materials.
To resubmit a revised assessment, follow these steps:
You must complete both steps for your resubmission to be considered complete. Resubmissions in Ed in will not be graded unless the Google Form is also filled out correctly. If you are having difficulty accessing the Google Form, try following these instructions.
The resubmission period for each week runs from Saturday to Friday. Resubmissions must be received by Friday at 11:59pm PT to be considered for that week. You may only make one resubmission per week, though you may change which submission or which assessment you are resubmitting throughout the week by modifying your responses in the Google Form. Resubmissions received each week will be graded and feedback released by the following Friday.
Each week you will have a short Checkpoint assessment assigned on Ed. These are intended to give you more immediate practice with the content covered in class that week outside of the larger, more time-consuming Take-Home Assessments. Checkpoints will generally be released on Wednesdays and due on Saturdays, and may be worked on collaboratively with classmates.
Checkpoints may be submitted late by utilizing a late checkpoint token and completing the checkpoint in Ed as normal. Late checkpoint tokens may be obtained by reading or watching an article/video discussing some current events or issues related to computer science and filling out the Late Checkpoint Token form with a link to the source and a brief summary of the article and what you found interesting or compelling.
Culminating assessments are designed to give you an opportunity to engage with all the material covered during course up to the time of the assessment. Unlike take-home assessments, which primarily emphasize the most recent concepts, culminating assessments give similar levels of focus to all topics.
Details on culminating assessments will be released later on in the quarter.
While culminating assessments will include solving problems, and may have the look and feel of an exam, they are not graded on correctness or accuracy. Your grade on a culminating assessment is based only on your completion of the required elements (outlined below). Culminating assessment are graded SN—no grades of E or U will be given.
The first culminating assessment will be a simulated midterm. This assessment will look similar to a traditional CSE 142 midterm exam, but you will not be graded on the accuracy of your answers. Instead, you will be asked to compare your responses to a published key, annotate your answers to indicate areas you made mistakes, and meet with your TA to discuss your work.
The simulated midterm will be conducted in Ed, and will consist of a series of problems of two types: mechanical problems where you answer questions about or predict the results of executing provided code; and programming problems where you write code to satisfy a given prompt. The assessment will also include a "cheat sheet" of notes that may be helpful in completing these problems.
To best simulate the circumstances of a traditional midterm, we recommend adhering to the following procedures:
These procedures will help to create a reasonable simulation of a traditional midterm and to provide the most accurate indication of your current level of mastery. They are highly recommended, but are not strictly required, and you will not be penalized for failing to follow these procedures. However, the further you stray from these suggestions (e.g. by utilizing outside resources), the less useful your performance will be in helping both you and the course staff evaluate your current mastery and provide meaningful support going forward.
To receive an S grade on the simulated midterm, you must complete the following three steps:
After you have completed and annotated your simulated midterm, you will attend a 15-minute, one-on-one session with your TA to discuss your progress in the class. (Your individual TA will tell you how they will schedule your session.) In this session, you may go over some of the problems on the assessment and discuss both how you could have improved your work on those problems and how you can improve your mastery of the material going forward, you may discuss your current grades in the class and work to understand how they affect the final course grade you will receive at the end of the quarter, and/or you may spend time discussing how you've been engaging in the class for the first half of the quarter and considering how you should continue engaging in the course moving forward. You should come to your meeting with a plan for what you would like to discuss and/or specific questions you would like answered. Note that, in the 15-minute meeting, you will likely not have time to review every problem on the assessment. Be sure to decide ahead of time what problems, concepts, or topics you would most benefit from discussing.
Note that missing your scheduled meeting with your TA without notice will result in a grade of N on the simulated midterm. If extenuating circumstances cause you to need to reschedule your meeting, you must contact your TA ahead of time to do so.
You can view an alternate form of this information on this notion page.
The second culminating assessment will be a video problem solving portfolio. For this assessment, you will work on a few problems similar to those that might have appeared on a traditional CSE 142 final exam. However, rather than simply submit your solutions to these problems, you will create videos to teach someone else how to solve them!
We will release a pool of programming problems in Ed for you to choose from in creating your portfolio. From this pool, you will select two (2) problems to solve and explain. For each problem you chose, you will create a three- to five-minute video walking through your problem-solving approach and explaining your solution. You can think of these videos as shorter versions of the walkthrough videos your TAs have been creating for section problems throughout the quarter.
Your videos should include your voice (and, if possible, face) explaning your solution to the problems you choose. Videos must also include some way of showing your code–this could be a screen-recording, whiteboard, tablet, or any other material that works for you. The format is not important; what matters is that you are able to effectively explain your approach and show your work. Your videos do not need to include an explanation of the problem itself, but should mention details as they become relevant to your solution. Your videos do not need to be perfectly edited or narrated–we are more interested in the work that you've done to solve the problems rather than the production quality! (See the sample videos for examples.)
As on the simulated midterm, you will not be graded on the correctness of your solutions. However, your work must demonstrate a good-faith effort to solve the problems to the best of your ability. If there are aspects of the problems you struggle with, you should call those out in your video. (Explanations of errors or areas of struggle are very effective teaching tools!)
You can use any technology you have available to create your videos. There are no minimum quality requirements, but both the video and audio should be clear enough to understand what you are saying and doing. (We highly recommend Loom as a simple, easy way to create videos that include screen recordings, voiceovers, and optionally video. Zoom should also be capable of creating recordings.) As mentioned above, you will need to include audio, and you are encouraged, but not required, to include video as well. If you do not have access to technology capable of creating a video that meets the requirements, or if you are in a living situation that makes recording video infeasible, please contact the course staff immediately to make arrangements. The UW Student Technology Loan Program may also be able to help.
To receive an S grade on the problem solving portfolio, you must submit video walkthroughs of two (2) problems chosen from the pool provided in Ed. Videos must meet the following requirements:
You do not need to "live-code" your solution in your video–in fact, you will likely find it easier to have your work already complete and simply explain what you have written. You do not need to fully script your video in advance (though you may if you prefer), but you will likely find it helpful to think about what you will say ahead of time and have a plan. You do not need to worry about creating "professional" quality productions–it's fine to stumble over your words a bit or back up if you make a mistake in your explanation. You also do not need to do any editing or post-processing on your videos.
The pool of available problems will be released in Ed on Friday, August 5. It will be Ed Lesson tab under Culminating Assessments named Culminating Assessment 2 Problem Solving Portfolio. Videos must be submitted by 11:59pm PT on Wednesday, August 17.