CHAPTER 1

INTRODUCTION

1.1 Introduction to Project

A library is a collection of sources of information and similar resources, made accessible to the
students and college faculty. Library‟s collection includes books, journals, thesis, e-books,
magazines, projects etc. Library is a vital learning resource in an institution of higher education.
IT offers continuously updated information on a variety of subjects. Library also contributes to
the development of student into a healthy and thinking personality. The need to use library
increasingly increased. But, the cost of text books and journals has grown enormously.
As the usage of library is increased rapidly and manage the library‟s different operations
manually is become very complicated. To reduce the complications of managing the library
system institution should automate the library. Automation of library means all operations done
computerized.
“Automation of library will give them altogether a new life. Library becomes tremendous
potential. Computerized cataloguing enormously enhances access to books and magazines etc.”
Students can easily search any book, project and thesis. Searching any book manually in library
is very time consuming. But searching any book online is very less time consuming. All
searching related books shown after searching. Sometimes some books are not available in the
library then just in few seconds' system show you that book is not available in the library. In
other hands if students search any book which is not available in the library is only the wastage
of precious time of student.
Our project LIBRARY AUTOMATION is based on managing the department library‟s
operation computerized to reduce the complications which arise from managing library‟s
operations manually. Students/teachers can easily search any book, thesis, projects, projects
reports, CDs, DVDs etc. There is a recommender system which provides the facility searching
the book based on keywords. Students/teachers can search by type the writer name, book title,
thesis title, area of thesis and many more options are available for the ease of students/ teachers.
Students can only check the books, thesis, projects etc. and overall rights/privileges given to the
admin. Admin enter the books and other sources. We use MYSQLi database at back end to

~1~
store the all information about books, thesis and projects. At front end we use PHP, HTML,
and CSS to develop the system.

1.2 Project Category

Department Library system falls under the institute automation category. It serves better
performance by replacing semi-automated system with an automated system.

1.3 Objectives

1. Design interface for entering book detail, thesis and projects details. Catering needs of
the department.
2. Construct a search facility for searching the book, thesis, projects.
3. Construct module for book issue and generate reports accordingly.
4. Developing a book recommender system based on keywords.

1.4 Problem Formulation

The problem in the previous system was to maintain the all record manually. The librarian has
to fill the information of every teacher who comes to the department library all by
himself/herself. The proposed solution is to maintain the graphical reports as well as maintain
all information about new coming books, existing books, thesis and projects. In manually
system there is a big amount of data that maintained every day and it is very difficult to
maintain all this day by day. It is very time consuming process. The scope of this project will be
basic redundancy control and also the automation of the system which will affect in less
wastage of time.

1.5 Existing System

In our existing system all the transaction of books are done manually, So taking more time for
a transactions 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. Fast report generation is not possible.

~2~
Therefore, there is a need for automation of current system to reduce manual work and to
improve overall performance.

1.6 Proposed System

Proposed system is an automated Library Management System. Through our software librarian
can add members, add books, search members, search books, update information, edit
information, borrow and return books in quick time.
1.7 Unique Features of the System
1. User friendly interface
2. Fast access to database
3. Less error
4. More Storage Capacity
5. Search facility

~3~
 CHAPTER 2
REQUIREMENT ANALYSIS AND SYSTEM SPECIFICATION

2.1 Feasibility Study

Feasibility study is a test of system proposal according to its workability, impact of the
organizations, ability to meet needs and effective use of the resources. In feasibility study we
are check that is the proposed system is feasible or not. For this we do feasibility study
according to following criteria:-
1. Technical Feasibility
2. Economic Feasibility
3. Schedule Feasibility
4. Operational Feasibility

Technical Feasibility
In this we study the resource availability means we check is the hardware or software needed
for the completion of project is available in the market and is that work on our this project. The
resources related to our project are easily available in the market. We have the knowledge about
the software and hardware which is used in our project. Technologies that will be used for
developing and implementing this project are free of cost and are technical feasible according
to the latest standards available.

Economic Feasibility
In this we check the cost and benefits associated with the system. The cost of our project is less
and cost can easily manage. Cost of project do not exceed from expected cost. In this project
we are using open-source technologies such as Xampp platform, MYSQLi, Sublime3, and
Php5, therefore economic factors such as funds are not going to be a problem.

Schedule Feasibility
Time is the important consideration in the development of project. In this we study is the
project will be completed in given deadlines. Is our project is feasible according to time or not
or it is very big and can‟t be completed in the given time. Our project is not too big so it can be
completed in given time.

~4~
Operational Feasibility
The operational feasibility assessment focuses on the degree to which the proposed system fits
in with the existing business environment. Our project can easily manage in the existing system
by providing guidance to the staff. The project proposed will have a user friendly interface; a
naive user will be able to understand the user interface in seconds. Also, it will reduce most of
the manual work of office.

2.2 Software Requirement Specification

Data Requirement

Data about new coming books, existing books, thesis and projects are required to maintain the
proposed system effectively. Based on these records reports are generated.

Functional Requirement

Functional requirements of department Library will include software requirements, hardware

requirements.

Software requirements:
1. Php5, HTML5, CSS, Bootstrap
2. MYSQLi Database
3. XAMPP
4. Sublime Text Editor

Hardware requirements:
1. Windows 2010
2. Intel i3 Processor or Above
3. 500 GB Hard Disk
4. 2 GB Ram

Maintainability requirement
This system will require up-to-date database records to generate graphical reports for better
results and conclusions, else reports will be generated based on past records and will lead to

~5~
false conclusions. Also when system will be able to generate graphical reports, it will need
updated graphical libraries every time or after some time.

2.3 Expected Hurdles

In future, this system will generate graphical reports based on the records available in the
database. We may face several hurdles implementing this module because to generate graphical
reports from CSV‟s needs knowledge of graphical libraries and these libraries are updated on
daily basis.

2.4 SDLC model to be used

Preliminary
investigation
System
requirement
System
design
System
development
System
testing

Figure 2.1 SDLC model

Preliminary Investigation
The first step is identifying need of a new system. This will include determine whether a
business problem or opportunity exists, conducting a feasibility study to determine if the
proposed solution is cost effective, and developing a project plan. This process may involve
end users who come up with an idea for improving their work.

System Requirement
Requirements analysis is the process of analysing the information needs of the end
users, the organizational environment and any systems presently being used thereby developing

~6~
the functional requirements of a system that can meet the needs of the users. Also, the
requirements should be recorded in a document, email, user interface.

Design of a System
After the requirements have been determined, the necessary specification for the hardware,
software, people, data resources and the information products that will satisfy the functional
requirements of the proposed system can be determined. The design will serve as a blue
print for the systems and helps to detect these problems before these errors or problems are
built into the final system.

Development of Software
Coding and debugging is the act of creating the final system. Software developed may use
purchased software or they may create new custom designed programs depending upon the
cost and time available. Documentation is essential to test the program and carry out
maintenance.

System Testing
The system must be tested to evaluate its actual functionality. In relation to expected or
intended functionality. Some other issues to consider during this stage would be converting old
data into the new system and training employees to use the new system. End users will be keys
in determining whether developed system meets the intended requirements, and the extent to
which the system is actually used.

~7~
 CHAPTER 3
SYSTEM DESIGN

Systems design is the process or art of defining the architecture, components, modules,
interfaces, and data for a system to satisfy specified requirements. One could see it as the
application of systems theory to product development. There is some overlap with the
disciplines of systems analysis, systems architecture and systems engineering.

External design
External design consists of conceiving, planning out and specifying the externally observable
characteristics of the software product. These characteristics include user displays or user
interface forms and the report formats, external data sources and the functional characteristics,
performance requirements etc. External design begins during the analysis phase and continues
into the design phase.

Logical design
The logical design of a system pertains to an abstract representation of the data flows, inputs
and outputs of the system. This is often conducted via modelling, which involves a simplistic
(and sometimes graphical) representation of an actual system. In the context of systems design,
modelling can undertake the following forms, including:
– Data flow diagrams
– Entity Relationship Diagrams

Physical design
The physical design relates to the actual input and output processes of the system. This is laid
down in terms of how data is input into a system, how it is verified/authenticate, how it is
processed, and how it is displayed as output.

3.1 Design Approach

Function oriented design approach is comprised of many smaller sub-systems known as
functions. This design mechanism divides the whole system into smaller functions, which

~8~
provides means of abstraction by concealing the information and their operation. These
functional modules can share information among themselves by means of information passing
and using information available globally.
Design approach for department library system is function-oriented. Basic emphasis is on
replacing existing semi-automated system with an automated system. Following a function
oriented design approach this system is divided into many smaller sub-systems like admin,
teacher, report creations, etc. These modules can share information with each other.

3.2 System Design

Data Flow Diagram (DFDs)
A data flow diagram is a graphical representation of the flow of data. The purpose of DFD is to
clarify system requirements and identify major transformations that will become programs in
system design. These diagrams help to understand the basic working of the system. It helps to
make and recognize various parts and their inter relationships. It is a way of expressing system
requirements in a graphical form, this leads to a modular design. It is also known as bubble
chart. A DFD consists of bubbles joined by lines. The bubbles represent data transformations
and the lines represent data flows in the system.
Following is the system design representation of department library system using flowcharts.
The system design is broken down into three parts i.e. admin, librarian and teacher.

Admin
Admin is the person who will login to the system and upload the books in the database, keep all
record about issuing and return books. Admin will generate graphical reports.

~9~
Data Flow Diagram (Admin)

Entering books,
thesis, projects

Search Facility

Admin Login
Add Teacher

Generate
reports

Figure 3.1 System design (Admin)

Data Flow Diagram (Librarian)

Search
facility

Librarian Login
Issue book

Return
book

Figure 3.2 System design (librarian)

~ 10 ~
3.3 Database Design
3.3.1 ER Diagram
An entity relationship (E-R) diagram is a technique that we use as a database designer to
represent the logical structure of the database of a system. It is a diagrammatic representation of
the database design. In a software development environment, a system analyst will interview a
client for all the project specifications, draw the E-R diagram and get it verified by the client. If
the diagram is as per requirements and fulfils all the needs of the client, creation of the database
and tables will follow. An E-R diagram is like a blue print for the database.

Guidelines for drawing E-R diagram: when gathering information, you have to:
1. Identify the entities in the system.
2. Identify the attributes of each entity.
3. Identify the relationships between the entities.

E-R diagram is used to represent the following three elements:

1. Entities
2. Attributes
3. Relationships

Symbols used in E-R diagram:

S
Entity

Relationship

~ 11 ~
Attribute

Primary Key Attribute

Many to many relationships

One to one relationship

Many to one relationship

~ 12 ~
 E-R diagram for Department Library Automation:

Library

Contain
Id Author

Acc. no
Publisher
Books
Title

Id Issue User_name

Designation Full_name

Teacher

Return Issue

Book_name
Status of return Status of issue

Issue date

Teacher_name Book_name
Teacher_name

Issue date

Figure 3.3: ER Diagram

~ 13 ~
3.4 Methodology
A methodology is a model, which project managers employ for the design, planning,
implementation and achievement of their project objectives. There are different project
management methodologies to benefit different projects.
A software development methodology or system development methodology in software
engineering is a framework that is used to structure, plan and control the process of developing
an information system.
Our Project is divided into modules and plan according to the following steps:

a) Database: First we will create the database of project which includes different tables of
every module.
b) Homepage: It will display all the book categories. Here Login panel is available for
admin and librarian.
c) Login Module: Here we will create the login interface of librarian and admin.
d) Librarian Module: Librarian can login by unique user id and password. After that they
can issue books of different subjects.
e) Book issue Module: Teachers of the department can easily get the books issued that
they want.
f) Admin Module: Admin can track and manage system. Admin can upload books, delete
books, add teacher details and keep track of all the books issued to the teachers of the
department.
g) Thesis and Projects Module: Teachers can also search thesis and projects in the library
and they can download the file/PDF which they want to download.
h) Design: Here we will design the GUI of our project.

~ 14 ~
 CHAPTER 4
IMPLEMENTATION, TESTING AND MAINTENANCE

4.1 Introduction to Languages, IDE’s, Tools and Technologies used for

Implementation
4.1.1 PHP
PHP is a server-side scripting language designed primarily for web development but also used
as a general-purpose programming language. Originally created by Rasmus Leadoff in 1994,
the PHP reference implementation is now produced by The PHP Development Team. PHP
originally stood for Personal Home Page, but it now stands for the recursive acronym PHP:
Hypertext Pre-processor.
PHP code may be embedded into HTML or HTML5 mark up, or it can be 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 the web server
or as a Common Gateway Interface (CGI) executable. The web server software combines the
results of the interpreted and executed PHP code, which may be any type of data, including
images, with the generated web page. PHP code may also be executed with a command-line
interface (CLI) and can be used to implement stand-alone graphical applications.
4.1.2 HTML
Hypertext Mark-up Language (HTML) is the standard mark-up 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.[2] Web browsers receive HTML
documents from a web server or from local storage and render them into multimedia web
pages. HTML describes the structure of a web page semantically and originally included cues
for the appearance of the document.
HTML elements are the building blocks of HTML pages. With HTML constructs, images and
other objects, such as interactive forms, may be embedded into the rendered page. It provides a
means to create structured documents by denoting structural semantics for text such as
headings, paragraphs, lists, links, quotes and other items. HTML elements are delineated by
tags, written using angle brackets. Tags such as <img/> and <input/> introduce content into the
page directly. Others such as <p>...</p> surround and provide information about document text

~ 15 ~
and may include other tags as sub-elements. Browsers do not display the HTML tags, but use
them to interpret the content of the page.
4.1.3 Sublime
Text is a proprietary cross-platform source code editor with a Python application programming
interface (API). It natively supports many programming languages and mark-up languages, and
functions can be added by users with plug-in, typically community-built and maintained under
free-software licenses.

4.2 Coding standards of Language used

4.2.1 Coding standards of PHP
i. Use two spaces for indentation. Don't use tab literal characters.
ii. Use UNIX line breaks ("\n"), not MS DOS ("\r\n") or OS9 ("\r").
iii. Put a space after control keywords like if and for.
iv. Put a space after commas in argument lists.
v. Put a space around operators like =, <, etc.
vi. Don't put spaces after function names.
vii. Parentheses should hug their contents.
viii. Generally, prefer to wrap code at 80 columns.
ix. Use " <? Php", not the "<?" short form. Omit the closing "?>" tag.
x. Prefer casts like (string) to casting functions like strval ().
xi. Prefer type checks like $v === null to type functions like is null ().
xii. Avoid all crazy alternate forms of language constructs like "end while" and"<>".
xiii. Always put braces around conditional and loop blocks.
xiv. Name variables and functions using lowercase_with_underscores.
xv. Name classes using UpperCamelCase.
xvi. Name methods and properties using lowerCamelCase.
xvii. Use uppercase for common acronyms like ID and HTML.
xviii. Name constants using UPPERCASE.
xix. Write true, false and null in lowercase.
xx. Do not use "#" (shell-style) comments.
xxi. Prefer "//" comments inside function and method bodies.

~ 16 ~
4.2.2 Coding standards of HTML

Validation: All HTML pages should be verified against the W3C validator to ensure that the
mark-up is well formed. This in and of itself is not directly indicative of good code, but it helps
to weed out problems that are able to be tested via automation. It is no substitute for manual
code review.

Self-closing Elements: All tags must be properly closed. For tags that can wrap nodes such as
text or other elements, termination is a trivial enough task. For tags that are self-closing, the
forward slash should have exactly one space preceding it.

Attributes and Tags: All tags and attributes must be written in lowercase. Additionally,
attribute values should be lowercase when the purpose of the text therein is only to be
interpreted by machines. For instances in which the data needs to be human readable, proper
title capitalization should be followed.

Quotes: According to the W3C specifications for XHTML, all attributes must have a value,
and must use double- or single-quotes (source). The following are examples of proper and
improper usage of quotes and attribute/value pairs.

Indentation: As with PHP, HTML indentation should always reflect logical structure. Use tabs
and not spaces. When mixing PHP and HTML together, indent PHP blocks to match the
surrounding HTML code. Closing PHP blocks should match the same indentation level as the
opening block.

4.3 Testing Techniques and Test Plans

Testing techniques to be followed for this project are as follows:
1. Functionality Testing
2. Usability testing
3. Interface testing
4. Compatibility testing
5. Performance testing
6. Security testing
~ 17 ~
Functionality Testing
Test for – all the links in web pages, database connection, forms used in the web pages for
submitting or getting information from user, cookie testing.

Usability testing
Web site should be easy to use. Instructions should be provided clearly. Check if the provided
instructions are correct meaning whether they satisfy the purpose. Main menu should be
provided on each page. It should be consistent.

Interface Testing
The main interfaces are:
 Web server and application server interface
 Application server and database server interface

Check if all the interactions between these servers are executed properly. Errors are handled
properly. If database or web server returns any error message for any query by application
server, then application server should catch and display these error messages appropriately to
users. Check what happens if user interrupts any transaction in-between? Check what happens
if connection to web server is reset in between?

Compatibility Testing

Compatibility of your web site is very important testing aspect. See which compatibility test is
to be executed:

 Browser compatibility
 Operating system compatibility
 Mobile browsing
 Printing options

Performance Testing
Web application should sustain to heavy load. Web performance testing should include:
 Web Load Testing

~ 18 ~
  Web Stress Testing

Security Testing
 Test by pasting internal URL directly into browser address bar without login. Internal
pages should not open.
 If you are logged in using username and password and browsing internal pages, then try
changing URL options directly, i.e., If you are checking some publisher site statistics
with publisher site ID= 123. Try directly changing the URL site ID parameter to
different site ID which is not related to log in user. Access should be denied for this user
to view others stats.
 Try some invalid inputs in input fields like login username, password and input text
boxes. Check the system reaction on all invalid inputs.
 Web directories or files should not be accessible directly unless given download option.
 Test the CAPTCHA for automates scripts logins.
 Test if SSL is used for security measures. If used, proper message should get displayed
when user switches from non-secure http:// pages to secure https:// pages and vice versa.
 All transactions, error messages, security breach attempts should get logged in log files
somewhere on web server.

4.4 Project Scheduling

4.4.1 GANTT CHART
A Gantt chart, commonly used in project management, is one of the most popular and useful
way of showing activities (tasks or events) displayed against time. On the left of the chart is a
list of the activities and along the top is a suitable time scale. Each activity is represented by a
bar; the position and length of the bar reflects the start date, duration and end date of the
activity.

~ 19 ~
Figure 4.1: Project Planning

Figure 4.2: Gantt chart

~ 20 ~
 CHAPTER 5
RESULTS AND DISCUSSIONS

5.1 User Interface Representation

To implement this project we have included many pages. In our project there are two are two
types of login: one for the admin and other for the librarian.
5.1.1 Admin Section
5.1.1.1 Login Page
Admin page of admin section contains the login module, here the admin has to fill his/her
username and password and then click the login button. If the username and password is
correct then only the next section opens.

5.1.1.2 Add Books, Thesis, Project Page

This is the main page of the admin section, here admin can add, delete, update the
information regarding to books, thesis and project. If the admin don‟t want to choose any
of the option then he/she may simply click on the logout button.

5.1.1.3 Add Teacher

Admin can add teacher and view the teacher detail.

5.1.2 Librarian Section

5.1.2.1 Login Page
Login page of librarian section contains the login module, here the librarian has to fill
his/her username and password and then click the login button after that the main page of
librarian section opens.

5.1.2.2 Main Page

This is the main page of the librarian section which has various options in the menu bar
like: issue books, search facility, view all books etc.

5.1.2.3 Upload Books Page

By choosing upload book option in the menu bar, librarian can easily upload a new book by

~ 21 ~
filling the details like: author, publisher, edition and then click on the submit button this
may simply upload the book.

5.1.2.4 List of Books Page

This page contains the list of all the books uploaded by the admin along with their
important details like: author, publisher, edition, type. Admin can also view the uploaded
book by clicking the view option and can also delete any of the books.

5.1.2.5 Book Issue Page

In this page librarian can issue the book to any teacher by just selecting the book and the
teacher and then click on the issue button.

5.1.2.6 Book Return Page

This page contains the list of books along with their details like: status, which shows
whether the book is available or issued and if any book is issued then on which date it is
issued and to which teacher. There is also an option of return, by clicking that return the
book gets returned.

5.1.2.7 Change Password Page

Here librarian can easily change his/her password by simply filling the new password after
that click on the submit button.

~ 22 ~
5.2 Snapshots of System
5.2.1 Home Page

Figure 5.1: Home Page

5.2.2 Admin Login

Figure 5.2: Admin Page

Index page of admin section contains the login module, here the admin has to fill his/her
username and password and then click the login button after that the main page of admin
section opens.

~ 23 ~
5.2.3 Admin Main Page

Figure 5.3: Admin Main Page

This is the main page of the admin section which has various options like: Add books, add
thesis, add projects, add teachers, edit librarian, contacts and report. Here admin can easily
see as well as manage the records of teachers and books by choosing the options available
according to their needs.

~ 24 ~
5.2.4 Book Entry

Figure 5.4: Book Entry

In this page admin add the books to the library by filling the information like account_no, title,
author, publisher about the books.

~ 25 ~
5.2.5 All Books

Figure 5.5: All Books

This page contains the list of all the books uploaded by the admin along with their important
details like: author, publisher, title and issue to which teacher and when. Admin can also view
the uploaded book by clicking the view option.

~ 26 ~
5.2.6 Projects Entry

Figure 5.6: Projects Entry

Here the admin can easily enter the projects by simply choosing the title, student name,
guided by, session year, session month etc. and filling the description and then after
choosing the type of file, click on the submit button.

~ 27 ~
5.2.7 All Projects

Figure 5.7: All Projects

This page contains the list of all the projects uploaded by the admin along with their important
details like: branch code, course code, title, student name, roll no, guided by etc. and PDF file is
attached here if anybody want to download then he/she can.

~ 28 ~
5.2.8 Thesis Entry

Figure 5.8: Thesis Entry

Here the admin can easily enter the thesis by simply choosing the title, student name,
guided by, session year, session month etc. and filling the description and then after
choosing the type of file, click on the submit button.

~ 29 ~
5.2.9 All Thesis

Figure 5.9: All Thesis

This page contains the list of the entire thesis uploaded by the admin along with their important
details like: branch code, course code, title, student name, roll no, guided by etc. and PDF file is
attached here if anybody want to download then He/She can.

~ 30 ~
5.2.10 Edit Librarian

Figure 5.10: Edit Librarian

In this page admin can change the librarian by resetting the username and password.

5.2.11 Librarian Main Page

Figure 5.11: Librarian Mane Page

Librarian has the authority to issue the books to the teachers. He/she can also see all the books
that are available in the library and also check that which book is issue to which teacher.

~ 31 ~
5.2.12 Issue Book

Figure 5.12: Issue Book

In this module librarian issue the books to the teachers by just simply selecting the book and
teacher.

5.2.13 Return Book

Figure 5.13: Return Book

In this module librarian return the book.

~ 32 ~
5.2.14 Book Search

Figure 5.14: Book Search

Admin and librarian can search the books by using the search facility. All results are shown
here.
5.2.15 Thesis Search

Figure 5.15: Thesis Search

~ 33 ~
Admin and librarian can search the thesis by using the search facility. All results are shown
here.

5.2.16 Project Search

Figure 5.16: Project Search

Admin and librarian can search the projects by using the search facility. All results are shown
here.

5.2.17 Contact Us

Figure 5.17: Contact Us

~ 34 ~
5.3 Database Snapshots
Table 5.3.1: Admin Login

Field Name Data type

Id Bigint(20)

User_name Varchar(30)

password Varchar(30)

role Enum(„admin‟,‟lib‟)

Table 5.3.2: Books

Field Name Data type

S_no. Int(10)

Account_no. Varchar(10)

Author Text

Title Varchar(50)

Publisher Varchar(50)

Issue_date Datetime

Issue_to Int(11)

status Enum(„0‟,‟1‟)

~ 35 ~
Table 5.3.3: Projects

Field Name Data type

Branch_code Int(10)

Course_code Int(10)

Title Text

File_name Text

Student_name Text

Univ_roll_no Int(10)

Guided_by Text

Session_month Text

Session_year Int(10)

Area Text

File Varchar(100)

Type Varchar(100)

Size Int(11)

~ 36 ~
Table 5.3.4: Thesis

Field Name Datatype

Branch_code Int(10)

Course_code Int(10)

Title Text

File_name Text

Student_name Text

Univ_roll_no Int(10)

Guided_by Text

Session_month Text

Session_year Int(10)

Area Text

File Varchar(100)

Type Varchar(100)

Size Int(11)

~ 37 ~
Table 5.3.5: Teacher

Field Name Datatype

Id Bigint(20)
Teacher_username Varchar(50)
Designation Varchar(50)
Teacher_full_name text

Table 5.3.6: Contact Us

Field Name Datatype

Name Text
Email_id Varchar(30)
Subject Varchar(30)
Message Varchar(500)

~ 38 ~
 CHAPTER 6
CONCLUSION AND FUTURE SCOPE

6.1 CONCLUSION
This project that we undertook was truly a very rewarding experience for us in more than one
way. It helped us enhance our skills on the personal front. We feel extremely satisfied we have
managed the Project with Equal Contribution from all the members. We think that almost all
the requirements of the User have meet satisfaction. This web system is fully Functional and
Features has been added, working nicely.

6.2 FUTURE SCOPE

In future, we will try to add feature that if any teacher requests for a particular book which is
already issued to any other teacher then that teacher will automatically receive a message that
the book is not available and also display the name of the teacher to which that requested book
is already issued.
In future it can has be a facility of teacher‟s login where teachers can add lectures notes and
also give necessary suggestion to library and also add info about workshops or events
happening in our college or nearby college in the online notice board.
There is a future scope of this facility that many more features such as online lectures video
tutorials can be added by teachers as well as online assignments submission facility can be
added to this project thus making it more interactive more user friendly and project which
fulfils each users need in the best way possible.

~ 39 ~
 BIBLIOGRAPHY

[1] Robin Nixon, Learning PHP, MYSQL, $ Java Script with jquery, CSS and HTML5.: O'
Reilly, 2015.

[2] Prabhakar Kumar Rahul Kumar Rajat Singh Vikram Pratap Singh, "LIBRARY
MANAGEMENT SYSTEM ," School of Engineering Cochin University of Science &
Technology , Kochi, Project Report 2014.

[3] Shraddha Panwar, Vijay Vaishnav Bhupendra, "Online Library Management System,"
International School of Informatics and Management, Jaipur, Project Report.

[4] Mario Lurig, PHP reference:Beginner to intermediate PHP5, First Edition ed.: ISBN:978-
14357-1590-5.

[5] (2017, september) getbootstrap. [Online].

https://getbootstrap.com/docs/4.0/components/alerts

~ 40 ~