Table of Contents

Chapter 1. Introduction Page No.

1) Introduction to the System 4

2) Problem Definition 4
3) Aim 4
4) Objective 4
5) Goal 5
6) Need of System 5

Chapter 2. Hardware and Software requirement

1) Introduction 7
2) System environment 7
3) Software requirement 8
4) Hardware requirements 8

Chapter 3. System Analysis

1) Purpose 9
2) Project Scope 9
3) Existing System 9
4) Proposed System 9
5) System Description 10

Page 1
 Chapter 4.Implementation issues

1) Python 12
2) HTML 13
3) Cascading style sheet(CSS) 14
4) Sqlite 15

Chapter 5. System Design

1) Introduction 21
2) Conceptual Design 22
3) ER-Diagram 23
4) Logical Design 23
5) Physical Design 24
6) Data Flow Diagram of “Library Management System” 24

Chapter 6.User Screens 25-32

Chapter 7.Coding 33-113

Chapter 8. Conclusion
7) Features of “Library Management System” 114
8) Benefits Accrued from “Library Management System” 114
9) Limitations of “Library Management System” 115

Bibliography

Page 2
 CHAPTER # 1
Introduction
Contents:

 Introduction
 Problem Definition
 Aim
 Objective
 Goal
 Need of System

Page 3
 Introduction to the System:

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

maintain all the daily work of library.
It has a facility of admin login through which the admin can monitor the whole system.
Admin modules are adding new book, view books, issue book and return book.
Overall this project of ours is being developed to help the library administration, maintain
the library in the best way possible and also reduce the human efforts.

Problem Definition:

Managing library management system may seem tricky, but this is part of user service
System (application support direct contact with user)
.

Aim:

“To manage online management of library.”

Page 4
Objective:

The main objective of the Library Management System is to manage the details of books,
students, book issue and book return. It manages all the information about book issue and
return. The project is totally built at administrative end and thus only the administrator is
guaranteed the access. The purpose of the project is to build an application program to
reduce the manual work for managing the books, Members, book issue and return. It tracks
all the details about the book issue and return, Books, Students. Fine is also auto calculated
in our project.

Page 5
 Goal:

 Provides the searching facilities based on various factors. Such as book issue and
return date, Books, Student.
 It tracks all the information of Member, Books etc
 Manage the information of Members.
 Shows the information and description of the Students, books, book issue and book
return.
 All the fields are validated and does not take invalid values
 It generates the report on Members and Books.
 Provide filter reports on Books,Students, Book issue and return
 You can easily export PDF for the Books,Students, Book issue and return
 Application also provides excel export for Books,Students, Book issue and return
 You can also export the report into csv format for Books,Students, Book issue and
return
 To increase efficiency of managing the Books,Students, Book issue and return
 It deals with monitoring the information and transactions of Books.
 Editing, adding and updating of Records is improved which results in proper resource
management of data.
 Manage the information of Books
 Integration of all records of Student.

Page 6
Need of the System:

There is always a need of a system that will perform online management of books, students,
book issue and return.
This system will reduce the manual operation required to maintain all the records. And also
generates the various reports for analysis.

Page 7
 CHAPTER #2
Hardware and
Software
Requirements

Contents:

 Software requirement
 Hardware requirements

Page 8
Software Requirements:

 Microsoft Windows 7/8/10 or Linux.

 XAMPP (MySQL, Apache, PHP).

 Notepad++ or any other text editor.

 Chrome or any other browser.

Hardware Requirements:

 Intel Processor 2.0 GHz or above.

 2 GB RAM or more.

 160 GB or more Hard Disk Drive or above.

Page 9
 CHAPTER # 3
System Analysis

Contents:

 Purpose
 Project Scope
 Existing System
 Proposed System
 System Overview

Page 10
Purpose:

The purpose of Library Management System is to automate the existing manual system by the help
of computerized equipments and full fledged computer software, fulfilling their requirements, so
that their valuable data/information can be stored for a longer period with easy accessing and
manipulation of the same.
This project also helps in administrative work such as keep information of book issue and return.

Project Scope:

The project has a wide scope, as it is not intended to a particular organization. This project is
going to develop generic software, which can be applied by any businesses organization.
More over it provides facility to its users. Also the software is going to provide a huge
amount of summary data.

Proposed System:

The Online Library Management system is available in the market that can serve librarians in
schools and colleges to manage book issue and book return.

Page 11
System Overview:

Online library Management System has one module–

 Admin

Admin Features
 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

Page 12
 CHAPTER # 4
Implementation issues

Python

Python is a widely used general-purpose, high level programming language. It was initially
designed by Guido van Rossum in 1991 and developed by Python Software Foundation. It was
mainly developed for emphasis on code readability, and its syntax allows programmers to express
concepts in fewer lines of code.
Python is a programming language that lets you work quickly and integrate systems more
efficiently.
Python is dynamically typed and garbage-collected. It supports multiple programming paradigms,
including procedural, object-oriented, and functional programming. Python is often described as a
"batteries included" language due to its comprehensive standard library.

Page 13
HTML

HTML (Hypertext Markup Language) is the set of markup symbols or codes inserted in a file
intended for display on a World Wide Web browser page. The markup tells the Web browser how to
display a Web page's words and images for the user. Each individual markup code is referred to as
an element (but many people also refer to it as a tag). Some elements come in pairs that indicate
when some display effect is to begin and when it is to end.

Page 14
CASCADING STYLE SHEET (CSS)

Cascading Style Sheets (CSS) are a collection of rules we use to define and modify web pages.
CSS are similar to styles in Word. CSS allow Web designers to have much more control over their
pages look and layout. For instance, you could create a style that defines the body text to be
Verdana, 10 point. Later on, you may easily change the body text to Times New Roman, 12 point by
just changing the rule in the CSS. Instead of having to change the font on each page of your
website, all you need to do is redefine the style on the style sheet, and it will instantly change on all
of the pages that the style sheet has been applied to. With HTML styles, the font change would be
applied to each instance of that font and have to be changed in each spot.

CSS can control the placement of text and objects on your pages as well as the look of those
objects.

HTML information creates the objects (or gives objects meaning), but styles describe how the
objects should appear. The HTML gives your page structure, while the CSS creates the
“presentation”. An external CSS is really just a text file with a .css extension. These files can be
created with Dreamweaver, a CSS editor, or even Notepad.

The best practice is to design your web page on paper first so you know where you will want to use
styles on your page. Then you can create the styles and apply them to your page.

Page 15
Javascript

JavaScript is a programming language commonly used in web development. It was originally devel-
oped by Netscape as a means to add dynamic and interactive elements to websites. While
JavaScript is influenced byJava, the syntax is more similar to C and is based on ECMAScript, a
scripting language developed by Sun Microsystems.
JavaScript is a client-side scripting language, which means the source code is processed by the
client's web browser rather than on the web server. This means JavaScript functions can run after a
webpage has loaded without COMMUNICATING with the server. For example, a JavaScript func-
tion may check a web form before it is submitted to make sure all the required fields have been
filled out. The JavaScript code can produce an error message before any information is actually
transmitted to the server.
Like server-side scripting languages, such as PHP and ASP, JavaScript code can be inserted any-
where within the HTML of a webpage. However, only the output of server-side code is displayed in
the HTML, while JavaScript code remains fully visible in the source of the webpage. It can also be
referenced in a separate .JS file, which may also be viewed in a browser.

Page 16
Django

Django is a web application framework written in Python programming language. It is based on

MVT (Model View Template) design pattern. The Django is very demanding due to its rapid devel-
opment feature. It takes less time to build application after collecting client requirement.

This framework uses a famous tag line: The web framework for perfectionists with deadlines.

Page 17
 CHAPTER # 5
System Design

Contents:
 Use case diagram
 Class Diagram
 Sequence Diagram
 Data flow diagram

Page 18
Use Case Diagram:

 Use case diagram consists of use cases and actors and shows the interaction between
them. The key points are:

 The main purpose is to show the interaction between the use cases and the actor.

 To represent the system requirement from user’s perspective.

 The use cases are the functions that are to be performed in the module.

Page 19
Sequence Diagram For Administrator:-

Login Application Database

Login
:Request

:Validate()
:executeQuery()

Administrator Response
Show Result

Success:hide() Failed:show()

Fig.5.4

Page 20
 Sequence Diagram For User:-

Login Application Database

Login
:Request

:Validate()
User
:executeQuery()

Response
Show Result

Success:hide()
Failed:show()

Page 21
 Fig.5.5

Data Flow Diagram

A Data Flow Diagram (DFD) is a graphical representation of the "flow" of data through an
Information System. A data flow diagram can also be used for the visualization of Data Processing.
It is common practice for a designer to draw a context-level DFD first which shows the interaction
between the system and outside entities. This context-level DFD is then "exploded" to show more
detail of the system being modeled.

A DFD represents flow of data through a system. Data flow diagrams are commonly used during
problem analysis. It views a system as a function that transforms the input into desired output. A
DFD shows movement of data through the different transformations or processes in the system.

Dataflow diagrams can be used to provide the end user with a physical idea of where the data they
input ultimately has an effect upon the structure of the whole system from order to dispatch to re-
stock how any system is developed can be determined through a dataflow diagram. The appropriate
register saved in database and maintained by appropriate authorities.

Data Flow Diagram Notation

Function

File/Database

Input/output

Page 22
 Flow

DFD Diagram – Zero Level

Page 23
DFD Diagram – First Level

Page 24
Entity Relationship Diagrams (ER-Diagrams):

An entity-relationship (ER) diagram is a specialized graphic that illustrates the interrelationships

between entities in a database. ER diagrams often use symbols to represent three different types of
information. Boxes are commonly used to represent entities. Diamonds are normally used to
represent relationships and ovals are used to represent attributes

An entity-relationship model (ERM) in software engineering is an abstract and conceptual

representation of data. Entity-relationship modeling is a relational schema database modeling
method, used to produce a type of conceptual schema or semantic data model of a system, often a
relational database, and its requirements in a top-down fashion.

Symbols used in this E-R Diagram:

Entity: Entity is a “thing” in the real world with an independent existence. An entity may be an
object with a physical existence such as person, car or employee. Entity symbol is as follows

Attribute: Attribute is a particular property that describes the entity. Attribute symbol is

Relationship: Relationship will be several implicit relationships among various entity types
whenever an attribute of one entity refers to another entity type some relationship exits.
Relationship symbol is:

Key attributes: An entity type usually has an attribute whose values are distinct for each
Page 25
individual entity in the collection. Such an attribute is called key attribute. Key attribute symbol is
as follows

ENTITY RELATIONSHIP(ER) DIAGRAM

Page 26
Class Diagram

Page 27
CHAPTER # 6
Output screens
HOME PAGE

Page 28
ADMIN LOGIN PAGE

Page 29
ADD BOOK PAGE

Page 30
VIEW BOOKS PAGE

Page 31
ISSUE NEW BOOK

Page 32
VIEW FINE PAGE CODING

Page 33
{% extends 'navigation.html' %}
{% load static %}
{% block body %}
<center><div class="container" style="background-color:rgb(240, 240,
240);width:600px;border-radius:4%;margin-top:200px;margin-left:440px;height:200px"> <i
class="fa fa-exclamation-triangle fa-5x" aria-hidden="true" style="color:red;margin-
top:20px"></i>
<h3 style="color:Darkslategrey;background-color:rgb(240, 240, 240);">You Have
{{late}} Days Late</h3>
<h3 font-color="white" style="color:Darkslategrey;background-color:rgb(240, 240,
240);">Your Fine is : {{fine}}</h3></div></center>

{% endblock %}

Page 34
 CHAPTER # 8
Advantages & Limitations

Advantages of “Online Library Management System”:

“Online Library Management System” provides various features, which

complement the information system and increase the productivity of the system.
These features make the system easily usable and convenient. Some of the important
features included are listed as follows:

 Intelligent User Forms Design

 Data access and manipulation through same forms
 Access to most required information
 Data Security
 Restrictive data access, as per login assigned only.
 Organized and structured storage of facts.
 Strategic Planning made easy.
 No decay of old Records.
 Exact financial position of the Business.

Limitations of “Online Library Management System”:

Page 35
Besides the above achievements and the successful completion of the project, we still
feel the project has some limitations, listed as below:

1. It is not a large scale system.

2. Only limited information provided by this system.
3. Since it is an online project, customers need internet connection.
4. People who are not familiar with computers can’t use this software.

Page 36
 CHAPTER # 8
Future Scope

FUTURE SCOPE

This web application involves almost all the features of the online booking. The future
implementation will be online help for the students and chatting with website administrator.

CONCLUSION

The project entitled “Online Library Management System” is developed using HTML, CSS and
Bootstrap as front end and Python , sqlite database in back end to computerize the process of online
management of books, issued and returned books. This project covers only the basic features
required.

Page 37
 Bibliography
BIBLIOGRAPHY

 Wikipedia

 https://www.geeksforgeeks.org/python-django/

 https://www.javatpoint.com

 https://www.python.org/

 https://www.tutorialspoint/

 REFERENCE BOOKS

Two scoops of Django for 1.11 by Daniel Greenfeld’s and Audrey Greenfield

Lightweight Django by Elman and Mark Lavin

Page 38