Hello, dear friend, you can consult us at any time if you have any questions, add WeChat: THEend8_
EECS 132: Homework Assignment
Programming Project 3
IMPORTANT: Read the Do's and Dont's in the Course Honor Policy found on blackboard.
I. Overview
The purpose of this project is to give you practice designing a class/type hierarchy. It is
important that you spend time designing your class hierarchy before you start coding. If
you properly organize your classes and/or interfaces, you can achieve the desired program
behavior below with significantly less code than with a poorly organized hierarchy. This
project will also how there are limitations to what we can do with Java's classes and
interfaces.
II. Code Readability (20% of your project grade)
New for this assignment: The comments above the class or interface and above each
method must be written in JavaDoc format. You will be introduced to JavaDoc style
commenting in the labs. You can also find a description in the Java in a Nutshell text. Be
sure to run JavaDoc and view the webpage in order to verify that you have implemented
the comments correctly.
To receive the full readability marks, your code must follow the following guideline:
All variables (fields, parameters, local variables) must be given appropriate and
descriptive names.
All variable and method names must start with a lowercase letter. All class and
interface names must start with an uppercase letter.
The class body should be organized so that all the fields are at the top of the file, the
constructors are next, the non-static methods next, and the static methods at the
bottom.
There should not be two statements on the same line.
All code must be properly indented (see page 644 of the Lewis book for an example
of good style). The amount of indentation is up to you, but it should be at least 2
spaces, and it must be used consistently throughout the code.
You must be consistent in your use of {, }. The closing } must be on its own line and
indented the same amount as the line containing the opening {.
There must be an empty line between each method.
There must be a space separating each operator from its operands as well as a space
after each comma.
There must be a comment at the top of the file that is in proper JavaDoc format and
includes both your name and a description of what the class represents. The comment
should include tags for the author.
There must be a comment directly above each method (including constructors) that is
in proper JavaDoc format and states what task the method is doing, not how it is
doing it.