STOCK MAINTENANCE SYSTEM

Ex no:
Date:

AIM: To create a system to manage personal budgets.

(I) PROBLEM STATEMENT:

The personal budget tracker system must take care of tracking income and expenses for an
individual user and provide analytical tools to review their financial health. It maintains the
number of transactions that are added or removed. The user initiates this process by adding
their income or expenses. The system allows the user to update and view financial records on
demand.

(II) SOFTWARE REQUIREMENT SPECIFICATION:

1.0 INTRODUCTION:

The personal budget tracker system serves as an interface between the user and their financial
data. It aims at improving the efficiency in managing personal finances and optimizing
budgeting.

1.1 PURPOSE:

The entire process of personal finance tracking is done manually for most individuals.
Considering the complexity of monthly and yearly expenses, a personal budget tracking
system is essential to meet the demands of modern financial management. This system uses
simple forms and data visualization tools to facilitate the tracking process and aid the user in
making informed financial decisions.

1.2 SCOPE:

-The system provides an interface where users can add their income and expense details.
-The user is concerned with managing their income, expenses, and savings, and can access
financial reports.
-The system provides reports on spending habits and savings trends for analysis.
-Provide a communication platform between the user and the system through feedback
notifications.

1.3 DEFINITIONS, ACRONYMS, AND ABBREVIATIONS:

-User: The individual managing their personal finances using the system.
-Transaction: A record of income or expense, including date, amount, and description.
-Category: A label or tag assigned to a transaction (e.g., Groceries, Rent, Utilities).

1.4 REFERENCES:

-IEEE Software Requirement Specification Format.

1.5 TECHNOLOGIES TO BE USED:

-Frontend: React.js or Vue.js (for user interface)
-Backend: Node.js (for server-side processing)
-Database: MongoDB (for storing user financial data)

1.6 TOOLS TO BE USED:

-IDE: Visual Studio Code

-Version Control: GitHub (for tracking project versions and collaboration)

1.7 OVERVIEW:

The Software Requirement Specification (SRS) includes two sections: overall description and
specific requirements.
Overall Description describes the major role of the system components and
interconnections.
Specific Requirements define the roles and functions of the system users.

2.0 OVERALL DESCRIPTION:

2.1 PRODUCT PERSPECTIVE:

The personal budget tracker acts as an interface between the user and their financial records.
This system makes the user interface as intuitive as possible while ensuring secure and
organized tracking of financial data.

2.2 SYSTEM FUNCTIONS:

-Add Transaction: User can log income or expenses.

-View Report: User can view monthly or yearly summaries of their financial activities.
-Set Budget Goals: User can set limits for specific expense categories.

2.3 USER CHARACTERISTICS:

-User: The person who manages their personal financial data.

-Transaction Validator: The system component that verifies the validity of the entered
transaction details.

2.4 CONSTRAINTS:

1. The user should have proper authentication to access their financial records.
2. The system must generate reports based on financial data without delay.
3. The user must ensure transaction data is accurate when inputting details.
Use Case Diagram

The Use Case Diagram will represent the interactions between the user and the system for
adding, editing, deleting, and viewing transactions, managing reports, setting budgets, and
more.

Actors:

• User: The main actor interacting with the budget tracker.

• System: The budget tracker application that stores and processes the user's data.

Use Cases:

• Add Income/Expense
• View Balance
• Edit/Delete Transactions
• Filter Transactions
• Generate Reports
• Categorize Expenses
• Set Budget Goals
• Visualize Expenses (Pie Chart)

Activity Diagram

The Activity Diagram will represent the flow of activities for core features like adding
transactions, calculating balance, and generating reports.

Activities:

1. Add Transaction:
o User inputs description, amount, category, type (income/expense), and date.
o System validates input.
 o System stores the transaction.
2. Calculate Balance:
o System retrieves all transactions.
o System calculates total income and total expenses.
o System updates the displayed balance.
3. Edit Transaction:
o User selects a transaction to edit.
o System allows modification of the transaction.
o System saves the updated transaction.
4. Generate Reports:
o User requests monthly or yearly report.
o System filters transactions by date.
o System generates and displays report summary.
Class Diagram

The Class Diagram will define the structure of your application, including the data and
methods for managing transactions, categories, users, and reports.

Classes:

• User:
o Attributes: userId, username, email
o Methods: addTransaction(), editTransaction(), deleteTransaction(), setBudgetGoal(), view
Report()
• Transaction:
o Attributes: transactionId, description, amount, category, type, date
o Methods: saveTransaction(), editTransaction(), deleteTransaction()
• Category:
o Attributes: categoryId, categoryName
o Methods: addCategory(), deleteCategory()
• Report:
o Attributes: reportId, reportType (monthly/yearly), startDate, endDate
o Methods: generateReport()