Vous êtes sur la page 1sur 34

LIBRARY MANAGEMENT SYSTEM

HARSHA HARIKUMAR (Reg.no:-320-17 994 011)


PAVITHRA MOL . J (Reg.no:-320-17 994 014)
JAISEKHAR. K. L (Reg.no:-320-17 994 012)

UNIVERSITY INSTITUTE OF TECHNOLOGY


UNIVERSITY OF KERALA
MUTHUKULAM CENTRE

PROJECT REPORT

SUBMITTED IN PARTIAL FULFILLMENT OF


THE REQUIREMENT FOR THE DEGREE OF BSc COMPUTER
SCIENCE, UNIVERSITY OF KERALA
2017-2020
LIBRARY MANAGEMENT SYSTEM

HARSHA HARIKUMAR (REG.NO- 320-17 994 011)


PAVITHRA MOL. J (REG.NO- 320-17 994 014)
JAISEKHAR . K. L (REG.NO- 320-17 994 012)

SUBMITTED IN PARTIAL FULFILMENT OF THE


REQUIREMENT FOR THE DEGREE OF BSC COMPUTER
SCIENCE, UNIVERSITY OF KERALA

UNIVERSITY INSTITUTE OF TECHNOLOGY


UNIVERSITY OF KERALA
MUTHUKULAM CENTRE
2017-2020
UNIVERSITY INSTITUTE OF TECHNOLOGY
UNIVERSITY OF KERALA
MUTHUKULAM CENTRE
2017-2020

CERTIFICATE

This is to certify that this report “LIBRARY MANAGEMENT SYSTEM” is a


bonafide record project work done by Harsha Harikumar, Pavithra Mol J and Jaisekhar KL
under our supervision and guidelines, towards partial fulfillment of the requirements for the
award of the degree of BSc Computer Science of the University of Kerala.

Miss .Aparna Padmakumar

Project Guide

Prof : Shajahan

Principal

External Examiner
DECLARATION

We hereby declare that the project entitled ”LIBRARY MANAGEMENT SYSTEM” has been
carried out by us in the partial fulfillment of the requirement of the arrangement of Bachelor
Degree in Computer Science from University Institute of Technology ,University of Kerala
,Muthukulam centre. We also declare that the findings in the report are based on the program
done and we have not copied from any other report submitted to University of Kerala.

Place:
Date:

Harsha Harikumar(Reg.no-320-17 994 011)


Pavithra Mol.J(Reg.no-320-17 994 014)
Jaisekhar K.L(Reg.no-320 17 994 012)
AKNOWLEDGEMENT

This project would not have been possible without the support of co-ordination of a number of
person of various talents and pursuits. We make of this opportunity to express our gratitude to those who
have helped us to bring out the project entitled LIBRARY MANAGEMENT SYSTEM.
First and foremost we thank God Almighty for giving us the opportunity to complete this project
successfully .We are grateful for all his blessings and his great care.
We are highly obliged to our Prof. Shajahan , principal of U.I.T muthukulam, for being the
source of inspiration and for his complete co-operation throughout our BSc Computer Science course.
We are very much greateful and indebted to our internal guide, Miss Aparna for their constant Guidance
and advise that helped us to compile, print and present this project work at the right time in the right way.
We are very much greateful and intended to our lab incharge Miss. reshma, University Institute of
Technology for her valuable guidance given to us.
We are indebted to all my friends, parents, and well-wishers for their sincere help for the completion of
this project.

Harsha Harikumar(Reg.no-320-17 994 011)


Pavithra Mol.J(Reg.no-320-17 994 014)
Jaisekhar K.L(Reg.no-320 17 994 012)
ABSTRACT

The paper titled Library Management System is Library management software for monitoring and
controlling the transactions in a library .The paper "Library Management System" is developed in php
which mainly focuses on basic operations in a library like adding new member, new books, and updating
new information, searching books and members and facility to borrow and return books. "Library
Management System" is a windows application written for 32-bit Windows operating systems, designed
to help users maintain and organize library. This software is easy to use for both beginners and advanced
users.
CONTENT
INTRODUCTION
INTRODUCTION

Library management system is all about organizing, managing the library and library-oriented tasks. It
also involves maintaining the database of entering new books and the record of books that have been
retrieved or issued, with their respective dates.
The main aim of this project is providing an easy to handle and automated library management system.
This project also provides features and interface for maintaining librarian’s records, student’s history of
issue and fines.

The owner can easily update, delete and insert data in the database with this project.

The purpose of the application is automation of library ,it provide facilities to student or member to search
for the required books and it allows the administrator or librarian to Issue & return books to students and
can create & delete membership of students. The software Library Management System has four main
modules.

 Insertion to Database Module

 User friendly input screen Extracting from Database module

 Attractive Output Screen Report Generation module

 borrowed book list & Available book list Search Facility system

 search for books and members


OBJECTIVE
Implementing library automation to prepare a database for library collections to proper organizing,
retrieving the information & providing the information to the users within the time.
• To maintain bibliographic records of all the materials in a computerized form.
• To provide online catalogue to the users to access from their desk.
• To reduce the duplication of housekeeping operations.
• To prepare various types of reports / statistic within a short time.
• To maintain the circulation section effectively.
• To provide the speed, quality services to the users.
• To maintain various types of materials (books, non-book materials, serials etc.) available in library.
• To save the time of the users
• To reduce the duplication of work.
• To provide online catalogue
• To reduce the manpower
• To share the resources through library networking.
• To Increase the operational efficiencies of library staff
• To improve the quality, speed accuracy and effectiveness of services.
• To access other networks on the web.
• To facilitate wider access to information for users.
EXISTING SYSTEM

System Analysis is a detailed study of the various operations performed by a system and their
relationships within and outside of the system. Here the key question is- what all problems exist in the
present system what must be done to solve the problem Analysis begins when a user or manager begins a
study of the program using existing system. 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.

DRAWBACKS OF EXISTING SYSTEM

 More man power.


 Time consuming.
 Consumes large volume of paper work.
 Needs manual calculations.
 No direct role for the higher officials.

To avoid all these limitations and make the working more accurately the system needs to be computerized
in a better way
PROPOSED SYSTEM
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. Our proposed system has the following advantages.
User friendly interface
 Fast access to database
 Less error
 More Storage Capacity
 Search facility
 Look and Feel Environment
 All the manual difficulties in managing the Library have been rectified by implementing
computerization
FEASIBILITY STUDY

Feasibility study is made to see if the project on completion will serve the purpose of the organization for
the amount of work, effort and the time that spend on it. Feasibility study lets the developer foresee the
future of the project and the usefulness. A feasibility study of a system proposal is according to its
workability, which is the impact on the organization, ability to meet their user needs and effective use of
resources. Thus when a new application is proposed it normally goes through a feasibility study before it
is approved for development.

The document provide the feasibility of the project that is being designed and lists various areas that were
considered very carefully during the feasibility study of this project such as Technical, Economic and
Operational feasibilities. The following are its features:

TYPES OF FEASIBILITY STUDY

 TECHNICAL FEASIBILITY

The system must be evaluated from the technical point of view first. The assessment of this feasibility
must be based on an outline design of the system requirement in the terms of input, output, programs and
procedures. Having identified an outline system, the investigation must go on to suggest the type of
equipment, required method developing the system, of running the system once it has been designed.

Technical issues raised during the investigation are:

Does the existing technology sufficient for the suggested one?

Can the system expand if developed?

The project should be developed such that the necessary functions and performance are achieved within
the constraints. The project is developed within latest technology. Through the technology may become
obsolete after some period of time, due to the fact that never version of same software supports older
versions, the system may still be used. So there are minimal constraints involved with this project. The
system has been developed using Java the project is technically feasible for development.
 ECONOMICAL FEASIBILITY

The developing system must be justified by cost and benefit. Criteria to ensure that effort is concentrated
on project, which will give best, return at the earliest. One of the factors, which affect the development of
a new system, is the cost it would require.

The following are some of the important financial questions asked during preliminary investigation:

The costs conduct a full system investigation.

The cost of the hardware and software.

The benefits in the form of reduced costs or fewer costly errors.

Since the system is developed as part of project work, there is no manual cost to spend for the proposed
system. Also all the resources are already available, it give an indication of the system is economically
possible for development.

 OPERATIONAL FEASIBILITY

Operational feasibility determines the working of the proposed system during installation.
Here the proposed works more efficiently than existing system.

 SOCIAL FEASIBILITY

The input and output screens are so user friendly such that any novice user could process this
application.
SYSTEM SPECIFICATION

HARDWARE SPECIFICATION
PROCESSOR :-
RAM :-
SPEED :-
HARD DISK DRIVE :-
MOUSE : -STANDARD MOUSE
KEYBOARD : -STANDARD KEYBOARD
MONITOR : -STANDARD MONITOR

SOFTWARE SPECIFICATION

OPERATING SYSTEM :-WINDOWS XP OR HIGHER VERSION


PROGRAMMING LANGUAGE :-PHP
DATA BASE :-MY SQL
WEB BROWSER :-GOOGLE CHROME
DATABASE DESIGN
DATABASE DESIGN

A database is an organized mechanism that has the capability of storing information through which a user
can retrieve stored information in an effective and efficient manner. The data is the purpose of any
database and must be protected.

The database design is a two level process. In the first step, user requirements are gathered together and a
database is designed which will meet these requirements as clearly as possible. This step is called
Information Level Design and it is taken independent of any individual DBMS.

In the second step, this Information level design is transferred into a design for the specific DBMS that
will be used to implement the system in question. This step is called Physical Level Design, concerned
with the characteristics of the specific DBMS that will be used. A database design runs parallel with the
system design. The organization of the data in the database is aimed to achieve the following two major
objectives.

Data Integrity

Data independence

Normalization is the process of decomposing the attributes in an application, which results in a set of
tables with very simple structure. The purpose of normalization is to make tables as simple as possible.
Normalization is carried out in this system for the following reasons.

To structure the data so that there is no repetition of data , this helps in saving.

To permit simple retrieval of data in response to query and report request.

To simplify the maintenance of the data through updates, insertions, deletions.

To reduce the need to restructure or reorganize data which new application requirements arise.
WATERFLOW MODEL

The waterfall model is a breakdown of project activities into linear sequential phases, where each
phase depends on the deliverables of the previous one and corresponds to a specialisation of tasks.
The approach is typical for certain areas of engineering design. In software development, it tends to
be among the less iterative and flexible approaches, as progress flows in largely one direction
("downwards" like a waterfall) through the phases of conception,
initiation, analysis, design, construction, testing, deployment and maintenance.

The waterfall development model originated in the manufacturing and construction industries; where
the highly structured physical environments meant that design changes became prohibitively
expensive much sooner in the development process. When first adopted for software development,
there were no recognized alternatives for knowledge-based creative work.[1]

In Royce's original waterfall model, the following phases are followed in order:

1. System and software requirements: captured in a product requirements document


2. Analysis: resulting in models, schema, and business rules
3. Design: resulting in the software architecture
4. Coding: the development, proving, and integration of software
5. Testing: the systematic discovery and debugging of defects
6. Operations: the installation, migration, support, and maintenance of complete systems

Thus the waterfall model maintains that one should move to a phase only when its preceding phase
is reviewed and verified.

Various modified waterfall models (including Royce's final model), however, can include slight or
major variations on this process.[3] These variations included returning to the previous cycle after
flaws were found downstream, or returning all the way to the design phase if downstream phases
deemed insufficient.
DATA FLOW DIAGRAM

The first step is to draw a data flow diagram (DFD). The DFD was first developed by Larry
Constantine as a way of expressing system requirements in graphical form. A DFD also known
as a “bubble chart” has the purpose of clarifying system requirements and identifying major
transformations that will become programs in system design. This is the starting point of the
design phase that functionally decomposes the requirements specifications down to the lowest
level of detail. A DFD consists of series of bubbles join by the data flows in the system.
The purpose of data flow diagrams is to provide a semantic bridge between users and developers.
• Graphical, eliminating thousands of words;
• Hierarchical, showing systems at any level of detail; and
• Jargon less, allowing user understanding and reviewing.
Data flow diagrams are supported by other techniques of structured systems analysis such as
data structure diagrams, data dictionaries, and procedure-representing techniques. The goal of
data flow diagram is to have a commonly understood of a system. In Data flow diagram, the
entire concept of the system is provided and drawn in flow chart.
SYMBOLS USED IN DATA FLOW DIAGRAMS

 EXTERNAL ENTITY

A rectangle ( ) creates any external entity to the system being modeled.

 PROCESS

Bubbled or circle are used to indicate where incoming data flows are proposed and then
transformed into outgoing data flow.

 DATA FLOW

The arrow marking is the movement of data through the system indicates data flow.
 DATA STORE

Open rectangles are used to identify holding points for data.


 OUTPUT SYMBOL

The hard copy is produced using the output t and the user of the copies cannot be
clearly specified or three or several users of the output.
LEVELO

ADMIN
ADMIN
LIBRARY
MANAGEMENT
SYSTEM

USER USER
LEVEL1

LOGIN

ADMIN
/USER

LOGIN

CHOOSE CHOOSE BOOK BOOK


BOOKCOPY ISSUE TYPE
BOOK

VIEW LIBRARY
MANAGEMENT

PRINT

LOG OUT
LEVEL2

RESERVE BOOK
USER USER RECEIVE
BOOKS

LIBRARY
MANAGEMENT FINE SYSTEM
DISPLAY INFO
SELECT BOOK

READER INFO

SYSTEM DISPLAY
ADD/DELETE
INFO

AUTHENTICATI
ON

ISSUE BOOK

DISPLAY
REPORTS
LIBRARY STAFF

RETURNBOOK
PLATFORM OVERVIEW
PHP
PHP is a general-purpose programming language originally designed for web development. It was
originally created by Rasmus Lerdorf in 1994;[5] the PHP reference implementation is now produced
by The PHP Group.[6] PHP originally stood for Personal Home Page,[5] but it now stands for
the recursive initialism PHP: Hypertext Preprocessor.

PHP code may be executed with a command line interface (CLI), embedded into HTML code, or
used in combination with various web template systems, web content management systems,
and web frameworks. PHP code is usually processed by a PHP interpreter implemented as
a module in a web server or as a Common Gateway Interface (CGI) executable. The web server
outputs the results of the interpreted and executed PHP code, which may be any type of data, such
as generated HTML code or binary image data. PHP can be used for many programming tasks
outside of the web context, such as standalone graphical applications[8] and robotic drone control.

The standard PHP interpreter, powered by the Zend Engine, is free software released under
the PHP License. PHP has been widely ported and can be deployed on most web servers on almost
every operating system and platform, free of charge.

The PHP language evolved without a written formal specification or standard until 2014, with the
original implementation acting as the de facto standard which other implementations aimed to follow.
Since 2014, work has gone on to create a formal PHP specification
Introduction to Database :

An organization must have accurate and reliable data for effective decision
making. To this end, the organization maintains records on the various facets maintaining
relationships among them. Such related data are called a database. A database system is
an integrated collection of related files, along with details of the interpretation of the data
contained therein. Basically, database system is nothing more than a computer-based
record keeping system i.e. a system whose overall purpose is to record and maintain
information/data.

A database management system (DBMS) is a software system that allows access


to data contained in a database. The objective of the DBMS is to provide a convenient
and effective method of defining, storing and retrieving the information contained in the
database. The DBMS interfaces with the application programs, so that the data contained
in the database can be used by multiple applications and users. In addition, the DBMS
exerts centralized control of the database, prevents fraudulent or unauthorized users from
accessing the data, and ensures the privacy of the data.

.
SQL Commands
o SQL commands are instructions. It is used to communicate with the database. It is
also used to perform specific tasks, functions, and queries of data.

o SQL can perform various tasks like create a table, add data to tables, drop the table,
modify the table, set permission for users.

Types of SQL Commands

There are five types of SQL commands: DDL, DML, DCL, TCL, and DQL.
1. Data Definition Language (DDL)
o DDL changes the structure of the table like creating a table, deleting a table, altering
a table, etc.

o All the command of DDL are auto-committed that means it permanently save all the
changes in the database.

Here are some commands that come under DDL:

o CREATE

o ALTER

o DROP

o TRUNCATE

2. Data Manipulation Language


o DML commands are used to modify the database. It is responsible for all form of
changes in the database.

o The command of DML is not auto-committed that means it can't permanently save all
the changes in the database. They can be rollback.

Here are some commands that come under DML:

o INSERT

o UPDATE

o DELETE

3. Data Control Language

DCL commands are used to grant and take back authority from any database user.

Here are some commands that come under DCL:


o Grant

4. Transaction Control Language

TCL commands can only use with DML commands like INSERT, DELETE and UPDATE only.

These operations are automatically committed in the database that's why they cannot be
used while creating tables or dropping them.

Here are some commands that come under TCL:

o COMMIT

o ROLLBACK

o SAVEPOINT

5. Data Query Language

DQL is used to fetch the data from the database.It uses only one command:

o SELECT

a. SELECT: This is the same as the projection operation of relational algebra. It is used to
select the attribute based on the condition described by WHERE clause.
Key Constraints in DBMS

 Constraints or nothing but the rules that are to be followed while entering data
into columns of the database table
 Constraints ensure that data entered by the user into columns must be within the
criteria specified by the condition
 For example, if you want to maintain only unique IDs in the employee table or if
you want to enter only age under 18 in the student table etc
 We have 5 types of key constraints
o NOT NULL: ensures that the specified column doesn’t contain a NULL
value.
o UNIQUE: provides a unique/distinct values to specified columns.
o DEFAULT: provides a default value to a column if none is specified.
o CHECK: checks for the predefined conditions before inserting the data
inside the table.
o PRIMARY KEY: it uniquely identifies a row in a table.
o FOREIGN KEY: ensures referential integrity of the relationship
ENTITY RELATIONSHIP DIAGRAM

An Entity Relationship (ER) Diagram is a type of flowchart that illustrates how “entities” such as
people, objects or concepts relate to each other within a system. ER Diagrams are most often
used to design or debug relational databases in the fields of software engineering, business
information systems, education and research. Also known as ERDs or ER Models, they use a
defined set of symbols such as rectangles, diamonds, ovals and connecting lines to depict the
interconnectedness of entities, relationships and their attributes.
There are different type of attributes .They are:-
 Single value and multi valued
 Simple or composite
 Null attributes

Different model are used for designing a database they are:-


 Relational model
 Hierarchical model
 Network model

In addition to this model there are other model, they are:-


 Entity relationship model
 Object oriented data model
 Semi structured model
ER DIAGRAMS

PRICE
PUBLISHER
BOOK_ID
NAME
ISBN EDITION\VERS
COPY_ID ION

ID

BOOK COPY RACK


BOOK HAS NUMBER
AUTHOR

TYPE_ID CURRENT
OWNER(USER)
BOOK ID _ID)

LANGUAGE
TRANSACTION
ID BOOK COPY ID
HAS ISSUED TO
BORR
TYPE_NAME
OW BOOK ISSUE ISSUED ON

DUE DATE

TYPE_ID BOOK TYPE


RETURN DATE

FINE

ISSUE
BOOK

USER_ID
USER_NAME

USER
ADDRESS USER
GENDER

USER PH NO

USER EMAIL PASSWORD


NAME
SYSTEM DESIGN
TABLE DESIGN
1. TABLE NAME: BOOK

FIELD NAME TYPE CONSTRAINTS DESCRIPTION


BOOK_ID INT(11) PRIMARY KEY BOOK_ID
BOOK_NAME VARCHAR(255) BOOK_NAME
PUBLISHER VARCHAR(255) BOOK_PUBLISHER
ISBN INT(11) BOOK_ISBN
AUTHOR VARCHAR(255) BOOK_AUTHOR
TYPE ID INT(11) BOOK_TYPE ID
LANGUAGE VARCHAR(255) BOOK_LANGUAGE

2.TABLE NAME:USER

FIELD NAME TYPE CONSTRAINTS DESCRIPTION


USER_ID INT(11) PRIMARY KEY USER_ID
USER_NAME VARCHAR(225) USER_NAME
USER_ADDRESS VARCHAR(225 USER_ADDRESS
USER_PH NO INT(11) USER_PH NO
USER_EMAIL VARCHAR(225 USER_EMAIL
NAME VARCHAR(225 NAME
PASSWORD VARCHAR(225 USER_PASSWORD
GENDER VARCHAR(225 USER_GENDER
3. TABLE NAME:BOOK COPY

FIELD NAME TYPE CONSTRAINTS DESCRIPTION


BOOK COPY_ID INT(11) PRIMARY KEY BOOK_ID
BOOK_ID INT(11) BOOK_NAME
PRICE INT(11) BOOK_PUBLISHER
EDITION\VERSION INT(11) BOOK_ISBN
RACK NUMBER INT(11) BOOK_AUTHOR
CURRENT OWNER VARCHAR(255) BOOK_TYPE ID

4. TABLE NAME:BOOK ISSUE

FIELD NAME TYPE CONSTRAINTS DESCRIPTION


TRANSACTION_ID INT(11) PRIMARY KEY TRANSACTION_ID
BOOK_ID INT(11) BOOK_ID
BOOK COPY _ID INT(11) BOOK COPY _ID
ISSUED TO VARCHAR(225) BOOK ISSUED TO
ISSUED ON DATE TIME BOOK ISSUED ON
RETURN ON DATE TIME BOOK RETURN ON
FINE INT BOOK FINE

5.TABLE NAME:BOOK TYPE

FIELD NAME TYPE CONSTRAINTS DESCRIPTION


TYPE_ID INT(11) PRIMARY KEY BOOK TYPE_ID

TYPE_NAME VARCHAR(225) BOOKTYPE_NAME

Vous aimerez peut-être aussi