Closed MESC2004 closed 4 months ago
Use Case Description Detail: Filling the database with tuples based on the developed schema.
Related Requirements: Existing card, game, match, and all other necessary values.
Goal In Context: Establishing the complete and filled database of the game in MySQL.
Preconditions: Completion of Issue #10
Successful End Condition: The database is fully filled with the appropriate values, showing all the necessary tables with the necessary information.
Failed End Condition: The database is partially or not filled, does not work or cannot run queries appropriately.
Primary Actors: Database Developers.
Secondary Actors: Game Developers, Backend Developers.
Trigger: The need for a database that allows for managing, consulting, adding, updating and deleting information for the game.
Main Flow:
Extensions: The database can use any adequate query necessary.
Closed with pull request #40
Use Case Description Detail: Filling the database with tuples based on the developed schema.
Related Requirements: Existing card, game, match, and all other necessary values.
Goal In Context: Establishing the complete and filled database of the game in MySQL.
Preconditions: Completion of Issue #10
Successful End Condition: The database is fully filled with the appropriate values, showing all the necessary tables with the necessary information.
Failed End Condition: The database is partially or not filled, does not work or cannot run queries appropriately.
Primary Actors: Database Developers.
Secondary Actors: Game Developers, Backend Developers.
Trigger: The need for a database that allows for managing, consulting, adding, updating and deleting information for the game.
Main Flow:
Extensions: The database can use any adequate query necessary.