The top level class of your program must be called Game. It must have a default constructor and a void method named playGame() with zero parameters that runs one complete game to execution. Your program must run correctly when the main method of class WarGameMain.java is called.

• War is played with a standard deck of cards. 
• There are 52 cards in a standard deck.
• Each card has a suit and a rank
• The suits are hearts, diamonds, clubs, and spades
• The ranks are 2, 3, 4, 5, 6, 7, 8, 9, 10, jack, queen, king, and ace
• At the start of the game the deck is shuffled and split between the two players
• Each player has active packet of cards and a won packet of cards
• The games is broken up into rounds
• To start a round each player flips over the top card of their active packet
• The player who flips the card with the highest rank of the two cards wins both cards and adds them to their won packet. Ace is the highest ranked card, two is the lowest

******Get this much running before you add the other features listed below******

• If the ranks' of the two flipped cards are the same then a war ensues.
  • Each player deals the top three cards of their active deck face down and then flips fourth a card face up.
  • The player who flips the card with the highest rank adds all 10 cards (the original 2 that tied, 6 face down, and the final 2 face up) to their won packet. 
    
  • If the second set of face up cards in a war also tie with the same rank, another war ensues. Wars continue until 
    • one player flips up a card with a higher rank
    • OR one or both player cannot complete the war

    Example of a war.
    

    	1st up card. (causes war)	down card	down card	down card	2nd up card. (resolves war)
    player 1	10 of Clubs	Down	Down	Down	3 of Clubs
    player 2	10 of Hearts	Down	Down	Down	2 of Spades

    Player 1 wins all 10 cards. The down cards are revealed to all players after the war is completed.

• If a player's active packet is ever empty, they shuffle all of the cards in their won packet and their won packet becomes their active packet.
  This may occur during the middle of a war if a player does not have enough cards in their active packet to complete the war
• If a player does not have any cards in their active packet or their won packet they lose the game
• If a player does not have enough cards to complete a war (3 down, 1 up, after the initial card that tied), they lose the game.
• It is possible for both players to run out of cards while trying to complete a war. There have to be a lot of ties for this to happen. But if both players have 26 cards or one player has 27 and the other has 25 it is possible (but not very unlikely) for 7 ties in a row and neither player to have enough cards to complete the last war. If this occurs the game is a draw.

• Start by reading over the rules of the game of War carefully. Be sure you understand exactly how the game is played.
• Take a look at the files provided so you will be familiar with what you have to start with.
• Make a list of the nouns and verbs in the description. From these you will get your classes and methods. Remember, nouns become classes and verbs become methods.
• Look carefully at your list of nouns, and decide which are the most important, and which nouns are attributes of the important nouns.
  For instance, in the Card class, two attribues of a Card are the suit (spade, heart, diamond, club) and rank (2,3,4,etc.)
• Make a first pass at the classes your program will use, with the attributes of each class. The attributes will be the instance variables.
• Now look at the verbs. Verbs are action words, so they will indicated what how the classes will be acted upon. Connect the verbs (now methods) with the nouns they are associated with.
• For your classes, decide on the data types or data structures for the attributes of each class.
• For your methods, think about what information must be passed in to the method so it can do its job (the arguments) and what information needs to be returned after the method finishes its job (the return type).
• After you figure out the arguments needed for a method, decide on the data types of the arguments; then on the data type of the return type.
• Sketch in each class. For each class, this should include the attributes (the instance variables and their data types), and the header of each method in the class, along with comments that tell exactly what the method will do.
• NO implementation yet. Do not worry about HOW you will do these things, now just concentrate on WHAT needs to be done.

• Spend some time away from the computer, with pencil and paper, brainstorming what classes you need and what methods they would have. Talk this over with classmates or Sam or Anne.
• Have a working program at all times and add to it as you implement more features.
• After deciding what classes you need, implement them one at a time, simplest ones first. Test a class thoroughly before going on to the next class. You may need to alter your design as you implement and test classes.
• Design a little - code a little - test a little. Repeat.

• In addition to providing a working version of the game War complete the following experiments.
• You should automate these tests and suppress the output so the games run and simply report the results of the experiments.
  1. Does your game seem fair? Each player should win about half the time. Run 50,000 games. How many times does each player win? Were there any draws?
  2. On average how many rounds does a game take? From the 50,000 games you ran what was the average length of games in rounds?
  3. How important is it to start with the aces? Set the game up so one player always starts with all four aces. The other cards are distributed randomly. Each player still starts with 26 cards, but one of the players starts with the 4 aces and 22 other cards. Run this game 50,000 times. Does the player who starts with the four aces win significantly more often?