Use Case Description Detail: Create the basic JavaScript API that will manage the json data for the cards.
Related Requirements: Existing card designs and values, including their stats and effects.
Goal In Context: Establishing a base structure that will evolve into a full API to connect the game to SQL and Unity.
Preconditions: Knowing the appropriate parameters that a card has, so the API can know what a card json looks like.
Successful End Condition: The API server works and can receive requests for consulting the current cards, adding a card and check that it has the appropriate parameters, delete cards and update a card in the API.
Failed End Condition: The server cannot connect or receive the appropriate requests.
Primary Actors: Backend developers
Secondary Actors: N/A
Trigger: The need to have Json file flow with card data.
Main Flow:
The API recieves a request.
The API analyzes the request and prepares a response depending on the endpoint received.
The API sends the approriate response, or the list of cards in case of an available_cards endpoint GET request.
Use Case Description Detail: Create the basic JavaScript API that will manage the json data for the cards.
Related Requirements: Existing card designs and values, including their stats and effects.
Goal In Context: Establishing a base structure that will evolve into a full API to connect the game to SQL and Unity.
Preconditions: Knowing the appropriate parameters that a card has, so the API can know what a card json looks like.
Successful End Condition: The API server works and can receive requests for consulting the current cards, adding a card and check that it has the appropriate parameters, delete cards and update a card in the API.
Failed End Condition: The server cannot connect or receive the appropriate requests.
Primary Actors: Backend developers
Secondary Actors: N/A
Trigger: The need to have Json file flow with card data.
Main Flow:
Extensions: Scaling to SQL and Unity connection.