PROJECT
SYNOPSIS
OF
BOOK SHOP MANAGEMENT
Submitted to:
Mr. ABC
Submitted by:
ABC
For More Synopsis visit : http://girfahelp.blogspot.in/
Preface
The main aim of science technology is to understand
natural event. We feel this event with our mind, which is
main part of our body. Computer is also gift of science,
which also works like a brain, but the manner speed at so
many other properties are much more than a men’s brain.
Modern age is an age of computer. Computer has just
become a part of our life.
The computer education in India was started in somewhere
in sixties. Now with the advent of micro computer, it has
become possible to have mass education in this field. The
major advantage of computers is the speed which
calculated are the and relative of output comes.
Computer can store much information and solve our
problem within very short duration.
So keeping these things in views, I have computerized my
small project work “BOOK SHOP MANAGEMENT ”.I
have maintained this project work on the suitable and
advance language i.e. “Visual Basic”.
For More Synopsis visit : http://girfahelp.blogspot.in/
Table of contents
1. Project Title
2.
Project Certificate
3.
Introduction
4.
Objective
5.
Project category
6. Feasibility study
7. Testing
8. DFD
9. ER Diagram
10. Data Structure
11. Process Logic
12. Output
13. Coding
14. Future Modification
15. Bibliography
For More Synopsis visit : http://girfahelp.blogspot.in/
Project Title
For More Synopsis visit : http://girfahelp.blogspot.in/
Introduction
Welcome to BOOK SHOP MANAGEMENT SYSTEM. This
project is for many purposes because I want to give full satisfaction of the
user.
In my project I provide many facilities to user. In Book shop
management system it is very difficult to manage all things but with the help
of my software it becomes very easy to handle. It saves our time and paper
work.
So we consider the above problem and make this software. In this
software you store all kinds of information like-
For More Synopsis visit : http://girfahelp.blogspot.in/
Objective of the Project
Our consideration while developing this software was to achieve the
following goals:1-
This software is for Book shop management so it provides those
facilities, which is used in any Book Shop.
2-
It also saves the valuable time of the shop owner and lots of paper
works.
3-
This will save lots of effort of the user. He/She is able to manage lots
of information after using this software and also able for seeing in
different angles.
4-
User can manage all the records very easily. You can generate all
kinds of reports like bundle receiving, Transport receiving, customer
detail and many more reports for management.
We also try to maintain security of data. User cannot enter directly to the
software without using login and password
6
Project Category
This project belongs to the category of application software as use the applications
of Book Shop Management System can it. It is a desktop application, At a time only
One user can use it. It is a type of commercial software so terms and conditions are
provides by the vender to buyer.
7
Feasibility Study
It has very important place in the study of any software because if the
project are not feasible then working on this working on this software is not
a good work.
So I conducted the feasibility study in order to check out whether our
software “TRANSPORT MANAGEMENT SYSTEM” is feasible or not. So
we study about thee types of feasibility:
Economic Feasibility

Technical Feasibility

Operational Feasibility
So brief description of above are following
1 Economic Feasibility:In this study, I was concerned about broad range of factors. Our
software has no need of any other equipment or software. It saves very much
time and lots of manual work. It also saves the paper work of the person.
So, in short we can say that it is economic feasible software and saves
lots of expenses of the person and time as well.
8
2 Technical Feasibility:In technical feasibility we studied that the system is technical feasible
or not. If system is not feasible then, a system analyst takes a decision about
software that will be proceeding out or not.
So, we take care of that our software is overall technically feasible. I
take care of the development and technology of the Varanasi region for
ensuring availability of the hardware and software needs for implementation
of this project and that is minimal.
3 Operational feasibility:Our software is user friendly. So a person who does not have any
technical background can operate this software, prior knowledge of
computer is not mandatory for operating the software. Icons menus and its
options describing its meaning itself, input and output form are designed in
user friendly way for providing proper instructions with user.
So we specially take care of that software is operational feasible.
9
DFD
I) DFD on book shop management system
Transaction
B.S.M.S
Books
Report
Employee
Customer
10
II) DFD ON CUSTOMER TABLE
Customer
Book Detail
Publication
B.S.M.S
Author Name
Reject
Report
11
Data Base
III) DFD ON BOOKS STOCK:
Employee
Check detail
Data Base
Books
Generate
Report
12
About Books
Save Detail on
Data
Base
Service
Employee
Save on
Maintain
by
Books
Receipt
Register
Save
Have
Purchase
Enquiry
Provide to
B.S.M.S
Provide
Data
Base
Have
Maintain
Save
Transaction
13
Customer
ER Diagram
I) Entity of book Shop Management System:
Customer, Books, Employee, Transaction, Book Shop
II) Attributes Entities and their structure
a) CUSTOMER ( Cust_id, Cust_Name, Cust_add, Cust_mno);
b) BOOKS (Book_Name, Book_Prize, Auther_Name,
Book_Publication);
c) EMPLOYEE (EMP_id, EMP_Name, EMP_add, EMP_Salary
,Emp_job, EMP_dob);
d) TRANSACTION (trans_id, trans_amt, trans_type, trans_date);
e) BOOK SHOP (Reg_no,BS_Name,BS_add);
III) Entity and their relationship
1) Relationship between Book shop & Customer
Have
Book Shop
Customer
2) Relationship between Book Shop & Employee
Book Shop
Employee
Have
14
3) Relationship between Book Shop & Books
Book Shop
Contains
Employee
4) Relationship between Book Shop & TransactionBook Shop
Maintain
Employee
5) Relationship between Employee & Books
Employee
Books
Maintain
6) Relationship between Employee & Customer
Employee
Deals
Employee
7) Relationship between Employee & Transaction
Employee
Deals
15
Transaction
Emp_id
Emp_add
Emp_no
Emp_name
Emp_ph
Employee
Maintain
Shop_name
B_ISDN
Shop_loc
Contains
Pub_nm
Emp_ph
Book Shop
Maintain
Auther
Tms_id
Books
Generate
Tms_no
B_nm
Have
Transaction
Report
Rep_id
Rep_ty
Rep_nm
Tms_dd
Customer
Deals
Buy
Custt_add
Cust_nm
16
Tms_ty
Cust_id
Custno
Data Structure
Employee Module:
This table contains employee related information
Attribute
Emp_id
Emp_Name
Emp_FN
Emp_MN
Emp_Dob
Emp_Add
Emp_P.no
Data types
Integer
String
String
String
Date
String
String
Size
2 byte
30 byte
30 byte
30 byte
10 byte
30 byte
10 byte
Constraint
Primnary key
Not Null
Not Null
Not Null
Not Null
Not Null
Not Null
Customer Module :
This table contains Customer related information
Attribute
Cust_id
Cust_Name
Cust_Add
Cust_P.no
Data types
Integer
String
String
String
Size
2 byte
30 byte
30 byte
10 byte
Constraint
Primnary key
Not Null
Not Null
Not Null
Book Module :
This table contains Book related information
Attribute
Book_ISDN
Book_Name
Auth_Name
Pub_Name
Data types
Integer
String
String
String
Size
2 byte
30 byte
30 byte
10 byte
17
Constraint
Primnary key
Not Null
Not Null
Not Null
Transaction Module :
This table contains Transaction related information
Attribute
Tms_id
Tms_Name
Tms_Type
Tms_Date
Data types
Integer
String
String
String
Size
2 byte
30 byte
30 byte
30 byte
Constraint
Primnary key
Not Null
Not Null
Not Null
Report Module :
This table contains Report related information
Attribute
Rep_id
Rep_Name
Rep_Type
Rep_Date
Data types
Integer
String
String
Date
Size
2 byte
30 byte
30 byte
10 byte
18
Constraint
Primnary key
Not Null
Not Null
Not Null
Process Logic
Logic For Registration Form
Start
Enter All Detail of Employee
No
Is Correct
Yes
Process of Registration
Stop
Logic for Delete Record form :
Start
Enter Employee id
No
Is Correct
Yes
Deleted record
19
Stop
Logic for update Record form :
Start
Enter employee id & name
No
Is Correct
Yes
Update Records
Stop
Logic for find Record form:
Start
Enter employee id & name
No
Is Correct
Display the employee recordYes
Stop
20
Logic for submit Employee salary details :
Start
Enter employee id & name
No
Is Correct
Yes
Display salary Record of
Employee
Stop
21
REFERENCES
 http://www.tutorialspoint.com/listtutorials/visual
http://www.vbtutor.net/vbtutor.html
22
22