How andron16/monopoly-1erproyecto-datosi works
This is a skeletal Monopoly project: the domain types describe a server-owned match, player turns, property and money transactions, and a transaction history. The apparent user workflow is to join a match, take turns moving and resolving a square, buy property, and eventually determine a winner; the sampled game methods are stubs, and Program.cs only prints “Hello, World!”, so this workflow is not wired up. The tree also indicates UI, networking, hardware, and reporting subsystems, but their implementation and connections are not established by the sampled source.
Main entry points: Juego.cs Match state · ListaDoble.cs Transaction history · Banco.cs Bank · Jugador.cs Player
Components 23
Match domain
- Player
Dominio/Jugador.cs - Match state
Dominio/Juego.cs - Board
Dominio/Tablero.cs - Board square
Dominio/Casilla.cs - Property
Dominio/Propiedad.cs - Bank
Dominio/Banco.cs - Transaction
Dominio/Transaccion.cs - Event card
Dominio/CartaEvento.cs - Dice
Dominio/Dado.cs
Game structures
- Turn queue
Estructuras/ColaCircular.cs - Card queue
Estructuras/ColaCartas.cs - Board links
Estructuras/ListaCircularDoble.cs - Transaction history
Estructuras/ListaDoble.cs - Player properties
Estructuras/ListaSimple.cs
Interfaces and integrations
- Game interface
Interfaz/VistaTablero.cs - Player menu
Interfaz/MenuJugador.cs - Network layer
Red/Servidor.cs - Network protocol
Red/Protocolo.cs - Hardware bridge
Hardware/main.py - RFID reader
Hardware/lector_rfid.py - Dice display
Hardware/display_dado.py - Transaction report
Reportes/ReporteTransacciones.cs
Other components
- Player
Connections 10
- Match state → Board: creates
- Match state → Turn queue: creates
- Match state → Card queue: creates
- Match state → Transaction history: creates
- Match state → Bank: creates
- Bank → Transaction history: records
- Match state → Transaction history: searches
- Player → Player properties: stores
- Player → Player menu: uses
- Player → Game interface: views