PLANNING - CREATING AN ERD

[keanacobarde]

User Story

As a user, I will not see this, but as a developer, I need to understand the flow of data of the application.

Acceptance Criteria

Capstone acceptance criteria for the ERD is as follows:

• You must have an ERD for your project
• You must have a user-related data scheme. This means that different people can authenticate with your application, and the resources that are created must be assigned to individual users.
• In addition to having user-related data, you need to have at least one more 1 -> many relationships defined in your ERD.
• Having a many -> many relationship is recommended, but not required for your client side project.
• You are required to use the persistent storage tool that you were taught (i.e. json-server, firebase, SQL Server, SQLite).

Dependecies

N / A - This is an essential first step to designing the execution and the structure of the site.

Dev Notes

• Created through DBdiagram.io.
• There most likely won't be very many entities. This is a simple finance tracker. You create an expense that falls under a category. Many expenses belong to a single category but an expense can only have one category. Everything else within the application pulls from those entities.

[keanacobarde]

PROPOSED ERD:

[keanacobarde]

HOW WOULD YOU EXPLAIN THIS?

• The first thing the user needs to input is a monthly income. This is what's divide into category spending limits. This is the data the entire application revolves around. One month can have MANY expenses, but each expense can only belong to a single month. Whenever an expense is created, it is attached to the firebaseKey of a specific month.
• Categories are created. Many expenses can belong to one category, but an expense can only belong to one category.

[keanacobarde]

FINAL VERSION OF ERD Removed the following:

• category.amountLeftToSpend: done in the UI.
• monthlyIncome.currentAmount: done in UI.