WEB APPLICATION

DEVELOPMENT
GROUP NUMBER 03
 Question
• To Create an e-commerce website with shopping cart functionality and
an order tracking system
Software Requirements Specification (SRS)
1. Introduction

• At Reconex, we build digital solutions that empower users to buy, sell,

and list products easily on our platform. Our services include:
• Allowing seller to sell products
• Allowing users as customer to buy products
• Allowing users as seller to upload and manage their products
1.1 Purpose
• The purpose of this document is to define the software requirements
for an e-commerce web application. The system allows users
(customers) to browse products, manage shopping carts, place
orders, and track those orders. It also includes functionalities for
sellers to manage products and admins to manage users and
transactions.
Scope of the E-commerce
System
• Scope:
• This e-commerce system is designed to provide a
comprehensive online shopping experience, encompassing
functionalities for customers, sellers, and administrators. The
system's scope specifically includes the following key areas:
• Customer Registration and Login: This module will allow
new users to register for an account and existing users to log
in securely. It will handle user authentication and profile
management.
• Product Browse and Search: Users will be able to browse
through various product categories and utilize a search
function to find specific products. This includes displaying
product details such as descriptions, images, and pricing.
Scope of the E-commerce
System
• Secure Order Placement and Payment: The system will facilitate
secure order placement, guiding customers through the checkout
process. It will integrate with payment gateways to enable secure
online transactions.
• Order Tracking: Following an order, customers will be able to track the
status of their purchases, from processing to shipment and delivery.
• Admin and Seller Dashboards: Dedicated dashboards will be provided
for both administrators and sellers. The admin dashboard will allow
for system oversight, user management, and product catalog
management. The seller dashboard will enable sellers to manage their
products, view orders, and track sales performance.
Intended Audience for the System

• Developers: This group will be directly involved in designing, coding,

and maintaining the system.
• Project Managers: Responsible for the overall planning, execution,
and closing of the project, project managers need high-level
overviews of features, timelines, resources, and potential risks.
• Testers: Their role is to identify bugs, verify functionality, and ensure
the system meets quality standards.
• Stakeholders (Business Owners, Clients): This broad category
includes individuals or groups who have a vested interest in the
success of the e-commerce system.
1.4 Definitions, Acronyms, and
Abbreviations
SRS – Software Requirements Specification
UI – User Interface
CRUD – Create, Read, Update, Delete
JWT – JSON Web Token (used for authentication)
SKU – Stock Keeping Unit
2. Overall Description

Product Perspective
• The system is a web-based application built using a client-server
architecture. It will be mobile responsive and accessible on all major
browsers.
 2.2 Product Functions
•Customer registration and login: Allows new users to create accounts and existing
users to securely access the e-commerce system.
•Product catalog with search and filter: Enables customers to browse available
products, and efficiently find specific items using search keywords or by applying
various filters.
•Checkout and order confirmation: Guides customers through the final steps of
purchasing, including payment processing, and provides a confirmation of their placed
order.
2.2 Product Functions
•Track order status in real-time: Allows customers to view the
current status and location of their placed orders as they move
through the fulfillment process.
•Seller product management: Empowers sellers to add, edit,
and remove their product listings, including details, pricing, and
inventory.
•Admin management of users and system settings: Provides
administrators with tools to oversee user accounts (customers
and sellers) and configure overall system parameters and
functionalities.
2.3 User Classes and
Characteristics
• Admin: Full access to all features, user/content/revenue
management.
• Seller: Can upload/manage products, view orders, pay posting fees.
• Customer: Can browse/order products, rate/report sellers, manage
Favorites.
2.4 Operating Environment

• Web browsers (Chrome, Firefox, Safari, Edge)

Server-side OS: Linux or Windows
DBMS: MySQL or MongoDB
2.5 Constraints
•Must be GDPR compliant: The system's design and operation must
adhere to the General Data Protection Regulation, ensuring the
lawful and secure processing of personal data, including user
consent, data access, and data deletion rights.
•Use of RESTful API architecture: All communication between
different parts of the system (frontend, backend, and potentially
third-party services) will be built following the principles of RESTful
APIs, promoting statelessness, a client-server architecture, and
uniform interfaces.
•Payment module will simulate transactions (not real gateway): For
development and testing purposes, the payment processing
functionality will not integrate with a live, real-world payment
gateway.
2.6 Assumptions and
Dependencies
• Sellers will be approved by Admin before posting products
Payment system will simulate 'Paid' status
3. Functional Requirements
The e-commerce system will support a range of functionalities to cater
to different user roles and ensure a comprehensive online shopping
experience.
Function Requirement: User Management and Security:
•User Registration: Users must be able to register as either a customer or
a seller.
•Secure Login: Users must be able to log in securely using a password or
an authentication token.
•Seller Approval: Administrators (Admins) can approve or reject new seller
registrations.
•Admin User Management: Admins can manage all users within the
system,
including Create, Read, Update, and Delete (CRUD) operations for both
customer and seller accounts.
Function Requirement:Product Management (Seller &
Admin):

•Seller Product Management: Sellers can add, edit, and delete

their listed products.
•Product Attributes: Each product must include essential
details: name, price, image, description, and stock quantity.
•Admin System Management: Admins can manage product
categories and view system reports.
 Function Requirement: Product Browse and contact
with seller (Customer):

•Product Browse and Search: Customers can browse

products by defined categories or search for specific
items using keywords.
•Product Details: Customers can view detailed
information for each product.
•Contact to seller: Customers can contact to get products
to buying.
Function Requirement:Order Management (Customer,
Seller & Admin):

•Order Placement: Customers can place orders directly from their

shopping cart.
•Stock Update: The system must automatically update the product
stock quantity after a successful order is placed.
•Order Statuses: Orders will have distinct statuses: Pending, Shipped,
and Delivered.
•Customer Order Tracking: Customers can view the current status and
history of their placed orders.
•Seller Order Status Update: Sellers can update the shipping status of
an order that originated from their products.
 4. Non-Functional Requirements
Non-functional requirements specify criteria that can be used to judge the operation of a system, rather than specific behaviors. They define the system's quality attributes and constraints.

Performance:
• Page Load Time: All web pages within the system should load in less than
3 seconds under normal operating conditions.
• Concurrency: The system must be capable of handling up to 10,000
concurrent users without significant degradation in performance.
Non-function Requirement
Reliability & Availability:
• System Uptime: The system must achieve an uptime of 99.9%,
meaning minimal unscheduled downtime.
• Data Persistence: In the event of a system failure, all critical data
must persist and be recoverable.
Security:
• Secure Data Transmission: All data transmitted between the client and
the server, and within the system, must use HTTPS (Hypertext
Transfer Protocol Secure) to ensure encryption and data integrity.
Non-function Requirement
• Password Security: User passwords must be stored in an encrypted format
using the crypt hashing algorithm to protect against unauthorized access.
• Authorization: Only authorized users (e.g., authenticated customers, sellers,
or administrators) shall be able to access resources and functionalities
relevant to their roles.
Usability & User Experience:
• Responsive and Intuitive UI: The User Interface (UI) should be responsive,
adapting to different screen sizes and devices, and intuitive, allowing users to
easily understand and navigate the system.
• Task Completion Efficiency: Users should be able to complete any major task
(e.g., placing an order, adding a product) within a maximum of three clicks.
Non-Function Requirement of the
system
Maintainability & Extensibility:
• Modularity: The system architecture should be modular to facilitate
future feature expansion, modifications, and easier maintenance.
• Code Quality: All code developed for the system should adhere to
industry-standard documentation practices and formatting guidelines
to ensure readability and maintainability.
Compatibility:
• Browser Compatibility: The system must function correctly and
consistently across all major modern web browsers (e.g., Google
Chrome, Mozilla Firefox, Microsoft Edge, Apple Safari).
Entity Relationship Diagram (ERD) - Key Relationships Between
09 Tables

• This is a summary of the key relationships between 09 tables from the

provided database system, presented in ERD format using a diagram
structure. The table includes:
- Names of the related tables
- Action word to place in the diamond (relationship verb)
- Type of relationship (Cardinality)
- Brief explanation
Appendix A: ER Diagram (Database
design)
Appendix B: Use Case Diagram