How alessiapacca/ing-sw-2019-13 works
Project type and purpose
• This is a full-stack Java multiplayer board-game application (“Adrenaline”) with:
• A Server component (game logic, controllers, network listeners)
• A Client component offering both CLI and JavaFX GUI, with support for Socket and RMI connections
• The README confirms: complete game rules, socket/RMI support, GUI/CLI, multiplayer.
File structure
• Top-level: pom.xml, UML folder, configfolder, src/main, src/test
• src/main/java splits into packages:
• answers (DTOs for server→client responses)
• client (cli/gui, ConnectionSocket/ConnectionRMI, Updater, GameModel)
• server (SocketServer/ServerRMI, ClientHandler, GameProxy, GameManager)
• server/controller (TurnHandler, validators/actuators for each player action)
• server/model (domain: gameboard, map, player, cards, items)
• constants, exceptions, launcher
• src/main/resources: fxml views, maps, JSON configs (weapons/powerups/ammo_tiles)
README
• Technologies: Java 11+, Maven, JavaFX, Sockets, RMI.
• Client Cluster (blue):
• UI Layer:
– CLI: CliInput, UpdaterCLI
– GUI: JavaFX controllers (StartMenuController, MainGuiController, LoadingScreenController, etc.)
• Controller Layer: ActionParser, InputAbstract, Updater, ReceiverInterface
• Model Layer: GameModel, DTO packages (Info)
• Network Adapters: ConnectionSocket, ConnectionRMI, ListenerSocketThread
• Network (orange):
• Server Cluster (green):
• Network Layer: SocketServer, SocketClientHandler, ServerRMI, GameProxyInterface
• Application Layer: GameProxy, GameManager
• Controller Layer: TurnHandler, TurnPhase, validators & actuators for each action
• Domain Model: packages under server.model (gameboard, map, player, cards, items)
• Timer sub-system: GameStartTimer, NextPlayerTimer, SpawnTimer, TagbackTimer
Final advice
• Layers but collapse low-level classes into packages for readability.
• Package with the main classes or responsibilities.