Software Requirements Specification (SRS) for SplitEase

1. Introduction
1.1 Purpose

SplitEase is a web application designed to simplify group expense management. It enables users to
log shared expenses, track contributions, and settle outstanding balances efficiently. The app
ensures fairness when contributions differ and minimizes the number of transactions needed for
settlements. It also includes chat functionality, history tracking, and additional user-friendly features.

1.2 Scope

SplitEase allows users to:

 Enter expenses for shared activities (e.g., lunch, cab, drinks, etc.).

 Automatically calculate fair splits, even when contributions are unequal.

 Use a smart settlement algorithm to minimize payments.

 Chat with group members for better collaboration.

 View past expenses and settlement history.

 Access a user-friendly dashboard with expense insights.

The system will be available as a web application with potential mobile support in future iterations.

1.3 Definitions, Acronyms, and Abbreviations

 User: Any individual using the SplitEase application.

 Expense Group: A collection of users splitting an expense.

 Net Balance: The difference between what a user has paid and what they owe.

 Settlement: The final amount a user must pay or receive.

1.5 Overview

This document details the overall description, specific requirements, system attributes, and change
management process for SplitEase.

2. The Overall Description

SplitEase is an independent web-based application designed to streamline expense splitting.

2.1.1 System Interfaces

 Web-based frontend .

 Database for storing user expenses and history.

2.1.2 User Interfaces

 Chat interface for group discussions.

 Graphical breakdown of expenses and settlements.

2.1.3 Hardware Interfaces

 Standard web browsers on desktops and mobile devices.

2.1.5 Communications Interfaces

 Supports in-app messaging.

 Notifications via email and mobile alerts.

2.1.6 Memory Constraints

 Cloud storage for expenses, chat history, and user data.

2.1.7 Operations

 Users can create expense groups, add expenses, track settlements, and communicate via
chat.

2.1.8 Site Adaptation Requirements

 Can be hosted on cloud servers with scalability support.

2.2 Product Functions

 Expense Entry: Users can add expenses and categorize them.

 Smart Settlements: Algorithm optimizes payments to minimize transactions.

 Group Chat: Users can discuss expenses and settlements.

 History Compilation: Users can view past expenses and settlements.

 Notifications: Users receive alerts for pending settlements.

2.3 User Characteristics

 Target audience includes friends, roommates, and colleagues sharing expenses.

 Basic technical knowledge required for navigation.

2.4 Constraints

 Internet connectivity required.

 Limited storage for free-tier users.

2.5 Assumptions and Dependencies

 Users will input expenses accurately.

 Secure authentication systems in place.

 Core features like expense entry and settlements in Phase 1.

 Advanced features like AI-based spending insights in future updates.

3. Specific Requirements
3.1 Functions

 User registration and authentication.

 Expense management (add, edit, delete expenses).

 Settlement calculations and payment tracking.

3.2 Performance Requirements

 Should process settlements within milliseconds.

 Should handle up to 1000 concurrent users.

3.3 Logical Database Requirements

 Tables for users, expenses, settlements, and chat logs.

3.4 Design Constraints

 Follows Material UI design principles.

 Mobile responsiveness ensured.

3.4.1 Standards Compliance

 Complies with GDPR for data privacy.

3.5 Software System Attributes

3.5.1 Reliability

 99.9% uptime expected.

3.5.2 Availability

 Web-based and accessible 24/7.

3.5.3 Portability

 Compatible across devices and browsers.

3.6 Organizing the Specific Requirements

3.6.1 System Mode

 Online mode only.

3.6.2 User Class

 Regular users (expense participants).

 Users, Expenses, Transactions, Settlements.

3.6.4 Features

 Smart settlements, chat, notifications.

3.6.5 Stimulus

 Users add expenses or request settlements.

3.6.6 Response

 System calculates and displays results instantly.

3.6.7 Functional Hierarchy

 Expense entry → Grouping → Settlement → Payment processing.

3.7 Additional Comments

 Future updates will include AI-based spending analytics.

4. Change Management Process

 Feature requests and bugs reported via feedback form.

 Regular software updates and security patches.

5. Supporting Information

 Detailed algorithm documentation for settlement logic will be available separately.