Exam #3 results

Exams have all been graded and you all did very well. I decided to count best five out of six as "the exam", given that time seemed to be against completion. For those who finished all six, kudos: you got some extra credit. Exam scores ranged from 95 to 110. Final grades have been posted on WebAdvisor and I'm pretty sure I emailed everyone their semester grades and/or let you know before you left last night.

Final grade distribution follows:

Registration reminder

Register for the spring term before the end of the fall semester! You will have a better selection of classes and sections if you do. Also, you should be aware that if you wait too long, there is the possibility that a section you want could be cancelled due to insufficient enrollment.

Tuition payments are not due until January 5th.

Exam #3 structure

The final exam is written. These are the six problems on the exam. Please prepare accordingly.

1. Three required programs
   1. Numerical conversion
   2. Geometric calculation
   3. One regular expression testing
2. Choice of one of two options in each category
   1. File I/O
   2. Decoupled class
   3. String manipulation

What did the computer say when it fell into the quicksand?

Lab 11 - FileIO

As one of the requirements to earn a B- or higher,
you must complete exercise 8.22 (6th ed, p300) / 8.19 (7th ed, p299) /
9.19 (8th ed, p339).

The class name must be FileIO and it may execute either as a GUI application or as a command line application.

Exam #3 programming problems

I strongly suggest that each student develop a Java solution to the following problems in preparation for the coding portion of the first exam. While I do not promise that the practical part of the exam will be *exactly* the same as any one of these problems, the actual test question will at least be very similar to several of these practice problems.

Watch this post - more to come!

Enumerating

Sometimes when you are programming, you come across situations where you need some constants but the constants all have something significant in common. Take for example a program which tracks a person's food intake. You might want to categorize each of the foods in the program's database.