CS 2102 (D15): Object-Oriented Design Concepts
Programming Exam Details

Wednesday's in-lab programming exam is designed to make sure you can do basic Java programming on your own. It isn't meant to be tricky, but rather to make sure you are able to do straightforward programming without the help of others.

How It Works

During the lab

• You will log into myWPI to access the test questions and starter file
• You will submit your work in Turnin
• You may not consult your notes or online resources (closed notes)
• You may ask the staff if you forget the name of a method or get stuck on syntax

You need to take the exam in your registered lab time. If you cannot, you must contact Professor Fisler by the end of Monday. myWPI and Turnin will provide access based on your registered lab times. If you try to take the test at a different time, you will not have access to the materials and/or submission areas.

If you have an academic accommodation and will be starting the exam at a different time from your registered lab, let Professor Fisler know.

What to expect

• We will give you a programming problem and a starter file. The starter file will provide initial class definitions (with default constructors), headers for key methods, and some examples of the classes that you can use in testing your work.

• You will be asked to do some routine Java programming, using operators and concepts that have appeared on prior homework assignments. If you have done enough of your own programming on the assignments (rather than letting a partner do all the programming), you should find the tasks straightforward.

• The exam is self-contained. It will not ask you to recall any specific examples from the course.

• Unless the assignment asks you to write test cases, you are not required to provide them. You may write tests if you wish.

• You are free to modify the starter file as needed, but please do not change the names of given classes or methods. If you find yourself making major modifications though, make sure you understand what the problem is asking you to do. As said above, this isn't designed to be tricky.

Logistics

• You may work either on your own laptop or on the lab computers.

• You may not look up notes or other materials during the exam. If you forget the name of a method or operator, or a basic bit of syntax, you may ask the lab staff. This should not be a cause for panic. Rather, it should reassure you that the exam uses straightforward Java programming concepts.

Grading

This test is designed to (a) make sure that you can do essential Java programming, and (b) let you make up for points lost earlier in the term (especially on the midterm). You will pass the test as long as your code compiles and you get the required method (mostly) working.

If you don't pass the test, you won't earn any points to offset prior losses. I will also look closely at your midterm and final exams to determine whether you should pass the course. This means you should focus on getting the required method to work first, then work on the parts that earn points back from the midterm.

If you do pass the test, parts of this exam can offset points lost on the midterm. The parts that earn offset points will be labeled on the problem statement. Failing to get to the "offset" parts will not lower your overall grade on the corresponding theme (meaning, for example, if the exam gives you a chance to offset program design points by encapsulating something, your overall program design theme grade won't drop if you don't get to this part). Once you pass, the exam only raises your grade.

Your code should follow good OO programming style as we have discussed all term (putting methods in the right classes, sharing duplicated code, avoiding instanceOf, using meaningful field names, etc). While you can still pass with some style violations, they will count heavily in offsetting losses from the midterm.