A project report on

“Bookstore Management System”

Submitted to Bharti Vishwavidyalaya

in partial fulfillment for the award of degree of

BACHELOR
OF
TECHNOLOGY
Submitted by

PRAGYA CHANDRAKAR (B.TECH SEMESTER-7 ROLL NO:

2013170021)

Guided by

Shanu gaur

December – 2023

Prepared By : Pragya Chandrakar 1|Page

 ACKNOWLEGEMENT

We have taken efforts in this project. However, it would not have been possible without
the kind support and help of our Faculties. We would like to extend my sincere thanks to all of
them.

We are highly indebted to Bharti Vishwavidalaya for their guidance and constant
supervision as well as for providing necessary information regarding the project & also for their
support in completing the project.

We would like to express my gratitude towards my parents & member of KBP for their
kind co-operation and encouragement which help us in completion of this project. Last but not
least, many thanks go to the head of the project, Mr. Naveen Pandit whose have invested his full
effort in guiding the team in achieving the goal. We have to appreciate the guidance given by
other supervisor as well as the panels especially in our project presentation that has improved our
presentation skills thanks to their comment and advices.

We would like to express our special gratitude and thanks to all above mentioned people
for giving us such attention and time. Our thanks and appreciations also go to our colleague in
developing the project and people who have willingly helped us out with their abilities.

Prepared By : Pragya Chandrakar 2|Page

 ABSTRACT

Bookstore Management System is basically used to build an web application program

which help people to find and buy latest design of Books with different categories like
Biography, Programming, Management, etc. It is useful in the way that it makes an easier way to
buy Personal Bookstore.

Today most of the book shop is useful for shopping site. The admin have lots of paper
work and they are using desktop, spread sheet like MS Excel application to manage data in soft
copy about user record. In this proposed Bookstore System it will run in server and user can
handle whole the registration activities.

This application maintains the centralized database so that any changes done at a location
reflects immediately. This is an online tool so more than one user can login into system and use
the tool simultaneously.

The aim of this application is to reduce the manual effort needed to manage transactions
and historical data used in various gods owns. Also this application provides an interface to users
to view the details And Design about Bookstore.

Prepared By : Pragya Chandrakar 3|Page

 Table of Contents

INTRODUCTION...........................................................................................................................8
1.1 Project Background..............................................................................................................9
1.2 Objectives of project.............................................................................................................9
1.3 Purpose of Project................................................................................................................9
1.4 Scope of Project.................................................................................................................10
1.5 Applicability of Project:.....................................................................................................10
REQUIREMENT AND ANALYSIS............................................................................................11
2.1 Problem Statement.............................................................................................................12
2.2 Requirement specifications................................................................................................12
2.3 Hardware requirement........................................................................................................13
2.4 Software Requirement........................................................................................................13
2.5 Planning and scheduling....................................................................................................14
SYSTEM DESIGN........................................................................................................................23
3.1 Over All System Design Using Designing Tools..............................................................24
3.2 Data dictionary...................................................................................................................37
3.3 Input/Output design............................................................................................................41
TESTING AND IMPLEMENTATION........................................................................................56
4.1 Testing Approach Used......................................................................................................57
4.2 Test Cases..........................................................................................................................59
4.3 Implementation approaches..............................................................................................63
CONCLUSION..............................................................................................................................64
5.1 Limitation of system.........................................................................................................65
5.2 Future Scope of System....................................................................................................66
5.3 Bibliography......................................................................................................................66

Prepared By : Pragya Chandrakar 4|Page

 Chapter 1
Introduction

 This Software allows the Admin to store the book details and the customer details.
 Easier access to information like customer information and availability.
 Provide facility of storing data to reduce the paper work.
 In Bookstore Management System Users can by a book and Admin shows their name and
other background of the user.
 A new idea about Project how Bookstore Management System works.
For make a system computerized.
 The main purpose of Book-store Management System is to focused on the solution of all
the problems related to the paper work from the different reasons.
 It provides a facility to handle all the activities at one place. With the help of this
application, admin can perform different kind of operations at the same time and place.
 Bookstore management System has an ability to keep the records safe related to Books.
 We provide the best service in our website or focuses on user choice. We will improve
new feat user can easily understand and trust our system.
 The intentions of the system are to reduce over-time pay and increase the number of
records that can be treated accurately; Requirements statements in this document are both
functional and non-functional.
 Correct and Accurate Searching that provides the result by applying search operation.
 Customers can book a book with just few clicks.
 Give flexibility admin to use database effectively and utilize the word, not pad and
calculator Unambiguous and understandable by all level facilities effectively.
 Unambiguous and understandable by all level.

Prepared By : Pragya Chandrakar 5|Page

 Chapter 2

Requirement And Analysis

2.1 Problem Statement
 So much Paper work
 Process is much time consuming
 Extra expense in paper work
 Large storage of data
 Manual process of Vehicle purchase and sales on finance and cash and generate reports
of model wise, weekly, monthly, annual progress is so difficulties.
 Speed and faster information retrieval.
 Accuracy and consistency in manual system is less.
 Personal delay.
 In manual system it is tedious task to search a particular record later after.
 Increase the staff in test taken place and wasting of their precious time.

2.2 Requirement Specification

As per the System Requirements it contains two (2) Modules:

1) Admin

2) Client

Functionalities of Admin:
 This Module includes the mainly following tasks:
 Entry of Category.
 Category List.
 Add a New Book.
Prepared By : Pragya Chandrakar 6|Page
Functionalities of Client:
 This Module includes the mainly following tasks:
 View Books.
 Add books to Cart.
 Search Books.
 View or Add items in Cart.

2.3Hardware requirement
 System type 32 bit Operating System.

 Windows 7/8/8.1/10

 Linux Ubuntu / Light ubuntu

 Mac OS

 350MB RAM

2.4 Software Requirement

 Wamp Server
 MySQL
 Browser
 PHPMyAdmin

Client Side Tools

 Processor : PC with a Dual core processor or above is Recommended: 2.20 GHz
processor.

 RAM : 512 MB or onwards Recommended.

 Hard Disk : 45 MB of available space required on system drive of available or more.

Prepared By : Pragya Chandrakar 7|Page

Planning and Scheduling:-

ID Task Name Start/Finish Duration

1 Analysis 25/12/2018 to 8 Days
01/01/2019
2 Design 01/01/2019 to 9 Days
09/01/2019
3 Coding 10/01/2019 to 4 Weeks
08/02/2019
4 Implementation 08/02/2019 to 5 Days
12/02/2019
5 Testing 12/02/2019 to 6 Days
17/02/2019
6 Documentation 18/02/2019 to 3Weeks
10/3/2019

(Figure 1 : Planning and Sheduling)

Back End - PHP, MySQL

1. PHP
The PHP Hypertext Pre-processor (PHP) is a programming language that allows
web developers to create dynamic content that interacts with databases. PHP is basically
used for developing web based software applications. This tutorial helps you to build
your base with PHP. PHP started out as a small open source project that evolved as more
and more people found out how useful it was. Rasmus Lerdorf unleashed the first version
of PHP way back in 1994.
 PHP is a recursive acronym for "PHP: Hypertext Preprocessor".

Prepared By : Pragya Chandrakar 8|Page

  PHP is a server side scripting language that is embedded in HTML. It is used to
manage dynamic content, databases, session tracking, even build entire e-
commerce sites.
 It is integrated with a number of popular databases, including MySQL, Postgre
SQL, Oracle, Sybase, Informix, and Microsoft SQL Server.
 PHP is pleasingly zippy in its execution, especially when compiled as an Apache
module on the Unix side. The MySQL server, once started, executes even very
complex queries with huge result sets in record-setting time.
 PHP supports a large number of major protocols such as POP3, IMAP, and
LDAP. PHP4 added support for Java and distributed object architectures (COM
and CORBA), making n-tier development a possibility for the first time.
 PHP is forgiving: PHP language tries to be as forgiving as possible.
 PHP Syntax is C-Like.

2. MySQL
MySQL is a database, widely used for accessing querying, updating, and
managing data in databases.
MySQL is an open source RDBMS that relies on SQL for processing the data in
database. MySQL provides APIs for the languages like C, C++, Eiffel, JAVA, Perl, PHP
and Python. MySQL is most commonly used for web applications and for embedded
applications and has become a popular alternative to proprietary database system because
of its speed and reliability. MySQL can run on UNIX, Windows and Mac OS.

Project Analysis and Planning

The BMS is critical to set-up online order, customers to browse through book categories.
This is a small scale project for BMS. The basic idea is that the customers can buy a book from
anywhere during any time by the cash through.

Prepared By : Pragya Chandrakar 9|Page

User

 User can Register, Login, Logout the system.

 View different categories and by books.
 Contact with Admin
 Add Books to Cart
 Order Books

Functionality
 One or more user visit web page at a time.

Usability

 In any browser run this webpage.

Performance

 It performs the webpage as per User’s operating system.

Admin

 Admin can manage system.

 Provide books.

Functionality

 Admin can insert a book or manage the records.

Prepared By : Pragya Chandrakar 10 | P a g e

 Chapter 3
System Design
3.1 Over All System Design Using Designing Tools
The Purpose of Design Phase is to plan a solution for problem specified by the
requirements. System Design aims to identify the modules that should be in the system, the
specification of those modules and how they interact with other to produce the results. The goal
of the design process is to produce a model that can be used later to build that system. The
produced model is called design of the system.

System Design is the process of defining the architecture, components, modules,

interfaces and data for a system to satisfy specified requirements.

Normally, the design proceeds in 2 stages:

 Physical Design
 Database Design

Physical Design
The Physical Design is a graphical representation of a system showing the system’s
internal and external entities and the flow of data into and out of these entities. An internal
entity is an entity within the system that transforms data.

To represent the Physical Design of the system, we use diagrams like Data Flow
Diagrams, E-R Diagrams, Use Case Diagrams, etc…

1. Data Flow Diagram

The Data Flow Diagrams (DFD) is a graphical representation of the flow of data
through an information system. Data Flow Diagrams are used by systems analysis to
design information processing systems but also a way to model whole organization. The
main merit of DFD is that it can provide an overview of what data a system would 1st
Level DFD (Website Flow Diagram)
Prepared By : Pragya Chandrakar 11 | P a g e
  Flowchart Diagram

(Figure 6 : BMS Flowchart Diagram)

Prepared By : Pragya Chandrakar 12 | P a g e

  User Flow Diagram

(Figure 7 : User Flow Diagram)

Prepared By : Pragya Chandrakar 13 | P a g e

 2. Use Case Diagram
A use case is a set of scenarios that describing an interaction between a user and a
system. A use case diagram displays the relationship among actors and use cases. The
two main components of a use case diagram are use cases and actors.

(Figure 8 : Use Case Diagram Symbols)

An actor is represents a user or another system that will interact with the sys

Item you are modeling. A use case is an external view of the system that
represents some action the user might perform in order to complete a task.

Prepared By : Pragya Chandrakar 14 | P a g e

  User Use Case Diagram

(Figure 9 : User Use Case Diagram)

Prepared By : Pragya Chandrakar 15 | P a g e

  BMS Use Case Diagram
BOOKSTORE MANAGEMENT SYSTEM
View Product

Order

Login

User

Add to Cart

Admin
Register

Add Cat, Books

Visitor Delete Cat, Books

Delete User

(Figure 10 : BMS Use Case Diagram)

Prepared By : Pragya Chandrakar 16 | P a g e

 3. E-R Diagram
Entity-Relationship Diagram is a graphical representation of entities and their
relationship to each other. It describes how data is related to each other. An entity is a piece
of data- an object or a concept about which data is stored. A relationship is how the data is
shared between entities.

In E-R Diagram, there are 3 main components:

Symbol Name Description

Entity An Entity can be any object, place,

person or anything.

Attribute An Attribute describes a property or

characteristics of an entity

Relationship A Relationship describes relation

between entities.

(Figure 14 : E-R Diagram Symbols)

Prepared By : Pragya Chandrakar 17 | P a g e

  E-R Diagram for Bookstore Management System

city e-mail

password con-no

name date

id Customers Buys id

name
name
image
id price

Cart BMS
Books image
qty Contai
ns

Cat..
price

Has
Man desc
y

Category

id name

(Figure 15 : E-R Diagram for Bookstore Management System)

Prepared By : Pragya Chandrakar 18 | P a g e

Prepared By : Pragya Chandrakar 19 | P a g e
 1. Book Details (Before Login)

Book Detail for Visitors.

Visitors Can’t add Books to Add to Cart.

(Figure 18 : BMS Book Details)

Prepared By : Pragya Chandrakar 20 | P a g e

 2. Visitor Login Page

Login Page for Viewers.

(Figure 19 : BMS Login Page)

Prepared By : Pragya Chandrakar 21 | P a g e

 3. Register Page

Register Page for Viewers.

(Figure 20 : BMS Register Page)

Prepared By : Pragya Chandrakar 22 | P a g e

 4. Cart Page

(Figure 22 : BMS Cart Page Viewers)

Prepared By : Pragya Chandrakar 23 | P a g e

 5. Order Page

Only Cash On Delivery is Available for Orders.

(Figure 23 : BMS Order Page)

6. Add to Cart (Logged In)

Users Can add books to add to cart.

Details of books and price.

Click Recalculate to Qty, Rate and Total will Calculate.

Users can order Books.

Prepared By : Pragya Chandrakar 24 | P a g e

 (Figure 26 : BMS Users Cart Page)

Prepared By : Pragya Chandrakar 25 | P a g e

 7. Search Books

Book Search Feature.

Search
Books

(Figure 27 : BMS Search Books)

8. Admin Login Page (New Template)

(Figure 28 : BMS Admin Login page)

Prepared By : Pragya Chandrakar 26 | P a g e

 4.2.3 Registration Details

Username EMPTY Password EMPTY

Full Name EMPTY Security Answer EMPTY
Expected Result :

 If fields empty then gives a error for fill up fields

 If password or username does not exist then gives error for valid detail.
 If password is < 8 characters then it will gives error.

4.2.4 Order Details

Full Name Address Contact Number EMPTY

Expected Result :

 If fields empty then gives a error for fill up fields

 If contact number is not Numeric then gives error

Screen-Shots
1. User Login

(Figure 39 : Test Cases 1)

Prepared By : Pragya Chandrakar 27 | P a g e

 2. Admin Login

(Figure 40 : Text Cases 2)

3. Add Book

(Figure 41 : Text Cases 3)

Prepared By : Pragya Chandrakar 28 | P a g e

 4. User Registration

(Figure 42 : Text Cases 4)

Prepared By : Pragya Chandrakar 29 | P a g e

 Chapter 5
Conclusion
Conclusion

 At the first look we can say that Bookstore Management System is a perfect system but it
has many limitations that are as follow :
 This is also used for list the category and books also manage the customer and books of
the Bookstore.
 The Bookstore Management System is used to give information of the Books to the
customer.
 We faced problems like Database creation, Flow of our system, designing of front end
and back end tools, coding etc.
 Only single user can use a system at a time.
 In this system we cannot add a service module.
 We learnt new languages like jQuery, PHP, Boot-Strap, HTML, CSS, etc..

5.1 Limitation of system

 Help

Currently the help feature is not available. Using this functionality user can get
help about the system.

 Payment

Currently the feature of online payment is not available. User cannot give
payment online.

 Multilingual

Multilingual is not supported in our system. Therefore user cannot work in

different languages.

 Backup & Recovery:

User cannot take the backup or recover the data in this the system.

Prepared By : Pragya Chandrakar 30 | P a g e

5.2 Future Scope of the System

 Help module

Using this module user can get help on how to access the system. All
functionalities of system are described in this module. And user can easily access the
entire module using this feature.

 Online payment module

User can do their payment online using this functionality. In future we will add
the online payment for make payment easier for the user.

 Multilingual

In this system we will add the multilingual therefore user can work in different
languages and understand easily.

5.3 Bibliography
Websites Used
o www.google.com

o www.w3cschools.com

o www.stackoverflow.com

o www.quora.com

o www.Scribd.com

Apps Used

 Youtube

 Solo Learn

 Udemy..

Prepared By : Pragya Chandrakar 31 | P a g e