Amos Chua

## Abstract Allow users to save decks on the server, after logging in (see #17) ## Details We should probably use MongoDB to allow horizontal scaling, should the player-base grow...

## Abstract Prototype the use case for the **Deck Manager** ## Details Draw a rudimentary use-case diagram to check for any loose ends, and update #59

## Abstract We intend to use a deck handler that comprises 3 sub-systems working in tandem. This issue thread serves as the parent thread; there will be issues for each...

## Abstract Draft the state diagram for the Deck Builder subsystem. ## Details To be completed after #65, and used as reference for implementation in code for #4

## Abstract Prototype the use case for the Deck Manager ## Details Draw a rudimentary use-case diagram to check for any loose ends, and update #4

## Abstract Draft the state diagram for the Deck Viewer subsystem. ## Details To be completed after #63, and used as reference for implementation in code for #58

## Abstract Displays the contents of a deck that was selected in the **Deck Manager** ## Details Should display the cards in the deck in a particular manner (refer to...

## Abstract Prototype the use case for the Deck Manager ## Details Draw a rudimentary use-case diagram to check for any loose ends, and update #58

## Abstract A deck-handling subsystem that offers a GUI interface for viewing existing/saved decks, as well as transitioning to the other two deck-handling sub-systems ## Details * Allows traversal between...

## Abstract Draft the state diagram for the Deck Manager subsystem. ## Details To be completed after #61, and used as reference for implementation in code for #59