A Final Project Proposal Report on

ONLINE LIBRARY MANAGEMENT SYSTEM

Submitted in Partial Fulfillment of the Requirements for

The Degree of

BACHELOR OF ENGINEERING IN INFORMATION TECHNOLOGY

Under Pokhara University

Submitted by:

Naina Maharjan, Roll No. 15485

Alisha Roy, Roll No.15451

Under the supervision of

Date: 11/Jan/2018

Department of Information Technology Engineering

NEPAL COLLEGE OF INFORMATION

TECHNOLOGY
Balkumari, Lalitpur, Nepal
ACKNOWLEDGEMENT

We are thankful to Nepal College of Information and Technology for providing us the chance to
build software during the minor project and managing the resources and specialists to assist our
project. We acknowledge the effort of those who have contributed significantly to our project.
Without the support, valuable suggestions and contributions from a number of individual, it
would have not been possible for the completion of this project within the duration.

We are indebted to Head Coordinator Dr. Roshan Chitrakar, who is our actual supporter for this
action they have managed everything a student need.

We are grateful to our Er.Niraj Maharjan, who will be the part of our project team with their
assistance, advices and suggestions.

1
ABSTRACT

To fulfill these purposes this study adopts a design strategy which contains theoretical and
empirical parts. This study chooses a suitable information system development methodology.
The title is concerned with developing an “ONLINE LIBRARY MANAGEMENT SYSTEM”
in order to make library management more efficient. This website is mainly focused on
providing guidance to students and staffs which allows them to search books online. This project
has many features which are generally not available in normal library management systems like
facility of users, staffs login through online and admin login through which admin can monitor
the whole system. It is a website having two modules, administrator and users. It has also the
facility where students after logging in their accounts can see list of books issued and its issued
date as well as return date. As it is online based system so to interact and access with the
database, the user interfaces are developed using php and mysql.

Keywords: Management system, modules, Administrator, php, mysql.

2
TABLE OF CONTENTS
ACKNOWLEDGEMENT…………………………………………………….............................1

ABSTRACT……….……………………………………………………………………………...2

1. INTRODUCTION…………………………………………………………………………….7
1.1 PROBLEM STATEMENT……………………………………………………………7
1.2 PROJECT OBJECTIVE………………………………………………………………7
1.3 SIGNIFICANT OF STUDY…………………………………………………………..8
1.4 SCOPE AND LIMITATIONS………………………………………………………...8
1.5 FEASIBILITY ANALYSIS…………………………………………………………...9
1.5.1 ECONOMIC FEASIBILITY………………………………………………..9
1.5.2 TECHNICAL FEASIBILITY……………………………………………...10
1.5.3 OPERATIONAL FEASIBILITY………………………………………….10
1.6 SYSTEM REQUIREMENT…………………………………………………………10
1.6.1 SOFTWARE REQUIREMNT……………………………………………..10
1.6.2 HARDWARE REQUIREMENT…………………………………………..10

2. LITERATURE REVIEW…………………………………………………………………...11
2.1 WHAT IS FRONT END AND BACK END………………………………………...11
2.2 PHP…………………………………………………………………………………..11
2.3 MySQL………………………………………………………………………………11

3. METHODOLOGY…………………………………………………………………………..12
3.1 SOFTWARE DEVELOPMENT LIFE CYCLE……………………………………..12
3.2 ANALYSIS PHASE…………………………………………………………………13
3.3 DESIGN PHASE…………………………………………………………………….13
3.3 CODING PHASE……………………………………………………………………15
3.4 TESTING PHASE…………………………………………………………………...31
3.4.1 UNIT TESTING…………………………………………………………...31
 3.4.2 INTEGRATION TESTING………………………………………………………..31
3.5 TOOLS TO BE USED……………………………………………………………………….32

4. SECTION OF WORK DETAIL……………………………………………………………33

4.1 EXPECTED OUTPUT……………………………………………………………....33
4.2 SCHEDULE………………………………………………………………………….33
4.3 WORK BREAKDOWN……………………………………………………………..34

5. CONCLUSION………………………………………………………………………………35

6. FURTHER WORKS…………………………………………………………………………35

7. BIBLIOGRAPHY……………………………………………………………………………36

8. APPENDIX A………………………………………………………………………………...37

9. APPENDIX B………………………………………………………………………………...38

4
LIST OF FIGURE

Figure 1: Software Development Life Cycle

Figure 2: Incremental model

Figure 3: ER-Diagram

Figure 4: Use-Case Diagram

5
LIST OF TABLE

Table 1: Tools to be used

Table 2: Project Task and Schedule

Table 3: Work Breakdown

6
1. INTRODUCTION

The online library management system is a system which is used by librarian to manage the
library using a computerized system where the person can record various transactions like issue
of books and searching of book through online. The user needs not to visit the library every time
to find books; instead the user can search books from his/her own PC/laptop and can issue
directly with logging through their accounts. The admin can update, delete the record of
membership as per the requirement and implementation. The Library management system
enables a fully automated library service. It has ability to display the details of the books
available and transactions of books and book holders.

Overall this project of ours is being developed to help students as well as staffs of the library to
maintain the library in the best way possible and also reduce human efforts. It provides
simplicity as well as security and efficiency to the management.

1.1 PROBLEM STATEMENTS

The problem occurred before having computerized system include of more possibilities of file
lost due to human handling and loss of records. It would consume more time to search records
and need a lot of human efforts. After the number of records become large, it would take more
space and chances of misplace the files. The user needs to visit library every time in search of
book.

1.2 PROJECT OBJECTIVES

The objectives of library management system are listed below:

• The user can issue books through online.

• A search column to search availability of books in library.
• A student login page where the student can find books issued by him/her and the date of
return.
• A request column for librarian for providing new books.
7
FUNCTIONAL REQUIREMENTS AND USER INTERFACE REQUIREMENTS

▪ Functional Requirements
1. New entries must be entered in database.
2. Any change in articles should be updated in case of update.
3. Inquiry all enrolled members to view their details.

▪ User Interface Requirements

1. Help should be very user friendly.

2. Professional look and feel.

1.3 SIGNIFICANCE OF THE STUDY

Library is the best place in the school where the students review and study. It is the place where
students study so our group aims to improve the manual operation of the library system. We
thought of something that makes the time of students and library personnel decreases for
searching and borrowing of the books. The main aim of our group is to change the existing
system of library and to make it automated. So that the managing of the library will be more
efficiently and secure.

It will be easy for the students/borrowers to know if the book they are searching in the library is
existing and they will have lesser time to locate where the books are located.

It will lessen their paper works when it comes to maintaining data that contains all the records in
the library as the computer restore the details.

8
1.4 SCOPE AND LIMITATIONS

The system is only limited to assist the students in searching available books in the library and
keep track the student login records, system will mainly deal in the keeping of the time of login
of every registered students and store in secured database. The library information system is
limited only to users two namely: librarian, the one who will be authorized in adding new books
records, updating book records and can access data storage and make an output results.

User’s level access only limited to register personnel information, login in every time of using
the library and in searching the books availability and the location of the books in the library by
entering their student library number.

• Any educational institute can make use of it for providing information about content of
available books.
• Facility to reserve books that are available.
• Facility to cancel reservation for the book made earlier.
• A status page for all the users to view books reserved by them.

1.5 FEASIBILITY ANALYSIS

Whatever we think need not to be feasible. It is wise to think about feasibility of any problem we
undertake. Feasibility is the study of impact which happens in the organization by the
development of the system. The impact can either be positive or negative. When the positive
nominates the negative, then the system is considered as feasible.

1.5.1 ECONOMIC FEASIBILITY

Development of this application is highly economically feasible. The organization needed to not
spend for the development of system already available. The only thing is to be done is to making
an environment for the development with an effective supervision. If we are doing so, we can
attain the maximum usability of corresponding resource.

9
1.5.2 TECHNICAL FEASIBILITY

We can strongly say that it is technically feasible, since there will not be much difficulty in
getting require resources for the development and maintaining the system as well. All the
resources needed for the development of the software as well. As the maintenance of the same is
available in the organization here we are utilizing the resources which are available already.

1.5.3 OPERATIONAL FEASIBILITY

The system will be easy to use so no any special skills will be required to use the system. New
user will find it easy to use. So, project will be operationally feasible.

1.6 SYSTEM REQUIREMENT

System requirement includes software requirement and hardware requirement.

1.6.1 HARDWARE REQUIREMENT

1. Color monitor for good resolution

2. Microsoft compatible mouse

3. Internet connectivity facility

1.6.2 SOFTWARE REQUIREMENT

1. Operating System: Windows 10 pro

2. Programming language: PHP, MySQL

3. Web Server: Apache

4. Documentation Tool: Microsoft Word 2010

10
2. LITERATURE REVIEW

Though a variety of software is available in software market, but only few of these are fully
compatible with web. It also focuses on the growth and development of library automation
software way back to their origin. It also discussed standards, both in terms of library and web
technology. Finally, web interface used in library management software system is covered
including the technological implications; Web based technical services and security issue.

2.1 WHAT IS FRONT END AND BACK END

Simply, front end means user appearance and back end means database and other internal parts.

2.2 PHP

PHP is a server side scripting language designed for web development but also used as a general-
purpose programming language. PHP is now installed on more than 244 million websites and 2.1
million web servers. Originally created by Rasmus Lerdorf in 1995, the reference
implementation of PHP is now produced by the PHP Group. PHP commands can be embedded
directly into HTML source document rather than calling an external file to process data. It has
also evolved to include a command-line interface capability and can be used in standalone
graphical applications.

2.3 MySQL

MySQL is world’s second most widely used open source relational database management
system. It is named after co-founder Michael Widenius daughter, My. The SQL phrase stands for
the Structured Query Language. MySQL is the popular choice of database for use in web
applications, and is a central component of the widely used LAMP open source web application
software stack. LAMP is acronym for “Linux, Apache, MySQL, and PHP/Python/perl.

11
3. METHODOLOGY

Software development methodology engineering is a framework that is used to structure, plan,

and control the process of developing an information system. A software development process
also known as software development life cycle (SDLC), is a structure imposed on the
development of the software product. The main idea of SDLC has been to pursue the
development of information systems in very deliberate, structured and methodical way, requiring
each stage of life cycle from inception of the idea to the delivery of final system.

3.1 SOFTWARE DEVELOPMENT LIFE CYCLE

The framework we will be using for developing this project is Incremental model. This model
combines linear sequential model with the iterative prototype model. New functionalities will be
added as each increment in each development. The phases of linear sequential model are :
Analysis, Design, Coding and Testing. The software repeatedly passes through these phase in
iteration and increment is delivered with progressive change.

Figure 1: Software Development Life Cycle

12
3.2 ANALYSIS PHASE

In this phase analysis will be performed in order to find out the requirements of the system. The
outcome of this phase would be SRS which is an acronym for “System Requirement
Specifications”.

Figure 2: Incremental Model

3.2 DESIGN PHASE

In this phase, the SRS would be translated into the system’s design. Context Diagram, DFD,
ER-Diagram, Use Case Diagram and Class Diagram will be developed.

13
 ER DIAGRAM

An ER Diagram is a graphical representation of entities and their relationships.

Library

Contains

Books

Book name

Issued

Issue Student Return

Date
Roll no.

Status of issue id Status of return

Book id

Book id
Figure 3: ER-Diagram

14
 USE CASE DIAGRAM

A Use Case Diagram is the representation of a user’s interaction with the system that shows the
relationship between the user and the different use cases in which user is involved.

Enquiry

Register Member

Login

Check availability of book Member

Librarian

Issue book

Return book

Maintain book

Figure 4: Use-Case Diagram

15
3.3 CODING PHASE

In this phase, coding will be done according to the design and a working system will be
developed by the end of this process.

Index.blade.php-layout

<! DOCTYPE html>

<html lang="en">

<head>

<meta charset="utf-8">

<meta http-equiv="X-UA-Compatible" content="IE=edge">

<meta name="viewport" content="width=device-width, initial-scale=1">

<meta name="author" content="">

<meta name="description" content="">

<meta name="keywords" content="">

<link rel="shortcut icon" href="">

<link rel="image_src" href="" />

<link rel="canonical" href="" />

<title>Automated Library Management System</title>

<link type="text/css" href="{{ Config::get('view.bootstrap.css') }}/bootstrap.min.css"

rel="stylesheet">

16
 <link type="text/css" href="{{ Config::get('view.bootstrap.css') }}/bootstrap-
responsive.min.css" rel="stylesheet">

<link type="text/css" href="{{ Config::get('view.css') }}/theme.css" rel="stylesheet">

<link type="text/css"
href='http://fonts.googleapis.com/css?family=Open+Sans:400italic,600italic,400,600'
rel='stylesheet'>

@include('common.script_top')

</head>

<body>

@include('layout.template_navbar')

<div class="wrapper">

<div class="container">

<div class="row">

@include('layout.template_leftbar')

<div class="span9">

@include('account.message')

17
@yield('content')

</div>

</div>

</div>

</div>

@include('layout.template_footer')

<script src="{{ Config::get('view.script') }}/jquery-1.9.1.min.js"

type="text/javascript"></script>

<script src="{{ Config::get('view.script') }}/jquery-ui-1.10.1.custom.min.js"

type="text/javascript"></script>

<script src="{{ Config::get('view.bootstrap.js') }}/bootstrap.min.js"

type="text/javascript"></script>

<script src="{{ Config::get('view.script') }}/underscore-min.js" type="text/javascript"></script>

<script src="{{ Config::get('view.custom.js') }}/script.common.js"

type="text/javascript"></script>

@include('common.script_bottom')

<script type="text/template" id="alert_box">

@include('underscore.alert_box')

18
</script>

</body>

</html>

Index.blade.php-account

<!DOCTYPE html>

<html lang="en">

<head>

<meta charset="utf-8">

<meta http-equiv="X-UA-Compatible" content="IE=edge">

<meta name="viewport" content="width=device-width, initial-scale=1">

<meta name="author" content="">

<meta name="description" content="">

<meta name="keywords" content="">

<link rel="shortcut icon" href="">

<link rel="image_src" href="" />

<link rel="canonical" href="" />

<title>Library Management System</title>

19
<link type="text/css" href="{{ Config::get('view.bootstrap.css') }}/bootstrap.min.css"
rel="stylesheet">

<link type="text/css" href="{{ Config::get('view.bootstrap.css') }}/bootstrap-

responsive.min.css" rel="stylesheet">

<link type="text/css" href="{{ Config::get('view.css') }}/theme.css" rel="stylesheet">

<link type="text/css" href="{{ Config::get('view.images') }}/icons/css/font-awesome.css"

rel="stylesheet">

<link type="text/css"
href='http://fonts.googleapis.com/css?family=Open+Sans:400italic,600italic,400,600'
rel='stylesheet'>

@include('common.script_top')

</head>

<body>

@include('account.navigation_top')

@include('account.message')

@yield('content')

@include('account.navigation_bottom')

<script src="{{ Config::get('view.script') }}/jquery-1.9.1.min.js"

type="text/javascript"></script>

20
<script src="{{ Config::get('view.script') }}/jquery-ui-1.10.1.custom.min.js"
type="text/javascript"></script>

<script src="{{ Config::get('view.bootstrap.js') }}/bootstrap.min.js"

type="text/javascript"></script>

<script src="{{ Config::get('view.script') }}/underscore-min.js" type="text/javascript"></script>

<script src="{{ Config::get('view.custom.js') }}/script.common.js"

type="text/javascript"></script>

@include('common.script_bottom')

<script type="text/template" id="alert_box">

@include('underscore.alert_box')

</script>

</body>

</html>

21
F:\xampp\htdocs\library-management-
system\app\storage\views\0759c31145013d8d025edf1f20562ec7:

5 <i class="icon-reorder shaded"></i>

6 </a>

7: <a class="brand" href="<?php echo URL::route('home'); ?>">NSIT

ALMS</a>

8 </div>

9 </div>

F:\xampp\htdocs\library-management-
system\app\storage\views\10212bff1dff699d78e126db8b34c59b:

3 <div class="btn-controls">

4 <div class="btn-box-row row-fluid">

5: <a class="btn-box span12"><b>NSIT Automated Library Management

System</b></a>

6 </div>

F:\xampp\htdocs\library-management-
system\app\storage\views\14a7b1b9cd2b1d5c84b798a158608662:

13 <link rel="canonical" href="" />

14

15: <title>NSIT Automated Library Management System</title>

16

22
17 <link type="text/css" href="<?php echo Config::get('view.bootstrap.css');
?>/bootstrap.min.css" rel="stylesheet">

F:\xampp\htdocs\library-management-
system\app\storage\views\50bf5c5dfcf6700b780f972873d6cb8e:

1 <div class="footer">

2 <div class="container">

3: <b class="copyright">&copy; 2015 NSIT - Automated Library Management

System </b> All rights reserved.

4 <br><a href="https://github.com/prabhakar267/library-management-system"
target="_blank">Fork on Github</a>

5 </div>

F:\xampp\htdocs\library-management-
system\app\storage\views\57877614331058d1339b4af0768c940a:

3 <div class="btn-controls">

4 <div class="btn-box-row row-fluid">

5: <a class="btn-box span12"><b>NSIT Automated Library Management

System</b></a>

6 </div>

F:\xampp\htdocs\library-management-system\app\views\panel\index.blade.php:

5 <div class="btn-controls">

23
 6 <div class="btn-box-row row-fluid">

7: <a class="btn-box span12"><b>NSIT Automated Library Management

System</b></a>

8 </div>

6 matches across 6 files

Searching 145 files for "tudent cannot issue any more books"

F:\xampp\htdocs\library-management-system\app\controllers\LogController.php:

63

64 if($books_issued >= $max_allowed){

65: throw new Exception('Student cannot issue any more

books');

66 } else {

67 $book = Issue::find($bookID);

F:\xampp\htdocs\library-management-system\app\storage\logs\laravel.log:

254 #17

24
F:\xampp\htdocs\library-management-system\server.php(20):
require_once('F:\\xampp\\htdocs...')

255 #18 {main} [] []

256: [2018-01-13 04:05:52] production.ERROR: exception 'Exception' with message 'Student

cannot issue any more books' in F:\xampp\htdocs\library-management-
system\app\controllers\LogController.php:65

257 Stack trace:

258 #0 [internal function]: LogController->store()

...

275 #17 F:\xampp\htdocs\library-management-system\server.php(20):

require_once('F:\\xampp\\htdocs...')

276 #18 {main} [] []

277: [2018-01-13 04:06:00] production.ERROR: exception 'Exception' with message 'Student

cannot issue any more books' in F:\xampp\htdocs\library-management-
system\app\controllers\LogController.php:65

278 Stack trace:

279 #0 [internal function]: LogController->store()

...

296 #17 F:\xampp\htdocs\library-management-system\server.php(20):

require_once('F:\\xampp\\htdocs...')

297 #18 {main} [] []

298: [2018-01-13 04:06:04] production.ERROR: exception 'Exception' with message 'Student

cannot issue any more books' in F:\xampp\htdocs\library-management-
system\app\controllers\LogController.php:65

299 Stack trace:

25
300 #0 [internal function]: LogController->store()

...

317 #17 F:\xampp\htdocs\library-management-system\server.php(20):

require_once('F:\\xampp\\htdocs...')

318 #18 {main} [] []

319: [2018-01-13 04:07:14] production.ERROR: exception 'Exception' with message 'Student

cannot issue any more books' in F:\xampp\htdocs\library-management-
system\app\controllers\LogController.php:65

320 Stack trace:

321 #0 [internal function]: LogController->store()

...

401 #17 F:\xampp\htdocs\library-management-system\server.php(20):

require_once('F:\\xampp\\htdocs...')

402 #18 {main} [] []

403: [2018-01-13 04:10:37] production.ERROR: exception 'Exception' with message 'Student

cannot issue any more books' in F:\xampp\htdocs\library-management-
system\app\controllers\LogController.php:65

404 Stack trace:

405 #0 [internal function]: LogController->store()

...

422 #17 F:\xampp\htdocs\library-management-system\server.php(20):

require_once('F:\\xampp\\htdocs...')

423 #18 {main} [] []

26
424: [2018-01-13 04:11:29] production.ERROR: exception 'Exception' with message 'Student
cannot issue any more books' in F:\xampp\htdocs\library-management-
system\app\controllers\LogController.php:65

425 Stack trace:

426 #0 [internal function]: LogController->store()

...

443 #17 F:\xampp\htdocs\library-management-system\server.php(20):

require_once('F:\\xampp\\htdocs...')

444 #18 {main} [] []

445: [2018-01-13 04:13:18] production.ERROR: exception 'Exception' with message 'Student

cannot issue any more books' in F:\xampp\htdocs\library-management-
system\app\controllers\LogController.php:65

446 Stack trace:

447 #0 [internal function]: LogController->store()

27
28
29
30
3.4 TESTING PHASE

In this phase, the system is tested with each testing a list of changes to the systems developed, is
suggested and the changes will be applied to the software and the software would be delivered as
a successive increment until a satisfying system is achieved. The tools used for documentation,
designing and developing UI/UX, testing are listed below the table. We are concerned mainly
with the following testing technique:

-Unit testing

-Integration testing

3.4.1 UNIT TESTING

Unit testing is applied to the individual testing modules. This test determines whether the
modules are logically and functionally sound. This test is performed throughout the project from
the beginning because the whole project is formed by combining different modules. Since
module development is continuous process in project construction so unit testing is important to
find errors in each module.

3.4.2 INTEGRATION TESTING

The process of getting together all of the modules that a program comprise for testing purposes is
integration testing. Modules are typically integrated in the top down incremental fashion.
Integration testing is gradual. First we test the coordinating module and only one of its sub-
ordinate modules. After the first test, we add one or two sub-ordinate modules from the same
level. Once the program has been tested with coordinating modules and all of its immediately
subordinate modules, we add modules from the next level and then test the program.

31
3.2 TOOLS TO BE USED

TOOLS PURPOSE

Sublime Text Editor Code Editor

PHP, MySQL Programming language

Apache Development Server

Designing Twitter Bootstrap

Xampp Development Environment

TABLE 1: TOOLS TO BE USED

32
4. SECTION OF WORK DETAIL

The project schedule has been designed as per requirements and constraints involved. This
project is scheduled to be completed in about 2 months. Requirement analyses have been given
more emphasis. Research and database management is to be done first and well documented.
Debugging and testing is to be done prior to the completion of the project.

4.1 EXPECTED OUTPUT

1. Students can issue the book online.

2. Students can search book.

2. Students need to physically return the book.

4.2 SCHEDULE

TASK APPROX. DURATION(in days)

Requirement Analysis and Specification 8

Undertake Analysis of the System 8

Design System 14

Produce Requirement Specification 9

Testing and Debugging 8

Test System Modules 4

Overall System Test 5

Develop Documentation 60

TABLE 2: PROJECT TASK AND SCHEDULE

33
4.2 WORK BREAKDOWN

Below is the labor division of the entire work load of this project:

Table 3: Work Breakdown

S.N Task Team Members

1 Front end and UI Design Naina

2 Back end and Core programming Naina, Alisha

3 Testing Naina, Alisha

4 Documentation Naina, Alisha

34
5. CONCLUSION

The package was designed in such a way that future modifications can be done easily. Library
management system of the entire system improves the efficiency. It provides a friendly graphical
user interface which proves to be better when compared to the existing system. It gives
appropriate access to the authorized user depending on their permissions. It effectively
overcomes the delay in communications. Updating of information become so easier.

6. FURTHER WORKS

This is the sample project for online library management system. If we develop this project we
will be able to issue and search availability of books through online.

35
7. BIBLIOGRAPHY

1. Andrews, k.1987. The Concept of Corporate Strategy. 3rd. ed. Homewood, IL: Richard D.
Irwin.

2. Ansoff, H. I. 1957. Strategies for diversification. Harvard Business Review. September-

October.

3. Ansoff, H. I. & Mcdonell, E.1990. Implanting Strategic Management. 2 nd ed. New York:
Prentice –Hall.

URL: https://www.slideshare.net/

URL: https://web.iiit.ac.in/

URL: http://docshare.tips/

URL: https://en.wikipedia.org/

36
8. APPENDIX

37
38