Bookstore System

BOOK STORE SYSTEM
1) INTRODUCTION TO SYSTEM
1.1) DEFINITION
Page 1 of 69
BOOK STORE SYSTEM

(1) INTRODUCTION TO SYSTEM
Roopal Book Store is located at Mota Bazar, Anand (Gujarat). Mr. Bipin
Panchal is the owner of this Book Store. The main reason for setting up the Roopal
Book Store was that there was no such book Store in that area that provided all the
types of books to the students with good discount.
The Roopal Store deals with many things i.e. Purchase, Sales of the Books,
Maintenance of Books, etc. The Book Store brings the Books from its go down and
sales the Books at their Book Store.
The Book Store maintains the record of the current rate of the Books. It also
maintains the records of their Vendors (Suppliers). It updates regularly day to day.
(1.1) DEFINITION
Book store system will computerized the process like inquiry of the books,
selecting the particular supplier for the order, placing the order either based on inquiry
or direct, receiving the order, maintaining the stock of order.
Page 2 of 69
BOOK STORE SYSTEM
2) INTRODUCTION TO EXISTING SYSTEM
Page 3 of 69
BOOK STORE SYSTEM

(2)
INTRODUCTION TO EXISTING MANUAL SYSTEM
Existing system is based on manual work and all the process are done
manually, so they maintain registers and files for recording all the details of the
system.
They maintain several registers for recording the entry of daily transactions
such as Purchase of Books from the Vendors as well as Sales of the Books to the
customers, etc.
They maintain the record of the Books so they keep each and every information
regarding the Books in the Book master file. In the similar fashion they maintain the
records of their vendors so they keep each and every information regarding their
vendors in the vendors master file.
They keep the bill book or cashbook to maintain the record for each sale of the
Book or transaction in the Book Store.
They maintain the register or book for their vendors so they can pay the money
to them after some time.
Thus maintaining party information, Book information, party transaction,
Customer transaction and all the things are done manually.
Page 4 of 69
BOOK STORE SYSTEM
3) REGUIREMENT OF ANALYSIS
3.1) NEED TO DEVELOP SUCH SYSTEM
3.2) SCOPE OF SYSTEM
3.3) BOUNDARIES OF PROPOSED SYSTEM
3.4) OBJECT OF PROPOSED SYSTEM
Page 5 of 69
BOOK STORE SYSTEM

3.5) FACT GATHERING TECHNIQUES
(3) REQUIREMENT OF ANALYSIS

(3.1) Need to develop such system
(1)
Answer the question whether a new system is to be installed or not?
(2)
Determine the potential of the existing system.
(3)
Improve the existing system.
(4)
Know what should be embedded in the new system.
(5)
Define the problems and objective involved in a project.
(6)
Avoid costly repairs at a later stage when the system is implemented.
(7)
Avoid crash implementation of a new system.
(8)
Avoid the Hardware Approach i.e. getting a computer first and then
deciding how to use it.
(3.2) SCOPE SYSTEM

As a part of the preliminary study, the scope of the system (a broad perspective
of what the system is going to do) has to be clearly outlined. This is useful for
estimating the amount of effort required, the cost involved etc.
In any Book Store Purchase and Sales department play an important role to
produce great image in market. We cannot think about an existence of an individual
department only. Here the Purchase department deals with all the procedure
regarding the purchase of the Book from the Vendor. Here the sales department deals
with all the procedure regarding the sale of the Books to the Customers.
During the purchase or sales procedure the Book Store will interact with the
Vendor or with the Customer as external entity and with other departments inside the
environment of Book Store.
Page 6 of 69
BOOK STORE SYSTEM

(3.3) BOUNDARIES OF PROPOSED SYSTEM
The boundary of the system is the boundary of the Book Store which encloses
the different departments including the purchase and sale department which interact
with the external entities as Vendor and Customers.
(3.4) OBJECT OF PROPOSED SYSTEM
To provide quick and efficient means for performing sales related activities and
to effortlessly generate report of the system.
To provide quick and efficient means of performing Purchase related activities

and to effortless generate report of the system.
To automize the work such as billing, Book record, Vendor record, etc.
To automize the different types of reports.
[PROBLEM IDENTIFICATION]
Page 7 of 69
BOOK STORE SYSTEM

The phase of system analysis process deals with problems, which are affecting
in the current manual system. The problems are those, which are affecting the Roopal
Book Store in its daily routine work.
As the growing trend in InfoTech World of computers need of accuracy,
perfectness, speed and high memory data storage is a must. Each and every problem
must be solved with a least amount of time and energy.
The problems faced by existing system are described as below:
Difficulty in Maintenance of Records.
Time Consuming.
Editing of data becomes a tedious job.
No Security of Data.
Mistakes Occurring in long Calculations [Total Purchase, Total Sales,
Grand totals, yearly sales, etc]
Proper Generation of Report.
Lack of Efficiency and Man Power.
Book Maintenance.
High Data Redundancy.
Data Inconsistency.
Difficulty in Maintenance of Records:

It is very difficult to maintain data record in the system as all the records are
entered in the register or the respective record books. There are chances of the
record books or files in which all the data is kept may be torn or wearied out or some
other damages which results in the destroyed data. Also a problem occurs if the data
file or register is misplaced somewhere else and is not getting at the time of actual
requirement of the data stored. It is also difficult to maintain old files and registers
which have data of past years, which the owner has kept for future references.
Page 8 of 69
BOOK STORE SYSTEM

The problem occurs when the sale of Book is more and when the monthly
report or bill is generated then the owner has to go through lots of records and which
is very tedious task.
Time Consuming :
It is very time consuming process to write each and every entry in the database
register. Also it takes a lot of time if all the entries are repeated. In the system
processes such as making different type of reports, billing, tedious calculations are
examples of time-consuming process in the system.
It is also time consuming process to know the total number of sale done or the
total purchase of books done by the Roopal Book Store when written manually but
through computerized system it takes less time as it is speedy and accurate.
Editing of Data:
Manual written data cannot be changed or edited once written. If there is a
mistake and if we try to rub and write it again it makes the register very dirty and
untidy, which crates a bad impression of the business. If data is entered incorrect
whole document gets incorrect while errors cannot be easily solved by editing wrongly
entered data.
If one had done some wrong entry then to edit the data one has to go through
lots of records and, again and again editing the record makes it difficult to read.
Data Insecurity:
As the data is stored in files or registers, it is not in a secure place. As the
storage media here are files and books or registers there are chances of getting these
storage media lost, torn, or it may go in the hand of wrong person, which can destroy
the database, or it can also be destroyed accidentally. Also in the system data should
be shown to the person according to his position and post in the office, everybody
should not be allowed to use all the data.
If the data goes in the hand of wrong person then he/she may take the
advantage of the data and the Book Store may go in loss. So security is the major
aspects of the Book Store.
Page 9 of 69
BOOK STORE SYSTEM

Report Generation:
After a certain time period if the user wants to checks his total sales or total
profit or total expenditure or monthly sale and similar is the case with purchase than it
becomes very tedious for the owner to check all the respected date and according to
the data creating respective reports for the transactions. A computerized system
having report making facility can do this job easily and also the owner can draw
different types of charts and diagrams to make him understand the ups and downs of
his Book Store.
High Data Redundancy:
As mentioned in the current system, due to maintenance of so many registers there is

a high redundancy of data i.e. same data is recorded repeatedly.
Data Inconsistency:
Here as mentioned in the above step the same information is written in more than
one place that creates the problem, when there is a change or deletion in the recorded
data.
(3.5) FACT GATHERING TECHNIQUES

Information gathering in any organization is not an easy task.
it has to be gathered in an organized way so that
(a) No system details are left out.

(b) Right problems are identified.
(c) Repetitive work is avoided.
(d) Wrong or incomplete details are not collected.
To do this, a proper search strategy must be decided first, search

strategy includes selecting information sources and search methods.
Page 10 of 69
BOOK STORE SYSTEM

It also includes modeling methods to make sense out of information so
collected.
Here an overall idea about the search methods or fact gathering
techniques which are used while gathering the information, they are:
(1) Interviewing.
(2) Record inspection.
(3) Observation.
These techniques are used in system analysis and design stage.

I have visited a many times at the organization to get information as well as the
basic problems which are occurring in the current existing manual system. As each
and every person in the organization has different types of job to be done so I met
some of the people of the organization.
(1)
Interviews:
Interview allows the analyst to collect or gather the information from the
individual or group who are generally the current user of the existing system or
potential user of the proposed system.
They may be managers or employee of the firm itself who provide the data for
the proposed system and who will be affected by it.
As far as interview is concerned, it is a time consuming process.
It is a basic source of qualitative information.
It allows the analyst to discover areas of misunderstanding, indication of
resistance to the proposed system.
Page 11 of 69
BOOK STORE SYSTEM

Interview could be (a) Structured (b) Unstructured.
(1) Structured:
Here, it uses standardized questions as far as response of the questions is
concerned; they are divided into two formats:
(a) Open response format:
Here the questions are answered in ones own words.
(b) Closed response format:
Here set of prescribed answers is used.
(2) Unstructured:
Here the questions are worded to suit the respondent that provide the information
about the areas overlooked or not thought to be important.
Advantages and Disadvantages of structured and unstructured interviewing:
ADVANTAGES:
(1) Structured:
Ensures uniform wording of questions to all respondents.
Easy to administer and evaluate.
Less interview training required.
Result in shorter time.
(2) Unstructured:
Questions can be worded to suit the respondent.
May produce the information about the areas overlooked or not thought
to be important.
DISADVANTAGES:
Page 12 of 69
BOOK STORE SYSTEM

(1) Structured:
Cost of preparation is high.
Such high level of structure may not always be suitable.
Some respondent may resist to such structure.
(2) Unstructured:
Inefficient use of interviewer and respondent time.
Results take a longer time.
Extra time required for the collection of essential facts.
The success of the interview depends on the skill of the interviewer and
his/her preparation for the interview.
Analysts must also be aware of the kinds of difficulties at some interview,
and must know how to deal with the potential problems.
User interviews were conducted to determine the qualitative information. These

interviews which were unstructured interviews provided opportunity to gathered
information from respondents who are involved in the process for a long time.
These interviews provided information such as
Activities involved in process of purchase.

Activities involved in process of sales.
Limitation of existing system.
Types and frequency of purchase.
Types and frequency of Sales.
Problems faced by the user in the existing system.
Page 13 of 69
BOOK STORE SYSTEM

(2)
Record Review:
It is said to better believe in records than in people.
Thus a good analyst always gets facts from documents.
An existing system can be better understood by examining existing documents,
forms and files.
In record review analyst examine information that has been recorded about the
system and users.
Records inspection can be performed at the beginning of study as an
introduction or later in study as a basis for comparing actual operations with
what the records indicate should be happening.
Records may include:
1) Written policy manuals.
2) Rules and regulations
3) Standard operating procedures used in the organization
4) Forms and documents.
A business system involves peoples and machines, data and procedure
between them.
A good documentation system provides relationships and interaction between
them.
Analyst also can know about organizational structures, activities, procedures
and flow of data.
E.g. From organization chart one can know formal grouping of people in a
department.
Page 14 of 69
BOOK STORE SYSTEM

Records do not show how tasks are performed or what activities are actually
occurring and where decision making power lies.
Analyst through good analysis can get answers to questions like:
1) Who uses the forms?
2) Do they include all necessary information?
3) How readable and easy to follow is the records?
4) Is it ideal for analysis and inferences? etc.
To gather details about the sales system, many kinds of records and reports
were reviewed. The study covered.
Standard operating procedure
Reports generated by the existing system.
Document flow (input/output) of the Book Store Management System.
Process of purchasing the Books from the party.
Process of sales of Books to the client.
Record of previous years purchase and sales of Books.
Types and format of database registers such as purchase from Vendor, sales to
Customer, etc.
(3)
Observation:
Observation can bring in missed facts, new ways to improve the existing
procedures, duplicate work done inadvertently, etc.
Observation can bring in what other fact-finding methods cannot! But this task
is delicate because people do not like to be observed when they work.
Page 15 of 69
BOOK STORE SYSTEM

It is not the quantity of time observed is important but the unorthodox angles of
observation of the work content and methods are going to be rewarding.
Observation gives analyst the opportunity to go behind the scenes in an
organization to learn inside story to discover how things work in new areas of
information.
Observation can look for:
(a) Operational inefficiencies.
(b) Alternate routes and procedures.
(c) Interruptions in the normal flow of work.
(d) The usage of files and documents.
(e) Informal communication channels, etc.
On site observation provides close view of the working of the real system.
He can observe people, objects, documents and occurrences of events.
Page 16 of 69
BOOK STORE SYSTEM
Page 17 of 69
BOOK STORE SYSTEM
4) INTRODUCTION TO PROPOSED SYSTEM

(4) INTRODUCTION TO PROPOSED SYSTEM
The manual system of Roopal Book Store is to be computerized in order to
overcome the problems, which affects the existing manual system. Computerizing the
existing system with the help of some programming language, database package
ease the work of the system up to a great extent.
Generally, there has been a criterion to work on any job or task for a specific
purpose. Nobody works without specific detailed information about the particular task
he is performing. Thus, any transaction can be performed such as Purchase, Sales
and Maintenance of Books. In the new computerized system the basic and the initial
first step is to ask for a specific user login name and password for it, thus it can also
take care of data security, now after when the user enters the necessary details in the
login name and password it checks for the correct password and allows the user of
the system to enter the main page.
Page 18 of 69
BOOK STORE SYSTEM

As the user is inside the system, the first screen of the system would be a
welcome message and a list of menus.
In the Customer Master screen the user can Add, Edit, Delete, Save and
search any particular record just by selecting the Customer Number from the list.
In the Author Master screen the user can Add, Edit, Delete, Save and search
any particular record just by selecting the Author Number from the list.
In the Publisher Master screen the user can Add, Edit, Delete, Save and search
any particular record just by selecting the Publisher Number from the list.
In the Book Master screen the user can Add, Edit, Delete, Save and search any
particular record just by selecting the Book Number from the list.
In the Vendor Master screen the user can Add, Edit, Delete, Save and search
any particular record just by selecting the Vendor Number from the list.
In the Purchase screen the user can Purchase the particular Books and the
screen will give the amount as well as the total amount of these Books.
In the Sales screen the user can sales the particular Books and the screen will
give the amount as well as the total amount of these Books.
In the similar way the Sale of Books is performed. The user can sale the
particular Books and the screen will give the amount as well as the total amount of the
items.
The user can easily find all the data any time with out wastage of time through
selecting specific menu used for specific purpose.
After the transaction is completed the user can log off from the system by
simply quitting from the system. Again if the user wants to enter in the system he must
Page 19 of 69
BOOK STORE SYSTEM

input the specific username and password to enter. The system will not allow any
wrong password and will not allow to enter the system, thus it is safe from
unauthorized access of the Book Stores data.
TOOLS INFORMATION
Microsoft Visual Basic 6.0 [Front-End]:

To develop any system along with the back-end tools which provide access to
the database and also solves the database queries like oracle, to make a system
interactive with the user the use of front-end tools comes into the picture. The frontend tools make the user interface with the system easier and also provide a userfriendly environment to the system.
This rich language enables you to develop many different types of applications.
You can create you can create programs that intersect with the hardware.
It is a programming language used to create window base application. Visual
Basic is an old BASIC (Beginners All-purpose Symbolic instruction code) language. It
makes it very easy to get the user interface portion of your application up and running.
Hundreds of functions and latest technological advances have been added to
the language to make it an industrial strength development environment suitable for
almost my type of windows application. This is especially true with the advent of
internet programming and object oriented programming.
Microsoft Visual Basic 6.0 is one of the front-end tool provided by Microsoft
Inc. Microsoft Visual Basic 6.0 provides a fast way to develop applications for
Microsoft Windows. As a front-end tool Microsoft Visual Basic 6.0 provides the G.U.I
interface to the user and it is supposed to be one of the beast front-end tools used
today.
Page 20 of 69
BOOK STORE SYSTEM

Some of the main features of Visual Basic 6.0 are listed below:
Data Access features allows you to create database and front-end
applications for most popular database formats, including Microsoft SQL
Server, Oracle, Microsoft Access and other enterprise level database.
It includes a GUI environment fro making windows based applications.
Active X technology allows you to use the functionality provided by other
application such as MS Word, MS Excel and other Windows
applications. You can even automate applications and professional or
enterprise editions of Visual Basic.
Internet capabilities make it easy to provide access to documents and
applications across the Internet from within your application.
It provides a vital link to graphical environment and allows you to
develop applications based on standard Windows features: Dialog
Boxes, Command buttons, Pull down menus, Scroll bars, Selection lists
etc. It also allows creating robust applications that fully make use of the
graphical user interface.
A multitude of wizards and other graphical tools aid developers new to
Visual Basic.
ADO-compliant data-bound controls.
Hierarchical record sets and the Flex Grid Control.
Visual Basic is an event driven programming language.
Page 21 of 69
BOOK STORE SYSTEM

Visual Basic allows you to adopt more of parallel approach, with
independent sections of code for each option that the user may select.
This is known as Event driven programming language.
Visual data tools (VDTS).
ADO Data Control (ADODC).
Data report design and Data form wizards.
It also helps the user with the SQL editor.
By connecting it with Oracle, SQL statements can be run and terminated
through Visual Basic 6.0.
Visual Basic Component creation.
The language is very easy and it provides a very user-friendly
environment while programming in Visual Basic 6.0.
Packaging and Deployment wizard.
Allows for the creation of p-code and native code EXE files. p-code is a
tokenized from of your source code that will be broken down at runtime
into machine code, which is why Visual
Basic will create this
intermediately forms.
Can be extended easily through the use of windows API calls, hundreds
of third party controls and DLLs, and integration with other windows
applications through COM and DCOM.
Has a shorter learning curve and development time than C/C++, Delphi,
and even Power Builder.
Page 22 of 69
BOOK STORE SYSTEM

Used by most of the office suite tool as macro language. With the rest to
follow. Other companies as well are starting to support VBA in their
products, such as AutoCAD, Vision, CorelDraw, SAP, and many others.
Allows for rapid application development and is excellent for business
applications.
Has an excellent integrated help facility and book online as well as it
includes good debugging facilities and have many wizards that help
automated repetitive tasks.
Object-based development is possible using class modules and rapid
application development (RAD).
Allows for the creation of COM components such as Active X controls,
DLLs, and Execs.
Can integrate with the Internet on both the server side and the client
side.
Can create Active X Automation server.
Integrates with Microsoft transaction server.
Can run server either on the same machine or remotely on another
computer. This allow for true distributed processing.
ADVANTAGES OF VISUAL BASIC 6.0: During design time, it is possible to see how the program will look at the
runtime.
Page 23 of 69
BOOK STORE SYSTEM

Visual Basic is very useful in designing and developing, effective and
efficient windows based programs
VB helps in making your program look quite effective and beautiful.
You can add menus, tool bars, status bars, text boxes, etc. to blank
window.
It is less time consuming and more users friendly. Also user-friendly
programs can be developed very easily.
DISADVANTAGES OF VISUAL BASIC 6.0: The programs that are developed utilize more memory.
Visual Basic requires specific operating system, which supports visual
programming.
Graphical User Interface is provided by visual basic, which takes some
more time then other non-visual programming for execution of the
program.
Oracle 8.0 [Back End]:

Oracle 8 is a Relational Database Management system (RDBMS) from Oracle
Corporation. Oracle 8.0 extends the tradition of the industry leading Oracle 7.6 and
other older versions of Oracle, with major enhancements in performance, scalability,
functionality, manageability and reliability. This helps greatly in viewing transaction log
contents, includes object functionality at no cost etc. The Oracle Enterprise Manager
supports easy to use console to manage the Oracle environment. There is fast-start
fault recovery, improved standby databases, online index builds and large databases.
Some of the features of oracle 8.0 are listed below:
Page 24 of 69
BOOK STORE SYSTEM

Central, easy -to-use GUI, distributed database management using
Oracle Enterprise Manager. Also Oracle 8 provides various tools for
managing different task.
Provides object-relation features such as abstract data type, object
views etc.
It eliminates all parent-child relationships and instead represented all
data in the database as simple row/column tables of data values.
Easy access to all data.
Reduce data storage and redundancy.
Professional ORACLE starts the DBMS (database management system)
in the extended memory, so more main memory is available for other
applications.
Relational model of data management is based on SET theory. Built-in
query language is designed in the RDBMS, so that it can manipulate
sets of data (one or more tuples).
User interface used with relational models is non-procedural because
only what needs to be done is specified and not how it has to be done.
Using any of the other methods, you have not only to specify what need
to be done but how it has to be done as well.
Each table is an independent entity and there is no physical relationship
between tables.
User requests for table data are simply not entertained, unless the
RDBMS engine in oracle is loaded.
Page 25 of 69
BOOK STORE SYSTEM

Oracle has special features of updating the database, retrieving
information from database, enforcing security specifications, enforcing
transaction consistency, data sharing, optimizing SQL statements i.e.
queries, and it also enforces security specifications.
FEATURES OF PROPOSED SYSTEM

The Book Store System of the Book Store is developed to overcome the
most of the problems occurring in the manual system by computerizing the existing
system. The features of the newly proposed computerized system are described in
brief as below:
After computerizing the system, the owner of the Book Store or the user of the
system can finish their work in least amount of time and efforts. The computerized
system has many gains and efforts, which the manual system cant give, in any type of
situations.
In any manual system if we take, the main problem arising is to maintain the
number of records and finding a particular record. The user here have to calculate the
amount of particular item depending on the rate and quantity of items sale or
purchase, but in the case of computerized system the user just has to enter the
Page 26 of 69
BOOK STORE SYSTEM

quantity and rate the computer will automatically will be calculating the amount of a
particular item and the grand total also will be calculated.
Computerized system helps the user by providing the accounting details of the
current time period and also provides the facility of producing the monthly reports for
monthly sale or monthly purchase so the owner can check whether the company is
doing loss or profit. With this he can also prepare reports, graphs or charts of profit
and loss of the Book Store.
Computerized systems are most helpful in dealing with areas where database
comes into the existence. A computer can hold large amount of data in its storage
devices and it can operate at very high speed. The user can put the entire information
in the computer and can be able to perform any type of task which when done
manually is tedious and time consuming. The new system will have the facility to sort
data according to any specific type on the basis of what the user wants in any order.
Also with the help of computerized system if the user wants to access any single
users data from many users data he can automatically get the desired data of the
desired Book or Vendor in a fraction of second which is again time saving and very
quick.
Page 27 of 69
BOOK STORE SYSTEM
Page 28 of 69
BOOK STORE SYSTEM
5) SYSTEM DESIGNING
5.1) DATA FLOW DIAGRAM
5.2) DATA DICTIONARY
5.3) I/O SCREEN OF PROPOSED SYSTEM
(5) SYSTEM DESIGNING

(5.1) DATA FLOW DIAGRAM(s) [D. F. D.] & CONTEXT LEVEL
DIAGRAM
The data flow diagrams are pictorial or graphical representation of the outline of
the system study. The data flow diagram covers all the processes and data storage
area, which takes place during any transaction in the system. The data flow diagrams
are functionally divided into context level, Zero level and first level data flow diagrams.
Symbols used in DFDs:

(1) Process: Here flow of data is transformed. e.g. Purchase of Books,
update inventory file, etc.
Page 29 of 69
BOOK STORE SYSTEM

(2) External Entity: A source or destination of data, which is external to the
system. E.g. Party, Client etc.
(3) A data flow: It is packet of data. It may be in the form of document, letter
etc.
(4) Data store: Any store data but with no reference to the physical method
of storing.
Page 30 of 69
BOOK STORE SYSTEM
Page 31 of 69
BOOK STORE SYSTEM
DATA FLOW DIAGRAM
Page 32 of 69
BOOK STORE SYSTEM
DATA FLOW DIAGRAM
Page 33 of 69
BOOK STORE SYSTEM
DATA FLOW DIAGRAM
(5.2) DATA DICTIONARY
Page 34 of 69
BOOK STORE SYSTEM

The data dictionary of any system is an integral component of structure
analysis, since data flow diagrams by themselves do not fully describe the subject
under investigation about the system.
A data dictionary is a catalog a repository of the elements in the system.
These elements center on data and the way they are structured to meet user
requirements and organization needs.
This step of creating a data dictionary is
simultaneous with the process of making data flow diagram(s). Here all the data fields
in their respective tables are allotted so as to access these data in the system. The
data tables are created in a back-end tool like Microsoft Access, Oracle, FoxPro,
etc. Here in the Book Store System we are using tables created in Oracle8.0, as it is
the back-end tool used in the system.
The data dictionary consists of different major elements like Data Elements,
Data Store [Tables Used], Data Flow, Processes and other External entities used in
the system. The data dictionary stores details and description of these elements.
It is developed during data flow analysis and assists the analysts involved in
determining the system requirements. Analysts use data dictionary for the following
important reasons:
To manage the details in large system.
To communicate a common meaning for all system elements.
To document the features of the system.
To facilitate analysis of the details in order to evaluate the characteristics
and determine where system changes should be made.
To locate errors and omissions in the system.
Page 35 of 69
BOOK STORE SYSTEM
The data dictionary contains different types of descriptions for the data flowing
through the system:
Data Elements is the most fundamental level, which is also considered as the
building block for all other data in the system. It refers to all the different data used like
fields, data item, etc. to make the system fully functional irrespective to the table used
in the system. Here all the different type of fields used to make table are written
sequentially without referring to the tables. This process helps in the process of
Normalization of tables.
Next to Data Elements comes the Data storage which provides the information
of where and how each data element is stored in which table and it also give
information of any constraints if there. This step also gives knowledge of different data
types used for different field and their size. All the normalized tables are showed in
data storage.
Data Flow stage shows the flow of data in the system. This step is can be
already seen in the data flow diagrams above in this document. This step refers to all
the data flow paths were transactions are done in the computerized system.
The data flow step also includes different processes used in the system and it is
followed by External Entities used in the system.
Page 36 of 69
BOOK STORE SYSTEM

DATA STORE [TABLE USED]
Described below in detail.
The above tables are described briefly and can be understand
clearly from below. Each table is described along with different fields
used, their data types, their size and constraints if any.
The description of tables is as follows:
Login
Objective: The Login table contains the information about the different users and their
passwords, which are used to access the system as there are more than one users in
the Book Store System and they can access data privately. The table stores the data
as username and password and thus provides security to the system. This table also
contains the administrator user and its password, so all the rights are provided to the
administrator and some rights are not provided by the system to some local users.
Tables Referred: Login
Table Format:
Field name Field description Type
Size Constraint
User login
User Name
Varchar2 20
No
Password
Password
Varchar2 20
No
Question
User question
Varchar2 50
No
Answer
User answer
Varchar2 50
No
Validations:
Page 37 of 69
BOOK STORE SYSTEM

The table does not allow to the user to enter blank record as both fields are not null
and it will show an error message if the any of the field i.e. Login or the user while
creating new user for the system keeps password null.
Provides an error message on getting incorrect username or password with error
message and does not allow entering in the system without correct username or
password. The system owner or administrator through the system can create new
user.
Primary Key: User login
Reference Key:
No reference key in this table.
Author Master
Objective: The Author Master table contains the information about the different
Authors related to books.
Tables Referred: Author Master
Table Format:
Field
Field
Type
Size
Constraint
name
description
Acode
Author Code
Varchar2
Primary Key
Aname
Author Name
Varchar2
30
Not null
Validations:
The table does not allow to the user to enter blank field those are required as those
fields are not null and it will show an error message if the any of the field which is
required is kept null by the user while doing any transaction using this table. Moreover,
in the author name cannot be entering any numerical.
Primary Key:
Acode
Page 38 of 69
BOOK STORE SYSTEM

Reference Key:
No Reference key is there in this Table.
Publisher Master
Objective: The Publisher Master table contains the information about the different
Publishers related to books.
Tables Referred:
Publisher Master
Table Format :
Field name
Field description
Type
Size Constraint
Pcode
Publisher Code
Varchar2
Primary Key
Pname
Publisher Name
Varchar2
30
Not null
Validations:
required is kept null by the user while doing any transaction using this table. Moreover,
in the publisher name cannot be entering any numerical.
Primary Key:
Reference Key:
Pcode
No Reference key is there in this Table.
Book Master
Objective: The Book Master table contains the information about the different Books.
Tables Referred: Book Master
Table Format:
Page 39 of 69
BOOK STORE SYSTEM

Field name
Field description
Type
Size Constraint
Bcode
Book Code
Varchar2
Primary Key
Bname
Book Name
Varchar2
30
Not Null
Pucode
Publisher Code
Varchar2
Foreign Key
Pname
Publisher Name
Varchar2
30
Not Null
Bprice
Book Price
Number
Not Null
Isbn Code
Isbn code
Varchar2
20
Edition
Book Edition
Varchar2
20
Aname
Author name
Varchar2
30
Not null
Validations:
required is kept null by the user while doing any transaction using this table.
Moreover, in the book name cannot be entering any numerical.
Primary Key:
Bcode
Reference Key: Acode from Author Master table.

Pcode from Publisher Master table.
Vendor Master
Objective: The Vendor Master table contains the information about the different
Vendors. Thus the table contains the personal information of different Vendors.
Page 40 of 69
BOOK STORE SYSTEM

Tables Referred:
Vendor Master
Table Format :
Field name
Field description
Type
Size
Constraint
Vcode
Vendor Code
Varchar2
Primary Key
Vname
Vendor Name
Varchar2
30
Not null
Add1
Address of the Vendor
Varchar2
50
Not null
Add2
Varchar2
50
City
City
Varchar2
30
Pincode
Pincode
Number
State
State
Varchar2
20
Country
Country
Varchar2
20
Phone
Phone number
number
15
Not null
Fax
Fax Number
Varchar2
15
Email
Email address
Varchar2
30
Validations:
Moreover, in the vendor name, state, country cannot be entering any numerical.
Primary Key:
VCode
Reference Key:
No Reference key is there in this table.
Purchase Transaction
Page 41 of 69
BOOK STORE SYSTEM

Objective: The Purchase transaction table contains the information about the different
Books that are purchased in the bookstore.
Tables Referred: Purchase Transaction
Table Format :
Size Constraint
Pcode
Purchase code
Varchar2 6
Primary key
Bcode
Book code
Varchar2 6
Foreign key
Bname
Book name
Varchar2 30
Acode
Author code
Varchar2 6
Foreign key
Aname
Author name
Varchar2 30
Pucode
Publisher code
Varchar2 6
Foreign key
Puname
Publisher name
Varchar2 30
Qty
Quantity of book
Number
Rate
Book rate
Number
8,2
Discount
Book discount
Number
Amt
Book amount
Number
10,2
Pdate
Purchase date
Date
Not null
Validations:
The table does not allow to the user to enter blank field because not all the fields are
null and it will show an error message if the any of the field which is required is kept
null by the user while doing any transaction using this table.
Primary Key:
PCode
Reference Key:
Bcode from book Master Table
Acode from Author Master Table

Pucode from Publisher Master Table
Page 42 of 69
BOOK STORE SYSTEM

Customer Master
Field name
Field description
Type
Size
Constraint
Ccode
Customer Code
Varchar2
Primary key
Cname
Customer Name
Varchar2
30
Not null
Address
Varchar2
50
City
City
Varchar2
25
Pincode
Pincode
Number
10
Phone
Phone Number
Number
15
Validations:
Moreover, in the customer name cannot be entering any numerical.
Primary Key:
Ccode
Reference Key:
No Reference key is there in this table.
Sales Transaction
Objective: The Sales Transaction table contains the information about the different
Books that are sales in the bookstore.
Tables Referred: Sales Transaction
Table Format :
Scode
Sales code
Size Constraint
Varchar2 6
Page 43 of 69
Primary key
BOOK STORE SYSTEM

Bcode
Book code
Varchar2 6
Foreign key
Bname
Book name
Varchar2 30
Acode
Author code
Varchar2 6
Foreign key
Aname
Author name
Varchar2 30
Pucode
Publisher code
Varchar2 6
foreign key
Puname
Publisher name
Varchar2 30
Qty
Quantity of book
Number
Rate
Book rate
Number
8,2
Discount
Book discount
Number
Amt
Book amount
Number
10,2 -
Sdate
Sales date
Date
Not null
Validations:
The table does not allow to the user to enter blank field because all the fields are not
null and it will show an error message if the any of the field which is required is kept
null by the user while doing any transaction using this table.
Primary Key:
Pcode
Reference Key: Bcode from book Master Table

Acode from Author Master Table
Pucode from Publisher Master Table
Page 44 of 69
BOOK STORE SYSTEM
(5.3) I/O SCREENOF PROPOSED SYSTEM

This section refers to the various types of interfaces, which the user has to face
during operating the computerized system of Book Store System.
The section refers with the entire interface [Screens] a user will have to face
while operating the current system. It shows the various screens appearing for
different transactions. All the screens of different transactions in the system are shown
here. The different transactions screens shown here are in the below given order:
Login Screen.
Main System Screen.
Master.
Customer Master
Author Master
Publisher Master
Book Master
Vendor Master
Transaction
Page 45 of 69
BOOK STORE SYSTEM
Purchase
Sales
Reports
Book Information Report
Vendor Information Report
Customer Information Report
Publisher Information Report
Author Information Report
Current Stock Report
Daily Sales Report
Monthly Sales Report
Yearly Sales Report
Sales Report
Purchase List
About Developer
Add User
Exit
Page 46 of 69
BOOK STORE SYSTEM
SCREENS
LOGIN:
The above given screen is the user login screen in which the user can logon the
system.
Page 47 of 69
BOOK STORE SYSTEM
MAIN SCREEN
The above given screen is the main screen of the system.
Page 48 of 69
BOOK STORE SYSTEM

CUSTOMER MASTER
The above given screen is the user login screen in which the user can
logon the system.
The above given screen is the customer master screen in which the user can add
new customer, save, edit, delete, search a particular customer, cancel the operation,
and finally exit from the form.
Page 49 of 69
BOOK STORE SYSTEM

PUBLISHER MASTER
The above given screen is the publisher master screen in which the user can add
new publication, save, edit, delete, search a particular publication, cancel the
operation, and finally exit from the form.
BOOK MASTER
Page 50 of 69
BOOK STORE SYSTEM
The above given screen is the book master screen in which the user can add new
book, save, edit, delete, search a particular book, cancel the operation, and finally exit
from the form.
VENDOR MASTER
Page 51 of 69
BOOK STORE SYSTEM
The above given screen is the vendor master screen in which the user can add new
vendor, save, edit, delete, search a particular vendor, cancel the operation, and finally
exit from the form.
Page 52 of 69
BOOK STORE SYSTEM

PURCHASE TRANSACTION
The above given screen is the purchase transaction screen in which the user can add
new purchase book, save, edit, delete, search a particular purchase book, cancel the
operation, and finally exit from the form.
Page 53 of 69
BOOK STORE SYSTEM

SALES TRANSACTION
The above given screen is the sales transaction screen in which the user can add
new sales book, save, edit, delete, search a particular sales book, cancel the
operation, and finally exit from the form
Page 54 of 69
BOOK STORE SYSTEM

BOOK INFORMATION REPORT
The above screen displays the publisher code, author name, book name,
publisher name, book price, and ISBN code, book edition.
Page 55 of 69
BOOK STORE SYSTEM

VENDOR INFORMATION REPORT
The above screen displays the vendor name, address, city, pin code, state,
country ,phone number, fax number and email address.
Page 56 of 69
BOOK STORE SYSTEM

CUSTOMER INFORMATION REPORT
The above screen displays the customer code, author name, book name,
publisher name, book price, and ISBN code, book edition.
Page 57 of 69
BOOK STORE SYSTEM

PUBLISHER INFORMATION REPORT
The above screen displays the publisher code, publisher name.
Page 58 of 69
BOOK STORE SYSTEM

AUTHOR INFORMATION REPORT
The above screen displays the author code, author name.
Page 59 of 69
BOOK STORE SYSTEM

CURRENT STOCK REPORT
The above screen displays the sales code, author name, book name,
publisher name, book quantity, sales date.
Page 60 of 69
BOOK STORE SYSTEM

DAILY SALES REPORT
The above screen displays the sales date, author name, book name,
publisher name, book quantity, book price, and discount of book, book
amount.
Page 61 of 69
BOOK STORE SYSTEM

MONTHLY SALES REPORT
amount.
Page 62 of 69
BOOK STORE SYSTEM

YEARLY SALES REPORT
amount.
Page 63 of 69
BOOK STORE SYSTEM

SALES REPORT
The above screen displays the sales code, book name.
Page 64 of 69
BOOK STORE SYSTEM

PURCHASE LIST
The above screen displays the author name, book name, publisher name,
book quantity, book price, and discount of book, book amount, and
purchase date
Page 65 of 69
BOOK STORE SYSTEM

ABOUT DEVELOPER
The above screen displays the information about developer, system

information.
ADD USER
Page 66 of 69
BOOK STORE SYSTEM
The above screen you can change the ser password, user question, user
answer also add user, edit, save, cancel operation, delete the user, search
the particular user and last exit the form.
EXIT
Page 67 of 69
BOOK STORE SYSTEM
The above screen displays c the exit of system.
Page 68 of 69
BOOK STORE SYSTEM

References
Mastering Visual Basic 6
Evangelos Petroutsos
WWW.GOOGLE.COM
Page 69 of 69

Bookstore System

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Bookstore System

Caricato da

Copyright:

Formati disponibili

BOOK STORE SYSTEM