Download as pdf or txt
Download as pdf or txt
You are on page 1of 36

NAME : SUMIT KISHOR

ROLL NO:-1308020300
M.Sc. IT
INTRODUCTION
 A library management system, also known as
an automated library system is software that
has been developed to handle basic
housekeeping functions of a library.
 It’s a well organized software solution for a
library.
 It help to provide information on any book
present in library to the user as well as staff
member.
 It keeps a track of book issued, returned and
added to library.
Specific Object of The
Library Management
System
 It provides "better and efficient" service to
members. It’s a well organized software solution
for a library.
 Reduce the workload of employee.
 Faster retrieval of information about the desired
book. It keeps a
 Provide facility for proper monitoring reduces
paper work and provide data security.
 Less Error, More Storage Capacity.
Problem of Statement:

In our existing system all the


transaction of books are done
manually, So taking more time for a
transaction like borrowing a book or
returning a book and also for
searching of members and books.
Another major disadvantage is that to
preparing the list of books borrowed
and the available books in the library
will take more time, currently it is
doing as a one day process for
verifying all records.
So after conducting the feasibility
study we decided to make the manual
Library Management System to be
computerized. Proposed system is an
automated Library Management
System. Through our software user
can add members, add books, search
members, search books, update
information, edit information, borrow
and return books in quick time.
SYSTEM CONFIGURATION

1.HARDWARE CONFUGRATION:-
 GENUINE INTEL : PENTIUM IV 3.0 GHz
 MEMORY : 256 MB RAM
 HARD DISK : 40GB

2.SOFTWARE CONFUGRATION:-
 INTERFACE : TURBO C++

 PLAT FORM : MICROSOFT WINDOWS


Functional Requirement:

 1. Accession number, roll number and


teacher identification must all be unique
as they form the primary keys of the
respective tables.
 2. All new books must be entered in the
accession table first, to avoid problems
later.
 3. A book must not be deleted from
student profile unless and until she pays
the appropriate fine or the same book.
 4. While inserting values in the database,
only valid values must be entered.
Date Requirement:

 1. The Library Management System shall be


required to maintain information about its
users and books.
 2. It shall store databases for students,
teachers and books.
 3. The student database stores information
about a student’s roll no, name, address, course
and year.
 4. The book database stores information about a
book title, author, publisher, cost, bill number,
year of publishing and pages.
 5. The teacher database stores information
about a teacher ’s id, name, department, and
designation, address and telephone number.
Methodology of the Study
Data Source
 1. Employees of the SMU Library : Since the
librarian officers are the main beneficiaries of
this Project they are one of our data source.
Internet:
 2. Students : this are another beneficiaries of
the project because they are main users of the
system and they know all needed requirements
and they well know the problems behind this.
 3. We used internet for getting tools we will be
using to develop this system.
Data Collection Methods
 The data collection methods used in this
project is
 Interviews - Interviewing the
stakeholders such as librarians
 Questioner - by asking open questions to
the librarian
 Observing Users at library - Watching
users performing their study at library.
SCOPE OF PROJECT:
 To make the existing system more efficient.

 To provide a user friendly environment where user


can be serviced better.

 Make functioning of library faster.

 Provide a system where the library staff can catch


defaulters and not let them escape.

 To minimize the loss done to books.


Methodology to be used for the
project
SDLC – WATERFALL MODEL:
 The Waterfall Model was first Process Model to
be introduced. It is also referred to as a linear
sequential life cycle model. It is very simple to
understand and use. In a waterfall model, each
Phase must be completed before the next phase
can begin and there is no overlapping in the
phases. Waterfall model is the earliest SDLC
approach that was used for software
development.
 The waterfall Model illustrates the software
development process in a linear sequential
flow; hence it is also referred to as a linear-
sequential life cycle model. This means that
any phase in the development process begins
only if the previous phase is complete. In
waterfall model phases do not overlap.
REQUIREMENTS:
 The Library Management System shall be
required to maintain information about its users
and books.

 It shall store databases for students, teachers and


books.

 The student database stores information about a


student’s roll no, name, address, course and year.
 The book database stores information about a
book title, author, publisher, cost, bill number,
year of publishing and pages.

 The teacher database stores information about


a teacher’s id, name, department, designation,
address and telephone number.
PROJECT AIM
 To eliminate the paper work in library.

 To record every transaction in computerized system so


that problem such as record file missing won’t be
happen.

 To design a user friendly graphical user interface


which suit the user.

 To save the cost and time.


Services Provided to the
User
The Library Management System automates the basic
library functions to aid in the day-to-day operations
of a library. It supports functions such as issue, return,
the very basic functions of searching for a particular book, etc.

It also maintains data about books about books, teachers,


students records that are required during various library
operations. The software aims to make the system user
friendly and efficient.
Add New Book
Add New Member
Issue Book
Return Book
List of Books
List of Members
Update/Delete Member
Update/Delete Book
Search For a Book
Check In Book
Check Out Book
 A data flow diagram(DFD) is graphical
representation of the “flow” of data through an
information system.

 A DFD shows what kinds of information will be


input to and output from the system.

 One of the most widely used system analysis


process models is the data flow diagram.
MODULES
 ADD BOOK
 ADD MEMBER
 ISSUE BOOKS/RETURN BOOK
 LIST OF BOOK
 LIST OF MEMBER
 EDIT
SCREEN SHOTS
 To make the existing system more efficient.

 To provide a user friendly environment where user


can be serviced better.

 Make functioning of library faster.

 Provide a system where the library staff can catch


defaulters and not let them escape.

 To minimize the loss done to books.


CONCLUSION
The system has been developed using C++ , the system was able
to process and update the database with more ease. It helped
in developing a total integrated system.

Thus the project “LIBRARY MANAGEMENT


SYSTEM” can be altered in accordance with the future
requirements of the organization.

You might also like