Cards Against Humanity WebGame Documentation

7/25/2019 Cards Against Humanity WebGame Documentation

1/24


2/24


3/24


4/24

SOFTWARE REQUIREMENTS SPECIFICATION

1.0 Introduction

This section provides an overview of the entire requirement document.

This document describes all data, functional and behavioral requirementsfor the game.

1.1 Goals and objectives

The goal of our project is to take an existing web game and recreate it with new

features and different functionality using ASP.Net. We wanted to choose somethingthat would be fun and enjoyable to make and to use. We want to take inspiration from

the game that is currently there and make it more interesting and interactie for the

players. We hope to accomplish this by making the user interface more appealing andengaging.

1.2 tatement of scope

!hat are we going to build"

We are going to build a replica of the popular card game! "ards Against #umanity!

that is hosted on a website. The game consists of $%&' players and are gien a

starting hand of &' white cards. (ach turn! eeryone draws a new white card to theirhand. To start the game! someone at random is chosen to be the card ")ar and a

black card will be drawn and shown to all players. Players will then choose the cardthey find the funniest! best fitting! or most cleer card. *nce all players hae chosen a

card! the "ard ")ar will then choose the one that he+she finds the best. The winningplayer is then awarded an awesome point and the next ")ar is chosen in round%robin

fashion. The game ends when a player reaches a certain number of points. The ,ame#ost determines the numbers of points that will end the game. -efore the game is

started! the host will select pre%defined rules for the game.

!h# is this interesting"

This web application is interesting in the same way that the physical card game isinteresting. There exists many web clones of the game! but many of them are difficult

to use or not customi)able to the extent we would like them. We want to take theopen source game and transform it into a more customi)able game experience for all

users.

1.$ oftware conte%t

The big picture is to hae a fun and easy to use web game that you can use to sit

down and play a funny game with some friends. t will easily allow people to play thegame and create new games. The web page will also allow for customi)ation in the

rules of the current game and the cards used during games. An important factor forthe games is flexibility.

&


5/24


6/24


7/24


8/24


9/24


10/24

7.4. ost onditions

13 The winner of the round was determined.

23 0epending on the rules! a new c)ar was chosen.

8. (se case 08

8.1. (se aseTrack Points

8.2. ctors

System

8.$. reconditions

13 A game needs to hae been created and started.

23 All players hae played a card for the round.

$3 Players hae been winning the rounds.8.&. Triggers

This use case is triggered when the game is playing out. After each round the system keeps

track of the ongoing points.

8.4. ost onditions8.5. 13 The Points hae been kept and the winner can be determined after each round.

10. (se case 10

10.1. (se ase

(nd ,ame

10.2. ctors

System10.$. reconditions



$3 Players hae been winning the rounds.

&3 A player has reached the winning number of points.10.&. Triggers

This use case is triggered when a player has reached the winning number of points for a

game.

10.4. ost onditions

13 The game is ended and the winner is announced.

23 A new game can be started or players can leae.

11. (se case 11

11.1. (se ase,ame Transition

11.2. ctors

Player! ")ar! and System

11.$. reconditions



$3 Players hae been winning the rounds.

9


11/24


12/24


13/24


14/24

&.$ (se ase +iagrams

1&


15/24

&.$ equence +iagrams

8ain flow % This shows the happy path of the web page and how a user would

interact with the game. *ne user would start a game and allow other players

to join. While other players are joining the user can select the rules and cardsfor the game. Then the player begins the game and the rounds are played

until a player wins.

1)


16/24

4.0 :ehavioral 'odel and +escription

description of the behavior of the software is presented.

4.1 +escription for software behavior

A detailed description of major eents and states is presented in this section.

4.1.1 vents

(ents consist of the following/

lic; tart Game

4pon clicking the 9Start ,ame: button! the user will now be in the

administrator of the game session. They hae access to controls that otherswho join the session do not. These controls include ,ame Settings! Actie

"ard 0ecks to choose 5rom! "reate New 0eck of "ards! and mport a 0eck of"ards.

lic;


17/24


18/24


19/24


20/24


21/24

inal Interface -esi,n:


22/24


23/24

0utstandin, Issues

Time constraint: :e hoose to do a pro#et that 'e thought 'ould be!nterest!ng and %un to do but !t turned out to be more d!;ult than 'eant!!pated and as a result 'e 'ere not able to aompl!sh as muh as 'e

'anted. In the end 'e opted %or us!ng a ard 3/I !nstead o% a database and 'e'ere not able to ma


24/24

Cards Against Humanity WebGame Documentation

Documents

Transcript of Cards Against Humanity WebGame Documentation