CST141 Project 2: Chapter 9

The Fan Class
--or--
The RegularPolygon Class

• In BlueJ create a new Java project named "project-2" with one of two classes:
   
  • Fan as per the instructions in the textbook for Exercise 9.8; include validation in the set methods so that data field speed is between 1 and 3 and data field radius is always greater than zero (0);
  • An if block must be utilized in the toString method as specified in the textbook so that it returns speed, radius and color when the variable on equals true and radius, color and the message "Fan is off" when the variable on equals false as per the image of the terminal window output below:

    

    ( This is the partial credit assignment--the maximum grade for completing this assignment is 9 out of ten (10) points )
  • For a one-half (½) point deduction or maximum grade of 8½ out of ten (10) points , complete the Fan class as per the instructions in the textbook for Exercise 9.8 and those in the paragraph above with the exception of the implementation of the three constrants SLOW, MEDIUM and FAST; to get credit for this element, use the constants SLOW and FAST in the if statement within the set method for the instance variable speed
  • RegularPolygon as per the instructions in the textbook for Exercise 9.9; include if validation in the set methods so that instance variable n is always 3 or greater and instance variable side is always 1 or greater; from the Math class of the java.lang package of the Java API use the Math.PI constant and the Math.tan(double) method in the calculation of the area of the polygon (this is the full credit credit assignment--the maximum grade for completing this assignment is 10 out of ten (10) points)
     
  • For any version of this project use the this reference when assigning parameters to instance variables in set methods
  • Always call the set methods from constructors rather than assigning values to instance variables directly
  • In the case of the RegularPolygon class use the this reference when calling overloaded constructors as follows:
     
    1. The no-arg constructor calls this to pass all four default values (3 for n (number) of sides, 1 for side length, 0 for x-coordinate and 0 for y-coordinate) to the four-argument constructor
    2. The two-arg constructor calls this to pass the two parameters for the number of sides (n) and length of side, and its two default values 0 for x-coordinate and 0 for y-coordinate to the four-argument constructor
    3. The four-arg (int, double, double, double) constructor takes parameters for the four instance variables and calls the set methods to initialize their values
        
• Document the program by:

1. Including a substantive comment statement that describes the class's purpose, as well as substituting your name for the existing @author comment and the assignment due date for the @version comment that already exist at the top of the new class
2. Entering a substantive comment before each method (including the constructor) to describe its function

• Draw the UML diagram for the class as specified in the textbook; it is suggested that you do this before you begin to create the class as this should make the coding much easier.
   
• For this assigment it will be necessary to "Write a test program ..." as specified in the textbook.  Create an additional class Main with a main() method that includes the test operations.

• Students may work on all projects in teams of two or three, and, if so, all students in the group must submit the same project to their own dropboxes in Blackboard.  In the text box's dropbox, as well as in the source code documentation (comments), state the name(s) of the classmate(s) with whom you worked.
   
• When all steps are finished, you will submit two Java files:
   
  • Either the "Fan.java" or "RegularPolygon.java" class file and ...
  • The "Main.java" file that contains the "test" program with the main() method
     
• The completed project with a copy of either the Fan or RegularPolygon class file and the Main class file (the .java files) along with the UML diagram submitted electronically via attachments to a Blackboard dropbox is due to Prof. Struck by 11:59 p.m. on the date specified in the course outline.