Repository navigation
Overall Architecture and Class Diagrams
Show us the layers in your system and your domain classes. You can also include individual class diagrams in your stories on GitHub Put in your highlevel arch diagram (ie the major components)
For all existing arch diagrams, please only describe changes in your arch
This diagram makes explicit the separation of the different aspects of our project, specifically that all communication between the actual game and any client will go through the FrontendServer first.
Note: The Website is not an actual class, it is simply the collection of frontend webpages, there may be webpages that are not outlined here later on, the GameViewer is a React Component that will be used in the LiveViewer and ReplayViewer pages, and the HostCreatedGame is an implementation of the GameServer with actual game logic, which will be the responsibility of anyone using our product.

This diagram shows the initial design of communication between all the required components for a participant to live test their agent code

Interaction Website Requirements
Team Website Meeting Minutes
Team Server Meeting Minutes
Team Viewer Meeting Minutes
User Consent and End-User License Agreement
Overall Architecture and Class Diagrams
Testing Plan and Continuous Integration
Deployment Plan and Infrastructure