Source Code For The Given Blackbook Can Be Downloaded From or For A Advanced Version of Library Source Code Can Be Downloaded From A Project ON
Source Code For The Given Blackbook Can Be Downloaded From or For A Advanced Version of Library Source Code Can Be Downloaded From A Project ON
Source Code For The Given Blackbook Can Be Downloaded From or For A Advanced Version of Library Source Code Can Be Downloaded From A Project ON
Year 2016-2017
DATE OF SUBMISSION
06-06-2017
1
Library Management System
A PROJECT
ON
Year 2016-2017
DATE OF SUBMISSION
06-06-2017
2
Library Management System
PROJECT CERTIFICATE
3
Library Management System
DECLARATION
I declare that this written submission represents my ideas in my own words and
where others' ideas or words have been included, I have adequately cited and
referenced the original sources. I also declare that I have adhered to all
principles of academic honesty and integrity and have not misrepresented or
fabricated or falsi ed any idea/data/fact/source in my submission. I understand
that any violation of the above will be cause for disciplinary action by the
Institute and can also evoke penal action from the sources which have thus not
been properly cited or from whom proper permission has not been taken when
needed.
4
Library Management System
(Signature)
Random Name
Date :
ACKNOWLEDGEMENT
I the undersigned have great pleasure in giving our sincere thanks to those who
have contributed their valuable time in helping us to achieve the success in our
project work.
I would like to express our gratitude to all those gave us the possibility to
complete this project. I want to thank St Stefen High School for giving us the
opportunity for doing this project.
I am indebted and thankful to our Project Guide Prof. Mr.Random Sir Name
to whom I owe his piece of knowledge for his valuable and timely guidance, co-
operation, encouragement & time spent for doing this project work.
5
Library Management System
PREFACE
Computers are now becoming part of almost every activity in organization. The
developments made on the fields of information and computer technology have
vastly blown up and have changed the face of the present world rapidly. The use
of IT has gradually and now computers are increasingly used for everyday
activities organizations. The Library Management System is full of feeling to
provide better services to its users.
The main objective of the program is too serve the library to handle day to day
books transaction and maintain sound information about the books as well as
the members.
My sincere thanks also goes to the friends who have suggest the flow of the
system and gave reliable ideas to work on.
I have worked with commitment right from the initialization of the project and
continuing all the way till its compilation.
Review of the project is an unending process and it may contain errors as there
is always a scope for improvements.
6
Library Management System
SYNOPSIS
7
Library Management System
Introduction:
The project entitled Library Management System is a pilot project for small
school to manage their library administration process.
Project:
Methodology:
Library is the place where information and books are stored. It is the place
where people from all fields uses the books and information required for them.
But for that purpose since long time the manual system was followed during
operation using the library card. But with the increasing demands of technology
in various fields are forcing to stop the manual system in library operation. So
to fulfill the increasing demands of the library management software has been
developed.
Objective:
Scope:
This application can be used by any library to maintain the student records,
daily transactions of books etc.
8
Library Management System
Problem Definition:
The existing system was a manual system to keep the transaction happened in
the library. All the transaction was manually recorded which was time
consuming and tedious. It was also not reliable. The current system was using
the traditional method for daily activities, where the librarian had to handle
most of the activities manually as it was taking a long time.
Here we have tried to implement the manual system into the computer based
system as it overcomes most of the flow of the manual system.
Proposed System:
In the proposed system, we assume that each member will be having a identity
card which can be used for the library book issue, fine payment etc. whenever
library member wish to take a book, the book issued by the library authority
will be check both the book details as well as the student details and store it in
library database. In case of retrieval of book much of human intervention can be
eliminated.
Limitations
There are not many limitations of the project but any of these limitations are not
affection the whole system. But anyhow it includes some limitations, which are
listed below:
Hardware Requirement
Software Requirement :
Wordpress 4.3+
MySql 5.7
INDEX
10
Library Management System
OBJECTIVE
&
SCOPE OF THE PROJECT
11
Library Management System
Library is the place where information and books are stored. It is the place
where people from all fields uses the books and information required for them.
But for that purpose since long time the manual system was followed during
operation using the library card. But with the increasing demands of technology
in various fields are forcing to stop the manual system in library operation. So
to fulfill the increasing demands of the people library management software has
been developed.
In the real world the data are stored in the register books they categorized data
as static & dynamic data. The data that are updated frequently falls under
dynamic and the one which is stable falls under the static one. Here we have
tried to implement the manual system into the computer based system as it
overcomes most of the flow of the manual system.
12
Library Management System
Proposed System:
Module Description:
Administrator Module:
This is the main module in the proposed project. The administrator can read
and write information about any students. The administrator can also update,
create and delete the record of students as per requirement and implementation
plans. The Admin can generate Library Cards. Issuing of book and Retrieving
of book is done easier than before.
13
Library Management System
2) Online use of the library can be good feature for the Library
Management system.
3) Advanced fine payment system can be added.
Hardware Requirement
Software Requirement :
The system allows us to know the total no. of different subject and authors
presents and initially available in the library.
LIMITATIONS
There are not many limitations of the project but any of these limitations are not
affection the whole system. But anyhow it includes some limitations, which are
listed below:
14
Library Management System
DEFINITION OF PROBLEM
&
PROPOSED SOLUTION
15
Library Management System
DEFINITION OF PROBLEM
In manual system we generally use the issue cards for issuing the book or
if the card has been lost then we have to make a new card again which
take time and till then student have to wait and we have to search the
database again for the student information which is complicated.
You cannot keep track of how many times in the register of workers
unite to form a copy.
The handwriting and a few human errors, for example, can be caused by
an incorrect telephone number databases are not always reliable.
16
Library Management System
PROPOSED SOLUTION
The main thing is to identify the main features that involved in the proposed
system. In this scenario, there are two types of users; they are librarian &
student. The advantages of the computerized system over the manual system are
as follows:-
User friendly interface
Fast access to database
Less error
More Storage Capacity
Search facility
Quick transaction.
A database is there to store the user details & book details. This
information can be retrieved by the users as per their advantage.
Librarian can register students, issue or return books,
add/delete/search/edit books and student info.
All the manual difficulties in managing the Library have been rectified by
implementing computerization.
17
Library Management System
System Analysis
&
System Design
18
Library Management System
SYSTEM ANALYSIS
In this chapter, we will discuss and analyze about the developing process of
Library Management System including software requirement specification
(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 requirement before the developing process
is carried out. Besides that, existing vs proposed provides a view of how the
proposed system will be more efficient than the existing one.
GENERAL DESCRIPTION
PRODUCT DESCRIPTION:
Library Management System is a computerized system which helps
user(librarian) to manage the library daily activity in electronic format. 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 effectively
and timesaving.
PROBLEM STATEMENT:
The problem occurred before having computerized system includes:
File lost
When computerized system is not implemented file is always lost because of
human environment.Some times 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 accdent like spilling of water by some member on file
accidentally.Besides some natural disaster like floods or fires may also damage
the files.
19
Library Management System
SYSTEM OBJECTIVES
Save time Librarian is able to search record by using few clicks of mouse
and few search keywords thus saving his valuable time.
SYSTEM REQUIREMENTS
EFFICIENCY REQUIREMENT
When a library management system will be implemented librarian and user
will easily acess library as searching and book transaction will be very faster .
RELIABILITY REQUIREMENT
The system should accurately performs member registration ,member
validation ,report generation, book transaction and search
USABILITY REQUIREMENT
20
Library Management System
The system is designed for a user friendly environment so that student and staff
of library can perform the various tasks easily and in an effective way.
ORGANIZATIONAL REQUIREMENT
IMPLEMENTATION REQUIREMNTS
In implementing whole system it uses html in front end with php as server side
scripting language which will be used for database connectivity and the backend
ie the database part is developed using mysql.
DELIVERY REQUIREMENTS
The whole system is expected to be delivered in six months of time with a
weekly evaluation by the project guide.
FUNCTIONAL REQUIREMENTS
NORMAL USER
USER LOGIN
Description of feature
This feature used by the user to login into system. They are required 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 user is allowed to not
enter the system.
Functional requirements
User id is provided when they register
The system must only allow user with valid id and password to enter
the system
The system performs authorization process which decides what user level
can acess to.
The user must be able to logout after they finished using system.
Functional requirements
System must be able to verify information
System must be able to delete information if information is wrong
21
Library Management System
SEARCH BOOK
DESCRIPTION OF FEATURE
This feature is found in book maintenance part . we can search book based on
book id ,book name , publication or by author name.
Functional requirements
System must be able to search the database based on select search type
System must be able to filter book based on keyword enterd
System must be able to show the filtered book in table view
DESCRIPTION OF FEATURE
This feature allows to issue and return books and also view reports of book
issued.
Functional requirements
System must be able to enter issue information in database.
System must be able to update number of books.
System must be able to search if book is available or not before issuing
books.
System should be able to enter issue and return date information.
EVENT ADDITION
DESCRIPTION OF FEATURE
This feature allows teacher and student to add information about various
workshops being conducted in college and colleges nearby.
Functional requirements
System should be able to add detailed information about events .
22
Library Management System
This section describes the software and hardware requirements of the system
SOFTWARE REQUIREMENTS
Operating system- Windows 7 is used as the operating system as it is
stable and supports more features and is more user friendly
Database MYSQL-MYSQL is used as database as it easy to maintain and
retrieve records by simple queries which are in English language which
are easy to understand and easy to write.
Development tools and Programming language- HTML is used to write
the whole code and develop webpages with css, java script for styling
work and php for sever side scripting.
HARDWARE REQUIREMENTS
Intel core i5 2nd generation is used as a processor because it is fast than
other processors an provide reliable and stable and we can run our pc for
longtime. By using this processor we can keep on developing our project
without anyworries.
Ram 1 gb is used as it will provide fast reading and writing capabilities
andwill in turn support in processing
Existing system does not have any facility of teachers login or student
login where as proposed system will have a facility of student login as
well as teacher’s login
Existing system does not have a facility of online reservation of books
whereas proposed system has a facility of online reservation of books
Existing system does not have any facility of online notice board where
description of workshops happening in our college as well as nearby
colleges is being provided.
Existing system does not has any option of lectures notes uploaded by
teachers whereas proposed system will have this facility
Existing system does not have any facility to generate student reports as
well book issue reports whereas proposed system provides librarian with
a tool togenerate reports
Existing system does not has any facility for book request and
sugeestionswhere as in proposed system after logging in to their accounts
23
Library Management System
Front end
The front end is designed using of html , Php ,css, Java script & angular.
HTML- HTML or Hyper Text Markup Language is the main markup
language for creating web pages and other information that can be displayed
in a web browser.HTML is written in the form of HTML elements consisting
of tags enclosed in angle brackets (like <html>), within the web page
content. HTML tags most commonly come in pairs like <h1> and </h1>,
although some tags represent empty elements and so are unpaired, for
example <img>. The first tag in a pair is the start tag, and the second tag is
the end tag (they are also called opening tags and closing tags). In between
these tags web designers can add text, further tags, comments and other
types of text-based content.
CSS- Cascading Style Sheets (CSS) is a style sheet language used for
describing the look and formatting of a document written in a markup
language. While most often used to style web pages and interfaces written
in HTML and XHTML, the language can be applied to any kind
of XML document, including plain XML, SVG and XUL. CSS is a cornerstone
specification of the web and almost all web pages use CSS style sheets to
describe their presentation.CSS is designed primarily to enable the
separation of document content from document presentation, including
elements such as the layout, colors, and fonts.
24
Library Management System
25
Library Management System
27, 2003, by its founders, Matt Mullenweg and Mike Little,as a fork of
b2/cafelog. WordPress is released under the GPLv2 (or later) license from the
Free Software Foundation.
SYSTEM DESIGN
Table Design
Wp_user Table:
user_login Varchar(500) InUse
user_pass Varchar(500) InUse
user_nicename Varchar(500) InUse
user_email Varchar(500) InUse
user_url Varchar(500) Future Prospect
user_registered Datetime Future Prospect
user_activation_key Varchar(500) Future Prospect
user_status Int(11) InUse
display_name Varchar(500) InUse
26
Library Management System
Wp_Option Table:
option_id Int(11) InUse
option_name Varchar(500) InUse
option_value longtext InUse
tblbooks Table:
Id Int(11) InUse
ISBN Varchar(500) InUse
BookTitle Varchar(500) InUse
BookDesc Varchar(500) InUse
Category Varchar(500) InUse
Author Varchar(500) InUse
BookPublisher Varchar(500) InUse
MainUrl Varchar(500) Future Prospect
MainUrlId Varchar(500) InUse
Price Int(11) InUse
Qty Int(11) InUse
Borrowed Int(11) InUse
AddedOn Date InUse
AddedBy Varchar(500) InUse
tblborrowed Table:
Id Int(11) InUse
BookId Int(11) InUse
StudentId Int(11) InUse
Notes Varchar(500) InUse
DateBorrowed Varchar(500) InUse
DateToReturn Varchar(500) InUse
DateReturned Varchar(500) InUse
DelayedDay Int(11) InUse
ReturnStatus Int(11) InUse
Fine Int(11) Future Prospect
AddedOn Date InUse
27
Library Management System
TblCourse Table:
id Int(11) InUse
Coursename Varchar(500) InUse
TblYears Table:
id Int(11) InUse
Yearsname Varchar(500) InUse
tblStudents Table:
Id Int(11) InUse
StudentId Int(11) InUse
StudentPic Int(11) InUse
FirstName Varchar(500) InUse
LastName Varchar(500) InUse
Address Varchar(500) InUse
Zip Varchar(500) InUse
State Varchar(500) InUse
City Varchar(500) InUse
Phone Varchar(500) InUse
Email Varchar(500) InUse
Course Int(11) InUse
LevelIndex Int(11) InUse
Note Varchar(500) InUse
AddedBy Varchar(500) InUse
AddedOn Varchar(500) InUse
Password Varchar(500) Future Prospect
Active Int(11) InUse
tblSubbooks Table:
28
Library Management System
Id Int(11) InUse
BookId Varchar(500) InUse
Available Int(11) InUse
ParentBookID Varchar(500) InUse
Active Int(11) InUse
METHODOLOGY ADOPTED,
29
Library Management System
SYSTEM IMPLEMENTATION
&
DETAILS OF
HARDWARE & SOFTWARE
METHODOLOGY ADOPTED
As per the project management there should be a proper selection of the
methodology so on that contrast we have to select the methodology for our
project i.e. Library Management System. Basically there are two types of
methodology used for the projects Structured System Analysis and Design
Methodology and Object Oriented Methodology. We have chosen Object
Oriented Methodology.
30
Library Management System
32
Library Management System
Use-case Modelling:
First adopted by Jacobson et al. (1992), use-case modelling is developed
in the analysis phase of the object-oriented system development life cycle.
Use-case modelling is done in the early stages of system development to help
developers gain a clear understanding of the functional requirement of the
system, without worrying about how those requirements will be implemented.
A use-case is a representation of a discrete set of work performed by a use (or
another system) using the operational system (). A use-case model consists of
actors and use cases. An actor is an external entity that interacts with the
system and a use case represents a sequence of related actions initiated by an
actor to accomplish a specific goal (Hoffer et al. 2002).
Class Modelling:
There are many new terms in object-oriented approach. Some have
already been introduced above. An object is the most fundamental element in
OO approach, which has a well-defined role in the application domain, and
has state, behaviour, and identity. A class is a set of objects that share the
same attributes, operations, methods, relationships, and semantics. A class
may use a set of interfaces to specify collections of operations it provides to its
environment.
Object modelling or class modelling is the key activity in object-oriented
development. If the use cases contain errors, then all is not lost. If the class
model contains errors then all may well be lost. The quality of the resulting
system in object-oriented development is essentially a reflection of the quality
of the class model. This is because the class model sets the underlying
foundation upon which objects will be put to work. A quality class model
should provide a flexible foundation upon which systems can be assembled in
component-like fashion. A poor class model results in a shaky foundation
34
Library Management System
upon which systems will grind to a halt and buckle under the threat of change
(Artisan 2001).
Benefits of Object-Oriented Approach:
Object-oriented databases make the promise of reduced maintenance,
code reusability, real world modelling, and improved reliability and flexibility.
However, these are just promises and in the real world some users find that the
object-oriented benefits are not as compelling as they originally believed. For
example, what is code reusability? Some will say that they can reuse much of
the object-oriented code that is created for a system, but many say there is no
more code reusability in object-oriented systems than in traditional systems.
Code reusability is a subjective thing, and depends heavily on how the system
is defined. The object-oriented approach does give the ability to reduce some
of the major expenses associated with systems, such as maintenance and
development of programming code. Here are some of the benefits of the
object-oriented approach:
Easy Debugging
If a particular object turns out to be a problem, you can simply remove it
from your application and plug in a different object as its replacement. This is
analogous to fixing mechanical problems in the real world. If a bolt breaks,
you replace it, not the entire machine.
Investigation Techniques
Only making the project is not only the task it requires removing the errors and
making the project more efficient and flexible. After throwing the project to
the market the information about the updation is only be retrieved by
following some investigation technique.
Basically there are Four techniques by which information can be gathered they
are as follows:-
Observation
Interview
35
Library Management System
Document Analysis
Questionnaire
Out of these four techniques, we had chosen the technique of interview and
questionnaire for the development of our project. Since this all activity has its
own features of finding the development facts but we have selected the
technique i.e. Interview and Questionnaire that favours the economical and
projects scheduled time. Following are reasons with advantage for selecting
these techniques.
We had selected Interview and questionnaire as an investigation technique
because it has more advantage over other techniques. Some of them are
follows:-
Disadvantages of Observation Method
1.The most limiting factor in the use of observation method is the inability to
observe such things such as attitudes, motivations, customers/consumers state
of mind, their buying motives and their images.
2.It also takes time for the investigator to wait for a particular action to take
place.
3.Personal and intimate activities, such as watching television late at night, are
more easily discussed with questionnaires than they are observed.
4.Cost is the final disadvantage of observation method. Under most
circumstances, observational data are more expensive to obtain than other
survey data. The observer has to wait doing nothing, between events to be
observed. The unproductive time is an increased cost.
RAM 100MB
Software Requirement :
37
Library Management System
FEASIBILITY
ANALYSIS
And for the System to be act as worth-while it should passed through some test
that examine that it should proceed further or not. This series of test is
commonly known as feasibility study on the system and it plays a very vital role
for every system projects. Feasibility studies undergo four major analyses to
predict the system to be success and they are as follows:-
5. Operational Feasibility
6. Technical Feasibility
7. Schedule Feasibility
8. Economic Feasibility
39
Library Management System
40
Library Management System
41
Library Management System
The essential questions that help in testing the operational feasibility of a system
include the following:
Is the project feasible within the limits of current technology?
Does the technology exist at all?
Is it available within given resource constraints?
Is it a practical proposition?
Manpower- programmers, testers & debuggers
Software and hardware
Are the current technical resources sufficient for the new system?
Can they be upgraded to provide to provide the level of technology
necessary for the new system?
Do we possess the necessary technical expertise, and is the schedule
reasonable?
Can the technology be easily applied to current problems?
Does the technology have the capacity to handle the solution?
Do we currently possess the necessary technology?
Automated library system deals with the modern technology system that needs
the well efficient technical system to run this project. All the resource constrains
must be in the favour of the better influence of the system. Keeping all this facts
in mind we had selected the favourable hardware and software utilities to make
it more feasible.
Recommending the Hardware Part:-
43
Library Management System
Recommended Software:-
The Following software is used for the development of the System:-
Economic Feasibility:-
Economic analysis could also be referred to as cost/benefit analysis. It is the
most frequently used method for evaluating the effectiveness of a new
system. In economic analysis the procedure is to determine the benefits and
savings that are expected from a candidate system and compare them with
costs. If benefits outweigh costs, then the decision is made to design and
implement the system. An entrepreneur must accurately weigh the cost versus
benefits before taking an action.
Possible questions raised in economic analysis are:
Is the system cost effective?
44
Library Management System
The concerned business must be able to see the value of the investment it is
pondering before committing to an entire system study. If short-term costs
are not overshadowed by long-term gains or produce no immediate reduction
in operating costs, then the system is not economically feasible, and the
project should not proceed any further. If the expected benefits equal or
exceed costs, the system can be judged to be economically feasible.
Economic analysis is used for evaluating the effectiveness of the Proposed
System. The economical feasibility will review the expected costs to see if
they are in-line with the projected budget or if the project has an acceptable
return on investment. At this point, the projected costs will only be a rough
estimate. The exact costs are not required to determine economic feasibility.
It is only required to determine if it is feasible that the project costs will fall
within the target budget or return on investment. A rough estimate of the
project schedule is required to determine if it would be feasible to complete
the systems project within a required timeframe. The required timeframe
would need to be set by the organization.
45
Library Management System
Following is the figure showing the approx. amount of cost and benefit to the
system:
TANGIBLE COST:-
DEVELOPMENT COSTS
Windows Xp INR 1300
MS office INR 5000
Visual Studio INR 12000
Monitor INR 4000
Key Board INR 450
Mouse INR 200
Hard Drive INR 2000
Ram INR 600
OPERATIONAL COSTS
46
Library Management System
CHARTS
47
Library Management System
48
Library Management System
Pert chart
49
Library Management System
11 D 21
3. 5.
11 10 21
B
08
0 A 3
1. 2.
0 3 3
C
03
6 E 31 F 36 G 51 H 56 J 60
4.B 6. 7. 8. 9. 11
6 25 31 05 36 15 51 05 56 04 60
I
05
56
10
56
A – Introduction - 03
B – System Analysis A 08
C – Problem found B 03
D – Recommendations B 10
E – Selection of Methodology C 25
F – Feasibility Report E 05
I – Context Diagram J 05
50
Library Management System
The PERT chart is sometimes preferred over the Gantt chart, another popular
project management charting method, because it clearly illustrates task
dependencies. On the other hand, the PERT chart can be much more difficult to
interpret, especially on complex projects. Frequently, project managers use both
techniques.
FISHBONE / ISHIKAWA DIAGRAM
TAKE TIME
51
Library Management System
DFD
&
CLASS DIAGRAM
52
Library Management System
Context Diagram
Student Details STUDENT
LIBRARIAN Book Details
Course Details Book
Login Details Report
(Username +
Password)
Confirmation/
Rejection Requesting Book
Issue/Return
Updating & Initializing 0. Login Details
All books/Student details LIBRARY MANAGEMENT (Username + Password)
SYSTEM Confirmation/
Rejection
53
Library Management System
Level 0 DFD
1.0
Sends information
Login details 1.
(Username + Password) Acknowledgment Admin_Table
Login
Login details Sends information
Login Approval
Confirmation
2.0
Student Details
Librarian
Manage 2. User Login
Students
Report Student
Book details information
3.0
Student
Report Book details
Manage Books Updated
Book details+
Student details
Book details+
Student details 4. Book_Table
4.0
Receives Book
5. Issue_Table
5.0 Book Details
Status update Issue book updated
6. Return_Table
Overdue
Fine amount
6.0
Fine
Calculation
54
Library Management System
Delete Request
Book
book
information STUDENT
Book
information Search Request
Book code
Search Book Information
book
Book Information
Update Request
Student
ID
Information
updated
Update
Book
55
Library Management System
Username
+ Password
Register Student Details
Student
Confirmation/
Rejection
Details
User Login Details
Student details
Save
Student details
Student
Librarian Confirmation/Reord Details
added successfully
Delete Request
Student
information Search Request
Student Search
code Student Information
Student
Details
Student
information
Update Request
Student
ID
Information
Update updated
Student
Details
56
Library Management System
Level 2 DFD
Request
Forwarded
Confirm request
Library Management
Fill User Details System
Registration confirmation
Check details
Student
Forward details
Register student
Details Ask for verification
details
verification
Confirm details
57
Library Management System
Class Diagram
request
Students
+member id
+member name
+date of membership
-no of book issued
-book limit
student
+request for book()
+return book()
+pay bill()
+update book issue()
58
Library Management System
59
Library Management System
start
book no available
else
avialable
validate details
Not Valid
display "not a memeber"
Validate
Successfully
check for no of book issued
make transaction
Update Record
60
Library Management System
Check Avaliability
acknowledge avalibility
succesfully validated
Issue Book
update issue record
due date
issue book with due date
61
Library Management System
62
Library Management System
System
login
-End2
*
Maintain Student
Detials
-End16
*
-End14
Issue book
*
-End4 «uses»
check and update
add book
database
*
-End10
Search Book
*
-End18
*
Calculate Fine
63
Library Management System
ENTITY
1. Librarian
2. Student
3. Book
RELATIONSHIP
ATTRIBUTES
64
Library Management System
Student
* * Issues/returns *
Register
* Books View Book search
book
Delete *
*
Book title
.
ER-diagram of Library Management System.
65
Library Management System
Data Dictionary
66
Library Management System
SCREEN LAYOUT
67
Library Management System
Login Form
68
Library Management System
DashBoard Form
69
Library Management System
70
Library Management System
71
Library Management System
72
Library Management System
73
Library Management System
74
Library Management System
75
Library Management System
78
Library Management System
80
Library Management System
81
Library Management System
82
Library Management System
83
Library Management System
84
Library Management System
85
Library Management System
Student DashBoard
86
Library Management System
87
Library Management System
CODING
88
Library Management System
89
Library Management System
TESTING
90
Library Management System
SYSTEM TESTING
The aim of the system testing process was to determine all defects in our
project .The program was subjected to a set of test inputs and various
observations were made and based on these observations it will be decided
whether the program behaves as expected or not. Our Project went through two
levels of testing
1. Unit testing
2. Integration testing
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.
UNIT TESTING
Unit testing is undertaken when a module has been created and
succesfully reviewed .In order to test a single module we need to provide a
complete environment ie besides the module we would require
The procedures belonging to other modules that the module under test calls
Non local data structures that module accesses
A procedure to call the functions of the module under test with appropriate
parameters Unit testing was done on each and every module that is described
under module description of
Test For the Admin/Librarian module:
91
Library Management System
92
Library Management System
book
added
succefull
yy
93
Library Management System
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 student can search books, staff can generate library cards
and do book transactions. It also has a facility for student login where student
can login and can see status of books issued.
This system has been developed in a way to make it very user friendly.Any
person having a basic understanding of computer can run this system without
any pain.
This project is very useful in managing the record and other operation of library.
Moreover this project can be upgraded and changed according to the need of
user.
Thank you !
94
Library Management System
BIBLIOGRAPHY
This refers to the books/websites which were gone throught for completion of
this project reports.
SOME BOOKS REFERED
System Analysis & Design – Senn
Software Enginneering – Pressman
System Analysis & Design – Elias Award
Angular Js Complete Reference
95