You are on page 1of 18

Book Shop Management System

Introduction:
In todays era computers have become a vital component of any enterprise for
giving it proper directions and extensive control of the various activities to attain
business objectives. Computer applications have affected scientific &
commercial knowledge.
The information System of the old times totally differs from the todays. It is
automation system of a book shop or any information system. In the previous
ages the process of maintaining data and record seemed very difficult. Now days,
computer is very essential component. The implementation of computer based
Information System can be depicted as the ease in handling and maintaining the
data bank of any size.
Our project is on Book Shop Management System whichdeals with almost all
the information of Book Shop .It keeps the database of customer records and
publishing records. It also keeps the author list, charges and Book-title list.
The business of Book Shop is spread all over the world. A large record should be
maintained in a proper manner for running of Book Shop.The proposed system is
a window based menu driven system. It reduces the paper works, time needed for
doing various tasks etc. Our project upholds the accuracy of data.

Project Objective:
The main objective of this work is to reduce the difficulties that are found in the
present system. The present system requires a lot of paper works, manual works
etc. The accuracy is less in the present system. The details must have to be stored
manually in the present system. In the present system, the details of a particular
book/transaction are stored in different registers by different persons; this often
leads to data isolation and inconsistency.
There is always an objective behind every innovation and behind every work. We
did have many objectives for our project which are described as follows:
I.
II.

To search records of a book efficiently.


Processing a large amount of data effectively and efficiently.

III.

To provide better service.

IV.

It keeps database of publishing details, price and Customer record.

V.

In such a huge project where the amount of data to handle was tremendous,
there was strong demand for greater accuracy and consistency.

VI.

Since the system is subjected to be accessed by number users, the system must
safeguard sensitive and important data in a form that is accessible only to the
authorized personal.

VII.

Input validation features to make sure that only correct information has been
provided.

VIII.
IX.

It is easiest way to maintain publishing record data.


It can generate knowledge about books.

X.

It Helps to Keep the entire information of the book shop in a systematic way
so that it becomes easier to know about the books and sale/purchase.

XI.

It also generates the reports like sales/purchase.

ER-DIAGRAM:
EnameEmpid

Pay

Job

P_addres
s

Publishi
d

Supplier
B_title

Bid

Publisher

Purchas
e
Publishid

Order
No.

ha
s

Book
D_id
Order No
Price

ISBN
NO

Bill

Distributor

Sell
Price
C_id

Bid

D_id

ha
s

Price
Cid

Emp_i
d

D_addres
s

Customer

Book-catalog

C_id
BookType
Cname
Caddress

BookType

D_name
eee

Complete Structure which includes


Main Project

User
Create
User

Customer
User
Type

Save
User

View

Supplier

Details

View

Product

View

Change
Password

Subject

View
Purchase
Order

Sales
Invoice
Splash

View

Number of modules and their descriptions: 1. User: It is used to create a user along with its profile. It is also used to filter
an authorized user, in order to access the system.
2. Customer: - This module of the system gathers customers information and inserts it into
the database.

3. Supplier: - This module gathers suppliers information and inserts into the database.
4. BOOK: - This module manages the insertion of product specific information into the
system.

5. Subject: - This module manages the various subject related details.


6. Purchase Order: - This system generates the purchase order.
7. Sales Invoice: - This system generates the sales invoice.
8. Attractive User Interface: - This module creates user interface for the
customer, so that, the interaction with the system can be made easy,
powerful, and effective.

Data Structures for all the modules: -

Table Name : - Books


Description : - Used to maintain Books records
Terms Used

Data Type

Width

Constraint

Book_ID
Book_Name

Number
Varchar2
Varchar2
Varchar2
Varchar2
Varchar2
Number
Varchar2

10
50
50
50
50
50
10,2
100

Primary Key

Category_Name
Author
ISBN
No of Pages
UnitPrice
Description

Table Name : - Supplier


Description : - Used to maintain Supplier records
Terms Used

Data Type

Width

Constraint

Supplier_ID

Number

10

Primary Key

CompanyName
Contact Person
Address
Phone
Fax
Email

Varchar2
Varchar2
Varchar2
Varchar2
Varchar2
Varchar2

50
50
100
15
15
30

Table Name : - Customer


Description : - Used to maintain Customer records
Terms Used

Data Type

Width

Constraint

CustomerID

Number

10

Primary Key

ContactFirstName
ContactLastName
BillingAddress
PhoneNumber
D_O_J
Email_id
Fax-Number

Varchar2
Varchar2
Varchar2
Varchar2
Number
Varchar2
Varchar2

50
50
100
15
5
15
30

Table Name : - Purchase_Order


Description : - Used to maintain Purchase order records
Terms Used
PurchaseOrderID
Deliveary_Address
PurchaseOrderDate

Data Type

Width

Constraint

Number

10

Primary Key

Number
Date

10

Foreign Key

Table Name : - Purchase_Order_Details


Description : - Used to maintain Purchase order details records
Terms Used

Data Type

Width

Constraint

PurchaseOrder ID

Number

10

Primary Key

PurchaseOrderID
PurchaseProductID
PurchaseQuantity
PurchaseUnitPrice
PurchaseDiscount
NetValue

Number
Number
Number
Number
Number
Number

10
10
10
10
10
10

Foreign Key

Table Name : - Payment_Details


Description : - Used to maintain order records
Terms Used

Data Type

Width

Constraint

Invoice_No

Number

10

Primary Key

Order_ID
Payment
Dues
Date of Payment
Discount
Status

Number
Date
Varchar2
Number
Number
Number

10

Foreign Key

50
5
10,2
50

Table Name : - Stock_Details


Description : - Used to maintain Purchase order details records
Terms Used

Data Type

Width

Constraint

Book_ID

Number

10

Primary Key

No_ of_ Copies


Date Of Matainces

Number
Number

10
20

Foreign Key

Table Name : - Supplay_Details


Description : - Used to maintain Purchase order details records

Terms Used

Data Type

Width

Constraint

Supplay_ID

Number

10

Primary Key

Book_ID

Number

10

Foreign Key

Table Name : - Purchase_Details


Description : - Used to maintain Purchase order details records
Terms Used

Data Type

Width

Constraint

Supplier_ID

Number

10

Book_ID
Quantity
Cost
Date _Of_ Payment

Number
Number
Number
Date

10
20
10
10

Reports Generation: -

This system generates some reports, which are as

follows: i.

Customer Report: - It Collects customer id and generates various details


related to the customer like first name, last name, address, phone number,
email address etc.

ii.

Purchase Report: - It collects order id and generates information such as


supplier id, order date, product id quantity, unit price, discount and net
value.

iii.

Sales Report: - It collects order id and generates information such as order


date, book name, quantity, unit price, and amount.

iv.

It collects customer code and generates total annual transaction report of


the customers.

Tools/Platform, Hardware and Software


Requirement Specifications
HARDWARE REQUIREMENT
Processor : - Pentium IV Processor

RAM

: - 1 GB RAM

Hard Disk: - 5 GB
Support

: - VGA/SVGA supported Monitor


(HIGH RESOLUTION)

SOFTWARE REQUIREMENT
Operating
System

: - WINDOWS 98/ME/XP/7/8

Front End
Language

: - Visual Basic.NET

Back End
Language : - SQL/PLSQL
RDBMS
Software : - Oracle 10G

Security Mechanisms:
Security mechanisms mean different things to different people. The term
"security" is somewhat vague unless it is discussed in some context. Here are
some points that could clarify what actually Security Mechanisms means: i.
ii.

Safe from malevolent programs.


Non-intrusive.

iii.

Authenticated.

iv.

Encrypted.

v.

Audited.

vi.

Well-defined.

vii.

Verified.

viii.

Well-behaved.

ix.

C2 or B1 certified

Based on the above definition, the security mechanisms provided in our project
are as follows: -

I. Use of Net9-compliant firewall on the server (both Web and Database): it basically separates a protected network from an unprotected one, on the
Internet/Intranet. It screens and filters all connections coming from the
Internet/Intranet to the protected (corporate) network, and vice versa,
through a single, concentrated security checkpoint.
II. Use of user id and password before entering highly secured areas on
the site i.e. Administrative Entry.
III. Use of ORACLE: - ORACLE provides extensive features to safeguard
our information from both unauthorized viewing intentional or inadvertent
damage. This security is provided by granting or revoking privileges on a
person-by-person and privileges-by-privileges basis, and is in addition to
any security our computer system already has.
The use of oracle lets us to implement the following security mechanisms: i.

We have used create user, create role, and grant commands to


control data access.

ii.

We have used Fine-grained access control (FGAC). Its a new


feature in Oracle8i that allows us to implement security policies with
functions and then use those security policies to implement row-level
security on tables and views.

iii.

We have used ORACLE LABEL SECURITY. It allows us to assign


security labels to rows.

IV. Use of JAVA technology: -It provides simple mechanisms for protecting
our computer (i.e. database and files) from evil programs like viruses. We
have used policytool utility to create a policy file that contains the
appropriate permission.

Future Scope and further enhancement of the project.


Future Scope of the Project: - Since the System is capable of generation
historical data as well in date Ware House. There is a further scope in improving
the performance System to enhance the management of the customers with a
goal to increase profitability of the company.

Further Enhancement: - The project can be extended to make it WAPEnabled so that it can be accessed using a Micro-Browser build within a Mobile.
The client of the project: - This System is capable enough to customize it as
per need of the specific organization.

Limitation of the Project

: - This is the demo project so it cant be use in

real world. Because, when the project is running it may produce some errors.

And the database is restricted because the Supplier cant add the records more
than hundred records. This project can use more memory and more CPU. Finally,
we can say that this project is made for the supplier but they cant use in real.
Guidelines in writing the scope and delimitation. The scope
and delimitation should include the

following:

1. A brief statement of the general purpose of the study.


2. The subject matter and topics studied and discussed.
3. The locale of the study, where the data were gathered or the entity to which the
data belong.
4. The population or universe from which the respondents were selected. This
must be large enough to make generalizations significant.
5. The period of the study. This is the time, either months or years, during which
the data were gathered.