CSE 142

Course Info

Getting Help

Check Scores

Other

Final: Thursday, August 16, in quiz section AND Friday August 17th, in lecture

Results:

icon Final key

You can now check your final score on MyUW (see instructions). Exams can be picked up from the CSE front desk.

The final average was 73% and was not curved (instead I curved up the overall grades).

Regrades

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

  • Type in the problem(s) to a Java file exactly as it appears on your exam.
  • E-mail Nick a detailed description of why you believe your problem(s) were graded incorrectly. Attach the Java file with your code.
  • Give the exam to the CSE front desk and ask that it be put in Marty Stepp's mailbox.
  • All regrade requests must be received by the second week of fall quarter.
  • We will regrade the entire exam meaning that your exam score may go down as a result of a regrade request (capped at -2).

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 120 minutes to complete the exam. You will receive a deduction if you keep working after the instructor calls for papers.
  • The 120 minutes will be split evenly across two days of testing (60 minutes in quiz section, 60 minutes in lecture).
  • The exam is open-book. 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.

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:
    • Mechanical:
      • array mystery
      • inheritance mystery
      • reference mystery
    • Programming:
      • at least one file processing programming problem
      • at least one array programming problem
      • at least one hard array programming problem
      • Critters programming problem
  • There will be 3 mechanical questions and 5 programming questions:
    • Day 1: 2 mechanical and 2 programming
    • Day 2: 1 methanical and 3 programming
  • The following topics were explicitly not tested on the midterm but are fair game for the final exam:
    • Random objects and generating random numbers
    • boolean variables, parameters, returns, etc.
  • 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)
    • 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, and lose
    • You will not be asked to write an object other than a new type of Critter
    • Inheritance mystery will not include calls to super.methodName
    • interfaces; abstract classes
    • material from Chapter 10 and above

Midterm: Friday July 20th, 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 77.77% and I was shooting for an average of 78%, so there won't be a curve

Here is how the class did (a star represents 1 student). Each number represents students who got that grade and up to 5 points higher. For example, the 85 line represents students who got between 85 and 89 points:

101 *
 95 ********************
 90 ******************
 85 *****************************
 80 ****************
 75 **************
 70 ****
 65 ***************
 60 **********
 55 ******
 50 *****
 45 **
 40 *****
 35 *
 30 
 25 
 20 *
 15 *
 10 
  5 
  0

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

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

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, Color and Random
    • 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)
    • using printf statements
    • 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 60 minutes to complete the exam. You will receive a deduction if you keep working after the instructor calls for papers.
  • The exam is open-book. 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.