During the test, you will not be able to access your regular home directory, access, receive, or send e-mail, print, or access the Internet.

The lab tests are closed-book and no aids are allowed.

At the end of your test session, this machine will be converted back to a standard, unrestricted Prism Lab machine. At this time, any files written by you during the test, except those that have been submitted, will not be recoverable. Make sure you submit your code before the end of the test. (Instructions to submit your code are below). If you do not submit your work on time, you will receive a grade of zero. (There are no exceptions.)

You have the lab period, 80 minutes, to complete this lab test. The computers will automatically shutdown at the end of the time (e.g., 6:20pm), warning you several minutes in advance. No additional time will be provided, so you must submit your work prior to this; otherwise, there will be no way to recover it (it will be lost), and you will receive a grade of zero (no exceptions).

You are encouraged to submit often during the test. Note that newer submissions overwrite older ones.

Your program will be marked for good style, as well as for running correctly (producing correct output in the correct format).

When you submit a file, you should include at the top of the file your name (surname, given name) and your Prism lab login. These should be placed in a comment so that the file will compile. Note that files which do not compile will receive a large penalty when marked, no matter how small the error that prevented compiling.

Submit the class FractionAction.java before the time deadline. Here is the command to submit your work:

% submit 1020 midtermR7.00 FractionAction.java

Further details regarding the submit command can also be obtained by typing man submit.

Once again, you are encouraged to submit regularly. Newer submissions simply overwrite older ones.

Unlike eCheck assignments, there is partial credit possible. If you are able to finish all aspects of the program (for example, say, input validation was requested but you did not do this), you should still submit it.

Here are the common APIs that you may access:

• Java 1.6 API
• Type API

Write a Java application called FractionAction.java. It will first prompt the user for how many fractions to read in. (You can assume this will be two or greater.) It then will read that number of fractions in, prompting the user for each.

After all the fractions have been read, your program should report the fraction seen with the smallest denominator of all the fractions seen, the fraction seen with the largest denominator, and whether the fraction itself with the smallest denominator is smaller than, the same size as, or larger than the one with the largest denominator. (For example, 24/49 < 1/2.) When considering the denominators, consider the fraction in reduced form! For example, 5/10 may have been entered, but you should consider it as 1/2. (In case of a tie for smallest or larger denominator, take the fraction that was input earlier.)

You do not have to do input validation.

Your output should look exactly like that indicated in the sample runs below. Your program should use the Fraction class from type.lib.

Here are two sample runs of a correctly written program. Note that the text in red is text that the user types. The text in black is what the program types. The '%' represents the prompt from the command-line window (shell).

% java FractionAction
Number of fractions to enter?
3
Enter fraction #1 (numerator denominator): 
2 9
Enter fraction #2 (numerator denominator): 
11 37
Enter fraction #3 (numerator denominator): 
4 28
The fraction with the smallest denominator seen was 1/7.
The fraction with the largest denominator seen was 11/37.
1/7 is smaller than 11/37.

% java FractionAction
Number of fractions to enter?
5
Enter fraction #1 (numerator denominator): 
23 41
Enter fraction #2 (numerator denominator): 
22 40
Enter fraction #3 (numerator denominator): 
23 39
Enter fraction #4 (numerator denominator): 
24 38
Enter fraction #5 (numerator denominator): 
25 36
The fraction with the smallest denominator seen was 12/19.
The fraction with the largest denominator seen was 23/41.
12/19 is larger than 23/41.

%

You should use good programming practises as described in the textbook, and your code should conform to the style guide in the textbook. You should comment at least minimally, as by the guidelines.

You should not use any features of Java not covered in the first five chapters of the text. There will be some deduction if you do.