On This Page
Overview
This assignment uses objects to simulate a simple dice game. During this assignment, you will:
- Code a class to hold the data for a die
- Code classes that hold multiple instances of the
Die class
- Optionally, construct a class that uses static methods to test a class
^ top
Operation
If the user chooses to roll the dice, the application rolls two six-sided dice, displays the results of each, and asks if the user wants to roll again.
Welcome to the Paradise Roller application
Roll the dice? (y/n): y
Roll 1:
2 5
Craps!
Roll again? (y/n): y
Roll 2:
2 1
Roll again? (y/n): y
Roll 3:
4 6
Roll again? (y/n): y
Roll 4:
6 6
Box cars!
Roll again? (y/n): y
Roll 5:
1 1
Snake eyes!
Roll again? (y/n): n
^ top
Specifications
- Create a class named
Die to store the data about each die. This class must contain these constructors and methods:
public Die() // default to six-sided die
public Die(int sides) // variable number of sides
public void roll() // randomly picks a face value
public int getValue() // returns the face value
- Create a class named
PairOfDice to store two dice. This class should contain two instance variables of the Die type, an instance variable that holds the sum of the two dice, and these constructors and methods:
public PairOfDice() // default to six-sided dice
public PairOfDice(int sides) // variable number of sides
public void roll() // roll both dice
public int getValue1() // get value of die1
public int getValue2() // get value of die2
public int getSum() // get sum of both dice
- You can use the random method of the
Math class to generate a random number from 1 to the number of sides on a die like this:
int value = (int) (Math.random() * sides) + 1;
- Create a class named
DiceRollerApp that uses the PairOfDice class to roll the dice. This class should display special messages for craps (sum of both dice is 7), snake eyes (double 1’s), and box cars (double 6’s). For this application, assume that two six-sided dice are used.
- Do not use package statements at this time.
^ top
Extra Credit
The following are worth extra credit points:
- Create a class named
Validator that contains static methods that can be used to validate the user input data in this application. (1 to 3 points depending on the completeness of the tests)
Make certain that your README.txt file lists any extra credit attempted.
^ top
Grading Criteria
The instructor will evaluate your assignment using the following criteria. Each criteria represents a specific achievement of your assignment and has a scoring guide. The scoring guide explains the possible scores you can receive.
Some scoring guides have a list of indicators. These indicators are a sign of meeting, or a symptom of not meeting, the specific criterion. Note that a single indicator may not always be reliable or appropriate in a given context. However, as a group, they show the condition of meeting the criterion.
For information on grading policies, including interpretation of scores, see the course information page.
Program Compilation
- 4: Source code compiles with no errors or warnings
- 2: Source code compiles with warnings
- 0: Does not compile
Functionality
- 10: Demonstrates mastery of the assignment
- Has extra features or demonstrates techniques beyond the assignment
- Applies concepts from the lessons appropriately
- Meets all specifications (see above) with particularly elegant solutions
- Runs to completion with no abnormal error conditions
- Generates correct output given correct input
- Behaves in a reasonable way in response to incorrect data
- All test cases pass
- 8: Has all the functionality expected of the assignment
- Demonstrates many techniques from the lesson
- Meets all specifications (see above)
- Implementation seems more complicated than necessary.
- May have one minor error
- All test cases pass
- 6: Has most of the functionality expected of the assignment
- Demonstrates some techniques from the lesson
- Meets all but one of the specifications (see above)
- Implementation seems excessively complicated.
- May have 2-3 minor errors
- All but one test case passes
- 4: Has some of the functionality expected of the assignment
- Demonstrates some techniques from the lesson
- Meets at least 1/2 of the specifications (see above)
- Implementation seems excessively complicated.
- May have more than 3 minor errors
- At least 1/2 of all test cases pass
- 2: Serious functional problems but shows some effort and understanding
- Meets less than 1/2 of the of the specifications (see above)
- Has a major error or many minor errors
- Implementation seems very convoluted
- Demonstrates few techniques from the lesson
- Less than 1/2 of all test cases pass
- 0: Does not execute
Program Style
- 4: Code is well-documented
- 3: Code has minor documentation errors
- Has 1 documentation error
- 2: Code has some documentation errors
- Has 2-3 documentation errors
- 1: Code has many documentation errors
- Has more than 3 documentation errors
- 0: No apparent attempt to document code
README.txt File
- 2: README.txt file submitted with specified information included
- 1: README.txt submitted but some information was not included
- 0: No README.txt submitted
Maximum Score: 20, plus extra credit
^ top
What to Turn In
Submit your assignment following the instructions for homework. Include the following items for grading:
README.txt file
Die.java
PairOfDice.java
DiceRollerApp.java
- Any other source code needed to make your program function
You must submit all the files needed to make your assignment function properly. Do not assume that the instructors has any files unless explicitly stated by the instructor. Your assignment must work as submitted.
^ top
Home
| WebCT
| Announcements
| Schedule
| Room Policies
| Course Info
Help
| FAQ's
| HowTo's
| Links
Last Updated: April 01 2005 @16:37:28
|