INTRODUCTION

The project titled Book store Management System is Book store

management software for monitoring and controlling the transactions in a
Book store .The project Book store Management System is
developed in VB.Net, which mainly focuses on basic operations in a Book
store like adding new Cutomer, new books, and updating new information,
searching books and Publisher and facility to sold and return books.

Book store Management System is a windows application written for 32-

bit Windows operating systems, designed to help users maintain and organize
Book store. Our software is easy to use for both beginners and advanced
users. It features a familiar and well thought-out, an attractive user interface,
combined with strong searching Insertion and reporting capabilities. The
report generation facility of Book store system helps to get a good idea of
which are the books sold by the Publisher, makes users possible to generate
reports hard copy.

The software Book store Management System has four main modules.

Insertion to Database Module User friendly input

screen
Extracting from Database module Attractive Output
Screen
Report Generation module sold book list & Available
book list
Search Facility system search for books and Publisher
 SYSTEM ANALYSIS

EXISTING SYSTEM:

System Analysis is a detailed study of the various

operations performed by a system and their relationships within and
outside of the system. Here the key question is- what all problems
exist in the present system? What must be done to solve the
problem? Analysis begins when a user or manager begins a study of
the program using existing system.

During analysis, data collected on the various files,

decision points and transactions handled by the present system. The
commonly used tools in the system are Data Flow Diagram,
interviews, etc. Training, experience and common sense are required
for collection of relevant information needed to develop the system.
The success of the system depends largely on how clearly the
problem is defined, thoroughly investigated and properly carried out
through the choice of solution. A good analysis model should provide
not only the mechanisms of problem understanding but also the
frame work of the solution. Thus it should be studied thoroughly by
collecting data about the system. Then the proposed system should
be analyzed thoroughly in accordance with the needs.

System analysis can be categorized into

four parts.

System planning and initial investigation

Information Gathering
Applying analysis tools for structured analysis
Feasibility study
Cost/ Benefit analysis.
 In our existing system all the transaction of books are done
manually, So taking more time for a transaction like saling a book or
returning a book and also for searching of Publisher and books. Another
major disadvantage is that to preparing the list of books borrowed and the
available books in the Book store will take more time, currently it is doing as
a one day process for verifying all records. So after conducting the
feasibility study we decided to make the manual Book store management
system to be computerized.
PROPOSED SYSTEM

Proposed system is an automated Book store Management

System. Through our software user can add Publisher, add books, search
Publisher, search books, update information, edit information, borrow and
return books in quick time. Our proposed system has the following
advantages.

User friendly
interface Fast
access to database
Less error
More Storage Capacity
Search facility
Look and Feel Environment
Quick transaction

All the manual difficulties in managing the Book store have been
rectified by implementing computerization.
 FEASIBILITY ANALYSIS

Whatever we think need not be feasible .It is wise to think about the
feasibility of any problem we undertake. Feasibility is the study of impact,
which happens in the organization by the development of a system. The
impact can be either positive or negative. When the positives nominate the
negatives, then the system is considered feasible. Here the feasibility study
can be performed in two ways such as technical feasibility and Economical
Feasibility.

Technical Feasibility:

We can strongly says that it is technically feasible, since there will not
be much difficulty in getting required resources for the development and
maintaining the system as well. All the resources needed for the
development of the software as well as the maintenance of the same is
available in the organization here we are utilizing the resources which are
available already.

Economical Feasibility

Development of this application is highly economically feasible .The

organization needed not spend much m one for the development of t he
system already available. The only thing is to be done is making an
environment for the development with an effective supervision. I f we are
doing so , we can attain the maximum usability of the corresponding
resources .Even after the development , the organization will not be in a
condition to invest more in t he organization .There fore , the system is
economically feasible.
Hardware Configuration

Processor : Pentium III 630MHz

RAM :

128 MB Hard Disk

: 20GB

Monitor : 15 Color monitor

Key Board : 122 Keys

Software Configuration

Operating System :

Windows

NT,

Windows

98,

Windows

XP.

Language : Visual Basic .Net

Database : MS Access2007.
 SYSTEM REQUIREMENTS

This Book store management system can be used in windows 98, Windows2000,
Windows XP and
Windows NT, windows 7 , windows 8 .

The system must be running Windows 98, Windows 98 or Windows NT4.0

operating system and must meet the following hardware requirements.

For Windows 95 based computers , a 486 / 66

MHz or higher processor with 8MB
For Windows 98 based computers , a
500/88MHz or higher processor with 32 Mb of RAM
For Windows NT based computers , a 488 / 66
MHz or higher processor with 16 MB of RAM
For Windows 200 based computers , a 700/850
MHz or higher processor with 512 MB of Ram
DATA FLOW DIAGRAM
SOFTWARE INTERFACE

Add New
Book

Listing All
Books
Available
Books

Sold Books
Remove
Book

Edit Book
Details
 Add a
Cutomer
Listing all
Publisher

Edit a
Cutomer

Remove a
Cutomer
Search for Publisher and Books

Borrow
Books

Returning a
Book
List of Issued
Books

Reserve a
Book
 SYSTEM DESIGN

INPUT DESIGN

Input design is the process of converting

user-oriented input to a computer based format.
Input design is a part of overall system design, which
requires very careful attention .Often the collection of
input data is the most expensive part of the system.
The main objectives of the input design are

1. Produce cost effective method of input

2. Achieve highest possible level of accuracy

3. Ensure that the input is

acceptable to and understood by

the staff. Input Data

The goal of designing input data is to make

enter easy, logical and free from errors as possible.
The entering data entry operators need to know the
allocated space for each field; field sequence and
which must match with that in the source document.
The format in which the data fields are entered should
be given in the input form .Here data entry is online; it
makes use of processor that accepts commands and
data from the operator through a key board. The input
required is analyzed by the processor. It is then
accepted or rejected. Input stages include the following
processes

D
a
t
a

R
e
c
o
r
d
i
n
g

D
a
t
a

T
r
a
n
s
c
r
i
p
t
i
o
n

D
a
t
a

C
o
n
v
e
r
s
i
o
n

D
a
t
a

V
e
r
i
f
i
c
a
t
i
o
n

D
a
t
a

C
o
 n
t
r
o
l

D
a
t
a

T
r
a
n
s
m
i
s
s
i
o
n

D
a
t
a

C
o
r
r
e
c
t
i
o
n

One of the aims of the system analyst must be to

select data capture method and devices, which reduce
the number of stages so as to reduce both the
changes of errors and the cost .Input types, can be
characterized as.

E
x
t
e
r
n
a
l

I
n
t
e
r
n
a
l

O
p
e
r
a
t
i
o
n
a
l

C
o
m
p
u
t
e
r
i
z
 e
d

I
n
t
e
r
a
c
t
i
v
e

Input files can exist in document form before

being input to the computer. Input design is rather
complex since it involves procedures for capturing data
as well as inputting it to the computer.

OUTPUT DESIGN

Outputs from computer systems are required

primarily to communicate the results of processing to
users. They are also used to provide a permanent copy
of these result for latter consultation .Computer output
is the most important and direct source of information
to the users. Designing computer output should
proceed in an organized well through out the manner.
The right output must be available for the people who
find the system easy o use. The outputs have been
defined during the logical design stage. If not, they
should defined at the beginning of the output designing
terms of types of output connect, format, response etc,

Va
rio
us
ty
 pe
s
of
ou
tp
ut
s
ar
e

External outputs
Internal outputs
Operational outputs
Interactive outputs
Turn around outputs

All screens are informative and interactive in

such a way that the user can full fill his requirements
through asking queries.

DATABASE DESIGN

The general theme behind a database is to

handle information as an integrated whole. A
database is a collection of interrelated data stored
with minimum redundancy to serve many users
quickly and effectively. After designing input and
output, the analyst must concentrate on database
design or how data should be organized around user
requirements. The general objective is to
make information access, easy quick,
inexpensive and flexible for other users. During
database design the following objectives are
concerned:-

Controlled Redundancy
Data independence
Accurate and integrating
More information at low cost
Recovery from failure
Privacy and security
Performance
Ease of learning and use
 TABLES USED

Table Name: Books

Field Name Data Type Description

BookI AutoNumber Primary Key
d
Subjec Text (30) -
t
Titl Text (30) -
e

Author Text -
(25)
Publisher Text -
(25)
Copyright Number -
Edition Number -
Pages Number -
ISBN T -
e
NumberOfBooks Number -
NumberOfAvailbleBooks Number -
NumberOfSoldBooks Number -
Bookstor Text(25) -
e
Availble Yes/No -
ShelfNo Number -
Table Name: Borrow

Field Data Type Description

Name
BookI Number Primary Key
d
CutomerID Number -
DayOfSold Date/Time -
DayOfReturn Date/Time -

Table Name: Publisher

Field Name Data Type Description

CutomerId AutoNumber Primary Key
ID Number -
Password Text(10) -
NAM Text(25) -
E
EMAI Text(25) -
L
Major Text(10) -
NumberOfBooks Number -
Mony Number -
Expire Date/Time -
d
 SYSTEM IMPLEMENTATION

Implementation is the stage in the project

where the theoretical design is turned into a
working system. The implementation phase
constructs, installs and operates the new system.
The most crucial stage in achieving a new successful
system is that it will work efficiently and effectively.

There are several activities involved while implementing a new

project they are

End user training

End user Education
Training on the application software
System Design
Parallel Run And To New System
Post implementation Review

End user Training:

The successful implementation of the new system will

purely upon the involvement of the officers working in
that department. The officers will be imparted the
necessary training on the new technology.

End User Education:

The education of the end user start after the

implementation and testing is over. When the system
is found to be more difficult to under stand and
complex, more effort is put to educate the end used to
make them aware of the system, giving them lectures
 about the new system and providing them necessary
documents and materials about how the system can
do this.

Training of application software:

After providing the necessary basic training on

the computer awareness, the users will have to be
trained upon the new system such as the screen flows
and screen design type of help on the screen , type of
errors while entering the data , the corresponding
validation check at each entry and the way to correct
the data entered. It should then cover information
needed by the specific user or group to use the system.

Post Implementation View:

The department is planning a method to know

the states of t he past implementation process. For that
regular meeting will be arranged by the concerned
officers about the implementation problem and success
 SOFTWARE TESTING

Is the menu bar displayed in the appropriate

contested some system related features included either
in menus or tools? Do pull Down menu operation and
Tool-bars work properly? Are all menu function and
pull down sub function properly listed ?; Is it possible
to invoke each menu function using a logical
assumptions that if all parts of the system are
correct, the goal will be successfully achieved .? In
adequate testing or non-testing will leads to errors that
may appear few months later.

This create two problem

1. Time delay between the cause and appearance of the problem.

2. The effect of the system errors on files and records within the
system

The purpose of the system testing is to consider all

the likely variations to which it will be suggested and
push the systems to limits.

The testing process focuses on the logical

intervals of the software ensuring that all statements
have been tested and on functional interval is
conducting tests to uncover errors and ensure that
defined input will produce actual results that agree with
the required results. Program level testing, modules
level testing integrated and carried out.

There are two major type of testing they are

1) White Box Testing.

2) Black Box Testing.
 White Box Testing

White box some times called Glass box testing is a test

case design uses the control structure of the procedural design
to drive test case.

Using white box testing methods, the following tests where made
on the system

A) All independent paths within a module have been

exercised once. In our system, ensuring that case was
selected and executed checked all case structures.
The bugs that were prevailing in some part of the
code where fixed

b) All logical decisions were checked

for the truth and falsity of the values.

Black box Testing

Black box testing focuses on the functional requirements of the

software. This is black box testing enables the software engineering to
derive a set of input conditions that will fully exercise all functional
requirements for a program. Black box testing is not an alternative to
white box testing rather it is complementary approach that is likely to
uncover a different class of errors that white box methods like..1 ) Interface
errors

2) Performance in data structure

3) Performance errors
4) Initializing and termination errors
 CONCLUSION

Our project is only a humble venture to satisfy the needs in

a Book store. Several user friendly coding have also adopted. This
package shall prove to be a powerful package in satisfying all the
requirements of the organization.

The objective of software planning is to provide a frame

work that enables the manger to make reasonable estimates
made within a limited time frame at the beginning of the software
project and should be updated regularly as the project progresses. Last
but not least it is no the work that played the ways to success but
ALMIGHTY
 Reference

www.google.com/googlegear.html
www.indiyakey.com
www.w3schools.com
www.tanmayonrun.blogspot.in\2013\01\msaccessdatabaseexam
ples.com
www.tutorialspoint.com/vb.net/vb.net_forms.htm
www.dreamincode.net/forums/topic/301618-tutorialvbnet-creating-
windows-form-app-using-notepadcommandprompt/
www.msdn.microsoft.com/en-us/library/ms172749.aspx
www.stackoverflow.com
Table of Contents
INTRODUCTION...................................................................................................................
THE SOFTWARE BOOK STORE MANAGEMENT SYSTEM HAS FOUR MAIN MODULES.........................................................
SYSTEM ANALYSIS...............................................................................................................
EXISTING SYSTEM.....................................................................................................................................
PROPOSED SYSTEM..................................................................................................................................
FEASIBILITY ANALYSIS.........................................................................................................
TECHNICAL FEASIBILITY:.................................................................................................................................
ECONOMICAL FEASIBILITY................................................................................................................................
HARDWARE CONFIGURATION....................................................................................................................
SOFTWARE CONFIGURATION.....................................................................................................................
SYSTEM REQUIREMENTS.....................................................................................................
DATA FLOW DIAGRAM..........................................................................................................
SOFTWARE INTERFACE........................................................................................................
SYSTEM DESIGN..................................................................................................................
INPUT DESIGN...........................................................................................................................................
OUTPUT DESIGN.......................................................................................................................................
DATABASE DESIGN....................................................................................................................................
TABLES USED......................................................................................................................
TABLE NAME: BORROW..................................................................................................................................
TABLE NAME: PUBLISHER...............................................................................................................................
SYSTEM IMPLEMENTATION...................................................................................................
END USER TRAINING:.....................................................................................................................................
END USER EDUCATION:..................................................................................................................................
TRAINING OF APPLICATION SOFTWARE:...............................................................................................................
POST IMPLEMENTATION VIEW:..........................................................................................................................
SOFTWARE TESTING............................................................................................................
WHITE BOX TESTING.....................................................................................................................................
BLACK BOX TESTING......................................................................................................................................
CONCLUSION......................................................................................................................
REFERENCE.........................................................................................................................