Department of Computer Science and Engineering

Faculty of Computer Science and Engineering

Hajee Mohammad Danesh Science and Technology University
Dinajpur-5200, Bangladesh

CERTIFICATE

This is to certify that the work entitled as “UNIVERSITY ONLINE LIBRARY” by Md.
Mojibur Rahman, Rakibul Islam and Md. Shamim Mia has been carried out under our
supervision. To the best of our knowledge this work is an original one and was not submitted
anywhere for a diploma or a degree.

Co-supervisor

…………………..
(Md. Fazle Rabbi)
Assistant Professor
Department of Computer Science and Engineering
Hajee Mohammad Danesh Science and Technology University, Dinajpur-5200, Bangladesh

Supervisor

……………………
(Md. Palash Uddin)
Assistant Professor
Department of Computer Science and Engineering
Hajee Mohammad Danesh Science and Technology University, Dinajpur-5200, Bangladesh

i
 Department of Computer Science and Engineering
Faculty of Computer Science and Engineering
Hajee Mohammad Danesh Science and Technology University
Dinajpur-5200, Bangladesh

DECLARATION

The work entitled “UNIVERSITY ONLINE LIBRARY” has been carried out in the
Department of Computer Science and Engineering, Hajee Mohammad Danesh Science and
Technology University is original and conforms the regulations of this University.

We understand the University’s policy on plagiarism and declare that no part of this thesis has
been copied from other sources or been previously submitted elsewhere for the award of any
degree or diploma.

…………………… ……………..
(Md. Mojibur Rahman) (Rakibul Islam)
Student ID: 1502036 Student ID: 1502038
Session: 2015 Session: 2015

……………
(Md. Shamim Mia)
Student ID: 1502064
Session: 2015

ii
Acknowledgement
Write your acknowledgement here……….

iii
CONTENTS
Certificate ii

Declaration iii

Acknowledgement iv

Contents v

List of Figures vii

Abstract viii

1 Introduction ....................................................................................................................... 1
1.1 Introduction….. ............................................................................................................ 2
1.2 Overview of the Project ............................................................................................... 2
1.3 Project Aims and Objectives ....................................................................................... 3

2 Feasibility Study ................................................................................................................ 4

2.1 Defining a Problem....................................................................................................... 5
2.2 Feasibility Study .......................................................................................................... 5

3 System Analysis ................................................................................................................ 7

3.1 System Analysis ........................................................................................................... 8
3.2 System Requirement Specifications ............................................................................. 8
3.2.1 General Description .............................................................................................. 8
3.3 System Objectives ........................................................................................................ 9
3.4 System Requirements ................................................................................................. 10
3.4.1 Non-Functional Requirements ............................................................................ 10
3.4.2 Functional Requirements ................................................................................... 10
3.5 Hardware and Software Requirements ....................................................................... 12
3.5.1 Hardware Requirements...................................................................................... 12
3.5.2 Software Requirements ....................................................................................... 12
3.6 Existing VS Proposed System .................................................................................... 12

iv
4 System Design ................................................................................................................. 13
4.1 E-R Diagram ............................................................................................................... 14
4.2 Data Flow Diagram .................................................................................................... 15
4.3 Database Table ........................................................................................................... 16
4.4 Use Case Diagram ...................................................................................................... 17

5 System Implementation .................................................................................................. 17

5.1 System Implementation ............................................................................................. 18

6 System Testing.................................................................................................................. 21
6.1 Unit Testing ................................................................................................................ 22
6.1.1 Test for the Admin Module................................................................................. 22
6.1.2 Test for the Student Login Module ..................................................................... 22
6.2 Integration Testing...................................................................................................... 23

7 Conclusion and Future Scope ......................................................................................... 24

7.1 Conclusion .................................................................................................................. 25
7.2 Future Plan.................................................................................................................. 25

References .............................................................................................................................. 26

v
LIST OF FIGURES
4.1: E-R Diagram for the System ....................................................................................... 14
4.2: DFD for the System .................................................................................................... 15
4.3: Student Diagram for Sign-Up and Login .................................................................... 16
4.4: Admin Diagram for C-Panel ....................................................................................... 16
5.1: Screenshot of Homepage ............................................................................................ 18
5.2: Screenshot of Sign-Up Page ....................................................................................... 18
5.3: Screenshot of Login Page ........................................................................................... 19
5.4: Screenshot of Books Page for CSE Department .......................................................... 19
5.5: Screenshot of Student Database Table......................................................................... 20

vi
Abstract

Any business that does not have a website is missing out on one of the most powerful marketing
tools available to them. The main reason that it is important for businesses to have a website is
how people are likely to find you. These days most people will go online and research products
and companies before they make a purchase. For this reason of dependency on online, we
develop a website for an Online Library in which students can get all information about the
library and he/she can access or enroll at the library via online. Usually, the client uses MS
Excel or paper, and maintains their records, however it is not possible them to share the data
from multiple system in multi user environment, there is lot of duplicate work, and chance of
mistake. When the records are changed they need to update each and every excel file. The
University Online Library eliminates most of the limitations of the existing software.
Increasing efficiency and effectiveness, automation, accuracy, user-friendly interface,
information availability, communication capacity, maintenance, cost reduction makes our
system smarter than the existing system. We integrate some new and prominent features along
with all the necessary features.

vii
Chapter 1

Introduction

1
1.1 Introduction
A University Online library is a system built to handle the primary housekeeping functions of
a library. Libraries rely on library management systems to manage asset coactions as we as
relationships with their members. Library management systems help libraries to keep track of
the books on their checkouts as we as members’ subscriptions and profiles.

Library management system also involve maintaining the database for entering new books an
recording books that have been borrowed with their respective due dates.

1.2 Overview of the Project

In any educational institution like a university it is complex to make a better library
management system for all departments in a faculty. In this regard, the project aims to meet the
requirements of a University Online Library in a proper planning. It helps to meet the
requirements of each department by considering the no. of departments in a faculty, no. of
different courses, no. of students, available books etc. The target of the project is how to avail
the books, sheets or hand-notes, previous exams’ question papers completely and properly in a
shortest possible time. It is a distributed system that allows multiple faculty and departmental
managers to coordinate efforts to build and modify a University Online Library that meets their
diverse needs while allowing for minimization of student course conflicts. It covers both of
semester final and mid-semester exams questions. It tries to build a complete Online Library
that minimizes the number of conflicting placements for all students.

It is difficult for the students to collect previous exam’s questions from university library. In
this regard, in this project there is an upload option for the questions by the administrator and
a download option for the students of different departments of different faculties in the
university. Some other services like available books in online library for different departments
to download are available in the project. The project is used by the librarian of the university
library to manage the library using a computerized system where he/she can record various
transactions like issues of books, return of books, addition of new books etc.

2
1.3 Project Aims and Objectives
The project aims and objectives of this project are summarized below:

• The main objective of the project is to design and develop a user friendly efficient
computerized Library Management System.
• Online book issue.
• An accurate system without any data redundancy.
• Secured data storage for Authority end.
• Secure the user ends data by providing each user’s own personal credentials.
• A search column to search available books.
• Computerization can be helpful as means of saving time & money.
• To provide previous exam’s questions for different departments.
• To avail sheets and hand-notes provided by both teachers and students the for
different courses. [7]

3
 Chapter 2

Feasibility Study

4
2.1 Defining a Problem

Defining a problem is one of the important activities of the project. The objective is to define
precisely the business problem to be solved & thereby determined the scope of the new system.
This phase consist of 2 main tasks. The 1st task within this activity is to review the organization
needs that originally initiated the project. The 2nd task is to identify, at an abstract or general
level, the expected capabilities of the new system. Thus, it helps us to define the goal to be
achieved & the boundary of the system. A clear understanding of the problem will help us in
building a better system & reduce the risk of project failure. It also specifies the resources that
have to be made available to the project. Three important factors project goal, project bounds
& the resource limits are sometimes called the project’s term of reference.

2.2 Feasibility Study

The systems objectives outlined during the feasibility study serve as the basic from which the
work of system design is initiated. Much of the activities involved at this stage is of technical
nature requiring a certain degree of experience in designing systems, sound knowledge of
computer related technology and through understanding of computers available in the market
and the various facilities provided by the vendors. Nevertheless, a system cannot be designed
in isolation without the active involvement of the user. The user has a vital role to play at this
stage too. As we know that data collected during feasibility study wills we utilized
systematically during the system design [1]. It should, however be kept in mind that detailed
study of the existing system is not necessarily over with the completion of the feasibility study.
Depending on the plan of feasibility study, the level of detailed study will vary and the system
design stage will also vary in the amount of investigation that still needs to be done. This
investigation is generally an urgent activity during the system. Sometimes, but rarely, this
investigation may form a separate stage between feasibility study and computer system design.
Designing a new system is a creative process, which calls for logical as well as lateral thinking.
The logical approach involves systematic moves towards the end product keeping in mind the
capabilities of the personnel and the equipment at each decision making step. Lateral thought
implies encompassing of ideas beyond the usual functions and equipment. This is to ensure
that no efforts are being made to fit previous solutions into new situations.

5
The feasibility study proposes one or more conceptual solutions to the problem set for the
project. The objective in assessing feasibility is to determine whether a development project
has a reasonable chance of success. It helps us to determine the input & output of the system.
The following are the criteria that are considered to confirm the project feasibility [2].

The following feasibility study was undertaken for the proposed system:

• Technical Feasibility: At first it’s necessary to check that the proposed system is
technically feasible or not & to determine the technology and skill necessary to carry
out the project. If they are not available then find out the solution to obtain them.
Hardware is already available in the University.
• Economic Feasibility: While considering economic feasibility, it is checked in points
like performance, information and outputs from the system. The developing system
must be justified by cost and benefit. Criteria to ensure that effort is concentrated on
project, which will give best, return at the earliest. One of the factors, which affect the
development of a new system, is the cost it would require.
• Social Feasibility: Although generally there is always resistance, initially to any change
in the system is aimed at reliving the work load of the users to extent the system is
going to facilitate user to perform Operations like calculating salary amounts and
deductions, generating reports with less possible errors. Thus there is no reason to make
system socially unfeasible.

6
 Chapter 3

System Analysis

7
3.1 System Analysis

In this chapter, we will discuss and analysis about the developing Library Management System
including software requirement specifications (SRS) and comparison between existing and
proposed system the functional and non-functional requirements are included in SRS part to
provide complete description and overview of system requirements before the developing
processing is carried out .Besides that, existing vs proposed provides a view of how the
proposed system will be more efficient than the existing one [3].

3.2 Software Requirement Specifications

3.2.1 General Description

• Product Description

Library Management System is a computerized system which help user to manage

the library daily activity in electronic forms .It reduces the risk of paper work such as
file lost, file damaged and time Consuming It can help user to manage the transaction
or record more effectivity and time-saving.

• Problem statement

The problem occurred before having comprised 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 if water by some member on file accidently. Besides, some natural disaster like
floods or fires may also damage the file.

• Difficult to search record

When there is no computerized system there is always a difficulty searching of records

if the records are large in number.

• Space Consuming

8
 After the number of records become large space for physical storage file and record
also increases if no computerized system is implemented.

• Cost consuming

As this there is no computerized system to add each record paper will be needed which
will increase the cost for the management of library [4].

3.3 System Objectives

• Improvement in control and performance

The system is developed to cope up with the current issues and problems of Library.
The system can add user, validate user and is also bug free.

• Save Cost

After computerized system is implemented less human force will be required to

maintain the library thus reducing the overall cost.

• Save Time

Librarian is able to search record by using few clicks the mouse and few search
keywords thus saving his valuable time.

• Option of Online Notice Board

Librarian will able to provide a detailed description of workshop going in the college
as well as in nearby colleges.

• Lectures Notes

Teachers have a facility to upload lectures notes in the pdf file having also more than
10mb [5].

9
3.4 System Requirement

3.4.1 Non Functional Requirement

• Efficiency Requirement

When a library management system will be implemented librarian and user will easily
access library as searching and book transaction will be very faster

• Reliability Requirement

The system should accurately perform member registrations, members validation, report
generation, books transaction and search.

• Usability requirement

The system is designed for a user friendly environment so that student and staff and staff
of library can perform the various takes easily and in an effective way.

• Organization requirement

In implementing whole system is uses html in front end with php as server side scripting
language which will be used in database.

3.4.2 Functional Requirements

User Login
• Description of Feature
This feature used by user to login into system. They have to enter user id and password
before they are allowed to enter the system. The user id and password will be verified
and if invalid id is there is allowed to not enter the system.
• Functional Requirement
User id is provided when they register.
-the system must only allow user with valid id and password to enter the system.
-The system perform authorizations process which decides what user level can access
to.
-the user must be able to logout after they finished using system.

10
Register New User
• Description of Feature
This feature can be performed by all users to registration new user to create account.
• Functional Requirements

-system must be able to verify information.

-system must be able to delete information.

Registration New Book

• Description of Feature
This feature allows to add new books to the library to the library
• Functional Requirements

-system must be able to verify information.

-system must be able to number if copies into table.

-system must be able to not allow two books having same book.

Search Book

• Description of Feature
This feature is found maintenance part.
• Functional Requirement
-system must be able to search the database on select search

Issue Books and Return Books

• Description of feature

This feature allows to issues and return books.

• Functional requirements

-system must be able to add information about database

-system must be able to update number of books

11
3.5 Hardware and Software Requirements

This section describes the hardware and software requirements of the system.

3.5.1 Hardware Requirements

Hardware Specifications of the system are the specification of the physical components of the
machine on which the project has been devised.
The hardware requirements for our project are:

• Intel core i5
• Hard disk ->1 GB free space
• Memory -> 4GB RAM
• Processor -> Intel ® Pentium 4 or Higher
• Monitor -> VGA or Higher 15
• Mouse -> Standard
• Keyboard -> Standard

3.5.2 Software Requirements

Software Specifications are the Software’s required to be installed on the computer on which
the software project is to be run. The software requirements for our project are:
• Microsoft Windows (Windows 7, Windows 8, Windows 10)
• Microsoft office Tools (Word, Power point) for preparing documentation, Data Flow
Diagram and Presentation.
• Apache Webserver
• JavaScript enabled Browser
• PHP/MySQL

3.6 Existing VS Proposed System

• Existing system does not having any facility of teachers login and students login system
but proposed system have it
• Existing system does not having facility online reservation system but proposed system
have reservation system.

12
 Chapter 4

System Design

13
4.1 E-R Diagram

s_id s_name s_faculty

b id s_title

s_dept.
Books
Student s_id

s_email
s_id
s_mobile

s_verify
b_id
s_id

Issue Record
s_id return
_date

issue_date
b_id
record

Fig. 4.1. E-R Diagram for the System.

There are three entities in the E-R diagram. These are Student, Books and Issue Record.

14
4.2 Data Flow Diagram

Fig. 4.2. Data flow diagram for student login

Fig. 4.3. Data flow diagram for account creation

Fig. 4.4. Data flow diagram for book search

15
 Fig. 4.5. Data flow diagram for book issued

4.3 Database Table

TABLE 4.1 STUDENT RECORD
S. No. Column Name Data Type Length Description

1 Student Id Text 50 Unique

identification of
student

2 Name Text 20 Name of student

3 Department Text 50 Department of

student

4 Date of Date/time Date of

Membership registration
5 Status Text 50 Active/Inactive

16
 TABLE 4.2 BOOKS RECORD

S. No. Column name Data type Description

1 Book id Text Book identification

number
2 Name Text Title of Book

3 Author Text Author of book

4 Status Text Either book is

available or not
5 No of books Number Quantity of books

TABLE 4.3 LIBRARIAN

S. No. Column Name Data type Description

1 Name Text Name of the

Librarian
2 Password password Login password of
the librarian

17
4.4 Use Case Diagram

Enquiry

Register Member

Login
Admin Member

Check availability of book

Issue Book

Return Book

Functions

18
 Chapter 5

System Implementation

19
5.1 System Implementation

Fig. 5.1. Homepage.

Fig. 5.2. Sign-Up Page.

20
 Fig. 5.3. Login Page.

Fig. 5.4. Books Page for CSE Department.

21
Fig. 5.5. Student Database Table.

22
 Chapter 6

System Testing

23
6.1 Unit Testing

Unit testing is undertaken when a module has been created and successfully reviewed. In order
to test a single module we need to provide a complete environment is beside the module we
would require [6]:

• The procedures belonging to other modules that the module under test calls non local
data structures that module success.
• A procedure to call the functions of the module under test with appropriate parameters.

6.1.1 Test for the Admin Module

• Testing admin login form- This form is used for log in of administrator of the
system.

In this we enter the user name and password if both are correct administration page
will open otherwise if any data is wrong it will get redirected back to the log in page
and again ask for username and password.

• Student account addition- In this section the admin can verify students details to
main library database it contains add and delete buttons if user click add button data
will be added to student database and if he clicks delete button student data will be
deleted.
• Book addition- Admin can enter details of book and can add the details to the main
book table also he can view the book requests.

6.1.2 Test for Student Login Module

• Test for student login form- This form is used for log in of student. In this we enter
the library _id, username and password if all these are correct student login page
will open otherwise it will be redirected back to the login page and again ask for
library _id username and password.
• Test for account creation-This form is used for new account creation when the
students does not fill the form completely it ask again to fill the whole form when

24
 he fill the form fully it gets redirected to page which show waiting for conformation
message as his data will be only added by administrator after verification.

6.2 Integration Testing

Integration testing is a level of software testing where individual units are combined
and tested as a group. The purpose of this level of testing is to expose faults in the interaction
between integrated units. Test drivers and test stubs are used to assist in Integration Testing.

In this type of testing we test various integration of the project module by providing the input.
The primary objective is to test the module interfaces in order to ensure that no errors are
occurring when one module invokes the other module.

Some different types of integration testing are big-bang, mixed (sandwich), risky-
hardest, top-down, and bottom-up. Other Integration Patterns are: collaboration integration,
backbone integration, layer integration, client-server integration, distributed services
integration and high-frequency integration.

In the big-bang approach, most of the developed modules are coupled together to form a
complete software system or major part of the system and then used for integration testing.
This method is very effective for saving time in the integration testing process. However, if
the test cases and their results are not recorded properly, the entire integration process will be
more complicated and may prevent the testing team from achieving the goal of integration
testing.

Bottom-up testing is an approach to integrated testing where the lowest level components are
tested first, then used to facilitate the testing of higher level components. The process is
repeated until the component at the top of the hierarchy is tested. All the bottom or low-level
modules, procedures or functions are integrated and then tested. After the integration testing
of lower level integrated modules, the next level of modules will be formed and can be used
for integration testing.

Top-down testing is an approach to integrated testing where the top integrated modules are
tested and the branch of the module is tested step by step until the end of the related module.

Sandwich testing is an approach to combine top down testing with bottom up testing.

25
 Chapter 7

Conclusion & Future Scope

26
7.1 Conclusion

This website provides a computerized version of library management system which will benefit
the students as well as the staff of the library.

It makes entire process online where students can search books staff can generate reports and
can do book transactions .It also has a facility for student login where students can login and
can see status of books issued as well request for books or give some suggestions. It has 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 campus in
the online notice board.

7.2 Future Plan

Present System is a combination of various modules.

In spite of our rigorous effort we had not been able to assimilate all the features of an ideal an
online library, since we have not included every area, which comes in an online library
management system, the project can be further enhanced to include more modules.

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.

Proposed System is very suitable for proposed institution. It helps users to do their work very
smoothly. This project has very much flexibility and according to time and need we can modify
data and facility also. We can add more features in this project in future as well as can remove
the limitation from the next version. So, this project has a great future scope.

27
References
[1] E.M Awad,Mclntire School of Commerce University of Virginia “feasibility study ”
System analysis and design 2nd ed, pp.200-210,22, Feb 1995.
[2] Tutorialspoint (https://www.tutorialspoint.com).
[3] Robert J waller, IEEE transactions on systems design, cybernatics, VOL. SMC-15, NO. 3,
MAY/JUNE 1985
[4] E.M Awad Mclntire School of Commerce University of Virginia “feasibility study ”
System analysis and design 2nd ed, pp. 502.
[5] Linda S. Hamnond, Daniel L. Mwphy, Mark K. Smith a system for analysis and
verifivation of software design.
[6] Tutorialspoint
(https://www.tutorialspoint.com/software_engineering/software_requirements.htm)
[7] Software Engineering (Sommerville) 8th ed; and System analysis and design (E.M Awad)
2nd ed (6.1)
[8] C. J. Date, A. Kannan and S. Swamynathan, An Introduction to Database Systems,
+Pearson Education, Eighth Edition, 2009.
[9] Abraham Silberschatz, Henry F. Korth and S. Sudarshan, Database System Concepts,
McGraw-Hill Education (Asia), Fifth Edition, 2006.
[10] Shio Kumar Singh, Database Systems Concepts, Designs and Application, Pearson
Education, Second Edition, 2011.
[11] Peter Rob and Carlos Coronel, Database Systems Design, Implementation and
Management, Thomson Learning-Course Technology, Seventh Edition, 2007
[12] Wellish, Hans H. "Dewey Decimal Classification, Universal Decimal Classification,
and the Broad System of Ordering: The Evolution of Universal Ordering Systems". College
of Library and Information Sciences, University of Maryland.
[13] Gregory, Ruth W. and Lester L. Stoffel. Public Libraries in Cooperative Systems:
Administrative Patters for Service. Chicago: American Library Association, 1971.

28
[14] Lyle, Guy R. The Administration of the College Library, with the collaboration of Paul
H. Bixler, Marjorie Hood, and Arnold H. Trotier. Third ed. New York: H. W. Wilson Co.,
1961. xiii, 419 p
[15] Wofford, Azile. The School Library at Work: Acquisition, Organization, Use, and
Maintenance of Materials in the School Library. New York: H. W. Wilson Co., 1959.
[16] Lock, Reginald Northwood. Library Administration. London: C. Lockwood & Son,
1961. vi, 132, [1] p

29