The system for final exam regrades is the same as on the midterm. If you disagree with the grading of a programming problem, such as if you think your solution actually does work, or that your solution is more nearly correct than it was given credit for, you must download our Eclipse code project, which will contain runnable testers for the exam problems. Type your code into the relevant project .java file(s), fixing any trivial syntax problems. Run it for yourself and see how nearly correct your solution is.
If after running the code files you still think your grade is incorrect, submit your exam to the instructor for a regrade. (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. You must also email your .java file(s) for the relevant problem(s) to the instructor so that we can compile and run your code to verify your claim. As part of your cover page, include copy/pasted output from the the test case results, so that we can to verify its correctness.
We will not accept any exam for a regrade unless it includes this cover page, and we will not re-evaluate grading of the correctess of any programming questions without a typed copy of your solution from the .ZIP / .java file being shown to us first.
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. So it is possible that a regrade request will result in you receiving a lower mark than what you started with.
All final exam regrade requests (other than simple score addition errors) must be submitted to the instructor within 7 days of the start of the following quarter (in this case, Autumn 2014).
Same as on the midterm exam (see rules below).
If you want more practice problems, here are links to some past exams given in 106A by other instructors. They don't exactly match the current exam format, so they may be of limited use. Some of the problems on these tests don't match the topics, difficulty level, and/or type of questions we currently plan to ask. Also note that some of these quarters do not match our exam policies such as whether the test is open or closed-book/notes, etc., so any notes about such policies on these exams do not apply this quarter. These links are provided merely as a convenience to help you study.
The actual final exam will have roughly 8-9 total problems. Those problems will be selected from the following categories. For each category, 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, class, or short program that solves a problem about that topic).
ArrayList
and/or HashMap
, and/or write code that uses these collections to solve a problem
GArc
, GPolygon
do/while
loops and the break
or continue
statements (regular while
loops may be needed, though)
switch
statement
You can now check your midterm score online using the instructions in an email that you have already been sent. You will get your midterm paper back in section. If you have questions about exactly what points you missed and why, please get your exam from your SL and look it over, compare it with our answer key, then contact the head TA and instructor if you still have any questions.
Curve: +7 points. Since the scores are a bit lower than our targets, we will add +7 points to everyone's midterm score. Scores are capped at a max of 120/120; for example, if you received a raw score of 115/120, your score curves up to 120/120, not 122/120.
Stats: Here are the raw stats before and after applying the curve:
raw | curved | |
---|---|---|
MEDIAN | 88.5 | 95.5 |
MEAN | 85.1 | 92.0 |
STDEV | 19.9 | 19.7 |
% range | count (curved) | % of class |
---|---|---|
90-100% | 66 | 23.3% |
80-89% | 69 | 26.7% |
70-79% | 57 | 22.1% |
60-69% | 26 | 11.6% |
0-59% | 40 | 16.3% |
Low Grades: Another topic some students ask about is: If their score was lower than they hoped, how much effect will that have on their grade, or what are their options, etc.? Most of the information to answer this can be found on this web site. The course info sheet 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. Also look at our FAQ page for info about pass/fail grading options, drop dates, and other information.
We work hard to grade consistently and correctly, but sometimes we make mistakes in grading. If you disagree with the grading of your exam, 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 the correctness of your solution to a programming question, you must download our Eclipse code project, which will contain runnable testers for the midterm problems. Type your code into the project .cpp file, fixing any trivial syntax problems. Run it for yourself and see how nearly correct your solution is.
If after running the code files you still think your grade is incorrect, 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. You must also email your Midterm14sp.java file and any other necessary files to the instructor so that we can compile and run your code to verify your claim. As part of your cover page, include copy/pasted output from the the test case results, so that we can to verify its correctness.
We will not accept any exam for a regrade unless it includes this cover page, and we will not re-evaluate grading of the correctess of any programming questions without a typed copy of your solution from the .ZIP / .java file being shown to us first.
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. So it is possible that a regrade request will result in you receiving a lower mark than what you started with.
All midterm regrade requests (other than simple score addition errors) must be submitted to the instructor within 7 days of receiving your exam back in section.
If you want more practice problems, here are links to some past exams given in 106A by other instructors. They don't exactly match the current exam format, so they may be of limited use. Some of the problems on these tests don't match the topics, difficulty level, and/or type of questions we currently plan to ask. These links are provided merely as a convenience to help you study.
import
statements in your exam code.
The actual midterm exam will have roughly 7-9 total problems. Those problems will test you on the following concepts. For each category, 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 function or short program that solves a problem about that topic).
for
loops, while
loops, if/else
, etc., evaluate it and write its output/results;
and/or,
write Java code that uses Java control statements to solve a problem.
GRect
, GOval
, etc., animation, and/or handling mouse events.
RandomGenerator
class.
Scanner
to read data from a file in a given format and produce a particular result.
ArrayList
, evaluate it and write its output/results;
and/or,
write Java code that manipulates an the elements of an ArrayList
.
GArc
, GPolygon
do/while
loops and the break
or continue
statements (regular while
loops may be needed, though)
switch
statement
throw
statement
Here is a handout created by a past CS 106A instructor with advice about how to study for, and take, a CS 106A exam.