E-commerce Website Requirements and Specifications

Project Title: E-commerce Website

Project Team:

 M. Umar Abbas (230417)

 M. Daniyal Haider (230383)
 Qasim (230370)

Submission Date: April 23, 2024

Table of Contents
1. Introduction

 1.1 Purpose of Document

 1.2 Project Overview
 1.3 Scope
 1.4 Definitions, Acronyms, and Abbreviations

2. User Roles

3. Use Cases

 3.1 Browse Products (Customer, Guest)

 3.2 Register/Login (Customer, Seller, Admin)
 3.3 Manage Account (Customer, Seller)
 3.4 Add to Cart (Customer, Guest)
 3.5 View Cart/Checkout (Customer)
 3.6 Process Order (Customer)
 3.7 Manage Orders (Admin, Seller) (Optional)
 3.8 Admin Dashboard (Admin)

4. Test Case Descriptions

 4.1 Browse Products (Customer, Guest)

 4.2 Register/Login (Customer, Seller, Admin)
 4.3 Manage Account (Customer, Seller)
 4.4 Add to Cart (Customer, Guest)
 4.5 View Cart/Checkout (Customer)
 4.6 Process Order (Customer)
 4.7 Manage Orders (Admin, Seller) (Optional)
 4.8 Admin Dashboard (Admin)

5. Functional Requirements

 5.1 Product Management

 o 5.1.1 Seller Product Management
o 5.1.2 Admin Product Management (Optional)
 5.2 Search and Browse
o 5.2.1 Browsing
o 5.2.2 Search Functionality
 5.3 Shopping Cart
o 5.3.1 Adding and Removing Items
o 5.3.2 Cart Display
o 5.3.3 Updating Quantities (Optional)
 5.4 Checkout Process
o 5.4.1 Secure Payment Integration
o 5.4.2 Shipping Options
o 5.4.3 Order Confirmation
 5.5 User Management
o 5.5.1 Registration
o 5.5.2 Login
o 5.5.3 User Roles and Permissions
 5.6 Order Management (Optional)
o 5.6.1 Order Status
o 5.6.2 Order Tracking (Optional)
 5.7 Account Management
o 5.7.1 Profile Updates
o 5.7.2 Customer Order History
o 5.7.3 Seller Account Management (Optional)

6. Non-Functional Requirements

 6.1 Performance
o 6.1.1 Scalability
o 6.1.2 Response Times
o 6.1.3 High Availability
  6.2 Security
o 6.2.1 Data Encryption
o 6.2.2 Regular Security Audits
o 6.2.3 Compliance with Regulations
 6.3 Usability
o 6.3.1 Intuitive Interface Design
o 6.3.2 Accessibility
o 6.3.3 Responsive Design

7. Additional Considerations

 7.1 Content Management System (CMS) (Optional)

 7.2 Analytics and Reporting
 7.3 Multilingual Support (Optional)

8. Assumptions and Dependencies

 8.1 Assumptions
o 8.1.1 Basic Internet Access and Standard Web Browsers
o 8.1.2 User Capabilities
 8.2 Dependencies
o 8.2.1 Third-Party APIs and Services
o 8.2.2 External Development Teams

9. References

1. Introduction
1.1 Purpose of Document

This document serves as a Software Requirements Specification (SRS) for the development of an
e-commerce website. It outlines the functionalities, features, and non-functional characteristics
that the website needs to possess to meet the project's goals. This document serves as a crucial
reference point for the development team, stakeholders, and any individual involved in the
development process.

1.2 Project Overview

The main objective of this project is to develop an e-commerce website that facilitates online
buying and selling of products. This platform will cater to two primary user groups:

 Customers: Customers will be able to browse through a variety of products offered by

different sellers, search for specific items, add products to their shopping cart, and
complete secure online purchases.
 Sellers: Sellers will be equipped with tools to manage their online presence within the
platform. They can list their products with descriptions, images, and pricing information.
They can also manage their inventory, process customer orders, and potentially track
shipments.

1.3 Scope

The e-commerce website development project encompasses the following functionalities:

User Management:

 User Registration and Authentication: The website will enable users to register accounts
with secure login credentials. This system will differentiate user roles: Customers,
Sellers, and Administrators. Each role will have specific access levels and functionalities
within the platform.
  Secure Login: Secure login mechanisms (e.g., password hashing) are crucial to protect
user credentials and prevent unauthorized access to accounts.

Product Management:

 Product Browsing and Search: Customers should be able to browse through products
using well-defined categories and subcategories. Powerful search functionalities with
filters (e.g., by price range, brand, or product attributes) will allow customers to find
specific items efficiently.
 Product Listings and Management: Sellers will have tools to create and manage their
product listings. This includes adding product details like titles, descriptions, high-quality
images, specifications, pricing information, and inventory levels.

Shopping Cart Features:

 Adding and Removing Items: Customers can add desired products to their shopping cart,
potentially indicating desired quantities for each item. They should also be able to
remove unwanted items from the cart before checkout.
 Cart Display and Management: The shopping cart page should provide a clear overview
of chosen products, displaying details like product images, titles, quantities, and
individual prices. It should also calculate the subtotal of all items in the cart and
potentially display any applicable taxes or estimated shipping costs.

Order Processing:

 Secure Payment Integration: The website will integrate with secure payment gateways to
allow customers to pay for their purchases using various methods (e.g., credit cards, debit
cards, PayPal). Sensitive payment information must be securely transmitted using
encryption protocols.
 Order Placement and Confirmation: Upon selecting desired payment and shipping
options, customers can finalize their orders. The system should display a confirmation
page summarizing order details for reference. An order confirmation email should also be
 sent containing the same information and potentially including a tracking number (if
applicable).
 Seller Order Management: Sellers will have functionalities to view, manage, and
potentially fulfill customer orders. This might include updating order statuses, processing
payments, generating shipping labels (depending on platform setup), and communicating
with customers regarding their orders.

Additional Functionalities:

 Admin Dashboard: Administrators will have access to a comprehensive dashboard that

provides overall website management tools. This could include user management
(adding, removing, or modifying user accounts), product management (e.g., reviewing
product listings), managing website settings, and potentially accessing website analytics
(user traffic, order trends).
 Wishlists (Optional): Customers might be able to create wishlists to save products they
are interested in for future purchase. This functionality can enhance customer
engagement and potentially lead to future sales.
 Product Reviews and Ratings (Optional): Integrating a product review and rating
system allows customers to share their experiences with other users. This can build trust
and influence purchasing decisions.

1.4 Definitions, Acronyms, and Abbreviations

This section (if applicable) should define any specific terms, acronyms, or abbreviations used
throughout the document to ensure clarity and avoid misunderstandings.
2. Use Case Diagram
3. Use Case Descriptions

3.1 Browse Products (Customer, Guest):

 Description: This use case allows both registered Customers and Guests to explore the
product catalog. They can navigate through product categories and subcategories, utilize
the search function with filters to find specific items, and view detailed information on
individual products (including images, descriptions, specifications, and pricing).
3.2 Register/Login (Customer, Seller, Admin):

 Description: This use case covers user account creation and login functionality. Users
can register for new accounts or log in with existing credentials to access personalized
features. The system enforces user roles and permissions, granting access levels based on
the user type (Customer, Seller, or Admin). For example, Admins can manage users,
while Sellers can manage their inventory.

3.3 Manage Account (Customer, Seller):

 Description: This use case allows both Customers and Sellers to manage their accounts.
Users can update their account information (e.g., name, address), edit their profiles, and
view their order history. Additionally, Customers can access their wishlists for saved
products. Sellers have the privilege to manage their product inventory, including adding,
editing, and deleting product listings. They can also utilize inventory management tools
provided by the system.

3.4 Add to Cart (Customer, Guest):

 Description: This use case enables both Customers and Guests to add desired products to
their shopping cart. They can potentially add varying quantities of each item to the cart.

3.5 View Cart/Checkout (Customer):

 Description: This use case allows Customers to review the items in their shopping cart.
They can check product details, quantities, and pricing. Customers may also be able to
modify product quantities (if allowed) before proceeding to checkout. The checkout
process facilitates the selection of shipping and payment options for order completion.

3.6 Process Order (Customer):

 Description: This use case guides Customers through the order confirmation and
payment process. Customers confirm their order details, submit secure payment through
 integrated payment gateways, and receive order confirmation with tracking information
(if applicable).

3.7 Manage Orders (Admin, Seller):

 Description: This use case outlines order management functionalities for both Admins
and Sellers. Admins have the authority to view and manage all orders placed on the
website. This includes access to customer information and product listings associated
with each order. Sellers, on the other hand, can access and manage their own orders
specifically. This might involve fulfilling orders (updating order statuses) and generating
shipping labels.

3.8 Admin Dashboard (Admin):

 Description: This use case is exclusive to Admins and provides them with a central hub
for managing various aspects of the website. Admins can manage users (create, edit, and
delete user accounts within their roles). They can also manage product listings
(add/remove product categories, update product information), configure website settings
(e.g., taxes, shipping costs, promotions), and monitor key performance metrics through
the Admin dashboard (e.g., number of users, orders, website traffic).

4.Test Case Description:

4.1 Browse Products (Customer, Guest):

 Test 1: Verify that all product categories and subcategories are displayed correctly on the
website.
 Test 2: Ensure the search functionality works accurately with relevant keywords and
filters. Search results should be displayed according to entered criteria (e.g., sort by price,
filter by brand).
 Test 3: Test product detail pages to confirm they display product images, descriptions,
specifications, and pricing information accurately.
  Test 4: Verify that clicking on a product category or subcategory navigates users to the
corresponding product listing page.
 Test 5: Ensure search results are relevant to the keywords or filters used. (e.g., searching
for "red shirt" should not return blue shirts).

4.2 Register/Login (Customer, Seller, Admin):

 Test 1: Validate that the registration process is successful and securely stores user
passwords (using encryption).
 Test 2: Test login functionality with valid credentials (username and password) to ensure
successful login. Also, test with invalid credentials to verify appropriate error messages
are displayed (e.g., "Invalid username or password").
 Test 3: Verify that user roles and permissions are enforced correctly. For instance, test if
Admins can manage users while Sellers can manage their inventory. (e.g., Admin tries to
edit a Seller's product listing - test for permission denial).
 Test 4: Test password recovery functionality to ensure users can retrieve forgotten
passwords. (e.g., user requests password reset, receives email with reset link).

4.3 Manage Account (Customer, Seller):

 Test 1: Verify that the system allows successful account information updates (e.g., name,
address).
 Test 2: Ensure profile management features work correctly. (e.g., update profile picture,
change email address).
 Test 3: Test order history displays past purchases accurately (Customer). Information
should include order details, product listings, and statuses.
 Test 4: Verify Seller can add, edit, and delete product listings. Test for functionalities
like uploading product images, setting prices, and managing stock levels.
 Test 5: Test inventory management tools function as expected (Seller). (e.g., track
inventory levels, receive low-stock alerts).
4.4 Add to Cart (Customer, Guest):

 Test 1: Verify items can be added to the cart successfully. Test adding single and
multiple items.
 Test 2: Ensure adding multiple quantities of the same item works correctly. Update cart
quantity and verify the total reflects the change.
 Test 3: Test handling of out-of-stock or discontinued products. The system should
display appropriate messages (e.g., "Out of stock" or "Product discontinued").
 Test 4: Verify that Guests can add items to the cart without registering. However,
checkout might require registration or guest checkout options.

4.5 View Cart/Checkout (Customer):

 Test 1: Verify cart displays accurate product details, quantities, and pricing. Ensure the
total price reflects the combined price of all items in the cart.
 Test 2: Ensure modifying product quantities in the cart works as expected. Test
increasing and decreasing quantities and verify the cart reflects the changes.
 Test 3: Test checkout process allows selection of valid shipping and payment options.
The system should display available shipping methods and payment gateways integrated
with the platform.
 Test 4: Verify that users can remove items from the cart before checkout.

4.6 Process Order (Customer):

 Test 1: Verify order confirmation page displays accurate order details. This includes
customer information, product listings, quantities, pricing, shipping address, and chosen
payment method.
 Test 2: Ensure secure payment gateway integration functions smoothly for various
payment methods. Test with successful transactions using different credit cards or
payment options.
 Test 3: Test handling of successful and failed payment scenarios. The system should
display a confirmation message for successful payments and appropriate error messages
for failed transactions.
  Test 4: Verify order confirmation email is sent with accurate tracking information (if
applicable). The email should include order details, a tracking number (if shipped), and
customer service contact information.

4.7 Manage Orders (Admin, Seller) :

 Test 3: Test order fulfillment process (Admin/Seller). This might involve:

o Admin marking orders as "shipped" and updating order statuses.
o Seller generating shipping labels and marking orders as "fulfilled."
 Test 4: Verify Admin/Seller can view order history with filters (e.g., by date, status,
customer). This allows for efficient order management and tracking.

4.8 Admin Dashboard (Admin):

 Test 1: Verify Admin can create, edit, and delete user accounts within their roles. This
allows for user management based on their role (Customer, Seller, Admin).
 Test 2: Ensure Admin can manage product listings, add/remove product categories, and
update product information. This empowers Admins to control the product catalog on the
website.
 Test 3: Test website settings management functionality (e.g., taxes, shipping costs,
promotions). This allows Admins to configure various aspects of the website's operation.
 Test 4: Verify Admin dashboard displays key performance metrics (e.g., number of
users, orders, website traffic). This provides Admins with insights into website usage and
performance.
 Test 5: Test that Admins can export relevant data (e.g., order reports, user reports) for
further analysis. This allows for data-driven decision making.

Additional Test Cases (Optional):

  Test website responsiveness across different devices (desktop, mobile, tablet). Ensure
the website displays and functions correctly on various screen sizes.
 Test website performance under load. Simulate multiple users accessing the website
concurrently and verify acceptable response times.
 Test security measures. This might involve penetration testing to identify and address
potential vulnerabilities.
 Test user interface (UI) usability. Conduct usability testing with real users to ensure the
website is intuitive and easy to navigate.
 Remember, these are just examples, and you can add more test cases based on the
specific functionalities and features of your e-commerce website. The goal is to
comprehensively test all aspects of the system to ensure a smooth and secure user
experience.

5. Functional Requirements

These requirements define the core functionalities of the e-commerce platform, outlining what
users can do within the system. Here's a breakdown with further explanations:

 Product Management:
o Sellers: Sellers should be able to add new products, edit existing product listings,
and delete products they no longer offer. This includes managing product
information such as title, description, high-quality images from various angles,
specifications (e.g., size, weight, materials), pricing (including potential sales or
discounts), and inventory levels. The system might require sellers to categorize
their products to improve searchability and browsing experience.
o Admins: In addition to seller functionalities, Admins might have broader product
management control. They could be responsible for creating and managing
product categories, setting product visibility rules (e.g., approve new product
listings before publishing), or managing bulk product uploads for efficiency.
 Search and Browse:
o Browsing: Customers should be able to browse products through well-defined
categories and subcategories. The system might also allow browsing by brand or
other relevant filters (e.g., size, color, material). Implementing faceted navigation
allows users to refine their search by applying multiple filters simultaneously.
o Search Functionality: A robust search engine allows customers to find specific
products using relevant keywords. It should support filtering by various attributes
(e.g., price range, brand, product features). Auto-suggestions can improve search
efficiency by suggesting relevant products as users type their search queries.
Sorting search results by different criteria (e.g., popularity, price, average rating)
empowers customers to find products aligned with their needs.

 Shopping Cart:
o Adding and Removing Items: Customers should be able to add products to their
shopping cart, potentially indicating desired quantities for each item. The system
might allow adding products to the cart from product listings, search results, or
even browsing through category pages. Customers should also have the option to
remove unwanted items from the cart before checkout.
o Cart Display: The shopping cart page should clearly display chosen products
with details like product images, titles, quantities, and individual prices. It should
also calculate the subtotal of all items in the cart, potentially including any
applicable taxes or shipping costs (estimated at this stage).
o Updating Quantities: The system might allow customers to update the quantities
of items already in their cart (e.g., increase or decrease the number of a specific
product). This flexibility helps adjust the order quantities before finalizing the
purchase.
 Checkout Process:
 o Secure Payment Integration: The checkout process should integrate with secure
payment gateways allowing customers to pay for their purchases using various
methods (e.g., credit cards, debit cards, PayPal). The system must securely
transmit sensitive payment information using encryption protocols to protect
customer data.
o Shipping Options: Customers should be able to choose their preferred shipping
method from a selection offered by the seller or platform. This could include
different delivery speeds (e.g., standard, express) or shipping providers with
associated costs displayed clearly.
o Order Confirmation: Upon successful order placement, the system should
provide customers with a confirmation page summarizing their order details
(products, quantities, prices, shipping address, chosen payment method, estimated
delivery timeframe). Additionally, an order confirmation email should be sent,
containing the same information for future reference and potentially including a
tracking number (if applicable).

 User Management:
o Registration: The system should allow different user roles (Customer, Seller,
Admin) to register accounts using email addresses and secure passwords. User
registration forms should collect relevant information for each user role (e.g.,
customer billing address, seller store details).
o Login: A secure login process requires users to enter their registered email
address or username and password. The system should implement password
hashing and encryption to protect user credentials from unauthorized access.
Additional security measures like two-factor authentication can be implemented
for enhanced protection.
o User Roles and Permissions: User roles define access levels within the system.
Customers can view products, add items to their cart, and place orders. Sellers can
manage their product listings, inventory, and potentially fulfill orders (depending
on the platform setup). Admins have the highest level of access, allowing them to
 manage users, products, orders, website settings, and potentially access system
analytics.

 Order Management:
Order Status: Orders should display their current status throughout the fulfillment
process (e.g., "Pending Payment," "Processing," "Shipped," "Delivered"). This provides
transparency to both customers and sellers regarding order progress.
o Order Tracking: Customers might be able to track their orders in real-time using
a dedicated tracking feature. This could involve integrating with the chosen
shipping provider's API to display estimated delivery timelines and shipment
location updates.

 Account Management:
o Profile Updates: Users should be able to update their account information,
including personal details (e.g., name, address, phone number) and potentially
their account settings (e.g., email preferences, password changes).
o Customer Order History: Customers should have access to their order history,
allowing them to view past purchases with details like order date, products
ordered, total amount, and order status. This functionality provides easy access to
past purchase information for reference or potential returns/exchanges.
o Seller Account Management: In addition to basic profile updates, Sellers might
have functionalities to manage their store settings, such as branding elements
(e.g., store logo, banner), return policies, or communication preferences with
customers.
6. Non-Functional Requirements

These requirements define the desired characteristics of the e-commerce system, influencing user
experience and overall system performance. Here's a breakdown with further considerations:

 Performance:
o Scalability: The e-commerce platform should be scalable to accommodate a
growing user base and increased traffic volume. This ensures smooth operation
during peak seasons or periods of high demand. Techniques like using cloud-
based infrastructure or implementing caching mechanisms can improve
scalability.
o Response Times: Website response times should be fast to maintain a positive
user experience. Fast page load times and quick product search results are crucial
for customer satisfaction. Performance testing helps identify bottlenecks and
optimize the system for responsiveness.
 o High Availability: The website should strive for high availability, minimizing
downtime and ensuring consistent accessibility for customers and sellers.
Techniques like using redundant servers and implementing disaster recovery
plans can improve uptime.
 Security:
o Data Encryption: All sensitive data, including user passwords, financial
information (credit card details), and customer order details, must be encrypted at
rest and in transit. This protects user data from unauthorized access or breaches.
o Regular Security Audits: Regular security audits and penetration testing help
identify potential vulnerabilities in the system. Promptly addressing these
vulnerabilities minimizes security risks and protects user data.
o Compliance with Regulations: The e-commerce platform might need to comply
with industry-specific regulations or data privacy laws (e.g., PCI-DSS for
payment card data, GDPR for user data protection in Europe).

 Usability:
o Intuitive Interface Design: The user interface (UI) design should be intuitive and
user-friendly, allowing customers of varying technical skills to navigate the
website seamlessly. Clear labeling of features, consistent design patterns, and
appropriate use of visual elements contribute to a positive user experience.
o Accessibility: The website should be accessible to users with disabilities. This
includes implementing features like screen reader compatibility, keyboard
navigation options, and alternative text descriptions for images.
o Responsive Design: The website should be responsive and adapt its layout to
display correctly across various devices (desktop computers, tablets,
smartphones). This ensures optimal user experience regardless of the device used
to access the website.

Additional Considerations:
  Content Management System (CMS): An e-commerce platform might integrate with a
CMS allowing content editors to manage website content (e.g., product descriptions, blog
posts, promotional banners). This empowers content creators to maintain website content
without requiring extensive development expertise.
 Analytics and Reporting: Integration with analytics tools allows e-commerce businesses
to track user behavior, website traffic, and conversion rates. These insights are valuable
for optimizing the website, product offerings, and marketing strategies.
 Multilingual Support: For businesses targeting international markets, the platform
might need to support multiple languages. This includes translating website content,
product descriptions, and user interface elements to cater to a broader audience.

7. Assumptions and Dependencies

An SRS (Software Requirements Specification) document outlines the functionalities and

requirements of a software system. The "Assumptions and Dependencies" section clarifies
external factors that influence the development process but are not directly controlled by the
development team. Here's a breakdown of the points mentioned in the provided text:

Assumptions:

 Basic Internet Access and Standard Web Browsers: The system assumes users have
access to the internet and use standard web browsers (e.g., Chrome, Firefox) to access the
website. This eliminates the need for developing functionalities specific to outdated
browsers or users with limited internet connectivity.
  User Capabilities: The document assumes basic user capabilities, such as navigating
websites, using search functions, and completing online forms. This helps focus
development efforts on core functionalities rather than extensive user education.

Dependencies:

 Third-Party APIs and Services: The development team relies on access to necessary
third-party APIs (Application Programming Interfaces) and services. Examples include
payment gateways (e.g., PayPal, Stripe) for secure online transactions, email delivery
services, or analytics platforms. Integration with these services might require additional
development effort or specific configurations.
 External Development Teams: For some functionalities, the development team might
depend on external development teams. This could involve integrating with a shipping
provider's system to generate shipping labels or working with a content management
system (CMS) provider for managing website content. Clear communication and
collaboration with these external teams are crucial for successful integration and project
completion.
Additional Considerations:

 Hardware and Software Requirements: While not explicitly mentioned in the provided
text, some SRS documents also specify any hardware or software requirements for the
system to function properly (e.g., minimum server specifications, operating system
requirements).
 Deployment Environment: The document might clarify the intended deployment
environment for the software (e.g., cloud-based deployment, on-premise servers).

8. References

List any relevant references you consulted during the project, such as project proposals, technical
documentation, or external sources.