- Concept Description
- Wire Frames
• Home Page
• Purchases Page
• Spending List Page
• Spending Summary Page
• Budget Page - Database Diagram
- User Stories
- Use Cases
- UML Diagram
- Requirements Table
- Test Table
- Database Diagram
The purpose of the app is to help individuals overview their spending to make better financial decisions. Just the act of writing down what you spend is enough to help you become wiser with your money. The app will focus on awareness through logging purchases and monthly expenses. The goal is to create an application with modular code that can be easily transferred to a mobile application.
• As a young adult, I want an app that aggregates my purchases, so that I can maintain records in one place. • As a transitioning military member, I want to know the difference between what I spend and my budget, so I can avoid going into debt. • As a career changer who is moving, I need to know the difference between what I expect to spend and what I actually spend so that I can adjust my budget. • As a financially educated individual, I want an overview of where my money is going so that I can maintain or change spending habits.
- Given a purchase, when the user has time then accept the information on the purchase.
- Given an income, when the user wants to find the difference between amount spent and income, then display that difference.
- Given monthly expenses, when the user inputs them, then show the total.
- Given monthly expenses, when the user has projected expenses that differ from actual expenses, display that difference for each category, subcategory, and total.
- Given purchase inputs, when a user wants to see the overview of purchases, display different formats for the user to interact with.
- Given purchase information, when the user wants to see them all in a order, display the list of purchases.
| Requirement ID | Requirement Description | Test Method | Test ID |
|---|---|---|---|
| 1 | The system shall accept the users purchase information | Unit | tbd |
| 1.2 | The software shall input that purchase information into the database to be retrieved later | Integration | tbd |
| 1.3 | The software shall populate a list of purchases | Unit | tbd |
| 2 | The user should be able to view the purchases in different formats like a pie chart, bar chart, and calendar | Integration | tbd |
| 2.1 | The software shall pull purchase data out and organize it on different variables such as price, category, and date | Unit | tbd |
| 3 | The user shall be able to input monthly expenses and income | Unit | tbd |
| 3.1 | The system shall calculate the difference between income and monthly expenses | Unit | tbd |
| 3.2 | The software shall send the monthly expenses to the database to be retrieved later | Integration | tbd |
| 3.3 | The software shall display total expenses for each category and for all categories combined | Unit | tbd |
| 4 | The user should be able to log back in and view all data previously input | Integration | tbd |
| 4.1 | The system shall pull data based off of a user identification | Unit | tbd |
| Test ID | Requirement ID | Test Procedure | Current Status | TimeStamp | Build/Version |
|---|---|---|---|---|---|
| 1 | 1 | Unit Test | Not Tested | 00-00-0000 | 0.1 |
| 2 | 1.2 | View the DB | Tested | 05-10-2021 | 0.1 |
| 3 | 1.3 | Unit Test | Not Tested | 00-00-0000 | 0.1 |
| 4 | 2 | View Charts | Tested | 05-10-2021 | 0.1 |
| 5 | 2.1 | Check each filter for accuracy on purchase list/Unit Test | Not Tested | 00-00-0000 | 0.1 |
| 6 | 3 | Type in values then check database for saved values/Unit Test | Tested | 05-10-2021 | 0.1 |
| 7 | 3.1 | Unit Test | Tested | 05-10-2021 | 0.1 |
| 8 | 3.2 | Check DB for values | Tested | 05-13-2021 | 0.1 |
| 9 | 3.3 | Unit Test | Not Tested | 00-00-0000 | 0.1 |
| 10 | 4 | Log in and out | Tested | 05-13-2021 | 0.1 |
| 11 | 4.1 | Unit Test/Manual verification | Tested | 05-13-2021 | 0.1 |
