Reference no: EM13351144

In this assignment, you will be asked to implement a card game. You will need to make several design decisions for your code. It will be expected that all classes you write will utilize the principle of encapsulation. Part of your mark will be based on your design decisions for this assignment.

Don't try to solve the entire assignment in one go. Break it down into smaller manageable sub-problems. Don't wait to test your code until the end. Test each small part as you proceed. You are allowed to create as many helper classes as needed. You are allowed to create your own class hierarchies as needed.

Spend some time thinking before you start coding.

Don't wait until the last minute to start the assignment.

In this assignment, part of your correctness marks will be based on observing your running programs (and not solely on matching expected output). Be sure that the outputs you display in your programs are enough so that a marker can easily follow your program (and see that it is working properly). Do not include too much output so that it is overwhelming (or difficult) to follow.

Card Game

This assignment deals with a card game called Pairs. The game is defined as follows:

It is a game for two to four players and a single judge.

All 52 cards in a standard deck of playing cards are used in the game. The game starts with the judge giving 8 cards to each player. All the remaining cards are turned face up on the pile.

Each player takes a turn (defined below) in a given order and this repeats until some player has no cards left in their hand. The players take their turns in same order throughout the game. As soon as one player has no cards left the game immediately ends (the other players are not allowed to take a final turn). The game also ends when a player starts a turn and there are no cards left in the pile.