CSE 142: Computer Programming I,

Dates:

• Midterm: Friday, November 1, 5:30-6:45pm
• Final: Wednesday, December 11, 12:30-2:20pm

Exam Rules and Information:

• You will have an assigned seat and you must sit in that seat. If you arrive for the exam and find someone else in your seat, ask them to move as we will move students to their assigned seats. We will take pictures of the room to help us verify that students sit in their assigned seats (please contact us if you have a concern about this). Students are expected to make a reasonable effort to sit in their assigned seat. Students who demonstrate an egregious disregard for the seating assignments will receive a 5-point penalty (e.g., if a student goes to the wrong room or refuses to move when asked to).
• We will ask to check your UW ID card during the exam so please have it ready.
• We will distribute the exam early and you can read and fill out the cover page of the exam, but you should not look at the exam questions until you are told to begin. At the end when time is called, you are required to stop writing and close your exam. Students who look at the exam before being told to begin and students who make changes to their exam after time is called will receive a 10-point penalty. Students who do not close their exam booklet when time is called may also receive a 10-point penalty. Students that continue to write (anything) on their exam after time is called will receive a 10-point penalty.
• The exam is closed-book and closed-note. You must work alone and may not use any computing devices of any kind including calculators or digital copies of the textbook. Cell phones, music players, smart watches, and other electronic devices may NOT be out during the exam for any reason.
• There will be a cheat sheet included as the last page of the exam. Space will be provided for your answers. If you need additional scratch paper, raise your hand and a TA will give it to you. You are not allowed to use your own paper during the exam.
• Unless a question specifically mentions otherwise, the code you write will be graded purely on external correctness (proper behavior and output) and not on internal correctness (style). So, for example, redundancy or lack of comments will not reduce your score.
• You are allowed to abbreviate "Always", "Never," and "Sometimes" as "A", "N", and "S" for the assertions question. You are also allowed to abbreviate "System.out.print" as "S.o.p" and "System.out.println" as "S.o.pln", but you should otherwise NOT use any abbreviations on the exam.
• You don't need to write any import statements in your exam code.
• You are not allowed to use advanced material to solve exam problems. For the midterm, you are limited to the constructs described in chapters 1 through 5 of the textbook. For the final, you are limited to the constructs described in chapters 1 through 10 of the textbook.
• You are not allowed to use break or continue statements or to have a return from a void method.
• For standard Java classes such as Math and String, you are limited to the methods listed on the cheat sheet. You are not allowed to use the Arrays class or other standard classes. You are also not allowed to use methods that aren't included on the cheat sheet.
• Please be sure that your answer is clearly indicated. This is particularly important if you provide more than one answer or if you have notes in addition to your answer. You can draw a box around the answer you want to have graded and you can draw an "X" through anything that you do not want to have graded. If you provide multiple answers without clearly indicating which to grade, the instructor reserves the right to grade the answer that they deem more intentional, or to choose not to give any credit for your solution.
• You do not need to turn in scratch paper unless you have all or part of an answer on that sheet of paper (you can take the other sheets of paper with you). If you have a sheet of paper with all or part of an answer, please write your name on that sheet of paper, staple it to your test (a stapler will be available), and clearly indicate under the corresponding problem that your answer is attached on an extra sheet of paper.
• Please be quiet during the exam. If you have a question or need assistance, please raise your hand.
• When you have finished the exam, please turn in your exam quietly and leave the room.

After the Final:

• Guide to reading Gradescope scoresheets
• mean: 77.74
• median: 83.0
• final exam key
• regrade policy

Final Resources:

• Pre-final exam reflection (due by 11:59pm on Sunday, December 8)
• sample final
• key to sample final
• final cheat sheet (will be included at end of exam)
• old exam questions
• The TAs will hold an optional review session for the final exam on Monday, December 9 at 4:30pm in GUG 220

Final Content:

The final will cover material from chapters 1 through 10 of the textbook but will not include graphics. You are not allowed to use more advanced material to solve the programming problems. The final will have the following structure:

Note: unlike other programming problems, the Critters problem may be graded partially on proper object-oriented style and design.

After the Midterm:

• Guide to reading Gradescope scoresheets
• Post-midterm reflection (due by 11:59pm on Sunday, November 17)
• mean: 81.54
• median: 85
• standard deviation: 14.43
• midterm key