Exam logistics and preparation

As a reminder, the midterm will consist of two parts (50 minutes each): a written exam on Tuesday, and a coding exam on Thursday. You are encouraged to study all previous activities and labs, textbook chapters and reading quizzes, and programming assignments. Please use the following materials as prep for the exams.

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

Video walkthrough from Dr. Mayfield for this example

If you have questions about the material - post in Piazza under exam1 heading.

-------------------------------------------------------------------------

Written Exam

Objectives

Students will be able to...

Recognize vocabulary/concepts from Ch1-4.
Declare and assign variables and constants.
Define and invoke methods with parameters.
Evaluate arithmetic expressions (type and value).
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 modulus.
Invoke methods from the Math class.

Logistics

You must use a Linux lab machine and log in with your JMU account (not student). It's strongly recommended that you practice the sample exam in the lab so there will be no surprises on Friday.
During the exam, you may access materials on the course website including prior activities, lab instructions, and the textbook. However, you may not watch any of the videos or click on links to external websites.
You may only run the following programs: JGrasp/DrJava (or other simple editor - no Eclipse), 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.
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.
At the end of the exam, you will submit your code via Webcat. You may not use Canvas for any other purpose (e.g., looking at sample solutions to prior labs) during the exam.