Use Case Description Detail: Creation of the ER model for the game's database
Related Requirements: Establishment of game mechanics, card attributes, and data to be compiled from the game.
Goal In Context: Establishing the ER model of the database in third normal form with all the necessary relations and cardinalities to beg9n development of the SQL database.
Preconditions: Established values for each entity in the ER model.
Successful End Condition: An ER model is fully completed and represented visually with their appropriate relations and cardinalities in third normal form.
Failed End Condition: The ER model is incomplete, misrepresented, not in third normal form, not visually finished or not finished at all.
Primary Actors: Database manager.
Secondary Actors: Game Developers, Backend Developers.
Trigger: The need to have Json file flow with card data.
Use Case Description Detail: Creation of the ER model for the game's database
Related Requirements: Establishment of game mechanics, card attributes, and data to be compiled from the game.
Goal In Context: Establishing the ER model of the database in third normal form with all the necessary relations and cardinalities to beg9n development of the SQL database.
Preconditions: Established values for each entity in the ER model.
Successful End Condition: An ER model is fully completed and represented visually with their appropriate relations and cardinalities in third normal form.
Failed End Condition: The ER model is incomplete, misrepresented, not in third normal form, not visually finished or not finished at all.
Primary Actors: Database manager.
Secondary Actors: Game Developers, Backend Developers.
Trigger: The need to have Json file flow with card data.
Main Flow:
Extensions: Scaling to an SQL schema.