WEEK-1:

Development of problem statement.

The Online Shopping is an application intended for customers who want to shop online . The
main objective of this application is to make it interactive and its ease of use. It would make
searching, viewing and selection of a product easier. It contains a sophisticated search engine for
users to search for products specific to their needs. The search engine provides an easy and
convenient way to search for products where a user can search for a product interactively and the
search engine would refine the products available based on the user’s input. The user can then
view the complete specification of each product. They can also view the product reviews and
also write their own reviews. The application also provides a drag and drop feature so that a user
can add a product to the shopping cart by dragging the item in to the shopping cart.
WEEK-2:
Preparation of Software Requirement Specification Document.

1. Introduction

1.1 Purpose

This Software Requirements Specification (SRS) document outlines the requirements for the
development of an online shopping site, version 1.0. The document covers the complete scope of
the online shopping platform, including user interfaces, functional and non-functional
requirements, system architecture, and other critical aspects. The SRS encompasses the entire
system and does not limit itself to a single subsystem or component.

1.2 Document Conventions

This document follows specific conventions for clarity and consistency:

 Bold text is used to highlight section titles and important terms.

 Italic text indicates emphasis on particular items.
 Underlined text is reserved for hyperlinks or references to other documents.
 Numbered lists (e.g., 1., 2., 3.) are used for ordered sequences.
 Bulleted lists (e.g., -, •) are used for unordered items.
 Requirements are categorized by priority: High, Medium, and Low.
 Each requirement statement has a unique identifier (e.g., FR-1 for Functional
Requirements, NFR-1 for Non-Functional Requirements).

1.3 Intended Audience and Reading Suggestions

This SRS is intended for a variety of stakeholders involved in the development and deployment
of the online shopping platform, including:

 Developers: For understanding the functional and non-functional requirements of the

system.
 Project Managers: For planning, scheduling, and resource allocation.
 Marketing Staff: For insights into features and benefits that can be communicated to
potential users.
 End Users: For understanding the capabilities and limitations of the system.
 Testers: For developing test cases and ensuring the system meets the specified
requirements.
 Documentation Writers: For creating user manuals and help guides.

The document is organized as follows:

1. Overview: Start with sections 1 and 2 to get a general understanding of the system.
2. Functional Requirements: Focus on section 3 for detailed requirements.
 3. Non-Functional Requirements: Refer to section 4 for performance, security, and other
non-functional aspects.
4. Appendices and References: Consult the appendices and reference section for
supplementary information.

1.4 Product Scope

The online shopping site is designed to provide a comprehensive e-commerce solution, enabling
users to browse, search, and purchase products online. The platform supports various features
including user account management, product catalog, shopping cart, checkout process, order
tracking, and customer service. The primary goals of the online shopping site are:

 To provide a seamless and user-friendly shopping experience.

 To increase customer satisfaction and retention.
 To support a wide range of products and categories.
 To integrate with various payment gateways for secure transactions.
 To provide robust administrative tools for managing inventory, orders, and customer
data.

The online shopping site aligns with the company’s strategic objective to become a leading
online retailer by offering a superior digital shopping experience.

1.5 Acronyms

The following acronyms are used in this document:

 SRS: Software Requirements Specification

 UI: User Interface
 UX: User Experience
 HTTP: Hypertext Transfer Protocol
 HTTPS: Hypertext Transfer Protocol Secure
 SQL: Structured Query Language
 API: Application Programming Interface
 SKU: Stock Keeping Unit
 SSL: Secure Sockets Layer
 TOS: Terms of Service

1.6 References

 Das, Lucky. (2023). Online Shopping System (SRS Report).

 Chen, Su‐Jane, and Tung‐Zong Chang. "A descriptive model of online shopping process:
some empirical results." International Journal of Service Industry Management 14.5
(2003): 556-569.
1.6 Overview

The rest of the document deals with all the main features of this software. It not only describes
various functions but also gives details about how these functions are related to each other. Apart
from the data flow diagrams, the document also contains cost estimates for developing this
system. Various risks associated with the system have also been mentioned along with the ways
to mitigate them.

The timeline chart describing how the entire project was scheduled has been attached. At the
end, a pseudo code for the "customer management module" has been provided. A flow graph has
been generated corresponding to this module and test cases that were used to test the system have
also been mentioned.

2. Overall Description

2.1 Product Perspective

The online shopping site specified in this SRS is a new, self-contained product designed to
provide an integrated e-commerce solution. It is intended to replace and enhance the capabilities
of existing online shopping systems by offering improved user experience, enhanced security
features, and a wider range of functionalities.

This product will be a standalone application but can be integrated with other systems, such as
payment gateways, inventory management systems, and customer relationship management
(CRM) systems.

2.2 Product Functions

The online shopping site must perform several major functions, including but not limited to:

 User Account Management: Registration, login, profile management, and password

recovery.
 Product Catalog: Browsing, searching, and filtering products.
 Shopping Cart: Adding, updating, and removing items.
 Checkout Process: Entering shipping information, selecting payment methods, and order
confirmation.
 Order Management: Viewing order history, tracking orders, and managing returns.
 Customer Service: Accessing support, FAQs, and contact forms.
 Administrative Tools: Managing products, categories, inventory, orders, and user
accounts.

2.3 User Classes and Characteristics

The primary user classes for this product include:

  End Users: General customers who will browse, shop, and purchase products. They may
vary in technical expertise, frequency of use, and familiarity with online shopping.
 Administrators: Users with elevated privileges to manage the platform, including
product inventory, user accounts, and order processing. They are expected to have a
higher technical expertise.
 Customer Service Representatives: Users who assist end users with their queries and
issues. They need access to customer and order information but with limited
administrative privileges.
 Guest Users: Users who browse the site without creating an account. They have limited
access compared to registered end users.

2.4 Operating Environment

The software will operate in the following environment:

 Hardware Platform: Standard web servers and user devices (desktop computers, tablets,
smartphones).
 Operating System: Compatible with major operating systems, including Windows,
macOS, Linux for servers, and iOS, Android, and Windows for user devices.
 Web Browser: Compatible with modern web browsers such as Chrome, Firefox, Safari,
and Edge.
 Other Software Components: Integration with payment gateways (e.g., PayPal, Stripe),
inventory management systems, and CRM systems.

2.5 Design and Implementation Constraints

The development of the online shopping site will be subject to the following constraints:

 Corporate Policies: Adherence to company policies regarding data privacy, security, and
compliance with regulations such as GDPR.
 Hardware Limitations: Ensuring performance efficiency given memory and processing
constraints of the user devices and servers.
 Interfaces to Other Applications: Seamless integration with existing systems such as
payment gateways, inventory management, and CRM systems.
 Technology Stack: Use of specified technologies, tools, and databases (e.g., MySQL,
React.js, Node.js).
 Security Considerations: Implementation of SSL for secure communications, data
encryption, and regular security audits.
 Design Conventions: Adherence to company’s design guidelines and programming
standards.

2.6 User Documentation

The following user documentation will be delivered along with the software:

 User Manual: A comprehensive guide covering all features and functionalities.

  Online Help: Context-sensitive help available within the application.
 Tutorials: Step-by-step guides and video tutorials for common tasks.
 Quick Start Guide: A brief document to help users get started quickly.

The documentation will be provided in both digital formats (PDF, HTML) and physical copies if
required.

2.7 Assumptions and Dependencies

The following assumptions and dependencies could affect the requirements stated in this SRS:

 Third-Party Components: The project assumes the availability and integration of third-
party components such as payment gateways and inventory systems.
 Operating Environment Stability: Assumes the stability and compatibility of the
development and operating environments, including web browsers and operating
systems.
 User Access: Assumes users will have reliable internet access to use the online shopping
platform.
 Regulatory Changes: Assumes no significant changes in regulatory requirements that
could impact the system.
 Reusable Components: The project may reuse certain components from other projects,
assuming their availability and compatibility.

3. External Interface Requirements

3.1 User Interfaces

The user interfaces (UIs) for the online shopping site are designed to be intuitive, user-friendly,
and consistent with modern e-commerce standards. The following logical characteristics define
the UI:

 GUI Standards and Style Guides: The UI will adhere to the company's GUI standards
and style guides, ensuring consistency in colors, fonts, and layouts.
 Screen Layout Constraints: Each screen will have a header with the site logo and
navigation menu, a main content area, and a footer with links to important information
(e.g., terms of service, privacy policy).
 Standard Buttons and Functions: Common buttons such as "Add to Cart," "Buy Now,"
"Login," and "Sign Up" will be standardized across the platform. A "Help" button will be
available on every screen.
 Keyboard Shortcuts: Keyboard shortcuts will be implemented for common actions (e.g.,
Ctrl+F for search, Alt+C for cart).
 Error Message Display Standards: Error messages will be displayed in a user-friendly
manner, with clear instructions on how to resolve the issue. Errors will be highlighted in
red and placed near the relevant fields.
 User Interface Components: The following UI components are needed:
  Home Page: Featured products, search bar, categories.
 Product Page: Product details, images, reviews, add to cart button.
 Cart Page: List of items in the cart, total price, checkout button.
 Checkout Page: Shipping information, payment options, order summary.
 User Account Pages: Login, registration, profile management, order history.
 Admin Interface: Product management, order management, user management.

Details of the user interface design will be documented in a separate user interface specification.

3.2 Hardware Interfaces

The online shopping site will interface with various hardware components, including:

 Supported Device Types: The site will support desktops, laptops, tablets, and
smartphones.
 Data and Control Interactions: The site will interact with hardware to handle user
inputs (e.g., keyboard, mouse, touchscreens) and display outputs (e.g., screens, printers).
 Communication Protocols: Standard protocols such as USB, HDMI, and Wi-Fi will be
used for data transfer and communication with peripheral devices like barcode scanners
and receipt printers in a retail environment.

3.3 Software Interfaces

The online shopping site will interact with various software components, including:

 Databases: The site will use a relational database (e.g., MySQL) to store user data,
product information, orders, and other relevant data.
 Incoming Data: User input (registration, login), product data updates, order
details.
 Outgoing Data: User information for profile display, product details for
browsing, order confirmation details.
Operating Systems: The site will be compatible with major operating systems, including
Windows, macOS, Linux for servers, and iOS, Android, and Windows for user devices.
Tools and Libraries: The site will use various development tools and libraries (e.g.,
React.js for the frontend, Node.js for the backend).
Integrated Commercial Components: Integration with payment gateways (e.g., PayPal,
Stripe) and third-party analytics tools (e.g., Google Analytics).
APIs: The site will expose and consume APIs for data exchange between the online
shopping platform and other systems (e.g., inventory management, CRM).
 Data Sharing: User information, product details, order status.
 Implementation Constraints: Data sharing will be implemented using RESTful
APIs with JSON format.

3.4 Communications Interfaces

The online shopping site will require various communications functions, including:
  E-mail: Automated e-mails for order confirmations, password resets, promotional offers.
The SMTP protocol will be used for sending emails.
 Web Browser: The site will be accessed via web browsers, using HTTPS for secure
communication.
 Network Server Communications Protocols: The site will use HTTP/HTTPS for web
communication and RESTful APIs for server interactions.
 Message Formatting: JSON will be used for data exchange in APIs. E-mails will be
formatted using HTML for rich text content.
 Communication Standards: The site will adhere to standards such as SSL/TLS for
secure communications, ensuring data integrity and privacy.
 Communication Security: All communications will be encrypted using SSL/TLS. Data
transfer rates will be optimized to ensure fast and reliable user interactions.
Synchronization mechanisms will ensure data consistency across different components
and systems.

4. System Features
4.1 User Account Management

4.1.1 Description and Priority

The User Account Management feature allows users to register, log in, manage their profiles,
and recover passwords. This feature is of High priority as it is essential for user interaction with
the platform.

4.1.2 Stimulus/Response Sequences

 Registration: User provides required details → System creates a new account and sends
a confirmation email.
 Login: User enters credentials → System authenticates and redirects to the dashboard.
 Profile Management: User updates profile details → System saves changes and
confirms the update.
 Password Recovery: User requests password reset → System sends a reset link via
email.

4.1.3 Functional Requirements

 REQ-1: The system shall allow users to register with a unique email address and
password.
 REQ-2: The system shall authenticate users using their email address and password.
 REQ-3: The system shall provide an interface for users to update their profile
information.
 REQ-4: The system shall allow users to reset their passwords via a secure email link.
4.2 Product Catalog
4.2.1 Description and Priority

The Product Catalog feature allows users to browse, search, and filter products. This feature is of
High priority as it is critical for the shopping experience.

4.2.2 Stimulus/Response Sequences

 Browsing: User navigates to the product catalog → System displays products with
pagination.
 Searching: User enters search query → System returns relevant products.
 Filtering: User applies filters (e.g., price range, category) → System updates product
display based on filters.

4.2.3 Functional Requirements

 REQ-1: The system shall display a list of products with images, names, and prices.
 REQ-2: The system shall provide a search bar for users to search for products.
 REQ-3: The system shall allow users to filter products based on predefined criteria.
 REQ-4: The system shall support pagination to display large numbers of products.
4.3 Shopping Cart

4.3.1 Description and Priority

The Shopping Cart feature allows users to add, update, and remove items before proceeding to
checkout. This feature is of High priority as it directly impacts sales.

4.3.2 Stimulus/Response Sequences

 Adding Items: User adds a product to the cart → System confirms the addition and
updates the cart count.
 Updating Items: User changes the quantity of a product → System recalculates the total
price.
 Removing Items: User removes a product from the cart → System updates the cart and
total price.

4.3.3 Functional Requirements

 REQ-1: The system shall allow users to add products to their shopping cart.
 REQ-2: The system shall display the current items in the user's shopping cart.
 REQ-3: The system shall allow users to update the quantity of products in the cart.
 REQ-4: The system shall allow users to remove products from the cart.
 REQ-5: The system shall display the total price of the items in the cart.
4.4 Checkout Process

4.4.1 Description and Priority

The Checkout Process feature enables users to enter shipping information, select payment
methods, and confirm orders. This feature is of High priority as it completes the sales
transaction.

4.4.2 Stimulus/Response Sequences

 Shipping Information: User enters shipping details → System validates and saves the
information.
 Payment Selection: User selects a payment method → System processes the payment.
 Order Confirmation: User reviews and confirms the order → System generates an order
summary and sends a confirmation email.

4.4.3 Functional Requirements

 REQ-1: The system shall provide a form for users to enter shipping information.
 REQ-2: The system shall validate the shipping information entered by the user.
 REQ-3: The system shall support multiple payment methods, including credit card and
PayPal.
 REQ-4: The system shall process the payment and confirm the transaction.
 REQ-5: The system shall generate and display an order summary upon confirmation.
 REQ-6: The system shall send an order confirmation email to the user.
4.5 Order Management

4.5.1 Description and Priority

The Order Management feature allows users to view their order history, track orders, and
manage returns. This feature is of Medium priority.

4.5.2 Stimulus/Response Sequences

 View Order History: User navigates to order history → System displays past orders.
 Track Order: User selects an order to track → System displays the current status of the
order.
 Manage Returns: User initiates a return → System processes the request and updates the
order status.

4.5.3 Functional Requirements

 REQ-1: The system shall display the user's order history with details of each order.
 REQ-2: The system shall allow users to view the status of their current orders.
 REQ-3: The system shall provide a mechanism for users to initiate returns.
 REQ-4: The system shall update the status of orders based on return requests.
4.6 Customer Service

4.6.1 Description and Priority

The Customer Service feature provides users with access to support, FAQs, and contact forms.
This feature is of Medium priority.

4.6.2 Stimulus/Response Sequences

 Access Support: User navigates to the support page → System displays support options.
 View FAQs: User selects FAQ section → System displays frequently asked questions
and answers.
 Submit Query: User fills out contact form → System sends the query to customer
service.

4.6.3 Functional Requirements

 REQ-1: The system shall provide a support page with various support options.
 REQ-2: The system shall display a list of frequently asked questions and answers.
 REQ-3: The system shall provide a contact form for users to submit queries.
 REQ-4: The system shall route queries to the appropriate customer service
representative.
4.7 Administrative Tools

4.7.1 Description and Priority

The Administrative Tools feature enables administrators to manage products, categories,

inventory, orders, and user accounts. This feature is of High priority for maintaining the
platform.

4.7.2 Stimulus/Response Sequences

 Manage Products: Admin adds/updates/removes products → System updates the

product catalog.
 Manage Orders: Admin views and processes orders → System updates order status.
 Manage Users: Admin views and manages user accounts → System updates user
information.

4.7.3 Functional Requirements

 REQ-1: The system shall allow administrators to add, update, and remove products from
the catalog.
 REQ-2: The system shall allow administrators to view and process orders.
 REQ-3: The system shall allow administrators to manage user accounts.
 REQ-4: The system shall provide reports on inventory levels, sales, and user activity.

5. Other Nonfunctional Requirements

5.1 Performance Requirements

The performance requirements for the online shopping site ensure that the system remains
responsive and efficient under various conditions. Key performance requirements include:

 Response Time: The system shall respond to user inputs within 2 seconds under normal
conditions. For critical operations such as adding items to the cart and checkout, the
response time should be less than 1 second.
 Throughput: The system shall handle up to 1,000 concurrent users without performance
degradation.
 Scalability: The system shall be able to scale horizontally to handle increased loads,
supporting up to 10,000 concurrent users during peak times, such as sales events.
 Data Processing: The system shall process batch updates (e.g., inventory updates) within
5 minutes.
 Availability: The system shall maintain an uptime of 99.9%, translating to a maximum of
8.76 hours of downtime per year.

5.2 Safety Requirements

Safety requirements focus on preventing loss, damage, or harm that could result from using the
online shopping site:

 Data Integrity: The system shall ensure data integrity by implementing transaction
mechanisms to prevent data loss during updates.
 Error Handling: The system shall gracefully handle errors and provide meaningful error
messages to users. Critical errors shall be logged, and alerts shall be sent to the support
team.
 Compliance: The system shall comply with industry standards and regulations, such as
PCI DSS for payment processing and GDPR for data protection.
 Backup and Recovery: The system shall perform regular backups (daily) and support
full recovery within 4 hours in the event of data loss.

5.3 Security Requirements

Security requirements address the protection of data and user privacy:

 Authentication: The system shall require users to authenticate using a username and
password. Multi-factor authentication (MFA) shall be available as an option.
 Authorization: The system shall enforce role-based access control (RBAC) to restrict
access to administrative functions based on user roles.
 Encryption: All sensitive data, including personal information and payment details, shall
be encrypted in transit (using TLS) and at rest (using AES-256).
 Data Privacy: The system shall adhere to privacy policies and regulations, ensuring that
user data is not shared without consent.
 Security Audits: Regular security audits shall be conducted to identify and mitigate
vulnerabilities.
5.4 Software Quality Attributes

Quality attributes outline the essential characteristics of the software:

 Usability: The system shall be designed with a user-friendly interface, ensuring ease of
navigation and accessibility for all users.
 Reliability: The system shall operate reliably under various conditions, with mechanisms
in place for fault tolerance and automatic recovery.
 Maintainability: The system shall be modular, with well-documented code to facilitate
easy maintenance and updates.
 Interoperability: The system shall be compatible with external systems, including
payment gateways, shipping providers, and third-party APIs.
 Testability: The system shall be designed to support automated testing, ensuring that
new features and updates do not introduce regressions.
 Portability: The system shall be deployable on various platforms and environments,
including cloud services and on-premises servers.

5.5 Business Rules

Business rules govern the operational principles of the online shopping site:

 User Roles: Only registered users can make purchases. Admin users have additional
privileges, such as managing products and orders.
 Pricing and Discounts: The system shall support various pricing models, including
discounts, promotions, and dynamic pricing based on user behavior.
 Return Policy: Users can initiate returns within 30 days of purchase. The system shall
enforce this policy and handle return processing.
 Inventory Management: The system shall automatically update inventory levels based
on sales and restocks, preventing overselling of out-of-stock items.
 Order Processing: Orders shall be processed in the order they are received. The system
shall handle payment authorization, shipping calculation, and order confirmation.

6. Other Requirements

Database Requirements

The online shopping site shall utilize a relational database management system (RDBMS) to
store and manage data. Specific database requirements include:

 Schema Design: The database shall be designed to efficiently store product information,
user profiles, orders, and other relevant data.
 Data Integrity: The database shall enforce referential integrity and constraints to
maintain data consistency.
 Scalability: The database architecture shall support horizontal scalability to
accommodate future growth.
  Backup and Recovery: Regular backups shall be performed to prevent data loss, and a
disaster recovery plan shall be in place to restore data in case of emergencies.

Internationalization Requirements

The online shopping site shall support multiple languages and currencies to cater to a global
audience. Internationalization requirements include:

 Language Support: The user interface shall be translatable into multiple languages, with
support for language-specific content.
 Currency Conversion: Prices shall be displayed in the user's preferred currency, with
real-time conversion rates updated regularly.
 Localization: Date formats, address formats, and other regional preferences shall be
customizable based on the user's location.

Legal Requirements

The online shopping site shall comply with relevant laws and regulations governing e-commerce,
data protection, and consumer rights. Legal requirements include:

 GDPR Compliance: The site shall adhere to the General Data Protection Regulation
(GDPR) to protect user privacy and data rights.
 PCI DSS Compliance: Payment processing shall comply with the Payment Card
Industry Data Security Standard (PCI DSS) to ensure secure handling of credit card
information.
 Tax Regulations: The site shall calculate and apply appropriate taxes based on the user's
location and the type of products purchased.

Reuse Objectives

The project shall prioritize code reuse and modularity to facilitate future development and
maintenance. Reuse objectives include:

 Component Reusability: Common functionalities such as user authentication, product

catalog management, and order processing shall be designed as reusable components.
 Code Documentation: Reusable code components shall be well-documented to aid in
understanding and reuse by other developers.

Appendix A: Glossary

Acronyms and Abbreviations

 RDBMS: Relational Database Management System

 GDPR: General Data Protection Regulation
 PCI DSS: Payment Card Industry Data Security Standard