Project Name

Software Requirements Specification Document

Date: 29 Nov, 2024

Version #: 846022708.doc

2/1/2025, 7:13 PM 1
 Version History

VERSION AUTHOR(S) CHANGE DESCRIPTION DATE NOTES

2/1/2025, 7:13 PM 2
 Table of Content

1 Introduction................................................................................................................................................4
1.1 System Overview...............................................................................................................................4
1.2 Operating Environment......................................................................................................................4
1.3 Conceptual Model..............................................................................................................................5
2 Functional Requirements..........................................................................................................................8
2.1 Product Services................................................................................................................................9
2.2 User Interface Specifications.............................................................................................................9
2.3 External Interfaces and Database Requirements............................................................................10
2.4 Error Handling..................................................................................................................................11
2.5 Foreseeable Functional Changes and Enhancements....................................................................13
3 Non-Functional Requirements.................................................................................................................14
3.1 Performance Requirements.............................................................................................................14
3.2 User Documentation and Other User Aids.......................................................................................15
3.3 Development Requirements.............................................................................................................15
3.4 Foreseeable Non-Functional Changes............................................................................................17
4 Remarks and Guidelines for Later Lifecycle Phases..............................................................................18
5 Glossary and Index.................................................................................................................................19

2/1/2025, 7:13 PM 3
1 Introduction

1.1 System Overview

The proposed mobile application facilitates the buying and selling of used items. The platform
connects sellers, buyers, and delivery services in a seamless and user-friendly manner. Sellers can
list their used products, subject to approval by an administrator, ensuring quality control and
adherence to platform policies. Buyers can browse approved products, make purchases, and arrange
for delivery through integrated delivery services.
The key features of the system include:
 Seller Functionality: Sellers can create accounts, list products for sale, and manage their
listings.
 Administrative Control: Administrators can review product submissions, approve or reject
listings, and ensure the quality and legality of items displayed.
 Buyer Functionality: Buyers can browse product categories, search for specific items, and
complete purchases through secure payment options.
 Delivery Services Integration: Delivery services handle logistics, transferring items from
sellers to buyers efficiently.

1.2 Operating Environment

The mobile application for buying and selling used items is designed to operate on modern mobile
devices. The application will run on Android platform. Below are the specifications for the target
hardware and software environment:
Target Hardware Environment:
Optimal Configuration:
 Device: Mobile Phone
 Operating System: Android 11 or higher
 Processor: Octa-core 2.0 GHz or better
 RAM: 4 GB or higher
 Storage: 100 MB free space for app installation
 Network: Stable internet connection
Minimal Configuration:
 Device: Smartphone
 Operating System: Android 8.0 or higher
 Processor: Quad-core 1.5 GHz
 RAM: 2 GB
 Storage: 50 MB free space for app installation
 Network: Stable Internet connection

2/1/2025, 7:13 PM 4
 Target Software Environment:
Backend:
 Server: Cloud-based hosting
 Database: MySQL
 Backend Framework: Node.js
 APIs: REST or GraphQL for client-server communication
Frontend:
 Android Development: Java with Android Studio

1.3 Conceptual Model

A high-level graphical view of the major functionalities and components of the product can be depicted
using use-case diagrams. Below is a description of the key components and their relationships:
1. Buyer
Following are the use cases of buyer actor:
 Choose an Item
 Make Payment
 Track Delivery
 Rate Transaction
 Request Support
2. Seller
Following are the use cases of Seller actor:
 Track Delivery
 Rate Transaction
 Request Support
 Manage Listing
 Arrange Delivery
 Make Listing
3. Customer
Following are the use cases of Customer actor:
 Login
 Choose a Service
4. Delivery Service
Following are the use cases of Delivery Service actor:
 Track Delivery
 Deliver Product
 Provide Support

2/1/2025, 7:13 PM 5
  Pick up Product
 Manage Listings
 Confirm Delivery
5. Admin
Following are the use cases of Admin actor:
 Provide Support
 Manager Users
 Approve/Reject Listing
 Monitor Transactions

2/1/2025, 7:13 PM 6
2/1/2025, 7:13 PM 7
2 Functional Requirements

The following sections detail the services and operations provided by the system, describing the
functionality comprehensively and specifying its relationship with users and the environment. The
requirements are categorized below.
FR 1. User Management
FR 1.1. The system shall allow users (sellers, buyers, and administrators) to register and log in.
FR 1.1.1. The system shall support account creation using email and password.
FR 1.1.2. The system shall allow users to reset their passwords if forgotten.
FR 1.2. The system shall differentiate between user roles (seller, buyer, administrator).
FR 1.2.1. The system shall provide specific interfaces and permissions based on user roles.
FR 1.2.2. The system shall allow administrators to manage user accounts (e.g., suspend, delete).
FR 2. Product Listing Management
FR 2.1. Sellers shall be able to add used products to the platform.
FR 2.1.1. The system shall require sellers to provide product details.
FR 2.1.2. The system shall validate that all required product information is provided.
FR 2.2. Administrators shall approve or reject product listings before they are displayed to buyers.
FR 2.2.1. The system shall notify sellers when their product is approved or rejected.
FR 2.2.2. The system shall log the administrator's decision with a timestamp.
FR 3. Product Search and Browsing
FR 3.1. Buyers shall be able to browse available products.
FR 3.1.1. The system shall categorize products based on type, price range, and location.
FR 3.1.2. The system shall display product details (title, description, price, and images).
FR 3.2. Buyers shall be able to search for specific products.
FR 3.2.1. The system shall provide a search bar with filters (e.g., price, category, location).
FR 3.2.2. The system shall display search results based on relevance.
FR 4. Order and Delivery Management
FR 4.1. Buyers shall be able to purchase products through the platform.
FR 4.1.1. The system shall support secure payment options (e.g., credit card, PayPal).
FR 4.1.2. The system shall generate a receipt for each transaction.
FR 4.2. The system shall facilitate delivery services for purchased products.
FR 4.2.1. The system shall notify delivery services when a purchase is made.
FR 4.2.2. The system shall track the delivery process and update the buyer and seller.
FR 5. Notifications and Communication
FR 5.1. The system shall notify users about important events (e.g., approval of products, order status).
FR 5.1.1. Notifications shall be sent via in-app messages and emails.

2/1/2025, 7:13 PM 8
 FR 5.2. The system shall provide a chat feature for communication between buyers and sellers.
FR 5.2.1. The chat shall be accessible only after a buyer initiates an inquiry about a product.

2.1 Product Services

The mobile application will provide the following high-level services and computations:
1. User Registration and Authentication
The application will allow users (sellers, buyers, and administrators) to create accounts, log in, and
manage their credentials. It will also ensure secure authentication processes, such as email
verification and password recovery.
2. Product Listing Management
Sellers can list their used items for sale by providing essential details such as title, description,
images, and price. Administrators will review these listings to approve or reject them based on
predefined policies.
3. Product Browsing and Search
Buyers can explore the available products through categorized browsing and use search
functionalities with filters like price range, category, and location to find specific items.
4. Purchasing and Payment Processing
Buyers can purchase approved products through the application, with secure payment options
provided for seamless transactions. A receipt will be generated for each purchase.
5. Delivery Management
The application will facilitate delivery services by notifying logistics providers when a product is
purchased. It will also track the delivery status and notify both buyers and sellers about updates.
6. Notifications and Alerts
Users will receive notifications about significant actions and updates, such as product approval, order
confirmation, delivery status, and chat messages.
7. Buyer-Seller Communication
Buyers can directly contact sellers through an in-app chat feature to inquire about listed products. This
service is initiated only for active product listings.
8. Administrative Control
Administrators will have the capability to manage user accounts, approve or reject product listings,
and monitor activities within the application to ensure compliance with platform policies.

2.2 User Interface Specifications

Describe and sketch the screens, windows, graphics, and other visual aspects of the product. Specify
the interaction or dialog conventions governing the user interface.

2/1/2025, 7:13 PM 9
 2.3 External Interfaces and Database Requirements

2.3.1 External Interfaces

The application will interface with the following external systems and environments:
1. Payment Gateways:
APIs for processing payments e.g. stripe which will enable secure transactions between buyers and
sellers
2. Delivery Services:
APIs of logistics providers (e.g., FedEx, local courier services) to facilitate the transportation of
products from sellers to buyers and track delivery status.
3. Push Notification Services:
Firebase Cloud Messaging (FCM), which will be used to send real-time notifications to users for
events such as product approvals, order updates, and chat messages.
4. Authentication Services:
OAuth or similar protocols for secure user authentication to manage secure login and user identity
verification.
2.3.2 Database Requirements
The system will use a relational database to store and manage application data. Below is the logical
organization of the database:
1. User Table:
In the table, there are fields, UserID (Primary Key), Name, Email, Password, Role (Buyer, Seller,
Admin), RegistrationDate, ProfileStatus to store user account details and roles.
2. Product Table:
In this table, there are fields, ProductID (Primary Key), SellerID (Foreign Key), Title, Description,
Category, Price, Images, ApprovalStatus, CreatedDate, UpdatedDate to maintain information about
products listed by sellers.
3. Order Table:
In this table, there are fields, OrderID (Primary Key), BuyerID (Foreign Key), ProductID (Foreign Key),
OrderDate, PaymentStatus, DeliveryStatus, TotalAmount to track details of buyer transactions and
order statuses.
4. Chat Table:
In this table, there are fields, ChatID (Primary Key), BuyerID (Foreign Key), SellerID (Foreign Key),
ProductID (Foreign Key), Message, Timestamp to log messages between buyers and sellers for
product inquiries.
5. Notification Table:
In this table there are fields, NotificationID (Primary Key), UserID (Foreign Key), Message,
NotificationType, Status (Read/Unread), Timestamp to store and manage notifications sent to users.
6. Delivery Table:
In this table, there are fields, DeliveryID (Primary Key), OrderID (Foreign Key), DeliveryServiceID
(Foreign Key), PickupDate, DeliveryDate, DeliveryStatus to manage delivery-related information for
orders.

2/1/2025, 7:13 PM 10
 7. Administrator Logs Table:
In this table, there are fields, LogID (Primary Key), AdminID (Foreign Key), Action, TargetID
(ProductID/UserID), Timestamp to record actions performed by administrators for auditing purposes.
Database Management System (DBMS):
Preferred DBMS: MySQL or PostgreSQL.
Rationale: Scalability, reliability, and compatibility with mobile applications and cloud environments.

2.4 Error Handling

The system will identify and respond to various exceptional and error conditions to ensure robust
functionality and a seamless user experience. Below is a catalog of potential errors and their
respective handling mechanisms:
1. User Authentication Errors
Condition Response
Incorrect email or password entered during Display a message: "Invalid email or password.
login. Please try again."
Allow up to three login attempts before
temporarily locking the account for 15 minutes.
Password reset request for an unregistered Display a message: "Email not registered.
email address Please check and try again."

2. Product Listing Errors

Condition Response
Seller attempts to submit a product listing with Highlight missing or incorrect fields with error
incomplete or invalid information (e.g., missing messages.
fields or unsupported image format).
Prevent submission until all fields are correctly
completed.
Administrator attempts to approve or reject a Log the error in the administrator logs.
product with an invalid product ID
Display a message: "Product does not exist.
Please verify and try again."

3. Payment Processing Errors

Condition Response
Payment gateway declines a transaction (e.g., Display a message: "Payment failed. Please
insufficient funds, expired card). check your payment details and try again."
Allow the buyer to reattempt the payment or
choose a different payment method.
Network error during payment processing. Display a message: "Network error. Please
check your connection and try again."
Retry the payment process automatically up to
two times before prompting the user to
manually retry.

2/1/2025, 7:13 PM 11
 4. Delivery Management Errors
Condition Response
Delivery service API fails to respond or returns Log the error and notify the administrator.
an error.
Display a message to users: "Delivery service
is temporarily unavailable. Please try again
later."
Delivery tracking information is missing or Notify the delivery service API for updated
outdated. information.
Inform the buyer and seller: "Delivery status
update is delayed. We are working to resolve
this issue."

5. Database and System Errors

Condition Response
Database connection failure. Log the error and send an alert to system
administrators.
Display a generic error message to users:
"System is currently experiencing issues.
Please try again later."
Attempt to access a resource that does not exist Display a message: "The requested resource is
not available."
Redirect the user to the homepage or previous
valid page.

6. Notification and Chat Errors

Condition Response
Failure to deliver a chat message due to a Notify the sender: "Message delivery failed.
network or server issue. Retrying..."
Automatically retry sending up to three times
before informing the user to retry manually.

Notifications fail to send due to a service Log the error and notify the administrator.
outage.
Retry sending notifications when the service
becomes available.

2/1/2025, 7:13 PM 12
 7. Network Errors
Condition Response
User attempts an action with no internet Display a message: "No internet connection.
connection. Please check your connection and try again."
Queue non-essential actions (e.g., message
sending) for automatic retry when the
connection is restored.

2.5 Foreseeable Functional Changes and Enhancements

The future of the app will boast an AI-based recommendation system to suggest products to suit you
personally; a bidding feature to incorporate an auction system; and expanded delivery options. A
global audience can be catered with multi-currency and multi language support, social media
integration, social media integration and a rating system can improve user engagement and trust. And
for added convenience, plus incentive to use the app frequently, advanced features like a seller
subscription plan, in app wallet and loyalty program will be included. The purpose of these changes is
to make the product more useful, to increase the market and to offer a better user experience.

2/1/2025, 7:13 PM 13
3 Non-Functional Requirements

The non-functional requirements define the operational constraints, performance expectations, and
quality attributes of the system. These requirements ensure that the system performs efficiently and
meets user and environmental needs:
NFR 1. Performance Requirements
NFR 1.1. The system must support up to 1000 concurrent users without performance degradation.
NFR 1.2. Product listings should load within 2 seconds under normal conditions.
NFR 1.3. The payment processing system must complete transactions within 5 seconds.
NFR 2. Reliability Requirements
NFR 2.1. The system must have an uptime of 99.9% per month.
NFR 2.2. All critical system operations must have redundancy mechanisms to prevent failure.
NFR 3. Scalability Requirements
NFR 3.1. The system must scale to handle a 200% increase in traffic during peak shopping periods.
NFR 3.2. Database capacity must expand dynamically to support additional product listings without
manual intervention.
NFR 4. Usability Requirements
NFR 4.1. The mobile application interface must conform to Material Design guidelines for Android.
NFR 4.2. New users must be able to complete the registration process within 2 minutes.
NFR 5. Security Requirements
NFR 5.1. The system must enforce two-factor authentication (2FA) for all administrative accounts.
NFR 5.2. All sensitive data, such as passwords and payment information, must be encrypted.
NFR 5.3. The system must comply with GDPR and CCPA regulations for data privacy.

3.1 Performance Requirements

The system must meet the following performance expectations to ensure efficient and seamless
operation:
1. Efficiency
 The application must respond to user interactions within 2 seconds for 90% of actions, such as
loading product details or submitting a purchase request.
 The backend server should handle 100 API requests per second without performance
degradation.
2. Reliability
 The system must maintain 99.9% uptime, ensuring continuous availability for users.
 Key operations like product approval and payment processing must include failover
mechanisms to guarantee uninterrupted service.

2/1/2025, 7:13 PM 14
 3. Robustness
 The system must handle unexpected scenarios, such as sudden disconnection or API failures,
by retrying operations or notifying users of issues.
 Incomplete transactions must be rolled back automatically to maintain data integrity.
4. Portability
 The application must function on Android (version 8.0 and above).
 The system should adapt to various screen sizes and resolutions seamlessly.
5. Memory and Resource Usage
 The mobile application must not exceed 200 MB of storage space, including cached data.
 Memory usage must not exceed 150 MB during active use on devices with 2 GB RAM or
more.
6. Response Time
 Product searches and filter results must display within 2 seconds for datasets containing up to
10,000 items.
 Payment confirmation must complete within 5 seconds under normal network conditions.

3.2 User Documentation and Other User Aids

The following documentation and user aids will be provided to ensure a smooth onboarding
experience and continued usability for the application:
User Tutorials
Quick Start Guide: A concise guide outlining the basic steps for registering, adding products,
browsing, and purchasing.
Video Tutorials: Short videos demonstrating key features, such as adding a product as a seller,
searching for items, and completing a purchase.
Interactive Walkthroughs: Built-in app tutorials guiding new users through the main functions during
their first login.
Reference Material
User Manual: A detailed document covering all features and functions of the application, including
troubleshooting common issues.
FAQs Section: Answers to frequently asked questions about using the app, managing accounts, and
resolving problems.
Glossary: Definitions of terms and concepts used within the application, such as product approval
and delivery tracking.

3.3 Development Requirements

The development of the application will adhere to the following quality standards, methods, and tools
to ensure reliability, maintainability, and customer satisfaction:

2/1/2025, 7:13 PM 15
 1. Quality Standards
 The application will comply with ISO/IEC 25010 standards for software product quality,
ensuring usability, performance, and security.
 Code quality will be maintained according to Google’s Android Coding Standards.
 Regular code reviews will be conducted to ensure adherence to best practices.
2. Verification and Validation Requirements
 Third-party testing teams of my fellows requested to evaluate the application’s functionality,
security, and performance.
 Automated and manual testing processes will validate critical features, such as payment
processing, product approval workflows, and delivery tracking.
3. Testing Strategies
 Unit Testing: All individual components, such as product listing and purchase modules, will be
tested using tools like JUnit for Android.
 Integration Testing: Ensure seamless interaction between components like the user
interface, database, and delivery APIs.
 System Testing: Validate the application as a whole under simulated real-world scenarios.
 Performance Testing: Use tools like Apache JMeter to test response times and concurrency.
 User Acceptance Testing (UAT): Final testing phase involving a subset of target users to
gather feedback and validate the product meets user needs.
4. Development Methods
 Agile Development: Iterative development with regular sprints to ensure flexibility and
incorporate user feedback.
 Continuous Integration/Continuous Deployment (CI/CD): Employ tools like GitHub Actions
to automate testing and deployment processes.
5. Tools and Techniques
 Programming Languages: Java for Android.
 Frameworks: Retrofit for API calls, Firebase for push notifications, and Stripe SDKs for
payment processing.
 Version Control: Git for source code management with repositories hosted on GitHub.
 Project Management: Use Jira or Trello to track progress, tasks, and issues.
6. Development Constraints
 The system must integrate with third-party APIs (e.g., delivery services, payment gateways)
specified by the customer.
 The application must be deployable on Android.
 Development must be completed within the allocated timeframe and budget as defined by the
customer.

2/1/2025, 7:13 PM 16
 3.4 Foreseeable Non-Functional Changes

Foreseeable non-functional changes for the application include performance enhancements to support
a larger user base, with optimizations such as caching and load balancing to meet faster response time
expectations. Compatibility updates may be required for new operating system versions, hardware
advancements like foldable screens, and potential integration with emerging technologies such as AI-
driven recommendations, voice commands, or blockchain for secure transactions. The system may
also need to scale globally, supporting multiple languages and currencies, while accommodating
enhanced security features, including biometric authentication and fraud prevention measures. Future
user experience improvements could focus on accessibility, incorporating features like WCAG 3.0
compliance, and integration with IoT or autonomous delivery systems, ensuring the application remains
adaptable to changing technological and user demands.

2/1/2025, 7:13 PM 17
4 Remarks and Guidelines for Later Lifecycle Phases

During the requirements analysis phase, several potential issues and pitfalls have been identified that
may impact later stages of the project lifecycle. One potential challenge is ensuring smooth integration
between multiple third-party services (e.g., payment gateways, delivery systems), which could lead to
delays or compatibility issues. To mitigate this, integration testing will be started early in the
development phase and choose reliable, well-documented APIs.
Another challenge is maintaining scalability as the user base grows, which may require significant
backend optimization, such as implementing micro services architecture or using cloud-based solutions
like AWS or Google Cloud for auto-scaling. Additionally, security will be a key concern throughout the
lifecycle, so regular security audits, penetration testing, and adherence to best practices in data
encryption and user authentication should be prioritized. A clear versioning strategy and rigorous
testing should be followed to prevent issues as the application evolves. In the user experience (UX)
design phase, early prototyping and user feedback collection will be crucial to avoid significant
redesigns later on.

2/1/2025, 7:13 PM 18
5 Glossary and Index

Glossary
API (Application Programming Interface): A set of protocols and tools for building software and
applications that allows different systems to communicate with each other.
Biometric Authentication: A security process that uses an individual's physical characteristics, such as
fingerprints or facial recognition, to verify their identity.
Caching: The process of storing frequently accessed data in a temporary storage location for faster
retrieval.
CI/CD (Continuous Integration/Continuous Deployment): A development practice that involves frequent
code changes, automated testing, and deployment to streamline the software development lifecycle.
Encryption: The process of converting data into a code to prevent unauthorized access, ensuring
confidentiality.
Load Balancing: Distributing incoming network traffic across multiple servers to ensure no single server
becomes overwhelmed, enhancing performance and reliability.
Microservices Architecture: A design approach where an application is broken down into smaller,
independent services that communicate with each other, making it easier to scale and maintain.
Payment Gateway: A service that processes online payments, typically integrating with credit cards, digital
wallets, and bank accounts.
UAT (User Acceptance Testing): A phase of software testing where end-users verify that the system
meets their requirements and functions as expected.
WCAG (Web Content Accessibility Guidelines): A set of guidelines aimed at making web content more
accessible to people with disabilities.

2/1/2025, 7:13 PM 19
Index
API - 3.3, Glossary
Biometric Authentication - 3.4, Glossary
Caching - 3.4, Glossary
CI/CD - 3.3, Glossary
Encryption - 3.4, Glossary
Load Balancing - 3.4, Glossary
Microservices Architecture - 3.3, Glossary
Payment Gateway - 3.3, Glossary
UAT - 3.3, Glossary
WCAG - 3.4, Glossary

2/1/2025, 7:13 PM 20