Book Shop Management System

Computer is fast emerging as a daily need in walks of life. The knowledge of computers

and programming language has become basic

Skill need to service in today’s information based society. Every business

Institution and the corporate section, make a use of computer for making their

operation efficient & effective.

Book distributors transaction handling is one of the complex process and it required

computerized system to maintain overall transactions in an easier manner. Due to heavy

demand of books in these competitive worlds, data increase so much. Books shop

required

up to date information about the customer who purchased books or about the suppliers

from where books are purchased. The books shop requires large amount of data to

record and to store, which are collected from the Book House

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

Book Details

Quantities of Books

Customer Details

S a l e Details

Quantities of the products System will help to produce following outputs

C u s t o m e r bill receipt

R a t e List

C u r r e n t Quantities of the products

V a r i o u s Reports sales, stock, customers etc

OBJECTIVE OF THE PROJECT

The objective and scope of my Project Book Shop Management System is to record the

details various activities of user. It will simplify the task and reduce the paper work. During

implementation every user will be given appropriate training to suit their specific needs.

Specific support will also be provided at key points within the academic calendar. Training

will be provided on a timely basis, and you will be trained as the new is Book Shop

Management System rolled out to your area of responsibility.

At the moment we are in the very early stages, so it is difficult to put a specific time on the

training, but we will keep people informed as plans are developed. The system is very user

friendly and it is anticipated that functions of the system will be easily accessed by

administrators, academics, students and applicants.

Hence the management system for the College management has been designed to remove all

the deficiency from which the present system is suffering and to ensure

.

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.

2.1 Current system

The book shop contains different types of books of various subjects with various

quality according to the customer’s needs and requirement. The main thing of the book

shop is to maintain lot of records for the daily transaction of the business. It is necessary

for every business to maintain all records, which show the profit and loss of the business.

In today’s life people have very little time and many things

To do. They have to manage all this unbalance workload, although everyone wants to

achieve all their ambitions and dreams. And the present system of managing Books is very

time consuming so it is very difficult to maintain good records and fast service. The paper

work is becoming very difficult to handle day by day. Currently we have to keep track of

each and every thing about the book shop on the paper or in register. We have to maintain

lot of registers to enter these large volumes of data. This leads to the wastage of stationary.

Some disadvantages are:

Manual system involves a lot of paper work, so it becomes time-consuming

and costly.

The chances of errors in calculation of delivery of Books are more in the

current manual system. The calculation of total collection for day or month or

year is very difficult.

Currently no security is provided to the large amount of data of the every

book details.

It becomes very difficult to maintain details of every Book as records increases day

by day

2.2 Proposed system

While creating new software we should analyze what is the basic need of the software.

Analysis is nothing but a planning of creation of software to get proper output from it.

Analysis is details study of projects that you want to show in your software solving

problems. The basic need of the software is to save the time of the user with the help of all

useful information. And also to maintain the collection of data in your computer

systematically, so that it’s easy to understand. The proposed system provides lot of facility

to the user to store information of the Books and it provides information in quick time in a

systematic manner. The processing time on the data is very fast. It provides required data

quickly to the user and also in specified manner to the user. All the information of Books

changes is given to the

user and also the reports are also generated according to the requirement of the user.

Today it is becoming very difficult to maintain record manually. This software system

easily does

the job of maintaining daily records as well as the transaction according to the

user requirements. Some advantages are

User – Friendly software

Easy to record all data about the Books and its details

It saves time of the user as well as prevent paper work

It provides the security to the database that is large amount of important data of the

Book

Shop

It provides more reliability for keeping information.

2.3 Requirement Analysis

Identifying needs is the first step while designing a system and implementation. This

is the way to handle user needs, it 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

2.4 FEASIBILITY STUDY

Depending on the results of the initial investigation the survey is now expanded to a

more detailed feasibility study. “FEASIBILITYSTUDY” 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

2.4.1 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

backgrou

nd.

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.

2.4.2 Economic Feasibility

Economic justification is generally the “Bottom Line” consideration for most

systems. Economic justification includes abroad 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.

1.3 SYSTEM ENVIRONMENT:

HARDWARE CONFIGURATION:

System : HCL

Processor : Pentium IV

Processor Speed : 2.80GHz

Main Storage : 512MB RAM

Hard Disk Capacity : 80GB

Floppy Disk Drive : 1.44MB

CD-ROM Drive : LG 52X Reader

Keyboard : 104 Keys

Mouse : Logitech

Monitor : Samsung 17” Color

SOFTWARE CONFIGURATION

Operating System : Windows XP

Front end : Visual Basic.Net

Back End : SQL Server 2000

4SOFTWARE FEATURES

VISUAL BASIC.NET

Visual Baic.Net has revolutionized windows programming windows programming and with an

object based, event driven approach to software designs. Visual basic.Net applications act as a front end

to the database. Visual basic.Net application provides the interface between the user and the database.

Sophisticated features that make the language truly object oriented and interfaces it with the latest in the

database technology.

.NET provides a new, object-oriented API as a set of classes that will be accessible from any

programming language. This book describes this framework of classes and provides a reference to what

is available and how you can use this framework to write Windows applications in the brave new world

of .NET.

Microsoft .NET Framework is a computing platform for developing distributed applications for

the Internet. Following are the design goals of Microsoft .NET Framework:

1. To provide a very high degree of language interoperability

2. To provide a runtime environment that completely manages code execution

3. To provide a very simple software deployment and versioning model

4. To provide high-level code security through code access security and strong type

checking

5. To provide a consistent object-oriented programming model

6. To facilitate application communication by using industry standards such as SOAP and

XML.

7. To simplify Web application development

Visual basic.net lets the user to add menus, text boxes, command buttons, option buttons, check

boxes, list boxes, scroll bars, and file directory boxes to blank windows. Visual basic.net has many

different tools.

The Common Language Runtime

The CLR is the mechanism through which .NET code is executed. It is built upon a single,

common language—IL—into which source languages are compiled and includes mechanisms for

executing the compiled code. This includes code verification and just-in-time (JIT) compilation, garbage

collection and enforcement of security policies, and the provision of profiling and debugging services.

The CLR provides a lot of added value to the programs it supports. Because it controls how

a .NET program executes and sits between the program and the operating system, it can implement

security, versioning support, automatic memory management through garbage collection, and provide

transparent access to system services

IMPORTANT FEATURES:

The application is a graphical user interface.

Client-Server architecture benefits picture and image box can be easily handled

using bit mapped files and icons.

Bit mapped files and icons are used as simple debugging tools.

With the advent of .NET, Microsoft has introduced many new technologies that

make writing component-based distributed systems easier, more flexible, and

more powerful than ever before.

It is now easier than it has ever been to write components in any programming

language that can interoperate with components on other machines, which may

not be Windows-based at all.

SQL SERVER 2000

The purpose of this document is to help you migrate your applications when you are

migrating the underlying database from Microsoft SQL Server to Some other Database.

Most of the issues encountered when migrating applications to use an Sql Server Database

are related to database incompatibility. This paper presents these incompatibilities and

provides solutions for many issues.

You should familiarize yourself with this document prior to migrating your databases. The

choices made about how to migrate your application affect how you migrate the underlying database

from Microsoft SQL Server to some other Database.

If the application uses the Microsoft OLE DB Provider for SQL Server or a third-party OLE DB

Provider to connect the Microsoft SQL Server database, use the Sql Server Provider for OLE DB

(SQLOLEDB) to connect to the migrated Database.

SQL Server Security

Login Authentication.

Windows NT Authentication

SQL Server Authentication

Permissions validation on user database.

T-SQL statements sent to SQL Server.

SQL server checks user permissions on receipt of T-SQL statements

FEATURES

Created by Microsoft and Sybase in the 80s.

Is SQL Compliant - Uses ANSI SQL

Supports SQL – 92 standards - Uses T-SQL

Stores data in a central location and delivers it to clients on request

New Server Architecture

Graphic Administration Tools

Maintains ANSI standards and 6.x Compatibility

Data integrity means reliability and accuracy of data.

Integrity rules keep data consistent.

Supports Client/Server model.

Request response dialog.

workload is split between the client and the server.

Operating System compatibility.

Runs on Win 95/98 NT, Netware, UNIX, OS/2, Appletalk, Banyan VINES.

SQL Server must have Service Pack 4 (SP4) to run on Windows NT 4.0.

Multiple protocol compatibility.

SQL Server supports these protocols - Appletalk, TCP/IP.

SMP Compatibility and Scalability

Supports multiple processors. SMP leads to scalability.

SYSTEM DESIGN

System design is the process of planning a new system to complement or altogether

replace the old system. The purpose of the design phase is the first step in moving from the

problem domain to the solution domain. The design of the system is the critical aspect that

affects the quality of the software. System design is also called top-level design. The design

phase translates the logical aspects of the system into physical aspects of the system.

3.2 INPUT DESIGN

Input design is one of the most important phase of the system design. Input design is the

process where the input received in the system are planned and designed, so as to get necessary

information from the user, eliminating the information that is not required. The aim of the input

design is to ensure the maximum possible levels of accuracy and also ensures that the input is

accessible that understood by the user.

The input design is the part of overall system design, which requires very careful

attention. if the data going into the system is incorrect then the processing and output will

magnify the errors.

The objectives considered during input design are:

Nature of input processing.

Flexibility and thoroughness of validation rules.

Handling of properties within the input documents.

Screen design to ensure accuracy and efficiency of the input relationship

with files.

Careful design of the input also involves attention to error handling,

controls, batching and validation procedures.

Input design features can ensure the reliability of the system and produce result from

accurate data or they can result in the production of erroneous information. The input design of

the system includes the following

3.3 OUTPUT DESIGN

Output design is very important concept in the computerized system, without reliable output the user may feel the entire system is unnecessary and avoids using it. The proper output design is important in any system and facilitates effective decision-making.

The output design of the system includes the following

TESTING

Testing is a series of different tests that whose primary purpose is to fully exercise the

computer based system. Although each test has a different purpose, all work should verify that all system

element have been properly integrated and performed allocated function. Testing is the process of

checking whether the developed system works according to the actual requirement and objectives of the

system.

The philosophy behind testing is to find the errors. A good test is one that has a high

probability of finding an undiscovered error. A successful test is one that uncovers the undiscovered

error. Test cases are devised with this purpose in mind. A test case is a set of data that the system will

process as an input. However the data are created with the intent of determining whether the system will

process them correctly without any errors to produce the required output.

Types of Testing:

Unit testing

Integration testing

Validation testing

Output testing

User acceptance testing

5.1unit Testing

All modules were tested and individually as soon as they were completed and were checked for their

correct functionality.

5.2 Integration Testing

The entire project was split into small program; each of this single programs gives a frame as an

output. These programs were tested individually; at last all these programs where combined together by

creating another program where all these constructors were used. It give a lot of problem by not

functioning is an integrated manner.

The user interface testing is important since the user has to declare that the arrangements made in

frames are convenient and it is satisfied. when the frames where given for the test, the end user gave

suggestion. Based on their suggestions the frames where modified and put into practice.

Validation Testing:

At the culmination of the black box testing software is completely assembled as a package.

Interfacing errors have been uncovered and corrected and a final series of test i.e., Validation succeeds

when the software function in a manner that can be reasonably

Accepted by the customer.

5.3 Output Testing

After performing the validation testing the next step is output testing of the proposed system. Since

the system cannot be useful if it does not produce the required output. Asking the user about the format

in which the system is required tests the output displayed or generated by the system under consideration.

Here the output format is considered in two ways. one is on screen and another one is printed format. The

output format on the screen is found to be corrected as the format was designed in the system phase

according to the user needs. And for the hardcopy the output comes according to the specifications

requested by the user.

User Acceptance System

An acceptance test as the objective of selling the user on validity and reliability of

the system. It verifies that the procedures operate to system specification and mat the integrity of vital is

maintained.

Performance Testing

This project is a application based project, and the modules are interdependent with the other

modules, so the testing cannot be done module by module. So the unit testing is not possible in the case

of this driver. So this system is checked only with their performance to check their quality.

SYSTEM TESTING AND IMPLEMENTATION

The purpose of System Implementation can be summarized as follows:

It making the new system available to a prepared set of users (the deployment), and positioning

on-going support and maintenance of the system within the Performing Organization (the transition). At

a finer level of detail, deploying the system consists of executing all steps necessary to educate the

Consumers on the use of the new system, placing the newly developed system into production,

confirming that all data required at the start of operations is available and accurate, and validating that

business functions that interact with the system are functioning properly. Transitioning the system

support responsibilities involves changing from a system development to a system support and

maintenance mode of operation, with ownership of the new system moving from the Project Team to the

Performing Organization.

List of System implementation is the important stage of project when the theoretical design is tuned into

practical system. The main stages in the implementation are as follows:

Planning

Training

System testing and

Changeover Planning

Planning is the first task in the system implementation. Planning means deciding on the method

and the time scale to be adopted. At the time of implementation of any system people from different

departments and system analysis involve. They are confirmed to practical problem of controlling various

activities of people outside their own data processing departments. The line managers controlled through

an implementation coordinating committee. The committee considers ideas, problems and complaints of

user department, it must also consider;

The implication of system environment

Self selection and allocation form implementation tasks

Consultation with unions and resources available

Standby facilities and channels of communication

The following roles are involved in carrying out the processes of this phase. Detailed descriptions of

these roles can be found in the Introductions to Sections I and III.

_ Project Manager

_ Project Sponsor

_ Business Analyst

_ Data/Process Modeler

_ Technical Lead/Architect

_ Application Developers

_ Software Quality Assurance (SQA) Lead

_ Technical Services (HW/SW, LAN/WAN, TelCom)

_ Information Security Officer (ISO)

_ Technical Support (Help Desk, Documentation, Trainers)

_ Customer Decision-Maker

_ Customer Representative

_ Consumer

The purpose of Prepare for System Implementation is to take all possible steps to ensure that

the upcoming system deployment and transition occurs smoothly, efficiently, and flawlessly. In the

implementation of any new system, it is necessary to ensure that the Consumer community is best

positioned to utilize the system once deployment efforts have been validated. Therefore, all necessary

training activities must be scheduled and coordinated. As this training is often the first exposure to the

system for many individuals, it should be conducted as professionally and competently as possible. A

positive training experience is a great first step towards Customer acceptance of the system.

During System Implementation it is essential that everyone involved be absolutely synchronized

with the deployment plan and with each other. Often the performance of deployment efforts impacts

many of the Performing Organization’s normal business operations. Examples of these impacts include:

_ Consumers may experience a period of time in which the systems that they depend on to perform their

jobs are temporarily unavailable to them. They may be asked to maintain detailed manual records or logs

of business functions that they perform to be entered into the new system once it is operational.

_ Technical Services personnel may be required to assume significant implementation responsibilities

while at the same time having to continue current levels of service on other critical business systems.

_ Technical Support personnel may experience unusually high volumes of support requests due

to the possible disruption of day-to-day processing.

Because of these and other impacts, the communication of planned deployment activities to all

parties involved in the project is critical. A smooth deployment requires strong leadership, planning, and

communications. By this point in the project lifecycle, the team will have spent countless hours devising

and refining the steps to be followed. During this preparation process the Project Manager must verify

that all conditions that

must be met prior to initiating deployment activities have been met, and that the final ‘green light’ is on

for the team to proceed. The final process within the System Development Lifecycle is to transition

ownership of the system support responsibilities to

the Performing Organization. In order for there to be an efficient and effective transition, the Project

Manager should make sure that all involved parties are aware of the transition plan, the timing of the

various transition activities, and their role in its execution.

Due to the number of project participants in this phase of the SDLC, many of the necessary

conditions and activities may be beyond the direct control of the Project Manager. Consequently, all

Project Team members with roles in the implementation efforts must understand the plan, acknowledge

their responsibilities, recognize the extent to which other implementation efforts are dependent upon

them, and confirm their commitment.

SCOPE FOR FUTURE ENHANCEMENT

This software has demands in private and public area. This software provides a great

help in managing the data in a well-mannered order. This project is designed specially to

maintain the data in a sequential manner and to save the tome and efforts of database

Administrator. The project is structured according to today’s need.

Due to time constraint it is possible that some points might remain uncovered by us. In

future we will update our software to give valuable information left at present.

Though the system has been designed according to the requirements of the users it has its

own limitation. Thus the limitation of system are-

N o facility to create new users with different roles

O b j e c t oriented Approach has been not been fully utilized

The “Book management system “been developed to satisfy all proposed requirements. The

system is highly scalable and user friendly. Almost all the system objectives have been met. The system

has been tested under all criteria. The system minimizes the problem arising in the existing manual

system and it eliminates the human errors to zero level.

The software executes successfully by fulfilling the objectives of the project. Further extensions

to this system can be made required with minor modifications. The invention can be implemented in

digital electronic circuitry, or in computer hardware, firmware, software, or in combinations of them.

Apparatus of the invention can be implemented in a computer program product tangibly embodied in a

machine-readable storage device for execution by a programmable processor; and method steps of the

invention can be performed by a programmable processor executing a program of instructions to

perform functions of the invention by operating on input data and generating output

BIBLIOGRAPHY

.Elias Awath, “SYSTEM ANALYSIS AND DESIGN”, Tata Mc Graw Hill

Publication, Sixth Edition,2003

.S.Ramachandran,”COMPUTER AIDED DESIGN”, Air Walk Publication, Third

Edition,2003

.Richard Fairley, “SOFTWARE ENGINEERING CONCEPTS”, Tata Mc Graw

Hill Publication, Second Edition,1997

.Distributed .NET Programming in VB .NET by Tom Barnaby

Professional VB.NET, 2nd Edition by Fred Barwell, et al

The .NET Languages: A Quick Translation Guide by Brian Bischof

Programming VB.NET: A Guide for Experienced Programmers

by Gary Cornell, Jonathan Morrison

Learning Visual Basic.NET Through Applications by Clayton Crooks II

Visual Basic .NET How to Program (2nd Edition) by Harvey M. Deitel,

Paul J. Deitel, Tem R. Nieto

Data Tables

1) Users Table – Login Information

No. Field Name Data Type

1 User_Name Text

2 Password Text

2) Books Table – Book Information

No. Field Name Data Type

1 BookID Number

2 BookName Text

3 ISBN Text

4 Category Number

5 Author Text

6 Price Number

7 SalePrice Number

8 Stock Number

3) Cat Table – Book Categories Information

No. Field Name Data Type

1 Cat_ID Number

2 Cat_Name Text

4) Customers Table – Customer Information

No. Field Name Data Type

1 Cust_ID Number

2 Cust_Name Text

3 Cust_Addr Text

4 Cust_No Text

5 CreditAmt Number

6 GenTime Date\Time

5) Bills Table – Bills Information

No. Field Name Data Type

1 Bill_ID Number

2 Customer_ID Number

3 BillDate Date\Time

4 Bill_Details Number

5 Bill_Time Date\Time

6 Total Number

7 TotalDisc Number

8 AmtRecv Number

6) Bill Details Table – Bill Item Details Information

No. Field Name Data Type

1 Bill_Details_ID Number

2 Bill_ID Number

3 Book_ID Number

4 Quantity Number

5 Discount Number

6 Cust_ID Number