Application-Specific Requirements for an Online Shopping System

Experiment no.03

1. Functional Requirements (FR)

These describe what the system should do.

1. User Account Management
   • Users shall be able to register, log in, and log out.
   • Users shall be able to update profile details and change passwords.
2. Product Catalog Management
   • The system shall allow browsing of products by categories, price, and brand.
   • The system shall provide a search option with filters (price, popularity, ratings).
   • Admin shall be able to add, update, or remove products.
3. Shopping Cart & Checkout
   • Users shall be able to add or remove products from the shopping cart.
   • The cart shall update total prices dynamically.
   • The system shall allow checkout with different payment methods (Credit/Debit Card, UPI, COD, Wallet).
4. Order Management
   • The system shall generate an order confirmation number.
   • Users shall be able to track order status (Pending, Shipped, Delivered, Cancelled).
   • Admin shall be able to update shipping details.
5. Payment & Security
   • The system shall integrate with secure payment gateways.
   • Users shall receive an invoice for every order.
   • Transactions shall be encrypted.
6. Customer Support
   • Users shall be able to contact support through chat or email.
   • Users shall be able to return/exchange products with proper authorization.

2. Non-Functional Requirements (NFR)

These describe quality attributes of the system.

1. Performance:
   • The system should support at least 1000 concurrent users.
   • Page load time should be < 3 seconds.
2. Security:
   • Passwords shall be stored in encrypted format.
   • Two-factor authentication shall be provided for login.
3. Usability:
   • The website shall have a responsive design (desktop, tablet, mobile).
   • Navigation shall be simple with minimal clicks to checkout.
4. Availability & Reliability:
   • The system should be available 99.9% of the time.
   • Backups shall be taken every 24 hours.
5. Scalability:
   • The system shall handle future growth in users, products, and transactions.

3. Domain-Specific Constraints

1. Compliance with e-commerce regulations (e.g., taxation, consumer protection).
2. GDPR compliance for user data privacy.
3. Integration with courier/warehouse APIs for real-time shipment tracking.

Assimilation into RE Model

The Requirements Engineering Model includes the following phases:

1. Requirement Elicitation

• Sources: Customers, sellers, delivery partners, payment providers.
• Methods: Interviews, surveys, prototyping, and document analysis.

2. Requirement Specification

• Documented in an SRS (Software Requirement Specification) format.
• Organized into Functional, Non-Functional, and Constraints (as listed above).

3. Requirement Analysis & Modeling

• Use Case Diagram:
  • Actors: User, Admin, Payment Gateway, Delivery Partner.
  • Use Cases: Register/Login, Search Products, Manage Cart, Checkout, Track Orders, Manage Products.
• Data Flow Diagram (DFD):
  • Shows flow of data between user, system, and database.
• ER Model:
  • Entities: User, Product, Order, Payment, Cart, Delivery.

4. Requirement Validation

• Walkthrough with stakeholders.
• Prototyping and feedback collection.
• Checking requirements for consistency, completeness, and feasibility.

5. Requirement Management

• Use of tools (e.g., JIRA, DOORS, Trello) for requirement tracking.
• Version control and traceability matrix for changes.