The Digital Library Mangement System

See discussions, stats, and author profiles for this publication at: https://www.researchgate.
net/publication/369020218
The Digital Library Management System 2021 : Design and Implementation of

an integrated Library Management System
Thesis · February 2021

DOI: 10.13140/RG.2.2.12011.00803
CITATIONS READS
0 1,391
1 author:
Glavin Gaga
University of Mumbai
1 PUBLICATION 0 CITATIONS
SEE PROFILE
All content following this page was uploaded by Glavin Gaga on 05 March 2023.
The user has requested enhancement of the downloaded file.

LIBRARY MANAGEMENT SYSTEM
T.Y.B.Sc.I Page 1
T

A Project Report
Submitted in partial fulfillment of the
Requirements for the award of the Degree of
BACHELOR OF SCIENCE (INFORMATION TECHNOLOGY)

By
GLEVIN STANISLAUS GAGA
Under the esteemed guidance of
Ms.Meenakshi Dhande
&
Ms.Sheetal Vekhande
DEPARTMENT OF INFORMATION TECHNOLOGY

MODEL COLLEGE OF SCIENCE & COMMERCE
University of Mumbai
KALYAN (E)-421306
MAHARASHTRA
2020-2021
T.Y.B.Sc.I Page 2
T
.
T.Y.B.Sc.I Page 3
T
PERFORM FOR THE APPROVAL OF THE PROJECT PROPOSAL
(Note: All entries of the proforma of approval should be filled up with

appropriate and complete information. Incomplete proforma of approval in
any respect will be summarily rejected.)
PNR No.: ................................ Roll no:
1. Name of the Student : GLEVIN STANISLUS GAGA
2. Title of the Project : LIBRARY MANAGEMENT SYSTEM
3. Name of the Guide : Ms.Meenakshi Dhande & Ms.Sheetal Vekhande
4. Is this your first submission? Yes No
Signature of the Student Signature of the Guide

Date: ………………… Date: …………………
Signature of the coordinator

Date: ………
T.Y.B.Sc.I Page 3
T
NGO
MODEL COLLEGE OF SVIENCE & COOMMERCE
(Affiliated to University of Mumbai)
DEPARTMENT OF INFORMATION TECHNOLOGY
CERTIFICATE
This is to certify that the project entitled, "LIBRARY MANAGEMENT ", is bonafied
work of GLEVIN STANISLAUS GAGA bearing Seat No: ( ) submitted in partial
fulfillment of the requirements for the award of degree of BACHELOR OF SCIENCE in
INFORMATION TECHNOLOGY from University of Mumbai.
Internal Guide Coordinator
External Examiner
Date: College Seal
T.Y.B.Sc.I Page 4
T
NGO
DECLARATION
I GLEVIN STANISLAUS GAGA STUDENT OF MODEL COLLEGE OF SCI. & COM.

RAJBHAR NAGAR CHINCHPADA ROAD, KATEMANAVALI, KALYAN (EAST)
421306. STUDYNIG IN 3RD YEAR BSC INFORMATION TECHNOLOGY HEAR BY
DECLARE THAT I HAVE COMPLETED THIS PROJECT ON SOCIAL NETWORKING
SITE DURING THE ACDEMIC YEAR 2019-20
THE INFORMATION SUBMITTED IS TRUE AND ORIGINAL TRUE THE BEST OF MY

KNOWLEDGE
DATE:
PLACE:
Ram Gajanan Barapatre
T.Y.B.Sc.I Page 5
T
NGO
ACKNOWLEDGEMENT
I WISH TO EXPRESS MY SINCERE GRATITUDE TO PROJECT MR. K.S

BRAMHAWALE PRINCIPAL OF MODEL COLLEGE OF SCI. & COM. FOR
PROVIDING ME AND OPPORTUNITY TO DO ANY MY WEB PROJECT WORK ON
ONLINE DONATION TO NGO IN SINCERELY THANK MY PROJECT GUIDE
MS.MINAKSHI DHANDE AND MS. SHEETAL VEKHANDE FOR GUIDENCE AND
ENCOURAGMENT IN CARRYING OUT THIS PROJECT WORK.
SPECIAL THANKS TO ALL THE LAB SYSTEMS FOR SEEMINGLY SMALL BUT
VALUABLE HELP FOR TIMELY INTERNET ACCESS AND LAB ACCESS
T.Y.B.Sc.I Page 6
T
TABLE OF CONTENTS
Sr. No. INDEX Pg. Sign
No.
CHAPTER 1: INTRODUCTION
1.1 Background
1.2 Objectives
1.3 Purpose, Scope & Applicability
1.3.1 Purpose
1.3.2 Scope
1.3.3 Applicability
1.4 Organization of Report
CHAPTER 2: SURVEY OF
TECHNOLOGIES
CHAPTER 3: REQUIREMENTS AND

ANALYSIS
3.1 Problem Definition
3.2 Requirements Specification
3.3 Planning and Scheduling
3.4 Software and Hardware
Requirements
3.5 Conceptual Models
CHAPTER 4: SYSTEM DESIGN

4.1 Basic Modules
4.2 Data Design
4.2.1 Schema Design
4.2.2 Data Integrity and Constraints
4.3 Procedural Design
4.3.1 Logic Diagrams
4.3.2 Algorithm Design
4.4 User Interface Design
4.5 Security Issues
4.6 Test Case Design
T.Y.B.Sc.I Page 7
T
CHAPTER5 IMPLEMENTATION
5.1 Introduction
5.2 Sample Code
CHAPTER 6 TESTING
6.1 Introduction to system training
CHAPTER 7 SAMPLE SCREENSHOTS
CHAPTER8 CONCLUSION
CHAPTER 9 BIBLIOGRAPHY
T.Y.B.Sc.I Page 8
T
NGO
ABSTRACT
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 not
available in normal library management systems like facility of user login and a facility of
teachers login .It also has a facility of admin login through which the admin can monitor the
whole system .It also has facility of an online notice board where teachers can student can put up
information about workshops or seminars being held in our colleges or nearby colleges and
librarian after proper verification from the concerned institution organizing the seminar can add it
to the notice board . It has also a facility where student after logging in their accounts can see list
of books issued and its issue date and return date and also the students can request the librarian to
add new books by filling the book request form. The librarian after logging into his account ie
admin account can generate various reports such as student report, issue report, teacher report
and book report
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.
T.Y.B.Sc.I Page 8
T
NGO
CHAPTER 1:- INTRODUCTION

The project titled Library Management System is Library Management software for monitoring and
controlling the transactions in a library .The project “Library Management System” is developed in
php, which mainly focuses on basic operations in a library like adding new books, and updating new
information, searching books and members and return books.
This project of “LIBRARY MANAGEMENT” of gives us the complete information about the
library. We can enter the record of new books and retrieve the details of books available in the
library. We can issue the books to the students and maintain their records and can also check how
many books are issued and stock available in the library. In this project we can maintain the late fine
of students who returns the issued books after the due date.
Throughout the project the focus has been on presenting information and comments in an easy and
intelligible manner. The project is very useful for those who want to know about Library
Management System.
T.Y.B.Sc.I Page 9
T
NGO
1.1 BACKGROUND
Library Management System is an application which refers to library systems which are
generally small or medium in size. It 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. With 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 Management 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.
T.Y.B.Sc.I Page 10
T
NGO
1.2 OBJECTIVES
This project is based on the RDBMS technology; the main objective of this project is to computerize
the manual system & reduce the time consumption.
In other words we can say that our project has the following objectives:-
• Make all the system computerize
• Reduce time consumption
• Reduce error scope
• All system managements are automated
• Centralized database management
• Easy operations for operator of the system
• No paper work requirement
T.Y.B.Sc.I Page 11
T
NGO
T.Y.B.Sc.I Page 12
T
NGO
1.3.1 PURPOSE
A Library Management System (LMS) gives access to and manages the resources in your library. A
well-chosen system will increase your library’s efficiency, save valuable administration time, lead to
a better educational experience for pupils and help develop independent learning.
A typical computerised LMS has the following functions/modules as standard:
• circulation – this not only deals with the borrowing and returning of materials but also renewals, the
management of overdue and user records
• report and statistic generation of various library activities
• administration – so you can configure the system to your school’s own needs e.g. create IDs and
passwords, establish user classes and set loan periods etc
• OPAC (Online Public Access Catalogue) – this is an online database of all materials held in the
library which is made public so users can search and locate books for reading teaching and learning
purposes The OPAC also lists the number of items available, whether they are in the library or out
on loan, and their call number.
1.3.2 SCOPE
The scope of Online Library Management System includes:
• Create distinct product users based on their roles and permissions.

• Authenticate users at their login.
• Provide the list of books the users can borrow.
• Facility to reserve books that are available.
• A status page for all users to view books reserved by them.
• Facility to cancel the reservation for a book made earlier.
• A status page for all users to view books borrowed by them, their individual due dates and their
individual penalties if any.
• An interface to view and edit the own profile.
• Provide method for adjusting account settings such as passwords.
• Mechanism to reset the password in case user forgets it.
• Providing interface to add or delete books to staffs
T.Y.B.Sc.I Page 13
T
NGO
1.3.3 APPLICABILITY
▪ Using library management system the librarian can catalogue and maintain all types of books,
journals, CD's etc.
▪ Provision to request for new titles, journals and magazines.
▪ Powerful search engine allows users to find information in the library in no time.
▪ Charge users for lost/damaged books.
▪ Automatic fine fees calculation.
▪ Newspapers attendance is maintained.
1.4 ORGANISATION OF REPORT
➢ SURVEY OF TECHNOLOGIES : In this chapter we should discuss the

student should awareness and understanding of available technologies related
to the topic
➢ REQUIREMENTS AND ANALYSIS: In this chapter we should discuss the
requirements specification of the system i.e hardware and software problem
definition planning and scheduling.
➢ SYSTEM DESIGN: In this chapter we discuss the or describes features and
operation in detail, including screen layout , business rule, process diagram,
pseudo code and other documentation.
➢ The chapter 5 to 7 include the IMPLEMENTATION AND TESTING

,RESULTS AND DISCUSSION ,CONCLUSIONS,REFERENCES should be
submitted in next semester i.e VI
➢ IMPLEMENTATION AND TESTING: inside the implementation and testing

we should discuss Coding Details and Code Efficiency, types of testing,
testing approches, Modifications and Improvements of there projects.
T.Y.B.Sc.I Page 14
T
NGO
➢ RESULTS AND DISCUSSION :we should discuss the test reports and user
documentation
➢ CONCLUSIONS: The conclusions can be summarised in a fairly short chapter

(2 or 3 pages). This chapter brings together many of the points that would
have made in the other chapters.
➢ REFERENCES: In this topic we should discuss the bibliography and website

used to create the project.
T.Y.B.Sc.I Page 15
T
NGO
CHAPTER 2:-SURVEY OF TECHNOLOGIES
FRONT END – HTML
Hypertext Markup Language (HTML) is the standard markup language for creating web pages and
web applications. With Cascading Style Sheets (CSS) and JavaScript, it forms a triad of cornerstone
technologies for the World Wide Web. Web browsers receive HTML documents from a web server
or from local storage and render the documents into multimedia web pages. HTML describes the
structure of a web page semantically and originally included cues for the appearance of the
document.
BOOTSTRAP
BOOTSTRAP is a framework to design websites. I have used Bootstrap because it reduces length of
the program. Suppose, a program is of 50 lines, bootstrap can make it in 15-20 lines. So, it saves
time, space and reduces complexity.
CSS
Cascading Style Sheets (CSS) is a style sheet language used for describing the presentation of a
document written in a markup language like HTML. CSS is a cornerstone technology of the World
Wide Web, alongside HTML and JavaScript.CSS is designed to enable the separation of
presentation and content, including layout, colors, and fonts. This separation can improve content
accessibility, provide more flexibility and control in the specification of presentation characteristics,
enable multiple web pages to share formatting by specifying the relevant CSS in a separate .css file,
and reduce complexity and repetition in the structural content.
Java Script
JavaScript often abbreviated as JS, is a high-level, interpreted programming language. It is a

language which is also characterized as dynamic, weakly typed, prototype-based and multi-
paradigm.
T.Y.B.Sc.I Page 16
T
NGO
BACK END – PHP
PHP is a scripting language, which is what is needed for interactive websites. Meanwhile, PHP can
work alongside HTML.
MySQL
MySQL here works s Database Management System. Databases are essential component for a
website. PHP & MySQL work hand-in-hand to create quality rich content applications.
Overall, the project is made up of compatible languages. Front End & Back End, both work hand-in-
hand to make this project successful.
PHP is an open source language and all its components are free to use and distribute. PHP is server-
side scripting language. It is embedded in HTML source code. PHP supports all major web servers
such as Apache, Microsoft IIS and Netscape etc. All the major database such as Mysql, PostgreSQL,
Oracle, Sybase, Microsoft SQL Server is supported by PHP. Following are the some major
advantage:- ▪ Friendly With HTML - PHP and HTML are interchangeable within the page. You can
put PHP outside the HTML or inside. ▪ Interactive Features - PHP allows you to interact with your
visitors in ways HTML alone can't. ▪ Top-Notch Online Documentation - The PHP documentation is
the best on the web. Hands down. ▪ Compatible With Databases - A good benefit of using PHP is
that it can interact with many different database languages including MySQL.
T.Y.B.Sc.I Page 17
T
NGO
CHAPTER 3 :-REQUIREMENTS AND

ANALYSIS
3.1 PROBLEM DEFINATION
The problem occurred before having computerized system includes:
• File lost when computerized system is not implemented file is always lost because of human
environment. Sometimes due to some human error there may be a loss of records.
• File damaged When a computerized system is not there file is always lost due to some accident
like spilling of water by some member on file accidentally. Besides some natural disaster like floods
or fires may also damage the files. Library Management System Division Of Computer Science And
Engineering
• Difficult to search record when there is no computerized system there is always a difficulty in
searching of records if the records are large in number
• Space consuming after the number of records become large the space for physical storage of file
and records also increases if no computerized system is implemented.
• Cost consuming As there is no computerized system the to add each record paper will be needed
which will increase the cost for the management of library
T.Y.B.Sc.I Page 18
T
NGO
3.2 REQUIREMENTS SPECIFICATION
A software requirements specification is a document that captures complete description about how
the system is expected to perform. It is usually signed off at the end of requirements engineering
phase
Product Requirements
EFFICIENCY REQUIREMENT
When a library management system will be implemented librarian and user will easily acess library
as searching and book transaction will be very faster.
RELIABILITY REQUIREMENT
The system should accurately performs member registration, member validation , report generation,
book transaction and search
USABILITY REQUIREMENT
The system is designed for a user friendly environment so that student and staff of library can
perform the various tasks easily and in an effective way.
IMPLEMENTATION REQUIREMNTS
In implementing whole system it uses html in front end with php as server side scripting language
which will be used for database connectivity and the backend i.e. the database part is developed
using MySQL.
DELIVERY REQUIREMENTS
The whole system is expected to be delivered in six months of time with a weekly evaluation by the
project guide.
T.Y.B.Sc.I Page 19
T
NGO
3.3 PLANNING AND SCHEDULING
➢ PLANNING
Project planning defines the project activities and end products that will be performed and
describes how the activities will be accomplished. The purpose of project planning is to define
each major task, estimate the time and resources required, and provide a framework for
management review and control. The project planning activities and goals include defining: • the
specific work to be performed and goals that define and bind the project. • Estimates to be
documented for planning, tracking, and controlling the project. •
Commitments that are planned, documented, and agreed to by affected groups. • Project
alternatives, assumptions, and constraints.
➢ SCHEDULING:
The project schedule provides a graphical representation of predicted tasks, milestones,

dependencies, resource requirements, task duration, and deadlines. The project’s master schedule
interrelates all tasks on a common time scale. The project schedule should be detailed enough to
show each WB Stask to be performed, the name of the person responsible for completing the task,
the start and end date of each task, and the expected duration of the task.
• Define the type of schedule

• Define precise and measurable milestones
• Estimate task duration
• Define priorities
• Define the critical path
• Document assumptions
• Identify risks
T.Y.B.Sc.I Page 20
T
GANTT CHART
➢ A Gantt chart is a horizontal bar chart used in project management as a tool for
graphically representing the schedule of a set of specific activities or tasks. The
horizontal bars indicate the length of time allocated to each activity, so the x- axis of a
Gantt chart is subdivided into equal units of time, e.g., days, weeks, months. The y-axis
of a Gantt chart, on the other hand, simply lists all the activities or tasks being
monitored by the Gantt char
July August September
Month
Weeks Weeks Weeks
1 2 3 4 1 2 3 4 1 2 3 4
Planning
Requirement
gathering
Analysis
Design
T.Y.B.Sc.I Page 19
T
NGO
3.4 HARDWARE AND SOFTWARE REQUIREMNTS
SOFTWARE REQUIREMENTS
•Operating system- Windows 7 is used as the operating system as it is stable and supports more
features and is more user friendly
• Database MYSQL-MYSQL is used as database as it easy to maintain and retrieve records by
simple queries which are in English language which are easy to understand and easy to write.
• Development tools and Programming language- HTML is used to write the whole code and
develop webpages with css, java script for styling work and php for sever side scripting. 2.1.4.2
HARDWARE REQUIREMENTS  Intel core i5 2nd generation is used as a processor because

it is fast than other processors an provide reliable and stable and we can run our pc for longtime.
By using this processor we can keep on developing our project without any worries.  Ram 1 gb is
used as it will provide fast reading and writing capabilities and will in turn support in processing
T.Y.B.Sc.I Page 20
T
NGO
3.5 CONCEPTUAL MODLES
ER DIAGRAMS: A graphical model of the data needed by a system, including things

about which information is stored & the relationships among them, produced in structured
analysis & information engineering. ER Diagram represents entities or tables and their
relationships with one another.
T.Y.B.Sc.I Page 21
T
NGO
ER DIAGRAM
T.Y.B.Sc.I Page 22
T
NGO
DATA FLOW DIAGRAM

➢ A data flow diagram (DFD) is a graphical representation of the "flow" of data
through an information system.
➢ DFDs can also be used for the visualization of data processing (structured design).
➢ It views a system as a function that transform the input into desired output.
SYMBOLS:
T.Y.B.Sc.I Page 23
T
NGO
DFD LEVEL -0
DFD LEVEL -1
T.Y.B.Sc.I Page 24
T
NGO
T.Y.B.Sc.I Page 25
T
NGO
OBJECT ORIENTED DIAGRAM
CLASS DIAGRAM:
A class diagram is an illustration of the relationships and source code
dependencies among classes in the Unified Modeling Language (UML).
In this context, a class defines the methods and variables in an object,
which is a specific entity in a program or the unit of code representing
that entity. Class
Diagrams are useful in all forms of object-oriented programming (OOP).
T.Y.B.Sc.I Page 26
T
NGO
CHAPTER 4 :-SYSTEM DESIGN
4.1 BASIC MODULES
BASIC MODULES: -
• Admin Panel
▪ Admin Dashboard
▪ Admin can add/update/ delete category
▪ Admin can add/update/ delete author
▪ Admin can add/update/ delete books
▪ Admin can issue a new book to student and also update the details when student return book
▪ Admin can search student by using their student ID
▪ Admin can also view student details
▪ Admin can change own password
• Student Panel
▪ Student can register yourself and after registration they will get studentid
▪ After login student can view own dashboard.
▪ Student can update own profile.
▪ Student can view issued book and book return date-time.
▪ Student can also change own password.
▪ Student can also recover own password.
T.Y.B.Sc.I Page 27
T
NGO
Process Login
Home:
When the user/student click on this tab, it will display the other modules and pages of
the website such as Books, payment status, login, sign up, popular section, feedback
section, contact and admin login. This module will be used to display the brief
introduction of the project and will show the title of the project.
Books:
Student can view all available Books by clicking on Books tab where he can choose
book according to his own interest and by clicking on a particular book, will display
more details with title of the book, if he wants to purchase he will be able to make
payment (required login).
Payment Status:
After purchasing book student will be provided an order id which can be used to get
the status of payment using Payment status tab. If student wants he can get print out of
his payment status.
Login:
This is a login form. Student can use their own email and password to login into the
student panel.
Sign Up:
This is a Registration form for new Students. New Students can fill up the form for
registration and after successful registration they can use their email id and password to
login into the application.
T.Y.B.Sc.I Page 28
T
NGO
Feedback:
This is very simple section which displays feedback given by the registered student.
Contact:
Students can use this section to contact the admin/tutor for any kind of queries.
Student Panel:-
Profile:
Students can view their student id, registered email id, name, occupation, profile
picture as well as they can modify and update the new data if they need.
My Books:
Students can view all Books which they purchased. This is the place where they can
start watching Books by clicking on Watch books button which leads to books playlist
where they can watch the entire lesson of book.
Feedback:
Students can view/write feedback.
Change Password:
Students can use this module to change password.
Logout:
This module is used exit student panel and return back to Home Page.
T.Y.B.Sc.I Page 29
T
NGO
Admin Panel
Dashboard:
This module displays overview of whole application such as number of books,

number of registered students etc.
Books:
This is the most important module of admin panel where Admin can view list of book as
well as add new books and modify or delete books.
Students:
Admin can view registered students details. Admin can add, edit and delete student.
Feedback:
Admin can view/delete feedback given by student.
Sell Report:
Analyzing sales is very import for any kind of business and this module is perfect for
analyzing sales based on date. It will generate sells report which can be possible to
print out for office records.
T.Y.B.Sc.I Page 30
T
4.2 DATA DESIGN
EVENT TABLE
Event Trigger Source Activity Response Destination

Validate Login
Admin Login
Admin password & successful or Admin
Login request sent
login name denied
Admin Validate
Donation Donation
creates Donation
program Admin Program Admin
program for Program
created. Created
donation Details
Admin
Verifies and Verified and
deletes Deletion
Admin deletes deleted Admin
member request sent
account account
account
Admin Add Event Admin Add Event Event Admin
creates event details details Details
program successfully Added
Admin Delete Event Admin Deleted Deleted Admin
delete Event Details Event details Event
program Successfully details.
T.Y.B.Sc.I Page 31
T
NGO
4.2.1 SCHEMA DESIGN
A database system is an overall collection of different database software components and

database containing the parts viz. Database application programs, front-end components,
Database Management Systems, and Databases.
Normalization
Normalization is the process of organizing data in a database. This includes creating tables
and establishing relationships between those tables according to rules designed both to
protect the data and to make the database more flexible by eliminating redundancy and
inconsistent dependency. Redundant data wastes disk space and creates maintenance
problems .If data that exists in more than
one place must be changed , the data must be changed in exactly the same way in all
locations. A buyer’s or promoter’s address change is much easier to implement if that data is
stored only in the buyer’s or promoter’s table and nowhere else in the database. There are a
few rules for database normalization. Each rule is called a “normal form
Data structuring is defined through a process called normalization. Data are grouped in the
simplest way possible so that later changes can be made with a minimum of impact on the
data structure.
There are different forms of normal forms
• First normal form(1NF)
• Second normal form(2NF)
• Third normal form(3NF)
• Boyce code normal form(BCNF)
• Fourth Normal form(4NF)
• Fifth Normal Form(5NF)
T.Y.B.Sc.I Page 32
T
NGO
User_ DeTails Table:
Attribute Data Type Description
admin_id # int(11) Stores Admin ID
admin_name Varchar(255) Stores Admin Name
Admin_email Varchar(255) Stores Admin Email ID
Admin_pass Varchar(255) Stores Admin Password
Admin _details Table :-
stu_id # int(11) Stores Book ID
stu_name Varchar(255) Stores book Name
stu_email Varchar(255) Stores book description
Stu_pass Varchar(255) Stores book author/instructor
Stu_occ Varchar(255) Stores book display picture
Stu_img text Stores book duration
T.Y.B.Sc.I Page 34
T
NGO
Table Name:Feedback (Stores Feedback Detail)

f_id # int(11) Stores Feedback ID
f_content text Stores Feedback content
stu_id int(11) Stores Student ID
Table Name:book (Stores Book Detail)

book_id # int(11) Stores Book ID
book_name text Stores book Name
book_desc text Stores book description
book_author varchar(255) Stores book author/instructor
book_img text Stores book display picture
book_duration text Stores book duration
book_price int(11) Stores book selling price
book_original_price int(11) Stores book original price
T.Y.B.Sc.I Page 35
T
NGO
Table Name:bookorder (Stores Book order Detail)

co_id # int(11) Stores book order ID
order_id varchar(255) Stores Order ID (Random)
stu_email varchar(255) Stores student email id
book_id int(11) Stores book id
status varchar(255) Stores payment status
respmsg text Stores payment response msg
amount int(11) Stores book amount
order_date date Stores purchase date
T.Y.B.Sc.I Page 36
T
NGO
4.2.2 DATA INTEGRITY AND CONSTRAINTS
The term data integrity refers to the accuracy and consistency of data.
When creating databases, attention needs to be given to data integrity and how to maintain it. A
good database will enforce data integrity whenever possible.
For example, a user could accidentally try to enter a phone number into a date field. If the
system enforces data integrity, it will prevent the user from making these mistakes.
Maintaining data integrity means making sure the data remains intact and unchanged
throughout its entire life cycle. This includes the capture of the data, storage, updates, transfers,
backups, etc. Every time data is processed there’s a risk that it could get corrupted (whether
accidentally or maliciously).
Risks to Data Integrity
Some more examples of where data integrity is at risk:
• A user tries to enter a date outside an acceptable range.
• A user tries to enter a phone number in the wrong format.
• A bug in an application attempts to delete the wrong record.
• While transferring data between two databases, the developer accidentally tries to insert the
data into the wrong table.
• While transferring data between two databases, the network went down.
• A user tries to delete a record in a table, but another table is referencing that record as part
of a relationship.
T.Y.B.Sc.I Page 37
T
NGO
4 Types of Data Integrity
In the database world, data integrity is often placed into the following types:
❖ Entity integrity
❖ Referential integrity
❖ Domain integrity
❖ User-defined integrity
Entity Integrity
Entity integrity defines each row to be unique within its table. No two rows can be the same.
To achieve this, a primary key can be defined. The primary key field contains a unique
identifier – no two rows can contain the same unique identifier.
Referential Integrity
Referential integrity is concerned with relationships. When two or more tables have a
relationship, we have to ensure that the foreign key value matches the primary key value at all
times. We don’t want to have a situation where a foreign key value has no matching primary
key value in the primary table. This would result in an orphaned record.
So referential integrity will prevent users from:
• Adding records to a related table if there is no associated record in the primary table.
• Changing values in a primary table that result in orphaned records in a related table.
• Deleting records from a primary table if there are matching related records.
Domain Integrity
Domain integrity concerns the validity of entries for a given column. Selecting the appropriate
data type for a column is the first step in maintaining domain integrity. Other steps could
T.Y.B.Sc.I Page 38
T
NGO
include, setting up appropriate constraints and rules to define the data format and/or restricting
the range of possible values.
User-Defined Integrity
User-defined integrity allows the user to apply business rules to the database that aren’t
covered by any of the other three data integrity types
Constraints enforce limits to the data or type of data that can be inserted/updated/deleted from
a table. The whole purpose of constraints is to maintain the data integrity during an
update/delete/insert into a table. In this tutorial we will learn several types of constraints that
can be created in RDBMS.
Types of constraints
• NOT NULL
• UNIQUE
• DEFAULT
• CHECK
• Key Constraints – PRIMARY KEY, FOREIGN KEY
• Domain constraints
• Mapping constraints
T.Y.B.Sc.I Page 39
T
NGO
4.3 PROCEDURAL DESIGN:-
T.Y.B.Sc.I Page 40
T
NGO
4.3.1 LOGIC DIAGRAM:-
The diagram control is used for creating diagrams like flow charts, organizational charts, mind
maps, floor plans, and swim lane diagrams either through code or through a visual interface.
Nodes
Nodes are used to host graphical objects like paths and controls that can be arranged and
manipulated on a diagram page.
Many predefined standard shapes are included.
➢ Custom shapes can also be created and added easily.
➢ A node’s appearance can be fully customized.
➢ A node’s UI can also be templated and re-used across multiple nodes.
Connectors :-
The relationship between two nodes is represented using a connector. Multiple instances of
nodes and connectors form a diagram.
T.Y.B.Sc.I Page 41
T
NGO
ACTIVITY DIAGRAM
Activity diagram is another important diagram in UML to describe the dynamic aspects of
the system.Activity diagram is basically a flowchart to represent the flow from one activity
to another activity. The activity can be described as an operation of the system.
The control flow is drawn from one operation to another. This flow can be sequential,
branched, or concurrent. Activity diagrams deal with all type of flow control by using
different elements such as fork, join, etc
T.Y.B.Sc.I Page 42
T
NGO
4.4 USER INTERFACE DIAGRAM
USE CASE DIAGRAM

Use Case
A use case diagram is essentially a picture showing system behavior

along with the key actors that interact with the system. The use case
represents complete functionality. Use case diagram can be imagined as a
black box where only the input, output, and the function of the black box
are known. Use Case elements are used to make test cases when
performing the testing. The use case should contain all system activities
that have significance to the users. A use case can be thought of as a
collection of possible scenarios related to a particular goal, indeed. Use
cases can be employed during several stages of software development,
such as planning system requirements, validating design and testing
software.
Use case Diagram Objects
Use case diagrams mostly consist of 3 objects: -
Actor - Actor is a use case diagram is any entity that performs a role in
one given system. This could be a person, organization or an external
system.
T.Y.B.Sc.I Page 43
T
NGO
Use Case - A Use case represents a function or an action within the

system. its drawn as an oval and named with the function.
System - System is used to define the scope of the use case and
drawn as rectangle.
There are two functions: -
Include – This represents required. Symbol of this function is

dashed arrow and arrow is labeled with the keyword
<<include>>
Extend – This represents optional and it is also shown with dashed

arrow the arrow is labeled with the keyword <<extend>>
T.Y.B.Sc.I Page 44
T
NGO
T.Y.B.Sc.I Page 45
T
NGO
4.5 SECURITY ISSUSE
Security is a vital responsibility of the library management system; while absolute security
can never be guaranteed, threats and their associated risks can be mitigated and vulnerabilities
reduced once identified and assessed. A formalized security risk management process is the
key to accomplishing this vital function.
T.Y.B.Sc.I Page 46
T
4.6 TEST CASES
Test Test Test Case Pre- Test Steps Test Data Expecte Actua Status
Case ID Scenario Conditio d Result l Pass/Fai
n Resul l
t
TC_Login_1 Verify Enter Valid Need a valid 1. Enter Valid Successful Successful Pass
Login username and username and username username login, Main login, Main
valid password to do 2. Enter Valid screen of screen of
password login Password password application application
3. Click should displayed
Login displayed
TC_Login_2 Verify Enter Valid Need a valid 1. Enter Valid No Matched No Matched Pass
Login username and username and username username Username/ Username/
invalid password to do 2. Enter Invalid Password Password
password login Password Password
3. Click
Login
TC_Login_3 Verify Enter Need a valid 1. Enter Invalid No Matched No Matched Pass
Login Invalid username and username username Username/ Username/
usernam password to do 2. Enter Valid Password Password
e and login Password Password
valid 3. Click
passwor Login
d
TC_Login_4 Verify Enter Invalid Need a valid 1. Enter Invalid No Matched No Matched Pass
Login username and username and username username Username/ Username/
invalid password to do 2. Enter Invalid Password Password
password login Password Password
3. Click
Login
T.Y.B.Sc.I Page 45
T
Admin/Student Registration
Test Case ID Test Test Case Pre- Test Test Data Expected Actual Status
Scenario Condition Steps Result Result Pass/Fail
TC_SREG_1 Verify User Enter valid Need valid 1. Enter Valid Successful, Successful, Pass
Registration name, Data to be name name, User Added User Added
Detail email, new entered 2. Enter valid Successfully Successfully
password email email,
3. Enter valid
Password password
4. Click
Sign up
TC_SREG_2 Verify Staff Enter Need Data 1. Enter Valid Email ID Email ID Pass
Registration name, to be name name, Already Already
Detail already entered 2. Enter already Registered Registered
registered Email registered
email, new 3. Enter email, valid
password Password password
4. Click
Sign up
TC_SREG_3 Verify Staff Entering - Click Nothing to Fill required Fill required Pass
Registration Nothing, Sign up enter field field
Detail Required Required
Fields are fields are
blank blank
Add Books
Test Case ID Test Test Case Pre- Test Steps Test Data Expecte Actua Status
Scenari Conditio d Result l Pass/Fai
o n Resul l
t
TC_Book_1 Verif Enter Need valid 1. Enter Valid Successful, Successful, Pass
y Valid and text and Valid Data Text and Book Added Book Added
Book correct number in Number Successfully Successfully
Detail data Data to be appropriate Data
entered fields
2. Clic
k
Submi
t
TC_Book_2 Verif Enter Need text Enter Invalid Enter Enter Pass
y invalid and invali Text Valid Data Valid Data
Book and number d Data and
Detail incorrec Data to be in Number
t data entered fields Data
TC_Book_3 Verif Entering - Click Nothing Fill Fill Pass
y Nothing, Submi to enter required required
Book Require t Required field field
Detail d Fields fields are
are blank
blank
T.Y.B.Sc.I Page 46
T
CHAPTER 5
IMPLEMENTATION
T.Y.B.Sc.I Page 47
T
5.1 Introduction: -
Implementation is the stage of the project when the theoretical design is turned out into
a working system. Thus, it can be considered to be the most critical stage in achieving a
successful new system and in giving the user, confidence that the new system will work
and be effective.
The implementation stage involves careful planning, investigation of the existing
system and it’s a constraint o implementation, designing of methods to achieve
changeover and evaluation of changeover methods.
5.2 Sample code:-

• HOME PAGE
T.Y.B.Sc.I Page 48
T
T.Y.B.Sc.I Page 49
T
• Admin home
T.Y.B.Sc.I Page 50
T
• Book request
T.Y.B.Sc.I Page 51
T
T.Y.B.Sc.I Page 52
T
• Admin
T.Y.B.Sc.I Page 53
T
T.Y.B.Sc.I Page 54
T
• Index
T.Y.B.Sc.I Page 55
T
T.Y.B.Sc.I Page 56
T
• Add book
T.Y.B.Sc.I Page 57
T
T.Y.B.Sc.I Page 58
T
T.Y.B.Sc.I Page 59
T
• Issue
T.Y.B.Sc.I Page 60
T
T.Y.B.Sc.I Page 61
T
• Request
T.Y.B.Sc.I Page 62
T
T.Y.B.Sc.I Page 63
T
• Change admin password
T.Y.B.Sc.I Page 64
T
T.Y.B.Sc.I Page 65
T
T.Y.B.Sc.I Page 66
T
• Password change
<
T.Y.B.Sc.I Page 67
T
T.Y.B.Sc.I Page 68
T
• Issue book
T.Y.B.Sc.I Page 69
T
T.Y.B.Sc.I Page 70
T
T.Y.B.Sc.I Page 71
T
• Register
T.Y.B.Sc.I Page 72
T
T.Y.B.Sc.I Page 73
T
T.Y.B.Sc.I Page 74
T
T.Y.B.Sc.I Page 75
T
CHAPTER 6
TESTING
T.Y.B.Sc.I Page 76
T
6.1 INTRODUCTION TO SYSTEM TESTING:
The purpose of testing is to discover errors. Testing is the process of trying to

discover every conceivable fault or weakness in a work product. It provides a way to
check the functionality of components, sub-assemblies, assemblies and/or a finished
product It is the process of exercising software with the intent of ensuring that the
Software system meets its requirements and user expectations and does not fail in an
unacceptable manner. There are various types of test. Each test type addresses a
specific testing requirement.
TYPES OF TESTING:
Unit testing:
Unit testing involves the design of test cases that validate that the internal
program logic is functioning properly, and that program inputs produce valid outputs.
All decision branches and internal code flow should be validated. It is the testing of
individual software units of the application .it is done after the completion of an
individual unit before integration. This is a structural testing, that relies on knowledge
of its construction and is invasive. Unit tests perform basic tests at component level and
test a specific business process, application, and/or system configuration. Unit tests
ensure that each unique path of a business process performs accurately to the
documented specifications and contains clearly defined inputs and expected results.
Integration testing:
Integration tests are designed to test integrated software components to
determine if they actually run as one program. Testing is event driven and is more
concerned with the basic outcome of screens or fields. Integration tests demonstrate
that although the components were individually satisfaction, as
T.Y.B.Sc.I Page 77
T
shown by successfully unit testing, the combination of components is correct and

consistent. Integration testing is specifically aimed at exposing the problems that arise
from the combination of components.
Functional test:
Functional tests provide systematic demonstrations that functions tested are available as
specified by the business and technical requirements, system documentation, and user
manuals.
Functional testing is center on the following items:
Organization and preparation of functional tests is focused on requirements, key

functions, or special test cases. In addition, systematic coverage pertaining to identify
T.Y.B.Sc.I Page 78
T
Business process flows; data fields, predefined processes, and successive processes
must be considered for testing. Before functional testing is complete, additional tests
are identified and the effective value of current tests is determined.
System Test:
System testing ensures that the entire integrated software system meets requirements.
It tests a configuration to ensure known and predictable results
An example of system testing is the configuration-oriented system integration test.

System testing is based on process descriptions and flows, emphasizing pre-driven
process links and integration points.
White Box Testing:
White Box Testing is a testing in which in which the software tester has
knowledge of the inner workings, structure and language of the software, or at least its
purpose. It is purpose. It is used to test areas that cannot be reached from a black box
level.
Black Box Testing:
Black Box Testing is testing the software without any knowledge of the inner
workings, structure or language of the module being tested. Black box tests, as most
other kinds of tests, must be written from a definitive source document, such as
T.Y.B.Sc.I Page 79
T
specification or requirements document, such as specification or requirements
document. It is a testing in which the software under test is outputs without considering
how the software works.
Unit Testing:
Unit testing is usually conducted as part of a combined code and unit test phase of
the software lifecycle, although it is not uncommon for coding and unit testing to be
conducted as two distinct phases. Test strategy and approach Field testing will be
performed manually and functional tests will be written in detail.
Test objectives
• All field entries must work properly.

• Pages must be activated from the identified link.
• The entry screen, messages and responses must not be delayed.
Features to be tested
• Verify that the entries are of the correct format

• No duplicate entries should be allowed
• All links should take the user to the correct page.
Integration Testing:
Software integration testing is the incremental integration testing of two or

more integrated software components on a single platform to produce failures caused
T.Y.B.Sc.I Page 80
T
by interface defects.
The task of the integration test is to check that components or software
applications, e.g. components in a software system or ± one step up ± software
applications at the company level ± interact without error.
Test Results:
All the test cases mentioned above passed successfully. No defects

encountered.
T.Y.B.Sc.I Page 81
T
Acceptance Testing:
User Acceptance Testing is a critical phase of any project and requires significant participation by the
end user. It also ensures that the system meets the functional requirements.
Test Results:
All the test cases mentioned above passed successfully. No defects encountered
T.Y.B.Sc.I Page 82
T
CHAPTER 7
SAMPLE SCREENSHOTS
T.Y.B.Sc.I Page 83
T
Desktop Screenshots: -
Issue book
Student portal login
T.Y.B.Sc.I Page 84
T
Admin functions
Student registration
T.Y.B.Sc.I Page 85
T
Request for unavailable books
Book request
T.Y.B.Sc.I Page 86
T
Add books
Admin login page
T.Y.B.Sc.I Page 87
T
Home page
Book issued by students
T.Y.B.Sc.I Page 88
T
CHAPTER 8
T.Y.B.Sc.I Page 89
T
CONCLUSION: -
Since we have created the website of library management system, it will become easier
for students to issue and request a book from the library which has access to the
internet. Without concerning any vendors or third party to get the information about the
books or the publishers.
T.Y.B.Sc.I Page 90
T
CHAPTER 9
T.Y.B.Sc.I Page 91
T
Bibliography: -
• INTRODUCING HTML 5 (book by By Bruce Lawson & Remy Sharp)
JSON and PHP (Online video lecture by educare)
T.Y.B.Sc.I Page 92
T
View publication stats

The Digital Library Mangement System

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

The Digital Library Mangement System

Uploaded by

Copyright:

Available Formats

See discussions, stats, and author profiles for this publication at: https://www.researchgate.

The Digital Library Management System 2021 : Design and Implementation of

Thesis · February 2021

The user has requested enhancement of the downloaded file.

LIBRARY MANAGEMENT SYSTEM

LIBRARY MANAGEMENT SYSTEM

BACHELOR OF SCIENCE (INFORMATION TECHNOLOGY)

GLEVIN STANISLAUS GAGA

Under the esteemed guidance of

DEPARTMENT OF INFORMATION TECHNOLOGY

PERFORM FOR THE APPROVAL OF THE PROJECT PROPOSAL

(Note: All entries of the proforma of approval should be filled up with

PNR No.: ................................ Roll no:

1. Name of the Student : GLEVIN STANISLUS GAGA

2. Title of the Project : LIBRARY MANAGEMENT SYSTEM

3. Name of the Guide : Ms.Meenakshi Dhande & Ms.Sheetal Vekhande

4. Is this your first submission? Yes No

Signature of the Student Signature of the Guide

Signature of the coordinator

DEPARTMENT OF INFORMATION TECHNOLOGY

Internal Guide Coordinator

Date: College Seal

I GLEVIN STANISLAUS GAGA STUDENT OF MODEL COLLEGE OF SCI. & COM.

THE INFORMATION SUBMITTED IS TRUE AND ORIGINAL TRUE THE BEST OF MY

Ram Gajanan Barapatre

I WISH TO EXPRESS MY SINCERE GRATITUDE TO PROJECT MR. K.S

CHAPTER 3: REQUIREMENTS AND

CHAPTER 4: SYSTEM DESIGN

CHAPTER 7 SAMPLE SCREENSHOTS

Library management system is a project which aims in developing a computerized system to

CHAPTER 1:- INTRODUCTION

In addition, report module is also included in Library Management System. If user’s

• Make all the system computerize

• Reduce time consumption

• Reduce error scope

• All system managements are automated

• Centralized database management

• Easy operations for operator of the system

• No paper work requirement

A typical computerised LMS has the following functions/modules as standard:

The scope of Online Library Management System includes:

• Create distinct product users based on their roles and permissions.

1.4 ORGANISATION OF REPORT

➢ SURVEY OF TECHNOLOGIES : In this chapter we should discuss the

➢ The chapter 5 to 7 include the IMPLEMENTATION AND TESTING

➢ IMPLEMENTATION AND TESTING: inside the implementation and testing

➢ CONCLUSIONS: The conclusions can be summarised in a fairly short chapter

➢ REFERENCES: In this topic we should discuss the bibliography and website

FRONT END – HTML

JavaScript often abbreviated as JS, is a high-level, interpreted programming language. It is a

BACK END – PHP

CHAPTER 3 :-REQUIREMENTS AND

3.1 PROBLEM DEFINATION

The problem occurred before having computerized system includes:

3.2 REQUIREMENTS SPECIFICATION

3.3 PLANNING AND SCHEDULING

The project schedule provides a graphical representation of predicted tasks, milestones,

• Define the type of schedule

July August September

Weeks Weeks Weeks

HARDWARE REQUIREMENTS  Intel core i5 2nd generation is used as a processor because

ER DIAGRAMS: A graphical model of the data needed by a system, including things

DATA FLOW DIAGRAM