Practice-It

Exams

Final: Wednesday June 11th, 12:30 - 2:20pm, in KNE 120, 130

General rules and information:

Preparing for the exam

  • There will be a review session on Tuesday, 6/10 in Guggenheim 220 from 5 - 6:30pm.

Coming to the exam

  • The room your exam is in, and the seat you will sit in is assigned. The seat assignments are:
    • Kane 120 (sections AD, AF-AO, AQ-AR, BM): list, map
    • Kane 130 (sections AA-AC, AE, AP, BA-BL, BN-BO): list, map
  • Have your UW Student ID card out and on your desk, so we can verify your identity if necessary.
  • You may have one 8.5x11 sheet of paper with handwritten notes. This double-sided cheatsheet will be provided as the last page of the exam.
  • There will not be computationally-intensive math problems on the exam. You will not be allow to any computing devices of any kind including calculators or digital copies of the textbook. Don't bring cell phones, music players, and other electronic devices - they may NOT be out during the exam for any reason.
  • If you need a left-handed desk, please fill out this form. (If you took it for the midterm, no need to take it again. The survey will take less than 2 minutes.)

During the exam

  • Write complete code. This means reading the instructions for each question carefully. If the instructions ask you to write a method, you do not need to write a complete Java program.
  • You may assume any necessary import statements are present -- you do not need to write any in your exam code.
  • Your code should compile. Do not omit curly braces or semi-colons, and do not abbreviate any method calls.
  • Unless a question specifically mentions otherwise, your 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.
  • Please be quiet during the exam. If you have a question or need, please raise your hand and a TA or instructor will come to you.
  • You will have 1 hour, 50 minutes to complete the exam. You will receive a 10-point deduction if you keep working after the instructor calls time.
  • Corrections or clarifications to the exam will be written at the front of each of the rooms.
  • Work on your own. If you violate the University Code of Conduct during the exam, you may receive a 0% for the exam and possibly further punishment.

After you finish

  • When you have finished the exam, please turn in your exam quietly and leave the room.
  • If you finish with less than 5 minutes remaining, please sit quietly so as to not distract other students who are trying to finish the exam
  • If you enter the room, you must turn in an exam paper and will not be permitted to leave the room without doing so.

Topics

Material from Chapters 1-9 and the lectures is considered "fair game" for questions on the final. The exam will focus on material from the second half of the course, though it is likely that you will use knowledge you learned in the first half as well.

The following topics are guaranteed to not be on the final exam.

  • converting between decimal (base-10) and binary (base-2) numbers
  • classes DrawingPanel, Graphics, and Color
  • exceptions
  • do/while loops and the break statement (regular while loops may be needed, though)
  • the Java assert statement (not the same as logical assertions, which WILL be tested)
  • preconditions and postconditions
  • null
  • multidimensional arrays
  • the Object class; implementing an equals method; the instanceof keyword
  • classes with static fields / methods
  • the advanced Husky-only methods of Critters, such as getX, getNeighbor, win, lose, and mate
  • interfaces; abstract classes
  • material from Chapter 10 and above

Practice Finals:

Sample final exams posted here are intended to be very similar to the actual final. The number of problems and type of problems on the actual exam will be much like what is seen on these practice exams.

Midterm: Friday May 9th, 5pm - 6pm, in KNE 110 and 120, and GUG 220

Results:

icon Miderm key

You can now check your midterm score on MyUW (see instructions). The exam had a mean of 78.1 and a median of 81.

Your exam will be returned to you in section on Thursday. Please wait to receive your exam before asking grading questions.

Regrades:

If your exam score was simply added up incorrectly, take it to your TA and they'll fix it for you.

If you believe that one or more programming problem was incorrectly graded and you would like us to regrade it, you must:

  • Type in the problem(s) to a Java file exactly as it appears on your exam.
  • E-mail the instructors a detailed description of why you believe your problem(s) were graded incorrectly, including testing that you've done to show that it works, or mostly works. Attach the Java file(s) with your code.
  • You have one week to submit regrade requests -- we must receive your request by Thursday, May 22nd.
  • We will regrade your entire exam, meaning that your exam score may go down as a result of a regrade request.

General rules and information:

Preparing for the exam

  • There will be a review session on Wednesday, May 7 at 5:30pm in Bagley 131.
  • There will be no lecture, but the instructors and TAs will be present in class on Friday for an optional office hour. Come and ask questions, or use the time to study on your own.

Coming to the exam

  • The room your exam is in, and the seat you will sit in is assigned. The seat assignments are:
    • Kane 110 (sections AA-AE, AP, AQ, BB, BH, BK): list, map
    • Kane 120 (sections AF-AO, AR, BM): list, map
    • Guggenheim 220 (sections BA, BC-BG, BI, BJ, BL, BN, BO): list, map
  • Have your UW Student ID card out and on your desk, so we can verify your identity if necessary.
  • You may have one 8.5x11 sheet of paper with handwritten notes. This cheat sheet will also be available, as the last page of the exam.
  • There will not be computationally-intensive math problems on the exam. You will not be allow to any computing devices of any kind including calculators or digital copies of the textbook. Don't bring cell phones, music players, and other electronic devices - they may NOT be out during the exam for any reason.
  • If you need a left-handed desk, please fill out this form by 12pm May 3rd. (The survey will take less than 2 minutes.)

During the exam

  • Write complete code. This means reading the instructions for each question carefully. If the instructions ask you to write a method, you do not need to write a complete Java program.
  • You may assume any necessary import statements are present -- you do not need to write any in your exam code.
  • Your code should compile. Do not omit curly braces or semi-colons, and do not abbreviate any method calls.
  • Unless a question specifically mentions otherwise, your 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.
  • Please be quiet during the exam. If you have a question or need, please raise your hand and a TA or instructor will come to you.
  • You will have 60 minutes to complete the exam. You will receive a 10-point deduction if you keep working after the instructor calls time.
  • Corrections or clarifications to the exam will be written at the front of each of the rooms.
  • Work on your own. If you violate the University Code of Conduct during the exam, you may receive a 0% for the exam and possibly further punishment.

After you finish

  • When you have finished the exam, please turn in your exam quietly and leave the room.
  • If you enter the room, you must turn in an exam paper and will not be permitted to leave the room without doing so.

Topics

Material from Chapters 1-5 and the lectures is considered "fair game" for questions on the midterm.

However, the following topics are guaranteed NOT to be tested on the midterm in any form:

  • converting between decimal (base-10) and binary (base-2) numbers
  • classes DrawingPanel, Graphics, and Color
  • exceptions
  • do/while loops and the break statement (regular while loops WILL be tested)
  • the Java assert statement (not the same as logical assertions, which WILL be tested)
  • material from Chapter 6 and above (file I/O, etc.)

Practice Midterms:

Sample midterm exams posted here are intended to be very similar to the actual midterm. The number of problems and type of problems on the actual exam will be much like what is seen on these practice exams.