Page 1 of 5

System Requirements Document for simple-ui

1. Introduction

This document outlines the system requirements for the "simple-ui" project, which facilitates the sale of digital license keys through an online platform. The application includes both user-facing and administrative functionalities, leveraging Firebase for data management and Razorpay for payment processing.

2. System Overview

The system is designed to manage products, durations, prices, license keys, coupons, and orders. It provides a user-friendly interface for customers to purchase license keys and an administrative interface for managing the store's operations.

3. Functional Requirements

User Stories

Page 2 of 5

Customer

As a customer, I want to select a product from a list of available products.
As a customer, I want to select a duration for the product I choose.
As a customer, I want to apply a coupon code to receive a discount on my purchase.
As a customer, I want to view the total price, including any discounts, before making a purchase.
As a customer, I want to initiate a payment using Razorpay.
As a customer, I want to receive a license key immediately after a successful payment.
As a customer, I want to download an invoice for my purchase.
As a customer, I want to download an APK if available after my purchase.
As a customer, I want to copy my license key to the clipboard for easy access.
As a customer, I want to view the amount paid after a successful transaction.
As a customer, I want to see the original price of the product before any discounts are applied.
As a customer, I want to view detailed payment information, including payment ID and status.
As a customer, I want to view detailed product information, including product name and duration.

Page 3 of 5

Admin

As an admin, I want to log in using a username and password.
As an admin, I want to view a dashboard with total orders, sales, and revenue.
As an admin, I want to manage products, including adding, editing, and deleting them.
As an admin, I want to manage durations for each product.
As an admin, I want to set and manage prices for product-duration combinations.
As an admin, I want to manage license keys, including importing and adding single keys.
As an admin, I want to view stock summaries of license keys.
As an admin, I want to manage coupons, including creating and deleting them.
As an admin, I want to view and search through orders, both paid and failed.
As an admin, I want to configure payment settings, including Razorpay and admin credentials.
As an admin, I want to configure APK download settings.
As an admin, I want to replace placeholder configurations with actual settings in the system.

4. User Personas

Customer

A user who visits the store to purchase digital license keys for various products.

Admin

A user responsible for managing the store's operations, including products, prices, orders, and settings.

5. Core User Flows

Page 4 of 5

Customer Purchase Flow

Customer selects a product.
Customer selects a duration.
Customer applies a coupon code (optional).
Customer views the total price.
Customer initiates payment via Razorpay.
Customer receives a license key and invoice upon successful payment.
Customer downloads the APK if available.

Admin Management Flow

Admin logs in with credentials.
Admin views the dashboard with key metrics.
Admin manages products, durations, prices, keys, coupons, and orders.
Admin configures payment and APK settings.

6. Visuals Colors and Theme

The application uses a modern, dark theme with a color palette that includes shades of blue, green, and white for a professional and sleek appearance.

7. Signature Design Concept

The design emphasizes simplicity and ease of use, with a focus on clear navigation and accessibility.

8. Interaction Model & Motion Direction

The application uses a responsive design with smooth transitions and animations to enhance user experience.

Page 5 of 5

9. Non-Functional Requirements

The system must be highly available and scalable to handle peak loads.
The system must ensure data security and privacy.
The system should provide a responsive user interface across devices.

10. Tech Stack

Frontend: React.js
Backend: Python + FastAPI
Database: Firebase Realtime Database
Payment Gateway: Razorpay

11. Assumptions and Constraints

The system assumes internet connectivity for accessing Firebase and Razorpay services.
The system is constrained by the features and limitations of the Firebase and Razorpay APIs.

12. Glossary

Product: A digital item available for purchase.
Duration: The time period for which a product is valid.
License Key: A unique code provided to the customer upon purchase.
Coupon: A code that provides a discount on the purchase.
Razorpay: A payment gateway used for processing transactions.
APK: Android Package Kit, a file format for distributing Android apps.

simple-ui

Comments (0)