-
Notifications
You must be signed in to change notification settings - Fork 2
Meetings
15min
Class L-15 during class hour
- Jaime Alonso Fernández
- Pelayo Pérez Cueto
- Ana Calleja Ramón
- David García Weiss
- Matías Valle Trapiella
We started investigating the different approaches toward the development of the system and how to approach as well as discussing different alternatives for DDBB.
We have yet to decide, though discussed for a bit, whether if to segregate development into frontend and backend with assigned developers towards each front or to have everyone doing a bit of everything.
By the moment we have agreed to use firebase as our DDBB.
30min
Class L-15 during class hour
- Jaime Alonso Fernández
- Pelayo Pérez Cueto
- Ana Calleja Ramón
- David García Weiss
- Matías Valle Trapiella
Deployment of a prototype of the documentation.
- Develop the front-end
- Login
- Game mode selection
- Display
- Game display
- Leaderboard/End of game
- Tutorial of the game
- Timer
- Start the deployment via Vercel
- Initit progress on the bot IA (normal difficulty, not random)
30min
Class L-15 during class hour
- Jaime Alonso Fernández
- Pelayo Pérez Cueto
- Ana Calleja Ramón
- David García Weiss
- Matías Valle Trapiella
First deployement of the application in Azure. Assignation of the documentation.
- Do the first version of the documentation
- Develop the front-end
- Finish Login
- Game mode selection
- Display
- Game display
- Leaderboard/End of game
- Tutorial of the game
- Timer
- Start the deployment via Vercel
- Initit progress on the bot IA (normal difficulty, not random)
1 hour
Class L-15 during class hour
- Jaime Alonso Fernández
- Pelayo Pérez Cueto
- Ana Calleja Ramón
- David García Weiss
- Matías Valle Trapiella
First Sprint revision -> Documentation v_0.1 and First Deployment of the app on Azure.
- Create the FireBase database
- Connect the database with the game
- Connect the game + database with the frontened
- Create a new bot strategy
- Implement level of difficulty for the bots
- Fullfill 70 % of the mandatory requirements for the next sprint
To structure the application, we will use a hexagonal architecture. We'll host the frontend and game engine on Azure and use Firebase for the database, using the 'Ports and Adapters' pattern to bridge the two cloud platforms. Also we considered to use kubernetes in a more advanced project phase in order to orchestrate our microservices, manage container lifecycles, and seamlessly handle the communication between our Azure-hosted logic and the Firebase data layer.
| Special note: Colleague David García Weiss had abandoned the assignment and as so, the group.
30 min
Class L-15 during class hour
- Jaime Alonso Fernández
- Pelayo Pérez Cueto
- Ana Calleja Ramón
- Matías Valle Trapiella
Groupal revision of the Login Window and discussion and agreement in the global project architecture.
- Create the FireBase database
- Connect the database with the game
- Connect the game + database with the frontened
- Create a new bot strategy
- Implement level of difficulty for the bots
- Fullfill 70 % of the mandatory requirements for the next sprint
We have finally agreed to stay with express rather thsn using springboot and we will be using bootstraps for the visual components.
30 min
Class L-15 during class hour
- Jaime Alonso Fernández
- Pelayo Pérez Cueto
- Ana Calleja Ramón
- Matías Valle Trapiella
Revision of the progress of the login window and the game interface as well as discussion of the progress of the gameManager microservice
- Connect the game + backend with the frontend
- Continue to create a new bot strategy
- Implement level of difficulty for the bots
- Fullfill 70 % of the mandatory requirements for the next sprint
To use Redis to cache the ongoing matches for quick and easy access.