AS A Administrator/CEO, INSTEAD OF having a static backend infrastructure for the budgeting app, I WANT TO design and set up a backend architecture IN the next week SO THAT created user accounts are saved on the database following our backend schema
SCENARIO: Setting Up Scalable Backend
GIVEN the budgeting app currently operates with a basic backend structure handling limited user data, WHEN the backend design and setup process begins, AND the development team sets up user authentication and a database via firebase, THEN the backend infrastructure successfully stores user accounts and user data WITHIN the next week, AND the app maintains high performance and reliability during usage WITHIN one week.
jasonli97
commented
8 months ago
AS A Administrator/CEO, INSTEAD OF having a static backend infrastructure for the budgeting app, I WANT TO design and set up a backend architecture IN the next week SO THAT created user accounts are saved on the database following our backend schema
SCENARIO: Setting Up Scalable Backend
GIVEN the budgeting app currently operates with a basic backend structure handling limited user data, WHEN the backend design and setup process begins, AND the development team sets up user authentication and a database via firebase, THEN the backend infrastructure successfully stores user accounts and user data WITHIN the next week, AND the app maintains high performance and reliability during usage WITHIN one week.
schema.json