UNIVERSITY OF PUNE

MASTER OF COMPUTER APLLICATION

JSPM NARHE TECHNICAL CAMPUS,NARHE

PUNE-411041
2020-2021

Project Report On -

BookShop Management System

 Group members:-
• 21058_Shubham bhujbal
• 21110_Aniket shete
• 21057_Shradhdha Bhandare
• 21095_Shubhangi patil
• 21068_Nikita Godase
BookShop Management
System
INTRODUCTION

 
1.1 Introduction
• Bookshop Management System is used to keeps the records of
the Customer Sale Bill, Shopkeeper details ,Supplier Details
And Also etc.
• This system is specially designed for regular Bookshop Billing
and Details management .
• This system is handled by ShopKeeper .
• This system is also maintain the Shopkeeper details and their
Customer & Supplier details.
• BookShop involves the production of the Books from the
material as suppiler.
 
1.2 Scope of System
• This system is maintain the Shopkeeper, Customer and their Bill details.
• It is provide security to the user regarding the records and data store.
• It is easy to user to search for Books Details.
• It is very easy to use.
• Time saving.
• Maintain Record.
1.3 Proposed System
• System will generate the Customer Bill, Books price Receipt.
• System is useful for Shopkeeper because reduce workload.
• System is provides facility of maintaining a stock.
• Security is provided in terms of username and password.
• Better Documentation.
• Easy to handle
 
2.ANALYSIS
2.1 Fact Finding Techniques
Fact finding technique is a process to collect information about the system
requirements. There are four kinds of fact finding technique:
1) Interview.
2) Record Review.
3) Observation.
4) Questionnaire.
We have used following techniques:
 INTERVIEW:-
1. Collect information from individuals or groups.
2. To gather qualitative information, opinions, policies, suggestions,
etc
3. Direct communicate with the Shopkeeper, Customer.
4. The responses are quickly received, so quick information in less
time
 QUESTIONNAIRE:-
1.This technique is of asking questions for collecting required
information.
2.We have used few questioned for making our project easier and
simpler.
  RECORD REVIEW:-
1. This technique believes in records than in people.
2. Take place at the beginning of the system study or
later in the study of comparing actual operations with records.
 OBSERVATION:-
1. It usage of files and document of stored reports & informal
communication channels,etc
 
2.2 Feasibility Study

1.The main objective of feasibility study is to test the Technical, Operational

and Economical feasibility of developing a computer system.

2.The feasibility of any system may be viewed from the following three methods:

i. Technical Feasibility Study

ii. Economic Feasibility Study

iii. Operational Feasibility Study

 Economic Feasibility Study
•It is the measure of cost effectiveness of the system. At present the system can use
one person to operate so the labor charge is reduced and other charges for the facility
along with maintenance cost is reduced. Our system is less costly. There is no
restriction for use high level or specific printer for printing bills or records slips. This
system can install any lower cost machines.

 Technical Feasibility Study

•Technical Study is the study of system hardware and software requirement that is
technical requirement of the system. The technical requirement is MS-Access .

 Operational Feasibility Study

•The system is user friendly hence any person in the organization can operate or use
the system. The system can provide correctly & timely information as required by
the organizational personal.
2.3 HARDWARE & SOFTWAR REQUIREMENTS
Hardware :-
Processor :- Intel Core i3 inside”
RAM :- 7.88GB and above
Hard Disk :- 1TBand above
Printer :- Any Printer
Software :-

Operating System :- Windows 10 pro

Front End :- JAVA(jdk1.7)
Back End :- Microsoft Office Access.
 
 
3.SYSTEM DESIGN
 3.1 Entity Relationship Diagram:-
M 1
CUSTOMER Visit BOOK SHOP

M 1

Send
To

1
Pay SALE_BILL

Gener- Has
ate
Purchase

To
SHOP KEEPER

1
To 1 1

Pay Orde
-r To

PURCHASE_B-
ILL

M
M
BOOKS M Supp-
SUPPLIER
ly
M
 3.2 Context Level Diagram:-

0.0
Shop Keeper Details Shop Keeper Details
SHOP KEEPER
SHOP KEEPER
BOOK SHOP
Book Details Book Details
BOOK MANAGEMENT BOOK

Customer Details SYSTEM

Provide Books
CUSTOMER CUSTOMER

Supplier Details Purchase Bill

SUPPLIER SUPPLIER
 3.3-Data Flow Diagram

ShopKeeperDetails ShopKeeperDetails
SHOPKEEPER
1.0 SHOPKEEPER

Book Purchase

SupplierDetails Process OrderToBooks

SUPPLIER SUPPLIER

Boo Details

BOOK
Supplier_Details

SUPPLIER Phurchase Order Details and Book

Details

2.0
Pay_Bill Bill_Receipt
SHOPKEEPER SHOPKEEPER
Book Purchase

Billing PayPurchase
Bill_Details Bill
SUPPLIER Process SUPPLIER

PURCHASE_BILL_DETAILS

A
 A
Shopkeeper Deatils

BOOK

EnquiryForBook 3.0 BookInformation

CUSTOMER s
CUSTOMER

Selling
EnquiryDetails
SHOPKEEPER
BookDetails Process SHOPKEEPER

CUSTOMER
CUSTOMER_DETAIL
DETAILS
S
BOOK_DETAILS

Customer Details & Book Details

Generate Sale Bill to Customer

4.0

CustomerDeatil, SaleBill ProvideBook,

Pay Bill Bill Receipt
Process CUSTOMER
CUSTOMER

CUSTOMER_DEATILS SALS_BILL_DETAILS

BOOK_DETAILS

B
 B

CustomerDetails
BookDetails CUSTOMER
BOOK_DETAILS
5.0
Customer
Supplier
_Details Report
CUSTOMER_DETAILS _Details
SUPPLIER
Generation
SupplierDetails Process ShopKeeperDetails
SUPPLIER_DETAILS
PurchaseBill SHOPKEEPER
_Details
PURCHASE_BILL_DETAILS
SaleBillDetails

SALE_BIIL_DETAILS
 3.4 Object Diagram

w:Walk

start time = 1.30 pm

end time = 3.00 pm

p:Person
b: Book Supplies

name = “Java”
firstName = “NIKI” prince = 1500.00
SurName = “Godase” description = “lanaguade”
getprice = 1300.00

Purchase

time = 5.00 pm
sum= 1000.00
 3.5 Class Diagram

Walk

+star Time
+end Time
*
+pickUp ()
0. . *
+return ()
+end () *
+buy ()
Person 1
Book Supplies
+firstName
+SurName +name
+prince
+creatWalk()
+description
+getprice
*
+pickUp ()
1 +return ()
Purchase
* *
+getprice()
+Time
+summ
+summUp ()
+charge ()
+addSupplies ()
 3.6 Use Case Diagram
GGGGG General Use Case

Manage Books
Info And
Category

Manage and
Count Books
Available

Customer

Admin Manage Sales

and Purchases
of Books

Monitor
Transaction
Recored
 3.7 Sequence Diagram

BookShop Management Book Management Stock Management

Admin | | |

| | | Add/Edit
Add/Edit Add/Edit
Stock
BookShop Book
| | |

| | |
Save/Update
Save/Update
| | | Stock
Book
Manage
BookShop | | |
Save/Update List/Delete
| | |
BookShop Stock
| | |
List/Delete
| Manage | |
Book
| Books | |
| Details | |
| | |
| | |
| | Manage |
| | Stock |
| | Details |
| List/Delete | |
Book
| | |
| | |
| | |
 3.8 Activity Diagram

Start
Check User Level and

Permissions

Check
Check Check
Permission
Permission Permission

Manage Stocks
Manage BookShop Manage Books

END
Exit From the System
 3.9 Component Diagram

BookShop Encryption
Security
Data Access
Access Control
Books
Encryption
Bookshop ----------
Management Data Access Persistance
System ----------

Stock Access Control

Data Access

System Admin of BookShop Database

Management System
 3.10 Deployment Diagram

BookShop

Books DATABASE

ADMIN
4 DataDictionry
Name:- Book Details

Description:-Store Information about of Book Details

Data Type Lenght Description Data Store Constraint

Element
Bid Number 5 A unique Book Details Primary Key
Permanant No
Assiged to the
Book
Bnm Text 20 Assigened to _ Not null
the Book
Name
Bpub Text 20 Assigened to
the Book
Publication
Bqty Text 20 Assighed the _ Not null
Book
Quantity
Bpt Number 10 Assighed the _ Not null
Book Prize
 Name:- Customer Details

Description:-Store Information about of Customer Details

Data Type Lenght Description Data Constraint

Element Store
Cid Number 5 A unique Customer Primary
Permant Deatails Key
Number assigned
to each
Cnm Text 20 Assigned the _ Not null
Customer Name
Cadd Text 20 Assigned the _ Not null
customer
Address
Cphn Text 20 Assigned the _ Not null
customer Phone
Number
Cem Text 20 Assigned the _ Not null
customer
EmailId
Name:- Shopkeeper Details

Description:-Store Information about of Shopkeeper Details

Data Type Lenght Description Data Constraint

Element Store
Sid Number 5 A unique Shopkeeper Primary
Permant Deatails Key
Number
assigned to each
Snm Text 20 Assigned the _ Not null
Shopkeeper
Name
Sadd Text 20 Assigned the _ Not null
Shopkeeper
Address
Sphn Text 20 Assigned the _ Not null
Shopkeeper
Phone Number
Sem Text 20 Assigned the _ Not null
Shopkeeper
EmailId
Name:- Supplier Details

Description:-Store Information about of Supplier Details

Data Type Lenght Description Data Constraint

Element Store
Suid Number 5 A unique Supplier Primary
Permant Deatails Key
Number assigned
to each
Sunm Text 20 Assigned the _ Not null
Supplier Name
Suadd Text 20 Assigned the _ Not null
Supplier
Address
Suphn Text 20 Assigned the _ Not null
Supplier
Phone Number
Suem Text 20 Assigned the _ Not null
Supplier
EmailId
Data Element Type Size Description Data Constrain
Store t
Pubid Number 5 The unique Permanent Phurchase Primary Key
No Assigned Details
Suid Number 5 Assigned the supplier _ Not null
  Number for purchase
Bill
Bid Number 5 Assigned the Book _ Not null
  Number
Data Element Type Size Description Data Constrain
Store t
Sbid Number 5 The unique Permanent SaleBill Primary Key
No Assigned Details
Cid Number 5 Assigned the Customer _ Not null
  Number for SaleBill
Bid Number 5 Assigned the Book _ Not null
  Number
5.FORM DESIGN
LOGIN FORM:-
This is login form of a System
MDI FORM:-
This is MDI form of a System
Book Form:-
This is Book form.It accept and store the Book details
 
Customer Form:-
This is Customer form.It accept and store the
Customer details
ShopKeeper Form:-
This is Shopkeeper form. It accept and store ShopKeeper
details
Supplier Form:-
This is Supplier form. It accept and store ShopKeeper
details
PurchaseBill Form:-
This is PurchaseBill form. It accept and store
PurchaseBill details
SaleBill Form:-
This is SaleBill form. It accept and store SaleBill details
5.REPORT
Book Report
Customer Report
Shopkeeper Report
Supplier Report
Purchase Bill Report
Sale Bill Report
6.Advantages
And
Disadvantages
 
• Advantages: -

1. Fast access as well as processing.

2. User friendly system.

3. Paperwork is reduced.

4. Security for information.

5. Accurate and complete data store.

• Disadvantages:-

1. This system is applicable for single user only.

2. This project is offline.

3. We provide limited facilities to user.

4. The system provides only a single login and password, which can be
dangerous if password is leaked out.
7.CONCLUSION
• Bookshop Management system is actually a software which handle
the essential data and save the data  and actually about the database
of a Bookshop Management and it's Billing management.
• This software help in effectively management of the Customer Sale
Bill, Shopkeeper details ,Supplier Details and store the database.
• It provide the statistics about Books which are in stocks which data
can also be updated and edited. It works as per the requirement of the
user and have options accordingly.
• The record of suppliers supplies can also be saved in it.
• There are other function available too . The main purpose is
effectively and easily handling of Books data and it's management.
 
8.BIBLIOGRAPHY
Biblography

      
    
  v Books…
1. SADSE
…….S.PARTHASARATHY

2. The Complete Reference

……..Herbert Schildt

v Websites…

1.http://www.tutorialspoint.com

      
THANKING
YOU…!