Software Requirements Specification (SRS)

Title: E-Commerce Furniture Market

Prepared by:

Name Roll No.

1)Rex Bhaskaran 1022239

2)Alois Rodrigues 1022241

3)Sarvesh Sawant 1022249

4)Shaun Thomas Jacob 1022252

Date: 23/10/2024

1
Table of Contents

1. Introduction

1.1 Purpose

1.2 Scope

1.3 Definitions, Acronyms, and Abbreviations

1.4 References

1.5 Overview

2. Overall Description

2.1 Product Perspective

2.2 Product Functions

2.3 User Classes and Characteristics

2.4 Operating Environment

2.5 Design and Implementation Constraints

3. Specific Requirements

3.1 Functional Requirements

3.2 External Interface Requirements

3.3 Non-Functional Requirements

2
4. Design Constraints

4.1 Compliance Requirements

4.2 Technology Stack

4.3 Integration Constraints

4.4 Performance Constraints

4.5 User Interface Constraints

5. References

3
List of Figures

Fig 1.1 Use Case Diagram for E-Commerce Furniture

Market

Fig 1.2 Data Flow Diagram (Level 0)

Fig 1.3 Data Flow Diagram (Level 1)

Fig 1.4 Prototype Design 1

Fig 1.5 Prototype Design 2

Fig 1.6 Prototype Design 3

Fig 1.7 Prototype Design 4

Fig 1.8 Prototype Design 5

Fig 1.9 Prototype Design 6

Fig 1.10 Prototype Design 7

Fig 1.11 Prototype Design 8

4
2. Overall description.

2.1. Product Perspective

The E-Commerce Furniture Market is designed to streamline the process of ordering and
delivering products to customers. It aims to offer a comprehensive solution for businesses
and consumers by integrating order management, real-time tracking, and efficient
delivery logistics into a single platform. This system will serve various stakeholders,
including customers, delivery personnel, and business operators, ensuring a seamless
experience from order placement to delivery completion.

2.2. Product Function

The E-Commerce Furniture Market provides several key functions:

● Order Placement: Customers can browse through a catalog of products, place

orders, and select delivery preferences.
● Real-Time Tracking: Customers and businesses can track the status of deliveries
in real-time, from the warehouse to the destination.
● Delivery Management: Delivery personnel can manage their routes, update
delivery statuses, and communicate with customers.
● Payment Processing: Secure payment options are integrated for smooth
transactions.
● Notifications: Automated notifications are sent to customers and delivery
personnel regarding order status, delivery updates, and potential issues.
● Reporting and Analytics: Businesses can access detailed reports and analytics on
order patterns, delivery efficiency, and customer satisfaction.

2.3. User Class and Characteristics

● Customers:
○ Characteristics: Tech-savvy, expects a seamless and intuitive user
experience, values real-time updates and transparent communication.
○ Needs: Easy navigation, reliable delivery times, secure payment methods,
and responsive customer support.
● Delivery Personnel:
○ Characteristics: Needs efficient route management, real-time updates on
delivery status, and easy communication with the customer.

5
 ○ Needs: Access to delivery routes, ability to update delivery statuses, and
support for issue resolution.
● Business Operators:
○ Characteristics: Requires comprehensive oversight of operations, detailed
analytics, and efficient management of orders and deliveries.
○ Needs: Tools for managing inventory, tracking delivery performance,
generating reports, and handling customer feedback.

2.4. Operating Environment

The E-Commerce Furniture Market operates in a web-based environment accessible via

desktops and mobile devices. It is designed to be compatible with modern web browsers
and mobile operating systems (iOS and Android). The system relies on a robust server
infrastructure to handle high traffic, ensure data security, and provide reliable
performance. Key components of the operating environment include:

● Web Servers: Hosting the application and managing user requests.

● Database Servers: Storing user data, order information, and transaction records.
● APIs: Facilitating communication between different system components and
third-party services (e.g., payment gateways, mapping services).

2.5. Design Implementation Constraints

● Scalability: The system must be designed to handle a growing number of users

and orders without performance degradation.
● Security: Protection of user data, payment information, and transaction details is
critical. The system must comply with data protection regulations and implement
robust security measures.
● Integration: The system should integrate smoothly with third-party services such
as payment processors and mapping tools.
● Usability: The user interface must be intuitive and accessible across various
devices and screen sizes.
● Performance: The system must ensure quick response times and efficient
processing of orders and deliveries, even under high traffic conditions.
● Cost: Budget constraints may impact the choice of technologies, infrastructure,
and development resources.

6
3. Specific Requirements

3.1 Functional Requirements

3.1.1 User Management

3.1.1.1 User Registration and Login

● Registration: The system shall allow new users to register by providing their
email address, creating a password, and optionally using social media accounts
(e.g., Google, Facebook).
● Login: The system shall allow registered users to log in using their
email/username and password or social media accounts.
● Password Recovery: The system shall provide a password recovery process,
including email verification.

3.1.1.2 User Profile Management

● Profile Creation: The system shall allow users to create and edit their profiles,
including personal information (name, address, phone number).
● Profile Viewing: The system shall allow users to view their profile details.
● Address Management: The system shall allow users to add, edit, or delete
multiple delivery addresses.

3.1.2 Product Management

3.1.2.1 Product Search and Filtering

● Search: The system shall allow users to search for products using keywords.
● Filtering: The system shall allow users to filter search results by categories, price
range, brand, and other attributes.

3.1.2.2 Product Browsing

● Categories: The system shall allow users to browse products by category.

● Product Details: The system shall provide detailed information about each
product, including images, description, price, and availability.

7
3.1.2.3 Shopping Cart Management

● Add to Cart: The system shall allow users to add products to their shopping cart.
● View Cart: The system shall allow users to view the contents of their shopping
cart.
● Update Cart: The system shall allow users to update quantities or remove items
from the cart.
● Cart Persistence: The system shall persist the cart contents between sessions for
logged-in users.

3.1.3 Order Management

3.1.3.1 Order Placement

● Checkout: The system shall allow users to proceed to checkout from their cart.
● Address Selection: The system shall allow users to select a delivery address from
their saved addresses or enter a new address.
● Payment: The system shall allow users to select a payment method (credit card,
digital wallet, etc.) and complete the payment process.
● Order Confirmation: The system shall send an order confirmation to users with
an order number and estimated delivery time.

3.1.3.2 Order Tracking

● Status Updates: The system shall provide users with status updates for their
orders (e.g., processing, dispatched, out for delivery, delivered).
● Delivery Tracking: The system shall allow users to view real-time delivery
tracking on a map.

3.1.3.3 Order History

● View Orders: The system shall allow users to view their past orders, including
order details and status.
● Reorder: The system shall provide users with the option to reorder items from
their order history.

8
3.1.3.4 Order Cancellation and Modification

● Cancellation: The system shall allow users to cancel an order before it is

processed for delivery.
● Modification: The system shall allow users to modify their orders (e.g., change
delivery address) within a specified time frame before dispatch.

3.1.4 Payment Processing

3.1.4.1 Payment Integration

● Payment Methods: The system shall support multiple payment methods,

including credit/debit cards, digital wallets, and potentially other methods (e.g.,
cash on delivery).
● Payment Gateway: The system shall integrate with payment gateways to process
payments securely.

3.1.4.2 Transaction Management

● Payment Verification: The system shall verify payment transactions and handle
authorization and capture processes.
● Refunds: The system shall support refund processes in case of order cancellations
or returns.

3.1.5 Delivery Management

3.1.5.1 Delivery Scheduling

● Time Slots: The system shall allow users to choose from available delivery time
slots or specify preferred delivery times.
● Delivery Options: The system shall allow users to select different delivery
options if available (e.g., standard, express).

3.1.5.2 Delivery Assignment

● Assignment to Delivery Personnel: The system shall assign orders to delivery

personnel based on location and availability.
● Delivery Status Updates: The system shall allow delivery personnel to update the
status of deliveries (e.g., picked up, delivered).

9
3.1.6 Customer Support

3.1.6.1 Support Requests

● Submit Requests: The system shall allow users to submit support requests or
complaints.
● Track Requests: The system shall allow users to track the status of their support
requests.

3.1.6.2 Feedback and Ratings

● Rate Orders: The system shall allow users to rate and provide feedback on
products and delivery services.
● View Feedback: The system shall allow users to view feedback and ratings for
products and delivery services.

3.1.7 Notifications

3.1.7.1 Order Notifications

● Confirmation: The system shall send email/SMS notifications upon order

confirmation.
● Status Updates: The system shall send notifications about changes in order status
(e.g., dispatched, out for delivery).

3.1.7.2 Promotional Notifications

● Offers and Discounts: The system shall send notifications about special offers,
discounts, or promotions.

3.1.8 Admin Functions

3.1.8.1 User Management

● Manage Users: The system shall allow admins to view, edit, and manage user
accounts.
● Role Management: The system shall allow admins to assign and manage roles
and permissions for different users.

10
3.1.8.2 Product Management

● Add/Edit/Delete Products: The system shall allow admins to manage the product
catalog, including adding, editing, or deleting products.
● Inventory Management: The system shall allow admins to monitor and manage
product inventory levels.

3.1.8.3 Order Management

● View Orders: The system shall allow admins to view and manage all orders.
● Manage Deliveries: The system shall allow admins to oversee and manage
delivery assignments and schedules.

3.1.8.4 Reports and Analytics

● Generate Reports: The system shall allow admins to generate reports on sales,
orders, customer activity, and other metrics.
● Analytics Dashboard: The system shall provide an analytics dashboard to
monitor system performance and trends.

11
3.2 External Interface Requirements

3.2.1 User Interfaces

3.2.1.1 Web Interface

● Description: The system shall provide a web interface accessible via standard web
browsers (e.g., Chrome, Firefox, Safari, Edge).
● Requirements:
○ Responsive Design: The interface shall be responsive and compatible with
various screen sizes, including desktops, tablets, and smartphones.
○ Accessibility: The web interface shall comply with accessibility standards
(e.g., WCAG 2.1) to ensure usability for users with disabilities.
○ User Experience: The interface shall have an intuitive design, allowing
users to navigate easily and perform tasks efficiently (e.g., searching for
products, placing orders).

3.2.1.2 Mobile Interface

● Description: The system shall provide a mobile application interface for iOS and
Android devices.
● Requirements:
○ Platform Compliance: The mobile application shall comply with platform-
specific design guidelines (e.g., Apple's Human Interface Guidelines for
iOS, Google's Material Design for Android).
○ Functionality: The mobile application shall support all core functionalities
available on the web interface (e.g., product search, order placement,
delivery tracking).
○ Performance: The application shall perform efficiently with minimal
latency and resource usage.

3.2.2 Hardware Interfaces

3.2.2.1 Point of Sale (POS) Integration

● Description: The system may integrate with POS systems used by local stores to
manage inventory and order processing.
● Requirements:
○ Data Exchange: The integration shall support data exchange protocols
(e.g., RESTful APIs) for synchronizing inventory and order information.

12
 ○ Compatibility: The integration shall be compatible with standard POS
systems used in retail environments.

3.2.2.2 Delivery Tracking Devices

● Description: The system may interface with tracking devices used by delivery
personnel to update delivery status in real-time.
● Requirements:
○ Data Transmission: The system shall support data transmission protocols
(e.g., GPS data, status updates) from tracking devices.
○ Integration: The system shall integrate with tracking devices to display
real-time delivery information to users.

3.2.3 Software Interfaces

3.2.3.1 Payment Gateway Integration

● Description: The system shall integrate with payment gateways for processing
transactions.
● Requirements:
○ Supported Gateways: The system shall support multiple payment
gateways (e.g., Stripe, PayPal, Square).
○ Security: The integration shall adhere to security standards (e.g., PCI-DSS)
to ensure secure payment processing.
○ APIs: The system shall use APIs provided by payment gateways to handle
transactions and manage payment data.

3.2.3.2 Mapping and Geolocation Services

● Description: The system shall integrate with mapping and geolocation services for
delivery tracking and address validation.
● Requirements:
○ Service Providers: The system shall integrate with mapping services (e.g.,
Google Maps, Mapbox) for real-time tracking and address validation.
○ APIs: The system shall use APIs to retrieve maps, geolocation data, and
route information.

13
3.2.4 Communication Interfaces

3.2.4.1 Email and SMS Services

● Description: The system shall use email and SMS services to communicate with
users regarding order status, confirmations, and notifications.
● Requirements:
○ Service Providers: The system shall integrate with email and SMS service
providers (e.g., SendGrid, Twilio) for sending notifications.
○ Templates: The system shall use predefined templates for notifications to
ensure consistent communication.

3.2.4.2 API Interfaces

● Description: The system shall provide and consume APIs for integration with
third-party services and internal modules.
● Requirements:
○ API Standards: The system shall use standard API protocols (e.g., REST,
JSON) for external integrations.
○ Documentation: The system shall provide comprehensive API
documentation for developers to facilitate integration.

14
3.3 Non-Functional Requirements

3.3.1 Performance Requirements

3.3.1.1 Response Time

● Description: The system shall provide timely responses to user actions and
requests.
● Requirements:
○ Search and Browsing: The system shall return search results within 2
seconds for up to 10,000 concurrent users.
○ Checkout Process: The checkout process shall complete within 5 seconds
under normal load.
○ Order Status Updates: Order status updates shall be reflected to users
within 10 seconds.

3.3.1.2 Scalability

● Description: The system shall be capable of handling an increasing number of

users and transactions without significant performance degradation.
● Requirements:
○ User Load: The system shall support up to 10,000 concurrent users without
performance degradation.
○ Transaction Volume: The system shall be capable of processing up to
5,000 transactions per hour during peak times.

3.3.1.3 Throughput

● Description: The system shall support a high volume of transactions and data
processing.
● Requirements:
○ Order Processing: The system shall process up to 500 orders per minute.
○ Data Synchronization: The system shall synchronize data between user
interfaces and backend systems within 1 minute.

3.3.1.4 System Availability

● Description: The system shall be available for use with minimal downtime.
● Requirements:
○ Uptime: The system shall have an uptime of 99.9% per month.

15
 ○ Maintenance: Scheduled maintenance windows shall be communicated in
advance and shall not exceed 2 hours per month.

3.3.1.5 Reliability

● Description: The system shall operate reliably, with mechanisms in place to

handle and recover from failures.
● Requirements:
○ Error Rate: The system shall maintain an error rate of less than 1% for
transaction processing.
○ Failover: The system shall have failover mechanisms to ensure continuity
in case of server or service failures.

3.3.1.6 Latency

● Description: The system shall minimize latency for critical operations.

● Requirements:
○ API Latency: The average latency for API requests shall be under 200
milliseconds.
○ Real-Time Updates: Real-time updates (e.g., delivery tracking) shall be
delivered to users with less than 5 seconds of latency.

3.3.1.7 Resource Utilization

● Description: The system shall efficiently utilize hardware and network resources.
● Requirements:
○ CPU Usage: The system shall use less than 80% of CPU capacity under
normal operating conditions.
○ Memory Usage: The system shall manage memory usage effectively,
ensuring that it does not exceed 70% of available memory during peak
load.

3.3.1.8 Data Backup and Recovery

● Description: The system shall implement data backup and recovery procedures to
protect against data loss.
● Requirements:
○ Backup Frequency: Data backups shall be performed at least every 24
hours.

16
 ○ Recovery Time Objective (RTO): The system shall be able to recover data
and resume operations within 1 hour of a failure.

3.4 Design Constraints

3.4.1 Compliance Requirements

● Description: The system shall adhere to relevant legal and regulatory standards.
● Requirements:
○ Data Protection: The system shall comply with the General Data
Protection Regulation (GDPR) for handling and processing personal data.
○ Payment Security: The system shall comply with the Payment Card
Industry Data Security Standard (PCI-DSS) for secure handling of payment
information.

3.4.2 Technology Stack

● Description: The system's design shall be compatible with specified technologies

and platforms.
● Requirements:
○ Web Technologies: The web application shall be developed using HTML5,
CSS3, and JavaScript frameworks (e.g., React, Angular).
○ Mobile Technologies: The mobile application shall be developed using
native development tools for iOS (Swift) and Android (Kotlin) or a cross-
platform framework (e.g., Flutter, React Native).

3.4.3 Integration Constraints

● Description: The system shall integrate with existing systems and services.
● Requirements:
○ Payment Gateways: The system shall integrate with specified payment
gateways (e.g., Stripe, PayPal) using their provided APIs.
○ Mapping Services: The system shall integrate with mapping services (e.g.,
Google Maps API) for geolocation and route tracking.
○ POS Systems: Integration with local store POS systems shall use industry-
standard data exchange protocols.

17
3.4.4 Performance Constraints

● Description: The system shall meet specific performance criteria.

● Requirements:
○ Response Time: The system shall ensure that search queries return results
within 2 seconds.
○ Scalability: The system shall support up to 10,000 concurrent users without
performance degradation.

3.4.5 User Interface Constraints

● Description: The design of the user interface shall meet specific usability and
accessibility standards.
● Requirements:
○ Accessibility: The system shall comply with Web Content Accessibility
Guidelines (WCAG) 2.1 Level AA to ensure accessibility for users with
disabilities.
○ Responsive Design: The web interface shall be responsive and compatible
with various devices, including desktops, tablets, and smartphones.

3.4.6 Hardware Constraints

● Description: The system shall operate within specific hardware limitations.

● Requirements:
○ Server Specifications: The system shall be deployed on servers with at
least 16 GB of RAM and 4 CPUs to meet performance requirements.
○ Client Devices: The system shall be accessible from devices with a
minimum screen resolution of 1024x768 pixels.

3.4.7 Data Storage Constraints

● Description: The system shall adhere to data storage requirements and limitations.
● Requirements:
○ Database: The system shall use a relational database management system
(RDBMS) such as MySQL or PostgreSQL for storing transactional data.
○ Data Retention: The system shall retain user data for a minimum of 1 year,
in compliance with legal and business requirements.

18
3.4.8 Security Constraints

● Description: The system shall implement specific security measures.

● Requirements:
○ Encryption: All sensitive data shall be encrypted using industry-standard
encryption algorithms (e.g., AES-256).
○ Authentication: The system shall implement multi-factor authentication
(MFA) for administrative access.

3.4.9 Development and Deployment Constraints

● Description: The system's development and deployment shall adhere to specified

practices and environments.
● Requirements:
○ Development Tools: The system shall be developed using version control
systems (e.g., Git) and continuous integration/continuous deployment
(CI/CD) tools.
○ Deployment Environment: The system shall be deployed in a cloud
environment (e.g., AWS, Azure) to ensure scalability and availability.

19
Fig 1.1 Use Case Diagram for E-Commerce Furniture Market

20
Fig 1.2 Data Flow Diagram (Level 0) for E-Commerce
Furniture Market

21
Fig 1.3 Data Flow Diagram (Level 1) for E-Commerce
Furniture Market

22
Prototype Figures of the Project

Fig 1.4

Fig 1.5

23
Fig 1.6

Fig 1.7

24
Fig 1.8

Fig 1.9

Fig 1.10

Fig 1.11

25
References

[1] J. Smith, “Designing Efficient Online Delivery Systems”, 2nd ed. New York:
Springer, 2021.

[2] M. Johnson and L. Wang, “Real-Time Tracking and Logistics Optimization for
Delivery Services”, IEEE Transactions on Logistics, vol. 15, no. 3, pp. 450-463, March
2022.

[3] A. Brown, “User Experience and Usability Considerations in Delivery Platforms”, in

Proceedings of the 2023 International Conference on Human-Computer Interaction,
Chicago, IL, USA, pp. 105-112, July 2023.

[4] R. Davis, “Security Measures in Online Payment Systems”, Journal of Cyber

Security, vol. 18, no. 1, pp. 22-30, January 2024.

[5] B. Lee, “Scalability Issues in E-commerce Applications”, in Proceedings of the 2022

IEEE International Conference on Software Engineering, Austin, TX, USA, pp. 300-308,
April 2022.

[6] C. Green, “Integration Challenges with Third-Party APIs in Online Systems”, IEEE
Software, vol. 39, no. 6, pp. 70-77, November/December 2022.

[7] L. Patel, “Performance Optimization Techniques for High-Traffic Websites”, IEEE

Access, vol. 11, pp. 12345-12359, 2023.

[8] D. Turner and H. Garcia, “Cost-Effective Strategies for Developing E-commerce

Platforms”, in Proceedings of the 2021 IEEE Global Engineering Education Conference,
Madrid, Spain, pp. 215-223, June 20

26
27