Homework answers / question archive / You are tasked with designing a program for a card game

You are tasked with designing a program for a card game

Computer Science

Share With

---

You are tasked with designing a program for a card game. This program should create a Deck, populate the Deck with Card objects and randomize the order of the cards. Cards should then be played to hands in accordance to the rules of the game.

Over the next week, I would like you to decide on the game you propose to create a program for. Some suggestions would be games like, Black Jack, Draw Poker, Uno, Hearts… etc. The game must require at least 2 players, and a single deck of unique cards which all players feed from, and formal rules.

Complexity of games vary, and I will only require one complex piece of the game. For example, a game like poker requires that the hand combinations are compared to determine which hand is of higher value; Full house is of higher value then a pair of aces, or three kings is of higher value then three queens. For poker I would not require an AI for a computer player as that would be beyond the scope of this class and the program will already have a complexity piece to it. A game like Go-Fish on the other hand does not need a complex piece to determine if the player has four of a kind. This program I would require an AI player component and want to make sure that the computer player is not requesting just the same card each time of the player.

When you return next week, I will require a write up of the following:

1. The Game you want to develop
2. The approach you want to take
3. The Complexity Component
4. If you choose to have one, your partner.

If you do choose to have a partner, I will expect more from your project.

Send me an email of what you are planning.

Card Game Project Requirements:

Title Screen

Title Menu:

• Run Game
• Rules – How game is played. This should display a string output explaining the game.
• Run Mode

Object Oriented Design pieces:

• Building Card Objects
• Building a Deck of Card Objects
• Shuffling Card Objects in Deck
• Creating Player Objects
• Moving cards from Deck to Player
• Validating Card values

Functional Design pieces:

Engine – Used to test pieces of functionality separately

• • Should allow for test cases to validate functions are working as expected
• Game Engine
  • Pregame functions – betting, dealing out cards, number of players. Essentially any thing that needs to happen before game starts.
  • Game workflow – setting which players turn it is, giving player turn choices. If Computer Player exist then logic must be in place to handle Computer players choices.
  • Game Over conditions – What happens at end of game

Design Documentation

• Overview of what program does.
• Specification of each Object (Card, Deck, Player)
• Description and workflow for game engine.

Complexity requirement:

• Part of the Program which adds complex logic; Validation of Card values, complex workflow for determining whos turn it is, Decision making for Computer players.

Code Standards:

• Code is Readable
• Variable Names are meaningful
• Code Tabs Lineup properly
• Comments are handled appropriatel

  Card Game Project part one(on separate document)

• Specification for building your Deck

  For part 1 of your card game you will need to create a specification for your card deck.This specification will include functions for populating cards to your deck and shuffling the deck (randomizing the order of the cards).For the specification I do expect a list of each operation with preconditions and postconditions

• Part 2

• For Task 2, You must implement the code for your deck. This implementation will require a run menu that can be easily used to demonstrate and run the functionality thus far.

  Card Game Project Requirements:
• Title ScreenTitle Menu:
  • Run Game
  • Rules – How game is played. This should display a string output explaining the game.
  • Run Test Mode
  Object Oriented Design pieces:
  • Building Card Objects
  • Building a Deck of Card Objects
  • Shuffling Card Objects in Deck
  • Creating Player Objects
  • Moving cards from Deck to Player
  • Validating Card values
  Functional Design pieces:
  • Test Engine – Used to test pieces of functionality separately
    • Should allow for test cases to validate functions are working as expected
  • Game Engine
    • Pregame functions – betting, dealing out cards, number of players. Essentially any thing that needs to happen before game starts.
    • Game workflow – setting which players turn it is, giving player turn choices. If Computer Player exist then logic must be in place to handle Computer players choices.
    • Game Over conditions – What happens at end of game
  Design Documentation
  • Overview of what program does.
  • Specification of each Object (Card, Deck, Player)
  • Description and workflow for game engine.
  Complexity requirement:
  • Part of the Program which adds complex logic; Validation of Card values, complex workflow for determining whos turn it is, Decision making for Computer players.
  Code Standards:
  • Code is Readable
  • Variable Names are meaningful
  • Code Tabs Lineup properly
  • Comments are handled appropriately
• Title ScreenTitle Menu:
  • Run Game
  • Rules – How game is played. This should display a string output explaining the game.
  • Run Test Mode
  Object Oriented Design pieces:
  • Building Card Objects
  • Building a Deck of Card Objects
  • Shuffling Card Objects in Deck
  • Creating Player Objects
  • Moving cards from Deck to Player
  • Validating Card values
  Functional Design pieces:
  • Test Engine – Used to test pieces of functionality separately
    • Should allow for test cases to validate functions are working as expected
  • Game Engine
    • Pregame functions – betting, dealing out cards, number of players. Essentially any thing that needs to happen before game starts.
    • Game workflow – setting which players turn it is, giving player turn choices. If Computer Player exist then logic must be in place to handle Computer players choices.
    • Game Over conditions – What happens at end of game
  Design Documentation
  • Overview of what program does.
  • Specification of each Object (Card, Deck, Player)
  • Description and workflow for game engine.
  Complexity requirement:
  • Part of the Program which adds complex logic; Validation of Card values, complex workflow for determining whos turn it is, Decision making for Computer players.
  Code Standards:
  • Code is Readable
  • Variable Names are meaningful
  • Code Tabs Lineup properly
  • Comments are handled appropriatel