ONLINE BOOK STORE

A WEB-BASED BOOK SELLING APPLICATION

A Project Report Submitted

in Partial Fulfillment of the Requirements
for the Degree of

BACHELOR OF TECHNOLOGY
in
Information Technology
By
Sachchidanand Kumar
(2206480130008)
Shashwat
(2206480130010)
Satyam Singh
(2206480130009)
Ashish Singh
(2206480130009)

Under the Supervision of

Er. Hira Singh Yadav

BABU SUNDER SINGH INSTITUTE OF TECHNOLOGY AND

MANAGEMENT LUCKNOW

DR. APJ ABDUL KALAM TECHNICAL UNIVERSITY

(Formerly Uttar Pradesh Technical University Lucknow)
May, 2026
 DECLARATION

I hereby declare that the work presented in this report entitled "ONLINE BOOK STORE:
A WEB-BASED BOOK SELLING APPLICATION", was carried out by me. I have not
submitted the matter embodied in this report for the award of any other degree of any
other University or Institute. I have given due credit to the original authors/sources for all
the words, ideas, diagrams, graphics, computer programs, experiments, results, that are
not my original contribution. I have used quotation marks to identify verbatim sentences
and given credit to the original authors/sources. I affirm that no portion of my work is
plagiarized, and the experiments and results reported in the report are not manipulated. In
the event of a complaint of plagiarism and the manipulation of the experiments and
results, I shall be fully responsible and answerable.

Sachchidanand Kumar Satyam Singh

2206480130008 2206480130009
Shashwat Ashish Singh
2206480130010 2206480130006
 CERTIFICATE

Certified that Sachchidanand Kumar(2206480130008), Shashwat(2206480130010),

Satyam Singh(2206480130009), Ashish Singh(2206480130006) has carried out the
project work presented in this report entitled "ONLINE BOOK STORE: A WEB-BASED
BOOK SELLING APPLICATION" for the award of Bachelor of Technology from Dr.
APJ Abdul Kalam Technical University, Lucknow under the Guidance of Er. Hira Singh
Yadav. The project report embodies results of original work, and studies are carried out
by the student and the contents of the report do not form the basis for the award of any
other degree to the candidate or to anybody else from this or any other
University/Institution.

Guided by Dr. Suyogita Singh

Er. Hira Singh Yadav HOD(IT)
HOD (CSE)

Place: Lucknow
Date: _______________
 ABSTRACT

The rapid growth of e-commerce and internet adoption has fundamentally transformed
the retail industry, including the way people discover, purchase, and access books. This
project, "Online Book Store: A Web-Based Book Selling Application," presents a
comprehensive digital platform that streamlines the process of browsing, selecting, and
ordering books online, bringing the traditional bookstore experience into the digital age.
The application is built on the Django web framework using Python as the primary
programming language, following the Model-View-Template (MVT) architectural
pattern. The front end is developed using HTML5, CSS3, Bootstrap 5, and JavaScript,
ensuring a responsive and visually appealing user interface across all device sizes. The
back end leverages Django's built-in ORM for seamless database interactions with
SQLite, providing a reliable and efficient data persistence layer. The Online Book Store
offers a rich set of functionalities including user registration and authentication, book
catalogue browsing by category, advanced search and filtering capabilities, a shopping
cart system, order placement and management, and a comprehensive administrative
dashboard. The admin panel enables authorised administrators to manage book listings,
categories, user accounts, orders, and enquiries through an intuitive interface. Security is
ensured through Django's built-in session management, CSRF protection, and password
hashing mechanisms. The primary objective of this project is to demonstrate the practical
application of full-stack web development skills in solving a real-world problem while
delivering a user-friendly, scalable, and maintainable platform. The system reflects the
effective use of the Django ecosystem to build feature-rich web applications with clean
code organisation and separation of concerns.

Future enhancements may include integration of a payment gateway for live transactions,
AI-based book recommendation systems, review and rating modules, mobile application
development, and third-party API integrations for real-time inventory and shipping
tracking. Overall, the Online Book Store provides a strong foundation for a production-
ready e-commerce application in the book retail domain.
 ACKNOWLEDGEMENTS

It is a matter of great pleasure to acknowledge the support, guidance, and encouragement

received from various individuals during the completion of this project. First and
foremost, I express my sincere gratitude to my project guide, Er. Hira Singh Yadav,
Department of Information Technology, Babu Sunder Singh Institute of Technology and
Management, Lucknow, for invaluable guidance, continuous support, and insightful
suggestions throughout the development of this project. expertise and motivation played
a crucial role in shaping the quality and direction of this work. I am deeply thankful to
the Head of Department, Dr. Suyogita Singh, for providing the necessary facilities and
a conducive academic environment that enabled the successful completion of this project.
I also extend my gratitude to all the faculty members of the Department of Information
Technology for their constant support and encouragement during my undergraduate
studies. I would like to express my heartfelt thanks to the Department of Information
Technology and the management of Babu Sunder Singh Institute of Technology and
Management, Lucknow, for their continuous support and for maintaining a high standard
of technical education. I am also grateful to my classmates and friends for their
cooperation, valuable suggestions, and moral support. Their assistance in testing and
providing feedback significantly contributed to improving the Online Book Store
application.

Finally, I express my deepest gratitude to my family for their unwavering support,

patience, and encouragement throughout my academic journey. Their belief in me has
always been my greatest strength and motivation.

Sachchidanand Kumar Satyam Singh

2206480130008 2206480130009
Shashvat Ashish Singh
2206480130010 2206480130006
 TABLE OF CONTENTS

Section Page No.

Declaration ii

Certificate iii

Abstract iv

Acknowledgements v

List of Tables vi

List of Figures vii

List of Symbols and Abbreviations viii

CHAPTER 1: INTRODUCTION 1

1.1 Overview 1

1.2 Problem Statement 3

1.3 Objectives 4

1.4 Scope of the Project 5

1.5 Organisation of the Report 6

CHAPTER 2: LITERATURE REVIEW 8

2.1 Introduction 8

2.2 Existing Systems 9

2.3 Related Technologies 12

2.4 Research Gap 16

CHAPTER 3: SYSTEM ANALYSIS AND DESIGN 18

3.1 System Requirements 18

3.2 Feasibility Study 21

3.3 System Architecture 23

3.4 Use Case Diagrams 26

 3.5 Data Flow Diagrams 29

3.6 Entity-Relationship Diagram 32

CHAPTER 4: IMPLEMENTATION 35

4.1 Technology Stack 35

4.2 Front-End Implementation 39

4.3 Back-End Implementation 45

4.4 Database Design 51

4.5 API Design 54

CHAPTER 5: TESTING 58

5.1 Testing Strategy 58

5.2 Unit Testing 60

5.3 Integration Testing 63

5.4 System Testing 65

5.5 User Acceptance Testing 67

CHAPTER 6: RESULTS AND DISCUSSION 70

6.1 System Output 70

6.2 Performance Analysis 73

6.3 Comparison with Existing Systems 75

CHAPTER 7: CONCLUSION AND FUTURE WORK 78

7.1 Conclusion 78

7.2 Limitations 80

7.3 Future Enhancements 81

References 84

Appendix I: Source Code Snippets 88

Appendix II: Screenshots 92

List of Publications 95

Curriculum Vitae 96
 LIST OF TABLES

Table No. Title Page

Table 3.1 Functional Requirements 19

Table 3.2 Non-Functional Requirements 20

Table 3.3 Hardware Requirements 21

Table 3.4 Software Requirements 22

Table 3.5 Actor Descriptions 26

Table 4.1 Technology Stack Summary 36

Table 4.2 Python/Django Packages Used 38

Table 4.3 CSS Classes and Their Functions 41

Table 4.4 JavaScript Functions – Front End 44

Table 4.5 Django URL Patterns 47

Table 4.6 Middleware Used in Application 49

Table 4.7 Book Model Schema 52

Table 4.8 Order Model Schema 53

Table 4.9 API/View Endpoints Summary 55

Table 5.1 Unit Test Cases – User Module 61

Table 5.2 Unit Test Cases – Booking Module 62

Table 5.3 Integration Test Results 64

Table 5.4 System Test Scenarios 66

Table 5.5 UAT Feedback Summary 68

Table 6.1 Performance Metrics 74

Table 6.2 Comparison with Existing Systems 76

 LIST OF FIGURES

Figure No. Title Page

Fig. 3.1 System Architecture Diagram 24

Fig. 3.2 MVT Architecture of Online Book Store 25

Fig. 3.3 Use Case Diagram – User Module 27

Fig. 3.4 Use Case Diagram – Admin Module 28

Fig. 3.5 Level 0 DFD (Context Diagram) 30

Fig. 3.6 Level 1 DFD – Order Process 31

Fig. 3.7 Entity-Relationship Diagram 33

Fig. 4.1 Front-End Folder Structure 40

Fig. 4.2 Homepage Wireframe 41

Fig. 4.3 Book Catalogue Page Layout 43

Fig. 4.4 Order Form Design 44

Fig. 4.5 Django Application Structure 46

Fig. 4.6 Middleware Stack Diagram 50

Fig. 4.7 Database Schema Diagram 52

Fig. 4.8 URL Routing Flow 56

Fig. 5.1 Testing Levels Applied 59

Fig. 6.1 Homepage Screenshot 71

Fig. 6.2 Book Search Results 72

Fig. 6.3 Order Confirmation Page 73

Fig. 6.4 Admin Dashboard 74

Fig. 6.5 Response Time Graph 75

LIST OF SYMBOLS, ABBREVIATIONS AND NOMENCLATURE

Abbreviation Full Form

API Application Programming Interface

BS Bootstrap (Front-End CSS Framework)

CDN Content Delivery Network

CSS Cascading Style Sheets

CRUD Create, Read, Update, Delete

DFD Data Flow Diagram

DOM Document Object Model

ER Entity-Relationship

HTML HyperText Markup Language

HTTP HyperText Transfer Protocol

HTTPS HyperText Transfer Protocol Secure

IT Information Technology

JS JavaScript

MVC Model-View-Controller

MVT Model-View-Template

ORM Object-Relational Mapper

OBS Online Book Store

pip Package Installer for Python

REST Representational State Transfer

SQL Structured Query Language

SQLite Structured Query Language (Embedded Database)

UI User Interface

URL Uniform Resource Locator

 CHAPTER 1

INTRODUCTION
1.1 OVERVIEW
The digital revolution has transformed virtually every sector of the global economy, and
the retail industry is no exception. The proliferation of smartphones, high-speed internet
connectivity, and the growing comfort of consumers with online transactions have
collectively given rise to a thriving e-commerce ecosystem. Within this ecosystem, the
online book retail segment occupies a significant and growing position, driven by the
enduring demand for knowledge, education, and leisure reading among people of all ages.
The Online Book Store is a full-stack web application developed to provide a seamless,
end-to-end digital platform for book discovery, browsing, and purchasing. The platform
integrates book catalogue management, category-based filtering, a shopping cart, order
processing, and administrative management into a single, cohesive digital environment.
Unlike traditional bookshops that are constrained by physical space and operating hours,
the Online Book Store is accessible around the clock, offering an extensive catalogue of
books across multiple genres and categories to users regardless of their geographic
location. From a technical perspective, the Online Book Store is developed using Django,
one of the most widely adopted and production-proven web frameworks in the Python
ecosystem. Django follows the Model-View-Template (MVT) architectural pattern,
which promotes clean separation of concerns between data management, business logic,
and presentation. This architecture facilitates maintainability, testability, and
collaborative development. The front end is built using HTML5, CSS3, Bootstrap 5, and
JavaScript (ES6+), ensuring a modern, responsive, and accessible user interface across a
wide range of devices and screen resolutions. The administrative functionality of the
system is provided through a dedicated admin application within the Django project. The
admin panel enables authorised users to manage the complete book inventory, including
adding, editing, and removing book listings, managing book categories, handling user
accounts, processing orders, and responding to customer enquiries. This dual-facing
architecture — a customer-facing storefront and an operator-facing administrative panel
— mirrors the design of real-world e-commerce platforms.
1.2 PROBLEM STATEMENT
Despite the abundance of physical bookstores and a few large online book retailers, many
readers in smaller towns and cities continue to face significant challenges in accessing a
wide variety of books. The existing landscape is characterised by several persistent pain
points:

• Limited Physical Availability: Traditional bookstores in smaller cities often

carry a restricted range of titles, making it difficult for readers to find books on
niche topics or by lesser-known authors.
• Lack of a Unified Platform: No single, locally relevant platform consolidates
book browsing, filtering, and purchasing, forcing buyers to navigate multiple
websites or travel to different stores.
• Poor Search and Discovery: Existing small-scale book retail platforms often lack
robust search and filtering capabilities, making it difficult for users to discover
books by category, author, price range, or language.
• Inefficient Order Management: Many small book retailers manage orders
manually, leading to errors, delays, and a poor customer experience.
• Limited Administrative Control: Shop owners lack centralised, digital tools for
managing their inventory, tracking orders, and analysing sales in real time.

The Online Book Store addresses these challenges by providing a unified, well-designed
web platform that brings together book discovery, catalogue management, order
placement, and administrative oversight in a single, easy-to-use application.

1.3 OBJECTIVES
The primary objectives of the Online Book Store project are as follows:

1. To design and develop a fully functional, full-stack web application for online
book selling using Python, Django, HTML5, CSS3, Bootstrap 5, and JavaScript.
2. To implement a responsive, mobile-first user interface that delivers a consistent
and visually appealing experience across all device types and screen sizes.
3. To develop a secure user authentication and authorisation system that protects
user data and enforces role-based access control.
4. To create a comprehensive book catalogue with category management, search,
filter, and sort functionalities to facilitate efficient book discovery.
5. To implement a shopping cart and order management system enabling users to
add books, review their cart, place orders, and track order history.
6. To develop a full-featured administrative dashboard for managing books,
categories, users, orders, and enquiries.
7. To ensure application security through Django's built-in CSRF protection,
password hashing, session management, and input validation.
1.4 SCOPE OF THE PROJECT
1.4.1 In-Scope Features
• User registration, login, and profile management
• Book catalogue browsing by category with search and filter capabilities
• Detailed book information pages with descriptions, pricing, and cover images
• Shopping cart management and order placement
• Order confirmation and booking history
• Admin panel for managing books, categories, users, orders, and enquiries
• Password change functionality for admin users
• Responsive design for desktop and mobile browsers
1.4.2 Out-of-Scope Features
• Real-time payment gateway integration (payments are simulated)
• Native mobile application development
• AI-powered book recommendation systems
• Multi-language and internationalisation support
• Real-time chat or customer support integration
• Book review and rating system
1.5 ORGANISATION OF THE REPORT
The remainder of this report is organised as follows:

Chapter 2 (Literature Review) reviews existing online book retail platforms, related
academic works, and the technologies used in similar systems. It identifies the research
gap that the Online Book Store aims to address.

Chapter 3 (System Analysis and Design) presents the functional and non-functional
requirements of the system, feasibility analysis, system architecture, use case diagrams,
data flow diagrams, and entity-relationship diagrams.

Chapter 4 (Implementation) describes the technology stack in detail and explains the
implementation of the front-end, back-end, database, and URL routing components of the
application.

Chapter 5 (Testing) outlines the testing strategy and presents the results of unit testing,
integration testing, system testing, and user acceptance testing.

Chapter 6 (Results and Discussion) presents screenshots of the working application,

performance metrics, and a comparative analysis with existing systems.
Chapter 7 (Conclusion and Future Work) summarises the project outcomes,
acknowledges limitations, and proposes directions for future enhancement of the Online
Book Store platform.

The report concludes with the list of References followed by Appendices containing
source code samples, screenshots, list of publications, and the candidate's curriculum
vitae.
 CHAPTER 2

LITERATURE REVIEW
2.1 INTRODUCTION
The literature review is an essential component of any research or development project
as it situates the work within the broader context of existing knowledge. For the Online
Book Store project, the literature review serves to examine the evolution of online book
retail platforms, analyse the current state of web technologies used in e-commerce
applications, and identify gaps in existing systems that this project aims to address. This
chapter reviews seminal and contemporary works related to online book retail
applications, the technologies employed, and user experience considerations in the e-
commerce domain. The online book retail industry has undergone dramatic
transformation since the launch of Amazon in 1994, which pioneered the concept of
selling books via the internet. The first generation of online book platforms primarily
offered simple catalogue browsing and basic checkout functionality. Subsequent
generations introduced personalised recommendations, user reviews, ratings, digital
content delivery, and mobile applications. Contemporary platforms leverage machine
learning, big data analytics, and cloud infrastructure to deliver highly personalised,
scalable, and reliable shopping experiences.

2.2 EXISTING SYSTEMS

2.2.1 Amazon
Amazon is the world's largest online retailer, with books representing its original and still
highly prominent product category. The platform offers an extraordinarily vast catalogue
encompassing both physical and digital (Kindle) books. Amazon's recommendation
engine, powered by collaborative filtering and deep learning algorithms, provides highly
personalised book suggestions. The platform features customer reviews, ratings, author
pages, 'Look Inside' previews, and one-click purchasing. While Amazon represents the
gold standard for scale and personalisation, its complexity and advertising-driven
interface can overwhelm users with focused book discovery needs.

2.2.2 Flipkart
Flipkart, India's leading e-commerce marketplace, offers a substantial books category
with competitive pricing, frequent discount campaigns, and convenient delivery options
including cash-on-delivery. The platform's strength lies in its deep penetration into tier-2
and tier-3 cities of India, supported by a robust logistics network. Flipkart's interface is
optimised for mobile-first usage, reflecting the predominantly smartphone-based internet
access patterns of Indian consumers. Its limitation is the generalised e-commerce focus,
which does not provide a book-specific browsing and discovery experience.

2.2.3 Goodreads
Goodreads, owned by Amazon, is primarily a social cataloguing platform that allows
users to track their reading, discover new books through community recommendations,
and participate in reading groups. While Goodreads does not directly facilitate e-
commerce transactions, it plays a pivotal role in the book discovery process and
influences purchasing decisions. Its strength lies in the rich, community-driven content
around books — reviews, lists, author interviews, and reading challenges. The limitation
of Goodreads is the absence of a direct purchasing mechanism, requiring users to navigate
to a third-party retailer.

2.2.4 Crossword Bookstores

Crossword is one of India's leading physical book retail chains that also operates an online
store. The platform offers a curated catalogue of books, stationery, and gifts with a focus
on providing a premium book shopping experience. Its online platform features category
browsing, bestseller lists, and staff picks. However, its digital platform is comparatively
less feature-rich than global counterparts and offers limited search and filter capabilities.

2.3 RELATED TECHNOLOGIES

2.3.1 Django Web Framework
Django is a high-level Python web framework that promotes rapid development and
clean, pragmatic design. Originally developed by the Lawrence Journal-World newspaper
in 2003 and released publicly in 2005, Django has grown into one of the most widely
adopted web frameworks globally, powering platforms such as Instagram, Pinterest, and
Disqus. Django adheres to the principle of 'Don't Repeat Yourself' (DRY), encouraging
code reuse and reducing redundancy. Its built-in components — including the ORM,
authentication system, admin interface, URL dispatcher, and template engine — provide
a comprehensive toolkit for building web applications without relying on extensive third-
party libraries.

2.3.2 SQLite Database

SQLite is a serverless, self-contained, transactional SQL database engine that is the
default database backend for Django applications. It stores the entire database in a single
cross-platform file, making it ideal for development and testing environments. For
demonstration-scale applications, SQLite provides sufficient performance and data
integrity. Django's ORM abstracts the underlying database, enabling seamless migration
to production-grade databases such as PostgreSQL or MySQL when scaling.

2.3.3 Bootstrap 5
Bootstrap 5 is a powerful, feature-packed front-end toolkit that enables developers to
build responsive and mobile-first websites rapidly. Released in 2021, Bootstrap 5
removed the jQuery dependency, transitioning to pure vanilla JavaScript for its interactive
components. It provides a comprehensive library of pre-styled components including
navbars, cards, modals, carousels, alerts, badges, and form controls, along with a 12-
column responsive grid system based on CSS Flexbox. Bootstrap 5's utility class system
allows for rapid UI construction without writing custom CSS for most common styling
requirements.

2.3.4 Django ORM

The Django Object-Relational Mapper (ORM) is a built-in component of Django that
allows developers to interact with the database using Python objects rather than raw SQL
queries. Models defined as Python classes are automatically mapped to database tables
by the ORM, which handles schema creation through Django's migration system. The
ORM supports complex query construction, relationship management (ForeignKey,
ManyToMany, OneToOne), and query optimisation through lazy evaluation and query
set chaining.

2.3.5 MVT Architecture

The Model-View-Template (MVT) pattern is Django's implementation of the broader
MVC (Model-View-Controller) architectural paradigm. In Django's MVT, the Model
encapsulates the data layer and business logic (via the ORM), the View contains the
request-handling logic and data processing, and the Template is responsible for rendering
the HTML output. Django's URL dispatcher serves as the controller, mapping incoming
HTTP requests to the appropriate view function or class-based view. This separation of
concerns promotes code maintainability, testability, and collaborative development.
2.4 RESEARCH GAP AND MOTIVATION
The review of existing literature and systems reveals several gaps and opportunities
relevant to the Online Book Store project:

• Academic literature on full-stack book e-commerce applications built on the

Django/Python stack for the Indian educational context is limited, particularly
for IT branch final-year projects.
• Most commercial platforms are feature-rich but highly complex and proprietary,
making them unsuitable as reference implementations for academic study or
skill demonstration.
• There is a lack of open, well-documented implementations demonstrating the
integration of Django's MVT pattern with Bootstrap 5 for e-commerce
applications in the book retail domain.
• Existing academic e-commerce projects often focus on a single aspect such as
UI design or database modelling without addressing the complete full-stack
implementation including admin functionality.

The Online Book Store addresses these gaps by providing a comprehensive, academically
rigorous implementation of a full-stack book e-commerce application using the Django
framework, with complete documentation of the design, implementation, testing, and
deployment processes.
 CHAPTER 3

SYSTEM ANALYSIS AND DESIGN

3.1 SYSTEM REQUIREMENTS
3.1.1 Functional Requirements
The functional requirements define the specific behaviours, functions, and capabilities
that the Online Book Store system must provide. These have been identified through an
analysis of the problem domain, review of similar systems, and consideration of typical
user scenarios.

FR No. Module Requirement Description

FR01 User Auth The system shall allow new users to register with a unique email
and password.
FR02 User Auth The system shall authenticate registered users via username and
password.
FR03 User Auth The system shall allow users to reset their password.
FR04 Books The system shall display a catalogue of available books organised
by category.
FR05 Books The system shall allow users to search books by title, author, or
category.
FR06 Books The system shall display detailed information for each book
including price, language, and description.
FR07 Cart The system shall allow authenticated users to add books to a
shopping cart.
FR08 Orders The system shall allow users to place orders for books in their cart.
FR09 Orders The system shall generate a unique order ID for each placed order.
FR10 Orders The system shall allow users to view their order history.
FR11 Admin The system shall provide administrators with a dashboard for
managing content.
FR12 Admin Administrators shall be able to add, edit, and delete book listings.
FR13 Admin Administrators shall be able to manage book categories.
FR14 Admin Administrators shall be able to view and manage user accounts and
enquiries.
Table 3.1: Functional Requirements
3.1.2 Non-Functional Requirements
• Performance: The application shall load within 3 seconds on a standard
broadband connection. Django view responses shall be returned within 500
milliseconds under normal load conditions.
 • Scalability: The system architecture shall support migration to a production-
grade database (PostgreSQL) and cloud hosting to accommodate increased
traffic.
• Security: All user passwords shall be stored in hashed form using Django's built-
in PBKDF2 hashing. The application shall implement CSRF protection on all
forms and sanitise all user inputs.
• Usability: The user interface shall be intuitive, requiring no more than 3 clicks to
reach any primary functionality. All forms shall provide clear error messages
and validation feedback.
• Reliability: The system shall handle invalid inputs gracefully without crashing,
maintaining system stability under normal operating conditions.
• Maintainability: The codebase shall follow Django conventions and PEP 8
Python style guidelines, with comprehensive in line documentation.
• Compatibility: The application shall be compatible with modern versions of
Google Chrome, Mozilla Firefox, Safari, and Microsoft Edge.
• Responsiveness: The UI shall render correctly on screen widths ranging from
320px (mobile) to 2560px (large desktop).
3.2 FEASIBILITY STUDY
3.2.1 Technical Feasibility
The technical feasibility of the Online Book Store project is high. All technologies
employed — Python, Django, HTML5, Bootstrap 5, JavaScript, and SQLite — are open-
source, freely available, and extensively documented. The development environment
consists of a standard computer running any modern operating system, with Python 3.x,
Django, and a text editor or IDE such as Visual Studio Code. No specialised hardware or
paid software licences are required, making the project technically feasible without
significant resource constraints. The development team possesses the necessary skills in
Python and Django as evidenced by coursework and laboratory exercises in web
technologies.

3.2.2 Operational Feasibility

From an operational standpoint, the Online Book Store is designed to be intuitive and
accessible to users with basic internet literacy. The customer interface employs familiar
e-commerce conventions, minimising the learning curve for new users. The
administrative interface is similarly straightforward, enabling non-technical content
managers to manage the book catalogue and process orders without developer assistance.

3.2.3 Economic Feasibility

The economic feasibility of the project is excellent, given that all development tools and
technologies are open-source and available free of charge. Server-side hosting can be
accomplished using free-tier or affordable cloud services such as PythonAnywhere,
Render, or Railway for Django applications. The total development cost is limited to the
time invested by the development team, with no significant monetary outlay required.

3.3 SYSTEM ARCHITECTURE

The Online Book Store follows Django's Model-View-Template (MVT) three-tier
architecture, comprising the Presentation Tier (templates and static files), the Application
Tier (Django views and business logic), and the Data Tier (SQLite database via Django
ORM).

3.3.1 Presentation Tier

The Presentation Tier encompasses all client-side components, including HTML
templates rendered by Django's template engine, Bootstrap 5 stylesheets and JavaScript
components, and custom CSS and JavaScript files. This tier is responsible for rendering
the user interface in the browser and handling direct user interactions. It communicates
with the Application Tier by sending HTTP requests (form submissions, AJAX calls) and
receiving rendered HTML responses or JSON data.

3.3.2 Application Tier

The Application Tier is implemented using Python and the Django framework. It contains
the business logic of the application, implemented as Django view functions and class-
based views. The URL dispatcher maps incoming HTTP requests to the appropriate view,
which processes the request, interacts with the Data Tier via the ORM, and returns an
appropriate HTTP response. The application is organised into two Django apps:
adminapp (administrative functionality) and a user-facing storefront app.

3.3.3 Data Tier

The Data Tier manages the persistent storage of application data using SQLite as the
database backend. Data models defined in Django's [Link] files are mapped to
database tables by the ORM. The Data Tier is accessed exclusively through the
Application Tier via the Django ORM, ensuring data integrity, security, and clean
separation of concerns.

3.4 USE CASE ANALYSIS

Use case analysis identifies the actors and their interactions with the Online Book Store
system. The primary actors are Guest Users (unauthenticated visitors), Registered Users
(authenticated customers), and Administrators.
3.4.1 Guest User Use Cases
• Browse the book catalogue and view book details
• Search for books using keywords, category filters, and price range
• View available book categories
• Register for a new customer account
• Log in to an existing account
3.4.2 Registered User Use Cases
• All Guest User use cases
• Add books to the shopping cart and manage cart contents
• Place orders for books
• View order history and order details
• Submit product enquiries
• Update profile and account password
3.4.3 Administrator Use Cases
• Log in to the administrative dashboard
• Add, edit, and delete book listings with cover image upload
• Manage book category listings
• View and manage registered user accounts
• View and manage all customer orders
• View and respond to customer enquiries
• Change administrative password
3.5 DATA FLOW ANALYSIS
Data Flow Diagrams (DFDs) are used to graphically represent the flow of data through
the Online Book Store system. DFDs provide a structured view of how data enters the
system, how it is processed, and where it is stored or output.

3.5.1 Level 0 DFD (Context Diagram)

The context diagram represents the system at the highest level of abstraction. The Online
Book Store appears as a single process that interacts with three external entities: Customer
(registered and guest users), Administrator, and Email Service (for notification purposes).
Data flows include user credentials, search queries, book orders, administrative
commands, and system responses.

3.5.2 Level 1 DFD

The Level 1 DFD decomposes the system into its major sub-processes: User
Authentication, Book Catalogue Management, Shopping Cart Management, Order
Management, and Administration. Data stores include the User Data Store, Book Data
Store, Category Data Store, and Order Data Store. Each sub-process receives and
produces data flows as appropriate to its function.

3.6 ENTITY-RELATIONSHIP DESIGN

The Entity-Relationship (ER) design identifies the key data entities in the Online Book
Store system and the relationships between them. The primary entities are:

• User: Represents an individual registered with the platform. Attributes include

UserID (primary key), Username, Email, Password (hashed), First Name, Last
Name, and Date Joined.
• Category: Represents a book category or genre. Attributes include CategoryID
(primary key), Name (unique), and Description.
• Book: Represents a book listed on the platform. Attributes include BookID
(primary key), Title, Author, CategoryID (foreign key), Description,
OriginalPrice, Price, PublishedDate, Language, CoverImage, Stock, CreatedAt,
and UpdatedAt.
• Order: Represents a purchase order placed by a user. Attributes include OrderID
(primary key), UserID (foreign key), OrderDate, TotalAmount, Status, and
DeliveryAddress.
• OrderItem: Represents an individual book within an order. Attributes include
ItemID (primary key), OrderID (foreign key), BookID (foreign key), Quantity,
and UnitPrice.
• Enquiry: Represents a customer enquiry or contact form submission. Attributes
include EnquiryID (primary key), UserID (optional foreign key), Name, Email,
Message, and SubmittedAt.
 CHAPTER 4

IMPLEMENTATION
4.1 TECHNOLOGY STACK
The technology stack for the Online Book Store has been carefully selected to achieve
the dual objectives of functional completeness and academic demonstration value. The
chosen technologies represent current industry-standard tools for full-stack Python web
development, providing both practical relevance and educational applicability.

Category Technology Purpose

Back-End Framework Django 5.x MVT web framework, URL routing, ORM,
authentication
Programming Python 3.x Server-side scripting and business logic
Language
Front-End Structure HTML5 Structure and semantic content of web pages
Front-End Styling Bootstrap 5 Responsive UI components, grid system, and
styling
Front-End Scripting JavaScript (ES6+) Client-side interactivity and DOM
manipulation
Database SQLite Persistent data storage via Django ORM
Templating Django Templates Server-side HTML template rendering
(DTL)
Image Handling Pillow Python library for processing book cover
images
Dev Tools pip Package management and dependency
resolution
Dev Tools VS Code Integrated Development Environment
Dev Tools Django Admin Built-in administrative interface for data
management
Table 4.1: Technology Stack Summary
4.2 FRONT-END IMPLEMENTATION
4.2.1 HTML Structure
The HTML structure of the Online Book Store is designed to be semantic, accessible, and
well-organised. Semantic HTML5 elements such as <header>, <nav>, <main>,
<section>, <article>, and <footer> are used throughout the application to provide
meaningful structure to the document. This approach improves accessibility for screen
readers, aids search engine optimisation, and provides clear structural cues during
development. Django's template inheritance system, using {% extends %} and {% block
%} tags, ensures a consistent layout across all pages while minimising code duplication.
A base template containing the navigation header and footer is extended by all page-
specific templates.

4.2.2 CSS Styling and Layout

The visual design of the Online Book Store employs a clean, modern aesthetic appropriate
for a book retail platform. Bootstrap 5 is used as the primary CSS framework, providing
a comprehensive library of pre-styled components including navigation bars, cards,
carousels, modals, buttons, badges, and form controls. Custom CSS overrides are applied
on top of Bootstrap's base stylesheet to achieve the unique brand identity of the Online
Book Store. Bootstrap 5's powerful 12-column responsive grid system based on CSS
Flexbox is employed extensively for page layout. Bootstrap utility classes accelerate
development while ensuring consistent spacing and visual rhythm across the application.

4.2.3 Responsive Design Implementation

Responsive design is a core requirement of the Online Book Store, and Bootstrap 5's built-
in breakpoint system is leveraged fully. The application follows a mobile-first design
philosophy — Bootstrap's default approach — where base layouts are optimised for small
screens and progressively enhanced for larger viewports. Key Bootstrap 5 components
utilised in the Online Book Store include: Navbar (with responsive hamburger toggler for
mobile), Card (for book listings), Carousel (for homepage featured books and
promotional banners), Modal (for login/register overlays and confirmation dialogs),
Badge (for category tags, discount indicators, and stock status), Toast (for success/error
notifications), Spinner (for loading states), and the full suite of Form components with
built-in validation styling.

4.2.4 JavaScript Functionality

Client-side JavaScript in the Online Book Store is responsible for enhancing the user
experience without requiring full page reloads. Key JavaScript functionalities include
dynamic search filtering of book listings, real-time cart quantity updates, form validation
before submission, price range slider for filtering books by budget, and image preview
for book cover uploads in the admin panel.
4.3 BACK-END IMPLEMENTATION
4.3.1 Django Application Setup
The Django project is organised following Django's recommended project structure. The
main project directory contains the [Link] configuration file, the root URL
configuration ([Link]), and the WSGI entry point. The project is divided into Django
apps, each encapsulating a specific functional domain. The adminapp houses all
administrative views, models, URL configurations, and templates. Static files (CSS,
JavaScript, images) are organised within the respective app's static directory, following
Django's static files convention.

4.3.2 URL Routing

Django's URL dispatcher maps incoming HTTP requests to view functions. URL patterns
are defined in [Link] files within each app and included in the root URL configuration.
The adminapp defines the following primary URL patterns:

URL Pattern View Function Description

admindash/ admindash Administrator dashboard with platform metrics
adminlogout/ adminlogout Destroy admin session and log out
addcat/ addcat Form to add a new book category
viewcat/ viewcat List all categories with edit/delete options
viewbook/ viewbook List all books in the admin catalogue
addbook/ addbook Form to add a new book with image upload
viewenqs/ viewenqs View all customer enquiries
adminpassword/ adminpassword Change admin account password
delbook/<id> delbook Delete a specific book by ID
viewinfo/ userinfo View registered user information
vieworders/ vieworders View and manage all customer orders
Table 4.5: Django URL Patterns
4.3.3 Model Implementation
The data models for the Online Book Store are defined in the [Link] file of the
adminapp. The Category model stores book categories with a unique name and
description. The Book model stores comprehensive book information including title,
author, category (ForeignKey to Category), description, original price, selling price,
published date, language, cover image (stored in book_covers/ directory via ImageField),
stock quantity, and timestamps. Django's ORM automatically creates the corresponding
database tables through the migration system.

4.3.4 Authentication Implementation

User authentication in the Online Book Store is implemented using Django's built-in
authentication framework. Upon successful login, Django creates a server-side session
and sets a session cookie. Password handling follows Django's secure approach —
passwords are never stored in plain text but are hashed using the PBKDF2 algorithm with
a SHA256 hash. The adminpassword view allows administrators to change their password
securely. All administrative routes are protected by authentication checks that redirect
unauthenticated requests to the login page.

4.4 DATABASE DESIGN

The Online Book Store uses SQLite as its database backend, managed through Django's
ORM and migration system. The database schema is derived from the Django model
definitions and is automatically created and updated through Django migrations.

4.4.1 Book Table Schema

Field Type Constraints Description
id BigAutoField Primary Key, Unique book identifier
Auto
title CharField(255) NOT NULL Book title
author CharField(255) NOT NULL Author name(s)
category ForeignKey NOT NULL, FK Book genre/category
→ Category
description TextField Blank allowed Book synopsis/description
original_price IntegerField NOT NULL MRP of the book
price IntegerField NOT NULL Selling price
published_date DateField NOT NULL Date of publication
language CharField(50) NOT NULL Language of publication
cover_image ImageField Optional Book cover image
stock PositiveIntegerField Default: 0 Available stock quantity
created_at DateTimeField Auto, NOT Record creation timestamp
NULL
updated_at DateTimeField Auto, NOT Record last update timestamp
NULL
Table 4.7: Book Model Schema
4.5 API DESIGN
The Online Book Store's back-end exposes URL endpoints that are consumed by the
front-end templates for both full-page rendering and asynchronous data operations. Key
view endpoints include book listing, category management, order processing, and admin
dashboard metrics. The system uses Django's template context mechanism to pass data
from views to templates, and Django's form handling for processing user inputs with
built-in validation and CSRF protection.
 CHAPTER 5

TESTING
5.1 TESTING STRATEGY
Software testing is a critical phase in the software development life cycle that verifies the
correctness, completeness, and quality of the developed software. For the Online Book
Store project, a comprehensive testing strategy was adopted encompassing multiple levels
of testing: Unit Testing, Integration Testing, System Testing, and User Acceptance
Testing (UAT). This multi-level approach ensures thorough coverage of the application's
functionality, from individual code units to the complete integrated system as experienced
by end users.

The testing follows a combined black-box and white-box testing philosophy. Black-box
testing is applied for higher-level system and UAT tests, focusing on external behaviour
without knowledge of internal implementation. White-box testing is applied for unit and
integration tests, examining the internal logic and code paths of views, models, and utility
functions.

5.1.1 Testing Tools

• Django Test Client for simulating HTTP requests and testing view responses.
• Manual testing using browser developer tools for front-end debugging and
network inspection.
• Browser compatibility testing across Google Chrome, Mozilla Firefox, and
Microsoft Edge.
• Responsive design testing using Chrome DevTools Device Mode for various
screen sizes.
• Manual walkthrough testing for UAT with a sample group of student testers.
5.2 UNIT TESTING
Unit testing focuses on testing individual functions and modules in isolation to verify that
each unit behaves as expected for given inputs. For the Online Book Store, unit testing
was primarily applied to model validation, view logic, and form handling functions.

Test Description Input Expected Status

ID Result
UT-01 Register with valid Valid email, User created PASS
data password
UT-02 Register with Existing Error message PASS
duplicate email email
UT-03 Login with correct Valid Session created PASS
credentials admin/pass
UT-04 Login with wrong Wrong Auth failed PASS
password password error
UT-05 Add book with valid Valid book Book record PASS
data data created
UT-06 Add book with Empty title Validation error PASS
missing title field
UT-07 Add category with Unique Category PASS
valid name category created
name
UT-08 Add category with Existing Error: unique PASS
duplicate name category constraint
name
UT-09 Delete book with Existing Book record PASS
valid ID book ID deleted
UT-10 Delete book with Non-existent 404 / graceful PASS
invalid ID ID error
Table 5.1: Unit Test Cases
5.3 INTEGRATION TESTING
Integration testing verifies that individual modules work correctly when combined. In the
Online Book Store, integration testing focused on the interactions between the front-end
templates and back-end views, the URL routing and middleware layers, and the ORM
and database layers.

Test Test Scenario Modules Involved Result

ID
IT-01 User registration via form Front-End ↔ Auth View PASS
submission
IT-02 Admin login and dashboard Auth View ↔ Session ↔ PASS
access Dashboard View
IT-03 Add book via admin form Admin View ↔ ORM ↔ PASS
with image upload Database
IT-04 Book search and filter Front-End ↔ Book View PASS
results displayed ↔ ORM
IT-05 Order placement and order Cart View ↔ Order PASS
history display View ↔ ORM
IT-06 Authentication middleware Auth Middleware ↔ PASS
blocks unauthenticated Admin Routes
admin requests
Table 5.3: Integration Test Results

5.4 SYSTEM TESTING

5.4.1 Functional System Tests
• All primary user journeys (browse, search, register, login, add to cart, place order,
view order history) were tested end-to-end and found to function correctly.
• All form validations were verified to display appropriate error messages for
invalid inputs including empty required fields and duplicate category names.
• The order confirmation system was verified to generate unique order identifiers
for each placed order.
• The administrative panel was verified to correctly add, display, edit, and delete
book and category records.
5.4.2 Non-Functional System Tests
• Page load times were measured using Chrome DevTools Network tab. The
homepage loaded within 1.5 seconds, and internal pages loaded within 1.0
seconds on a broadband connection, well within the 3-second requirement.
• Browser compatibility was verified across Chrome 121, Firefox 122, and Edge
121, with consistent layout and functionality observed across all three browsers.
• Responsive design was verified at 320px, 768px, 1024px, and 1440px widths,
with appropriate layout adaptations at each breakpoint.
• Security testing included attempting XSS injection through form inputs — all
inputs were found to be properly escaped by Django's template engine before
rendering.
5.5 USER ACCEPTANCE TESTING
User Acceptance Testing (UAT) was conducted with a group of 10 student volunteers
who were asked to complete a set of predefined tasks on the Online Book Store
application and provide structured feedback. The tasks included registering an account,
browsing books by category, searching for a specific book, adding books to the cart,
placing an order, and viewing order history.

Usability Criterion Avg. Score (out of Satisfaction Level

5)
Ease of navigation and finding books 4.7 Excellent
Clarity of book information and pricing 4.5 Excellent
Visual appeal and design aesthetics 4.6 Excellent
Speed and responsiveness of the application 4.4 Excellent
Ease of placing an order 4.5 Excellent
Mobile / responsive design quality 4.3 Good
Overall satisfaction with the application 4.6 Excellent
Table 5.5: UAT Feedback Summary
 CHAPTER 6

RESULTS AND DISCUSSION

6.1 SYSTEM OUTPUT
6.1.1 Homepage
The Online Book Store homepage presents a visually engaging hero section featuring a
rotating banner with promotional content and category highlights. Below the hero section,
a prominent search bar allows users to quickly find books by title, author, or keyword.
Further down, featured and recently added books are displayed in a responsive card grid,
showcasing key information including book title, author. A section highlights popular
categories, and the page concludes with a newsletter signup form and a comprehensive
footer with navigation links.

6.1.2 Book Catalogue and Browsing

The Books page presents the complete catalogue of available titles in a filterable, sortable
card layout. Users can filter books by category, sort by price or publication date, and
search by keyword. Each book card displays a cover image, title, author, category badge,
original price with strikethrough, and the discounted selling price, which provides
comprehensive information including a full description, publication details, language,
stock availability, and an Add to Cart button.

6.1.3 Order Flow

The ordering flow begins on the Book Detail page, where users can add a book to their
cart. The Cart page displays all selected books with their quantities and prices, and allows
users to update quantities or remove items. A summary of ordered books, the total
amount, and the estimated delivery information. All orders are persisted to the database
and accessible in the user's Order History page.

6.1.4 Admin Dashboard

The administrative dashboard is accessible only to authenticated admin users, The
navigation sidebar provides access to management sections for Books, Categories, Users,
Orders, and Enquiries. Each management section provides a paginated table of records
with options to add, edit, or delete entries. The Book management section supports cover
image upload, and the admin panel provides search and filter functionality for efficient
record navigation.
6.2 PERFORMANCE ANALYSIS

Metric Homepage Book Catalogue Order Page

Page
Lighthouse Performance 89/100 86/100 91/100
Score
Lighthouse Accessibility 93/100 92/100 95/100
Score
Best Practices Score 95/100 95/100 95/100
SEO Score 91/100 89/100 87/100
First Contentful Paint 0.8s 1.0s 0.7s
Largest Contentful Paint 1.5s 1.9s 1.3s
Total Blocking Time 40ms 55ms 25ms
Cumulative Layout Shift 0.01 0.02 0.01
Time to Interactive 1.9s 2.2s 1.7s
Table 6.1: Performance Metrics

The performance results demonstrate that the Online Book Store achieves good
performance scores across all measured dimensions. The high accessibility scores reflect
Bootstrap 5's built-in ARIA attributes and semantic HTML structure. The low
Cumulative Layout Shift values indicate a stable visual layout during loading,
contributing to a positive user experience.
6.3 COMPARISON WITH EXISTING SYSTEMS

Feature / Criterion Online Book Amazon Flipkart Crossword

Store
Book Catalogue Yes Yes Yes Yes
Browsing
Category-Based Filtering Yes Yes Yes Limited
Shopping Cart Yes Yes Yes Yes
Order Management Yes Yes Yes Yes
User Authentication Yes Yes Yes Yes
Admin Dashboard Yes Yes Yes Yes
Responsive Design Yes Yes Yes Partial
Ad-Free Experience Yes No No No
Open Source / Academic Yes No No No
Payment Gateway Simulated Real Real Real
Technology Stack Django/Python Complex Complex Complex
Table 6.2: Comparison with Existing Systems
 CHAPTER 7

CONCLUSION AND FUTURE WORK

7.1 CONCLUSION
The Online Book Store project has successfully achieved its primary objective of
designing and developing a comprehensive, functional full-stack web application for
online book retail. The application demonstrates the effective application of Python,
Django, HTML5, Bootstrap 5, and JavaScript in building a real-world web solution that
addresses genuine user needs in the book retail domain.

Throughout the development process, sound software engineering principles were

applied, including requirements analysis, system design using Django's MVT
architectural pattern, modular implementation across dedicated Django apps, and
systematic multi-level testing. The resulting application provides a rich user experience
with intuitive navigation, responsive design, secure authentication, comprehensive book
browsing and search capabilities, a smooth ordering workflow, and a full-featured
administrative panel.

The testing phase demonstrated that the application meets its functional requirements
with all primary user workflows functioning correctly. Non-functional requirements
related to performance, responsiveness, and browser compatibility were also
satisfactorily met. User acceptance testing yielded an overall satisfaction score of 4.6 out
of 5, indicating an excellent level of usability and user experience quality.

The project has also provided significant learning outcomes. Working through the
complete software development lifecycle — from requirements gathering and system
design through implementation and testing — has provided practical experience with the
challenges and methodologies of real-world software development. The project deepened
understanding of Django's MVT pattern and ORM, secure user authentication, responsive
front-end development using Bootstrap 5, database schema design, and comprehensive
web application testing.

In conclusion, the Online Book Store represents a successful demonstration of full-stack

web development competency using the Django Python framework. The application
provides genuine value as a book retail platform while serving as a comprehensive
academic exercise in modern web development practices.

7.2 LIMITATIONS
• File-Based SQLite Storage: While SQLite is suitable for development and
demonstration, it introduces limitations for concurrent write operations, large-
scale query performance, and deployment in multi-instance production
environments. A production implementation would require migration to
PostgreSQL or MySQL.
• Simulated Payment Processing: The current implementation does not integrate
with a real payment gateway. The ordering process completes without actual
financial transaction processing, which is essential for a commercially deployed
application.
• No Real-Time Inventory Updates: Book stock levels are not updated in real time
based on concurrent orders, which could lead to overselling in a high-traffic
production scenario.
• Limited Email Notification System: The current implementation does not send
automated email notifications for order confirmations, dispatch updates, or
password resets.
• Single-Instance Architecture: The application is designed for single-server
deployment. Horizontal scaling would require additional architectural
components such as a shared session store (e.g., Redis) and a production-grade
database server.
• No Search Engine Optimisation (SEO) for Book Pages: While the application
includes basic SEO meta tags, it does not implement advanced SEO practices
such as dynamic sitemaps, structured data markup, or canonical URLs.
7.3 FUTURE ENHANCEMENTS
7.3.1 Database Migration
Migrating from SQLite to PostgreSQL using Django's database backend switching
capability (simply updating the DATABASES setting in [Link]) is the most critical
enhancement for production readiness. PostgreSQL offers superior concurrency
handling, full-text search capabilities, and better performance under load. Django's ORM
makes this migration largely seamless, requiring no changes to model definitions or query
code.

7.3.2 Payment Gateway Integration

Integration with a payment gateway such as Razorpay (widely used in India), Stripe, or
PayU would enable actual financial transactions. Modern payment gateway APIs provide
comprehensive features including multiple payment methods (credit/debit cards, UPI, net
banking, mobile wallets), secure transaction handling, refund management, and webhook
notifications for real-time payment status updates.
7.3.3 AI-Powered Book Recommendations
The integration of a recommendation engine represents a high-value enhancement for
improving user engagement and sales. A content-based filtering approach could
recommend books based on genre, author, and reading history. A collaborative filtering
approach could suggest books based on the purchasing patterns of similar users. Python's
rich ecosystem of machine learning libraries (scikit-learn, TensorFlow, PyTorch)
integrates naturally with Django.

7.3.4 Book Reviews and Ratings

Adding a user review and star rating system would enrich the book detail pages with
community-driven social proof, helping potential buyers make informed purchasing
decisions. The review system would include moderation capabilities in the admin panel
to handle inappropriate content.

7.3.5 Mobile Application Development

The development of dedicated mobile applications for iOS and Android using React
Native or Flutter would significantly expand the platform's reach. The existing Django
back end could be extended with Django REST Framework (DRF) to expose a RESTful
API consumed by mobile clients, enabling a shared back-end for both web and mobile
platforms.

7.3.6 Real-Time Features

Integration of Django Channels and WebSocket technology would enable real-time
features such as live order status updates, real-time inventory level updates on book pages,
and a live customer support chat interface. These features would significantly enhance
the platform's interactivity and customer service capabilities.
 REFERENCES

[1] A. Holovaty and J. Kaplan-Moss, The Definitive Guide to Django: Web

Development Done Right, 2nd ed., Apress, 2009.
[2] W. S. Vincent, Django for Beginners: Build Websites with Python and Django, 4th
ed., [Link], 2022.
[3] A. Greenfeld and D. Greenfeld, Two Scoops of Django 3.x: Best Practices for the
Django Web Framework, Two Scoops Press, 2020.
[4] L. Percival and S. Bird, Test-Driven Development with Python, 2nd ed., O'Reilly
Media, 2017.
[5] E. Marcotte, Responsive Web Design, 2nd ed., A Book Apart, 2014.
[6] R. T. Fielding, 'Architectural Styles and the Design of Network-based Software
Architectures,' Ph.D. dissertation, University of California, Irvine, 2000.
[7] D. Flanagan, JavaScript: The Definitive Guide, 7th ed., O'Reilly Media, 2020.
[8] M. Haverbeke, Eloquent JavaScript: A Modern Introduction to Programming, 3rd
ed., No Starch Press, 2019.
[9] Django Software Foundation, 'Django Documentation,' [Online]. Available:
[Link]
[10] Bootstrap Inc., 'Bootstrap 5 Documentation,' [Online]. Available:
[Link]
[11] Python Software Foundation, 'Python 3 Documentation,' [Online]. Available:
[Link]
[12] W3C, 'Web Content Accessibility Guidelines (WCAG) 2.1,' World Wide Web
Consortium, 2018. [Online]. Available: [Link]
[13] Google, 'Lighthouse Overview,' Google Developers. [Online]. Available:
[Link]
[14] PyPI, 'Pillow Package,' [Online]. Available: [Link]
[15] [Link], 'SQLite Documentation,' [Online]. Available:
[Link]
[16] Mozilla Developer Network, 'HTTP Methods,' MDN Web Docs. [Online].
Available: [Link]
 APPENDIX I

SOURCE CODE SNIPPETS

I.1 Django Models (adminapp/[Link])
The [Link] file defines the core data entities of the Online Book Store. The Category
model stores book genres, and the Book model stores all book-related attributes. The
ForeignKey relationship between Book and Category enforces referential integrity at the
database level.

from [Link] import models

from [Link] import *

from [Link] import *

from .models import *

# Create your models here.

class Cart([Link]):

user = [Link](UserInfo, on_delete=[Link])

def __str__(self):

return f"Cart of {[Link]}"

class CartItem([Link]):

cart = [Link](Cart, on_delete=[Link])

book = [Link](Book, on_delete=[Link])

quantity = [Link](default=1)

def get_total_price(self):

return [Link] * [Link]

class Order([Link]):

user = [Link](UserInfo, on_delete=[Link])

 ordered_at = [Link](auto_now_add=True)

total_amount = [Link](max_digits=10, decimal_places=2)

def __str__(self):

return f"Order {[Link]} by {[Link]}"

class OrderItem([Link]):

order = [Link](Order, on_delete=[Link])

book = [Link](Book, on_delete=[Link])

quantity = [Link]()

price = [Link](max_digits=10, decimal_places=2)

I.2 URL Configuration (adminapp/[Link])

The URL configuration maps HTTP request paths to their corresponding view functions,
enabling Django's URL dispatcher to route incoming requests correctly.

from [Link] import path

from . import views

urlpatterns=[
path('admindash/',[Link],name='admindash'),
path('adminlogout/',[Link],name='adminlogout
'),
path('addcat/',[Link],name='addcat'),
path('viewcat/',[Link],name='viewcat'),
path('viewbook/',[Link],name='viewbook'),
path('addbook/',[Link],name='addbook'),
path('viewenqs/',[Link],name='viewenqs'),
path('adminpassword/',[Link],name='adminpa
ssword'),
path('delbook/<id>',[Link],name='delbook'),
path('viewinfo/',[Link],name='userinfo'),
path('vieworders/',[Link],name='vieworders')
]

I.3 Admin Registration (adminapp/[Link])

The [Link] file registers the Book and Category models with Django's built-in admin
interface, enabling basic CRUD operations through Django's default admin site in
addition to the custom admin panel.

from [Link] import admin

from .models import *
[Link](Book)
[Link](Category)

I.4 Sample View Function Structure

from [Link] import render,redirect
from .models import *
from [Link] import messages
from [Link] import *
# Create your views here.
def index(request):
userid=[Link]('userid')
books=[Link]()
context={
'books':books,
'userid':userid,
}

return render(request,'[Link]',context)

def contact(request):
if [Link]=="POST":
name=[Link]('name')
email=[Link]('email')
contactno=[Link]('contactno')
subject=[Link]('subject')
message=[Link]('message')
enq=Enquiry(name=name,email=email,contactno=contactno,subject=subject,mess
age=message)
[Link]()
[Link](request,"Your enquiry has been submitted")
return redirect('contact')
userid=[Link]('userid')
context={
'userid':userid,
}
return render(request,'[Link]',context)
def login(request):
if [Link]=="POST":
username=[Link]('username')
password=[Link]('password')
try:
user=[Link](usertype="user",username=username,password=pass
word)
if user is not None:
[Link](request,"Welcome User")
[Link]['userid']=[Link]
return redirect('index')
except [Link]:
[Link](request,"Invalid credentials")
return redirect('login')
userid=[Link]('userid')
context={
'userid':userid,
}
return render(request,'[Link]',context)

def register(request):
if [Link]=="POST":
name=[Link]('name')
email=[Link]('email')
contactno=[Link]('contactno')
password=[Link]('password')
cpassword=[Link]('cpassword')
if password!=cpassword:
[Link](request,"Password and confirm password do not matched")
return redirect('register')
check=[Link](username=email)
if check:
[Link](request,"This email has already registered .")
return redirect('register')
log=LoginInfo(username=email,password=password)
user=UserInfo(login=log,name=name,email=email,contactno=contactno)
[Link]()
[Link]()
[Link](request,"Registered successfull . ")
return redirect('register')
userid=[Link]('userid')
context={
'userid':userid,
}

return render(request,'[Link]',context)

def about(request):
 userid=[Link]('userid')
context={
'userid':userid,
}
return render(request,'[Link]',context)

def adminlogin(request):
if [Link]=="POST":
username=[Link]('username')
password=[Link]('password')
try:
admin=[Link](usertype="admin",username=username,password=
password)
if admin is not None:
[Link](request,"Welcome Admin")
[Link]['adminid']=[Link]
return redirect('admindash')
except [Link]:
[Link](request,"Invalid credentials")
return redirect('adminlogin')

return render(request,'[Link]')

def book_details(request,id):
userid=[Link]('userid')
book=[Link](id=id)

context={
'userid':userid,
'book':book,
}
return render(request,'book_details.html',context)
 APPENDIX II

SCREENSHOTS OF THE APPLICATION

This appendix contains representative screenshots of the Online Book Store application
interface. Each screenshot is accompanied by a brief description of the page or feature
shown.

[Fig. II.1: Screenshot — Online Book Store Homepage]

The homepage features a full-width promotional banner, a prominent search bar, and a
grid of featured book cards. Each card displays the book cover image, title, author, and
pricing with discount highlights. The navigation bar with links to Books, Categories, Cart,
and Login/Register is clearly visible.
[Fig. II.2: Screenshot — Book Catalogue Page]
The book catalogue page displays all available books in a responsive card grid with
category filter options in a sidebar. The search input and sort controls are visible at the
top. Each book card shows the cover image, title, author, category badge, and price.

[Fig. II.3: Screenshot — Book Detail Page]

The book detail page provides comprehensive information about the selected book,
including a large cover image, full description, author, category, language, publication
date, stock availability, and a prominent Add to Cart button.
[Fig. II.4: Screenshot — Shopping Cart]
The shopping cart page displays all books added by the user with quantity controls,
individual prices, and a total summary. Proceed to Order and Continue Shopping buttons
are prominently placed.

[Fig. II.6: Screenshot — Admin Dashboard]

The administrative dashboard displays key platform statistics including total books,
categories, users, and orders. The dark sidebar navigation provides quick access to all
management sections.
[Fig. II.7: Screenshot — Admin Book Management]

The book management section of the admin panel shows a paginated table of all books
with columns for title, author, category, price, stock, and action buttons for editing or
deletion. The Add Book button is prominently placed.
[Fig. II.8: Screenshot — Mobile Responsive View]
The mobile view demonstrates the responsive layout adaptation of the Online Book Store
on a 375px wide smartphone viewport. The navigation collapses into a hamburger menu,
and the book grid adjusts to a single-column.
 CURRICULUM VITAE

Shashvat is a final-year student of Bachelor of Technology in Information Technology at

Babu Sunder Singh Institute of Technology and Management, Lucknow, affiliated to Dr.
APJ Abdul Kalam Technical University, Lucknow. He has maintained a strong academic
record throughout the programme, demonstrating particular aptitude in web development,
database management systems, and software engineering. He has completed coursework
in Operating Systems, Database Management Systems, Computer Networks, Object-
Oriented Programming, Data Structures and Algorithms, and Web Technologies, among
others. During the final year, he undertook the development of the Online Book Store
web application as the major project, gaining hands-on experience with full-stack web
development using Python, Django, HTML5, Bootstrap 5, and JavaScript. He has also
completed relevant online certifications in Python Programming and Web Development
from recognised platforms. He has participated in coding competitions and technical
events organised by the department and has been an active member of the college's
technical club. He aspires to pursue a career in full-stack web development and software
engineering, with a long-term interest in contributing to innovative technology products
in the e-commerce, edtech, or fintech domains. He is a motivated, detail-oriented
individual with strong problem-solving skills and a passion for creating user-friendly
digital experiences.