Heads-Up One Card Poker

Objectives

• To gain experience designing, coding, and testing classes
• To gain experience with the use of composition in an OO design.
• To gain experience implementing an API
• To gain experience using classes from a library

As in project 2, the work for this simulation is broken into two parts. The GUI interface is being written by another group of students. Your assignment is to implement the supporting classes discussed in class this week.

This project will use a GUI to allow the user to control the game and display pertinent information as the game progresses. The GUI and the main driver will be provided for you in Project3.java to be found in Mr. Frey's public directory for this project.

• The Deck
One Card Poker uses a single standard 52-card deck. There are four suits (hearts, diamonds, clubs, and spades). In each suit there are thirteen (13) ranks. In order from highest to lowest the ranks are ace, king, queen, jack, 10, 9, 8, 7, 6, 5, 4, 3, and 2. Suits are irrelevant in One Card Poker.

So that all students play the same game (i.e. the cards are dealt in the same order), it is necessary that the deck of cards be initialized appropriately before shuffling. Initialize the deck of cards in the order Ac, 2c, 3c, ..., Qc, Kc, Ad, 2d, ..., Qd, Kd, Ah, 2h, ..., Qh, Kh, As, 2s, ..., Qs, Ks .

The algorithm below which shuffles an array of integers must be adapted and implemented to shuffle the cards to start a new game. This algorithm is known as the Fisher-Yates algorithm, was first designed for computers by Richard Durstenfeld, and popularized by Donald Knuth.

1. A[0], A[1]... A[n-1] is an array of integers
2. Let N = n-1
3. Pick a random index, k, between 0 and N (inclusive).
4. Swap the values of A[k] and A[N].
5. Decrease N by one.
6. Repeat from step (c) until N is less than 1.
To choose a random index (step c), use the nextInt( ) method of the random number generator class Random found in the Java library. To insure that all students get the same result after shuffling, seed the random number generator with the value 1234.
• Card Images
The GUI will display images of the player's cards during the game. The filenames for these images have the form <rank><suit>.gif where rank and suit are 1-char lower-case symbols. For ranks, a=Ace, k=King, q=queen, j=jack, t=ten and digits are used for 2-9. For suits, h=hearts, c=clubs, d=diamonds, s=spades. For example the image for the "king of spades" is in the file ks.gif and the image for the "9 of hearts" is in the file 9h.gif. The filename for each card should be stored in the Card class and available to GUI via an accessor.

A directory named cards that contains card images to be used for this project can be found in Mr. Frey's public directory. Copy this directory into your Eclipse project so that the cards directory is at the same level as the src directory. The cards directory is also available in tar and zip formats.

• Betting Strategy
The bettor's strategy is well defined and is very simple.
If the bettor's card is an Ace, King, Queen, or Jack he bets $40.
If the bettor's card is a 10, 9, 8 or 7 he bets $30.
If the bettor's card is a 6, 5, or 4 he bets $20.
If the bettor's card is a 3 or 2 he bets $10.
• Calling Strategy
The calling strategy is up to you, but should be based on the amount bet by the bettor. A very simple calling strategy is possible and requires little code.
Extra Credit will be awarded for a much more intelligent calling strategy that attempts to minimizes loses. To be awarded extra credit, you must submit a plain text document named Calling.txt that explains your strategy and the logic/mathematics that shows how your strategy minimizes loss of chips as compared to the simple strategy.
• Provided Classes
Two classes are provided for you. Their .java files may be copied from Mr. Frey's public directory.

Suit.java defines Suit objects used to identify a card. For example, Suit.HEARTS is used to represent the suit "hearts". This class is provided so that there is no possible discrepancy among all classes that refer to a card's suit. The four suits in a standard 52-card deck are Suit.HEARTS, Suit.SPADES, Suit.DIAMONDS, and Suit.CLUBS. Do not submit Suit.java. Documentation for Suit.java is provided in the file itself and in the Suit API document

Rank.java defines Rank objects used to identify a card. For example, Rank.TWO is used to represent a card with a rank of two. This class is provided so that there is no possible discrepancy among all classes that refer to a card's rank. The ranks of the cards in a standard 52-card deck are Rank.ACE, Rank.TWO, Rank.THREE, ... Rank.JACK, Rank.QUEEN, and Rank.KING. Do not submit Rank.java. Documentation for Rank.java is provided in the file itself and in the Rank API document

1. Mr. Frey's public directory for this project is /afs/umbc.edu/users/f/r/frey/pub/202/Proj3
2. Each file for this project should be part of a package named proj3.
3. You must implement main in each class to perform unit testing. See Testing Your Class in Main for help writing main to test your classes.
4. Note that some of these classes may be designed and implemented as immutable classes. That means that making copies of them is not necessary since "aliasing" does no harm. Use this fact to make your code easier, but be sure you can tell the difference.
   If your class is not immutable, be sure that you make copies of objects when apporpriate.
5. Inheritance is not used in this project.

1. submit all .java files you create.. DO NOT submit Project3.java, Suit.java, Rank.java.
2. submitls to verify they are in the remote directory

You can check to see what files you have submitted by typing

Remember -- if you make any change to your program, no matter how insignificant it may seem, you should recompile and retest your program before submitting it. Even the smallest typo can cause compiler errors and a reduction in your grade.

Avoid unpleasant surprises!