CSE 142

Course Info

Getting Help

Check Scores

Other

Final: Wednesday, June 12, 2013 in 10:30 - 12:20

Lecture A: KNE 130

Lecture B: KNE 120

Results:

icon Final key

You can now check your final exam score on MyUW (see instructions). Please pick up your exam from the CSE reception before asking grading questions. The reception is open 9am-5pm daily with a lunch break 12pm-1pm.

The average was around 68% and the median around 72%. A shift of +5 points up to a maximum of 100 out of 100 will be applied to everyone's score. Note that this shift does NOT appear on MyUW but will be used in final grade calculations.

Regrades

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

  • Type in the problem(s) to a Java file exactly as it appears on your exam.
  • E-mail Allison a detailed description of why you believe your problem(s) were graded incorrectly. Attach the Java file with your code.
  • Give Allison your original final either in person or slide it under her door in CSE340.
  • All regrade requests must be received by Wednesday, July 3 at 5pm.
  • Allison will regrade your entire exam meaning that your exam score may go down as a result of a regrade request.

Final Rules and Information:

Cheat sheet draft

  • You must show your UW Student ID card to a TA or the instructor for your submitted exam to be accepted.
  • You will have 110 minutes to complete the exam. You will receive a deduction if your test booklet is open after the instructor calls for papers.
  • The exam is open-book to the course textbook only. 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, and other electronic devices may NOT be out during the exam for any reason.
  • You may not bring in notes or scratch paper.
  • 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. No one may leave before 60 minutes have passed.

Sample exams

Many of the sample exams below are also found on Practice-It

  • Sample final exams posted here are intended to be very similar to the actual final exam. Material from chapters 1-9 is considered "fair game"
  • Your exam may vary somewhat from the samples provided but is guaranteed to have the following problems:
    • expressions
    • array mystery
    • inheritance mystery
    • reference mystery
    • at least one file processing programming problem
    • at least one array programming problem
    • Critters programming problem
  • 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
    • the Java assert statement
    • 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

Midterm: Friday May 10th, in lecture

Results:

icon Miderm key

You can now check your midterm score on MyUW (see instructions). Your exam will be returned to you in section on Thursday. Please wait to receive your exam before asking grading questions.

The midterm average was around 69% which is a little low. Therefore we have raised everyone's score +7 points (capped at 100).

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 Allison to regrade it, you must:

  • Type in the problem(s) to a Java file exactly as it appears on your exam.
  • E-mail Allison a detailed description of why you believe your problem(s) were graded incorrectly. Attach the Java file with your code.
  • Give Allison your original midterm either in person or slide it under her door in CSE340.
  • All regrade requests must be received by Friday, May 24th.
  • Allison will regrade your entire exam meaning that your exam score may go down as a result of a regrade request.

icon cheat sheet (will be provided as last page of exam)

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. 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
    • 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.)

Midterm 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 10-point deduction if you keep working after the instructor calls for papers. You may not leave the room until 35 minutes have passed.
  • The exam is open-book to the textbook only. 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, 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.