Quoridor - cs428TAs/w2023 GitHub Wiki

Table Of Contents

Deliverables

#1: Final Group

#2: Organization Chart

#3: Requirements Document

#4: PERT/Gantt Chart

#5: Arch & Design

#6: Test/SQA

Status Reports

#1: 2/4/2023

#2: 2/11/2023

#3: 2/18/2023

#4: 2/25/2023

#5: 3/4/2023

#6: 3/11/2023

#7: 3/18/2023

#8: 3/25/2023

#9: 4/1/2023

#10: 4/15/2023

Project Overview

How To Play

The Project

Deliverables

#1 Final Group

  • Colby Weber
  • Nick McMurdie
  • Nathan Burnett
  • Jake Edvenson
  • Tanner Ellison
  • Helaman Lee

#2 Organization Chart

Quoridor Team Organization.pdf

Role Person Responsibility
Project Manager Nathan Burnett Makes sure project is on track and assign tasks, helps either on the front end or back end depending on the project's needs.
Project Architect Colby Weber Ensures that the software is consistent for the whole project, designs both front and back end communication, leads in design decisions to allow for easy future linking of both ends of the software.
Project UI Designer Nick McMurdie Chief Designer for the front end of the project handling UI, webpage design, and all necessary assets.
Project Back end Programmers Tanner Ellison & Helaman Lee Chief Designers for the back end of the project handling game logic, server logic, and the game engine.
Project File Organizer & Asset Creator Jake Edvenson Design front end assets and compile weekly deliverables for the team, manage the github wiki page, assist front end development where needed.

#3 Requirements Document

Quoridor Requirements.docx

Prototype Demo Requirements (3/6/2023)

  • Functioning Front-End Webpage

    • HTML/Javascript coded game-board w/ custom game piece assets (players, walls)
    • Reacts based upon dragging/dropping assets & encodes results in JSON format
    • Communicates with a server via JSON parsing/encoding
  • Functioning Back-End Engine

    • Handles all game logic for 2 players
    • Keeps track of walls, player locations, movements, illegal actions, score, etc.
    • Communicates with server via JSON parsing/encoding
  • Functioning Server

    • Stores data in JSON format
    • Acts as middle-ground between Game Engine & Webpage
    • Allows multiple players at once

Work-In-Progress Requirements (3/27/2023)

  • Online Multiplayer

    • Communication accomplished through server
  • Asset Customization

    • Customizable game boards, player icons, etc.

Final Demo Requirements (4/17/2023)

  • 4-Player Multiplayer

    • Allows up to 4 players to play against each other at once
  • Scoreboard

    • Keeps track of player who has won the most matches

#4 Pert/Gantt Chart

PERT Chart.pdf Gantt Chart.pdf image image

#5 Arch/Design Document

Architecture & Design Document

image image

#6 Test/SQA Document

Quoridor Test Plan image

Status Reports

2/4/2023

image

2/11/2023

image

2/18/2023

image

2/25/2023

image

3/4/2023

image

3/11/2023

image

3/18/2023

image

3/25/2023

CS428 weekly status 3-25-2023

4/1/2023

CS428 weekly status 4-1-2023-1

4/15/2023

image

Project Overview

How To Play

Quoridor is a board game played with two or four players. The point of the game is to be the first to get your pawn to the opposite end of the board. On your turn you can either move your piece or place a barrier. When placing a barrier, you must leave at least one path from each pawn to their destination. With two players, each gets 10 barriers they can place.

There is a good amount of replay-ability with this game with multiple strategies that can be used. For instance, barriers can be used to force you opponent to take longer paths or to prevent them from blocking your path.

Amazon link

quoridor_amazon

The Project

The idea is to make a video game version of this so you can play with others online. This would require a server client architecture. The game logic for this should be strait forward and easy to implement. The style can be as simple or detailed as needed, and the networking could also be dropped depending on development time.