Δ CSE Home Δ About Us Δ Search Δ Contact Info

CSE 142

Coursework

Getting Help

Check Your Scores

Other

Exams

Final Exam:

Solution Key:

Regrade and Exam Pick-up Procedure:

If you want to pick up your final exam, you can do so by going to the front desk of the CSE building starting Monday Mar 24. The exams will still be there in Spring quarter if you want to pick yours up after break. If you want a regrade, type in the relevant problem(s) into one of our FinalTesterX.java programs above, capture the output, and bring it to Marty as with the midterm. You can slide it under his office door in CSE room 466. Marty will accept 142 final exam regrades through the end of the first week of Spring 08 quarter.

Score Stats:

Q1    Q2    Q3    Q4    Q5    Q6    Q7    Q8    QX    Average  Median  StDev
7.5   8.9   12.5  10.8  6.8   4.1   6.0   4.0   0.9   61.6     64      19.3
  • Place: GUG 220
  • Date/Time: Wednesday, March 19, 2008
    • 10:30am - 12:20pm (Section A, the 9:30 lecture)
    • 12:30pm - 2:20pm (Section B, the 11:30 lecture)

Sample Exams: (answer keys included)

I strongly suggest that you try to solve all of these problems yourself, on paper, without a computer, and without looking at the answer key until you're done.

  • Sample final exams posted here are intended to be very similar to the actual final exam. The number of problems and type of problems on the actual exam will be much like what is seen on these practice exams. Material from Chapters 1-9 is considered "fair game" for questions on the actual final.
  • The following topics are guaranteed NOT to be explicitly tested on the final exam:
    • DrawingPanel, Graphics
    • do/while loops, break statement
    • System.out.printf
    • the Java assert statement
    • exceptions and try/catch statements
    • preconditions and postconditions
    • null
    • arrays of objects
    • multidimensional arrays
    • the Object class; implementing an equals method
    • classes with static fields / methods
    • interfaces
    • material from Chapter 10 and above

Midterm Exam:

Date/Time:

  • Friday, February 15, in class

Curve:

  • We decided to add +5 points to everyone's midterm score. This won't show up on MyUW, but you can consider your score to be +5 higher than you see on your test paper.

Solution Key:

Regrade Policy:

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

If you disagree with the grading, such as if you think your solution actually does work, or that your solution is more nearly correct than it was given credit for, the procedure for regrades is the following:

  • If your complaint is about a programming question (#5 or #6), type in your code into our MidtermTester.java above. Fix any trivial syntax problems. Run it for yourself and see how nearly correct your solution is.
  • Submit your exam to Marty for a regrade. (Either give it to him in lecture, go to his office hours, or slide it under his office door.) You must include a cover page with a brief written explanation of what specifically you think was misgraded and why, along with printout of your typed-in code and its output from the MidtermTester.java if appropriate. Marty will not accept any exam for a regrade unless it includes this cover page, and he will not re-evaluate any programming questions without their being typed into the MidtermTester.java by you first.
  • NOTE: When you submit an exam for a regrade, Marty will regrade your entire exam. If he notices anywhere that you were mistakenly given too many points, he will also correct this, up to a maximum of -2 for the entire exam. So it is possible that a regrade request will result in you receiving a slightly lower mark than what you started with.
  • All midterm regrade requests (other than simple score addition errors) must be submitted to Marty by Friday, February 29.

Sample Exams:

I strongly suggest that you try to solve all of these problems yourself, on paper, without a computer, and without looking at the answer key until you're done.

  • 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. Material from Chapters 1-5 is considered "fair game" for questions on the actual midterm.
  • The following topics are guaranteed NOT to be tested on the midterm in any form:
    • DrawingPanel, Graphics, Color
    • do/while loops, break statement
    • System.out.printf
    • the Java assert statement (not the same as logical assertions, which WILL be tested)
    • exceptions
    • preconditions and postconditions
    • material from Chapter 6 and above (file I/O, etc.)

Rules and Information

  • You have 50 minutes to complete the exam. You may receive a deduction if you keep working after the instructor calls for papers.
  • You must show your UW Student ID card to a TA or the instructor for your submitted exam to be accepted.
  • The exam is open-book/notes. You must work alone and may not use any computing devices of any kind including calculators. Cell phones, music players, and other electronic devices may NOT be out during the exam for any reason.
  • Your code you write will be graded purely on external correctness (proper behavior and output) and not on internal correctness (style).
  • You don't need to write any import statements in your exam code.
  • Do not abbreviate any code on your exam, such as writing S.o.p for System.out.println.
  • Please be quiet during the exam. If you have a question or need, please raise your hand.
  • Corrections or clarifications to the exam will be written at the front of the room.
  • If you violate the University Code of Conduct during the exam, you may receive a 0% for the exam and possibly further punishment.
  • 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.