Shri Shivaji Shikshan Prasarak Mandal’s

Loknete Ramdas Patil Dhumal

ARTS, SCIENCE & COMMERCE COLLEGE,
RAHURI.
A Project Report On

“Book Store”
Submitted in partial fulfillment of the requirement of Department of

Bachelor Of Computer Application,

As laid down by the University Of Pune.

During academic year 2023-2024

SUBMITTED BY

VRUSHALI PAWAR

SAKSHI GULDAGAD

SUBMITTED TO
University Of Pune

2023 – 2024

Under Guidance of

Prof. Adhav P. B.
ID.NO.PU./AN/ASC/021/ (1978 ) PRINCIPAL
SENIOR COLLEGE CODE NO:-124 Dr. ANITA VETAL
(MA, B.Ed, PHD)

This is certify that,

VRUSHALI PAWAR
SAKSHI GULDAGAD
Has satisfactorily completed assigned project of BBA[CA] sem VI on
“Book Store” as laid down by the University of Pune for the academic
2023-2024.

His/her
His / Her performance performance is
is ________________________

Internal Examiner External Examiner HOD

(Prof. Dhage S.P.) (Prof.Shalake M.)

2
SR NO TITLE PAGE NO.

1. Acknowledgement 4
2. Abstract 6
3. Introduction 8
3.1 Objective and Goal 9
3.2 Literature Survey 10
3.3 Project Scope and Limitation 12
4. System Analysis 13
4.1 Existing System 14
4.2 Scope and Limitation Of Existing System 15
4.3 Requirement Analysis-Functional Requirement, 16
Performance Requirement, Security Requirement

5. System Design 20
5.1 Design Constraint 21
5.2 Data Model 24
5.3 System Model 26
5.4 User Interface 37
6. Implementation Details 43
6.1 Hardware Specification 44
6.2 Software Specification 44
7. Output And Report Testing 45
7.1 Black Box Testing and Data Validation Test Case 46
7.2 White Box Testing and Data Validation Test Case 47
8. Conclusion and Recommendation 49
9. Future Scope 51

10. Bibliography and Reference 53

3
ACKNOWLEDGEMENT

4
 ACKNOWLEDGEMENT

Before going further to the project details, I would like to thank

those peoples who have helped in many ways for successful completion
of this project.
We would like to thank our internal guide Prof. Dhage S.P. and
head of department Prof. Shalake M. For the constant encouragement
and assistance they provide us at every stage of the project.
They have spent their valuable time for us, suggested necessary
changes and point out the limitations of my system.
I would also like to express my deep gratitude to my parents
whose love and blessings have been a source of inspiration for me.

5
ABSTRACT

6
 ABSTRACT

The main objective of this system is easy to use, reliable or secure. online
book ordering system is one of the most innovative ideas of this centuary.
This system actually save the time of customer’s.
It would make searching, viewing and selection of a book easier.
This system is a computerized system. This system are also provides a
Best services, discounts, category, features, login & registration. To order
book, the user just have click on the order now button provided. Storing data
easier
It will able to check any report at any time.

7
INTRODUCTION

8
 OBJECTIVE AND GOALS
Objective:-
 The main objective of this system is to reduce the manual work for managing the books,
stocks, and bill.

 It tracks all the details about the customer , order, payment.

 Introduce new services.

 Save peoples time and efforts.

Goals:-
 Increase customers by giving pleasuring experience to them.
 To increase your system more by increasing customers.

9
LITERATURE
SURVEY

10
 FACT FINDING TECHNIQUE
We are four fact-finding techniques in the system analysis.
1. Questionnaires
2. Interview
3. Record Review
4. Observation

1. Questionnaires

We used this technique in the initial and final phase of my project. We conducted
this session by asking document to the customer of the in the initial phases we
prepared verification in customer then loan assign to a customer to get some basic
information about the current system. We could find out the work structure of the
organization.
And it’s functioning. In the final stages we used the customer bank details and
financial condition to get some numerical data that was required or was missing
after all the observations.
Asked were both open ended and close ended, which were related to user.
Interaction with current system, updating and rules for record maintenance, reports
generated by current system complications in the system as per use.

2. Interview

We used this technique frequently in the system analysis after customer

verification. The limited in our college related activity with the project. We them
many times. This helped us understand all the stages involved in activity

3. Observation

While finding the facts we keenly observed all the activities in the organization.
We paid attention to the transaction, usage of files and documents, the record
keeping and the handling of the queries in the existing system. Observation helped
us in finding out the actual way of functioning apart from the ideal or desired. This
helped us majority in the interface design.
11
 PROJECT SCOPE AND LIMITATION
Scope:-

 To provide great discount over purchasing.

 This system will help to reduce user’s searching time.

 Good platform for customer to find books as per there budget.

 On this system, the customers can contact us if they have any query.

Limitations:-

 Only cash on delivery, no online payment is available.

 Doesn’t keep track of order.

12
 SYSTEM
ANALYSIS

13
 EXISTING SYSTEM

 No automatic backup facilities available.

 Lack of security of data.

 Difficult to maintain new record.

 It is time consuming process.

 Difficult to maintain.

14
SCOPE AND LIMITATION OF EXISTING
SYSTEM

Limitations:-

 Time consuming:
As the records are to be manually it consume a lot of time.

 Paper work:
Lot of paper work is involved as the records are maintained in the files and
register.

 Storage requirement:
As files and register are used the storage requirement is increased.

 Difficult in keeping new records:

It is difficult for keeping all the new entries of the books, their updates,
review, feedback etc.

 Accuracy:
As the system is in manual, there are not many chances of human error.
these cause error in calculating mechanism or maintaining products and
supplier data in register.

15
REQUIREMENT
ANALYSIS

16
 Functional Requirement

 Keeping records of visited of customers.


 Keeping the records of books.

 Keeping the daily sale.

 Sorting the books selected by the customer in the temporary storage.

17
 Performance Requirements

 A powerful server: A large number of the html puts a lot of load on

the server it is imperative that server must be powerful enough.

 Hard disk: A good hard disk (fast and big) is essential for a serve.

18
 System Requirements

 The system wants a minimum of two GB of ram to run all the options sleek
and unforeseen.
 It wants a minimum 1.3 gigahertz processor to run sleek as but which will
produce issue.
 The system must be operated by some approved person as wrong hands will
p r oduce issue.
 Rest is all up to the user’s usage can take care of the hardware.
 For security opposing virus is suggested.

19
SYSTEM DESIGN

20
 DESIGN CONSTRAINT

FEASIBILITY STUDY

Feasibility Study refers to the determination that it is possible to automate

the existing system. Feasibility study forms the most important phase in the system
development life cycle so that the people who are affected by the system benefit
from the change. This involves some very crude estimates of schedules of
completion of the proposed system and the cost of the system. This study ensures
that the system meets the objectives of the organization before it can be approved
for development. It also involves the study of different risks involved in
developing the system.

The major areas to consider while determining the feasibility of a system are:-

1. Technical Feasibility.

2. Operational Feasibility.

3. Economical Feasibility.

21
 1.Technical Feasibility

It is the study of functions, performance and constraints .That may affect the
ability to achieve an acceptable system. The issues raised during technical
feasibility were

1. Does proposed equipment have technical capacity to hold data

required to use the new system?

2. Will proposed system provide adequate responses to inquires,

regardless number and location of user?

3. Can system be expanded if developed?

4. Are there any technical guarantees of accuracy, reliability, ease of

access and data security? Discussing the above mentioned points
we found system to technically feasible as existing equipment
were cable to handle system.

5. Data can be added to existing system and system can provide

feature of Accuracy, reliability, data security and ease of access.

2.Operational Feasibility

Operational feasibility refers to the determination that whether the system

will operate and hence used by the end user or not.
Our input screens are familiar with their existing data processing environment,
as we have checked acceptability of users for the input screens frequently.
In the proposed system we don’t require lots of work. One or two days
training is sufficient to train the Administrator of this system. As system is very
user friendly, they have lot ease at work.

22
 3.Economical Feasibility

A system to be developed should be hotel management system. In

general economical feasibility includes cost benefit analysis. The main point
discussed by me during developing the system were.

1. Cost of developing system.

2. Cost of hardware and software.

3. Costs of manpower handle the system.

The proposed system will require new hardware and software setup, and for
the Administrator (user) it will require to give the initial training. The proposed
system is economically feasible because it will save valuable time, money and it is
more stable.

23
DATA MODEL

24
 ENTITY RELATIONSHIP DIAGRAM (ERD)
Cnm Name Password

Email

Customer Has Registration

Password

Email
Id
Pays Bill

Paid by
Id
Search
amount

manage To

Bid

Bnm
Books
ship Admin
Price

Author
Has

Quntity

Login
Place Order

Cname
Oid Price

25
SYSTEM MODEL

26
 CONTEXT LEVEL DIAGRAM

0000
0.0
0.0
Personal details Registration Customer
Customer
Book
Store
Manage whole system Report
Admin Admin

27
 DATA FLOW DIAGRAM (1st LEVEL)

1.0

Customer Personal Details Registration Details Customer

2.0
Customer
Customer Id, password Login login

3.0

Customer Search cake Search

Book Book

4.0

Customer Add to Cart

Cart

28
 5.0

Customer Placed order Order Order

6.0

Customer Address Confirm Order

Order

7.0
Payment
Customer Pay
amount

8.0

Customer Id, password

Logout Customer

29
Admin side:
1.0
1.0
Id, password Admin
Admin
Login

Insert cakes 2.0

Admin Books
Manage
Store

3.0
Admin Price Manage Price
Check
price

Order info.
Admin 4.0
Order
Manage
Order

5.0
Accept payment
Admin Payment
Accept
payment

30
Admin Admin
6.0

Logout

31
 CLASS DIAGRAM

Customer Admin
-name: string
-name: string
1..* -id: integer 1…* 1
-address: string -email: string
1 -address: string
+login ( ): void +manage product ( ): void
+register ( ): void + manage details ( ): void
+register( ):void
1...* 1

1..* 1…*
1...*
Order
Books
-name: string
-name: string
-id: integer
-price: integer
-author: string 1…* 1…* -address: string

+order details ( ): void

+search book ( ): void
+manage order ( ): void
+buy book ( ): void
1
1…*

1
Cart Payment
-cname: string -payment details: string
-cid: integer -amount: integer
-address: string -date: integer
1…*
+delete ( ): void +accept payment ( ): void
+update ( ): void +display payment ( ): void

32
 OBJECT DIAGRAM

C: Customer A: Admin

1..* +name=”abc” 1…* 1 +name=”abc”

+id=1 +email=”abc@gmail.com”
+address=”abc” 1 +address=”abc”

1..* 1

1..* 1..*
B:Book 1…* O: Order

+name=”abc” +name=”abc”
+price=500 1…* 1…* +id=12
+author=”abc” +address=”abc”

1..* 1…*

1 1…*

C1:Cart P: Payment

1…* +cname=”abc” +payment details=”abc”

+cid=123 +amount=500
+address=”abc” +date=16-9-2023

33
USECASE DIAGRAM
Book Store

Login

Search book

View book

Customer Add to cart

Order book

Payment

Check details

Confirm orders

Add books

Admin Update books

Delete books

34
 SEQUENCE DIAGRAM

C:Customer A:Admin B:Book P1:Payment

1.Login

4. 2. Authenticate

3.Book Request 4.Request

6.Book 5.Responce

7 .Add to cart

8. Order

9.Order successful

10.Payment

35
 COLLABORATION DIAGRAM

3. Book Request
1.Login

C:Customer A:Admin
2.Authenticate
11.Order successful
5.Responce
12. Payment 7.display book
10.Order 4.Request
6. Search book
8. Add to cart
9.order request

B1: Bank B: Book

36
 ACTIVITY DIAGRAM
Customer Admin

Registration Check

Valid invalid
Search book

Check book

View book Available unavailable

Add to cart Confirm order

Payment

37
STATECHART DIAGRAM

Register

Registration successful

Search book

Book available

Add to cart

Added to cart successfully

Order book

Order confirmed

Payment

38
 COMPONENT DIAGRAM

View classes
Home page

Register Payment

Add to
Search Cart Order
Book Book

Book store class

Customer Admin

Access database

Access
database

39
DEPLOYMENT DIAGRAM

Client Book
Server Server

Database
Server

40
USER INTERFACE

41
INDEX PAGE

42
NEW BOOK PAGE

43
LOGIN PAGE

44
REGISTRATION PAGE

45
USER PAGE

46
IMPLIMENTATION
DETAILS

47
HARDWARE AND SOFTWARE SPECIFICATIONS :

Hardware Specification :

 Pentium IV 1 GHz with at least 2 GB of RAM.

 CD-ROM with 32 bit driver.
 At least 5 Gigabytes free space on hard disk.
 Color monitor.
 Keyboard.
 Mouse.
 Printer.

Software Specification :

 Windows10 Operating System.

 Java
 Chrome
 Eclipse EE
 Maven

48
OUTPUTAND REPORT
TESTING

49
 BLACK BOX TESTING AND DATA
VALIDATION TEST CASE
Test case for login module:

Steps carried out Test Data Expected result Actual result

1. Enter user type user type should display warning should display warning
And press login message please enter all message please enter
button the fields all the fields

2. Enter user name user name should display warning should display warning
and press login message please enter message please enter
button the password the password

3. Enter password password should display warning should display warning

and press login message invalid email message invalid email
button and password and password

4. Enter user name, user name=” show username show username

Password and “password=” password password
Press login button “

5. Enter user name, user name=” show username show username

Password and “password=” password password
Press login button “

50
 WHITE BOX TESTING
AND FUNCTIONAL VALIDATION TESTING

Login:

Test Engineer Vrushali Pawar

Test Case ID 1

Date 06/12/2023

Purpose The purpose of this test in sure that the user can login with his id
Use this app.
.
Pre requirement The customer enter his correct name and password for a successful
Login page email id , password.

Test data Email id, password 1.Visit Login page

2. Enter username
3. Enter password
4. Click login button

Status Pass

51
Registration:
Test Engineer Sakshi Guldagad

Test Case ID 2

Date 06/12/2023

Purpose The purpose of this test for register customer by his name

.
Pre requirement The customer sure that login with his name, id use this app.

Test data Name, password, email 1.Visit registration page

2. Enter customer name
3. Enter customer email
4. Enter customer password

Status Pass

52
 CONCLUSION AND
RECOMMENDATION

53
Conclusion:

 The system provides excellent features.

 User can operate this system very easily.

 This is best way for ordering book.

 Reduce workload.

 Provide data security.

54
FUTURE
SCOPE

55
Future Scope:

 Detailed information about Help & Printing code will be given in future

 We will try to make it mobile application in future.

 Centralized Database.

 Providing run time help to user.

 These systems modules can be also develop in other language.

56
BIBLOGRAPHY AND
REFERENCE

57
Bibliography:

1. Software Engineering :
- Manisha Kumbhar

2. YouTube
3. www.google.com

WWW.W3SCHOOL.COM

58