CHAPTER-4

ANALYSIS
4.1 problem statement
The existing system provides the basic functionalities which have to be handled
in a Book Inventory Management system. In the existing system all the
sales men details, admin details, availability details, stock are
maintained manually by the admin. There is no search technique to check
book information. It is a very difficult task to maintain the records by
using this existing system. These are the main disadvantages of the
existing system.
1. In some of the book stores data and records are stored manually in the
form of papers.

4.1.2 PROPOSED SYSTEM

In our proposed system we are going to provide solutions to all the
above said problems by automating the entire book management system.
By using user friendly software that handles the entire book store, we
can search the required information relating to a book. All the data of
the book store is stored on the system.

1. This system is most efficient and effective.

2. There is no risk of losing the data.
4.2 FUNCTIONAL REQUIREMENTS

FR01 ADMIN This module allows registering

new salesmen.
FR02 SALESMEN This module sells the book to
purchaser.
FR03 PURCHASER This module helps in purchasing
books.
FR04 STOCK This module helps in maintaining
quantity of books and helps in
knowing availability of books.
 4.3 NON FUNCTIONAL REQUIREMENTS

1. User Friendly Application:

This application can be used by any book shop and user can easily
use the application with basic computer knowledge.
2. Easily Maintained:
All the data and records of book, salesmen are easily maintained
and can be updated whenever required.
3. Reduces Manual Work Load :
This kind of management reduces labour because everything
is stored on the system.
4. Secured:
Data is stored and it is highly secured data cannot be
destroyed or lost.
 CHAPTER-5
DESIGN
5.1 ER DIAGRAM
5.2 DATA FLOW DIAGRAM

5.3.1 ZERO LEVEL DFD

5.2.2FIRST LEVEL DFD
5.3 USE CASE DIAGRAM

UML Diagrams: Actor: A coherent set of roles that users of use

cases play when interacting with the use cases.

Use case: A description of sequence of actions, including variants,

that a system performs that yields an observable result of value of
an actor.

UML stands for Unified Modeling Language. UML is a language

for specifying, visualizing and documenting the system. This is the
step while developing any product after analysis. The goal from
this is to produce a model of the entities involved in the project
which later need to be built. The representation of the entities that
are to be used in the product being developed need to be designed.
5.4 INTERFACE DESIGN