1.

INTRODUCTION
The project titled Library Management System is Library Management Software for
monitoring and controlling the transactions in a library.The purpose of LMS is to manage daily
operations of library effectively & efficiently. This system basically has four types of modules
that handle daily activity for the library. It is a sub-discipline of management that focuses on
specific issues faced by libraries and library management professionals. Library
management encompasses normal managerial tasks, as well as intellectual freedom and
fundraising responsibilities.
The transactions like login, register, add, search, delete, issue are provided. The Library
Management System stores the details like name, address, ID number, Date of Birth of
members working in the library and users who come to library. The details of books like book
name, book number, Price, author, edition, year of publication etc are also stored. The
application 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

1.1 OVER VIEW OF THE PROJECT

The “Library Management System” is developed by using ASP.NET as a Front-End,
Sql Server as a Back-End. This Automation has Six Modules such as Master, Book
Reservation, Book Issue, Book Return, Fine, Stock and Reports The Master Module has the
details about the Book Purchase, Book Maintain, Supplier Master, Member Master,
Reservation, Issue, Return, and Fine. In Book Purchase have the information of the Book
name, Date, Number of book Purchase, Rate, and Amount of the books. In Supplier and
Member master has the information of the Suppliers and Members. Library management
system is a small program to manage library which includes the task of library. Adding new
users, books and magazines / newspapers. Updating users, books and magazines /newspapers
.deleting users, books and magazines/newspapers. Issuing books. Collecting books back.
Searching for book users. Crystal report generation.
The Book Reservation is used to information about the Reservation ID, Book Name,
Date, Member Name, Issue Date and Returning Date. This Reservation ID will be from the
Reservation Master. And Member Name from the Member Mast the Book Issue is used to get
the information about Issue ID, Book Name, in this module check the Book Name was
reserved or not, that is Issue type. The Issue Type is Reserved and Unreserved. Reserved
means Reservation ID, Book Name, Issue Date, and Return Date are also maintained. The
Book Return has the details about Book Return Details.
1
 Return ID, Issue ID, Issue Type, Book Name, Author Name, Date of the Issue, Return
and Today. The Fine Details are also maintained. Fine will be calculated by using Issue Date,
Return Date and Today Date. The Fine has the details about the Fine Details of the Member.
That is Fine Date, Book ID, Book Name, Author Name, Member Name, and Date of the Issue,
Returning, and Fine amount will be maintained. The Reports are generated by using Crystal
Reports. There are six Reports in this Automation. Our project we will be able to classify users
as staff or students. Classifying users allows the book issue controls, fine rates based on the
classification. For example for students we will be able to issue books at the fine books. We
have to set this values jest one and not every time the program starts. We have used my.
Setting class to implement this.
Whatever we think need not be feasible. It is wise to think about the library feasibility
of any problem we undertake. Feasibility is the student library of impact which happens in the
organization by the development bow system .The impact of library Automation can be
either positive. Or negative .when the position nomination the negatives then the system is
considerate feasible. Here the feasibility study can be performed in two ways such as technical
feasibility and economic feasibility. library Automation feasibility we can strong say that it is
technically feasibility ,since they will not be much difficulty in getting required resource for
the development and maintaining the system as well all the resources for the development of
the software as well as the maintenance of the same is available in the already.
The library Automation of risk is often instrumental in achieving organization
objectives; it makes sense to consider how risk Automation may be incorporated into the to
help with the identity, measurement, library Automation and reporting of key risks.
Consequently, is an integrating framework it lends itself well to initiatives such as risk can be
just as important as measuring performance. Although the application of in the business sector
is well document very little research has been report reported the risk Automation .they are
only a few studies have considered how enterprise risk Automation and can be linked.

2
2. SYSTEM ANALYSIS
2.1 SYSTEM STUDY
The system is studied to the minutest detail and analyzed. The system study plays the
role of an interrogator and dwells deep into the working of the present system. The system is
viewed as a whole and the inputs to the system are identified. The outputs from the
organization are traced through the various processing that the inputs phase through in the
organization.

2.2 EXISTING SYSTEM

Lot of information is to be gathered in this competitive world. Library is one of the
means by which information are provided. Maintaining the details of books and magazines
issued, bought, issuing library cards are some of the details that has to be maintained properly
in a library. Since the information stored gets larger, the process has to be automated. In the
automated system, all the details all stored under a master category where the books purchased,
supplier of book details, member details, issue and reservation of books. Stock details are
maintained under a separate category. The date on which the book is issued and returned are
maintained. Fine is collected for late return or loss of books. Those details are also maintained
separately. Reports are generated on the details of fine, issue, reservation, return and stock. The
whole system in a library is automated. So that maintenance of books such as inflow and
outflow along with supplier, author and price details are maintained.

DISADVANTAGES
 Data’s access is difficult.
 Reorder level of each and every item cannot maintained properly so that the purchase
order cannot be placed at correct time.
 Maintain the stock level without nil problem occur.
 Improper maintenance of Purchase invoice details, so that the amount balance to the
suppliers cannot be identified easily.
 Sales details to regular customers of the store cannot be maintained.

3
2.3 PROPOSED SYSTEM
Library Automation System is an application which refers to library systems which are
generally small or medium is used by librarian to manage the library using a computerized
system where he/she can record various transactions like issue of books, return of books,
addition of new books, addition of new students etc. Books and student maintenance modules
are also included in this system which would keep track of the students using the library and
also a detailed description about the books a library contains. In this computerized system there
will be no loss of book record or member record which generally happens when a non-
computerized system is used. In addition, report module is also included in Library
Automation System. If user’s position is admin, the user is able to generate different kinds of
reports like lists of students registered, list of books, issue and return reports. All these modules
are able to help librarian to manage the library with more convenience and in a more efficient
way as compared to library systems which are not computerized.

ADVANTAGES
 Increase the efficiency of the system
 Easy access to data’s
 Reorder level of each and every item will be maintained so that the purchase order can
be placed timely to maintain the stock level without nil.
 Purchase invoice details can be maintained, so that the amount balance to the suppliers
can be identified easily.
 Generating day wise, weekly, monthly sales and purchase reports.
 Sales details to regular customers of the store can be maintained.

2.4 FEASIBILITY STUDY

The feasibility of the project is analyzed in this phase and business proposal is put forth
with a very general plan for the project and some cost estimates. During system analysis the
feasibility study of the proposed system is to be carried out. This is to ensure that the proposed
system is not a burden to the company. For feasibility analysis, some understanding of the
major requirements for the system is essential.
Three key considerations involved in the feasibility analysis are
 Economical Feasibility
 Technical Feasibility
 Social Feasibility

4
I. ECONOMICAL FEASIBILITY
This study is carried out to check the economic impact that the system will have on the
organization. The amount of fund that the company can spend into the research and
development of the system is limited. The expenditures must be justified. Thus the developed
system as well within the budget and this was achieved because most of the technologies used
are freely available. Only the customized products had to be purchased.

II. TECHNICAL FEASIBILITY

This study is carried out to check the technical feasibility, that is, the technical
requirements of the system. Any system developed must not have a high demand on the
available technical resources. This will lead to high demands on the available technical
resources. This will lead to high demands being placed on the client. The developed system
must have a modest requirement, as only minimal or null changes are required for
implementing this system.

III. SOCIAL FEASIBILITY

The aspect of study is to check the level of acceptance of the system by the user. This
includes the process of training the user to use the system efficiently. The user must not feel
threatened by the system, instead must accept it as a necessity. The level of acceptance by the
users solely depends on the methods that are employed to educate the user about the system
and to make him familiar with it. His level of confidence must be raised so that he is also able
to make some constructive criticism, which is welcomed, as he is the final user of the system.

2.5 PROJECT MODULE DESCRIPTION

The project contains following modules:
• User management
• Book Inventory Module
• Book Borrowing Module
• Search Facility Management
• Assign Book Module
• Pending Overdue Books From Inventory
User management
The web application can add members quickly, add books, browse members, search
books, update information, edit information, borrow and return books in the shortest time
possible. It focuses on paperless lending and stock management.
5
Book Inventory Module
Book search processes become much easier with just a mouse click. Stores all books
and member information, such as the name of the book, the name of the author of the book’s
title, the publications, and the information on the shelf in the database.

Search Facility Management

In addition, it provides a search function to help students get the book by the access
number/name of the author/title of the book. The librarian is willing to view and edit data from
the machine’s database. The administrator may feel like creating users for the system.

Assign Book Module

The books are assigned to the students and, once the date of the assignment is made, the
date of return will be shown along with the arrears charges.

Users:
This module will allow admin to add users in the sense students who will actually be
provided with books. Type in Student ID, Student Name, select Year and Branch from a
respective year and Branch drop downs and click on Add User.The saved Student details will
be beaded in the grid. It provides edit option which when clicked will provide Update option.
Edit will actually allow name, branch and year details to be edited in edit mode. Click on the
Update button to update the updated values.

Books:
This module will allow admin to Add books to the application, Edit the Book Details
and then delete a Book detail.

To add book:
Provide a Book ID, Book Name, Book Publisher Name, Book Published year, Book
Price, Book Quantity. Click on Add to save the Book details. Click on Reset to clear all fields
in the view.
To Edit Book details:
Select Edit option.Type in Book Id, click on Check and it will show details related to
the searched Book ID. Edit the field values whichever needed to be and click on Update.Click
on Reset to clear all fields in the view.

6
3. SYSTEM REQUIREMENT
HARDWARE AND SOFTWARE CONFIGURATION
3.1 HARDWARE SPECIFICATION
The hardware used for the development of the project is:
Processor : Pentium III 866 MHz
Hard Disk Capacity : 40 GB
RAM : 128 MB
Monitor : 15” Color
Keyboard : 102 keys
Mouse : 3 buttons
3.2 SOFTWARE SPECIFICATION
The software used for the development of the project is:
Operating system : Windows XP professional
Environment : Visual studio .Net 2012
.Net framework : Version 3.5
Front end : ASP.NET
Back end : SQL SERVER 2005.
3.3 ABOUT SOFTWARE
In this project .NET Framework is used as front end tool. .NET is one of the most
beautiful and recently more popular front-end tools. It contains several parts of techniques.
They are VB.NET, ASP.NET, and XML.NET. This is used in this project. In this project SQL
Server is used as the back-end tool. This is the default back-end tool of VB.NET. Then it
comes the turn of the operating system. The good and preferred OS for .NET is Window 2003.
We can also use Windows 2000 Server and Window XP. In this project we are using
Windows 2003 as platform.
VB.NET AN OVERVIEW:
The Microsoft Visual Basic .NET programming language is a high-level programming
language for the Microsoft.NET Framework. Although it is designed to be an approachable
and easy-to-learn language, it is also powerful enough to satisfy the needs of experienced
programmers. The Visual Basic .NET programming language is closely related to the Visual
Basic programming language but the two languages are not the same.
A discussion of the different between Visual Basic.NET and Visual Basic 6.0 is beyond
the scope of this document. The Visual Basic .NET programming language has a syntax that
is similar to English, which promotes the clarity and readability of Visual Basic .NET code.

7
Wherever possible, meaningful words or phases are used instead of abbreviations, acronyms,
or special character. Extraneous or unneeded syntax is generally allowed but not required.
The Visual Basic .NET programming language can be either a strongly typed or a loosely
typed language. Loose typing defers much of the burden of type checking until a program is
already running. This includes not only type checking of conversions but also of method calls,
meaning that the binding of a method call can be deferred until run-time. This is useful when
building prototypes or other programs in which speed of development is more important than
execution speed. The Visual Basic .NET programming language also provides strongly typed
semantics that performs all type checking at compile-time and disallows strongly typed
semantics that performs all type checking at compile-time and disallows run-time binding of
method calls. This guarantees maximum performance and helps ensure that type conversions
are correct. This is useful when building production applications in which speed of execution
and execution correctness is important.
Features of VB.NET
VB.NET is a program that is the advanced version of VB 6.0. Microsoft is the
company that developed this language. VB.NET is a good and powerful language. The main
features of the VB.NET are
 Object oriented language.
 Powerful language for development of application programs
 Multithreading and Multitasking
 Internet Programming
 Intranet Programming
 Interpretability
Microsoft’s Visual Studio.NET Framework

.
Common Language Runtime

Class Libraries

Programming Languages
(VB.NET, C#, VC++, Jscript.NET)

ASP.NET

8
4. SOFTWARE DESCRIPTION

SOFTWARE DESCRIPTION

THE .NET FRAMEWORK

The .NET Framework is a new computing platform that simplifies application
development in the highly distributed environment of the Internet.

OBJECTIVES OF. NET FRAMEWORK

1. To provide a consistent object-oriented programming environment whether object
codes is stored and executed locally on Internet-distributed, or executed remotely.
2. To provide a code-execution environment to minimizes software deployment and
guarantees safe execution of code.
3. Eliminates the performance problems.
There are different types of application, such as Windows-based applications and Web-
based applications.To make communication on distributed environment to ensure that code be
accessed by the .NET Framework can integrate with any other code.

COMPONENTS OF. NET FRAMEWORK

THE COMMON LANGUAGE RUNTIME (CLR)

The common language runtime is the foundation of the .NET Framework. It manages
code at execution time, providing important services such as memory management, thread
management, and remoting and also ensures more security and robustness. The concept of
code management is a fundamental principle of the runtime. Code that targets the runtime is
known as managed code, while code that does not target the runtime is known as unmanaged
code.

THE .NET FRAME WORK CLASS LIBRARY

It is a comprehensive, object-oriented collection of reusable types used to develop
applications ranging from traditional command-line or graphical user interface (GUI)
applications to applications based on the latest innovations provided by ASP.NET, such as
Web Forms and XML Web services.The .NET Framework can be hosted by unmanaged
components that load the common language runtime into their processes and initiate the
execution of managed code, thereby creating a software environment that can exploit both
managed and unmanaged features.

9
 The .NET Framework not only provides several runtime hosts, but also supports the
development of third-party runtime hosts. Internet Explorer is an example of an unmanaged
application that hosts the runtime (in the form of a MIME type extension). Using Internet
Explorer to host the runtime to enables embeds managed components or Windows Forms
controls in HTML documents.
FEATURES OF THE COMMON LANGUAGE RUNTIME
The common language runtime manages memory; thread execution, code execution,
code safety verification, compilation, and other system services these are all run on CLR.
 Security
 Robustness
 Productivity
 Performance
SECURITY
The runtime enforces code access security. The security features of the runtime thus
enable legitimate Internet-deployed software to be exceptionally feature rich. With regards to
security, managed components are awarded varying degrees of trust, depending on a number of
factors that include their origin to perform file-access operations, registry-access operations, or
other sensitive functions.
ROBUSTNESS
The runtime also enforces code robustness by implementing a strict type- and code-
verification infrastructure called the common type system(CTS). The CTS ensures that all
managed code is self-describing. The managed environment of the runtime eliminates many
common software issues.
PRODUCTIVITY
The runtime also accelerates developer productivity. For example, programmers can
write applications in their development language of choice, yet take full advantage of the
runtime, the class library, and components written in other languages by other developers.
PERFORMANCE
The runtime is designed to enhance performance. Although the common language
runtime provides many standard runtime services, managed code is never interpreted. A feature
called just-in-time (JIT) compiling enables all managed code to run in the native machine
language of the system on which it is executing. Finally, the runtime can be hosted by high-
performance, server-side applications, such as Microsoft® SQL Server™ and Internet
Information Services (IIS).

10
DATA ACCESS WITH ADO.NET
As we develop applications using ADO.NET, you will have different requirements for
working with data. You might never need to directly edit an XML file containing data - but it
is very useful to understand the data architecture in ADO.NET.
ADO.NET offers several advantages over previous versions of ADO:
 Interoperability
 Maintainability
 Programmability
 Performance Scalability

INTEROPERABILITY
ADO.NET applications can take advantage of the flexibility and broad acceptance of
XML. Because XML is the format for transmitting datasets across the network, any component
that can read the XML format can process data. The receiving component need not be an
ADO.NET component. The transmitting component can simply transmit the dataset to its
destination without regard to how the receiving component is implemented. The destination
component might be a Visual Studio application or any other application implemented with
any tool whatsoever. The only requirement is that the receiving component be able to read
XML. SO, XML was designed with exactly this kind of interoperability in mind.

MAINTAINABILITY
In the life of a deployed system, modest changes are possible, but substantial,
Architectural changes are rarely attempted because they are so difficult. As the performance
load on a deployed application server grows, system resources can become scarce and response
time or throughput can suffer. Faced with this problem, software architects can choose to
divide the server's business-logic processing and user-interface processing onto separate tiers
on separate machines. In effect, the application server tier is replaced with two tiers, alleviating
the shortage of system resources. If the original application is implemented in ADO.NET using
datasets, this transformation is made easier. ADO.NET data components in Visual Studio
encapsulate data access functionality in various ways that help you program more quickly and
with fewer mistakes.

PERFORMANCE
ADO.NET datasets offer performance advantages over ADO disconnected record sets.
In ADO.NET data-type conversion is not necessary.
11
SCALABILITY
ADO.NET accommodates scalability by encouraging programmers to conserve limited
resources. Any ADO.NET application employs disconnected access to data; it does not retain
database locks or active database connections for long durations.

VISUAL STUDIO .NET

Visual Studio .NET is a complete set of development tools for building ASP Web
applications, XML Web services, desktop applications, and mobile applications In addition to
building high-performing desktop applications, you can use Visual Studio's powerful
component-based development tools and other technologies to simplify team-based design,
development, and deployment of Enterprise solutions.
Visual Basic .NET, Visual C++ .NET, and Visual C# .NET all use the same integrated
development environment (IDE), which allows them to share tools and facilitates in the
creation of mixed-language solutions. In addition, these languages leverage the functionality of
the .NET Framework and simplify the development of ASP Web applications and XML Web
services.
Visual Studio supports the .NET Framework, which provides a common language
runtime and unified programming classes; ASP.NET uses these components to create ASP
Web applications and XML Web services. Also it includes MSDN Library, which contains all
the documentation for these development tools.

VISUAL BASIC .NET

Visual Basic. NET, the latest version of visual basic, includes many new features. The
Visual Basic supports interfaces but not implementation inheritance. Visual basic.net supports
implementation inheritance, interfaces and overloading. In addition, Visual Basic .NET
supports multithreading concept.

12
COMMON LANGUAGE SPECIFICATION (CLS)
Visual Basic.NET is also compliant with CLS (Common Language Specification) and
supports structured exception handling. CLS is set of rules and constructs that are supported by
the CLR (Common Language Runtime). CLR is the runtime environment provided by the
.NET Framework; it manages the execution of the code and also makes the development
process easier by providing services.
Visual Basic.NET is a CLS-compliant language. Any objects, classes, or components
that created in Visual Basic.NET can be used in any other CLS-compliant language. In
addition, we can use objects, classes, and components created in other CLS-compliant
languages in Visual Basic.NET .The use of CLS ensures complete interoperability among
applications, regardless of the languages used to create the application.

IMPLEMENTATION
Visual Basic.NET supports implementation inheritance. This means that, while creating
applications in Visual Basic.NET, we can drive from another class, which is know as the base
class that derived class inherits all the methods and properties of the base class. In the derived
class, we can either use the existing code of the base class or override the existing code.
Therefore, with help of the implementation inheritance, code can be reused.

CONSTRUCTORS AND DESTRUCTORS

Constructors are used to initialize objects, whereas destructors are used to destroy them.
In other words, destructors are used to release the resources allocated to the object. In Visual
Basic.NET the sub finalize procedure is available. The sub finalize procedure is used to
complete the tasks that must be performed when an object is destroyed. The sub finalize
procedure is called automatically when an object is destroyed. In addition, the sub finalize
procedure can be called only from the class it belongs to or from derived classes.

GARBAGE COLLECTION
Garbage Collection is another new feature in Visual Basic.NET. The .NET Framework
monitors allocated resources, such as objects and variables. In addition, the .NET Framework
automatically releases memory for reuse by destroying objects that are no longer in use. In
Visual Basic.NET, the garbage collector checks for the objects that are not currently in use by
applications. When the garbage collector comes across an object that is marked for garbage
collection, it releases the memory occupied by the object.

13
OVERLOADING
Overloading is another feature in Visual Basic.NET. Overloading enables us to define
multiple procedures with the same name, where each procedure has a different set of
arguments. Besides using overloading for procedures, we can use it for constructors and
properties in a class.

MULTITHREADING
Visual Basic.NET also supports multithreading. An application that supports
multithreading can handle multiple tasks simultaneously, we can use multithreading to
decrease the time taken by an application to respond to user interaction. To decrease the time
taken by an application to respond to user interaction, we must ensure that a separate thread in
the application handles user interaction.

STRUCTURED EXCEPTION HANDLING

Visual Basic.NET supports structured handling, which enables us to detect and remove
errors at runtime. In Visual Basic.NET, we need to use Try…Catch…Finally statements to
create exception handlers. Using Try…Catch…Finally statements, we can create robust and
effective exception handlers to improve the performance of our application.

MS -ACCESS 2000
It is a personal computer based RDBMS. This provides most of the features available in
the high-end RDBMS products like Oracle, Sybase, Ingress etc. VB keeps access as its native
database. Developer can create a database for development & further can create. The tables
are required to store data. During the initial Development phase data can be stored in the
access database & during the implementation phase depending on the volume data can use a
higher – end database. Office Access, previously known as Microsoft Access, is an active
secure database embedded in a virtual object-oriented work cluster. It is a member of the 2007
Microsoft Office system. Access can use data stored in Access/Jet, Microsoft SQL Server,
Oracle, or any ODBC-compliant data container. Skilled software developers and data
architects use it to develop application software. Relatively unskilled programmers and non-
programmer "power users" can use it to build simple applications. It supports some object-
oriented (OO) techniques but falls short of being a fully OO development tool. Access was also
the name of a communications program from Microsoft, meant to compete with ProComm and
other programs. This Access proved a failure and was dropped. Years later Microsoft reused
the name for its database software.
14
5. SYSTEM DESIGN
The design of the system is essentially a blue print, or plan for a solution of the system
to be developed. A part of the system or subsystem of a whole of the system can itself be
considered a system with its own complements. Here the focus is on detecting that which is all
the modules method needed for the system, the specification of these design is the only way by
which we can accurately translate the end-user requirements in to a finished software product
or system. The data flow oriented design in an architectural design method that allows a
convenient transition from the analysis model to a design description of program structure the
DFD presents a system overview depicting its overall purpose an its interactions with external
objects it provides a general pictorial of data transformations in the system.
A DFD shows the flow of data through a system which may be a manual procedure
software system, a hard ware system or any combination of these. A DFD shows the
movements of the data through the different transformations, which are the process in the
system. DFD are made up of a number of symbols, which represent system components,
process, data store, and data flow and external entities.

5.1 INPUT DESIGN

Input Design is one of the most expensive phases of the operation of
computerized system and is often the major problem of a system. A large number of
problems with a system can usually be tracked backs to fault input design and method.
Needless to say, therefore, that the input data is the life blood of a system and have to
be analysed and designed with utmost case and consideration.
The decisions made during the input design are
 To provide cost effective method of input.
 To achieve the highest possible level of accuracy.
 To ensure that the input is understand by the user.
System analysis decide the following input design details like, what data to input,
what medium to use, hoe the data should be arranged or coded, data items and
transactions needing validations to detect errors and at last the dialogue to guide user
in providing input. Input data of a system may not be necessarily be raw data captured
in the system from scratch. These can also be the output of another system or sub
system. The design of input covers all phases of input from the creation of initial data
to actual entering the data to the system for processing. The design of inputs involves
identifying the data needed, specifying the characteristics of each data item, capturing and
preparing data for computer processing and ensuring correctness of data.
15
5.2 DATABASE DESIGN
The most important consideration in designing the database is how information will be used.
The main objectives of designing a database are:
 Data Integration
 Data Integrity
 Data Independence

Data Integration
In a database, information from several files are coordinated, accessed and operated
upon as through it is in a single file. Logically, the information are centralized, physically, the
data may be located on different devices, connected through data communication facilities.

Data Integrity
Data integrity means storing all data in one place only and how each application to
access it. This approach results in more consistent information, one update being sufficient to
achieve a new record status for all applications, which use it. This leads to less data
redundancy; data items need not be duplicated; a reduction in the direct access storage
requirement.

Data Independence
Data independence is the insulation of application programs from changing aspects of
physical data organization. This objective seeks to allow changes in the content and
organization of physical data without reprogramming of applications and to allow
modifications to application programs without reorganizing the physical data.The tables
needed for each module were designed and the specification of each and every column was
given based on the records and details collected during record specification of the system
study.

5.3 CODE DESIGN

The code design should be such that with less amount of coding we can achieve more
results. The speed of the system will be more if the coding is less. Whether the data in the
system is usable and readable by the system is depending on the coding. In the project, the
coding is being done such that proper validations are made to get the perfect input. No error
inputs are accepted.

16
 In addition care is taken such that the data integrity and referential integrity is not
violated in the database. When large volumes of data are being handled, it is important that the
items to be stored selected easily and quickly. To accomplish this, each data item must have a
unique specification and must be related to other forms or item of data of the same type. The
master file transaction within related to the same type in the other table with using primary
key. A primary key item in master file is related to another table. In that table, it acts as the
foreign key.

5.4 OUTPUT DESIGN

Output Design generally refers to the results and information’s that are generated
by the system for many end-users, output is the main reason for developing the system
and the basis on which they evaluate the usefulness of the application. The objective of
a system finds its shape in terms of the output. The analysis of the objective of a
system leads to determination of outputs. Outputs of a system can face various forms.
The most common are reports, screen displays, printed forms, graphical drawings etc.,The
output also vary in terms of their contents frequency, timing and format. The user of
the output from a system are the justification for its existence. If the output are
inadequate in any way, the system are itself is adequate. The basic requirements of
output are that it should be accurate, timely and appropriate, in terms of content,
medium and layout for its intended purpose.
When designing output, system analysis most accomplish things like, to determine
what information to be present, to decide whether to display or print the information
and select the output medium and to decide how to distribute the output to intended
recipients. External outputs are those whose destination will be outside the organization
and which require special attention as they project the image of the organization.
Internal outputs are those whose destination is within the organization. it is to be carefully
designed as they are the users main interface with the system.

17
5.5 DATA FLOW DIAGRAM
A Data Flow Diagram (DFD) or a Bubble Chart is a graphical tool for structured
analysis, it was De Marco (1978) and Gane and Sarson (1979) who introduced DFD. DFD
models a system by using external entities from which data flows to process, which transforms
the data and creates, output-data-flows which go to other processes or external entities or files.
Data in files may also flow to processes as inputs.
These are various symbols used in a DFD. Bubbles represent the processes. Named
arrows indicate the dataflow. External entities are represented by rectangles and are outside
the system such as vendors or customers with whom the system interacts. They either supply
or consume data. Entities supplying data are known as sources and those that consume data
are called sinks. Data are stored in a data store by a process in the system. Each component in
a DFD is labeled with a descriptive name. Process names are further identified with a number.
DFD’s can be hierarchically organized, which help in partitioning and analyzing large
systems. As a first step, one Data Flow Diagram can depict and entire system which gives he
system overview. It is called Context Diagram of level 0 DFD. The Context Diagram can be
further expanded. The successive expansion of a DFD from the context diagram to those
giving more details is known as leveling of DFD. Thus a top down approach is used, starting
with an overview and then working out the details.The main merit of DFD is that it can provide
an overview of what data a system would process, what transformation of data are done, what
files are used, and where the result flow.

18
Basic DFD Symbols

A data flow is a route, which enables packets of data to travel from one
point to another. Data may flow a source to a processor and from data store or
process. An arrow line depicts The Flow, with arrow head pointing in the
direction of the flow.

A process represents transformation where incoming data flows are

changed into outgoing data flows.

A data stored is repository of data that is to be stored for use by one or

more processes. It may be as simple a buffer or queue or sophisticated as
relational database. They should have clear names. If a process merely uses the
content of store and does not alert it, the arrowhead goes only from the store to
the process. If a process alters the detail in the store then a double-headed
arrow is used.

A source or sink is a person or part of an organization which enter or

receives information from the system, but is considered to be outside the contest
of dataflow model.

19
DATA FLOW DIAGRAM

Level - 0

EDIT BOOK
DETAILS

DELETE
BOOK
DETAILS
ADMIN

ASSIGN

OVER
DUE

20
6. SYSTEM TESTING
TESTING
After the source code has been completed, documented as related data structures.
Completed the project has to undergo testing and validation where there is subtitle and definite
attempt to get errors. The project developer treads lightly, designing and execution test that
will demonstrates that the program works rather than uncovering errors, unfortunately errors
will be present and if the project developer doesn’t find them, the user will find out.The project
developer is always responsible for testing the individual units i.e. modules of the program. In
many cases developer also conducts integration testing i.e. the testing step that leads to the
construction of the complete program structure.
This project has undergone the following testing procedures to ensure its correctness.
 Unit testing
 Integration testing
 Validation testing
 User Acceptance Testing

6.1 UNIT TESTING

In unit testing, we have to test the programs making up the system. For this reason,
Unit testing sometimes called as Program testing. The software units in a system are the
modules and routines that are assembled and integrated to perform a specific function, Unit
testing first on the modules indepently of one another, to locate errors. This enables, to detect
errors in coding and logic that are contained with the module alone. The testing was carried
out during programming stage itself.

6.2 INTEGRATION TESTING

Integration testing is a systematic technique for constructing the program structure.
While at the same time conducting tests to uncover errors associated with interfacing. The
objective is to take unit tested modules and build a program structure that has been dictated by
design. In this integration testing its done using the main module and based on the type of
integration testing the subordinate stubs are replaced one at a time with actual modules.

6.3 VALIDATION TESTING

In the project Validation is made such that, only the raw materials entered in the raw
material master table can be accepted during the purchase. Only after the selection of the
products, the record can be added.
21
 Otherwise a message is displayed to enter the product details. During the purchase
return, the item quantity returned cannot exceed the stock maintained. Negative stock is not
allowed. The customer details entered in the lot section details alone can be entered in the
delivery bill.

6.4 USER ACCEPTANCE TESTING

The system under consideration is tested for user acceptance by constantly keeping in
touch with the prospective system user at the time of developing and making changes
whenever required.

22
7. SYSTEM IMPLEMENTATION AND MAINTENANCE
7.1 IMPLEMENTATION
When the initial design was done for the system, the client was consulted for the
acceptance of the design so that further proceedings of the system development can be carried
on. After the development of the system a demonstration was given to them about the working
of the system. The aim of the system illustration was to identify any malfunction of the system.
After the management of the system was approved the system implemented in the
concern, initially the system was run parallaly with existing manual system. The system has
been tested with live data and has proved to be error free and user friendly.
Implementation is the process of converting a new or revised system design into an
operational one when the initial design was done by the system; a demonstration was given to
the end user about the working system. This process is uses to verify and identify any logical
mess working of the system by feeding various combinations of test data. After the approval
of the system by both end user and management the system was implemented.
System implementation is made up of many activities.
The six major activities as follows.
 Coding
 Testing
 Installation
 Documentation
 Training and support
Coding
Coding is the process of whereby the physical design specifications created by the
analysis team turned into working computer code by the programming team.
Testing
Once the coding process is begin and proceed in parallel, as each program module can
be tested.
Installation
Installation is the process during which the current system is replaced by the new
system. This includes conversion of existing data, software, and documentation and work
procedures to those consistent with the new system.
Documentation
It is result from the installation process, user guides provides the information of how
the use the system and its flow.

23
Training and support
Training plan is a strategy for training user so they quickly learn to the new system.
The development of the training plan probably began earlier in the project. The best-suited
application package to develop medical system is Visual Basic .NET under windows XP’
environment. Visual Basic .NET has all them features that can store, edit, retrieve, and print
information quickly and easily access the broad range of application.

7.2 MAINTENANCE
After development of the software, Maintenance of software is important aspect.
Maintainability is the ease with which software can be understood and corrected,
adapted and enhanced. The goal is to improve the ease with which changes can be
accommodated and reduce the amount of effort expanded on maintenance. Software
maintenance is one of the phases in, and follows deployment of the software into the field. The
software maintenance phase involves changes to the software in order to correct defects and
deficiencies found during field usage as well as the addition of new functionality to improve
the software's and applicability.Maintenance can be classified as,
 Corrective
 Adaptive
 Perfective.

CORRECTIVE MAINTENANCE
Corrective maintenance means repairing processing or performance failures or making
changes because of previously uncorrected problems of false assumptions. In this project, the
existing system can’t control the task manger with maximum duration of the time, now it is
over come with user time consumption.
PERFECTIVE MAINTENANCE
Perfective maintenance means enhancing performance or modifying the programs to
respond to the user’s additional or changing needs. In this project, various links are available
instead of menus are available so it successfully interactive with the user.
ADAPTIVE MAINTENANCE
Adaptive maintenance means changing the program function. Of these types more time
and money are spent on perfective than on corrective and adaptive maintenance together. This
project should be inter-operability with Hardware devices and also interact with the other
software’s.

24
8. CONCLUSION
The selection of data can be extended. The user’s information maintenance, all the
details of the databases can be implemented. It’s time is consumed and provided to the security
.All the data values that stored in the table can be extended. In this computerized system there
will be no loss of book record or member record which generally happens when a non-
computerized system is used. In addition, report module is also included in Library
Automation System. If user’s position is admin, the user is able to generate different kinds of
reports like lists of students registered, list of books, issue and return reports. All these modules
are able to help librarian to manage the library with more convenience and in a more efficient
way as compared to library systems which are not computerized.

25
9. BIBLIOGRAPHY

1) “. NET developers guide 2002”- Prentice-Hall India.- Grey Buczek,

2) “VB.NET by example 2003” – TataMcGraw-Hill- Benolt Marchal,
3) “System Analysis & Design” – Alenis Leon.
4) “An Integral approach to software engineering” – Pankaj Jalole.
5) “Microsoft Visual Basic.NET Programmer’s Cookbook”-
(TataMcGraw-Hill Edition)-MATTHEW MACDONALD
6) Jittery R.Shapiro, “The Complete Reference Visual Basic .NET” Edition 2002, Tata
McGraw-Hill, Publishing Company Limited, New Delhi.
7) Ian Sommerville “Software Engineering”
8) “Modern System Analysis and Design”
 Jeffrey A.Hoffer
 Joey F.George
 Joseph S.Valacich

WEBSITES
1.http://www.dotnetheaven.com
2.http://www.startvbdotnet.com/
3.http://msdn.microsoft.com/vbasic/using/understanding/data/default.aspx

26
10. APPENDIX

10.1 SCREENS

27
28
29
10.2 SOURCE CODING
ASP .NET code for Login:
using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;
public partial class Login : System.Web.UI.Page
{
protected void Page_Load(object sender, EventArgs e)
{
try
{
Request.Cookies["user"].Expires = DateTime.Now.AddMinutes(-30);
Request.Cookies.Remove("user");
}
catch (Exception)
{
}
}
protected void btnLogin_Click(object sender, EventArgs e)
{
if (inputEmail.Value == "admin" && inputPassword.Value =="admin@123")
{
Response.Cookies["user"]["login"] = "true";
Response.Redirect("Home.aspx");
}
}}
ASP .NET code for Book Assign:
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Configuration;
using System.Data;
30
using System.Data.SqlClient;
public partial class BookAssign : System.Web.UI.Page
{
SqlConnectioncon=new
SqlConnection(ConfigurationManager.ConnectionStrings["bs"].ConnectionString);
SqlCommand cmd = new SqlCommand();
SqlDataAdapter da;
DataSet ds;
string sql_query;
protected void Page_Load(object sender, EventArgs e)
{
}
protected void btn_Assign_Click(object sender, EventArgs e)
{
try
{
string returndate = DateTime.Today.AddDays(15).ToShortDateString();
sql_query = "Insert into Assign (studentid, bookid, assigneddate, returndate, penality, statusid)
values ('" + txt_assign_studentid.Text.Trim() + "','" + txt_assign_bookid.Text.Trim() + "','" +
txt_assign_bookdate.Text.Trim() + "','" + returndate + "','0','s1')";
cmd = new SqlCommand(sql_query, con);
con.Open();
cmd.ExecuteNonQuery();
con.Close();
lblresult_bookassign.Text = "<b>Book ID :</b> " + txt_assign_bookid.Text + " is assigned to
<b>Student ID :</b> " + txt_assign_studentid.Text + " on the <b>Date of :</b> " +
txt_assign_bookdate.Text + " and you have to <b>return on Date :</b> " + returndate + "
otherwise <b>Penality per day : </b> 5 Rupees.";
}
Catch
{
con.Close();
}
}
protected void txt_assign_bookid_TextChanged(object sender, EventArgs e)
31
{
try
{
sql_query = "Select * from BookRecord Where bookid='" + txt_assign_bookid.Text.Trim() +
"'";
da = new SqlDataAdapter(sql_query, con);
ds = new DataSet();
da.Fill(ds);
if (ds.Tables[0].Rows.Count > 0)
{
txt_assign_bookid.Text = ds.Tables[0].Rows[0]["bookid"].ToString();
txt_assign_bookname.Text = ds.Tables[0].Rows[0]["bookname"].ToString();
txt_assign_bookqty.Text = ds.Tables[0].Rows[0]["bookquantity"].ToString();
txt_assign_bookdate.Text = DateTime.Today.Date.ToShortDateString();
}
}
catch
{
con.Close();
}
}
protected void txt_assign_studentid_TextChanged(object sender, EventArgs e)
{
try
{
sql_query = "Select * from Student Where studentid='" + txt_assign_studentid.Text.Trim() +
"'";
da = new SqlDataAdapter(sql_query, con);
ds = new DataSet();
da.Fill(ds);
if (ds.Tables[0].Rows.Count > 0)
{
txt_assign_studentid.Text = ds.Tables[0].Rows[0]["studentid"].ToString();
txt_assign_studentname.Text = ds.Tables[0].Rows[0]["studentname"].ToString();
txt_assign_studentbranch.Text = ds.Tables[0].Rows[0]["studentbranch"].ToString();
32
txt_assign_studentyear.Text = ds.Tables[0].Rows[0]["studentyear"].ToString();
}
}
catch
{
con.Close();
}
}
}

ASP .NET code for User:

using System;
using System.Collections.Generic;
using System.Data.SqlClient;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;
public partial class Users : System.Web.UI.Page
{
protected void Page_Load(object sender, EventArgs e)
{
}
protected void btnAdd_Click(object sender, EventArgs e)
{
try
{
SqlConnection conn = new
SqlConnection(System.Configuration.ConfigurationManager.ConnectionStrings["LIBRARYC
onnectionString"].ConnectionString);
SqlCommand cmd = new SqlCommand("insert into Student
(studentid,studentname,studentbranch,studentyear) values (@id,@name,@branch,@year)",
conn);
cmd.Parameters.AddWithValue("@id", txtStudentId.Text);
cmd.Parameters.AddWithValue("@name", txtStudentName.Text);
33
cmd.Parameters.AddWithValue("@branch", ddlBranch.SelectedValue );
cmd.Parameters.AddWithValue("@year", ddlyear.SelectedValue);
try
{
conn.Open();
cmd.ExecuteNonQuery();
GridView1.DataBind();
txtStudentId.Text = "";
txtStudentName.Text = "";
}
catch (Exception ex)
{
}
finally
{
conn.Close();
}
}
catch (Exception ex)
{
}
}
}

34