Library Management System

LIBRARY MANAGEMENT SYSTEM

1. INTRODUCTION

2010-2011 1


1.1 Company Profile

The project titled Library Management System is Library management software for monitoring and controlling the transactions in a library .The project "Library Management System" is developed in vb.net, which mainly focuses on basic operations in a library like adding new member, new books, and updating new information, searching books and members and facility to borrow and return books.

"Library Management System" is a windows application written for 32-bit Windows operating systems, designed to help users maintain and organize library. Our software is easy to use for both beginners and advanced users. It features a familiar and well thought-out, an attractive user interface, combined with strong searching Insertion and reporting capabilities. The report generation facility of library system helps to get a good idea of which are the books borrowed by the members, makes users possible to generate reports' hard copy.

The software Library Management System has four main modules.

Insertion to Database Module - User friendly input screen

Extracting from Database module - Attractive Output Screen

Report Generation module - borrowed book list & Available book list

Search Facility system - search for books and members

2010-2011 2


1.2 Existing System

A Library is a collection of information resources and services, organized for use, and

maintained by a public body, institution, or private individual. In the more traditional sense, it

means a collection of books. This collection and services are used by people who choose not to

— or cannot afford to — purchase an extensive collection themselves, who need material no

individual can reasonably be expected to have, or who require professional assistance with their

research.

The Library Management System is designed & developed for a receipt and issuance of

books in the library along with the student’s details. The books received in the library are entered

in Books Entry form and the new student is entered in the student entry form. When the student

wants to get the desired book the same is issued on the availability basis to the student. The

issuance and due date for the returning of the book is also entered into the Book Issue form under

third menu Book Issue. The student has to pay the fine if any on the basis of no. of days delayed

deposit of the book in the library.

The existing system that is being used in majority of public libraries is completely

manual in nature. Information about all the books and members/users is maintained separately in

data entry registers. The entries made in each and every register are having a serial number

corresponding to the register name and year. Also there are separate registers for purchase

and sale of books and for different user plans. This often leads to redundant information too.

Though some libraries do have computerized systems that provide basic features such as adding

books, user etc and also that of issuing the books, but what they lack is the user involvement and

interactivity.

Basic tasks in library management include the planning of acquisitions (which materials

the library should acquire, by purchase or otherwise), library classification of acquired materials,

preservation of materials (especially rare and fragile archival materials such as manuscripts), the

deaccessioning of materials, patron borrowing of materials, and developing and administering

library computer systems. More long-term issues include the planning of the construction of new

2010-2011 3


libraries or extensions to existing ones, and the development and implementation of outreach

services and reading-enhancement services (such as adult literacy and children's programming).

2010-2011 4


1.3 Problems in Existing System

Initially LIBRARY MANAGEMENT SYSTEMS involved intervention of man. The

systems employed several different groups of people, each group to handle a particular section in

library-be it issuing books, adding member details etc. These systems were very time consuming

and required a lot of paper work and maintenance. This sometimes results in insufficient

handling of books and records thereby increasing complexity.

In our existing system all the transaction of books are done manually, So taking more

time for a transaction like borrowing a book or returning a book and also for searching of

members and books. Another major disadvantage is that to preparing the list of books borrowed

and the available books in the library will take more time, currently it is doing as a one day

process for verifying all records. So after conducting the feasibility study we decided to make the

manual Library management system to be computerized.

Limitations of existing system:

Majority of libraries are dependent on paper-work which turns out to be very inefficient,

and data backup is very difficult and tedious

Users or members in such systems either become dependent on the librarian when they

enquire about the books existing in the library or find themselves helpless when they try

to search the library for their book of interest unknown of even its availability.

Present day systems involve the users very little in the entire process, and also do not

consider the user wants for newer books etc. This non-involvement of end users, also

mean that either they have to manually ask the librarian whether a particular book is

already issued by some other user or they have to browse through the library.

They are also unable to gather the information about user interests and books

that aremore popular than others

2010-2011 5


1.4 Need for Computerization

The purpose of Library Management Pro system is to provide a medium for the public

libraries to computerize their entire functioning and would contribute as a first step in

digitalizing their libraries.

As till now in India, public libraries (medium and small scale) had their entire records

on paper which again required maintenance and the problem of finding relevant information

proved to be a herculean task. Even if the required information was found it was usually at cost

of much valuable time.

Library Management Pro would not only simplify this process but also speedup the entire

functioning of the library. It will also contribute towards increasing the efficiency of the library

as a whole, right from the data entry to maintaining the historical records.

One major purpose is to provide user or the library members the opportunity to not only

search through the books but to reserve books that are issued by other users and also request

newer books.

From our past experiences we have seen that manual management is difficult and

moreover inefficient. Thus, we have designed a Computer based Library Management

System. This system helps us to carry out all the tasks related to library in an efficient manner. It

takes lesser time for solving our problems and is much easier and safer.

Through this system we can find a better management scheme. The system we have

designed gives correct solutions of our problems in less time. Need is the mother of invention, so

there was the need of designing such a system for the management of library tasks which was all

the more a very tedious task for a man to manage. Earlier it was very difficult for man to

maintain books and the records related to those books. But with the help of this system, we can

easily issue and return books, add members and books in our library as well as we can modify

the details of any book or the concerned member (if required). We can also display the records

2010-2011 6


related to any book or the member (in this case it is student) if the situation demands. Thus, on

the whole, reducing the labour, cost, time etc will increase the effectiveness and efficiency.

The objective behind this project is for automating the manual library. Our library

management system is going to have the following functions:-

FUNCTIONS OF NEW LIBRARY MANAGEMENT SYSTEM :

1) On the login form the system requests to user id and password then select admin, staff

and student.

2) After typing the password if you are admin you’ll allow to access all six options, if you

are staff you only allow to access four options and if you are student then you only allow

to access two options.

3) We have Six main options-

a) Search Book – You can Search book whether its available or not.

b) Exit – Exit from software.

c) Issue Book – You can Issue book to Student or Member.

d) Return Book – You Return book from Student or Member.

e) Add Member – You can add Member or Student.

f) Add Book – You can add book which came new in Library.

4) A student or member can any books issued.

7) The project takes the current system date as the date of issue and calculates date of due.

8) We can save the student as well as the book information.

9) The student who has got the book issued can only return the book.

10) Only a registered user (that is the student) can get the books issued.

2010-2011 7


2. Proposed System

2010-2011 8


2. Proposed SystemProposed system is an automated Library Management System. Through our software

user can add members, add books, search members, search books, update information, edit

information, borrow and return books in quick time. Our proposed system has the following

advantages.

User friendly interface

Fast access to database

Less error

More Storage Capacity

Search facility

Look and Feel Environment

Quick transaction

All the manual difficulties in managing the Library have been rectified by implementing

Computerization.

2010-2011 9


2.2 Hardware and Software Specification

Hardware & Software Requirements:-

1. ProcessorFor Client- PC with Pentium III-class processor, 600 MHz

(Recommended: Pentium IV-class processor, 866 MHz)

2. RAMWindows 2000 Professional- 128 MB or more

Windows 2000 Server- 128 MB or more

3.

Available

Hard-disk space

S/W

Hard-disk space

Approx.600 MB or more on system drive,

5 GB installation drive

50 MB on system drive

4. Operating System Windows XP

5. Supporting S/W VB.Net & Ms-2003

6.CD-Rom or DVD

Rom DriveOptional(Recommended)

7. Video 1024X768, 32 bit

8. Mouse Ps/2 mouse

9. Environment No Need

10. Printer A good quality DeskJet Printer

2010-2011 10


11. Monitor A 14-inch color monitor. A XGA(1024 X 768) video card

12. Floppy disk 1.44” floppy disk drive

2010-2011 11


2.3 Feasibility Studies

Whatever we think need not be feasible .It is wise to think about the feasibility of any

problem we undertake. Feasibility is the study of impact, which happens in the organization by

the development of a system. The impact can be either positive or negative. When the positives

nominate the negatives, then the system is considered feasible. Here the feasibility study can be

performed in two ways such as technical feasibility and Economical Feasibility.

Technical Feasibility:

We can strongly says that it is technically feasible, since there will not be much difficulty

in getting required resources for the development and maintaining the system as well. All the

resources needed for the development of the software as well as the maintenance of the same is

available in the organization here we are utilizing the resources which are available already.

Economical Feasibility:

Development of this application is highly economically feasible .The organization needed

not spend much m one for the development of t he system already available. The only thing is to

be done is making an environment for the development with an effective supervision. I f we are

doing so , we can attain the maximum usability of the corresponding resources .Even after the

development , the organization will not be in a condition to invest more in t he organization.

There fore , the system is economically feasible.

2010-2011 12


2.4 Fact finding Techniques

A Software has to be developed for automating the manual library. The system should be stand

alone in nature. It should be designed to provide functionality’s as explained below:

ISSUE OF BOOKS:

A Student or Member should be able to get books issued.

A limitation is imposed on the 1 book to 1 student can issue.

The due date for return of the books is stamped on the book.

RETURN OF BOOKS:

Any person can return the issue of books.

The information is saved and the corresponding updating take place in database.

QUERY PROCESSING:

Availability of a particular book.

Check the books whom it to be issued.

Search the books also with the Book Code.

2010-2011 13


3. Analysis

2010-2011 14


3.1 Nomenclature (ERD, DFD Symbols)

Entity Relationship Diagram (ERD):

Entity Relationship Diagrams (ERDs) illustrate the logical structure of databases.

Entity Relationship Diagram Notations

Peeter Chen developed ERDs in 1976. Since then Charles Bachman and James Martin have

added some slight refinements to the basic ERD principles

Entity

An entity is an object or concept about which you want to store information.

Weak Entity

A weak entity is an entity that must defined by a foreign key relationship with another entity as it

cannot be uniquely identified by its own attributes alone.

2010-2011 15

Entity

Entity


Key attribute

A key attribute is the unique, distinguishing characteristic of the entity. For example, an

employee's social security number might be the employee's key attribute.

Multivalued attribute

A multivalve attribute can have more than one value. For example, an employee entity can have

multiple skill values.

Derived attribute

A derived attribute is based on another attribute. For example, an employee's monthly salary is

based on the employee's annual salary.

Relationships

Relationships illustrate how two entities share information in the database structure.

Learn how to draw relationships:

First, connect the two entities, and then drop the relationship notation on the line.

2010-2011 16

Attribute

Attribute

Attribute


Data Flow Diagram (DFD)

In the late 1970s data-flow diagrams (DFDs) were introduced and popularized for structured

analysis and design. DFDs show the flow of data from external entities into the system, showed

how the data moved from one process to another, as well as its logical storage. In DFD there are

four symbols:

1. Squares representing external entities, which are sources or destinations of data.

= Source of Destination of data

2. Arrows representing the data flows, which can either, be electronic data or physical

items.

=Data flow

3. Circle or Rounded rectangles representing processes, which take data as input, do

something to it, and output it.

2010-2011 17

Relationships


= Process that transforms data flow

4. Open-ended rectangles representing data stores, including electronic stores such as

databases or XML files and physical stores such as or filing cabinets or stacks of paper.

Or = Data Source

2010-2011 18


3.2 System Flowchart

A system flowchart is a diagram that describes the overall flow of control between

computer programs in a system

It is a computer system representation of various computer programs, files, databases and

associated manual procedures.

It is observed that programs and sub systems have complex interdependencies including

flow of data, flow of control and interaction with data stores.

The interdependencies can be represented through a system flowchart using below

figures.

For convenience of design, it is a good idea to segregate the inputs, processes, output and

files involved in the system into a tabular form before proceeding with a flowchart.

= = Progress Or Program.

= File or Database.

= Document or Report.

2010-2011 19


= Connection between component, an Arrow indicates flow.

2010-2011 20


3.3 Context Level Diagram

A context level diagram is a top level (also known as Level 0) Data Flow Diagram. It is only

contains one process node (process 0) that generalizes the function of the entire system in

relationship to external entities.

All external agents and data flows into and out of the system are shown in a single

diagram with the entire system represented as a single process. A context diagram is useful for

showing the scope of the system which is being designed. The project scope defines the

functions of the system or the application which is to be developed is suppose to perform. The

context diagram includes external agents, data flows and a single process which represents the

entire system being developed.

The Context Diagram shows two external entities namely client and Accounting

(Accounts Dept.). The data flows in and out of the system are also shown. A single process

namely ‘Purchase Order System’ is shown which represents the computerized system as a whole.

The symbols used in the Context Diagram are:

A directed arrow to represent data flows in and out of the System.

A circle to represent a process.

A rectangular box with to represent External agent

2010-2011 21


Context Level Diagram

2010-2011 22


3.4 Entity Relationship Diagram

Entity Relationship diagram constitute a technique for representing the logical structure

of database in a pictorial manner. In this the entities are isolated and the relationships between

them are defined. The data is the focal point of an Entity Relationship diagram.

Guidelines for drawing Entity Relationship diagram:

o Determine the entities.

o Generate a list of all potential entities.

o Determine the relationships between the entities.

o Develop individual Entity Relationship diagrams

o Develop an integrated Entity Relationship diagram.

o Define the attributes for each entity.

The symbols used in an Entity Relationship diagram are:

o A rectangle to represent entities.

o A diamond is used to represent the relationships.

o The lines between the entities represent relationships.

The attributes are shown within ovals. Attributes which represent primary keys are underlined.

2010-2011 23


ENTITY RELATIONSHIP DIAGRAM

2010-2011 24


3.5 Data Flow Diagram

A DFD is also known as a ‘Bubble Chart’. Its purpose is to classify system requirement and

identifying major transformation that will becomes programs in system design. The Data Flow

Diagram is a graphical model showing the inputs, processes, storage & outputs of a system

procedure in structure analysis.

Advantages of DFD:-

o A DFD typically shows the minimum contents of data stores.

o It is quite effective, to clear the design to the user.

o Analyst has to the notational language for communication.

o Hence it requires the large number of iterations that often are required to arrive at the

most accurate & complete solution.

2010-2011 25


0 level Diagram

DFD FRAGMENT LEVEL

2010-2011 26


1) Maintain Login Info:-

Process Name: - Maintain Login InfoInflow: - Store Login InfoOutflow: - Generate Login Info

If Store login info thenShow Generated Login infoEnd if

2) Maintain Book Track Info:-

Process Name: - Maintain Book Track InfoInflow: - Store Book Track InfoOutflow: - Generate Book Track Info

If Store Book Track Info thenShow Generated Book Track InfoEnd if

2010-2011 27


3) Maintain Book User Info:-

Process Name: - Maintain Book User InfoInflow: - Store Book User InfoOutflow: - Generate Book User Info

If Store Book User Info thenShow Generated Book User InfoEnd if

4) Maintain Book Info:-

Process Name: - Maintain Book InfoInflow: - Store Book InfoOutflow: - Generate Book Info

If Store Book Info thenShow Generated Book InfoEnd if

2010-2011 28


4. System Design

2010-2011 29


Input Design

Input design is the process of converting user-oriented input to a computer based format.

Input design is a part of overall system design, which requires very careful attention .Often the

collection of input data is the most expensive part of the system. The main objectives of the input

design are…

1. Produce cost effective method of input

2. Achieve highest possible level of accuracy

3. Ensure that the input is acceptable to and understood by the staff.

Input Data:

The goal of designing input data is to make enter easy, logical and free from errors as

possible. The entering data entry operators need to know the allocated space for each field; field

sequence and which must match with that in the source document. The format in which the data

fields are entered should be given in the input form .Here data entry is online; it makes use of

processor that accepts commands and data from the operator through a key board. The input

required is analyzed by the processor. It is then accepted or rejected. Input stages include the

following processes.

Data Recording

Data Transcription

Data Conversion

Data Verification

Data Control

Data Transmission

Data Correction

2010-2011 30


One of the aims of the system analyst must be to select data capture method and devices,

which reduce the number of stages so as to reduce both the changes of errors and the cost .Input

types, can be characterized as.

External

Internal

Operational

Computerized

Interactive

Input files can exist in document form before being input to the computer. Input design is

rather complex since it involves procedures for capturing data as well as inputting it to the

computer.

OUTPUT DESIGN:-

Outputs from computer systems are required primarily to communicate the results of

processing to users. They are also used to provide a permanent copy of these result for latter

consultation .Computer output is the most important and direct source of information to the

users. Designing computer output should proceed in an organized well through out the manner.

The right output must be available for the people who find the system easy o use. The outputs

have been defined during the logical design stage. If not, they should defined at the beginning of

the output designing terms of types of output connect, format, response etc,

Various types of outputs are:-

External outputs

Internal outputs

Operational outputs

Interactive outputs

Turn around outputs

2010-2011 31


All screens are informative and interactive in such a way that the user can full fill his

requirements through asking queries.

DATABASE DESIGN:-

The general theme behind a database is to handle information as an integrated whole. A

database is a collection of interrelated data stored with minimum redundancy to serve many users

quickly and effectively. After designing input and output, the analyst must concentrate on

database design or how data should be organized around user requirements. The general

objective is to make information access, easy quick, inexpensive and flexible for other users.

During database design the following objectives are concerned:

Controlled Redundancy

Data independence

Accurate and integrating

More information at low cost

Recovery from failure

Privacy and security

Performance

Ease of learning and use

2010-2011 32


4.1 Data Element Dictionary

Book

Sr.No Field Name Data Type Size Primary Key

1 BookCode Text 255 Yes

2 BookName Text 255 No

3 BookAuthor Text 255 No

4 BookPrice Text 255 No

5 IssuedTo Text 255 No

Registration


1 MemberNo Text 255 Yes

2 FName Text 255 No

3 LName Text 255 No

4 Address Text 255 No

5 MobileNo Text 255 No

6 Gender Text 255 No

7 Age Text 255 No

User1


1 UserName Text 255 Yes

2 Password Text 255 No

2010-2011 33


3 Address Text 255 No

4 PhoneNo Text 255 No

5 Fname Text 255 No

6 Lname Text 255 No

7 IsAdmin Text 1 No

8 Gender Text 255 No

BookTrack


1 BookCode Text 255 Yes

2 MemberNo Text 255 Yes

3 IssueDate Date/Time --- No

2010-2011 34


4.2 Table Design Table Name:- Book

This table holds Books information.

Fields Type Description

BookCode TextThis Fields Store the Unique

Code of Book.

BookName TextThis Field Store the Name of

Book.

BookAuthor TextThis Field Store the Name of

Author of the Book.

BookPrice TextThis Field Store the price of

Book.

IssuedTo TextThis Field used to store Whether

this Issued or Not.

Table Name:- Registration

This Table Holds Members and Students Information.


MemberNo TextThis Fields Store the Unique

Member or Student ID Number.

FName TextThis Field Store the First Name

of Member or Student.

LName TextThis Field Store the Last Name

of Member or Student.

Address Text This Field Store the Address of

2010-2011 35


Member or Student.

MobileNo TextThis Field Store the Contact

Number of Member or Student.

Gender TextThis Field Store the Gender of

Member or Student.

Age TextThis Field Store the Age of

Member or Student.

Table Name:- User1

This Table Holds Admin and Staff Information.


UserName TextThis fields store the user name of

Staff or Admin.

Password TextThis fields store the password of

Staff or Admin.

Address TextThis fields store the address of

Staff or Admin.

PhoneNo TextThis fields store the contact

number of Staff or Admin.

Fname TextThis fields store the first name of

Staff or Admin.

Lname TextThis fields store the last name of

Staff or Admin.

IsAdmin TextThis fields store the whether the

user is Admin or not

Gender Text This fields store the gender of

2010-2011 36


Staff or Admin.

Table Name:- BookTrack

This Table Holds Book Issue and Book return Information.


BookCode TextThis Fields Store the Unique

Code of Book.

MemberNo TextThis Fields Store the Unique

Member or Student ID Number.

IssueDate Date/TimeThis fields store the Date of book

issued.

2010-2011 37


Program Specification

Form No. 1

Form Name Form 1(Beginning Window)

Form Purpose Startup screen, displayed when the project gets

loaded.

Input Table -

Output Table -

Validations It’s a startup form so one cannot skip this.

Form No. 2

Form Name Form 2(Login window)

Form Purpose Admin, Staff and Member can use this for log in

proposes.

Input Table -

Output Table -

Validations Admin, Staff and Member must be fillip this form

2010-2011 38


Form No. 3

Form Name Form 3(Home Page)

Form Purpose This form describe Home page for all Menu assess.

Input Table -

Output Table Assessed Menus Display

Validations -

Form No. 4

Form Name Form 4(Registration Members window)

Form Purpose This form describe to Open an Account to user .

Input Table -

Output Table -

Validations -

2010-2011 39


Form No. 5

Form Name Form 5(Add and Update Book window)

Form Purpose This form describe to Add new book and update existing book.

Input Table -

Output Table -

Validations -

Form No. 6

Form Name Form 6(Issue Book window)

Form Purpose This form describe whether book is issued on not.

Input Table -

Output Table -

Validations -

2010-2011 40


Form No. 7

Form Name Form 7(Return window)

Form Purpose This form describes returning the book.

Input Table -

Output Table -

Validations -

Form No. 8

Form Name Form 8(Search Book window)

Form Purpose This form describes to search any book which is available in library.

Input Table -

Output Table -

Validations -

2010-2011 41


Form No. 9

Form Name Form 9(Remove Book window)

Form Purpose This form describes Remoove Book from library which is no longer to be use.

Input Table -

Output Table -

Validations -

Form No. 10

Form Name Form 10(Help Counter)

Form Purpose This form describes for help to user for there suggestion or inconvenience.

Input Table -

Output Table -

Validations -

2010-2011 42


Form No. 11

Form Name Form 11(Removing User Window)

Form Purpose This form describes to permanently Remove a user from Library .

Input Table -

Output Table -

Validations -

2010-2011 43


4.4 Menu Design

2010-2011 44

Library Management System

Add Member

Save

Clear All

Close

Add Book

Check

Add

Update

Clear All

Remove

Close

Issue Book

Is Available

Close

Clear All

Issue

Return Book

Return

Clear All

Close

Search Book


2010-2011 45

Library Management System

Help Exit

Help

Exit


4.5 Input Screen Design

Login Screen

2010-2011 46


Add User

2010-2011 47


Add Member

2010-2011 48


Add or Update Book

2010-2011 49


Issue Book

2010-2011 50


Return Book

2010-2011 51


Search Book

2010-2011 52


Remove Book

2010-2011 53


Remove Member

2010-2011 54


Help Counter

2010-2011 55


5. Testing Procedure

2010-2011 56


SOFTWARE TESTING:-

Is the menu bar displayed in the appropriate contested some system related features

included either in menus or tools Do pull -Down menu operation and Tool-bars work properly

Are all menu function and pull down sub function properly listed ; Is it possible to invoke each

menu function using a logical assumptions that if all parts of the system are correct, the goal will

be successfully achieved . In adequate testing or non-testing will leads to errors that may appear

few months later.

This creates two problems:-

1) Time delay between the cause and appearance of the problem.

2) The effect of the system errors on files and records within the system.

The purpose of the system testing is to consider all the likely variations to which it will

be suggested and push the systems to limits.

The testing process focuses on the logical intervals of the software ensuring that all

statements have been tested and on functional interval is conducting tests to uncover

errors and ensure that defined input will produce actual results that agree with the

required results. Program level testing, modules level testing integrated and carried out.

There are two major type of testing they are:-

1) WHITE BOX TESTING.

2) BLACK BOX TESTING.

2010-2011 57


WHITE BOX TESTING:-

White box some times called "Glass box testing" is a test case design uses the control

structure of the procedural design to drive test case.

This testing methodology looks under the covers and into the subsystem of an

application. Whereas black-box testing concerns itself exclusively with the inputs and

outputs of an application, white-box testing enables you to see what is happening inside the

application. White box testing provides a degree of sophistication that is not

available with black-box testing as the tester is able to refer to and interact with the objects

that comprise an application rather than only having access to the user interface. An

example of a white-box system would be in-circuit testing where someone is looking at the

interconnections between each component and verifying that each internal connection is

working properly. Another example from a different field might be an auto-mechanic who

looks at the inner-workings of a car to ensure that all of the individual parts are working

correctly to ensure the car drives properly.

Using white box testing methods, the following tests where made on the system

All independent paths within a module have been exercised once. In our system, ensuring

that case was selected and executed checked all case structures. The bugs that were

prevailing in some part of the code where fixed.

All logical decisions were checked for the truth and falsity of the values.

2010-2011 58


BLACK BOX TESTING:-

Black box testing focuses on the functional requirements of the software. This is black

box testing enables the software engineering to derive a set of input conditions that will fully

exercise all functional requirements for a program. Black box testing is not an alternative to

white box testing rather it is complementary approach that is likely to uncover a different class of

errors that white box methods like..

1) Interface errors

2) Performance in data structure

3) Performance errors

4) Initializing and termination errors

This testing methodology looks at what are the available inputs for an application and

what the expected outputs are that should result from each input. It is not concerned with the

inner workings of the application, the process that the application undertakes to achieve a

particular output or any other internal aspect of the application that may be involved in the

transformation of an input into an output. Most black-box testing tools employ either coordinate

based interaction with the applications graphical user interface (GUI) or image recognition. An

Example of a black-box system would be a search engine you enter text that you want to

search for in the search bar, press “Search” and results are returned to you. In such

a case, you do not know or see the specific process that is being employed to obtain your

search results, you simply see that you provide an input – a search term – and you receive an

output – your search results.

2010-2011 59


6. Output Screens

2010-2011 60


Report

2010-2011 61


7. Implementation Procedure

2010-2011 62


System Implementation:-

Implementation is the stage in the project where the theoretical design is turned into a working system. The implementation phase constructs, installs and operates the new system. The most crucial stage in achieving a new successful system is that it will work efficiently and effectively.

There are several activities involved while implementing a new project they are

End user training End user Education Training on the application software System Design Parallel Run And To New System Post implementation Review

End user Training:The successful implementation of the new system will purely upon the involvement of

the officers working in that department. The officers will be imparted the necessary training on the new technology.

End User Education:The education of the end user start after the implementation and testing is over. When the

system is found to be more difficult to under stand and complex, more effort is put to educate the end used to make them aware of the system, giving them lectures about the new system and providing them necessary documents and materials about how the system can do this.

Training of application software:After providing the necessary basic training on the computer awareness, the users will

have to be trained upon the new system such as the screen flows and screen design type of help on the screen , type of errors while entering the data , the corresponding validation check at each entry and the way to correct the data entered. It should then cover information needed by the specific user or group to use the system.

Post Implementation View:

The department is planning a method to know the states of t he past implementation process. For that regular meeting will be arranged by the concerned officers about the implementation problem and success.

2010-2011 63


The anticipated system has been totally developed in two environments

1. Front-end as ‘VB.net’

2. Back-end as ‘Microsoft Access’.

Back-end: Microsoft Access

(a) Computer: Intel or compatible Pentium 166MHz or higher.

(b) Operating System: Microsoft Windows 2000 Professional, Windows 2000

Server

(c) Memory (RAM): 128MB or more (recommended).

(d) Hard Disk Space: 250MB for typical installation.

(e) Internet Software: Microsoft Internet Explorer Version 5.0 or later.

2010-2011 64


FACTORS FOR CONSIDERING MS-SQL AS BACK END TOOL

Microsoft SQL (Structured Query Language) is powerful program to create and

manage your databases .It has many built in features to assist you in constructing and

viewing your information .SQL is much more involved and is a more genuine application

than other programs

SQL Server is a family of products and technologies that meets the data storage

requirements of OLTP (Online Transaction Processing) and OLAP (Online Analytical

Processing) environment.SQL Server is a Relational Database Management System

(RDBMS) that:

Manage Data Storage for transaction and analysis

Responds to requests from client application

Uses Transact –SQL, Extensible Markup Language (XML), Multidimensional

Expressions (MDX) or SQL Distributed Management Objects (SQL-DMO) to send

requests between a client and SQL Server .

SQL Server uses client-server architecture to separate the workload into the tasks that run on

server computers and those that run on client computers.

Microsoft ActiveX Data Objects (ADO) wrap OLE DB for use in languages such as

Microsoft Visual Basic.

2010-2011 65


8. User Manual

2010-2011 66


Now we are looking for how to use this application.

To open Home page,

Go through Login Process as per Appropriate User for say Admin, Staff or Member. And proceed by entering proper user id & password.

After we will go on Home page.1. For Add Member Click Add Member Button.2. For Add Book Click Add Book Button. It is also use for updating Book details.3. For Issue Book Click Issue Book Button.4. For Return Book Click Return Book Button.5. For Searching Book Click Search Book Button.6. For Exit Application Click Exit Button.7. And Last is Help counter to use it, go at top left corner and press help button for getting any kind of help.

2010-2011 67


9. Scope for Future Enhancement

2010-2011 68


In the future versions of the system, I would like to introduce Interactive voice

technology to minimize the use of keyboard and make the system user-friendly, hence;

customers themselves can operate the system.

This will lead to an exclusive implemented of CRM. The only reason for this technology

not being implemented in the current system is the high cost of taking permission for the

interactive voice software. As a result, institute might not be willing to purchase

2010-2011 69


10. Conclusion

2010-2011 70


Conclusion

Our project is only a humble venture to satisfy the needs in a library. Several user friendly coding have also adopted. This package shall prove to be a powerful package in satisfying all the requirements of the organization.

The objective of software planning is to provide a frame work that enables the manger to make reasonable estimates made within a limited time frame at the beginning of the software project and should be updated regularly as the project progresses. Last but not least it is no the work that played the ways to success but ALMIGHTY.

2010-2011 71


11. Bibliography

2010-2011 72


BIBLIOGRAPHY:-

http://www.vbdotnethaven.comhttp://www.startvbdornet.comhttp://www.msn.microsoft.comThe Complete Reference – Visual Basic.Net – Jefrey R. Shapiro

2010-2011 73

http://www.msn.microsoft.com/

http://www.startvbdornet.com/

http://www.vbdotnethaven.com/

Library Management System

Documents

Transcript of Library Management System