Skip to content

Latest commit

 

History

History
65 lines (40 loc) · 2.09 KB

README.md

File metadata and controls

65 lines (40 loc) · 2.09 KB

FinFinity - http://finfinityse.s3-website.us-east-2.amazonaws.com

Empower Your Wallet: Tracking Every Penny, Planning Every Possibility

Delivered to Srimathi Srinivasan on 31 March 2024 by Group 7

Table of Contents

  1. Introduction
  2. Requirements
  3. Architecture Design
  4. Glossary

Introduction

FinFinity is designed to make financial management accessible to everyone, offering tools for tracking transactions, setting budgets, and analyzing financial data. This document outlines the core components, features, and the structure of the FinFinity application.

Requirements

Functional Requirements:

  • Automatic transaction tracking and categorization.
  • Budget setting and monitoring with notifications for limits.
  • Financial reporting and analysis with customizable reports.
  • AI chatbot for personalized financial advice.
  • Goal setting with progress tracking.

Non-Functional Requirements:

  • Intuitive, user-friendly interface.
  • Strong security and privacy measures.
  • High performance, capable of handling peak usage.
  • Reliable, with 99.9% uptime and automatic data backup.

Use Cases Summary:

  • User account management, financial advice via AI chatbot, budget management, and financial goal tracking.

Architecture Design

FinFinity's design includes:

  • Context Diagram: Outlines the system's external interactions.
  • System Architecture: Covers logical and physical views, including the main components and their interactions.
  • UML Diagram: Provides a visual representation of the system's structure.

Glossary

  • FinFinity: Personal finance management app.
  • Functional/Non-Functional Requirements: Behaviors and quality attributes of the app.
  • Transaction Tracking, Budget Monitoring, Financial Reporting, AI Chatbot, Goal Setting: Key features of FinFinity.
  • Usability, Security, Performance, Reliability: Core quality attributes.

For detailed descriptions of use cases, architecture diagrams, and a full glossary, refer to the extended documentation.