Final Exam

Answers

Final Exam | Solutions | Code (Eclipse project for testing your answers)

Scores and Graded Exams

How do I find out my score? Like for the midterm, the scores have been released on Gradescope. Log in to Gradescope to see your score.

If you have questions about exactly what points you missed and why, please look over the grade and markings made by the grader, compare it with our answer key and Eclipse project, and then contact your Section Leader if you still have any questions.

How do I pick up my paper exam? A complete scan of your exam is available on Gradescope; we are not distributing paper exams to students. If you would like to see the paper exam, they will be available by appointment only the first week of Fall quarter (September 25 - October 1).

The statistics of the exam scores (out of 180, to the nearest whole number) were as follows:

Mean: 125

Median: 140

Standard Deviation: 47

Here is a histogram of the exam scores (out of 180):

Regrade Policy

We work hard to grade consistently and correctly, but sometimes we make mistakes in grading. If you believe part of your exam was incorrectly graded, please first download the Eclipse project linked to above and run your answer. This is the easiest way to test your code. If, after running your code, you still believe your grade is incorrect, submit a regrade request online using our CS 106A Final Exam Regrade Request form. Regrade requests need to point out the aspect of the problem that was correct, but for which points were taken off. We use a detailed rubric to grade exams, so simply requesting that an incorrect answer "should be worth more points" is not likely to result in additional points. You must also submit your typed Java code for the given problem (if applicable), and any other necessary code/content so that we can run and evaluate your code.

You must provide all the required information listed above and in the regrade request form in order for us to review your regrade request. Also, we reserve the right to re-grade the whole exam to make sure there are no other grading issues present - this may result in a lower total score.

All regrade requests must be submitted by 11:59PM PST on Sunday, October 1, 2017, which is 7 days after the start of the next quarter, Fall Quarter (Fall Quarter starts on September 25).

Practice Materials

Syntax Reference Sheet

Practice Final Exam | Solution | Code

Practice Final Exam 2 | Solution | Code

Sample final exam(s) posted here are intended to be similar to the actual final. The number of problems and type of problems on the actual exam will be relatively similar to what is seen on these practice exams, though we do not promise that it will be exactly the same in length or in difficulty.

Section Handouts and CodeStepByStep lecture practice problems (on the schedule page) are also great ways to practice relevant material.

Logistics

The logistics for the final exam are the same as for the midterm exam (except for the updated syntax reference sheet above); please see the midterm logistics section for more information.

Material Covered

The final focuses on material taught since the time of the midterm, including the following concepts listed below. However, programming is inherently cumulative in that new topics build upon old ones. So you may be asked to solve problems that involve, though not necessarily focus primarily upon, past topics such as strings, int, double, boolean, random numbers, loops, if/else, parameters, return, expressions, variables, constants, file input with Scanner, and so on. Note that you may be asked to read code (look at a piece of existing code and answer questions about it, such as writing its output) and/or write code (write a piece of code such as a method or short program that solves a given problem).

• Pass-by-value vs. pass-by-reference: demonstrate your understanding of objects vs. primitive values (e.g. passing objects, primitives, or arrays as parameters)

• GraphicsPrograms: write Java code to implement a graphics program with certain behavior using Stanford's libraries; this may include drawing shapes such as GRect, GOval, etc., animation, and/or handling mouse events. (Though this topic was covered before the midterm, Breakout, which gave practice with this, was due after the midterm)

• Arrays: interpret/write code that uses a 1D array to solve a problem.

• 2D Arrays: interpret/write code that uses a 2D array (possibly from the pixels of a graphical image, possibly not) to solve a problem.

• Collections: interpret/write code that uses the collections ArrayList and/or HashMap to solve a problem.

• Objects and Classes: interpret/write a class and/or add behavior to an existing class.

• Inheritance: interpret/write a class that extends another class, such as GCanvas.

• Interactors: interpret/write a program that uses GUI components (buttons, labels, text fields) and events to produce a given behavior.

The following concepts will NOT be tested on the final:

• Karel the Robot

• Material from the "Life After CS 106A" lectures

• Graphical shapes not used in lecture/section, such as GArc and GPolygon.

• converting numbers to/from other bases, such as binary or hexadecimal

• do loops and the continue statement (while loops may be needed, though)

• the switch statement

• static methods or data (other than static final constants)

• throwing exceptions with the throw statement

• any Stanford library functionality not explicitly taught in class, section or homeworks

• anything else not explicitly covered in lecture, section or homeworks

Exam Strategies

The recommended exam strategies for the final exam are the same as for the midterm; please see the midterm exam strategies section for more information.