Updates:

Objectives - At the conclusion of this assignment students will have demonstrated that they can:

• Use loops to repeat actions in a program
• Use a Random number generator.
• Practice if/else statements in calculating the logic of the hands.
• Practice loops by traversing the array of Die objects.
• Manipulate a game which consists of among other things an array of Die objects
• Organize operations into individual methods.
• Properly format output to specification.
• Do everything necessary to create, debug, and run a java program.
• Use comments to delineate each section of the program.
• Adhere to a Java Style Guide.
• READ AND FOLLOW DIRECTIONS!!!!!

Background

Yahtzee is a dice rolling game in which players compete to get the best score. By rolling the dice up to three times, players try to match "hands" in the game. The object of this PA is to write a checker class in which various "Hands" will be passed into the methods of the checker and the resulting "score" for that hand will be determined. An array of Dice will be passed to the checker and a score will be returned.

Requirements

PART A-Part A is to create the fully documented stubs for the YahtzeeChecker class.

PART B - Submitted to WebCAT. 

You will write a Java file, named YahtzeeChecker, that will check Dice for the score. The user will specify what kind of hand they want to check and the checker will call the appropriate method to check the dice for that hand. Each hand has a corresponding value and "rules" for acheiving that value. If the Dice do not conform to the rules for that hand, a zero is returned.

Part B Structure

Yahtzee.java is being given to you. It will play a game of yahtzee and use your YahtzeeChecker class to determine the value of the hand.

You will write your YahtzeeChecker from scratch based on the following UML diagram and further explanation.

Part B Deliverables

1. Upload your YahtzeeChecker.java toWeb-CAT (http://webcat.cs.jmu.edu).
2. Your program will be judged on correctness (80%) and conformance to the StyleGuide (20%). The checkoff chart is found here. Deductions for failing to follow the structure will be taken from the 80% correctness score. There is an increase in penalties for not documenting your methods or failing to include the acknowledgement section in your work.

Part C, D - Reflection and Pair Programming Log - graded as regular homework assignments. There will be separate Canvas Assignments for this.

You will write a reflection document for this assignment which will let you consider the process of building this program. It will also let you critique all of the assignments for this class.

In addition, you should keep a log showing how much time you and your partner worked together and how much time you worked alone. For students working without a partner, this log should reflect the time that you put into the assignment.

Honor Code

This is a pair programming assignment. You may work with your partner, but may not work with any other team. This assignment should be viewed as a take home exam. Your work on the assignment and your submission must conform to the JMU Honor Code. Authorized help is limited to the classroom handouts, lab material, the TAs for any CS139 or CS 149 section, and either professor. Copying work from another student not in your partnership or the Internet is an honor code violation, which will result in a zero on the assignment and possibly further sanctions. Any internet "help" you recieve should be documented in the acknowledgement section. Your work on this assignment is subject to review by MOSS which is a plagiarism detection tool for programs. Submission to WebCAT constitutes your submission of work for academic credit and your agreement that your work may be submitted to MOSS.