Rules of the game:

1. Chooser/Picker: Picks the topic to define (from the list below) & informs the group.
2. The guesser walks away so they can't overhear the group's discussion
   • It is highly recommended that the guesser join another group to help that other group complete step 3 (below), since the next step may take a while
3. The group discusses the term, makes sure that everyone understands what the topic is, and then agrees on a definition.
   • Where possible, the definition must contain a sample of Java source code that demonstrates how to use the term in an actual Java program.  You only need to write out the source code for the actual example, and not the rest of the program.
4. Everyone else (except the guesser) makes a definition that is wrong, but sounds plausible (like it MIGHT be right)
   • Everyone except the guesser must look at the definition so that they don't accidentally make a definition that is too correct.
5. The guesser rejoins the group
6. The chooser/picker reads all the definitions aloud
7. The guesser picks one definition
   1. If the chooser/picker's definition (the correct one) was chosen, then the guesser gets a point
   2. If anyone else's definition was chosen, whoever wrote the definition gets a point.
8. The group should pause & make sure that everyone understands the correct definition, and why each of the other definitions are (intentionally) wrong.  Also, they should make sure that each person understands the concept, and any questions that the group can't handle should be asked of the instructor.
9. At the end of the game the person with the most points wins the game.

List Of Topics:

For each of the bold-faced terms, the "official" definition is listed immediately underneath it in white text.  Select/Highlight the text to see the definition.

• syntax / compile-time error:
  Errors that occur when the program does not conform to the rules of the Java language
  pg 31
• logical / intent error
  Errors that occur when the program fails to carry out it's intended purpose.
  pg 33
• Describe how a simple "If" statement works
  The simplest form of an if statement asks a question and if the answer is true, it executes a group of statements once and then continues with the rest of the program.  If the answer to the question is false, that group of statements is not executed.
  pg 168
• Describe how an "If/Else" statement works
  First, the <<test>> is evaluated to determine whether it is true in the current situation.  If the <<test>> is true, the first block of statements is executed.  If the << test>> is false, then the statements following the word else are executed.
  pg 183
• Describe how a "while" loop works
  When a while statement asks a question and the answer is true, it executes a group of statements (just like the if statement).  However, instead of continuing with the rest of the program, the while statements asks the question again.  If the answer is still true, that same group of statements is executed again.  This continues until the answer to that question is false.
  pg 168
• Describe how a "Counting (while)" loop works, as we examined it in this class
  Prior to the start of the loop, set a counter variable to be zero (typically).  The <<test>> of the while loop should see if the counter is still less than the target number of repetitions.  If that condition is met, then the <<work>> of the loop should be done once, the counter should be incremented (increased) by one, and the loop should repeat (starting with the check at the top of the loop)
  pg 259
• Parameters
  A type of variable used to communicate a value to a service to use in accomplishing it's purpose.  See also: class variable, instance variable, temporary variable.
  pg 780
• Instance variables
  A variable that is specific to an object.  See also class variable, parameter variable, temporary variable.
  pg 777
• Override
  Replacing a service in the class being extended with a new version of the service.
  pg 780
• return type (for predicate methods)
  The type of the value returned by the query.  Specified just before the method's name when it is declared.
  pg 782

Less Detailed Topics:

Feel free to use these - the main difference between these & the above topics is that these topics have even less description here, so you may need to tell the guesser what you're looking for when you ask him/her to define something like "canPickThing"

• single-line comment
• multi-line comment
• new command
• canPickThing
• frontIsClear
• Logical operator: NOT !
• getAvenue
• getStreet
• countThingsInBackpack
• Output
  • System.out.println
  • System.out.print
• Input
  • Scanner
• If, if/else, while -
  • Rule about {'s
• Variable data types:
  • int
  • double
  • boolean
• Variable storage/lifetime types:
  • local variable
  • parameter
  • instance variable
• Simple types (int, double, boolean)
• Multi-file programs
• Nested loops
• Random numbers
• for loops
• Arrays
  • The "loop through all elements of an array" pattern
  • How to create an array (of int, double, or boolean)
  • How to go through an array ("Process all elements of an array" pattern)

• Ex: Print every element of an array

• Ex: average of an array

• Arrays as parameters
• Arrays are return values
• Debugging
  • "printf" / printing strategies

  • "Here's some code, where would you put print statements?  What would those statements tell you?"

  • Approach: figure out what it should do, see how the program (appears to) solve the problem, then check program by 'mentally tracing' the code
• Logical operators
  • AND - &&
  • OR - ||

• Non-robotic code

  • Helper classes – to ask for input, etc, etc