Hearts Card Game - Due Tues. Dec 14
*Use linked lists to implement a simulation of a game of Hearts for three to six players. Use the Omnibus Rules described on Alan Hoyle's Hearts web page:
[url removed, login to view]~alanh/[url removed, login to view]
*There are also links to more than you ever wanted to know about Hearts at: [url removed, login to view]
Our variation from Hoyle's rules adds these rules:
*All cards are dealt until there are not enough cards to deal one to each player. The leftover cards are the "kitty" (which should contain 52 % playerCount cards.) The kitty is given to the player who takes the first trick.
The passing of three cards at the beginning of each round follows this pattern: passToTheLeft = roundNumber % playerCount ... so, for example, if the players in clockwise order are Fred, Barney, and George, then in the fifth round, Fred passes to George, Barney passes to Fred, and George passes to Barney
If the two of clubs is in the kitty, then the player to the left of the dealer plays first.
This will be a "dumb" version of Hearts. That is, your program only needs to follow the rules of the game. Any additional playing strategies for more "intelligent" play are not included in the requirements. Your application asks the user for the number of players and their names. The dealer for the first round is randomly selected. Then the output of the simulation looks like this: See attached
The expected deliverable items for the completed assignment are:
**********The Design Is More Important Than The Code TO ME************
Attachment shows examples of what I want
** OO analysis(See Attachment)
** Event Scenarios(See Attachment)
** Noun/Verb Analysis(See Attachment)
** CRC and/or UML for the Hearts model objects and their relationships(See Attachment)
**algorithms which detail unambiguous terminating steps you use to solve the problem for the methods needed to implement the behaviors of Each of your objects/classes. These algorithms should be written in a manner so that the code could be coded from the algorithm they are not an afterthought.
**a test plan
**test execution listing for all test cases listed in the test plan.
**all .java source and .class files.
I will compile/run in JPadPro