Chit Fund System Requirements Document

1. Introduction

This document outlines the system requirements for the Chit Fund project, a cross-platform application designed to manage chit funds in Tamil Nadu. The application will support both individual members and chit organizers, providing a comprehensive platform for managing financial transactions and member interactions.

2. System Overview

The Chit Fund application is intended to streamline the management of chit funds, offering functionalities for both organizers and members. It will be developed using React Native, Expo, and TypeScript for the frontend, ensuring compatibility across web, Android, iOS, and tablet platforms. Supabase will be used for backend services, including database management, authentication, storage, and messaging.

2a. Product Interpretation and Delivery Boundary

• Domain Descriptors:

  • Chit Fund Management: The application is designed to manage chit funds, including member and organizer functionalities.
  • Financial Transactions Management: The application handles various financial transactions related to chit funds.

• What is being built:

  • A cross-platform chit fund management application for Tamil Nadu, supporting both individual members and chit organizers.

• Excluded Assumptions:

  • Generic e-commerce features
  • Unrelated enterprise modules

• Custom Pages:

  • Company Management
  • Branch Management
  • User & Role Management
  • Customer Management
  • Customer Portal
  • Chit Management
  • Organizer Dashboard
  • Member Portal
  • Chit Agreement & Registration
  • Ticket Management
  • Membership Management
  • Instalment Management
  • Collection Management
  • Payment Management
  • Payment Allocation
  • Payment Reversal
  • Receipt Management
  • Draw / Auction Management
  • Draw / Auction Minutes
  • Outstanding & Overdue Management
  • Document Management
  • Dashboard & Business Overview
  • Reports & Exports
  • Global Search
  • System Administration & Settings
  • Landing
  • Authentication

• Access:

  • Application-owned identity with authentication and security measures.

• Behavior Contracts:

  • Branch Management: Admin manages branches (create, update, deactivate).
  • User & Role Management: Admin manages users and roles.
  • KYC & Customer Documents: Customer submits KYC and documents.
  • Nominee Management: Customer adds or updates nominee information.
  • Subscriber / Chit Joining Management: Customer joins a chit as a subscriber.
  • Customer Statements: Customer requests statements.
  • Notification Management: System sends notifications to users.
  • Global Search: User enters a search query from any main application page.
  • Audit Trail Logging: Any user or system action that modifies application data.
  • Tenant / Company Data Isolation Enforcement: Any data access or modification request.
  • Automated Backup & Recovery: Scheduled backup interval or manual recovery request.
  • System Administration & Settings Management: Administrator accesses system settings interface.
  • API & Integration Layer Access: External system sends API request.
  • Monitoring & Error Management: System detects error, exception, or performance anomaly.
  • Chit Creation and Management: Organizer initiates creation or management of a chit group.
  • Chit Participation and Payment: Member joins a chit and makes scheduled payments.

2c. Page Content and Component Coverage

For each custom page, the application will provide a balanced set of information, actions, and supporting context. Each page will include applicable empty/loading/success/error states, ensuring a mature MVP composition for its accepted personas.

3. Functional Requirements as Story Points

• As a Chit Organizer, I should be able to manage chit groups, including creation, updates, and status changes.
• As a Company Admin, I should be able to manage branches, users, and roles.
• As a Customer, I should be able to submit KYC documents and manage nominee information.
• As a Customer, I should be able to join chits and make payments.
• As a Customer, I should be able to request and view statements.
• As a System, I should send notifications to users.
• As an Authenticated User, I should be able to perform global searches across modules.
• As a System, I should log all actions that modify application data.
• As a System, I should enforce tenant/company data isolation.
• As a System, I should perform automated backups and recoveries.
• As a System Administrator, I should be able to update system settings.
• As an External System, I should be able to access the API and integration layer.
• As a System, I should monitor and manage errors and performance anomalies.

4. User Personas

• Chit Organizer: Responsible for creating and managing chit groups.
• Individual Member: Participates in chit groups and manages personal financial transactions.
• Company Admin: Manages branches, users, and roles within the application.
• System Administrator: Oversees system settings and configurations.

5. Core User Flows

1. Chit Organizer Flow:

   • Access the Organizer Dashboard.
   • Create or manage chit groups.
   • Update chit group details and status.

2. Individual Member Flow:

   • Access the Member Portal.
   • Join a chit and make payments.
   • View personal statements and notifications.

3. Company Admin Flow:

   • Access the Admin Dashboard.
   • Manage branches, users, and roles.

4. Customer Flow:

   • Access the Customer Portal.
   • Submit KYC documents and manage nominee information.

6. Visuals Colors and Theme

• Primary: #007BFF
• Primary Light: #66B2FF
• Secondary: #6C757D
• Accent: #28A745
• Highlight: #FFC107
• Background: #F8F9FA
• Surface: #FFFFFF
• Text: #212529
• Text Muted: #6C757D
• Border: #DEE2E6

7. Signature Design Concept

The design concept for the Chit Fund application will focus on a clean, modern interface that emphasizes usability and accessibility. The landing page will feature a dynamic hero section with subtle animations to engage users. The overall design will use a consistent color palette and typography to ensure a cohesive user experience across all platforms.

8. Interaction Model & Motion Direction

The interaction model will be animated, featuring moderate scroll-triggered reveals and hover transitions. This approach will provide a polished user experience while maintaining clarity and usability.

9. Non-Functional Requirements

• Cross-platform support: The application must function seamlessly across web, Android, iOS, and tablet platforms.
• Authentication & Security: Secure access control and data protection measures must be implemented.
• Data Isolation: Tenant/company data must be isolated to prevent unauthorized access.
• Backup & Recovery: Automated backup and recovery processes must be in place to ensure data integrity.

10. Tech Stack

• Frontend: React Native, Expo, TypeScript
• Backend: Supabase (including database, authentication, storage, and messaging)

11. Assumptions and Constraints

• The application will not include generic e-commerce features or unrelated enterprise modules.
• The application will rely on Supabase for backend services, including database management and authentication.

12. Glossary

• Chit Fund: A type of rotating savings and credit association system practiced in India.
• KYC: Know Your Customer, a process of verifying the identity of customers.
• Supabase: An open-source Firebase alternative providing backend services.

This document provides a comprehensive overview of the requirements for the Chit Fund project, ensuring a clear understanding of the application's scope and functionality.