Comp202: Principles of Object-Oriented Programming II
Fall 2007 -- Grading Criteria for Hangman Project   

Milestone 1

(adapted from the "Checkpoint" at the bottom of the body parts page)

At this point the students should be able to demonstrate:
 

• A working IWord and IBody systems:
  • Full working composite, state and visitor pattern system.
  • Full accessor method functionality
  • Proper factory functionality, although implementation of all the body parts is not necessary, only the NoosePart and a couple of others are needed.
• A working Hangman game class (which naturally incorporates the
  two above criteria) whose methods have the following capabilities:
  • makeAnswer() need only return a fixed answer, not a random answer.
  • reset() should
    • reinstantiate the word and body lists
    • return the current String representation of _word.
  • getWord() and getBody() should both work.
• paint() will
  • print indications of the currently visible body parts, which corresponds to the number of incorrect guesses.
  • indicate on the console if the game has been lost, via the ILoseGameAdapter (via the ILoseAdapter).
• guess(c) will check if c exists in _word, toggling corresponding state to visible everywhere c is located.
  • show a dash (or some specifically identified symbol) when corresponding IWord is invisible.
  • Checks if the game has been won and indicates it on the console via the IGameWonAdapter.
  • make another body part visible if the guess is incorrect.   (Note it should not actually "paint" the body).
  • Return the new (current) String representation of _word.
    
     

Grading breakdown:

• Documentation completeness (including README), clarity and correctness: 20%
• Design completeness and correctness: 40% total
  • 20% word list
  • 15% body list
  • 5% HangmanGame
• Operational completeness and correctness: 40% total
  • 15% word list
  • 10% body list
  • 5% HangmanGam
  • 10% test code
     

Milestone 2

The program must possess 100% functionality.   That is it must pass both the check list in milestone 1 and the checklist in milestone 2.

It is not required that the ILoseAdapter be disconnected after the game is lost.  That is, (optional) losing sounds and messages may repeat each time the frame is repainted.  However, once the game is lost, additional guesses should not be accepted.

Grading breakdown:

• Documentation completeness, clarity and correctness: 20%
• Design completeness and correctness: 40% total
  • 25% View
  • 15% Model
• Operational completeness and correctness: 40% total
  • 25% View
  • 15% Model

A lot is left to the to the discretion of the grading staff.

Should you have any questions, please feel free to ask.

Last Revised Thursday, 03-Jun-2010 09:52:28 CDT

©2007 Stephen Wong and Dung Nguyen