Moodhar SRS

Software requirements Specification for Spare parts E-commerce Website

Maxamed Ibraahim wacays

C/casiis Maxamuud Camuud

2/27/24 Software Project Managemen

Table of Contents
1. Introduction
1.1 Purpose
1.2 Intended Audience and Reading Suggestions
1.3 Product Scope
1.4 References
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
2.6 Assumptions and Dependencies
3. External Interface Requirements
3.1 User Interfaces
3.2 Software Interfaces
3.3 Communications Interfaces
4. Analysis Models
4.1 Customer Use case diagram
4.2 Seller Use case diagram
4.3 ER diagram
5. System Features
5.1 User Accounts
5.2 The search facility
5.3 Shopping cart facility
5.4 Payment
5.5 Order and returns
5.6 Other system features
5.7 Seller features
6. Other Nonfunctional Requirements
6.1 Performance Requirements
6.2 Safety Requirements
6.3 Security Requirements
6.4 Software Quality Attributes
6.5 Business Rules
7. Other Requirements Appendix A: Glossary Appendix B: Field Layouts Appendix C:
Requirement Traceability matrix

1
1. Introduction
This Software Requirements Specification (SRS) outlines the essential details for developing an
efficient and user-friendly E-commerce Spare Parts Shop. The project focuses on simplifying
spare parts procurement, offering a diverse catalog, advanced search features, secure
transactions, and a seamless user experience. This document serves as a roadmap, ensuring the
development team aligns with stakeholder expectations, delivering a high-quality e-commerce
platform for the automotive and machinery spare parts market.

1.1 Purpose
The e-commerce spare parts shop website aims to be a one-stop platform for convenient
procurement of automotive and machinery spare parts. It focuses on easy navigation, secure
transactions, detailed product information, order tracking, efficient inventory management,
competitive pricing, and global accessibility. The goal is to enhance the overall spare parts
shopping experience for individuals and businesses through customer feedback, support, and
promotional activities.

1.2 Intended Audience and Reading Suggestions

The e-commerce platform serves a diverse user base including individual consumers, mechanics,
enthusiasts, retailers, distributors, and manufacturers worldwide. It offers a wide range of
automotive products and facilitates efficient transactions, catering to personal, professional, and
global needs within the automotive [Link] serving this diverse audience, the E-commerce
Spare Parts Shop Website aims to become a central platform for efficient and transparent spare
parts transactions.

1.3 Product Scope

SRS Scope: E-commerce Spare Parts Shop
The Software Requirements Specification (SRS) scope for the E-commerce Spare Parts Shop
encompasses the following aspects:

1. Platform Functionality User authentication, browsing, cart, checkout, and order

management.
2. Product Catalog Listing, categorization, pricing, and inventory management.
3. User Interface Design Intuitive and responsive design.
4. Security HTTPS, data encryption, and threat protection.
5. Payment Integration Secure payment gateways.
6. Order Processing Confirmation emails, shipping integration.
7. User Feedback: Moderated feedback and reviews.
8. Customer Support: Contact form, FAQ, and ticket system.
9. Performance Fast loading and scalability.
10. Compliance Data protection and e-commerce regulations.

2
11. Documentation: User manuals and training materials.
12. Maintenance Regular updates and bug fixes.
This scope aims to deliver a secure, user-friendly platform for efficient spare parts purchasing.

1.4 Definitions, Acronyms and Abbreviations

SPEW Spare Parts E-commerce Website

FAQs Frequently Asked Questions

ODM Object Document Modeling

CRUD Create Read Update Delete

UML Unified Modeling Language

HTTPS HyperText Transfer Protocol Secure

HTML Hypertext markup language

2. Overall Description
This section includes details about what is and is not expected of the SPEW system in addition
to which cases are intentionally unsupported and assumptions that will be used in the creation of
the SPEW system.

2.1 Product Perspective

The Online Spare Parts E-commerce Website functions as a central hub in the spare parts market.
Users interact through the website, administrators manage the platform, and external systems like
payment gateways and shipping services enhance functionality. It operates in a competitive
market, complying with regulations, utilizing a specific technology stack, and ensuring optimal
performance. Regular maintenance, user feedback, scalability are vital. Marketing strategies,
integration with social media, and adaptability to change requests contribute to its success within
the dynamic online spare parts landscape.

2.2 Product Functions

Sure, here's an integrated list of all the functions for customers, sellers, both customers and
sellers, and administrators:
Customers can view items, search for specific products, add items to their shopping cart, view
their shopping cart contents, make changes to items in their cart, proceed to purchase, place
orders, track their orders, cancel orders, return items, view their order history and returns,

3
register for an account, log in and log out, view their account details, edit their account details,
and receive personalized product recommendations.
Sellers can view sales data, fulfill orders by delivering items, upload new product listings,
register for an account, log in and log out, view their account details, edit their account details,
and receive personalized product recommendations.
Both customers and sellers share functions such as registering for an account, logging in and
logging out, viewing account details, editing account details, and receiving personalized product
recommendations.
Administrators have functions including logging in and logging out of the administrative
dashboard, tracking the number of users, products, and transactions from the dashboard, and
managing all aspects of the platform through CRUD operations, including items, customers,
partners, orders, individual sellers, mechanics, and feedback.

2.3 User Classes and Characteristics

Customer
- He/she is a verified user of the system who is intended to buy a product sold by a seller using
the platform. The functions used by customer are register, view account, login, browse item,
view item, buy item now, add to cart, view cart, proceed to buy, enter delivery address, enter
mode of payment, make payment, place order, write review, cancel order, return item, logout
Seller
- He/she is a verified user of the product who is intended to sell items over the platform. The
product functions used by sellers are register, view account, login, upload listing, your sales,
deliver the items to customers.

2.4 Operating Environment

The operating environment for an e-commerce website refers to the infrastructure and conditions
in which the website functions. Here are key components of the operating environment for an e-
commerce website:

Web Servers:
- The website is hosted on web servers that handle incoming requests from users and deliver
web pages.
-we have used localhost
Database Servers:
- Backend databases store and manage product information, user data, and transaction records.
- operating on Mongodb and Postgresql.

4
Network Infrastructure
- Reliable and high-speed internet connectivity is crucial for seamless data transfer between
users and the website servers.
- using nodejs for NETWORK I/0 that is making our system performance high
Security Protocols
- Implementation of robust security measures, including firewalls, encryption (HTTPS), and
secure socket layers (SSL), to protect user data and transactions.
Operating System
- The underlying operating system of the web and database servers, often using Linux,
Windows, or other server-oriented systems.
Web Browsers
- Compatibility with major web browsers (Chrome, Firefox, Safari, Edge) to ensure a
consistent user experience across different platforms.
Mobile Device
- Responsive design to accommodate users accessing the e-commerce website from various
mobile devices, including smartphones and tablets.
Content Delivery Networks (CDNs)
- CDNs (like font awesome cdn, box icons cdn and other)may be employed to enhance website
performance by caching and delivering content from servers geographically closer to the users.
Payment Gateways
- Integration with secure payment gateways that operate in a trusted and secure environment.

Third-Party Services
- Interaction with external services, such as shipping carriers for order fulfillment, analytics
tools, and marketing services.
Development Frameworks and Technologies
- Utilization of specific development frameworks and languages ([Link], Expressjs, OMD
mongoose on Mongodb) and technologies (e.g., HTML, CSS, JavaScript) to build and maintain
the website.
Compliance with Regulations

5
 - Adherence to data protection regulations, e-commerce laws, and other legal requirements in
the regions where the website operates.
Scalability Solutions
- Planning for scalability to handle an increasing number of users and transactions, often
through load balancing and cloud-based solutions.
Backup and Recovery Systems
- Regular backups and robust recovery systems to prevent data loss in case of unexpected
events.
Development and Testing Environments
- Separate development and testing environments to deploy and test new features or updates
before releasing them to the production environment.
Customer Support Systems
- Integration with customer support systems, including helpdesk software, chat support, and
contact forms.
Understanding and optimizing these components within the operating environment ensures the
SPEW functions efficiently, securely, and provides a positive experience for users.

2.5 Design and Implementation Constraints

For ease of maintenance, the customer will only be able to make payments once items have been
added to cart. There is no option to proceed directly to checkout with an empty cart. Brand
specific agendas have been excluded from our design. Section showing deals of the day, gifting
options and sales have not been included in the design. The wish list option has been merged
with the cart as it serves very identical purposes. In an effort to build a community of customers,
many sites had experimented with creating friendship communities on shopping platforms
however, due to the transparency into costs of products, revealing personal expenditures to
people- even within friendship communities could be seen as too transparent and even a breach
of user data protection. This puts a limitation to developers. As these systems lean heavily on the
ability to make real -time updates, the servers must be capable of handling sufficiently high
traffic bursts, which may not always be the case. Logistically, most companies outsource their
tasks to a third party organization which costs them more control over their implementation. Due
to interfaces with payment methods like google pay or PayPal, the risk for middle attacks is often
higher and may require additional safety at payment gateways. The recommendation system is
assumed to be a server side feature. Our system is also partial to the needs of the customer more
than it is to the seller. Customer functionalities have been more elaborately designed than Seller
functionalities.

6
2.6 Assumptions and Dependencies
Assumptions:
Stable internet access, user device compatibility, adherence to security practices, product
availability in inventory, compliance with e-commerce laws, valid user payments, authenticity of
user information, timely shipping by third-party carriers, and users seeking customer support if
needed.
Dependencies:
Integration with secure payment gateways, reliability of third-party services, effective database
management, web and database server uptime, chosen technology stack and development tools,
compliance updates with regulations, user engagement, feedback, and reviews, cybersecurity
measures, efficient supply chain management, and scalable solutions for increased traffic.

3. External Interface Requirements

3.1 User Interfaces
Home Page:
 The home page of this online shopping system is designed to be attractive and user friendly.
 It contains Four main parts:-
o Navigation section
o Main banner (main body header)
o Body content cards
o Body footer cards
o Footer

7
All Items Page
● The users while visiting to homepage, they can click on one of the buttons(pictures below
demonstrates this buttons) that will direct to some class items page to view all the items that is
available in the site.

● This usually includes more items or the products that has the some:- class name, model,
features, price, brand that is selling in the site.
● The user after viewing the products then he/she can click the product to direct into product
page that contains more description about the product and the transaction cards
● it contains these sections

8
Product Details Page
: ● The users while searching for products, can click on them to view the complete information
about the products.
● This usually includes one or more images of the product, product’s name, features, price,
brand that is selling it etc.
● The user after viewing the product details can then add the product to cart or buy it by clicking
on the ‘Add to cart’ or ‘Buy on whatsup’ buttons.
● By clicking on the ‘Buy now’ button, the user will be asked to select a payment method and
to proceed with placing the order.

Order generator and sell it page:-

Order generator
 It si designed to facilitate ordering process of the user that that will simplify transaction
process
 It is also a shortcut for the user to order and item that is not available in the site and that is
 A good strategy for customer holding and it will increase the market share.
 For sell it page when someone wants to sell a product that is a part of our products
He/she can sell easily by posting the product to the site.

9
 they contain two main cards :-

 One for the product

It has two main components :-
 product picture container that a user/seller can insert product picture.
 product description container for the product details
 And the other is a form for the customer/seller info input.

Sell it page:-
: ● This page allows the users to sell their products on this online shopping system. The user
wishing to sell their products must sign up as a seller. This requires the user to provide certain
details about themselves and their business such as location, product type, contact address,
identity details, GST number and mobile money transfer information.
● Once the user has been registered as a seller, the user has to upload their product listings to the
site. The customers can then choose to buy the seller’s products. The seller must then deliver the
products to the customers and receive payment

10
About us page
 If a user wants tp know more abut us he can visit about us page that contains
Different sections including :-
 Header cards that contains total transactions and different persons that entails on the
The services of the site.
 It is also contains a section body that is talking about our mission and vision
 More over, the achievements and testimonials sections that we have summarized
accomplishments and review of the most important persons that have used the site.
 All these sections are depicted below:-

11
Contact us page
 if user wants to get intouch with us he can visit one of the social media platforms that the
site
use or he can make direct communication if he wants to suggest, recommend or make a
compliant about the different services that our website gives to the customer
 it includes these components:-
o contact form
o written documentation downloading buttons form

12
3.2 Software Interfaces
● All the web pages of this online shopping system are majorly built using development tools
like HTML, CSS, JavaScript, EJS, , Ajax etc.
● This online shopping system is accessible through the internet on any Operating System like
Unix, Linux, Mac, Windows, etc.
● This system stores the product data, customer data and seller data in multiple databases which
are present in data centres located at various geographical locations. The types of databases
mainly include Mongodb(mongoose) database, postgresql database.
. ● The online shopping system shall communicate with the content manager to get the product
specifications to the users in the Product Specification page.
● The complete information about the products is stored in the databases of the system. The
content manager gets various information about the product like the images of the product,
product’s name, features, price, brand that is selling it, product reviews, product ratings etc
which is displayed to the users.
● The system shall communicate with the bill-paying system to identify the available payment
methods, validate the payments and process them. The data which includes customer email id/
phone number, selected bill payment method, product id of the products selected to be
purchased, their quantities, prices and payment details like (Card number, Name on the
services(ZAAD), submission date etc) are shared with the bill-payment system.
● The system shall communicate with the credit management system for handling financing
options. Data which includes the total price, payment method and payment details are shared
with the credit management system. Software Requirements Specification for Online shopping P
● The system shall communicate with the Sales system for order management. The orders
placed by the customers are managed by the Sales system based on the order details, the date &
time when the order was placed, delivery address of the product(s) and approximate delivery
date.
● The system shall communicate with the shipping system for tracking orders and updating of
shipping methods. Once the order is placed, the shipping system is responsible for updating the
users about the shipping process of the products they ordered. The updates are provided to the
customers by sending messages to their phone number and email id about the shipping process.

13
3.3 Communications Interfaces
● The user can access the online shopping system through the internet by searching the system’s
name on the web browser.
● The system shall use the HTTP protocol for communication over the internet.
● The system shall give a confirmation to the customer that their order is placed by sending a
message to the customer’s email id and phone number.
● The system also provides follow up messages to the customer’s phone number and email id to
update the customer about the shipping process like ‘product is dispatched from the site’,
‘product shall arrive in 2 days’ etc.

4. Analysis Models
4.1 CUSTOMER USE CASE DIAGRAM:

14
4.2 SELLER USE CASE DIAGRAM:

15
 ER DIAGRAM:

5. 5. System Features
5.1 User Accounts
5.1.1 Description and Priority
Users from both subsystems- customers and sellers must have an account to
conduct transactions on the shopping system. Users without system accounts will
only have browsing permissions from the home page and do not have options to
purchase or list goods on the system. Customers accounts will hold information
about their name, email id or phone number, password. Both users can view and
login to their accounts and even edit account details in the future. Seller accounts
hold information relevant to the selling organization or individual including name,
contact, gst number, pan, licenses and address. Priority level: High

5.1.2 Stimulus/Response Sequences

In the home page, users can select the signup or login button and type in their
credentials for registration or for login respectively. Upon matching the required
criteria, the account will either get created and the login page is displayed or the
user is logged in to his/her account and the home page is displayed. To edit or
view account details, the edit or view buttons may be clicked respectively. To edit
details, the user may type in the new details and click on save changes. Upon
validating the changes, the edited details are successfully updated.
5.1.3 Functional Requirements
REQ-1: Register
● User: Customers and sellers
● Input: In sign up page
0 Customer - enters name, email-id/phone number and password
○ Seller - enters name, email-id/phone number, gst
no, ● Output: Successfully registered, the login page is
displayed ● Alternative flow(s):
○ Incase of repeated/invalid email id or phone number, ask user to
re-enter a valid choice
REQ-2: View account details
● User: Customers and sellers
● Input: Click ‘view account details’ button in home page

16
 ● Output: Displays account details that were filled by the user at the time of
creating account
● Alternative flow(s) : none
REQ-3: Login
● User: Customers and sellers
● Input: In login page
0 Customer - enters registered email-id/phone number and password
○ Seller - enters registered email-id/phone number and
password ● Output: Successfully logged in, the home page is
displayed ● Alternative flow(s):
○ Incase of invalid email id/phone number or a mismatch between
user id and password, ask the user to re-enter a valid credential.
REQ-4: Logout
●User: Customers and sellers
●Input: Click ‘logout’ button in home page
●Output: User is logged out of the account, Login page will be displayed ●
Alternative flow(s) : none
REQ-5: Edit account details
● User: Customers and sellers
● Input: In home page
0 Click button to edit account details
○ Select the detail whose value has to be edited
○ Enter the new details
○ Click on save
changes ● Output:
Successfully updated ●
Alternative flow(s):
○ Incase of invalid details, ask the user to re-enter a valid credential

5.2 The search facility

5.2.1 Description and Priority
Customers can search for an item from the large catalogue of items in the shopping
system by two methods. They can either search for a product using keywords
related to the product or search for the product by image. Relevant options are
listed in a dropdown of the search bar which upon selection, lists the products
related to the keyword searched for Priority: High
5.2.2 Stimulus/Response Sequences
To search for the product, the customer types in keywords into a search box or
pastes an image of the product. This action immediately shows a drop down with
the most likely products. The user then clicks on the product he/she wants to view.

17
 5.2.3 Functional Requirements
REQ-1: Search item
● User: Customers
● Input: In the home page
○ click on the browse button
○ type in the keywords related to the item like item name/ brand
etc. ● Output: List of products related to the item searched for ●
Alternative flow(s):
○ Displays:
■ No results for the searched term/keyword
■ Try checking your spelling or use more general terms
REQ-2: View Item
● User: Customers
● Input: From the list of items click on an item to view its details
● Output: Details of the selected item like - price, brand, size, material,
quantity, delivery date, images of the item will be displayed, along with the
ratings and reviews for that item, and add to cart button ● Alternative
flow(s): none

5.3 The shopping cart facility

5.3.1 Description and Priority
Once the customer views and selects an item that he/she wishes to purchase, one
must add the item to cart using the add to cart button. The shopping cart contains
all the items that the customer intends to buy, there is one shopping cart associated
with one user account. The user can browse for an item, add it to cart and continue
his/her shopping gracefully and purchase all of them at once. Priority: high

5.3.2 Stimulus/Response Sequences

To add an item to the shopping cart, the user must click on the add item to cart
button in the view item page, and the customer can continue shopping other items.
The customer can view all the items in his cart by clicking on the view cart button,
upon which a list of all items along with price of individual item, quantity and total
cost of the cart is displayed. In this page the customer has the option to remove
items from the cart or change the quantity of the products by clicking on the delete
item button next to the item or ‘plus’ or ‘minus’ symbols respectively.
From here the customer can proceed to buy all the items in the cart, by clicking on
the proceed to buy button or can further continue shopping by going back to the
home page by clicking on the continue shopping button.

18
5.3.3 Functional Requirements

REQ-1: Add item to cart

● User: Customers
● Input: In view item page
0 click on the add item to cart button
● Output: Added item to cart, will remain in the same page ● Alternative
flow(s):
0 Incase of adding an item that is already in the cart, the quantity of
that item will be increased by 1 in the cart.
REQ-2: View shopping cart
● User: Customers
● Input: present in all pages
0 click on the view cart button
● Output: List of items that were added to cart is displayed along with item
details and total cost
● Alternative flow(s): Incase the cart is empty, ‘cart empty’ is displayed and
the customer has the option to return to home page by clicking on continue
shopping
REQ-3: Change items in cart
● User: Customers
● Input: In shopping cart page
0 click on delete item button present next to the item to delete the
item from the cart
○ to change the quantity of items click on ‘+’ to increase quantity by
1, or ‘-’ to decrease quantity by 1
● Output: Changes reflected in the shopping cart page based on activity
performed, the item will be removed from the page if it is deleted ●
Alternative flow(s): none
REQ-4: Proceed to buy
● User: Customers
● Input: In shopping cart page
0 click on proceed to buy button
● Output: Payment page is displayed
● Alternative flow(s): none
REQ-5: Continue shopping
● User: Customers
● Input: In shopping cart page
0 click on continue shopping button
● Output: home page is displayed

19
 ● Alternative flow(s): none

5.4 Payment
5.4.1 Description and Priority
Once the customer proceeds to buy from the cart page, the delivery and payment
page is visible where the total cost of all the items in the card is visible and the
customer has to fill in the details necessary for delivery to the customer’s desired
address and for the payment of items to be ordered. After filling the details the
customer has to click on place order to confirm and book the order.

5.4.2 Stimulus/Response Sequences

To buy the items in the cart, the customer has to click on proceed to buy button in
the shopping cart page, then the ‘delivery and payment’ page is displayed where
the customer has to fill in the delivery address- house number, street address,
pincode, city, state and click on delivery to this address, then the payment details
like payment mode- credit/debit card/pay on delivery. In case of credit/debit card
enter the card details and cvv number and make the necessary verifications through
otp, and click on Pay. On successful payment the place order page is displayed
where the customer has to click on the place order button for placing the order
confirmly and the items then enter the delivery process. The customer is then
redirected to the home page.
5.4.3 Functional Requirements
REQ-1: Delivery details
● User: Customers
● Input: In delivery & payment page ○ Enter the delivery address:
■ house number, street address, pincode, city, state
○ Click on deliver to this address
● Output: the payment page is displayed
● Alternative flow(s): Incase of invalid address entry, the order is not
delivered and is cancelled in the future
REQ-2: Payment details
● User: Customers
● Input: In delivery & payment page ○ Enter the payment details:
■ Payment mode:
● debit/credit card: enter card number, cvv number, otp verification
● pay on delivery
○ Click on deliver to this address
● Output: Payment successful, the place order page is displayed

20
 ● Alternative flow(s): Incase of invalid payment details, the user has to re-enter valid
details, unless successful payment the customer cannot place order REQ-3: Place order
● User: Customers
● Input: In place order page
○ Click on place order
● Output: Order successfully placed, the home page is displayed
● Alternative flow(s): Incase the user exists the page, order is not placed

5.5 Orders and returns

5.5.1 Description and Priority
Orders and returns feature offers order management and flexibility to return orders
within certain period of time that is specified by the seller of that [Link]
customer can view and manage orders that are yet to be delivered to the customer.
He/she can cancel the order that is yet to be delivered or return the item that is
delivered and get the paid amount back, or view past orders and returns. Also upon
successful placing of the order, the customer can track order, i.e the delivery
stagedispatchment, shipment of the item along with the location- city, state in
which the item is currently in. Priority: Medium
5.5.2 Stimulus/Response Sequences
In the home page the customer can click on ‘orders and returns’ button, a list of
past and existing orders and returns are displayed. If the customer wants to cancel
an existing order that is not yet delivered he/she can click on cancel order in the
orders section of the returns and orders page, and if the customer wants to return
an item that is delivered, he/she can click on return item and enter the reason for
cancelling order or returning an item in the reason box. If the customer wants to
track the order that had been placed earlier and yet to be delivered he/ she can click
on the track order button of that particular item and the different stages of the
delivery of the item will be displayed along with the date, time and location at that
time, and current stage of the item.
5.5.3 Functional Requirements
REQ-1: View orders and returns
● User: Customers
● Input: In home page
Click on orders and returns button
0
● Output: the past and existing orders and past returns are displayed ● Alternative
flow(s): none REQ-2: Cancel order
● User: Customers
● Input: In orders and returns page
0 Click on cancel order button present next to the order and type in
the reason for cancelling
● Output: the order is successfully cancelled, the orders and returns page remains displayed

21
 ● Alternative flow(s): none REQ-2: Track order
● User: Customers
● Input: In orders and returns page
0 Click on track order button present next to the order
● Output: the tracking information of that order is displayed
● Alternative flow(s): none REQ-2: Return item
●User: Customers
●Input: In orders and returns page
0 Click on return item button present next to the item and type in the
reason for returning the item
● Output: the item is successfully booked for return, the orders and returns page remains
displayed
● Alternative flow(s): none

5.6 Other system features

5.6.1 Recommendation models: The server is responsible for maintaining the
recommendation model. The recommendation model is used to customize the products that are
visible to the customer in their home page. These are built using collaborative filtering models.
5.6.2 Rate and Review: The rate and review features are available to the client
subsystem and are used to build a community of consumers. Each customer has the option to
review purchased products and assign ratings or satisfaction levels. The system may choose to
terminate products that have low satisfaction ratings.

5.7 Seller features

5.7.1 Description and Priority
Sellers can sell their items using the features provided by the system such as easy
uploading of the list of items to sell and effective notification system when the
order is made by a customer and display history of the sales made in the past
Priority: High
5.7.2 Stimulus/Response Sequences
To upload the listings of the items that the seller wishes to sell, he/she has to click
on the upload listing button and enter the details for each item such as name of the
product, price, colour, material, quantity, brand. For viewing the current order
from the customers he/she has to click on the view of new orders, where the details
of the customer like the delivery address and the items booked are visible. To
deliver the ordered items to the customers one can click a self delivery option
where he/she can deliver to the customer independently, or can click use external
delivery and can hire an external delivery system to perform the delivery.
5.7.3 Functional Requirements
REQ-1: Upload listing

22
 ● User: Sellers
● Input: In home page
0 Click on upload listings and enter details (name of the item, price,
material, quantity, colour) of all the items to sell
● Output: the items successfully uploaded, customers can view these items ●Alternative
flow(s): none REQ-2: View new orders
● User: Sellers
● Input: In home page
0 Click on view new orders
● Output: displays the orders for his/her items from the customers ● Alternative flow(s):
none REQ-3: Deliver to customer
● User: Sellers
● Input: In view new orders page
0 Click on deliver to customer and select either
■ deliver independently (self delivery)
■ external delivery (hire external delivery agency)
● Output: Item added to delivery, items undergo delivery process ● Alternative flow(s):
none

6. Other Nonfunctional Requirements

6.1 Performance Requirements
An online shopping service has many levels of organization and its overall performance is a
confluence of factors that affect all these different levels
● Information system: The infrastructure and organization of the information system can
crucially affect performance in the following ways
0 average response time of web page
○ failure rate
○ average web page creation time
○ site maintenance costs
In order to maintain an acceptable speed at the maximum number of requests allowed from a
particular customer, any number of users must be able to access the system at any time. A
smooth UI/UX is a necessity for all ecommerce applications. While a visually appealing design
is essential, image optimization and other techniques can be implemented to ensure that the site
is not very heavy. Real-time technologies equip online retailers with tools to keep up with the
ever-evolving search ecosystem. Flexible goal setting, third-party data integration and real-time
optimization offers a systematic solution to many ongoing challenges.
● Logistics:
0 product availability
○ average delivery time

23
 ○ quality of delivery
○ liability failure rate
○ inventory turnover
To overcome issues related to the logistics, the service has to ensure that the right product should
be available at the right time and adequate quality. Some services may hire a 3PL to ensure this.
A 3PL is a third party logistics service. Many online shopping services outsource their logistic
operations and choose to invest their resources in other areas. However, many e-stores prefer to
employ their own resources in logistic planning and implementation for better control over
distribution.
● Sales activity:
0 acquisition cost
○ acquisition cost per first customer
○ brand awareness
There are various measures that can be taken to ensure that sales activity is improved.
● Build engagement
● limit spending
● develop partnerships
The above points illustrate some of the important performance criteria in terms of profitability
analysis
● Market and customer
0 number of unique customers
○ average visit frequency
○ number of first buyers
○ average order value
● Sales process
0 fulfilment cost
○ personnel cost
○ marketing cost
○ return on sales
○ total turnover
The above points illustrate key performance criterias in terms of structural analysis. On
analyzing the current or immediate state of the service, some important criteria to consider while
evaluating performance is:
● sales growth

24
 ● order number growth
● visit frequency growth
● market share growth
● complaint rate
On a non-technical front, the customer satisfaction with the service itself is intrinsically linked
with general satisfaction with products, delivery and website experiences. All sellers have a
sellers account where they can monitor their account health. sellers are liable for product quality
and are measured based on order of
● customer feedback rating (target: 3.5 stars or more)
● negative feedback rate (target: 1% or less)
● cancellation rate (target: 5% or less)
● reschedule rate (target: 5% or less)
It is essential for sellers to maintain acceptable service levels to be able to continue their market
on the online service.

6.2 Safety Requirements

There are a wide range of concerns that arise wherever online transactions are
performedespecially with money transactions and address records. One of the most common
risks of online shopping is online shopping. Stealing one’s personal information to make
illegitimate purchases, phishing and keylogging are common ways used to steal identity.
Another common risk is credit card frauds. Customer’s may be redirected to the malicious user’s
site during payment- that is made to look similar to the legitimate payment gateway and cost
them money and may even have their credit card numbers stolen.
Malwares and Adwares commonly plague many websites. The risk is even higher with online
shopping websites as scammers may easily acquire sensitive information entered by the user.
Simply visiting the website makes the malware attack the user system.
To ensure user safety, measures must be taken from both the user side as well as the shopping
system’s side. From the user side, the user must never divulge any personal information except
during bill payment. Users must be careful not to fall prey to phishing by verifying that mails
being sent from the service are in fact, authentic. Users must be wary of ads and ensure that
appropriate antivirus softwares has been installed in one’s system.
The shopping system itself has to take concrete measures to ensure that customer;s can trust the
service being provided to them. SIte seals on web sites are visual indicators that the website is
safe and secure. Acquiring SSLs certificates are mandatory as this ensures the user that the
communication channel is encrypted.

6.3 Security Requirements

To ensure secure transfer of data, the system must use secure sockets in all transactions that
include any confidential customer information. The system may choose to automatically log out
all customers after a period of inactivity and verify by confirmation all the transactions with the

25
customer’s web browser. The system will ensure that cookies and all temporary storage do not
hold any sensitive information.
The customer’s web browser must never display a customer’s password or credit card details.
The system’s back-end servers must never display a customer’s password and these servers must
only be accessible to authenticated administrators. These databases must be encrypted and within
the company's perimeter.
The service can ensure user identity authentication using two-step verification procedures.
Further, the system can ensure that any additional security risks experienced by the users can be
reported to the system immediately.

6.4 Software Quality Attributes

Adaptability is of primary importance to both types of users of the system. It should be able to
easily cater to the needs of sellers and customers and be able to add additional features and
provide support as demanded- especially in case of system vulnerability. As an online shopping
system, it must define product availability by defining the targeted audience be it global users or
a more restricted user space. It is also important to ensure that sellers are able to deliver products
to the regions promised by the service. Due to user sensitive information being required,
ensuring that money transactions are not error prone is vital. Utmost correctness is to be expected
in ensuring that money is refund money in case of returns, offers on products are appropriately
deducted from the selling price, delivery services have minimal error and that warehouses
function properly. The system should also be highly flexible with servers that are equipped to be
able to accommodate large flow of traffic. The system must be interoperable and must work
without any compromise in performance and quality in both mobile applications as well as web
applications. should be built with modularity so that additional features can be added and
removed easily without changing too much of the original structure- this also allows reusability.
The reliability of the overall program depends on the reliability of the separate components. The
main pillar of reliability of the system is the backup of the database which needs to be
continuously maintained and updated to reflect the most recent changes. Testing the system can
be done on various fronts. Unit testing can be done by taking atomic components of the system,
isolating it from the remainder of the code, and determining whether it behaves as expected.
Program units are combined and tested as groups in multiple ways. Integration testing can
expose problems with the interfaces among program components before trouble occurs in real-
world program execution. Validation testing focuses on user visible actions and user
recognizable output from the system and is said to be successful when software functions in a
manner that can be reasonably expected by the customer.

26
6.5 Business Rules
Given the presence of two subsystems for the customers and sellers, the two types of users have
different levels of privileges - including functionalities.
Some of the functionalities common to the two subsystems are- registration, login, viewing
account details and editing account details. Some functionalities specific to Seller subsystems are
seller’s sales details, and uploading items to the inventory. Customers also have browsing
features, cart features, delivery details, payment options, cancellation, review options and many
more.

[Link] Requirements
A robust commercial backend that delineates customer and seller information is necessary. A
general management backend with inventory and general system requirements is also required.
Authorization from payment services is needed for customers to be able to make payments
through payment gateways. A defined privacy policy, SSL certification and two-step verification
through external mail or phone number is also necessary to ensure no breach in both user data
and system data.

Appendix A: Glossary
Some key terms used repeatedly throughout the document are
1. Customer subsystem: A subsystem within the online shopping system support for
customers
2. Seller subsystem: A subsystem within the online shopping system support for sellers
3. GST: Goods and services tax applicable to all products
4. PAN: permanent account number
5. Seller listing: Sellers will add their product listings to the system
6. Turnover: net sales generated by the system
7. avg response time: average time taken to respond to a user request
8. failure rate: frequency of failure of an individual component
9. liability failure rate: amount of product or service defects that hold the system liable
[Link] turnover: ratio that measures the number of times inventory is sold or
consumed in a given time period
11. acquisition cost: Customer Acquisition Cost is the cost of winning a customer to
purchase a product/service
[Link] awareness: marketing term that describes the degree of consumer recognition of a
product by its name

27
 [Link] cost: costs associated with receiving and storing products along with
processing orders from handling to shipping.
14. market share growth: growth strategies to broaden market share

1.4 References
 Common Format for Online-Shopping-SRS_by Devika S Nair, Mitravinda K M, Prathima B
 PES University February 5th, 2021

 Software Requirements Specification (SRS) Book E-Commerce System (BECS): Authors: Andrew
Blossom, Derek Gebhard, Steven Emelander, Robert Meyer
 Case Study: Flipkart online
o Author: Aman Goel
o Date: Nov, 2017

 10 Problems That Every Ecommerce Business Faces and Their Solutions [Updated 2020]:
o Author: Laduram Vishnoi
o Date: December 14, 2020
 A Study on Performance Measurement of Online Retail Stores:
 Authors: Binod Kumar Singh, Neeraj Anand
o Date: March 2014

 [Link] Inc.’s Mission Statement & Vision Statement (An Analysis)

o Author: Lawrence Gregory
o Date: February 13, 2019
 [Link] For creating UML DIAGRAMS
 [Link] FOR google content
 [Link]
 [Link]

28