Software Requirements

Specification
for

BooKaro

Version 1.0 approved

Prepared by

Prachi Shende (231071065)

Shreya Rajeev (231071067)
Mahima Sonawane (231071071)
Diksha Thongire (231071073)

Jan 29 , 2025

Copyright © 1999 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this
document.
Table of Contents
Table of Contents........................................................................................................................... ii
1.​ Introduction..............................................................................................................................1
1.1​ Purpose..............................................................................................................................................1
1.2​ Document Conventions.....................................................................................................................1
1.3​ Intended Audience and Reading Suggestions................................................................................... 1
1.4​ Product Scope................................................................................................................................... 1
1.5​ References......................................................................................................................................... 1
2.​ Overall Description..................................................................................................................2
2.1​ Product Perspective...........................................................................................................................2
2.2​ Product Functions............................................................................................................................. 2
2.3​ User Classes and Characteristics.......................................................................................................2
2.4​ Operating Environment.....................................................................................................................2
2.5​ Design and Implementation Constraints........................................................................................... 2
2.6​ User Documentation......................................................................................................................... 2
2.7​ Assumptions and Dependencies........................................................................................................3
3.​ External Interface Requirements........................................................................................... 3
3.1​ User Interfaces.................................................................................................................................. 3
3.2​ Hardware Interfaces.......................................................................................................................... 3
3.3​ Software Interfaces........................................................................................................................... 3
3.4​ Communications Interfaces...............................................................................................................3
4.​ System Features....................................................................................................................... 4
4.1​ System Feature 1- Inventory Management and Real-Time Book Availability................................. 4
4.2​ System Feature 2- User Driven Listing.............................................................................................4
4.3​ System Feature 3 - Dynamic Pricing................................................................................................ 4
4.4​ System Feature 4- Affordable and Flexible Payment Options..........................................................4
4.5​ System Feature 5 - User Verification for Security............................................................................ 4
5.​ Other Nonfunctional Requirements....................................................................................... 4
5.1​ Performance Requirements............................................................................................................... 4
5.2​ Safety Requirements......................................................................................................................... 5
5.3​ Security Requirements...................................................................................................................... 5
5.4​ Software Quality Attributes.............................................................................................................. 5
5.5​ Business Rules.................................................................................................................................. 5
6.​ Other Requirements................................................................................................................ 5
Appendix A: Glossary................................................................................................................... 5
Appendix B: Analysis Models....................................................................................................... 5
Appendix C: To Be Determined List............................................................................................ 6
1

1.​ Introduction
1.1​ Purpose
This document outlines the software requirements for the Book Karo e-commerce platform, aimed
at providing college students with a secure, user-friendly platform to buy, sell, and rent textbooks,
as well as other materials. The document specifies the functional, non-functional, and technical
requirements for the system, as well as the design and security features.

1.2​ Document Conventions

This document follows the following conventions:

Bold is used for section headings and key terms.

Monospaced font is used for code snippets and URLs.
Requirements are categorized as [High], [Medium], or [Low] priority.
External references are enclosed in [square brackets].
Diagrams are included with explanations.
Functional requirements are written in active voice; non-functional requirements address system
qualities like performance and security.

1.3​ Intended Audience and Reading Suggestions

Developers: Guide for building the platform. Focus on Functional and Technical Requirements.
Project Managers: Track project progress. Focus on Product Scope and Requirements.
Testers: Ensure platform functionality. Focus on Testing Requirements.
Stakeholders: Align platform with business goals. Focus on Product Scope and Functional
Requirements.
Users: Understand features and experience. Focus on Functional and Nonfunctional Requirements.

Reading Suggestions:
Developers & Managers: Product Scope → Functional & Technical Requirements
Testers: Testing Requirements → Functional & Non-Functional Requirements
Stakeholders: Product Scope → Functional Requirements

1.4​ Product Scope

Book Karo is a web and mobile e-commerce platform designed specifically for college students to buy,
sell, and rent new, used, and digital textbooks. The platform offers various features like real-time book
availability, dynamic pricing, payment flexibility, and a secure communication system for user
negotiations.
It also integrates third-party services for payment processing and book data retrieval.

The platform is built to be user-friendly, offering a customizable experience based on user preferences,
with multiple payment options for affordability and security. The system aims to offer a one-stop solution
for students’ textbook needs.

1.5​ References
Google Books API: https://developers.google.com/books
Open Library API: https://openlibrary.org/developers
1

2.​ Overall Description

2.1​ Product Perspective

The "Book Karo" platform is a new, self-contained e-commerce solution specifically designed to address
the textbook buying, selling, and renting needs of college students. It is not a follow-on product of an
existing system, but a fresh platform aimed at streamlining the textbook marketplace with a user-friendly
interface. "Book Karo" will allow students to easily access textbooks for their courses at affordable prices,
ensuring an optimized experience. The platform will integrate features like real-time inventory tracking,
secure payment systems, and student-centric features like reviews, book conditions, and pricing
comparisons.

The system will need to interface with external payment gateways for transactions, as well as third-party
service providers for shipping or delivery services, ensuring smooth operations. As the platform grows, it
may also interface with academic institutions for bulk orders or textbook recommendations.

A diagram of the system can show the core features like user management, book inventory
management, and transaction processing interacting with external systems (payment gateways, delivery
services).

2.2​ Product Functions

The primary operations and services offered by the 'Book Karo' platform are:

User Registration & Account Management: Allows students to sign up, create accounts, and
manage their profiles.
Book Listings: Enables students to post new or used books for sale or rent, including notes and
previous year questions (PYQs).
Book Search: Search functionality based on course name, author, title, condition (new/second-hand),
and price range.
Real-time Inventory Management: Tracks book availability and prevents over-selling or
under-selling by updating inventory in real-time.
Transaction Processing: Handles secure payments and confirms transactions for book purchases
or rentals.
Ratings & Reviews: Allows users to rate books and sellers, providing transparency and building
trust.
Notifications: Sends alerts about book availability, price drops, or transaction status.
Security: Ensures secure user authentication and transaction processing.

2.3​ User Classes and Characteristics

Student Buyers/Renters:
Frequency of Use: Regular users, primarily during the start of academic terms or for specific
course requirements.
Characteristics: Typically college students looking for affordable textbooks. They require ease
of
access to book listings, secure payment options, and efficient delivery methods.
Privileges: Access to browse, purchase, rent books, and leave reviews.

Student Sellers:
Frequency of Use: Occasional users, mostly when students want to sell their used books or
notes after completing a course.
Characteristics: Students who are selling books and notes to earn money or make textbooks
available for other students.
2

Privileges: Can list books, set prices, and manage their inventory. Can also view buyer feedback
and ratings.

Admin/Platform Owner:

Frequency of Use: Frequent, as they are responsible for overseeing platform operations.
Characteristics: Administrative users who manage the overall platform, book listings, and user
accounts.
Privileges: Full access to manage book listings, handle user disputes, and monitor financial
transactions.

2.4​ Operating Environment

The software will operate in the following environment:

Hardware Platform: The platform is designed to be accessible on both desktop and mobile
devices, ensuring students can use the service anywhere.
Operating Systems: It will be compatible with major operating systems, including Windows,
macOS, and Linux for desktop use, and iOS and Android for mobile applications.
Software Dependencies:
Web application framework: React or Angular (Frontend)
Backend: Node.js with Express for API handling
Database: MongoDB or PostgreSQL for storing user, book, and transaction data
Payment Gateway: Stripe or PayPal for secure payment processing

2.5​ Design and Implementation Constraints

The development of Book Karo will be guided by several key constraints to ensure the platform
is secure, scalable, and efficient. First, the platform must adhere to security best practices,
including SSL/TLS encryption, user authentication through OAuth, and secure payment
processing via trusted third-party services like Stripe. Scalability is also a key consideration, as
the system must be able to handle increased traffic during peak academic periods. The
payment gateway will be integrated with third-party services, meaning there will be limited control
over transaction processing, but ensuring secure and reliable payments is a priority. The system
will use a relational database (PostgreSQL) for managing inventory, users, and transactions, or
potentially a NoSQL database like MongoDB for greater flexibility with data structures.
Additionally, mobile optimization is crucial for providing a seamless user experience across
devices. Finally, compliance with academic regulations surrounding the resale of textbooks will
be considered to ensure the platform operates within legal boundaries.

2.6​ User Documentation

To ensure users can effectively navigate and utilize the Book Karo platform, the following user
documentation will be provided. This will offer comprehensive support to all user classes, from
buyers and sellers to platform administrators and developers.

User Manual: A comprehensive guide detailing how to use the platform, covering account
registration, searching for textbooks, buying, selling, and renting textbooks, and managing user
profiles.
Online Help: In-app help and FAQs that guide users through common actions and
troubleshooting steps.
Tutorials: Step-by-step tutorials that demonstrate how to list books for sale, make purchases, and
leave reviews.
Technical Documentation: For developers and administrators, detailing system architecture,
APIs, and integration points.
3

2.7​ Assumptions and Dependencies

Third-party Integrations: Google Books API and Stripe for payment processing) will be available and
functional throughout the development and deployment phases
Cloud Infrastructure: The platform will rely on cloud services (AWS, Google Cloud, or Azure) for hosting
and scalability. Assumes that these cloud services will remain stable and accessible.
User Authentication: The assumption is that users will have access to standard devices (smartphones,
laptops, etc.) with internet access to utilize the platform.
Payment Gateway Integration: Stripe Elements and other payment methods will function without
disruption. Any changes to Stripe’s features, security, or pricing models could affect the payment process.

Dependencies:

Third-Party APIs: The platform depends on external APIs (Google Books API, Open Library API) for
book data and payment gateway APIs (Stripe) for transaction handling.
External Libraries and Frameworks: The project relies on frameworks like React.js for frontend, Django
for backend, and Firebase for real-time capabilities. Any significant updates or discontinuations of these
technologies could affect the system.

3.​ External Interface Requirements

3.1​ User Interfaces

The e-commerce platform will feature an intuitive and accessible user interface, designed to
facilitate a seamless user experience for college students buying, selling, and renting textbooks.

Graphical User Interface (GUI) Standards:

Clean, modern, and minimalistic design for easy navigation.

Consistent theme and branding across all pages.
Standard buttons including Home, Search, Cart, Profile, Listings, Messages, and Help.
Pop-up modals for login, verification, and checkout processes.

Screen Layout Constraints:

Responsive design to support desktop, tablet, and mobile views.

Search bar with filters (book category, condition, price range, seller rating) prominently placed.
Profile dashboard displaying listings, purchases, and messages.

User Interface Components:

Book Listings Page: Displays books in grid format with thumbnail images, price, and availability.
Negotiation Chat Module: Enables students to discuss and finalize deals.
Payment Gateway: Secure checkout with various payment options.
4

3.2​ Hardware Interfaces

The platform will be designed to run efficiently across various hardware configurations, including:

Device Compatibility:
Desktop and laptop computers (Windows, macOS, Linux)
Tablets and smartphones (Android, iOS)

Server Requirements:

Cloud-based hosting for scalability.

Minimum 8GB RAM, multi-core processor, and SSD storage to support smooth operation.
Secure storage for user data and inventory tracking.

3.3​ Software Interfaces

The platform will integrate with various software components to ensure efficiency and
functionality. It will support Windows 10/11, macOS, Linux, Android, and iOS for cross-platform
accessibility.

For databases, the platform will use MySQL or MongoDB for structured data storage, handling
inventory, users, and transactions, while Redis will be utilized for caching real-time inventory
status to enhance performance.

In terms of external services and APIs, the platform will incorporate Stripe, PayPal, and
UPI-based payment gateways to ensure secure transactions. User authentication will be
managed through Firebase/OAuth, enforcing secure login via college email verification.

A real-time messaging system will be enabled using Twilio or WebSockets to facilitate smooth
communication between buyers and sellers. Data exchange between the front-end and back-end
will be handled through a secure JSON-based API, while RESTful services will be implemented
for dynamic pricing adjustments.

3.4​ Communications Interfaces

The communications functions for this e-commerce platform are crucial for ensuring a smooth, secure,
and efficient user experience for college students looking to buy, sell, and rent textbooks. This includes
communication protocols for transactions, inventory management, and user interaction, as well as
maintaining high standards of security and privacy.

E-mail & Notifications:​

Email will be used for order updates, account notifications, and promotional offers. Automated emails will
provide transaction details and reminders for payment or book return.

Web Browser & Protocols:

HTTPS: Secure browsing and transactions.

FTP: For transferring large inventory data.
WebSocket: Real-time messaging for user negotiations and deal confirmations.

Electronic Forms:

Forms will capture user details and book listings, with real-time validation to ensure secure and accurate
5

data entry.

Security & Encryption:

SSL/TLS Encryption: Secure transactions and data protection.

Multi-factor Authentication (MFA): Added security for user logins.
Data Privacy: Personal information will be encrypted and comply with data protection laws.

Synchronization Mechanisms:

Real-Time Inventory Sync: Keeps book availability accurate to prevent over/under-selling.

User-Seller Sync: Ensures smooth negotiations and deal confirmations.

Data Transfer Rates:

Optimized for fast, reliable data transfer, with load balancing during peak times for responsiveness.

Message Formatting & Standards:

Standardized message formats will ensure clear communication, with internationalization features for
region-specific users.

4.​ System Features

System Feature 1: Inventory Management and Real-Time Book Availability
This feature ensures that books are tracked in real-time, so the platform can accurately display their
availability to users. It directly impacts user satisfaction and trust by preventing over-selling or
under-selling of textbooks. High priority is given to this feature, as real-time inventory management is
crucial for a seamless buying/selling experience. Key functionality includes the system displaying real-time
availability when users search for books, updating the stock immediately after each transaction, and
sending notifications when out-of-stock books become available.

System Feature 2: User-Driven Listings

This feature allows students to list their own textbooks for sale or rent, creating a user-driven
marketplace. It enables users to create, edit, and delete listings while maintaining a high level of control
over their books. As a core feature of the platform, this is of High priority. The system must support book
details such as title, condition, price, and images, and notify users when their listings expire or sell/rent.
The inclusion of a review system helps ensure quality and trust in the marketplace.

System Feature 3: Dynamic Pricing

Dynamic pricing adjusts the price of textbooks based on supply, demand, and market conditions. This
feature helps ensure that textbooks are priced competitively, while also maximizing revenue for users. The
feature is of Medium priority as it enhances pricing flexibility. The system should allow users to set a base
price but automatically adjust it based on real-time market conditions. Users must also be notified when
prices change.
6

System Feature 4: Affordable and Flexible Payment Options

To ensure the platform is accessible to all users, this feature supports multiple payment methods (such as
credit/debit cards, UPI, and wallets) and offers flexible installment options for renting books. This
feature holds High priority as it addresses diverse user needs and payment preferences. It must support a
wide range of payment methods, process payments securely, and notify users upon successful
transactions.

System Feature 5: User Verification for Security

This feature ensures that all users are verified through email or phone before they can list items for sale or
rent, improving security and trust on the platform. High priority is assigned to this feature to protect both
buyers and sellers. The system should require email/phone verification during sign-up, and only verified
users should be able to list books. Notifications should be sent if verification is incomplete, and listings
should be blocked until the user is verified.

5.​ Other Nonfunctional Requirements

5.1​ Performance Requirements

Real-Time Updates: Inventory levels must update within 1 second of any transaction to prevent
over-selling or under-selling.
Rationale: To ensure accurate stock tracking and prevent customer dissatisfaction due to unavailable
items.

Search Speed: Search results for textbooks must appear within 2 seconds, even during high traffic.
Rationale: Provides users with a fast and seamless search experience, ensuring usability.

Concurrent User Support: The system should support up to 10,000 concurrent users without
performance issues.
Rationale: As the platform grows, it must handle heavy usage without slowing down.

Order Processing: The platform should process and confirm orders within 5 seconds, with real-time
updates on order status.
Rationale: Ensures a quick and responsive user experience, especially during checkout.

5.2​ Safety Requirements

The platform must comply with security and privacy regulations, including GDPR ,to ensure user data
protection.
Implement safeguards to prevent fraudulent transactions and unauthorized access.
Maintain backups to prevent data loss due to system failures or cyber threats.

5.3​ Security Requirements

Primary Authentication: Username/email & password.
Secondary Authentication: One-time password (OTP) via SMS/email or authentication app.

Authentication: Implement two-factor authentication (2FA) for logins and critical actions like changing
account info or making payments.
Rationale: Adds an extra layer of security to protect user accounts.
7

Role-Based Access Control: Enforce access restrictions so that only authorized users can access
sensitive data or manage listings.
Rationale: Prevents unauthorized access and ensures data integrity.

5.4​ Software Quality Attributes

Availability: The platform should be accessible almost all the time.
Scalability: The system should be able to handle more users and book listings as the platform grows.
Maintainability: The code should be well-organized and easy to update when needed.
Reliability: The platform should be stable and prevent errors from causing crashes or data loss.
Usability: The interface should be easy to use and work smoothly on all devices.
Testability: New features should be easy to test without affecting existing users.

5.5​ Business Rules

Only registered users can list, buy, or rent books.
Sellers must verify their identity before listing items.
Payment must be completed before book orders are processed.
Users must adhere to platform policies regarding acceptable listings and fair pricing.
Listings can be removed if they violate platform guidelines.

6.​ Other Requirements

Database Requirements:
Must store user data, book inventory, transactions, and order history securely.
Implement encryption for sensitive information.
Optimize queries for high-speed data retrieval.

Internationalization:
Support multiple languages for broader accessibility.
Currency conversion for international transactions.

Legal Compliance:
Adhere to e-commerce regulations and consumer protection laws.

Appendix A: Glossary
SRS: Software Requirements Specification. A document describing the functional and non-functional
requirements of the software.
E-commerce Platform: An online system enabling users to buy, sell, and rent textbooks and other
study materials.
User: A general term referring to anyone interacting with the platform, including buyers, sellers, and
renters.
Seller: A user who lists textbooks or study materials for sale or rent.
Buyer: A user who searches for, selects, and purchases or rents textbooks.
8

Admin: A user with administrative privileges to manage the platform, including inventory
management, user verification, and resolving issues.
PYQs: Previous Year Questions. Past exam papers available on the platform as study materials.
Dynamic Pricing: A system that adjusts the price of textbooks based on factors like demand,
condition, and competition.
Inventory Management: The process of tracking and updating the availability of textbooks and
materials in real time.
2FA: Two-Factor Authentication. An added security step requiring users to verify their identity through
a secondary method like OTP or email verification.
OTP: One-Time Password. A temporary password sent to users for authentication purposes.
UI/UX: User Interface/User Experience. Refers to the design and ease of use of the platform.
API: Application Programming Interface. A set of protocols for connecting the platform with external
systems like Google Books or payment gateways.
Google Books API: An external service used to fetch detailed book information, such as author, title,
and reviews.
Payment Gateway: A secure system used to process online payments, like Stripe or PayPal.
Cart: A virtual shopping cart where users add items they intend to buy or rent before checkout.
Wishlist: A feature allowing users to save items for future consideration without adding them to the
cart.
Order Summary: A detailed summary of an order, including item details, price, and delivery
information.
Chat Platform: A feature enabling direct communication between buyers and sellers for negotiations
or queries.
Verification Email: An email sent to validate a user’s email address during registration or 2FA.
Filters: Options provided to refine search results based on parameters like price, genre, or condition.
Sorting: Organizing search results based on preferences like price, popularity, or date added.
Second-Hand Textbooks: Used textbooks available for resale or rent on the platform.
Scalability: The ability of the platform to handle an increasing number of users or transactions.
Secure Payment Gateway: A trusted system for processing payments securely while ensuring
compliance with industry standards.
Real-Time Book Availability: An up-to-date reflection of the inventory showing which books are
currently in stock.
9

Appendix B: Analysis Models

1.​ Use Case Diagram :

Register User Login User

●​ Actor: User ●​ Actor: User
●​ Preconditions: User has access to the ●​ Preconditions: User must have an
registration page and email. account.
●​ Postconditions: User is registered after ●​ Postconditions: User is logged in.
email verification (or not, if email is ●​ Flow of Events:
optional). 1.​ User enters credentials.
●​ Flow of Events: 2.​ Server validates via authentication
1.​ User submits registration details. system.
2.​ Server validates and stores in 3.​ Server logs user in.
database. 4.​ (Optional) 2FA request if enabled.
3.​ Server sends verification email. ●​ Exceptions: Invalid credentials, server
4.​ User verifies email. errors.
5.​ Server confirms registration. ●​ Alternative Flow: Skip 2FA if not enabled.
●​ Exceptions: Invalid input, email already
exists, server errors.
●​ Alternative Flow: Skip email verification if
not required.
10

Search Books Place Order

●​ Actor: User ●​ Actor: User
●​ Preconditions: User is logged in or guest. ●​ Preconditions: User has selected items in
●​ Postconditions: Search results are the cart.
displayed. ●​ Postconditions: Order is placed and
●​ Flow of Events: stored.
1.​ User enters search query. ●​ Flow of Events:
2.​ Server fetches results from the 1.​ User reviews and confirms order.
database. 2.​ Server creates and stores the order.
3.​ Server filters and sorts results. 3.​ Server confirms the order to the
4.​ Display search results. user.
●​ Exceptions: No results found, server errors ●​ Exceptions: Out of stock, invalid payment
details.
11

Make Payment Negotiate via Chat

●​ Actor: User ●​ Actor: User
●​ Preconditions: User has a valid order. ●​ Preconditions: User has a listing or item
●​ Postconditions: Payment processed, to negotiate.
confirmation sent. ●​ Postconditions: Chat history saved, offer
●​ Flow of Events: sent.
1.​ User selects payment option. ●​ Flow of Events:
2.​ Server processes payment with 1.​ User initiates chat.
gateway. 2.​ User sends an offer.
3.​ Payment gateway confirms 3.​ Server stores chat.
payment. 4.​ Offer displayed to recipient.
4.​ Server stores transaction details. ●​ Exceptions: Server error, chat failure.
5.​ Payment confirmation sent.
●​ Exceptions: Payment failure, server
errors.
12

Update User Profile Submit Review

●​ Actor: User ●​ Actor: User
●​ Preconditions: User is logged in. ●​ Preconditions: User has purchased the
●​ Postconditions: Profile is updated. book.
●​ Flow of Events: ●​ Postconditions: Review is stored and
1.​ User modifies profile details. displayed.
2.​ Server updates database. ●​ Flow of Events:
3.​ Profile displayed with updates. 1.​ User writes review and rates.
●​ Exceptions: Invalid data, server error. 2.​ Server stores the review.
3.​ Updated reviews displayed.
●​ Exceptions: Invalid review, server error.
13

List Book for Sale Manage Inventory

●​ Actor: Seller ●​ Actor: Admin/Seller
●​ Preconditions: Seller is logged in. ●​ Preconditions: Admin or seller is logged in.
●​ Postconditions: Book listing is created. ●​ Postconditions: Inventory is updated.
●​ Flow of Events: ●​ Flow of Events:
1.​ Seller enters book details and price. 1.​ Admin/Seller updates stock.
2.​ Server stores listing in database. 2.​ Server updates database.
3.​ Confirmation sent to seller. 3.​ Inventory status displayed.
●​ Exceptions: Invalid details, listing already ●​ Exceptions: Stock update failure.
exists.
14

2.​ Sequence Diagram :

15
16
17
18
19

3.​ Class Diagram

20

Appendix C: To Be Determined List

The following items remain undecided and need to be finalized for the system to be fully defined:

Refund Policy Terms and Conditions

Define the exact rules for refunds, including eligibility criteria and processing time
.
Cloud Service Provider
Decide whether to use AWS, Google Cloud, or another provider for hosting and storage.

Payment Gateway Integration

Choose between Stripe, Razorpay, PayPal, or another secure payment processor.

AI-Based Recommendation Model

Determine the final approach for AI-powered book recommendations.
Choose between collaborative filtering, content-based filtering, or hybrid models.

Multi-Language Support
Finalize the list of languages to be supported for international users.

Return and Dispute Resolution Policies

Establish guidelines for handling product returns, refunds, and customer disputes.

Data Retention Policy

Define how long user data, order history, and transaction records will be stored