blackjack_java

Introduction

In this workshop you will continue implementation and documentation of a Black Jack game. The design i similar to what we have done on the lectures but it is not exactly the same. Save models and implementation in your portfolio. The focus is not usability or a nice user interface but to have a robust and well documented design that can handle change. In the zip files you find a started but not playable version of the game in C# or Java. As there are many different variants of the rules one of the aims is to create a flexible design that supports different combinations of rules. There are also a class diagram that describes the packages, classes and the relations in the implementation. There is also a sequence diagram for one not implemented part of the game.

Grade 2 requirements

• Download, compile and run the game in your development environment (remember that it should run, but it’s not playable).
• Study the class diagram and the source code to understand the design of the game.
• Implement the operation Game::Stand using the sequence diagram Game_Stand sequencediagram. The game should now be playable.
• Remove the bad, hidden, dependency between the controller and view (new game, hit, stand)
• Design and implement a new rule variant for when the dealer should take one more card. The new variant is “Soft 17″, use the same design pattern already present for Hit. Soft 17 means that the dealer has 17 but in a combination of Ace and 6 (for example Ace, two, two, two). This means that the Dealern can get another card valued at 10 but still have 17 as the value of the ace is reduced to 1. Using the soft 17 rule the dealer should take another card (compared to the original rule when the dealer only takes cards on a score of 16 or lower).
• Design and implement a variable rules for who wins the game. This variation could for example vary who wins on an equal score (in one implementation the Dealer wins, in the other the Player). The design should make it easy to add other variants without changing the Dealer.
• The code for getting a card from the deck, show the card and give it to a player is duplicated in a number of places. Make a refactoring to remove this duplication and that supports low coupling/high cohesion. The code that is duplicated i similar to this:

Card c = deck.GetCard();
c.Show(true/false)
player.DealCard(c);

• Use the Observer-pattern to send an event to the user interface that a player (human or dealer) has got a new card in his hand. When the event is handled the user interface should be redrawn to show the new hand (with the new card) and the game should be briefly paused, to make the game a bit more exciting, the pausing code should be in the user interface (view or controller) and not in the model. The pause should be when any player (dealer or player) gets a card. The start game procedure should be something like:

Dealer:

Player: c1

pause

Dealer: c1

Player: c1

pause

Dealer: c1

Player: c1, c2

pause

Dealer: c1, c2

Player: c1, c2

• Update the class diagram to reflect the changes you make (it is not necessary to recreate the whole diagram only the parts that have been affected by your changes). You should have the following in your portflio and all parts should match

• Easily executable version alt. instructions on how to execute. Source code for the entire application An updated class diagram