CSE 142

Course Info

Getting Help

Check Scores

Other

Exams

Final Exam:

  • Date: Wednesday, June 8, 2011
  • Time:
    • for the   9:30am "A" lecture: 10:30am - 12:20pm
    • for the 11:30am "B" lecture: 12:30pm -   2:20pm
  • Place: Kane 120 (please note that this is NOT our normal lecture room)

Sample Exams: (answer keys included)

We 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:
    • converting between decimal (base-10) and binary (base-2) numbers
    • classes DrawingPanel and Graphics
    • do/while loops and the break statement (regular while loops may be needed, though)
    • the Java assert statement
    • exceptions and try/catch statements
    • preconditions and postconditions
    • null
    • multidimensional arrays
    • the Object class; implementing an equals method; the instanceof keyword
    • interfaces; abstract classes
    • material from Chapter 10 and above

Midterm Exam

Scores, Curve, and Other Information:

You can now check your midterm score on MyUW. If you don't see your midterm score on your MyUW page, follow our MyUW directions.

The median score was around 79. There will be a +4 point curve added to each student's score. (But curved scores are capped at a max of 100.)

A topic students frequently ask about is: If their score was lower than they hoped, they want to ask about how much effect that will have on their grade, or what their options are, etc. The course syllabus lists the relative grading weight of homework vs. midterm vs. final exam, so you can use that to compute the rough effect on your grade of a particular midterm score. You may want to use the Grade-a-nator page to help you compute your approximate grade. Also look at our FAQ page for info about S/NS grading options, drop dates, and other information.

Regrade Policy:

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:

  • Submit your exam to the instructor for a regrade. (Either give it to us in lecture, go to our office hours, or slide it under our office doors.) You must include a cover page with a brief written explanation of what specifically you think was misgraded and why.
  • Also note: When you submit an exam for a regrade, we will regrade your entire exam. If we notice anywhere that you were mistakenly given too many points, we will also correct this, up to a maximum penalty of -2 for the entire exam. So it is possible (though unlikely) 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 by Monday, May 23, 2011.

Time/Place:

  • Date: Friday, May 6, 2011
  • Time: in lecture, 50 minutes
  • Place: in class

Practice Exams:

  • 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 and the lectures 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:
    • converting between decimal (base-10) and binary (base-2) numbers
    • classes DrawingPanel, Graphics, and Color
    • the Point class
    • printf
    • exceptions
    • preconditions and postconditions
    • 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.)

Rules and Information:

  • You must show your UW Student ID card to a TA or the instructor for your submitted exam to be accepted.
  • You will have 50 minutes to complete the exam. You may receive a deduction if you keep working after the instructor calls for papers.
  • The exam is closed-book and closed-notes, although each student will be allowed to bring to the exam a single index card with hand-written notes (no larger than 5" by 8"). 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.
  • 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.
  • You don't need to write any import statements in your exam code.
  • On the exam it will be allowed to abbreviate S.o.p for System.out.print and S.o.pln for System.out.println. Otherwise do not abbreviate any code on the exam.
  • 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.