Online Book Store Management System TU Purposal final
BIT (Nepal College of Information Technology)
Scan to open on Studocu
Studocu is not sponsored or endorsed by any college or university
Downloaded by ram shahi (
[email protected])
Tribhuvan University
Faculty of Humanities and Social Science
A PROJECT PROPOSAL
“Online Book Store Management System”
Submitted to
Department of Computer
Application
Nepal Mega College
In partial fulfillment of the requirements for the Bachelors in Computer Application
Submitted by
Kamal Sanjyal (26602081)
May, 2025
Table of Contents
1. Introduction...................................................................................................................1
2. Problem Statement:......................................................................................................1
3. Objectives......................................................................................................................2
4. Methodology:.................................................................................................................2
a. Iterative Waterfall Model.......................................................................................2
b. Requirement identifications...................................................................................3
I. Study of the existing system........................................................................................3
II. Requirement Collection:.............................................................................................4
c. Feasibility study:......................................................................................................4
I. Technical Feasibility...................................................................................................4
II. Operational Feasibility................................................................................................5
III. Economic Feasibility.................................................................................................6
IV. Overall Conclusion:...................................................................................................6
d. High level design of the system:.............................................................................6
I. System Flow Chart.......................................................................................................7
II. Use Case Diagram......................................................................................................8
III. Algorithm Overview................................................................................................10
5. Gantt Chart:................................................................................................................12
6. Expected Outcomes....................................................................................................13
7. References....................................................................................................................14
1. Introduction:
Online Book Store Management System is a modern web application that makes it easy
for customers to browse, search, and buy books online. With a clean and intuitive
interface, users can view detailed book information, read reviews, and manage their
accounts smoothly. The system ensures a seamless shopping experience from browsing to
checkout.
For administrators, it offers powerful tools to manage inventory, process orders, and
update book listings efficiently. Admins can monitor stock, track sales, and keep the
catalog up to date, making store management much simpler and more organized.
Security is a top priority, with strong data encryption and secure payment processing to
protect user information. The system also provides sales reports and analytics, helping
businesses make smart decisions and grow confidently. Overall, it boosts customer
satisfaction and streamlines bookstore operations.
2. Problem Statement:
Online Book Store Management system is facing significant operational and technological
challenges that hinder its efficiency and the overall customer experience. Managing
inventory effectively has proven complex, especially with the need to track stock levels
across multiple book formats such as physical copies and digital downloads. Inaccurate
stock information and delayed restocking lead to frequent out-of-stock situations, which
negatively impact sales and customer trust. Furthermore, the current system struggles to
process orders smoothly and coordinate shipping logistics, resulting in delays and
customer dissatisfaction.
Another critical issue is the protection of sensitive customer information, including
personal details and payment data, from potential breaches and fraudulent activity.
Inadequate security measures expose the business to regulatory penalties and loss of
reputation. Additionally, the lack of advanced tools for collecting and analyzing sales data
limits the organization’s ability to make informed business decisions and adapt to market
trends. Without improvements in these areas—inventory management, order fulfillment,
data security, and reporting—the online bookstore risks falling behind competitors and
failing to meet customer expectations.
3. Objectives:
The objective of this project is to develop an Online Book Store Management System that
improves operational efficiency and enhances the overall customer experience. The
system will focus on providing smooth inventory management, secure transactions, and a
seamless shopping journey.
The key objectives are:
• Continuously monitor and update book stock levels to prevent discrepancies.
• Design a user-friendly platform for easy navigation, search, and purchase.
• Integrate with shipping carriers for real-time tracking and delivery updates.
In short, these objectives are designed to be clear, practical, and achievable, addressing
the needs of both customers and administrators while supporting future growth and
scalability.
4. Methodology:
a. Iterative Waterfall Model:
The project follows the Iterative Waterfall Model is a structured and systematic approach
that divides the software development process into clear stages: requirement analysis,
system design, implementation, testing, deployment, and maintenance. Unlike the
traditional waterfall model, this iterative version allows developers to revisit and improve
earlier phases based on feedback and new insights before moving on to the next stage. In
the context of the Online Book Store Management System, this model is highly suitable
because it provides a balance of structure and flexibility.
Figure 1: Iterative Waterfall Methodology
b. Requirement identifications:
Requirement identification is the process of figuring out exactly what is needed for the
project. Online Book Store Management System are gathered before initiating the
development life cycle. To design and build the system effectively, both functional and
nonfunctional requirements have been thoroughly analyzed.
I. Study of the existing system:
This phase focuses on understanding existing online book store systems and identifying
their limitations. It involves reviewing online resources, visiting popular book store
websites, and analyzing local and international platforms to gather insights and improve
upon them in the proposed system.
The following sources were referred to during the study:
1. Amazon Books – Online Bookstore work [1]
2. Shopify, “Online Bookstore” [2]
3. Books Net – to create online Book Selling platform [3]
From this review, several common issues in current or older systems were identified:
• Complex and sometimes confusing user interfaces, especially for first-time users.
• High development and maintenance costs for small or local stores.
• Lack of personalized features like recommendations or simple order tracking in
many local platforms.
These findings help shape the direction of the Online Book Store Management System,
focusing on creating a simpler, more user-friendly, and affordable system that is easy to
manage and provides a better online shopping experience for customers.
II. Requirement Collection:
It is a process of collecting information required to build an effective and user-friendly
system. The below mentioned points were followed to collect requirements:
i. Source of Information:
• Interviews and discussions with bookstore owners, customers, and teachers.
• Observations and references from existing online book store websites such as
Building an onine bookstore withmodern technologies. [4] and Statista [5].
ii. Key Takeaways:
• User needs and desired functionalities such as easy book search, simple checkout
process, and secure payment options.
• Admin needs for easy inventory management, order tracking, and report
generation.
c. Feasibility study:
Feasibility study is carried out to check if the proposed system is practical, achievable,
and worth implementing. It helps ensure that the system can be developed successfully
using available resources and technology.
I. Technical Feasibility:
Technical feasibility evaluates whether the Online Book Store Management System can
be built with the current tools, technologies, and skills.
The goal of this system is to allow customers to easily browse and buy books online and
to help bookstore admins manage inventory and orders efficiently. This can be
accomplished
using:
• Backend: Python (Django or Flask) — reliable, secure, and perfect for building web
applications quickly.
• Frontend: HTML, CSS: For a clean, responsive user interface and simple interface.
• Database: MySQL or PostgreSQL — powerful and widely used
relational databases, perfect for storing structured data like book details, user
accounts, and order records.
These technologies are mature, widely supported, and match the system’s need for
simplicity, flexibility, and easy maintenance. No special or expensive hardware is needed.
The system can run smoothly on standard web hosting services or cloud servers.
Conclusion:
Based on available developer skills, trusted technologies, and the project requirements,
the system is technically feasible and can be implemented with minimal risk within the
given time and resources.
II. Operational Feasibility:
Operational feasibility determines whether the proposed system can work efficiently in its
real environment. It focuses on ease of use, maintenance, and overall practical
performance.
The Online Book Store Management System is designed to be simple and user-friendly so
that anyone can use it without needing technical knowledge. Customers can easily search
for books, add them to their cart, and place orders with just a few clicks. The system is
also mobile-friendly, allowing customers to shop using their smartphones or tablets.
For bookstore admins, the system offers an easy-to-use dashboard where they can add or
remove books, update prices and stock, and check order statuses. It requires no special
training and can be managed with basic computer skills.
The system is designed to fit smoothly into the daily workflow of a bookstore and does
not need complicated setup or maintenance.
Conclusion:
The system is practical to use, easy to maintain, and fits perfectly into existing bookstore
operations. Based on these factors, it is considered operationally feasible.
III. Economic Feasibility:
Economic feasibility checks if the system is financially reasonable and whether it will
provide good value for the investment.
The Online Book Store Management System is affordable to develop and much cheaper
than opening a new physical branch. By moving online, the bookstore can reach many
more customers without high operating costs like rent or extra staff.
After launching, the system is expected to increase book sales, reduce manual work, and
improve overall efficiency. This will help save costs and increase profit over time.
ROI:
ROI = (Net Profit / Total Cost) × 100
A positive ROI means the system will be beneficial in the long run.
Conclusion:
The system is cost-effective, profitable after deployment, and provides better value
compared to traditional business expansion methods. It is economically feasible.
IV. Overall Conclusion:
Based on these technical, operational, and economic analysis, the Online Book Store
Management System is feasible in all three areas. It can be developed successfully and is
expected to provide great benefits to both bookstore owners and customers.
d. High level design of the system:
High-level design is like making a big plan for a system before building it. It shows the
main parts of the system and how they work together.
A High-Level Design Document acts like a guidebook. It includes diagrams and
explanations about how the system works, how data moves, what technologies are used,
how security is managed, and what happens if something goes wrong.
system.
I. System Flow Chart:
A flowchart is a simple diagram that shows step by step how a system or process works. It
uses boxes, shapes, and arrows to make it easy to see what happens first, what happens
next, and how everything is connected. In an online book store, for example, a flowchart
can clearly show how a customer signs up, searches for books, places an order, and how
the admin handles that order behind the scenes. It helps everyone understand the system
in
a quick and clear way.
Figure 2: System Flow Chart
Figure 3: Dashboard Login Flow Chart
II. Use Case Diagram:
Actors:
• Customer –People who buy books online.
• Store Admin –People who manage the online bookstore.
A case diagram is a visual representation of the functional requirements of a system from
the perspective of its users. It illustrates the various interactions between users and
system.
Figure 4: Use Case diagram of Customer OBSMS
10
Figure 5: Use Case diagram of Admin OBSMS
Store Admin is responsible for all the changes in the system, whereas the Customer will
be responsible for tasks like browsing and searching for books, placing orders, making
payments, viewing order history, and writing reviews and ratings for purchased books.
III. Algorithm Overview:
• Trie for book title or author search (rule-based)
The In our bookstore system, the Trie algorithm is used to perform fast searching of book
titles or author names.
11
When a customer starts typing a book title or an author’s name in the search bar, the
system uses a Trie data structure to quickly find matching suggestions.
Example:
If the system has book titles like Harry Potter, Hunger Games, and Hamlet, and a user
types “[email protected]” , the Trie can instantly suggest Harry Potter and
Hamlet without scanning every single book title one by one.
The main advantage of using a Trie is that search speed depends on the length of the word
being typed rather than the total number of books. This makes the search experience fast
and smooth even if the bookstore has thousands of books.
• Random Forest for recommending books
The Random Forest algorithm is used to suggest books to customers based on their
behavior and preferences. It is a machine learning model trained on data such as purchase
history, browsing patterns, book categories, user ratings, and more.
Example:
During training, the model might learn that customers who buy romantic novels also often buy
poetry books, or that users who browse fantasy books late at night might like mystery novels.
When a new user browses books, the Random Forest model analyzes their activity and
recommends books they are likely to enjoy, using the combined votes of many decision
trees.
Random Forest is chosen because it is good at handling different types of data, works well
with large datasets, and reduces the risk of inaccurate or biased suggestions.
• Timsort for sorting orders and reviews
Timsort is used to sort lists shown on the admin dashboard and on the customer’s order
history page. These lists include orders, customer reviews, or book ratings. Sorting can be
based on date, price, or rating score.
Example:
Suppose if the admin wants to view orders by most recent first, or a customer wants to see
reviews from newest to oldest, Timsort organizes them quickly and accurately. For
12
instance, if there are orders from "March 1", "February 25", and "March 3", they will be
shown as "March 3", "March 1", "February 25".
Timsort is ideal here because it is designed for real-world data, which is often already
partly sorted. It is fast and stable, and is used by default in many popular programming
languages like Python and Java.
5. Gantt Chart:
A Gantt chart is a horizontal bar chart used in project management to visually represent a
project plan over time. The purpose of a Gantt chart is to help people see and understand
the schedule of a project. It shows all the tasks that need to be done, when they start, and
when they finish. This makes it easier to plan and manage the project, as everyone can see
what needs to be done and when it needs to be finished.
Table 1: Activity Table
Figure 5: Gantt Chart
13
6. Expected Outcomes:
The expected outcomes of the Online Book Store Management System project are listed
below:
• A order management page.
• A registering and login page.
A wireframe is a simple visual blueprint of the website or application. It shows the basic
structure and layout of the pages without focusing on design details like colors or images.
Here’s a simple example of a wireframe for the Online Book Store Management system:
Figure 6: Login page
Figure 7: User Dashboard
14
Figure 8: Admin Dashboard
In conclusion, these expected outcomes provide a clear vision for success. With a focus
on user-friendly design, smooth browsing and buying experience, and strong management
features, the project is ready to deliver an attractive, engaging, and reliable online book
store that meets the needs of both customers and store admins.
7. References
[1] Amazon, "How online book stores work," [Online]. Available:
https://www.aboutamazon.com/news/retail/how-amazon-sells-books-online.
[2] Shopify, "Start an online bookstore: Tips & tools," [Online]. Available:
https://www.shopify.com/blog/online-bookstore.
[3] Booknet, "How to create an online book selling platform," [Online].
Available: https://booknet.com/en/post/how-to-create-an-online-bookstore.
[4] Medium, "Building an online bookstore with modern web technologies,"
[Online]. Available: https://medium.com/@techwriter/building-an-online-bookstore.
[5] Statista, "E-commerce book sales statistics," [Online]. Available:
https://www.statista.com/topics/871/online-book-sales/.
15
