As a reminder, the midterm will consist of two parts (50 minutes for a 'written' Canvas portion on the first day Tuesday 9/25 and 50 minutes for a programming coding portion Thursday 9/27). You are encouraged to study all previous activities and labs, textbook chapters and reading quizzes, and programming assignments. Materials here are presented for you to help prepare for the exam(they are not a study guide for exact format, but as an aide to prepare for the exam). The solutions will NOT be posted, but you may ask questions about individual items on these via Piazza or in class.

 Sample Written Exam (Fall 2015)

 Sample Coding Exam (Fall 2015)     test1.in     test1.exp     test2.in     test2.exp

Written Exam

Objectives

Students will be able to...

• Recognize vocabulary/concepts from Ch1-4.
• Declare and assign variables and constants.
• Evaluate arithmetic expressions (type and value).
• Define and invoke methods with parameters.
• Predict the output of programs with 2+ methods.
• Write methods that require I/O and arithmetic.

Logistics

• This is a closed-book, closed-notes, no-calculator exam. Do not refer to any materials other than the exam itself.

• Do not look at anyone else's exam. Do not talk to anyone but the instructor during the exam. Turn off all cell phones, etc.

• Use the restroom and take care of personal needs before you arrive. If you need to leave during the exam, ask for permission.

Coding Exam

Objectives

Students will be able to...

• Meet any objectives from PA1 and PA2.
• Perform integer division and modulo.
• Invoke methods from the Math class.

Logistics

• You must use a Linux lab machine and log in with the generic student account. It's strongly recommended that you practice the sample exam in the lab so there will be no surprises on exam day.

• During the exam, you may only use the provided reference sheet.  No other website, the book or outside material may be consulted.

• You may only run the following programs: JGrasp, DrJava (or other simple text editor), a terminal, meld (or other diff tool), and a web browser. All windows should be arranged so that the instructor can see what you're doing(no use of Eclipse on this exam).

• The use of any pre-existing code (other than that provided as part of the exam), other documents/pages/sites, and/or other programs will be considered a violation of the Honor Code(no googleing of code).

• At the end of the exam, you will submit your code via Autolab. You may not use Canvas for any other purpose (e.g., looking at sample solutions to prior labs) during the exam.

Video Tutorial