Skip to content

Latest commit

 

History

History
153 lines (109 loc) · 4.48 KB

SRS.md

File metadata and controls

153 lines (109 loc) · 4.48 KB
Raw

Software Requirements Specification (SRS) for Blinkit App

Table of Contents

  1. Introduction
  2. Overall Description
  3. Functional Requirements
  4. Non-Functional Requirements
  5. Use Case Descriptions

1. Introduction

The Blinkit app is designed to provide users with a seamless platform for ordering groceries, essentials, and other goods for fast delivery. This document outlines the software requirements and detailed use cases for the Blinkit application.

2. Overall Description

2.1 Purpose

The purpose of this document is to specify the requirements for developing a user-friendly, scalable, and secure Blinkit app.

2.2 Scope

The Blinkit app allows users to:

  • Order groceries and essentials online.
  • Track real-time delivery status.
  • Manage multiple payment options.
  • Provide reviews and feedback.

2.3 Assumptions and Dependencies

  • Users must have internet access to use the app.
  • The app depends on integration with third-party APIs for payments and delivery tracking.
  • Inventory availability is managed by retail partners.

3. Functional Requirements

3.1 User Management

  • Register and log in using email/phone or social accounts.
  • Manage user profiles, addresses, and payment preferences.

3.2 Product Management

  • Browse and search for products by category or keyword.
  • View product details, pricing, and availability.

3.3 Cart and Checkout

  • Add or remove products from the cart.
  • Apply discounts, promo codes, and offers.
  • Select delivery address and payment method.

3.4 Order Tracking

  • Real-time updates on order status.
  • View estimated delivery time.

3.5 Payments

  • Support for UPI, credit/debit cards, and wallet payments.
  • Secure payment processing.

3.6 Reviews and Ratings

  • Allow users to rate and review delivered products.
  • View aggregated ratings and feedback on products.

4. Non-Functional Requirements

4.1 Performance

  • The app should handle 10,000 concurrent users without significant downtime.

4.2 Security

  • Implement two-factor authentication for login.
  • Encrypt sensitive user data and payment information.

4.3 Usability

  • Provide an intuitive and accessible user interface.

4.4 Availability

  • Ensure 99.9% uptime with proper server monitoring and scaling.

5. Use Case Descriptions

5.1 Use Case 1: User Registration and Login

Actors: User, System
Description: A new user registers using email/phone or logs in with existing credentials.

Steps:

  1. User enters email/phone and password or selects a social login option.
  2. System verifies credentials.
  3. User gains access to their account.

Precondition: User must have a valid email/phone or social media account.
Postcondition: User account is created or accessed.

5.2 Use Case 2: Search for Products

Actors: User, System
Description: A user searches for products by keyword or category.

Steps:

  1. User enters a keyword or selects a category.
  2. System displays matching products.
  3. User selects a product to view its details.

Precondition: Products are listed in the system.
Postcondition: User views the desired product.

5.3 Use Case 3: Place an Order

Actors: User, System, Delivery Partner
Description: A user selects items, adds them to the cart, and completes the order.

Steps:

  1. User adds items to the cart.
  2. User proceeds to checkout and selects payment and delivery options.
  3. System processes the payment and confirms the order.
  4. Delivery partner picks up and delivers the order.

Precondition: Selected items are in stock.
Postcondition: Order is placed and tracked for delivery.

5.4 Use Case 4: Track an Order

Actors: User, System, Delivery Partner
Description: A user tracks the status of their order in real-time.

Steps:

  1. User navigates to the "My Orders" section.
  2. System displays the current status and estimated delivery time.
  3. Delivery partner updates the status as they progress.

Precondition: Order is successfully placed.
Postcondition: User receives updates until the order is delivered.

5.5 Use Case 5: Provide Product Feedback

Actors: User, System
Description: A user provides feedback on delivered products.

Steps:

  1. User navigates to the "Order History" section.
  2. User selects an order to rate and review.
  3. System stores the feedback and updates the product’s rating.

Precondition: Order is marked as delivered.
Postcondition: Feedback is stored and displayed for future reference.