COSC 122 Programming II

Unless otherwise specified, your solutions to all programming problems must be expressed in Java. You may develop on the platform of your choice, but you should ensure that your submissions build and run correctly under Oracle's JDK 1.7.0_04. The development software is available at http://java.oracle.com.
The first six lines of every source file you submit should consist of comments like the following:
```
//  Name: Rick Halterman
//  Assignment number: 4
//  Assignment: Graphical Tic-Tac-Toe Game
//  File name: TicTacToeLogic.java 
//  Date last modified: June 13, 2012
//  Honor statement: I have neither given nor received any unauthorized help on this assignment. 
```
Including your name reassures me that the code I am grading actually is the person's code that I think it is. It also ensures that you will get the proper credit you are due. The honor statement reminds you that, unless specified otherwise, each assignment represents an individual effort and copying others' code is forbidden.
Submitting code that does not compile is a very bad thing. If you cannot complete a feature, document the missing functionality and provide at least a method stub. From wikipedia (http://en.wikipedia.org/wiki/Method_stub):

A Stub is a routine that doesn't actually do anything other than declare itself and the parameters it accepts and returns something that is usually the values expected in one of the 'happy scenarios' for the caller. Stubs are used commonly as placeholders for implementation of a known interface, where the interface is finalized/known but the implementation is not yet known/finalized. The stub contains just enough code to allow it to be compiled and linked with the rest of the program.

Help is readily available in the lab for resolving compiler errors; please take advantage of it.
Run-time errors and unhandled program exceptions are bad. While you genuinely may believe the problem lies in the compiler, your operating system, or your hardware, the problem almost certainly is somewhere in your code. The problem most likely involves an out-of-bounds array access or reference variable misuse.
For your safety, build your code with the highest warning levels provided by your IDE. The warnings are generated for a reason. Do not be satisfied until your code compiles cleanly (no warnings, no errors) under the strictest scrutiny.
You should examine any compiler warnings very carefully because often they infer subtle bugs in your code.
Unless otherwise specified, do not include any I/O (screen output or keyboard input) in the code you write. Clients of your code are responsible for I/O. You are welcome to add debugging output statements during development, but please remove them in your final product. Any stray output from your implementation code may interfere with a testing framework used to evaluate your code for correctness and completeness.
You are refining your skills with the possibility of becoming a professional software developer. With that in mind, the quality of the source code you submit should be a step above the code you wrote in COSC 121. Hopefully by now you have developed the habit of choosing descriptive variable and method names. Really long identifiers are neither necessary nor welcome, but using, for example, using a local variable named i as something more than a for loop control variable or a nondescript parameter is sketchy. Please be consistent with your spacing and indentation. Pick a style (K&R, ANSI, GNU, etc.) and use it throughout your program. Your IDE (if any) may be able to assist you in consistent formatting. Be consistent with how you name variables, constants, types, methods, etc. You should be using comments to clarify code that is not obvious. Methods should be documented sufficiently; consider:
```
/*****************************
 *  div(m, n)
 *    Returns m divided by n
 *****************************/
public static int div(int m, int n) {
    return m/n;
}
```
Really? What if n is zero? Your method comment should include the method's behavior under exceptional circumstances. A better description for the particular method above would be
```
/*****************************
 *  div(m, n)
 *    Returns m divided by n.
 *    The method's behavior is 
 *    undefined when n is zero.
 *****************************/
public static int div(int m, int n) {
    return m/n;
}
```
Please do your best to limit the length of each line of your source code to 80 characters or less.

All programming assignments receive a score of 0–10. Points are awarded as follows:

Points Qualification

0 Program does not address the assigned problem.

1 Program appears to address the assigned problem but does not compile.

2–7 Program compiles without errors and addresses various aspects of the assigned problem but contains logic errors or is functionally incomplete. Program may produce run-time errors.

8 Program compiles, behaves correctly in most situations, but it exhibits some incorrect behavior or is unreasonably slow performing some activities.

9 Program compiles, behaves correctly in all situations, and performs efficiently in all situations.

10 Program compiles, behaves correctly in all situations, performs efficiently in all situations, uses consistent style, good naming practices, and is well commented.

Points	Qualification
0	Program does not address the assigned problem.
1	Program appears to address the assigned problem but does not compile.
2–7	Program compiles without errors and addresses various aspects of the assigned problem but contains logic errors or is functionally incomplete. Program may produce run-time errors.
8	Program compiles, behaves correctly in most situations, but it exhibits some incorrect behavior or is unreasonably slow performing some activities.
9	Program compiles, behaves correctly in all situations, and performs efficiently in all situations.
10	Program compiles, behaves correctly in all situations, performs efficiently in all situations, uses consistent style, good naming practices, and is well commented.

Compiler warnings will not affect the assignment's grade; however, review the remarks above about the dangers of ignoring compiler warnings.

COSC 122 Programming II Remarks on Assignments

COSC 122
Programming II
Remarks on Assignments