DESKTOP APPLICATION

FOR LIBRARY
MANAGEMENT SYSTEM

BY
1)HARSHVARDHAN R. PATIL
2)VRUSHALI V. SAWANT
3)SHRADDHA C. SURVE
INDEX
SR.NO CONTENT

1) INTRODUCTION

2) SYSTEM ANALYSIS

3) SYSTEM DESIGN

4) SYSTEM IMPLEMENTATION

5) SYSTEM TESTING

6) FUTURE SCOPE & REFERENCES

  Library management system is a project which aims in developing
a computerized system to maintain all the daily work of library.
 This project has many features which are generally available in
library management systems. It has a facility of admin login
INTRODUCTION through which the admin can monitor the whole system.
 Overall this project of ours is being developed to help the students
as well as staff of library to maintain the library in the best way
possible and also reduce the human efforts.
 PROJECT AIMS AND OBJECTIVES
 The project aims and objectives that will be achieved after
completion of this project are discussed in this subchapter. The aims
and objectives are as follows:
Admin panel for generate new membership ID.
OBJECTIVE Admin can keep record of member.
Column for librarian for providing new books.
Member can issue book and find returning dates.
 SOFTWARE REQUIREMENT SPECIFICATION
 It reduces the risk of paper work such as file lost, file damaged and
time consuming. It can help user to manage the transaction or
record more effectively and timesaving.
 PROBLEM STATEMENT:
The problem occurred before having computerized system includes:
CONTINUED… I. File Lost
II. File Damaged
III. Difficult To Search Record
IV. Space Consuming
V. Cost Consuming
 SYSTEM REQUIREMENTS:
Register New Member : This feature can be performed by librarian
to register new member to create account.
Issue Library Card : This feature can be performed by librarian to
issue a new library card.
SYSTEM Search Book : This feature is found in book maintenance part.
System must be able to filter book based on keyword entered .
ANALYSIS Issue Book & Return Book : This feature allows to issue and return
books and also view reports of book issued. System must be able
to enter issue information in database.
Register New Book : This feature allows to add new books to the
library. System must be able to enter number of copies into table.
 TABLE DESIGN
VARIOUS TABLES TO MAINTAIN INFORMATION

SYSTEM  Books Table For Keeping Track Of Books.

 Members Table For Member Information.
DESIGN  Transact table to keep track of books issued.
 Fine table for keeping track on fine of books.
 Book Table For Keeping Track Of Books

Book_Id Int , Auto Generated

Title Varchar(100)
Author Varchar(100)
CONTINUED… Type_of_book Varchar(100)
Language Varchar(100)
Publication Varchar(100)
Price Int(10)
 Member Table For Member Information

Member Id Int ,Auto Generated

Full Name Varchar (100)
Member Type Varchar (100)
CONTINUED.. Date Of Birth Date
Mail Varchar(100)
Phone Varchar (100)
City Varchar (100)
Address Varchar (100)
 Fine table to keep record of fine & Transaction table to keep
track of books issued/returned

Member Id Int(Referred to Member Id in Member

table)
Total fine Int
Paid fine Int
Remaining fine Int
CONTINUED…
Member Id Int(Referred to Member Id in Member
table)

Book Id Int(Referred to Book Id in Book table)

Issue Date Date
 SOFTWARE TOOLS USED
C# .NET-
 It is an object-oriented programming language provided by
Microsoft that runs on .Net Framework.
SYSTEM  By the help of C# programming language, we can develop
different types of secured and robust applications:
IMPLEMEN-  Window applications
TATION  Web applications
 Distributed applications
 Web service applications
 Database applications etc.
 ADO .NET-
 It is a module of .Net Framework which is used to establish
connection between application and data sources. Data sources
can be such as SQL Server and XML. ADO.NET consists of classes
that can be used to connect, retrieve, insert and delete data.
CONTINUED…  All the ADO.NET classes are located into System.Data.dll and
integrated with XML classes located into System.Xml.dll.
 ADO.NET has two main components that are used for accessing
and manipulating data are the .NET Framework data provider and
the DataSet.
 Microsoft SQL Server-
 Microsoft SQL server is a fast, easy to use relational database. It is
currently the most popular open-source database. It is very
CONTINUED… commonly used in conjunction with .NET frameworks to create
powerful and dynamic server-side applications. SQL is used for
many small and big businesses.
DESKTOP
APPLICATION
FOR LIBRARY
MANAGEMENT
SYSTEM
 The aim of the system testing process was to
determine all defects in our project. The program was
subjected to a set of test inputs and various
observations were made and based on these
SYSTEM observations it will be decided whether the program
behaves as expected or not. Our Project went through
TESTING two levels of testing
 1. Unit testing
 2. integration testing
 UNIT TESTING
 Unit testing is undertaken when a module has been created and
successfully reviewed. In order to test a single module we need to
provide a complete environment i.e besides the module we would
require
 The procedures belonging to other modules that the module under
test calls
 Non local data structures that module accesses A procedure to call
CONTINUED… the functions of the module under test with appropriate parameters
Unit testing was done on each and every module that is described
under module description.
Test For the admin login module
 This form is used for log in of administrator of the system. In this we
enter the username and password if both are correct administration
page will open otherwise if any of data is wrong it will get redirected
back to the login page and again ask for username and password
 Test for registration of student-
 In this section the admin can verify student details from student
info and then only add student details to main library database it
contains add and delete buttons if user click add button data will
be added to student database and if he clicks delete button the
CONTINUED… student data will be deleted. It will generate membership id.
Test for Book Addition-
 Admin can enter details of book and can add the details to the
main book table also he can view the books requests.
  INTEGRATION TESTING
 In this type of testing we test various integration of the project
module by providing the input .The primary objective is to test the
CONTINUED… module interfaces in order to ensure that no errors are occurring
when one module invokes the other module.
 The project is designed to run on a single machine, no option to
run on a network of computers (LAN etc.).
The designing of project is not up to the level of software market,
it has a lot of scope to improve.
Only administrator can use this system, that means only one
LIMITATIONS transaction can be processed at one time that may be issue,
return or any other.
The database is not vast.
There is no option for the payment receipt of the fine submission.
 Project can be further enhanced with the facility to run project on
multiple machines (LAN) so that more than one library for the
same institution can be connected through same database and
controlled by same mechanism.
In depth details regarding every the security aspects of the project
needs to prepared and then taken steps taken or functionality
FUTURE included to preserve security.
SCOPE Enhancements can be made to provide user. We can provide user
a User Id and password with option that if one forgets his/her
password then it can be changed or retrieved.
New option like option for the payment receipt of the fine
submission can be included.
 Project is fully complete and running with every aspect of coding
and connectivity with the database.
CONCLUSION We have tried our best to present the simple interface to the user
and remove the complexity of using a manual library.
THANK YOU !