Home

Scenario: A Day in the Life of Aria

Morning

Aria opens her bank app while sipping her coffee. She scrolls through the transactions, trying to figure out where all her money went this month. “How did I spend so much?” she wonders, seeing a long list of charges that blur together. She decides to track her spending but quickly feels overwhelmed by the idea of categorizing everything.

Late Morning

At work, Aria overhears her colleague Ethan talking about his budgeting system. “I assign limits to categories like groceries, eating out, and subscriptions,” he says. Aria nods, thinking it sounds helpful but feels unsure about how to start. “I don’t even know what my categories should be,” she admits to herself.

Lunch

Over lunch, Aria grabs takeout and wonders how much she’s spent on eating out this month. “Probably too much,” she mutters. She considers skipping dinner plans with friends but doesn’t want to miss out. “If I could see how much is left in my budget, I’d feel less guilty about this,” she thinks.

Afternoon

On her way home, Aria stops at a store to pick up some essentials. She debates buying a new book but hesitates. “Can I afford this, or will it put me over my budget?” she wonders. She ends up leaving without the book, feeling frustrated about not knowing her limits.

Evening

Back home, Aria sits at her desk with receipts scattered everywhere. She tries to organize them into categories but gives up halfway through. “If only I had a tool to track my spending as I go,” she sighs, resolving to start fresh next month.

Business Requirements:

Primary:

• Create a tool to help Aria track and categorize her spending in real-time.

Non-primary:

• Include a feature that shows remaining budget for each category.

Use Cases:

• UC1: Track all expenses and categorize them as they occur.
• UC2: View remaining budget for each category in real-time.
• UC3: Set limits for each category to help manage spending.

Functional Requirements (as issues with appropriate priorities):

• FR1: The system must allow for adding expenses and categorizing them in real-time.
• FR2: Users must be able to set spending limits for each category.
• FR3: The system should show the remaining balance for each category.

Non-Functional Requirements (as issues with appropriate priorities):

• NFR1: The application should have a simple and intuitive user interface.
• NFR2: The system should provide real-time feedback for expense tracking and category balances.

Link corresponding requirements to use cases:

• UC1: Linked to FR1, NFR1.

  • Issue 1: The system must allow for adding expenses and categorizing them in real-time.

  • Issue 4: The application should have a simple and intuitive user interface.

• UC2: Linked to FR2, FR3, NFR2.

  • Issue 2: Users must be able to set spending limits for each category.
  • Issue 3: The system should show the remaining balance for each category.
  • Issue 5: The system should provide real-time feedback for expense tracking and category balances.

• UC3: Linked to FR2, FR3.

  • Issue 2: Users must be able to set spending limits for each category.
  • Issue 3: The system should show the remaining balance for each category.

Constraints

• The project must use .NET 8.
• The user interface must be a Console Application.