java program Card Dealer


1) Understanding the implementation and use of a _linked list_ ADT.

2) Review of _inheritance_

3) _Documenting_ ADTs

4) Enforcing _modular programming_

**Problem Definition:**

*Title*: Card Dealer

*Description*: A program is needed to deal hands for a simulated card game in which all cards are dealt to four players. The program simply starts with a full standard deck of 52 cards, and randomly divides them into 4 hands. After the hands are displayed, the user can choose to deal again or quit.

*Note*:You don't have to be a card player to understand the program; all you have to do is deal all 52 cards to four players (as in 4-player “Hearts??).

## Deliverables


1) You will need a **Card** class to represent a card (suit and value). This class must implement *Comparable*. Cards are ordered first by suit (Clubs, Diamonds, Hearts, Spades) and then by face-value within each suit. Aces are high, so you might want to assign face-values in [2 .. 14].

2) You will need a **Node** class for storing *Card*s. It should be generic.

3) You must implement your own **LinkedList** class for structuring the *Node*s. The *LinkedList* class must use a generic dynamic linking implementation.

4) Your **CardDeck** class and **CardHand** classes must both _inherit_ from your *LinkedList* class. i.e.:

· A *CardDeck* is a linked list of *Card*, plus a counter (*numCards*) to keep track of the number of cards remaining in the deck.

· A *CardHand* is a linked list of *Card*, plus the name of the *player*. (Players' names may be hard-wired, e.g., "North", "East", "South", "West".)

5) The *Game* class is a *CardDeck* and an array of four *CardHand*s.

6) All user input in the client program must be handled through a separate **UserInterface** class.

7) Each class must be in its own separate file.

8) Your classes must be documented. Remember that ADT documentation should be directed toward the client programmer.

9) There will be at least 9 files to be handed in (example names): *Dealer**.mcp, [url removed, login to view], [url removed, login to view], [url removed, login to view], [url removed, login to view], [url removed, login to view], [url removed, login to view], [url removed, login to view]* and *UserInterface*.*java*.

10) When a *CardDeck* is initialized, it may be in any order. To deal one card, your *deal* method must generate a random number in [1 .. *numCards*], remove the corresponding card from the deck, put the card into the appropriate player's hand

_**in order**_, and decrement *numCards*.

11) When the user chooses to deal again, the deck must be re-initialized, and the players' hands must be cleared before dealing.

12) The usual requirements apply: modularity, internal documentation, object orientation.

## Platform

java in windows platform

Kemahiran: Semua Boleh

Lihat lagi: name in diamonds, java programmer requirements, java 1.5 documentation, java 1.4 documentation, c plus plus array, internal documentation, remove object, java problem, java game, java card, HEARTS, full node, e card, documentation java, diamonds, deck of, deck of cards, deck cards, dealer, program linked list

Tentang Majikan:
( 0 ulasan ) Corvallis, United States

ID Projek: #3307652