U.P.

TECHNICAL UNIVERSITY
LUCKNOW

IIMT MANAGEMENT COLLEGE

DEPARTMENT OF MCA

PROJECT REPORT

ON

BOOK SHOP MANAGEMENT

SYSTEM

SUBMITTED TO SUBMITTED BY
Mr. Tushar Agarwal Veeresh pal Singh
& Sunil Kumar Sharma
Mrs. Anjali Sharma Aakankshi Sharma
ACKNOWLEDGEMENT
When we got the opportunity to do a work on Book Shop Management

System, it is challenge for us to do better in development field. We

take this challenge and finished the work with our hard working and

technical skill. We take this opportunity to express our gratitude to

them, whose guidance helped me bridge the gap between academics

and industry.

We are grateful to our project guide Mr. Tushar Agarwal & Miss.Neha

Mam for the guidance, inspiration and constructive suggestions that

helpful us in the preparation of this project.

We also thank our colleagues who have helped in successful

completion of the project. Last but not the least; I would like to extend

our gratitude towards our parents, who have always been our source

of inspiration and motivation.

Veeresh pal Singh

Sunil Kumar Sharma
Aakankshi Sharma
 INDEX
1) Synopsis

2) Introduction & Objective

3) System Analysis

4) Feasibility Study

4.1. Technical Study

4.2. Economical Study

4.3. Operational Study

4.4. Behavioral Study

5) Software Engineering Paradigm Applied

6) System Design Specification

6.1. Data Flow Diagram (DFD)

6.2. ER Diagram

6.3. Data Table

7) Snapshots

8) Code Efficiency

9) Optimization of codes

10) Testing

11) Implementation & Maintenance

12) Conclusion

13) Bibliography
Synopsis
 Preface
Book Shop Management System

A Book Shop Management system is basically for management of

incoming and outgoing material from the Book shop It also maintain
management of all incoming and outgoing finance from the Shop
account section. It will reduce paper work & work load of user.

To reduce the Paper work and provide fast service to customers.

The main objective is to provide the customers fast and error

free transaction.

It can be used in any Book Shop for maintaining database details

and their quantities.

This project is used for handle user needs. It must be outgoing

process to know requirements of customer during whole system
development life cycle.

Following are some of the inputs to the Book Shop

o Database
o Quantities of the products

System will help to produce following outputs

 Customer bill receipt
 Rate List
 Current Quantities of the products

System Requirement Analysis

Identification of Problem Areas and
Needs:

Identifying needs is the first step while designing a system and

implementation. This is the way to handle user needs.lt must be an
outgoing process to know requirements of customer during whole
system development life cycle.
During this phase the main things to be considered are got by placing
meetings and questionnaires with customer.
Requirements found during all the stages proposed system
development are:-

 How the present system work.

 Time take to operate the system.
 List of contents associated with the system.
 Error/failure rate to be acceptable.
 Risk factors involved.
 Proprietary aspects, liability risks, potential infringement, and
political issues to consider.
 Human-machine and machine-machine communication.
 Interfacing with external environment.

Question we asked with customer for gathering requirements

 during questionnaires. Some of those queries are as follows:-

 Who will the solution?

 Economical benefit of a successful solution.
 Other source of solution.
 Knowledge of the environment in which the proposed
system will be used.

For better understanding of customers need study of existing

system, application requirement, and scope of proposed system
must be known.

Study of Existing system:

Existing system worked very slowly and the management of the
news is not properly work. The existing system was not keep the
information of the news that which news or story assigned to which
person.

Drawbacks of existing system:-

 Following drawbacks were released in the existing
system by the company on its own-

 There was no way of providing automatic flow of product

on each user.
 The major drawback was the requirement of hard coding
and much of the manual interaction and dependency.
 Difficult to maintain the records of all types of incoming &
outgoing product.

General Constraints :-
 The project can run any operating system where java 1.5
and MS-Access are installed.
 GUI is only in English.
 Login and password is used for identification of user and
there is no facility for guest.

Assumption and Dependencies

 To use this software user have must authentication (user id and
password).

Project Requirements

Hardware Requirements

Processor RAM Disk Printe Monito Keyboard

spac r r & Mouse
e
Intel 64 Mb 130 Ink jet VGA Multimedia
Pentium IV, or Mb or enabled
Dual core, higher Laser
Core 2 Duo Printer
or higher
Software Requirements
Operating Language Database
system
Win-XP, Java 1.5 or MS-Access
Windows 7 above

Definitions of Problems
Problems with conventional system
1. Lack of immediate retrievals
The information is very difficult to retrieve and to find particular
information like- E.g. - To find out about the patient’s history, the
user has to go through various registers. This results in
inconvenience and wastage of time.

2. Lack of immediate information storage

The information generated by various transactions takes time
and efforts to be stored at right place.

3. Lack of prompt updating

Various changes to information like patient details or
immunization details of child are difficult to make as paper work
is involved.

4. Error prone manual calculation

Manual calculations are error prone and take a lot of time this
may result in incorrect information. E.g.- calculation of
patient’s bill based on various treatments.

5. Preparation of accurate and prompt reports

This becomes a difficult task as information is difficult to collect
from various registers.

Alternative Solutions
1. Improved Manual System
One of the alternative solutions is the improvement of the
manual system. Anything, which can be done by using
automated methods, can be done manually. But the question
arises how to perform thing manually in a sound manner.
Following are some suggestions, which can be useful in the
manual system.
A more sophisticate register maintenance for various Patient
Information, Doctor diary, Immunization Details and a good
system for writing bill amount employees and stock availed for
the customers can be maintained at central place. Adequate
staff may be maintained so that updations are made at the very
moment at the same time. Proper person for proper work should
be made responsible so that a better efficiency could be
achieved. This needs a lot of work force.
2. Batch System
Another alternative solution can be used of computer based
batch system for maintaining the information regarding purchase
details, customers and employees. A batch system refers to a
system in which data is processed in a periodical basis.
The batch system is able to achieve most of the goals and sub
goals. But a batch system data is processed in sequential basis.
Therefore batch system is not suggested.
3. Online System
This system (HMS) provides online storage/ updations and
retrieval facility. This system promises very less or no paper
work and also provides help to Doctor and operational staff. In
this system everything is stored electronically so very less
amount of paper work is required and information can be
retrieved very easily without searching here and there into
registers. This system is been discussed here.
Limitation of the Project
Though the system has been designed according to the
requirements of the users it has its own limitation. Thus the limitation
of system are-
 No facility to create new users with different roles
 Object oriented Approach has been not been fully utilized.
PROJECT
 Introduction and Objective
A Book Shop Management system is basically for management of
incoming and outgoing material from the Book shop It also maintain
management of all incoming and outgoing finance from the Shop
account section. It will reduce paper work & work load of user.
The main objective is to provide the customers fast and error
free transaction.
 System Analysis
Before developing any new system anywhere, it is imperative
upon the developers to acquaint themselves with environment in which
the proposed system would be installed. Also, it is necessary to
interact with the user regarding their demands and the resources
available with them. This gives a clear overview of the improvements
wanted and to be provided.
The study and analysis of the proposed system was carried out
diligently under the guidance of experts of the organization. In the
existing system, all the work is being carried out manually. Computers
available are just for typing in the excel sheets. Besides him, we have
checked an earlier package being done in FoxPro and the reports
created in Excel sheets for more hints.

Limitations

At Present, whenever some report is needed, it is being created

using excel, word after entering the collected data. To say that is
highly inefficient is of no use. Everyone recognize it and thus the work
in the direction of new system was started.
The worst problem with the manual work is speed of work. Many
things need to be re-entered repeatedly. The Project was undertaken
as a part of the drive to convert the existing computerized system at
work into a modern system.
Analysis is a detailed study of the various operations performed by a
system and their relationships within and outside of the system. One
aspect of analysis is defining the boundaries of the system and
determining whether or not a candidate system should consider other
related systems. It is fact-finding followed by analysis of the facts. It
provides a framework to assist in perceiving system weakness and
requirements. It also identifies strategies for fulfilling the stated
requirements, a basis for the transition into system design.

Feasibility study
Depending on the results of the initial investigation the survey is
now expanded to a more detailed feasibility study. “FEASIBILITY
STUDY” is a test of system proposal according to its workability,
impact of the organization, ability to meet needs and effective use of
the resources. It focuses on these major questions:
1. What are the user’s demonstrable needs and how does a
candidate system meet them?
2. What resources are available for given candidate system?
3. What are the likely impacts of the candidate system on the
organization?
4. Whether it is worth to solve the problem?
During feasibility analysis for this project, following primary areas of
interest are to be considered. Investigation and generating ideas about
a new system does this.
Steps in feasibility analysis
Eight steps involved in the feasibility analysis are:
 Form a project team and appoint a project leader.
 Prepare system flowcharts.
 Enumerate potential proposed system.
 Define and identify characteristics of proposed system.
 Determine and evaluate performance and cost effective of
each proposed system.
  Weight system performance and cost data.
 Select the best-proposed system.
 Prepare and report final project directive to management.
Feasibility study is the procedure to identify, describe the evaluate
candidate system and select the best possible action for the job. The
initial investigation culminated in a proposal summarized the thinking
of the analyst, was presented to the user for review. The proposal
initiated a feasible study to describe and evaluate the best system to
choose in terms of economical, technical and behavioral constraints.

The terms constraints involved in feasibility analysis are-

• Technical
• Economical
• Operational
• Behavioral

Technical Feasibility

A study of resource availability that may affect the ability to achieve

an acceptable system. This evaluation determines whether the
technology needed for the proposed system is available or not.
• Can the work for the project be done with current
equipment existing software technology & available
personal?
• Can the system be upgraded if developed?
• If new technology is needed then what can be developed?
This is concerned with specifying equipment and software that will
successfully satisfy the user requirement. The technical needs of the
system may include:
Front-end and back-end selection

An important issue for the development of a project is the selection of

suitable front-end and back-end. When we decided to develop the
project we went through an extensive study to determine the most
suitable platform that suits the needs of the organization as well as
helps in development of the project.
The aspects of our study included the following factors.

Front-End selection
1. It must have a graphical user interface that assists
employees that are not from IT background.
2. Scalability and extensibility.
3. Flexibility.
4. Robustness.
5. According to the organization requirement and the
culture.
6. Must provide excellent reporting features with good
printing support.
7. Platform independent.
8. Easy to debug and maintain.
9. Event driven programming facility.
10.Front end must support some popular back end like Ms
Access.
According to the above stated features we selected Java 1.6 as the
front-end for developing our project.
Back-End Selection
1. Multiple user support.
2. Efficient data handling.
3. Provide inherent features for security.
4. Efficient data retrieval and maintenance.
5. Stored procedures.
6. Popularity.
7. Operating System compatible.
8. Easy to install.
9. Various drivers must be available.
10. Easy to implant with the Front-end.
According to above stated features we selected Ms-Access as the
backend.
The technical feasibility is frequently the most difficult area
encountered at this stage. It is essential that the process of analysis
and definition be conducted in parallel with an assessment to technical
feasibility. It centers on the existing computer system (hardware,
software etc.) and to what extent it can support the proposed system.

Economic Feasibility
Economic justification is generally the “Bottom Line”
consideration for most systems. Economic justification includes a
broad range of concerns that includes cost benefit analysis. In this we
weight the cost and the benefits associated with the candidate system
and if it suits the basic purpose of the organization i.e. profit making,
the project is making to the analysis and design phase.

The financial and the economic questions during the preliminary

investigation are verified to estimate the following:
• The cost to conduct a full system investigation.
• The cost of hardware and software for the class of application
being considered.
• The benefits in the form of reduced cost.
• The proposed system will give the minute information, as a
result the performance is improved which in turn may be
expected to provide increased profits.

Operational Feasibility

It is mainly related to human organizations and political aspects.

The points to be considered are:
• What changes will be brought with the system?
• What organization structures are disturbed?
• What new skills will be required? Do the existing staff
members have these skills? If not, can they be trained in due course of
time?
The system is operationally feasible as it very easy for the End
users to operate it. It only needs basic information about Windows
platform.
Behavioral Feasibility
After considering the following point that the system is
behaviorally feasible. The project is carried out on the request of the
users. To a greater extent, the proposed system aims at maximizing
user friendliness. This is intended to overcome resistance to change by
the exiting staff. Users are quite experienced in handling the
computerized system. Users are aware of the software and hardware
environment.

Software Engineering Paradigm Applied

Purpose
 Purpose of any information system is to create reports out of the
data provided. It does this work methodically however compared to a
manual system. To achieve this goal, an information system has many
parts.
Here, we describe the system as finally envisaged and is under
implementation phase. The description ranges from the input
identified, output needed & input design, database design, form design
and report design. It also included process specification.

Software Engineering
Software Engineering is comprised of set of steps that
encompasses methods, tools and procedures. These steps are often
referred to as software engineering paradigms. A paradigm for
software Engineering is chosen based on the nature of the project and
application, the methods and tools to be used and the controls and
deliverables that are required.
The four paradigms widely discussed are
• The classical life cycle
• Prototyping
• The Spiral model
• Fourth Generation techniques
The classical life cycle paradigm is chosen for this project as per the
organization standards.

The Classical Life Cycle

The classical life cycle paradigm is often called as the “Water

Fall” model. The life cycle paradigm demands a systematic, sequential
approach to software development that begins at the system level and
progress through analysis, design, coding, testing and maintenance.

System Engineering and Analysis

As software is always a part of larger system, works begins by

establishing requirements for all system elements and then allocating
some subset of these requirements to software. This system view is
essential when software must interface with other elements such as
hardware, people and databases. System Engineering and analysis
encompasses requirement gathering at the system level with the small
amount of top level design analysis.
To solve actual problem in industry setting a software engineer
or team of engineers must incorporate a development strategy that
encompasses the process methods and tools layers. This strategy is
often referred to as process model or a software engineering is chosen
based on the nature of the project and application, the method and
tools to be used and the controls and deliverables that are required.
This project contains various modules and the nature of these modules
areas we choose Sequential Model or Waterfall model or classic life
cycle model. This Software engineering paradigm suggests a
systematic, sequential approach to software development that starts
right from system level and goes through planning, analysis, design,
coding, testing and maintenance.

System/information Engineering and modeling

System Engineering and analysis encompasses recruitments gathering

at the system level with a small amount of top level analysis and
design. Information engineering encompasses requirement gathering
at the strategic business level and at the business area level.

System requirements analysis

In this phase of this paradigm, requirements for both the system

and software are documented and reviewed with the customers.

Design

Software design is an actually a multi step process that focuses

on four distinct attributes of program namely data structure, software
architecture, interface representation and procedural details. The
design process translates requirements into a representation of the
software that can be assessed for quality before code generation
begins. The design is documented and is part of the software
configuration.

Code Generation
The design must be translated into a machine readable form.
The code generation steps perform this task.

Testing
The testing process focuses on the logical internals of the
software assuring that all statements have been tested and on the
functional externals that is conducting tests to uncover errors and
ensure that defined input will produce actual results that agree with
required.

Maintenance
Software will undoubtedly undergo changes after it is delivered
to the customer. Change will occur because errors have been
 encountered, because the software must be adapted to accommodate
changes in its maintenance reapplies each of the preceding phrases to
an existing programmer rather than a new one.

Paradigm Applied in this Project

Data Design

Design
Planning
 Implementation

Analysis

System Design

Design

Design

Implementation

Design Implementation

Implementation

Interface design

System
 System Analysis (DFDs, ER diagram)

Data inputs
Book Shop Admin
Admin
Management
System
Various reports

DFD: Level 0
 Admin
Login_db

login Stores & Retrieves

Login
sells
sells gives
book_db
takes
Stores & Retrieves
Book
s

Registers
Stationary
Stores & Retrieves stores& retrives

Back up Reg_db
stationary_db
stores & Retrieves

backup_db
buy buy

buy
Registers buy
USER

DFD: Level 1
 Admin
Book_db

stores
Books
Competitio
n books
stores
Purchase
Return Register compt_db

stores

Practical Stationar register_db

tools y
Buy

USER

pract_db stationay_db

buy buy

user

DFD: Level 2
 cust_fee_db

Receipt
Query Admin

Stores & retrieves

cust_fee_db Gives

Stores & retrieves

Accumulate
d Receipt Stores
cust_fee_db
Request

Request stores & retrives

User Request
Customer
Receipt
Entry

DFD: Level 3
 Entity Relationship Diagram

BSMS

User Hav Admin

e

bu
y Tak do
do e sells
do
Compition book

id name

Backup Login Recharge

book_ registration

book_id book_typ
book_id
e nl
mrp s
name uid passw
ord b
date Author
name
ai
tat rt
a el
 Data Tables
1. Login Table

Field Name Data type Width Description

User_name Text 20
Password Text 10

2.Book Information table

Field Name Data type

Book_Name Text
Author Name Text
Pub Text
Pur_Price Number
MRP Number
Qty Number
Rack no number
Dealer_Name Text
Date Date

2. Register Information table

Field Name Data type

Brand Name Text
Price Number
Mrp Number
Qty Number
Rack_No Number
Dealer Name Text
Date Date
3. Stationary Information Table

Field Name Data type

Item_Name Text
Price Number
MRp Number
Qty Number
Rack no Number
Dealer name Text
Date date

4. Recharge Information Table

Field Name Data type

Company Text
Name
Amount Number
Date Date

5. Practicals Tools Table

Field Name Data type

Item_Name Text
Price Number
MRP Number
Qty Number
Rack no Number
Dealer Name Text
Date Date
6. Competition Books Table

Field Name Data type

Book_Name Text
Price Number
MRP Number
Qty Number
Rack No Number
Dealer Name Text
Date Date
 Snapshots

1. Login Form
2.Home Page
3.Home Page with MenuItem
3.Book Information
4.Book Information With Return Back to Home Page
5.Register Information
6.Stationary Information
7.Recharge Information
9.Practical Tools Information
10.Compitition Books Information
 Code Efficiency
The amount of computing resources and code required by a
program to perform its function is known as code efficiency. The box-
structured specifications represented in a language are translated into
the appropriate programming language. Standard walkthrough or
inspection techniques are then used to ensure semantic conformance
of the code and correctness of the codes.
The correctness verification is also conducted for the source
code. To overcome the solid program architecture, which has more
difficulty in debugging and maintenance, individual modules are coded
in a simple manner. The resultant structured code is then reviewed
and tested to ensure that no anomalies have been introduced. Internal
code structured is implemented in such a way that the maintenance of
the project in future would not be a cumbersome job.

Optimization of code
Optimization plays a very effective and vital role in project
management particularly in implementation phase where user’s
acceptance has more say in terms of acceptance of the proposed
software.
The factors that influence the optimization criteria are as follows

 Speed
o The speed by which the program gets executed has a
major role in success of the project. If the speed of
the execution of the software program is high then
overall performance of the entire project will be very
high. It depends upon the effectiveness of the
modularity of the functions and subroutines in a
program. In our project is based on the concept of
modular design. A high amount of functions and
subroutines have been implemented, thus making
the entire project a modular one. Program execution
need not execute the entire program every time,
rather it calls functions required at that time thus
saving a great amount of time and making the
program the faster and accurate.
  Space
o Space available in hard disk also makes a difference.
If the program is compact one and dynamic
approach is being adopted then space could not be a
problem. Some time non availability of space in hard
disk also creates a flutter. Effective database
management and use of suitable operating system
are of high importance.
 Code
o The code writing is the heart of optimization.
Effective code writing and to the point approach
makes a program very effective. The code length
should be as small as possible and dynamic approach
should be adopted in calling functions and
subroutines.
 Database
o Selection of effective database is very important.
Here in our case MS-Acess has been selected due to
high performance and durability.
 Operating System
o Selecting of operating system is also very important
because it should be compatible with the front end
accepted by the project leader. In our case Windows
XP is the choice.
Optimization about bad events means the explanations will be
temporary, specific, and impersonal. Pessimism about bad events
means the explanations will be permanent, pervasive and personal.
 Testing
Project software testing is one of the elements of a
broader topic that is known as verification and validation (v & v).
Validation refers to a different set of activities that ensure that the
software that has been built is tractable to the organization
requirements.
Although the validation encompasses a wide array of SQA
(auditing, reporting, function of management) activities. Since the
validation is concerned with the SQA activities hence it comprised the
formal technical reviews, performance monitoring, feasibility study,
database review, qualification testing and installation testing while
developing the ESCHPD.

In Book Shop Management system validation is achieved through a

series of test cases i.e., by demonstrating the system function which is
operational that the input is properly accepted and output is properly
produced and that the integrity of the external information (e.g. Data
files) is maintained which really uncovers error in conformity with
requirements. Validation refers to a set of activities that ensures that
the software that has been built is traceable to customer
requirements. Verification refers to a different set of activities that
ensures that the software correctly implements a specific function.
Before starting the plan we kept one thing in our mind that the
must be that they have the highest likelihood of find the most errors
with a minimum amount of time and effort.
If we will go through the software engineering methodologies
then there are many test case design has been developed. Which
offers a systematic approach to testing and a mechanism to ensure the
completeness of test and uncovering errors in software?
Basically any engineered product can be tested in two ways:
Knowing the specified function that a product has been designed
to perform test can be conducted that demonstrate each function is
fully operational at the same time searching for errors in each
function.
Knowing the internal working of a product, test can be conducted
to ensure that “all gear Mesh” i.e., internal operation performs
according to specification and all internal components have been
adequately exercised. Hence in such consequences we concentrated on
following two approach of testing.

The system can be predicted on close examination of procedural

detail. Providing test cases that exercise specific sets of conditions and
or loops tests logical paths through the “Book Shop Management
System”. The status of the program may examine at various points to
determine if the expected or asserted status corresponds to the actual
status.
In the system analysis the system was designed according to the
requirement of the system. The system deals with a large number of
states, complex logics and activities. So some error might occur in the
system. Error may be in software, which is known as “software error”
i.e., the software doesn’t do what the requirement says. So an
exhaustive and through testing must be conducted to ascertain
whether the system the system produces right results. The guide and
user both did testing at the several stages.
First each program module was tested as single program which
is also known as module testing or unit testing. In unit testing, asset
of data was given as input to the module and output data produces
were observed. In addition, logic and boundary conditions for input
and output data was also checked. The interface between this model
and others was also checked for correctness. While collecting the input
data for testing the program module it was kept in mind that input
data must be from the all classes, so the entire condition of the
program could be checked. In the testing the role of the user is also
very important since they understand the full range of data and
condition that might occur in the system. So a wide range of data was
collected from the user to test the program thoroughly. The actual
evaluation of any system can occur along any of the following
dimensions.

Integration and system Testing

When the individual program modules were working properly, we

combined the module into a working system. This integration is
planned and coordinated so that when an error occurs, we have an
idea of what caused it. Integration is the process of verifying that the
components of the system work together. For testing, the entire
system was viewed as a hierarchy of modules. We began with the
highest level of design and worked down. The next modules to be
tested are those that call the previously tested are those that call the
previously tested modules.

Function Test

Once we were sure that information is passed among modules

according to the design prescription we tested the system to assure
whether the function described the requirement specification were
actually performed by the integrated system.

Acceptance Test

When the function test was completed, we involved the user to make
sure that the system worked according to user’s exception. Thus the
user did final acceptance test.

Installation Test

When acceptance test was completed, the acceptance system was

installed in the environment in which it would be used and a final
installation test was performed to make sure that the system function
as it should.
 Implementation & Maintenance
The term implementation signifies all those activities that the
take place to convert from old system to the new. Conversion is one
aspect of implementation. The other aspects are post implementation
review and software maintenance.

Basically there are three types of implementation

1. Training
2. Conversion
3. Post implementation

Training
Even well designed and technically elegant system can succeed
or fail because of the way they are operated and used. Therefore, the
quality of training received by the personnel involved with the system
in various capacities helps or hinders and may even prevent the
successful implementation of an information system. Those who will be
associated with or affected by the system must know in detail what
their roles will be, they can use the system and what the system will
or will not do. Both system operators and users need training.
Training system operators
Many systems depend on the computer center personnel, who
are responsible for keeping the equipment running as well as for
providing the necessary support service. Their training must ensure
that they are able to handle all possible operations, both routine and
extraordinary. Operator training must involve the data entry
personnel. Since the system in commercial tax is a new one so, the
training personnel have been given first hand idea of how to use and
handle the equipments properly. They have also been familiarized with
the operational activities of the system e.g., proper shutdown,
maintenance, common malfunction and their remedies.
It also involves familiarization with run procedures, which
involves working through the sequence of activities needed to use a
new system on ongoing basis. These procedures allow the computer
operators to become familiar with the actions they need to take, and
when these actions occur. In addition, they are also informed that how
long applications will run under normal condition. This information is
important both to enable users to plan work activities and to identify
system that run longer or shorter then expected a sign that typically
indicates problems with the run.

User Training
 During user training special emphasis has been given on
equipment use i.e., how to operate the equipment. In it users have
been the idea of troubleshooting the system, determining whether a
problem that arises is caused by the equipment or software or by
something they have done in using the system. A troubleshooting
guide has also been provided to users in case of emergency handling.
Data-handling activities receiving the most attention in user
training are adding data, editing data, formulating enquiries and
deleting records of data.

Conversion
Conversion is the process of changing from old system to new
system. Here phase in method has been adopted because it is not
possible to install a new system throughout an organization all at once.
The conversion of files, training of personnel or arrival of equipment
may force the staging of the implementation over a period of time,
ranging from weeks to months.
Conversion plan
The conversion plan includes a description of all the activities of
that must occur to implement the new system and put it into
operation. It defines the persons responsible for each activity and
includes a timetable indicating when each activity will occur.

Maintenance
The maintenance part basically concerned with the modification
that are made to a “admin” system in initial release. Maintenance used
to be viewed as merely bug fixing, and it was distressing to discover
that so much effort was being spent on fixing defects and rectifying
defects.
There is a general perception that maintenance is indeed
not the proper word to use with software because maintenance refers
to un keep of the product in response to the gradual deterioration of
parts due to extended use of the product. For example, transmissions
are oiled and air filters are dusted and periodically changed. To use the
word maintenance with software gives the wrong connotation because
software doesn’t wear out. Unfortunately, however the term is used so
widely that we will continue using it.
 Conclusion
Using Powerful development tools like Java and MS-Access the
project titled “Book Shop Management System” has been developed
successfully. Every possible validation is applied to the various controls
used in the forms. The system developed provides is applied to the
various controls used in the forms. The system developed provides a
high degree of accuracy and user friendliness. The back end MS-
Access provides flexibility for dealing with the data.
We use Java as a development platform. Obviously it is menu
driven program and there is flexibility of using MS-Access or SQL
Server at backend. But due to much flexibility our project suggested to
use MS-Access as backend.
When we started our project our first objective was to find such
a control which was very fast and also provided the flexibility of Test
report for they can be easily exported and printed.
The control on which we did our reporting work has a very large
scope we it also facilitate some extra features with their kin built
functions. But at some places we faced some unusual problems.
Overall, it has been a nice experience to work on Java and MS-
Access in the same project.
 Bibliography

Books ‘name Author Publisher

The complete Reference Herbert Schildt TMH
Java2
Java 2 Beginning Ivor Horton Dreamtech Press
Core Java 2-Vol II Cornell, Horstmann
Java 6 Programming Black - Dreamtech Press
Book
An Integrated approach to Pankaj Jalote Narosa
software Engineering Publications
Introduction to Database Bipin C. Desai Galgotia
Publications
Relational Database System C.J. Date Addison Wesley
Database Management Majumdar &
System Bhattacharya

WebSites:

www.google.com
www.altavista.com