SDD Warm Up

Prepared by Robert Kleffner, Tao Zhang and Jordan Leithart

Warm Up Game - Version 1.0

TABLE OF CONTENTS

• Change Log
• Introduction
  • Purpose
  • Scope
  • Glossary
  • Overview
  • References
• Architectural Design
  • Overview
• Interface Design
  • Tools
  • Navigation
• System Features
• Appendix A: Reference

Change Log

Date	Person	Change
2014-05-08	Rob Kleffner	Initial Design Document

Introduction

###Purpose

This Software Design Document details the design of Red Card Dev's second game, KickShot: Warm Up. The expected audience of the game goes from children at the age of 5 to adults of any age. The intended audience of this report is for technical users who wish to understand the design and implementation choices made in the development of Warm Up.

###Scope

This document contains a complete description of the design of KickShot: Warm Up. Rather than focus purely on Android, the decision was made early in production to develop for both Android and iOS devices, or all mobile devices which support HTML5 if possible. This will bring KickShot to a much wider audience, but introduces new design difficulties and implementation issues.

KickShot: Warm Up is also much more strategic than the Junior level, requiring the game state to be aware of more rules and handle them correctly. Input validation will be a large part of the interface design for Warm Up, to assure that the user can take certain actions only when those actions are permitted.

Architectural Design

###Overview The application will have two main components and eight sub-components:

• Activities:
  • Rules: The set of rules for the current game selected.
  • Actions: The set of actions that occur when different things happen during the course of the game.
    • Each action will have animation from the VTD group currently working on the project
  • Game: The main loop that controls the game logic.
  • Cards: The action chosen to be performed by the user. Click card to select and press 'Play Card'
• Views:
  • Board: The background of the viewport.
  • Dice: Dice that change based on a roll dice function.
  • Action Menu: Four buttons which allow the player to perform an action upon their turn.
  • Hand: The set of cards which are available to the player at any given time.
    • Cards: Cards which are playable appear in color; cards which cannot be played are grayed out and cannot be selected

Interface Design

###Tools

• Moqups: used to mock design the interface of Warm Up in the early design phase

###Navigation

• The application will use buttons that the user can click to navigate between menus.
• The application will use buttons for performing actions on the player's turn, including navigating between the different subviews.
• The application will utilize the touch input for button clicking.

Rules

Setup

Populating the Player Draw decks (27 cards total for each)

• 10 Pass cards
• 3 Goal Shot (right) cards
• 3 Goal Shot (left) cards
• 5 Intercept cards
• 3 Goal Block (right)
• 3 Goal Block (left)

Direct Free Kick cards

• Each player can draw up to 5 direct free kick cards during the game

Board setup

• Chip is placed on center line of the board (space ‘13’)
• Each player draws 6 random cards

Determining Kick-off team

• Both players roll one die
• High roll determines who has possession (who kicks off)

Global State

Tie-breaker

• Both players roll a die, higher roll wins the game
• If both players roll the same, perform tie breaker again
• Ad infinitum

Ending the half

• Half ends when either player first runs out of cards, then play goes around the board once
• Next half begins with the player who did not kick off the first half kicking off the second half

Turn Options

Kick-off

• Kick off only occurs after game start, end of half, or goal scored
• Only possible action is to roll dice
• If Not Doubles
  • Player moves forward # of zones equal to the higher die
  • e.g. roll 5 and 4 = move 5
• If Doubles
  • Player moves (# of one of the dice) + 1
  • e.g. roll 3 and 3 = move 4
• Player does not draw from the deck after kick off
• Immediately moves to defensive player’s turn

Play A Card

• Card is placed face up on board and it’s action taken
• If action requires dice roll, turn does not end and player must roll dice
  • This could be done automatically for the player, since they have no choice
  • Specific rules given for each card below
• When turn is complete, player draws another card from the top of his deck

Trading in a card

• Chosen card is placed face down on the board
• Card is drawn from the deck and moved into player’s hand
• If the player wants to play the newly drawn card, they may

Tools

Currently the project is using Java and NetBeans for the Warm Up game prototype. However, when the transition to cross platform app development occurs at the beginning of next semester, the language may change to more widely supported tool set such as Haxe or HTML5 and JavaScript.