Lib Main

SYNOPSIS
Book keeping is the main task in Library Administration. In the old method of book
keeping, preserving the manually written records and ledgers were very hard. Paper records
date back to more than 10 years require some special chemical to get preserved. By applying
some sort of special chemicals we can preserve them only for certain years. Moreover for
every transaction, we should make some entries on more than one corresponding ledgers.
Hence it is a laborious work to keep manually the book transaction in a library.
But the computerized book keeping relieves us from these burdens. The data are
written on electronic media which can be processed as and when required even after 100
years. The data can be copied, altered, reproduced in black and white form at any time. The
book transaction can also be done automatically. The computer employed in the book
keeping will make necessary entries in the corresponding ledgers.
It gives users the ability to search thorough materials by their unique assigned item
numbers, titles, author names, subject and keywords with or without any restriction on place
(for example queries only on reference section or any group of given sections are valid),
borrowing state (i.e. the book is usable or book has been barrowed more than 5 times that
year) and item type. Giving exact or partial phrases can do these searches. Users can borrow
items and they can put reserve on items for further borrowings.
User penalties for late returned items are automatically calculated by administrator
given constants, and users can be restricted to borrow any more items if they have penalty
more than an administrator set value. When there is more than one reserve on an item the
reserves are assigned automatic sequence numbers according to their reserve time so that first
person to reserve an item gets an opportunity to borrow the item first for a time period, then
the second person reserved that item.
Administrators are able to add items to the library; they can remove items as well as
they can change information on an item (i.e. location, mistyped title or any other item related
data). They can also list workers in each department and their working hours. Administrators
can view the borrow history to find out all the users that borrowed a specific material to keep
1
track of possibly missing or damaged library items. Administrators can add new users or
workers to the library, delete existing users or workers or modify user or worker information.
The LMS consists of three parts - one is user menu, the other is for the worker menu
in the library these are the clients that requests information from the server. The third part of
the program is the server, which is a bridge across the client and the actual database. As soon
as it gets a request from one of the clients it opens a connection to database send the query in
order to reply the requests of clients and after taking the result from database it sends the
result to the client.
The users will interact with the user menu and the workers will interact with the
worker menu. There is no access control for user menu but as worker menu starts it asks for a
password for security issues. There is also a server, which these clients interact with.
2
1. INTRODUCTION
1.1. PROJECT OVERVIEW

The project “Digitized Library Management System” is developed in VB.NET as
Front end and MS-Access as Backend. It gives users the ability to search thorough materials
by their unique assigned item numbers, titles, author names, subject and keywords with or
without any restriction on place (for example queries only on reference section or any group
of given sections are valid), borrowing state (i.e. the book is usable or book has been
barrowed more than 5 times that year) and item type
Home
This option takes the user to the homepage. Every pages of this website contains this
option.
About Us
This option gives idea about the operations of the Central Library with the history and
about the staff members.
Membership
This option enables users
1. To join as a new member - An application seeking details about the user will be
presented and on submission of the same the details will be structured for its
genuineness. The member will be invited for collecting the membership card.
2. To know about the waiting status.
3. To see the details of a particular member
4. To see the withdraw membership
Books
This option presents the details of the books available in the library. Every book will
be given a unique code number. The title of the books will be displayed as per the code
number. The details of the books can be viewed as per the subjects, book name, author name
and Publishers.
3
Transaction
This option presents
1. Details regarding the distributed of books. The details contain name of the
member, name of the book, Due date and penalty (if any).
2. Details of books delivered
3. Details of books to be returned as on date
Stock:
Number of books on hand, number of books damaged, number of books lent, number
of books missed are presented on selecting this option.
Branches:
Details of libraries of different location can be viewed on selecting this option.
Journals:
Details of magazines, daily newspaper and novels are given.
Office use:
This is meant for administering the database. The details collected from the options
specified above are stored in a database. Users are given a unique password to process their
data only. They are not allowed to process data of other users. The data of all the users can
be processed by authorized staff members of the library only by entering this option.
Feedback:
Opinion of the website users about this website are gathered through this option.
4
1.2. ORGANIZATION PROFILE
Thamizh Technologies is a professionally managed organization providing total HR
Solutions, Recruitments, Outsourcing and Training to various companies. We provide
services to various types of students which include Engineering, IT, Management department
etc.
GROUP
We have an enviable history of providing high quality services in the fields of R&D,
Design and Development, Training and HR Consulting in Sivaganga. Our organization has
already established its reputation in offering High quality education in the areas of
Engineering, Arts, Science, and Management Courses.
We have a well-documented quality system, which helps us to monitor measure and

analyze our performance and also to improve our service and delivery standards. We have a
dedicated team of people for monitoring the quality norms.
SERVICES
We dedicate our trainees in Software Development, Human Resource Consulting,
Academic Assistance and Training.
5
2. SYSTEM SPECIFICATION
2.1. HARDWARE SPECIFICATION

 Main Processor : Pentium Dual Core or Above
 RAM : DDR-III 2GB.
 Display Type : SVGA
 Hard Disk : 160 GB
 Keyboard : 108 Keys
 Mouse : Optical Mouse.
2.2. SOFTWARE SPECIFICATION

 Operating System : Windows 7 or Later
 Front End : VB.NET 2010.
 Back End : MS-ACCESS.
2.3. SOFTWARE OVERVIEW

VB.Net, the next generation of visual basic is designed to be the easiest and most
productive tool for creating .NET applications, including Windows applications, Web
Services and Web applications. Visual Basic .NET is a major component of Microsoft Visual
Studio .NET suite. The .NET version of Visual Basic is a new improved version with more
features and additions. After these new additions, VB qualify to become a full object-oriented
language such as C++. VB.NET is the following version of VB 6.0. Microsoft .NET is a new
programming and operating framework introduced by Microsoft. All .NET supported
languages access a common .NET library to develop applications and share common tools to
execute applications. Programming with visual basic using .net is called VB.Net.
While providing the traditional ease-of-use of Visual Basic development, Visual

Basic .NET also allows optional use of new language features. Inheritance, method
overloading, structured exception handling, and free threading all make Visual Basic a
powerful object-oriented programming language. Visual Basic .NET fully integrates with the
.NET Framework and the Common Language Runtime, which together provide language
interoperability, simplified deployment, enhanced security, and improved versioning support.
6
.NET FRAMEWORK
The .NET Framework is an environment for building, deploying, and running Web
Services and other applications. It is the infrastructure for the overall .NET Platform. The
framework consists of three main parts: the Common Language Runtime, the class libraries,
and VB.NET.
The Common Language Runtime and class libraries, including Windows Forms,
ADO.NET, and VB.NET, combine together to provide services and solutions that can be
easily integrated within and across a variety of systems. The .NET Framework provides a
fully managed, protected, and feature-rich application execution environment, simplified
development and deployment, and seamless integration with a wide variety of languages.
OVERVIEW OF THE .NET FRAMEWORK

The .NET Framework is a managed, type-safe environment for application
development and execution.
 It allocates memory for the storage of data and instructions
 Grants or denies the appropriate permissions to your application
 Initiates and manages application execution
 Manages the reallocation of memory for resources that are no longer needed.
The .NET Framework consists of two main components

 The Common Language Runtime and
 The .NET Framework class library.
COMMON LANGUAGE RUNTIME

The common language runtime can be thought of as the environment that manages
code execution. It provides core services such
 Code compilation
 Memory allocation
 Thread management, and
 Garbage collection
7
.NET FRAMEWORK CLASS LIBRARY
The .NET Framework class library provides a collection of useful and reusable types
that are designed to integrate with the common language runtime.
 Types are object-oriented and
 Fully extensible
LANGUAGES AND THE .NET FRAMEWORK

The .NET Framework is designed for cross-language compatibility. This means that
.NET components can interact with each other no matter what language they were originally
written in. This level of cross-language compatibility is possible because of the common
language run time. When a .NET application is compiled, it is converted from the language it
was written in Visual Basic .NET, C#, or any other .NET compliant language to Microsoft
Intermediate Language (MSIL or IL). This is a low-level language designed to be read and
understood by the common language run time. Because all .NET executables and DLLs exist
as intermediate language, they can freely interoperate.
The Common Language Specification defines the minimum standards that .NET
language compilers must conform to, and thus ensures that any source code compiled by a
.NET compiler can interoperate with the .NET Framework. The Common Type System
ensures type compatibility between .NET components. Because .NET applications are
converted to IL prior to deployment and execution, all primitive data types are represented as
.NET types. Thus, a Visual Basic Integer and a C# int are both represented in IL code as a
System.Int32. Because both languages use a common and interconvertable type system, it is
possible to transfer data between components and avoid time-consuming conversions or hard-
to-find errors.
THE STRUCTURE OF A .NET APPLICATION

The primary unit of a .NET application is the assembly. An assembly is a self-
describing collection of code, resources, and metadata. The assembly manifest contains
information about what is contained within the assembly. The assembly manifest provides
 Identity information, such as the name and version number of the assembly.
 A list of all types exposed by the assembly.
 A list of other assemblies required by the assembly.
8
Each assembly has one and only one assembly manifest, and it contains all the
description information for the assembly. The assembly manifest can be contained in its own
separate file, or it can be contained within one of the assembly's modules.
COMPILATION AND EXECUTION OF A .NET APPLICATION

When you compile a .NET application, it is not compiled to binary machine code;
rather, it is converted to IL, which is a low-level set of instructions understood by the
common language run time. This is the form that your deployed application takes—one or
more assemblies consisting of executable files and DLL files in IL form. At least one of these
assemblies will contain an executable file that has been designated as the entry point for the
application.
When execution of your program begins,

1. The first assembly is loaded into memory.
2. If the application passes the system's security policy, the common language run time
executes the code.
3. It creates a process for the application to run in and begins application execution.
4. When execution starts, the first bit of code that needs to be executed is loaded into
memory and compiled into native binary code from IL by the common language run
time's Just-In-Time (JIT) compiler.
9
Some of the services provided by the Execution Support are
 Automatic Memory Management
 Security
 Interoperability with Unmanaged Code
 Cross – Language Debugging Support
 Enhanced Deployment and Versioning Support
COMPONENTS OF CLR
VISUAL BASIC TO VISUAL BASIC.NET

There are significant changes to the language:
 A new optional Error handling structure
 Namespaces
 True Inheritance
 Free threading, and many others.
.NET also provides many other features, such as garbage collection for freeing up
resources, true inheritance for the first time, debugging that works across languages and
against running applications, and the ability to create Windows services and console
applications.
10
COMMON TYPE SYSTEM
The Common Type System specifies the types supported by the CLR. The types
specified by the CLR include
 Classes — the definition of what will become an object; includes properties, methods,
and events
 Interfaces — the definition of the functionality a class can implement, but does not
contain any implementation code
 Value Types — User-defined data types that are passed by value
The type system sets out the rules that language compilers must follow to produce
code that is cross-language compatible. By following the type system, vendors can produce
code that is guaranteed to work with code from other languages and other compilers because
all languages are consistent in their use of types.
INTEGRATED DEVELOPMENT ENVIRONMENT

Visual Studio .NET provides a single integrated development environment (IDE) that
helps developers build solutions faster using key productivity features accessible by any
.NET language. The IDE is a completely customizable cockpit that enables the highest
performance for developers. It provides unified access to the designers, editors, and tools of
Visual Studio from any .NET language.
In this system, the concept of ADO.NET will have different requirements for working
with data. In some cases, the user might simply want to display data on a form. In other cases,
the user might need to device a way to share information with another company. The user
might never need to know some of the details of data handling — for example, user might
never need to directly edit an XML file containing data — but it is very useful to understand
the data architecture in ADO.NET.
In traditional client/server applications, components establish a connection to a

database and keep it open while the application is running. Open database connections take
up valuable system resources. In most cases, databases can maintain only a small number of
concurrent connections. The overhead of maintaining these connections detracts from overall
application performance.
11
Similarly, applications that require an open database connections are extremely
difficult to scale up. An application that does not scale up well might perform acceptably with
four users but will likely not to do so with hundreds.
A model based on always-connected data can make it difficult and impractical to

exchange data across application and organizational boundaries using a connected
architecture. If two components need to share the same data, both have to be connected, and a
way must be devised for the components to pass data back and forth.
For all these reasons, data access with ADO.NET is designed around an architecture
that uses connections sparingly. Applications are connected to the database only long enough
to fetch or update the data. Because the database is not holding on to connections that are
largely idle, it can service many more users of languages.
ADO.NET
ActiveX ® Data Objects.NET (ADO.NET), formerly known as ADO+, is a new set of
classes that expose the data access services of the .NET Framework. ADO.NET is a natural
evolution of ADO and is built around N-Tier application development. ADO.NET has
been created with XML at its core. The ADO.NET object model is composed of two central
components: the connected layer, which consists of the classes that comprise the .NET Data
Provider, and the disconnected layer, which is rooted in the Dataset.
.NET Data Providers includes the following components: the Connection object, the
Command object, the Data Reader, and the Data Adapter. The first two should be familiar
to existing ADO programmers; they are used to open a connection to a data source and
execute a command against it. The Data Reader loosely corresponds to a forward-only, read-
only
ADO.NET is essentially a collection of classes that expose methods and attributes

used to manage communications between an application and a data store. An integral part of
the .NET Framework, ADO.NET simplifies integration of data sharing in distributed
VB.NET applications.ADO.NET is an expansion of ADO with some of the key concepts
retained. ADO.NET has greatly extended to provide access to structured data from diverse
sources, which are all accommodated in a consistent, standardized programming model.
12
ADO.NET can be used in any consumer application that needs to connect to, and
communicate with, data sources such as Microsoft SQL Server, as well as data sources
exposed via OLE DB and XML.
The ADO.NET object model is made up

 Data View
 Data Set
 Data Provider
DATA VIEW
The Data View speaks to the Dataset and is a special class designed for objects to
bind to and can provide customized views of the Data Set. It provides methods and properties
that enable objects such as a Data Grid to bind to a Dataset and contains properties such as
Allow Edit and Count that allow the object to work with the data in meaningful ways. A Data
View is only used in conjunction with a Dataset and never with a Data Reader.
DATA SET
The Dataset is the core component of the disconnected architecture of ADO.NET that
caches data locally on the client. The Dataset is explicitly designed for data access
independent of any data source. As a result it can be used with multiple and differing data
sources, XML data, or used to manage data local to the application. The Dataset contains a
collection of one or more Data Table objects made up of rows and columns of data, as well as
primary key, foreign key, constraint and relation information about the data in the Data Table
objects.
DATA PROVIDER
The Data Provider connects to the database on behalf of ADO.NET. It encapsulates all
connections to a database. The Data Provider containing some objects in it:
 Connection
 Command
 DataAdaptor
 DataReaderS
13
CONNECTIONS
Connections are part of a Data Provider and the Connection object provides
connectivity to a data source. Connections can be opened in two ways:
1. Explicitly by calling the Open method on the connection;
2. Implicitly when using a DataAdapter.
CLOSING THE CONNECTION

We must always close the Connection when we are finished using it. This can be done
using either the Close or Dispose methods of the Connection object. Connections are not
implicitly released when the Connection object falls out of scope or is reclaimed by garbage
collection.
COMMANDS
The Command object enables access to database commands to return data, modify
data, run stored procedures, and send or retrieve parameter information. Commands contain
information that is submitted to a database as a query, and, like connections, are represented
by the provider-specific classes SqlCommand and OleDbCommand. Functionally, once the
Connections are established and the Commands are executed the results are in the form of
streams. These resultant streams can be accessed either by DataReader object, or passed into
a DataSet object via a DataAdapter. The SqlCommand class provides four different methods
to execute a command. They are: ExecuteReader, ExecuteNonQuery, ExecuteScalar and
ExecuteXmlReader.
DATA ADAPTERS
The DataAdapter provides a set of methods and properties to retrieve and save data
between a DataSet and its source data store. It does the actual work of putting returned data
from a database into a DataSet. It also manages reconciling how data should be updated
against a database. Connections and Commands whose properties are set early on in code are
often passed into DataAdapters for use when their action methods are invoked. The
DataAdapter object encapsulates a set of data commands and a database connection, which
are used to fill the DataSet and update the data source.
14
DATA READERS
When dealing with large read only data, e.g. reading 5,000 rows of data, the .NET
framework includes the DataReader object, which is a read-only, forward-only stream
returned from the database record set. It is a highly optimized, no buffering, and fire hose-
style interface for getting the results of a query executed against the data source. The Data
Adapter provides the bridge between the .NET Data Providers and the Dataset. The Dataset
is a local buffer of tables or a collection of disconnected record sets.
BACK END: MS-ACCESS

A database program for windows, available separately or included in the Microsoft
office suite. Access is programmable using visual basic for applications (VBA). Access can
read Paradox, dBase and Btrieve files, and using ODBC, Microsoft SQL Server, SYBASE
SQL Server and Oracle data.
Microsoft Access (current full name Microsoft Office Access) is a relational database
management system from Microsoft, packaged with Microsoft Office Professional which
combines the relational Microsoft Jet Database Engine with a graphical user interface.
Microsoft Access can use data stored in Access/Jet, Microsoft SQL Server, Oracle, or
any ODBC-complaint 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.
Microsoft Access was also the name of a communications program from Microsoft,
meant to compete with ProComm and other programs. This Microsoft Access proved a
failure and was dropped. Years later Microsoft reused the name for its database software.
FEATURES
One of the benefits of Access from a programmers perspective is its relative
compatibility with SQL – queries may be viewed and edited as SQL statements, and SQL
statements can be used directly in Macros and VBA Modules to manipulate Access tables.
Users may mix and use both VBA and “Macros” for programming forms and logic and offers
object-oriented possibilities.
15
MSDE (Microsoft SQL Server Desktop Engine) 2000, a mini-version of MS SQL
Server 2000, is included with the developer edition of Office XP and may be used with
Access as an alternative to the Jet Database Engine.
Unlike a complete RDBMS, the Jet Engine lacks database triggers and stored
procedures. Starting in MS-Access 2000(Jet 4.0), there is a syntax that allows creating
queries with parameters, in a way that looks like creating stored procedures, but these
procedures are limited to one statement per procedure. Microsoft Access does allow forms to
contain code that is trigged as changes are made to the underlying table (as long as the
modifications are done only with that form), and it is common to use pass-through queries
and other techniques in Access to run stored procedures in RDBMS that support these.
In ADP files (supported in MS Access 2000 and later), the database-related features
are entirely different, because this type of file connects to a MSDE or Microsoft SQL Server,
instead of using the Jet Engine. Thus, it supports the creation of nearly all objects in the
underlying server (tables with constraints and triggers, views, stored procedures and UDF-s).
However, only forms, reports, macros and modules are stored in the ADP file (the other
objects are stored in the back-end database).
OPERATING SYSTEM : WINDOWS XP

Microsoft Windows XP is software program that makes IBM PC systems easy to use,
it does this by simplifying the computers. User Interface is a buzzword that refers to the way
we give commands to the computer and the way in which we interact with it.
With windows the user can run programs, enter and move data around and performs
DOS tasks by simply using the mouse to point objects on the screen. Windows owes its name
to the fact it runs each program or each document in its own separate window. Further, the
user can have any number of Windows on the screen at time, each containing its own
program. It is possible to switch between windows easily.
Another advanced feature in windows is that it has clipboard facility. It lets the user to
copy data of different document types, make it easy to cut and paste information from one
application to another.
16
FEATURES OF WINDOWS XP
Microsoft windows XP is more compatible and more powerful than any workstation
that you have used before.
- Easier to use
- Easier to manage
- More compatible and Powerful
EASIER TO USE
Windows XP makes it easier to:
- Work with files
- Find information
- Personalize your computer environment
- Work on the web Work remotely
WINDOWS XP ALSO PROVIDES

- Improved Driver support
- Increased support for new generation hardware and multimedia
technologies
- Integration of new Symbols
MORE POWERFUL
Windows XP provides
- Industrial Strength reliability
- The highest level of security
- Powerful performance
DISTRIBUTED PROCESSING
Windows XP allows the connectivity with variety of host environment through its
support of multiple transport protocol an client server facilities.
17
3. SYSTEM ANALYSIS
A single-user application which is typically found on a desktop computer there is no

need for any access control - the user has access to every function within the application.
However, in a multi-user application which is deployed over numerous devices which are
linked together in a network it is more than likely that not all functionality will be available to
all users.
In this situation a method is required to allocate a suitable person for the correct job at
correct time and maintain the authorized process at a place whereby functions within the
application can only be accessed by persons to whom permission has been granted.
3.1. EXISTING SYSTEM

In the existing system all the system is running on Foxpro, without any logical
integration. The system study gives the structure and functioning of the system study can be
done on existing system. The study will an idea of the user requirements, it gives the clear
idea about the drawback.
DRAWBACKS
 It is very difficult to keep track of the transactions accurately and
efficiently.
 It is unable for the existing system to generate variety of reports.
 Security and protection of the confidential data is not efficient.
 Much user performance leads to errors.
 Dynamic queries are not possible
 It is not user friendly
 Lack of speed, interactive-ness and flexibility.
 Possible violation of referential integrity.
18
3.2. PROPOSED SYSTEM
The proposed system was aimed to overcome the major drawbacks of the existing
(i.e.) FoxPro. To eradicate the problems faced there is a need to switch on to the system. The
proposed system is based upon online transactions.
The system that we proposed uses VB.NET 2005 as the front end and MS-Access as
the power database. The front end Visual Basic.NET tools providing graphical user interface
with oracle as a power database system.
Advantages of the Proposed System:

 Speed up the processing
 Handling large volume of data compared to the available
manpower.
 Improve accuracy.
 Prepare report, forms easily.
 Setting relations between tables are very easy.
3.3. FEASIBILITY STUDY

Feasibility is the determination of whether or not a project is worth doing. the
processes is followed in making this determination is called a feasibility study is the test of
system proposal according to its work ability impact on the organization ability to meet users
needs, and effective use of resources the result feasibility is a formal proposal.
This simply reports – a formal document detailing the nature and scope of the
proposed solution.
The main objective of the feasibility study is test the technical, social and economic
feasibility of developing a computer system. this is done by investigation the existing system
in the area under investigation and generating ideas about a new system.
On studying the feasibility of the system three major consideration are deal with, to
find whether the automation of the system feasible.
19
4. SYSTEM DESIGN
The design of the system is essentially a blue print or a plan for a solution for the
system. At the first level the focus is made which modules are needed for the system and how
modules should be interconnected. This is called system design.
In the second level, the internal design of the modules and how the specification of
the module can be satisfied is decide upon. Thus design level is called detailed design. Since
the detailed design delineates the major characteristics of the system and also its efficiency. A
Design methodology is a systematic approach to create a design by application of a set of
techniques and guidelines.
ARCHITECTURAL DESIGN
20
4.1. DATAFLOW DIAGRAM
Data Flow Diagram (DFD) is a directed graph in which the nodes specify processing
activities and the arcs specify data items transmitted between processing nodes.
Data Flow Diagrams are excellent mechanisms for communicating with customers
during analysis. Data Flow Diagram are quit valuable for establishing naming conventions
and names of system components such as subsystems, files and data link.
DFD is used to represent the functional relationship of input, process and output
values presented by system. DFD shows how information moves through the system and how
it is modified by series of transformation that are applied as data moves from input to output.
DFD may be used to represent a system at any level of abstraction.
A DFD also called context diagram represents entire system as a single module with
input to output data indicated by incoming and outgoing allows respectively. Additional
processes and information flow paths are represent as a DFD is partitioned to reveal more
detail represent the system with major modules, data flows and data stores, the other levels
will show each module in the top level DFD in a more detailed fashion.
21
22
23
24
4.2. INPUT DESIGN
Identification of the correct input and output for a system from the major parts of a
system analysis. During the System analysis the provider’s and seeker’s needs, the data
stores, the key system elements are identified. Based on this identification the input to be
provided to the system and the outputs that are to be generated and their formats are decided.
The Input Design is the kind that ties the information system into the World of its users.
Output refers to the results that are generated by the system. The design decision for handling
input specified how data are accepted for computer processing.
OBJECTIVES OF INPUT DESIGN

The quality of system input determines the quality of system output. Input
specification describes the manner in which data enter the system for processing. Input
design features can ensure the reliability of the system and produce results from accurate
data, or they can result in the production of erroneous information. The input design also
determines whether the user can interact efficiently with the system.
Four Objectives guiding the design of the input focus on

 Effectiveness
 Accuracy
 Easy to use
 Consistency
 Effectiveness
This means that input forms and screens serve specific purposes.
 Accuracy
Refers to design that assures proper completion.
 Easy to Use
Means that forms and screens should are straight forward and require no extra
time to understand.
 Consistency
Means that forms and screens should group data of similar nature together.
25
4.3. OUTPUT DESIGN
One of the most important features of an information system for users is the output it
produces. Output is the information delivered to the users through the information system.
Without quality output, the entire system may appear to the unnecessary that users will avoid
using it. Users generally merit the system solely by its output. Therefore an effective output
design is an important feature of design specifications.
OBJECTIVE OF THE OUTPUT DESIGN

Since useful output is essential to gaining use and acceptance of the system, the
system analyst should try and follow the following objectives, which are useful for designing
acceptable outputs.
 Design the output to serve the intended purpose.
 Design the output to fit the users.
 Deliver the appropriate quantity of output.
26
4.4. DATABASE DESIGN
Data Source Name: libproj
Table Name: applicant
Field Name Data Type Description
Name Char(15) Name of the applicant
F name char(15) Father’s Name
Dob Date/Time Date of Birth
Sex Char(8) Gender
Address Char(30) Address
Phno Number(10) Phone Number
Occup Char(15) Occupation
Samount Number(5) Subscription Amount
Ddno Number(5) Demand Draft No
Regdate Date/time Registration Date
Table Name: book

Bcode Number(5) Book Code
Sdate Date/Time Supply Date
Title Char(25) Book Title
Author Char(15) Author
Subject Char(10) Subject
Public Char(15) Publication
Price Number(4) Price
Pageno Number(3) Page No
Pyear Number(4) Publication Year
Lang Char(10) Language
Status Char(3) Status
Libname Char(30) Library Name
Table Name: branch

Libno Number(4) Library No
27
Name Char(15) Library Name
City Char(10) City
Phno Number(10) Phone Number
Librarian Char(20) Librarian
Books Number(5) Books
Comers Number(4) Commers
Members Number(5) Members
Employs Number(3) Employees
Table Name: comment

Name Char(15) Name
Cdate Date/Time Comment Date
Ctime Date/Time Comment Time
Com Char(15) Command
Table Name: employ

Empid Number(4) Employee ID
Name Char(15) Employee Name
Addr Char(30) Address
Phno Number(10) Phone No
Desig Char(15) Designation
Doj Date/Time Date of Joining
Libname Char(30) Library Name
Libcity Char(15) Library City
28
Table Name: entry
User Char(15) User Name
Pass Char(20) Password
Table Name:fine
Name Char(15) Name
Ledate Date/time Lending Date
Lastdate Date/time Last Date
Bname Char(25) Book Name
Table Name:journal
No Number(4) Journal No
Name Char(10) Journal Name
Issue Date/time Issue
Seasion Number(4) Seasion
Nobook Number(5) NoBook
Country Char(15) Country
Rate Number(5) Amount
Table Name:member
No Number(5) Member ID
Name Char(15) Member Name
Fname Char(15) Father’s Name
Sex Char(8) Gender
29
Phno Number(10) Phone No
Occup Char(15) Occupation
Samount Number(5) Subscription Amount
Ddno Number(5) Demand Draft No
Nocard Number(5) No. of. Cards
Wdraw Char(15) Withdrawal
Vdate Date/Time Withdrawal Date
Table Name: memcancel

Id no Number(5) ID No
Name Char(15) Name
Reason Char(20) Reason
Table Name: paper

No Number(4) Paper No
Name Char(10) Paper Name
Issue Date/time Issue
Season Number(3) Season
No book Number(6) No Book
Country Char(15) Country
Rate Number(4) Amount
Table Name: reserve

B code Number(5) Book Code
B name Char(25) Book Name
R date Date/time Reserve Date
S id Number(5) Subscriber ID
30
Table Name: stock
O year Number(4) Opening year
B stock Number(5) Book Stock
B given Number(4) Book Given to
Used Number(5) Used Books
Total Number(6) Total Books
Missed Number(4) Missed books
Damage Number(4) Damage Books
Table Name: withdraw

Bname Char(25) Book Name
Memid Number(5) Member ID
Name Char(15) Member Name
Ledate Date/time Lending Date
Ladate Date/time Last Date
31
5. SYSTEM IMPLEMENTATION
Implementation includes all the activity that takes place to convert the old system to
the new. The new system “Digitized Library Management System” is a totally new, replacing
existing manual system, proper implementation is essential to provide a reliable system to
meet the organization requirements.
Implementation Procedure:
An essential view of software requirements presents the functions to be accomplished
and information to be processed with out regard to implement detail. The system is
implemented and the conversion is complete, user and analysis alike usually conduct review
of the system. The review is also important to gather information for the maintenance of the
system. The review has been proved to meet the expectations and has also improved their
working condition.
User Training:
The quality of training received by the personnel involved with the system affects the
successful implementations of the system. Thus for a successful implementation efficient
training must be given to the system operators and the user of the system. Proper training has
been given to the system operators with regard to the operation system – data entry for
providing the necessary support service and that they are able to handle all possible
operations, both routine as well as extraordinary.
Operational Documentation:
Documentation outline can be used as a model for a design specification. Each section
is comprised of numbered paragraphs that address different aspects of the design
representation. Documentation outline presents a complete design description of software the
sections of the designs specification are completed as a designer refines his representation of
the software. The modules can be increase if they will any requirements in the future in the
project.
32
6. SYSTEM TESTING
The system “Digitized Library Management System” as a whole was deployed in the
VB.NET 2010 and was tested. The system was found to be working perfect and an end user
has been asked to enter the data, and further the connected systems has been tested with the
sample.
6.1. UNIT TESTING

Unit testing different modules are tested against the specifications produced during
the design of the modules. Unit testing is essential for Verification of the code produced
during the coding phase and hence the goal is to test the internal logic of the modules. Using
the details design description as a guide, important paths are tested to uncover errors within
the boundary of the Modules.
In the project, the login details of the user are being verified by various conditions.
All the conditions are satisfied, then after the user go to visit the system project.
This testing was carried out during the programming stage itself.
 Performance Test
 Stress Test
PERFORMANCE TESTING
It determines the amount of execution time spent in various parts of the unit, program
throughput, and response time and device utilization by the program unit. To recover the
project from the slow response time, try to avoid of apply the looping statement instead of the
control statements.
STRESS TESTING
Stress Test is those test designed to intentionally break the unit. A Great deal can be
learned about the strength and limitations of a program by examining the manner in which a
programmer in which a program unit breaks.
33
6.2. SYSTEM TESTING
System Testing involves two kinds of activities: Integration Testing and Acceptance
Testing. Strategies for integrating software components into a functioning product include the
bottom-up strategy, the top-down strategy and the sandwich strategy. Acceptance Testing
involves planning and execution of the functional tests, performance tests and the stress tests
to verify that the implemented system satisfies its requirements.
The System testing does not test the module wise, but the integration of each module
in the systems. System testing helps to find in discrepancies between the original objectives
of the system.
6.3. ACCEPTANCE TESTING

Acceptance testing is done with live data provided by the administrator to ensure that
the software works satisfactorily. Acceptance testing focuses on the external behavior of the
system. Giving inputs from actual data tested the system and the results were found to be
satisfactory.
The inputs are well verified by different conditions at different stages. Suppose the
user may give wrong username or password, then the system will inform the wrong entry.
The ID will be automatically generated for to avoid the redundancy and duplication.
6.4. INTEGRATION TESTING

System has been partitioned into sub Modules. The integration of them must be
subjected to a strong checking, so that data gets prevented from loss across the interface.
Thus Integration Testing system is subjected to integration.
Here book is the base of the project. The customer information, lending details,
books, journal and employee roles, and the lending fine information are maintained under the
same category.
34
7. CONCLUSION
The project “Digitized Library Management System” is user-friendly and easily

navigable by the user without any help because all the forms are explained with neat lines and
statements. This system has been developed for the present requirements such as and it works
satisfactorily under all circumstances that may arise in the real environment. It caters to need
of organizations effectively.
This system has been developed for the present requirement and it works satisfactorily
under all circumstances that may arise in the real environment. It caters to need of
organizations effectively.
The programming convention followed ensures future updating and maintenance.

Future enhancement capabilities can be carried out without having to perform too many
environment and correction of software bugs. Since documentation helps further
development and maintenance, it has been given much attention.
Reports generated with live data have proved to be information and also helpful in
making important decisions. This newly development system consumes less processing time
and high productivity. Since screens are user friendly and user get familiarized with use it.
The system is designed to be highly flexible so that any future modifications and requirement
can be easily incorporated without much design complications.
35
8. FUTURE ENHANCEMENT
As for other future developments, the following can be done:

 The Administrator of the project can be given more functionality, like looking at a
specific computer system, the books that have to be reordered, etc.
 Multiple tracking and performance settings can be allowed.
 A console for the data centre may be made available to allow the personnel to
monitor on the sites which were cleared for hosting during a particular period.
 Moreover, it is just a beginning; further the system may be utilized in various
other types of auditing operation viz. Network auditing or similar
process/workflow based applications...
36
9. BIBLIOGRAPHY
BOOK REFERENCE
o Essential .NET, James S.Miller, Tata McGraw Hill Publications, 2002 Second
Edition.
o Visual Basic.NET Programming, Matt J.Crouch, Neway Publicatons Private Limited,

Third Edition, 2003.
o Programming in the .NET Environment, Damien Watking, Mark Hammond, Brand

Abrams, APress S Publications, 2002.
o Software Engineering Concepts, Richard E.Fairly, Tata McGraw-Hill Education

Private Limited,20s11.
WEBSITE REFERENCE
http://code.msdn.microsoft.com/GotDotNet.aspx
http://www.devarticles.com/c/b/MSACCESS/
http://www.vbdotnetheaven.com/
37
10. APPENDIX
(A) SCREEN LAYOUTS
38
39
40
41
42
43
44
45
46
47
(B) SAMPLE SOURCE CODE
Public Class Form13

Dim con As New OleDb.OleDbConnection
Dim cmd As New OleDb.OleDbCommand
Dim dr As OleDb.OleDbDataReader
Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs)

Handles Button1.Click
Dim empid, fn, ln, s, q, bd, hd, hp, ad, em, n, sn, d
empid = Val(TextBox1.Text)
fn = TextBox2.Text
ln = TextBox3.Text
s = ComboBox1.Text
q = TextBox4.Text
bd = TextBox5.Text
hd = TextBox6.Text
hp = Val(TextBox8.Text)
ad = TextBox9.Text
em = TextBox10.Text
n = TextBox11.Text
sn = TextBox12.Text
d = TextBox13.Text
con = New OleDb.OleDbConnection("provider=sqloledb.1.0;user id='sa'
password='sa';initial catalog=; data source=;")
con.Open()
cmd = New OleDb.OleDbCommand("insert into t values( " & empid & " ,' " & fn & " ', '
" & ln & " ' ,' " & s & " ',' " & q & " ' , #" & bd & "#, # " & hd & " # ," & hp & ",' " & ad & "
',' " & em & " ',' " & n & " ' , ' " & sn & " ', ' " & d & " ')", con)
cmd.ExecuteNonQuery()
MsgBox("rec added")
con.Close()
End Sub
48
Dim x
x = Val(TextBox1.Text)

con.Open()
cmd = New OleDb.OleDbCommand("select * from t where empid=" & x, con)
dr = cmd.ExecuteReader()
If (dr.HasRows = 0) Then
MsgBox("no records", MsgBoxStyle.Information)
Else
Do While dr.Read
Dim i As New ListViewItem
i.Text = dr(0).ToString()
i.SubItems.Add(dr(1).ToString())
ListView1.Items.Add(i).ToString()
Loop
End If
con.Close()
End Sub
49
Dim x
x = Val(TextBox1.Text)
con.Open()
cmd = New OleDb.OleDbCommand("select * from t where empid=" & x, con)
MsgBox("no records", MsgBoxStyle.Information)
Else
Do While dr.Read
TextBox2.Text = dr(1).ToString()
ComboBox1.Text = dr(3).ToString()
Loop
End If
con.Close()
End Sub

50
con.Open()
cmd = New OleDb.OleDbCommand("select distinct(empid) from t", con)
MsgBox("no rec found", MsgBoxStyle.Information)
Else
ListBox1.BeginUpdate()
Do While dr.Read
ListBox1.Items.Add(dr(0).ToString())
Loop
ListBox1.EndUpdate()
End If
con.Close()
End Sub
Private Sub ListBox1_SelectedIndexChanged(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles ListBox1.SelectedIndexChanged
Dim x
x = Val(ListBox1.SelectedItem)
con.Open()
cmd = New OleDb.OleDbCommand("select * from t where empid= " & x & " ", con)
MsgBox("no rec found", MsgBoxStyle.Information)
Else
Do While dr.Read
Dim i As New ListViewItem
i.Text = dr(0).ToString()
51
ListView1.Items.Add(i).ToString()
Loop
End If
con.Close()
End Sub
Private Sub Form13_Load(ByVal sender As System.Object, ByVal e As System.EventArgs)

Handles MyBase.Load
Dim x
con.Open()
cmd = New OleDb.OleDbCommand("select max(empid) from t", con)
x = cmd.ExecuteScalar
TextBox1.Text = Val(x) + 1
con.Close()
End Sub
Public Class cost
Dim con As New OleDb.OleDbConnection
Dim cmd As New OleDb.OleDbCommand
Dim dr As OleDb.OleDbDataReader
Dim x
Private Sub Cost_Estimate_Load(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles MyBase.Load
52
con.Open()
cmd = New OleDb.OleDbCommand("select * from pro1", con)
ComboBox1.BeginUpdate()
Do While dr.Read
ComboBox1.Items.Add(dr(0))
Loop
ComboBox1.EndUpdate()
con.Close()
End Sub
Private Sub TextBox2_LostFocus(ByVal sender As Object, ByVal e As System.EventArgs)

Handles TextBox2.LostFocus
TextBox1.Text = Val(TextBox2.Text) + Val(TextBox3.Text)
TextBox4.Text = TextBox1.Text
TextBox5.Text = Val(TextBox4.Text) * Val(TextBox6.Text)
End Sub

TextBox1.Text = Val(TextBox2.Text) + Val(TextBox3.Text)
End Sub
Private Sub TextBox3_TextChanged(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles TextBox3.TextChanged
End Sub

53
End Sub

End Sub

TextBox21.Text = Val(TextBox7.Text) * (Val(TextBox12.Text) *
Val(TextBox15.Text)) * Val(TextBox18.Text)
End Sub

End Sub

End Sub

54
End Sub
End Sub

End Sub

Dim a, b, c, d, f, g
a = ComboBox1.Text
b = CSng(TextBox1.Text)
c = CSng(TextBox5.Text)
d = CSng(TextBox21.Text)
f = CSng(TextBox20.Text)
g = CSng(TextBox19.Text)
con.Open()
cmd = New OleDb.OleDbCommand("insert into Cost values('" & a & "','" & b & "','" &
c & "','" & d & "','" & f & "','" & g & "')", con)
cmd.ExecuteNonQuery()
MsgBox("Cost Entered Successfully", MsgBoxStyle.Information, "Workflow
Simulation")
con.Close()
End Sub
End Class
55

Lib Main

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Lib Main

Uploaded by

Copyright:

Available Formats

SYNOPSIS

1.1. PROJECT OVERVIEW

We have a well-documented quality system, which helps us to monitor measure and

2.1. HARDWARE SPECIFICATION

2.2. SOFTWARE SPECIFICATION

2.3. SOFTWARE OVERVIEW

While providing the traditional ease-of-use of Visual Basic development, Visual

OVERVIEW OF THE .NET FRAMEWORK

The .NET Framework consists of two main components

COMMON LANGUAGE RUNTIME

LANGUAGES AND THE .NET FRAMEWORK

THE STRUCTURE OF A .NET APPLICATION

COMPILATION AND EXECUTION OF A .NET APPLICATION

When execution of your program begins,

VISUAL BASIC TO VISUAL BASIC.NET

INTEGRATED DEVELOPMENT ENVIRONMENT

In traditional client/server applications, components establish a connection to a

A model based on always-connected data can make it difficult and impractical to

ADO.NET is essentially a collection of classes that expose methods and attributes

The ADO.NET object model is made up

CLOSING THE CONNECTION

BACK END: MS-ACCESS

OPERATING SYSTEM : WINDOWS XP

WINDOWS XP ALSO PROVIDES

A single-user application which is typically found on a desktop computer there is no

3.1. EXISTING SYSTEM

Advantages of the Proposed System:

3.3. FEASIBILITY STUDY

OBJECTIVES OF INPUT DESIGN

Four Objectives guiding the design of the input focus on

OBJECTIVE OF THE OUTPUT DESIGN

Table Name: book

Table Name: branch

Table Name: comment

Table Name: employ

Table Name: memcancel

Table Name: paper

Table Name: reserve

Table Name: withdraw

6.1. UNIT TESTING

6.3. ACCEPTANCE TESTING

6.4. INTEGRATION TESTING

The project “Digitized Library Management System” is user-friendly and easily

The programming convention followed ensures future updating and maintenance.

As for other future developments, the following can be done:

o Visual Basic.NET Programming, Matt J.Crouch, Neway Publicatons Private Limited,

o Programming in the .NET Environment, Damien Watking, Mark Hammond, Brand

o Software Engineering Concepts, Richard E.Fairly, Tata McGraw-Hill Education

(A) SCREEN LAYOUTS

Public Class Form13

Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs)

con = New OleDb.OleDbConnection("provider=sqloledb.1.0;user id='sa'

Private Sub Button6_Click(ByVal sender As System.Object, ByVal e As System.EventArgs)

Private Sub ListBox1_SelectedIndexChanged(ByVal sender As System.Object, ByVal e As

Private Sub Form13_Load(ByVal sender As System.Object, ByVal e As System.EventArgs)

Private Sub Cost_Estimate_Load(ByVal sender As System.Object, ByVal e As

Private Sub TextBox2_LostFocus(ByVal sender As Object, ByVal e As System.EventArgs)

Private Sub TextBox3_LostFocus(ByVal sender As Object, ByVal e As System.EventArgs)

Private Sub TextBox4_LostFocus(ByVal sender As Object, ByVal e As System.EventArgs)

Private Sub TextBox6_LostFocus(ByVal sender As Object, ByVal e As System.EventArgs)

Private Sub TextBox12_LostFocus(ByVal sender As Object, ByVal e As System.EventArgs)

Private Sub TextBox18_LostFocus(ByVal sender As Object, ByVal e As System.EventArgs)

Private Sub TextBox11_LostFocus(ByVal sender As Object, ByVal e As System.EventArgs)