A Project Report on

“Online book store management system”

Submitted By:
Vaijanath Prakash Mutkule (23510290045) (22369)
Kunal Ravindra Ghatol (23510290076) (22370)

Sandip Sanjay Pappulwar (23510290046) (22371)

Guided By:
Prof.P.P.Deshpande
Submitted To:
DEPARTMENT OF COMPUTER ENGINEERING

1
GOVERNMENT POLYTECHNIC HINGOLI
Fourth Semester
(Year: 2023-24)
Micro Project

Software Engineering (SEN) (22413)

Title of the Project: Online Book Store Management System

Program: Computer Engineering (CO4I)

Members of the Group:
1. Vaijanath Mutkule Roll No : 22369

2. Kunal Ghatol Roll No : 22370

3. Sandip Pappulwar Roll No : 22371

2
Maharashtra State Board of Technical Education, Mumbai

CERTIFICATE
This is to certify that,
Mr.Vaijanath Mutkule, Kunal Ghatol ,Sandip Pappulawar
Roll No: 22469, 22470, 22471 of Fourth Semester of Diploma in Computer
Engineering of Government Polytechnic Hingoli has completed the Micro Project
satisfactorily in course Software Engineering (22413) for academic year 2023-24
as prescribed in the curriculum.

Place: Hingoli Enrollment No : 23510290045

23510290076
23510290046

Date : / /2024

Course Coordinator HOD Principal

Institute seal

3
 MAHARASHTRA STATE BOARD OF TECHNICAL EDUCATION, MUMBAI
MICRO PROJECT
Progress Report/Weekly Report
Name of the Project:Online Book Store Management System

Course:SEN (22413)

Program: Computer Engineering (CO4I) Roll No: 22469, 22470, 22471

Week Date Duration Work/ Activity Performed Sign of the

No in Hours Faculty

1 03/01/24 1/2 Collection information about online book store

management system
2 04/01/24 1/4 Making the SRS i.e function requirement
and non functional requirement
3 11/01/24 1 Making the use case diagram for our project
4 16/01/24 ½ Making the DFD diagram for our project
5 20/01/24 ½ Making the ER diagram for our project
6 4 Making the Class Diagram, Sequence Diagram,
22/01/24 collaboration Diagram, State Tansition
Diagram for our project
7 25/01/24 2 Preparing Test Cases to Validate Requirements
for our Project
8 28/01/24 2 Preparing RMMMA Plan for our Project
9 03/02/24 2 Preparing the project report format
10 07/02/24 1 Adding the collected information in the report
11 10/02/24 1/4 Adding the diagram in the report
12 20/02/24 1 Making final changes in the report
13 29/02/24 2 Reviewing the report again and eliminating the
mistakes
14 03/03/24 1/2 Rechecking the project with guide
15 05/03/24 1 Finalizing the Micro-Project
16 / 03 /24 Submitting report to the teacher

4
 Teacher Evaluation Sheet for Micro Project
Course Title and Code: - Software Engineering (22413)

Project Tital of the : - Online Book Store Management System

Group No: -

COs addressed by the Micro Project:

CO a: Select suitable Software Process Model for software development

CO b: Prepare Software Requirement Specifications

CO c: Use software modeling to create data designs

CO :

CO :

Marks:-

Marks obtained
Marks for by the
Group Work individual Total
Roll No. Name Of Student
(06) based on viva Marks
(04) (10)

22369 Vaijanath Mutkule

22370 Kunal Ghatol

22371 Sandip Pappulwar

Name and designation of Faculty Member: Prof. P.P. Deshpande

Computer Engg. Department

Signature:

5
Action plan: -

Sr.No Details of activity Planned Planned Name of

start date finish date responsible
team member
1 Collection information about online 30/01/24 10/01/24 Vaijanat Mutkule
book store management system
2 Making the SRS i.e function Sandip
requirement and non-functional 10/01/24 17/01/24 Pappulwar
requirement
3 Making the use case diagram for our 17/01/24 24/01/24 Kunal Ghatol
project
4 Making the DFD diagrams for our 24/01/24 31/01/24 Vaijanat Mutkule
Project
5 Making the ER diagram for our project 31/01/24 07/02/24 Sandip
Pappulwar
6 Making the Class Diagram, Kunal Ghatol
Sequence Diagram, collaboration 31/01/24 07/02/24
Diagram, State Transition Diagram
for our project
7 Preparing Test Cases to Validate 07/02/24 21/02/24 Vaijanat Mutkule
Requirements for our Project
8 Preparing the project report format 28/02/24 29/02/24 Kunal Ghatol

9 Adding the collected information in 01/03/24 02/03/24 Vaijanat Mutkule

the report
10 Making final changes in the report 03/03/24 04/03/24 Kunal Ghatol

11 Rechecking the project with guide 04/03/24 05/03/24 Sandip

Pappulwar
12 Finalizing the Micro-Project 05/03/24 06/03/24 Kunal Ghatol

13 Submitting report to the teacher __/03/24 __/03/24 All Members

6
Resour Required:-

Name of the Resources Specification Quantity Remark

SR.
No.

1 Computer System 1
4GB RAM,1 TB HDD,
AMD processor with
Windows 10 OS

2 MS Office, MS Excel 2019

Actual Procedure Followed: -

1. Collecting information about online book store management systeam

2. Making the SRS i.e. Function requirements and Non Functional requirements.
3. Making the Use Case Diagram of for project online book store management
4. Making the DFD diagrams for our Project
5. Making ER Diagram of our Project
6. Making Class Diagram, Sequence Diagram, Collaboration Diagram, State
Transition Diagram for our Project
7. Preparing Test Cases to Validate Requirements for our Project
8. Preparing the project report format
9. Adding the collected information in the report
10. Making final changes in the report
11. Rechecking the project with guide
12. Finalizing the Micro-Project
13.Submitting report to the
teacher

7
 ACKNOWLEDGEMENT
It is my great pleasure to acknowledge my research guide Prof. P. P. Deshpande lecturer in
Government Polytechnic, Hingoli, His valuable guidance, constant inspiration, unending
support helped me a lot of focus my views in proper perspective.

I would like to express my sincere gratitude to Prof. N.S. Jadhao for their invaluable
guidance, support, and encouragement throughout this project. Their expertise, insight, and
advice have been instrumental in helping me to overcome challenges and achieve success. I
am truly grateful for their leadership and mentorship, which have been essential to my growth
and development as a professional. Thank you for your unwavering commitment to
excellence and for being an inspiration to us all.

Our sincere and whole hearted thanks Prof. B. P. Deosarkar, principal Government
Polytechnic, Hingoli for inspiring us to achive highest goal.Last but not least I am also
thankful to my parents and friends who helped me a lot in finalizing the project within limited
time frame.

Thank You.

8
 Abstract

This project is a web based application, designed to help the students to select books through
online system.It helps the Student to select available books. It has an easy to understand
interface which helps the Students to check for books. The books will be ordered into an
economy, premium and so forth. Based on a type of book required by the client, the client will
have able to make bookings. The main objective of the project is to create an online book store
that allows users to purchase books online based on title, Author and subject. It helps the clients
to select for available books and place the order of books. The selected books are displayed in a
tabular format and the user can order their books online through credit card and debit card
payment. Online Book store is an online web application where the customer can purchase
books online. The user can login using his account details or new customers can set up an
account very quickly. They should give the details of their name, contact number and address
for shipping. The Administrator will have additional functionalities when compared to the
common user. He can add and delete and update the book details.

9
 INDEX
Sr. No. Chapter Names Page No.

1 Introduction 12

2 Software Requirement Specification 13

2.1 Functional Requirements 13

2.2 Non-Functional Requirements 15

3 Use case Diagram 16

4 Activity Diagram 17

5 DFDs 18

5.1 Level 0 DFDs 18

5.2 Level 1 DFDs 19

5.3 Level 2 DFDs 20

6 ER Model 21

7 Class Diagram 22

8 Sequence Diagram 23

9 Collaboration Diagram 24

10
10 Advantages And Disadvantages 25

10.1 Advantages 25

10.2 Disadvantages 27

11 Conclusion 29

12 Future Scope 30

13 Reference 31

11
 Introduction
The Online Book Store is being developed for customers so that they can order their books.
This application takes information from the customers through filling their details. A
customer being registered in the website has the facility to place an order on books which he
require. Online Book Store, It helps the users for available books view profile and place the
books including number of copies. It has a user-friendly interface which helps the user to
check for books and order them. They could also make payment online. Based on the subject
of books required by the customer, the user shall be able to make order. The use of internet
technology has made it easy for the customers to buy books based on his requirement at any
time. This Online Book Store System makes the order easy. It saves time. The tool shall give
the user for information such as the date and time of their order. Also, it will need an
identification number.

Using these details, the tool shall help the customer to order books.

12
 2.Software requirement specification
This system provides an easy solution for customers to buy the product without going to the
shop and also to seller to sale the product. This proposed system can be used by any naïve
user and it does not require any educational level, experience or technical expertise in
computer field but it will be of good use if user has the good knowledge of how to operate a
computer.

2.1 Functioonal Requirement:

1. User Authentication and Authorization:

- The system must allow users to register, login, and manage their accounts securely.

- Different user roles (admin, staff, customer) must have appropriate permissions and access
levels.

2. Product Management:

- Admins should be able to add, edit, and remove books from the inventory.

- Each book entry should include details like title, author, genre, ISBN, price, quantity, etc.

- The system should support categorization and tagging of books for easy browsing.

3. Order Management:
- Customers should be able to add items to their shopping cart and proceed to checkout.

- Admins should have access to order details, including order history, status, and tracking
information.

- Automated email notifications should be sent to customers upon order placement, shipment,
and delivery.

4. Inventory Management:
- The system should track real-time inventory levels and update them upon each purchase.

- Admins should receive alerts for low stock levels and be able to replenish inventory.

5. Payment Processing:
- Integration with secure payment gateways for processing online payments securely.

- Support for various payment methods such as credit/debit cards, PayPal, etc.

13
 6. Customer Relationship Management (CRM):
- Capture and store customer information, including contact details, purchase history, and
preferences.

7. Search and Filtering:

- Users should be able to search for books based on various criteria like title, author, genre, etc.

- Advanced filtering options to refine search results based on price range, publication date, etc.

8. Reporting and Analytics:

- Generate reports on sales performance, popular products, revenue trends, etc.

- Utilize analytics to identify customer behavior patterns and market trends.

9. Shipping and Fulfillment:

- Integration with shipping carriers for calculating shipping costs and generating labels.

- Automated order fulfillment processes to streamline shipping operations.

10. Customer Support:

- de channels for customer Provisupport such as live chat, email, or ticketing system.
- Allow customers to track their orders and contact support for any queries or issues.

11. Website Management:

- Content management system (CMS) for updating website content, banners, promotions, etc.

- Ensure responsiveness and usability across various devices and screen sizes

12. Security and Compliance:

- Implement robust security measures to protect user data and financial transactions.

- Compliance with data protection regulations such as GDPR, CCPA, etc.

14
2.2Non Functional Requirement:
1. User interface:

-The system should have a user-friendly interface for easy navigation and use.

2. Data security:
-The system should protect data and ensure the privacy and confidentiality of library patrons
and their information.

3. Accuracy:
-The system should accurately provide real time information taking into consideration various
concurrency issues.

4. Performance:
-The system should be able to handle large amounts of data and refresh information at regular
intervals.

5. Inventory management:
-The system should include a complete inventory management facility to store and track stock
of books for the on-line bookstore. It should also have a facility to receive and add books to
the inventory.

15
3. Use Case Diagram
An interaction between a user and a system is described by use case diagram. Use case
diagrams describe what a system does from the standpoint of an external observer. The
emphasis is on what a system does rather than how. Use case diagrams are closely connected
to scenarios. A scenario is an example of what happens when someone interacts with the
system. A use case diagram is a collection of actors, use cases, and their communications. For
initial development we can use this use case.

Fig: Use case diagram

16
 4. Activity diagram

The activity diagram used to describe flow of activity through a series of actions. Activity diagram
is a important diagram to describe the system. Activity diagram is basically a flowchart to
represent the flow from one activity to another activity. The activity can be described as an
operation of the system. The control flow is drawn from one operation to another. This flow can be
sequential, branched, or concurrent.

Fig: Activity diagram

17
 5. DFDs

In Software engineering DFD(data flow diagram) can be drawn to represent the system of
different levels of abstraction. Higher-level DFDs are partitioned into low levels-hacking
more information and functional elements. Levels in DFD are numbered 0, 1, 2 or beyond.
Here, we will see mainly 3 levels in the data flow diagram, which are: 0-level DFD, 1-level
DFD, and 2level DFD.

5.1 Level 0 DFD:

It is also known as a 0context diagram. It’s designed to be an abstraction view, showing the

system as a single process with its relationship to external entities. It represents the entire

system as a single bubble with input and output data indicated by incoming/outgoing

arrows.

Fig: Level 0 DFD

18
5.2 Level 1 DFD:

A level 1 data flow diagram (DFD) is a general overview of a system's main sub-processes.
It's a more detailed view than a level 0 DFD, which is a context diagram that represents the
entire system as a single process.

Fig: Level 1 DFD

19
5.3 Level 2 DFD:

2 level DFD goes one step deeper into parts of 1-level DFD. It can be used to plan or record the

specific/necessary detail about the system’s functioning.

Fig: Level 2 DFD

20
6.ER Model
An entity–relationship model (or ER model) describes interrelated things of interest in a
specific domain of knowledge. A basic ER model is composed of entity types (which classify
the things of interest) and specifies relationships that can exist between entities (instances of
those entity types). An E–R model is usually the result of systematic analysis to define and
describe what data is created and needed by processes in an area of a business. Typically, it
represents records of entities and events monitored and directed by business processes, rather
than the processes themselves. It is usually drawn in a graphical form as boxes (entities) that
are connected by lines (relationships) which express the associations and dependencies
between entities.

Fig: ER Diagram

21
7.Class Diagram

Class diagram describes the attributes and operations of a class and also the constraints
imposed on the system. The class diagrams are widely used in the modeling of object oriented
systems because they are the only UML diagrams, which can be mapped directly with object-
oriented languages.

Fig: Class Diagram

22
8.Sequence Diagram
A sequence diagram is a type of interaction diagram because it describes how—and in what
order—a group of objects works together. These diagrams are used by software developers
and business professionals to understand requirements for a new system or to document an
existing process. A sequence diagram shows, as parallel vertical lines (lifelines), different
processes or objects that live simultaneously, and, as horizontal arrows, the messages
exchanged between them, in the order in which they occur. This allows the specification of
simple runtime scenarios in a graphical manner.

Fig:Sequence Diagram

23
9.Collaboration Diagram
A collaboration diagram, also known as a communication diagram, is an illustration of the
relationships and interactions among software objects in the Unified Modeling Language
(UML). Developers can use these diagrams to portray the dynamic behavior of a particular
use case and define the role of each object. To create a collaboration diagram, first identify
the
structural elements required to carry out the functionality of an interaction. Then build a model
using the relationships between those elements.

Fig: Collaboration Diagram

24
10.Advantages and Disadvantages

10.1 Advantages:
1. Global Reach: With an online platform, bookstores can reach customers beyond their
local area, expanding their customer base to a global scale without the constraints of
physical storefronts.

2. 24/7 Accessibility: Online bookstores are accessible 24/7, allowing customers to

browse, shop, and make purchases at their convenience, regardless of time zone or location.

3. Increased Sales Opportunities: By reaching a wider audience online, bookstores have

the potential to increase sales and revenue compared to traditional brick-and-mortar stores.

4. Reduced Overhead Costs: Operating an online bookstore typically incurs lower

overhead costs compared to maintaining physical stores, such as rent, utilities, and staffing
expenses.

5. Efficient Inventory Management: Online bookstore management systems enable

realtime tracking of inventory levels, facilitating efficient stock management, reducing
overstock or stockouts, and minimizing storage costs.

6. Personalized Customer Experience: Online platforms allow for personalized

recommendations based on customer browsing and purchase history, enhancing the
shopping experience and increasing customer satisfaction.

7. Convenience and Flexibility: Customers can browse a vast selection of books from the
comfort of their homes, avoiding the need to travel to physical stores. They can also choose
from various shipping options for added convenience.

25
8. Data-Driven Insights: Online bookstore management systems provide valuable data and
analytics on customer behavior, sales trends, and inventory performance, enabling informed
decision-making and strategic planning.

9. Marketing Opportunities: Online platforms offer various marketing tools and

techniques, such as email campaigns, social media promotions, and targeted advertisements,
to attract and retain customers effectively.

10. Scalability: Online bookstores can easily scale their operations to accommodate growth
in sales volume and customer traffic, without the limitations imposed by physical space or
geographical constraints.

26
10.2 Disadvantages:
1. Initial Setup Costs: Implementing an online bookstore management system can require
a significant upfront investment in terms of software licensing, hardware infrastructure, and
customization.

2. Technical Complexity: Managing and maintaining the system may require technical
expertise, particularly during the initial setup phase and for ongoing updates and
troubleshooting.

3. Dependency on Technology: The system's reliance on technology means that

disruptions such as server outages, software bugs, or cyberattacks could impact operations and
lead to downtime.

4. Data Security Risks: Storing sensitive customer data, such as payment information and
personal details, within the system exposes the business to potential data breaches and
cybersecurity threats.

5. Integration Challenges: Integrating the system with existing software applications or

thirdparty services, such as payment gateways or shipping providers, can pose compatibility
issues and require additional effort.

6. User Adoption Challenges: Users, including staff members and customers, may
encounter difficulties adapting to the new system, leading to resistance to change and
potential usability issues.

7. Maintenance Overhead: Regular maintenance tasks such as software updates, database

optimization, and security patches require ongoing attention and resources.

8. Customer Support Demands: Providing adequate customer support for technical issues,
order inquiries, and account assistance can be resource-intensive and time-consuming.

27
9. Competition and Market Dynamics: The online bookstore industry is highly
competitive, with constantly evolving market trends and consumer preferences. Keeping up
with competitors and staying relevant in the market requires continuous innovation and
adaptation.

10. Digital Divide: Not all customers may have access to the internet or be comfortable
with online shopping, potentially excluding certain demographic groups from the customer
base.

28
11.Conclusion
The transmition from buying written books in bookshops to ordering them online or even
simply digital versions has had a significant impact on the industry, including retailers and
libraries, as well as the general public throughout the globe. We present application developed
using software engineering methods. Digital Bookstore allows the users to buy as well as
review books line Comers can login and ward for their books, whether it is available or con uf
stock. Users can be give feedback. have implemented and tested the web application to satisfy
the user specifications.

29
12.Future Scope

• Prepare high-level and detailed system design specifications.

• Prepare a test plan as well as test cases.

• Develop the system and write the code.

• Analyze and develop detailed specifications and requirements.
• Unit, integration, and system testing should all be performed.

30
13.Reference List

Books:
1) Robert Cecil Martin (2008) Clean Code: Pearson Education

Websites :

• https://www.javatpoint.com/software-engineering

• https://www.geeksforgeeks.org/software-engineeringintroductiontosoftwareengineering/

• https://en.wikipedia.org/wiki/Software_engineering

• https://www.aplustopper.com/advantages-and-disadvantages-of-e-commerce/

• https://www.uml-diagrams.org/examples/online-shopping-usecasediagramexample.html

31
32