0% found this document useful (0 votes)
6 views23 pages

SE Sample

The document is a project report for 'BookHive', a web-based online bookstore system developed by Aashish Poudel for a Bachelor of Computer Engineering degree. It outlines the system's objectives, methodology, and features, including user management, book catalog, shopping cart, and payment processing, emphasizing security and efficiency. The report also details the development process using the incremental model, testing strategies, and technologies employed.

Uploaded by

subigyas07
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
6 views23 pages

SE Sample

The document is a project report for 'BookHive', a web-based online bookstore system developed by Aashish Poudel for a Bachelor of Computer Engineering degree. It outlines the system's objectives, methodology, and features, including user management, book catalog, shopping cart, and payment processing, emphasizing security and efficiency. The report also details the development process using the incremental model, testing strategies, and technologies employed.

Uploaded by

subigyas07
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

A PROJECT REPORT

ON
BOOKHIVE

Submitted in the partial fulfillment in the requirement for the


Award of the degree
of
BACHELOR OF COMPUTER ENGINEERING
By
Aashish Poudel
Roll: 231301
UNDER GUIDANCE
By
Er. Nirdosh Adhikari

DEPARTMENT OF COMPUTER ENGINEERING


Balkumari, NCIT
8 Feb 2026

1
Table of Content
Contents
ABSTRACT 1
List of Tables 2
CHAPTER 1: INTRODUCTION 3
1.1 Problem Statement 4
1.2 Objectives 5

1.3 Scope and Limitations 6

CHAPTER 2: LITERATURE REVIEW 7


CHAPTER 3: METHODOLOGY 8
3.1 System Analysis 9

3.2 Feasibility Study 10

3.3 Incremental Model 11

3.4 System Design 12


CHAPTER 4: IMPLEMENTATION AND TESTING 13

4.1 Module Description 14

4.2 Testing 15
4.3 Tools and Technologies 16

4.4 Gantt Chart 17

CHAPTER 5: CONCLUSION 18

REFERENCES 19

I
ABSTRACT

BookHive is a web-based online bookstore system designed to provide a convenient, efficient,


and user-friendly platform for purchasing books online. The system allows users to create
accounts, securely log in, browse and search for books, and filter them based on categories such
as author, price, and genre. Users can add selected books to a shopping cart, place orders, and
make secure payments using multiple payment options. The system automatically manages order
processing and updates book inventory after successful transactions. Additional features such as
reviews and ratings help users make informed purchasing decisions. BookHive also includes a
notification system that informs users about order confirmations and shipping updates. An
administrative module enables administrators to manage users, books, orders, and generate sales
reports. The system is developed using the incremental model, allowing features to be
implemented and tested in phases. Emphasis is placed on security, performance, reliability, and
compatibility across different devices and browsers. Overall, BookHive aims to automate the
book-selling process and deliver a reliable and scalable online bookstore solution.

II
List of Figures
1) Use Case Diagram

Figure 1: Use Case Diagram


2) Sequence Diagram

Figure 2: Sequence Diagram


3) Class Diagram

Figure 3: Class Diagram


4) DFD level 0 and DFD level 1

Figure 4: DFD level 0

Figure 5: DFD level 1


5) Component Diagram

Figure 6: Component Diagram


6) ER Diagram

Figure 7: ER Diagram
7) Activity Diagram
Figure 8: Activity Diagram

8) Architecture Diagram

Figure 9: Architecture Diagram


CHAPTER 1: INTRODUCTION
1.1 Problem Statement

With the rapid growth of internet technologies and e-commerce platforms, users increasingly
expect convenient, fast, and reliable online services. However, many traditional book
purchasing and management systems still rely on manual or semi-automated processes.
These systems often suffer from limitations such as inefficient inventory management,
difficulty in searching and tracking books, delayed order processing, lack of secure payment
integration, and poor communication with customers regarding order status and availability.

From the user’s perspective, customers face challenges in accessing a wide variety of books,
comparing prices, checking real-time availability, and receiving timely updates on orders
and deliveries. From the administrator’s perspective, managing book inventory, user
accounts, orders, payments, and generating sales reports manually is time-consuming, error-
prone, and inefficient.

To address these issues, there is a need for a centralized, web-based Online Book
Management System that automates book catalog management, user handling, order
processing, and payment transactions. The proposed system, BookHive, aims to provide a
secure, scalable, and user-friendly platform that enhances customer experience, improves
operational efficiency, ensures data accuracy, and supports effective decision-making for
administrators.

1.2 Objectives
 To provide users with convenient access to browse and purchase books online.
 To enable efficient searching, filtering, and selection of books.
 To ensure secure and reliable online payment for purchases.
 To allow users to track orders and view their purchase history.

1.3 Scope and Limitations

Scope

1. Users can browse, search, and buy books online.


2. Secure payments and order tracking are provided.
3. Admins manage books, inventory, and customer orders.
4. System generates reports for sales and activity.

Limitations

1. Requires stable internet connection for all services.


2. Delivery depends on external courier service efficiency.
3. Stock may be unavailable for multiple simultaneous orders.
4. Limited payment options depending on gateway integration.

1
1.4 Requirements
Functional Requirements:
1)User Management
● The system should allow users to create, login and log out an account.
● The system should allow users to update personal details (name, address, phone).

2) Book Catalog
● The system should display all available books with details (title, author, price, stock).
● The system should allow users to search books by title, author, category, or ISBN.
● The system should allow users to filter books by price, rating, genre, etc.
● The system should allow admins to add, update, or remove books.

3) Shopping Cart
● The system should allow users to add books to a shopping cart.
● The system should allow users to remove books from the cart.
● The system should automatically calculate total order amount.

4) Orders
● The system should allow users to place orders from their cart.
● The system should update inventory after a successful order.
● The system should allow users to cancel orders before shipping.

5) Payments
● The system should support multiple payment methods (credit card, debit card, eSewa).
● The system should verify and process payments securely.
● The system should notify users of payment success or failure.

7) Reviews & Ratings


● Users should be able to rate books (1–5 stars).
● Users should be able to write book reviews after purchase.

8) Notifications
● The system should send email/SMS for order confirmation.
● The system should notify users about shipping updates.

9) Admin Module
● Admins should be able to manage users (activate, deactivate accounts).
● Admins should be able to view and manage all orders.

Non- Functional Requirements:

1) Performance
● The website should feel quick and responsive, even when many people are using it at
once.
● Searching for books shouldn’t take more than a few seconds.

2
2) Compatibility
● The system shall work on major browsers (Chrome, Firefox, Safari, Edge).
● The system shall be mobile-friendly and support responsive design.

3) Reliability & Availability


● The system should have 99.9% uptime.
● The system should recover from failures within 5 minutes.

4) Maintenance
● The system should be easy for developers to update without breaking other features.
● Documentation should be clear so future changes can be made quickly.

5) Backup and Recovery


● All important data should be backed up regularly.
● If data is lost, the system should be able to restore it without much delay.

3
CHAPTER 2: LITERARURE REVIEW

The growth of e-commerce has significantly influenced the way people purchase products,
including books. Traditional methods of buying books from physical stores are gradually being
replaced by online platforms that provide convenience, accessibility, and efficiency. Several
studies have highlighted the benefits and challenges associated with online book buying systems.

According to research by Laudon and Traver (2021), online book buying platforms provide users
with easy access to a wide range of books without the limitations of geographical boundaries.
These systems allow users to search, compare, and select books based on categories, authors,
prices, and ratings. Moreover, the ability to access customer reviews and recommendations
enhances the decision-making process, improving user satisfaction.

A study by Chen et al. (2020) emphasized the role of secure online payment systems in building
trust among users. Online book buying platforms integrate multiple payment gateways, ensuring
that transactions are safe and efficient. The use of encryption and secure protocols is essential to
prevent unauthorized access to sensitive user information such as payment details and personal
data.

Inventory management is another crucial aspect discussed in the literature. Systems that maintain
real-time records of available books help prevent issues like double orders or stockouts. Research
by Kumar and Singh (2019) highlighted that automated inventory tracking and report generation
significantly reduce administrative workload and increase operational efficiency. Admins can
easily monitor sales trends, popular books, and customer preferences, which supports better
decision-making.

Several researchers also pointed out the limitations of online book buying systems. Dependence
on internet connectivity is a primary concern, as users cannot access the system offline. Delivery
delays due to third-party courier services can affect user satisfaction. Additionally, stock
availability may fluctuate when multiple users order the same book simultaneously, which can
lead to order cancellations or delays.

Despite these limitations, the literature agrees that online book buying systems are essential in
modern commerce. Platforms like Amazon, Flipkart, and Book Depository serve as practical
examples, demonstrating the effectiveness of online systems in providing convenience, variety,
and security. Emerging technologies, such as mobile applications and AI-based recommendation
systems, are further enhancing the user experience, making online book buying faster, more
personalized, and accessible.

In conclusion, online book buying systems provide a streamlined, user-friendly approach to book
purchasing, combining secure transactions, efficient inventory management, and easy
accessibility. While challenges such as delivery delays and stock management remain, ongoing
technological advancements continue to improve system reliability, user satisfaction, and overall
efficiency.

4
CHAPTER 3: METHODOLOGY
3.1 System Analysis

System analysis is an important phase in the development of the BookHive online bookstore
system. In this phase, the existing problems and user needs are studied in detail to understand
what the system should accomplish. The main goal of system analysis is to gather and analyze
functional and non-functional requirements of the system.

For the BookHive system, system analysis involved identifying the main users of the system,
such as customers and administrators, and understanding their roles. Customers need features
like user registration, book searching, shopping cart, order placement, and payment options,
while administrators require functionalities such as managing books, users, orders, and
generating reports. By analyzing these requirements, a clear understanding of system behavior
and limitations was achieved, which helped in planning the system effectively.

3.2 Feasibility Study

The feasibility study determines whether the BookHive system is practical and feasible to
develop. It evaluates the project from different aspects to ensure successful implementation.

Technical Feasibility: The BookHive system is technically feasible as it can be developed using
existing and widely available web technologies such as HTML, CSS, JavaScript, backend
frameworks, and database management systems. The required hardware and software resources
are easily accessible.

Economic Feasibility: The system is economically feasible since open-source tools and
technologies can be used, minimizing development costs. In the long run, the system helps
reduce manual effort and operational costs by automating book sales and inventory management.

Operational Feasibility: The system is user-friendly and easy to operate. Both customers and
administrators can use the system with minimal training, making it operationally feasible.

Schedule Feasibility: The system can be completed within the given time frame by following a
planned and structured development approach such as the incremental model.

3.3 Incremental Model

The Incremental Model is a software development approach in which the system is developed in
small, manageable parts called increments. Each increment adds new features to the existing
system, allowing partial functionality to be delivered early.

In the BookHive system, development is divided into multiple increments. The first increment
includes basic functionalities such as user registration, login, and book browsing. The second
increment focuses on shopping cart and order management. Later increments include payment
processing, reviews and ratings, notifications, and administrative features. This model is suitable
5
for BookHive because it allows continuous testing, early user feedback, reduced risk, and better
quality software development.

3.4 System Design

System design is the phase where the analyzed requirements are converted into a structured
solution. It defines how the system components will work together to achieve the desired
functionality.

The BookHive system follows a client-server architecture. The frontend is responsible for user
interaction and display, while the backend handles business logic, database operations,
authentication, and security. The database is designed to store information related to users,
books, orders, payments, and reviews.

The system design includes module design, database design, and interface design. Security
measures such as user authentication, data validation, and secure payment handling are included
to ensure data integrity and system reliability. The design ensures that the system is scalable,
maintainable, and efficient.

6
CHAPTER 4: IMPLEMENTATION AND TESTING
4.1 Module Description

1. User Management Module

 Handles user registration, login, and logout.


 Allows users to update personal information.
 Provides password reset and secure authentication.

2. Book Catalog Module

 Displays available books with detailed information.


 Supports searching and filtering of books.
 Allows admins to add, update, or remove book records.

3. Shopping Cart Module

 Enables users to add or remove books from the cart.


 Calculates total order amount automatically.
 Maintains cart details until checkout.

4. Order Management Module

 Processes user orders from the shopping cart.


 Updates inventory after successful orders.
 Allows users to cancel orders before shipping.

5. Payment Module

 Supports multiple payment methods.


 Handles secure payment processing.
 Confirms payment status to the system.

6. Review & Rating Module

 Allows users to rate and review purchased books.


 Displays reviews for other users.

7. Notification Module

 Sends order confirmation and status updates.


 Notifies users about payments, shipping, and offers.

7
8. Admin Module

 Manages users, books, and inventory.


 Monitors orders and generates sales reports.

4.2 Testing

Testing is performed to ensure that the BookHive system functions correctly, securely, and
reliably according to the specified requirements.

1. Unit Testing

 Individual modules such as user login, book search, cart, and payment are tested
separately.
 Ensures each function works as expected.

2. Integration Testing

 Tests interaction between modules like cart, order, payment, and inventory.
 Verifies correct data flow between system components.

3. System Testing

 The complete system is tested as a whole.


 Ensures all functional and non-functional requirements are met.

4. User Acceptance Testing (UAT)

 Conducted with end users to verify system usability and functionality.


 Confirms the system meets user expectations.

5. Security Testing

 Tests authentication, authorization, and payment security.


 Ensures user data is protected from unauthorized access.

6. Performance Testing

 Evaluates system response time under normal and heavy load.


 Ensures fast search and checkout operations.

8
4.3 Tools and Technologies

1. Front-End Technologies

 HTML – Structure of web pages


 CSS – Styling and responsive design
 JavaScript – Client-side interactivity

2. Back-End Technologies

 [Link] – Server-side runtime environment


 [Link] – Web application framework

3. Database

 MySQL – Storage of user, book, order, and payment data

4. Payment Integration

 eSewa API – Online payment processing

5. Development Tools

 Visual Studio Code – Code editor


 Git & GitHub – Version control

6. Design & Documentation Tools

 [Link] – UML and architecture diagrams


 MS Word / Google Docs – Documentation

7. Testing Tools

 Postman – API testing


 Browser Developer Tools – Debugging and testing

9
4.4 Gantt Chart

Task Week 1 Week 2 Week 3 Week 4 Week 5 Week 6


Requirement Analysis ███
System Design ███
Database Design ███
Front-End Development ███ ███
Back-End Development ███ ███
Payment Integration ███
Testing ███
Documentation ███ ███
Deployment ███

10
CHAPTER 5: CONCLUSION

The BookHive online bookstore system was designed and developed to provide a convenient and
efficient platform for buying and selling books online. The system successfully incorporates key
features such as user registration and authentication, book catalog management, advanced search
and filtering, shopping cart functionality, order processing, and secure payment methods.
Additional features like reviews, ratings, and notification services enhance user experience and
help customers make informed decisions. The system reduces manual processes, improves
accuracy in inventory management, and ensures smooth order handling.

The use of the incremental development model enabled systematic implementation and
continuous improvement of the system. An administrative module allows effective management
of users, books, orders, and sales reports. Non-functional requirements such as performance,
security, reliability, and compatibility were carefully considered to ensure a stable and user-
friendly application. Overall, BookHive achieves its objectives and provides a scalable, reliable,
and practical solution for modern online bookstore management.

11
REFERENCES

[1] K. C. Laudon and C. G. Traver, E-Commerce: Business, Technology, Society, 16th Edition,
Pearson Education, 2021.

[2] E. Turban, J. Outland, D. King, J. Lee, J. Liang, and D. Turban Jr., Electronic Commerce: A
Managerial and Social Networks Perspective, 9th Edition, Springer, 2018.

[3] X. Chen, Y. Li, and Z. Zhang, “Secure online payment systems and consumer trust in e-
commerce platforms,” International Journal of Electronic Commerce, 2020.

[4] R. Kumar and S. Singh, “Automated inventory management systems in e-commerce


applications,” International Journal of Computer Applications, 2019.

[5] J. A. Chevalier and D. Mayzlin, “The impact of online reviews on consumer purchasing
behavior,” Journal of Marketing Research, 2006.

12

You might also like