introduction
TRANSCRIPT
CHAPTER 1
INTRODUCTION AND PROBLEM DEFINITION
RFID (Radio Frequency Identification) is the latest technology to be used in different
industries for security and theft detection. Now a day this technology is widely used in the
library. In the library RFID based systems move beyond security to become tracking systems
that combine security with more efficient tracking of materials through out the library,
including easier and faster charge and discharge, inventory, and materials handling. The
application of this technology not only able to reduced the theft of books but also reduce the
manpower due to its self-check out and check in facility.
RFID is one of the automatic identification or auto ID systems like bar codes, smart
cards, and voice recognition etc., used to help machines identify objects. This technology is
often coupled with automatic data capture systems to identify objects and capture information
and transfer them into computer without data entry. Naturally, the aim of these systems is to
increase efficiency and reduce data entry. RFID has been around for long time with many
literatures published on it. This article is just a little extract of those, and hopes to give a high
level overview of the RFID technology, its characteristics, its applications, and its relevance
to Windows CE world. It is a generic term for technologies that use radio waves to
automatically identify people or objects.
Recently the use of RFID tags to track books, videotapes, CD-ROMs and other library
collection, components has risen in popularity. Libraries are finding that RFID technology
holds many advantages over traditional barcodes and antitheft tags and contributes to realize
considerable labor and cost savings. “The task of receiving, transporting, sorting and shelving
materials has exploded in recent years. Library staff size remains constant at best while
circulation and materials management continues to grow.
RFID provides a solution to automate much of these handling and return staff to the
business of customer service.”
1
1.1 Need of RFID In Library Management
Figure 1.1 : Need of RFID in Library Management
RFID is used in Library Management for providing security to it. Various transactions
on book can be done by using Barcode also, but then there wouldn’t be any security. It
provides security to both student and book by assigning RFID tag to it.
RFID is needed to be implemented in library since it reduces manpower by automation
and hence manual errors are reduced to certain extent.
Various transactions such as issue return book can be done at faster rate when RFID is
used. RFID provides various anti-collision algorithms that can reduce the reading error when
multiple books come into contact with the reader.
RFID provides security to the complete system since only librarian can access the
database and has the authority of looking at book inventory and transactions. So, no one else
other than librarian can access the database.
Hence RFID is required to be implemented into the Library Management for securing it
by using anti theft detection algorithms.
2
1.2 Advantages of RFID in Library Management
1.2.1 Rapid charging/discharging
The use of RFID reduces the amount of time required to perform circulation
operations. The most significant time savings are attributable to the fact that information can
be read from RFID tags much faster than from barcodes. That is due to the fact that the tags
can be read Regardless of item orientation or alignment (i.e., the technology does not require
line-of-sight or a fixed plane to read tags as do older technologies) and that several items in a
stack can be read at the same time. While initially unreliable, the anti-collision algorithm that
allows an entire stack to be charged or discharged now appears to be working well.
Finally, RFID tags can be read from distances of up to 24 inches distances far greater
than the use of light pens and barcode wands used with EM technology. That is what makes
RFID systems not only faster, but able to support electronic inventorying with handheld
devices.
Hence it does fast transactions in library and collision is also avoided. Since passive
tags are used, it does not require external battery for its charging.
1.2.2 High reliability
The readers are highly reliable. Several vendors of RFID library systems claim an
almost 100 percent detection rate using RFID tags. Anecdotal evidence suggests that is the
case whenever a reader is within 18 inches of the tags, but there appears to be no statistical
data to support the claims.
We are using the reader that provides 20 cm reading range. So data from the tag can be
read up to 20 cm range. It gives high reliability by giving correct information.
There are fewer false alarms than with older technologies once an RFID system is
properly tuned
RFID systems encode the circulation status on the RFID tag. This is done by
designating a bit as the "theft"(EAS) bit and turning it off at time of charge and on at time of
discharge. If the material that has not been properly charged is taken past the exit sensors, an
immediate alarm is triggered. Another option is to use both the "theft"(EAS) bit and the online
interface to an automated library system, the first to signal an immediate alarm and the second
to identify what has been taken.
3
1.2.3 High-speed electronic inventorying
A unique advantage of RFID systems is their ability to scan books on the shelves
without tipping them out or removing them to access the barcodes. A hand-held inventory
reader can be moved rapidly across a shelf of books at a distance of approximately six inches
to read all of the unique identification information. Using wireless technology, it is possible
not only to update the inventory, but also to identify items which are out of proper order.
1.2.4 Long tag life
RFID tags last longer than barcodes because nothing comes into contact with them.
Most RFID vendors claim a minimum of 100,000 transactions before a tag may need to be
replaced.
Once the tag is attached to the book, it can do minimum 100,000 transactions and
more than that .So for many years no need to think about replacing the tag.
1.2.5 Reduction in workplace injuries
Workplace injuries caused by the repetitive motions related to flipping books and
angling books under barcode readers cost libraries millions of dollars every year, and lead to
pain, limited physical range, and other problems familiar to a feminized workforce.
It gives very correct a result .Hence collision is avoided .There is minimum chance of
book lost.
1.2.5 Streamlined inventory management
Libraries spend a lot of money ensuring books are where they need to be. Books with
barcodes require humans to physically remove and handle every item to ensure it is in the
correct location. RFID offers the ability to analyze and correct library inventories without
handling the items.
1.2.6 Provide efficiency to collection management
Since no errors occur the system is efficient and the database is also consistent. Reader
reads the correct information and stores it into the database.
4
1.2.8. Provide wireless inventory management
There is no line of sight or no wired connection required between the tag and the
reader.Data is read by the reader using radio frequency waves captured by antenna of reader
and transmitted from the antenna of tag.
1.3 What we actually do?
1. Here RFID tag is used for books, students and the librarian.
2. When a book is issued / returned having RFID tag, reader reads the tag information and
database is updated automatically
3. While issuing book, Reader of RFID reads the information from book RFID tag. And
searches the relevant information regarding book in the database with library book
issue rules.
4. While returning of book, date of return is checked with the date on which he is supposed
to return in the database of student. If he has delayed then he has to pay fine as per
allotted. The fine paid by him is entered into the database by librarian.
5. Here RFID Reader is used to provide security, it provides facility to display message on
mobile phone if return date exceed & it also provide facility to student to access book
database in the campus of library.
6. Whenever librarian wants to log-in he /she will have to use his/her RFID card. Log-in and
Log-out details are automatically stored into the log database.
7. Searching of any student, book can be done very easily either by using his/her card, book
card respectively. And in case student want to search for book then he can do it by
entering any of the following fields i.e. book card no., author name, book name etc.
8. Student can also check the books issued by him, and his limit of issuing them, book return
date by simply scanning his card.
5
Reports are generated for student, book, book issue-return etc.
1.4 Problem Definition
“To implement Library Management Using RFID”. This system should provide
security to the library. Along with that it should also provide many facilities such as fast
searching of books/members, fast transactions etc. that makes the working of system efficient.
Library system provides many facilities for student, staff and other members for that
purpose we use RFID technique for issuing, renewing, updating database and provide
security. Here RFID tag is used for books and student when a book is issued / returned having
RFID tag reader reads the tag information and database is updated automatically.
RFID reader is used for reading RFID tag which is attached to book. To provide
security in library from thefting of book for that purpose we display message on screen that is
‘Book is misplaced’ and also student can access book database on any pc in library campus.
1.5 Organization of Report
Chapter 1: Introduction
In this chapter introduction about RFID ,its need in Library Management,key
issues and objective of area is seen.
Chapter 2: Literature Survey and Preliminary Survey
Study of previous systems that were used for managing library and how the current
System overcomes the problems found in them is specified.
Chapter 3: Systems Requirement and Specification
Current system requires some hardware and software for its working.Here
platform required for running the application and structure of team is stated.
6
Chapter 4: High Level Design
In this chapter cost of the project is estimated.For this COCOMO i.e. Constructive
Cost Model.It estimates cost in terms of lines of code , Number of team members and time
required for development of project.
Chapter 5: Project Planning
Here, schedule of the project is mentioned. This schedule is divided into semesters.
In each semester required work was completed.
Chapter 6: Risk Analysis
We have used GP-20 RFID reader for our poject.It gives 20 cm reading range that
is sufficient for library purpose. There are other readers also there in the market that provides
large range but cost is high.
Chapter 7: Detail Design
This system follows Object Oriented Approach.So, this chapter shows various
UML Diagrams such as Use Case, Class ,State Chart etc. .Entity Relationship(E-R) Diagram
specifies the relationships between various users(entities).
Chapter 8: Design Review
Detailed design is summarized in this chapter.
Chapter 9: Modeling
Here complete working is described.Hardware required for the system and
software platform is also mentioned. It shows the prototypes developed.
Chapter 10: Modeling Review
Review of Modelling chapter is described.
Chapter 11: Testing and Test Cases
It shows the various types of testing done on the system. It includes test cases for
each Module.
7
Chapter 12: Conclusion
It concludes that the current system is better from the previous and the traditional
Systems. But it is very much expensive.
8
CHAPTER 2
LITERATURE SURVEY AND PREFETCHING
PREFACE In this the complete survey of the existing system is done.What are the advantages in
using the and why there is a need for its replacement with the new technology is studied.
We have studied two systems-traditional manual system and the system using barcode.
2.1 Traditional System In traditional systems, everything was done by the human being. For complete
management of library it requires a great manpower. Since transactions are done manually in
this system ,there are more possibilities of errors. Here librarian had the responsibility of
maintaining book inventory database ,one more person was required to maintain the database
of issue/return of book ,then accountant was required for fin calculation and collection etc.
It requires less cost to implement the system.
2.1.2 Limitation It may happen that many student comes at the same time for either issuing or returning
the book, then collision may occur. Hence database may have some invalid entries into
the database.
If there is a great crowd ,then any member can take the book out of the library without the
permission of librarian.
Members have to wait for a long time for issuing /returning the book.
Librarian’s more time is wasted in performing transactions only. He can’t think about
library enhancement , increasing facilities etc.
Member’s time is wasted in searching book into the library.
Sometimes it may happen that the member searches the book and requests librarian for its
issue. Librarian searches for his record into the database and then gets that member can’t
issue more books. Hence wastage of member’s and librarian time.
9
2.2 Barcode SystemA Barcode is just a different way of encoding numbers and letters by using a
combination of bars and spaces of varying widths. This is just another way of entering data
into a computer. A bar code does not contain descriptive data. It is a reference number that a
computer uses to look up an associated record that contains descriptive data and other
important information. For example, a barcode found on a book does not contain the book
name, author, or price, instead it contains a 12 digit book_id.
This book_id is captured by the barcode reader and is decoded into the format that
computer can understand. When this number is scanned by the librarian at the check-out, it is
transmitted to the computer which finds the record associated with that book_id in the data
base.
The matching book record contains a description of the book, vendor name, price etc.
The computer instantly does an "availability" check and displays the result. It also subtracts
the quantity issued by the student. This entire transaction is done instantly. In a nutshell, a bar
code typically has ID data encoded in it, and that data is used by computer to look up all
specific information associated with the data.
2.2.1 Advantages Of Barcode Techniques
Transaction of book is done faster than the traditional system.
Barcodes are universally accepted because they are very inexpensive and there are
established standards for their use.
2.2.2 Disadvantages of Barcode Techniques
Barcode scanner scans only nearest barcode number. It has very short reading range.
It does not provide any security like RFID Scanner. Book can be taken out of library when
there is a crowd. It does not support Anti theft detection algorithms and Anti Collision
Algorithms.
The need for the bar code to be visible. Since it required lines of sight.
[1]Around 10% reading error. At the time of reading barcode, barcode reader can not scan
barcode properly. Since it gives error.
10
2.3 RFID Features and Benefits in Library Tags do not require “line of sight” to be read.
Tags can be read from a distance and from any orientation.
Tags can have read and write capabilities.
Tags can easily be embedded into different products.
Tags encrypt data, along with an unalterable unique identification number .
Tags provide permanent identification for the life of the product.
RFID tags for library items would be disabled after check-out.
Library databases are highly secure.
It’s too hard to use this information anyway.
CHAPTER 311
SYSTEM REQUIREMENT AND SPECIFICATION
3.1 Necessary Functions Reading tag
The reader sends a radio signal that is received by all tags present in the RF field
tuned to that frequency. Tags receive the signal via their antennas and respond by
transmitting their stored data. The tag holds a book_id. The read/write device receives the tag
signal via its antenna, decodes it and transfers the data to the computer system through a cable
or wireless connection.
Search
Book_id is searched into the computer and matched with the record. If book_id
matches with the record then it displays the output as “available”.
Display
Computer displays the list of available books on screen. it also displays whether a
member can issue more books or not. It shows the number of days delayed, issue/return date
from the database.
3.2 Desirable Functions
Security
This system provides security
Automation
Makes the system automated
CHAPTER 4
12
HIGH LEVEL DESIGN AND ESTIMATION
PREFACE
In this chapter project estimation is done on the basis of man power, lines of code, size
of development. This is required for computing the total cost of the project during planning
and deployment phase. For computing the LOC various models are being used such as
COCOMO model
4.1 Project Estimation
Effective software project estimation is one of the challenging and important activity
in software development. Proper project planning and control is not possible without sound
and reliable estimate.
The four basic steps in software project estimation are:
Estimate the size of development product .The units of measure are Lines of Code (LOC).
Estimate the effort in person-months or person-hours.
Estimate the scheduling calendar months.
Estimate the project cost in dollars (or local currency).
In this amount of work, resources and the time required to complete the project is
estimated. The metrics estimated will invariably change as time progress. This exercise will
help us to suitably distribute and allocate the work task equally among the members based on
the time line and way time allows.
4.2 Resources
The resources that would be utilized the project life cycle are:
Human Resources : The project team is comprised of 4(four) members.
Officially, the project is allotted 6 hours per week (h/w) over a period of roughly 8
months. Thus the available time period is:
6h/w * 4 person * 32 weeks = 768 man-hours
= 33 man-months
13
(@17 man-hours/month)
4.3 COCOMO Model
Constructive cost model is one of the most widely used and discussed software cost
estimation model. Our project is COCOMO model.the basic cocomo model complete software
development effort and cost as function of program size expressed in estimated line of code.
Table 4.1: Area in which project lies
Software project a b
b b
cb
d b
Organic 2.4 1.05 2.5 0.38
semidetached 3.0 1.12 2.5 0.35
embedded 3.6 1.20 2.5 0.32
Automated checking and result generation is software that is developed within a set of
tight hardware and software constraint. The basic cocomo model takes following equation:
Effort = a
bKLOC b
b
Duration = cbEffort
d b
COMPUTATION
Table 4.2: LOC Calculation
Function Estimated LOC
Module 1 600
Module 2 350
Module 3 430
14
Module 4 410
Module 5 210
Module 6 300
Module 7 350
Module 8 350
Total Line Of Code 3000
Effort =3.0*(3.0^1.12)
=10.26 person-month
Duration =2.5*(10.26^0.35)
= 5.64 months
Number of people recommended = Efforts/Duration
= 10.26/5.64
= ~ 3 people
Since there are 4 project members, project duration is reduced accordingly.
LOC based Estimation:
The average productivity for our product is: 600 LOC/per month
The labour rate estimated is: Rs.6600 per month
Thus the cost per line of code is: approximately Rs.11
Based on LOC estimated and historical productivity data,
Total estimated project cost is: Rs.40,500
15
CHAPTER 5
16
PROJECT PLANNING
PREFACE
Planning is the initial phase required for development of the project.It includes the
schedule that which task should start at what time and finish at what time.Schedule is
prepared as per the months in the project duration.
Table 5.1 Project plan
MODULE START DATE END DATE STATUS
Project research and
Development
15/06/2008 15/06/2008 Completed
Software
Requirement
Specification
23/07/2008 15/08/2008 Completed
UML Diagrams 23/09/2008 03/10/2008 Completed
Review of UML
Diagrams
05/10/2008 10/10/2008 Completed
Submission of Partial
Project Report
11/10/2008 18/10/2008 Completed
Studying
C#.NET2.0, MS-
Access 2007
01/01/09 05/01/09 Completed
Design
Designing Overall
structure of System
09/01/09 15/01/09 Completed
Development
17
Implementing Login
Module
17/01/09 20/01/09 Completed
Implementing
Barrower Module
21/01/09 31/01/09 Completed
Implementing Book-
issue Module
1/02/09 10/02/09 Completed
Implementing Book
Purchase Module
11/02/09 20/02/09 Completed
Implementing Book
Return Module
21/02/09 28/02/09 Completed
Implementing SMS
Module
01/03/09 03/03/09 Completed
Implementing Search
Module
04/03/09 10/03/09 Completed
Testing
Testing 1/01/09 10/03/09 Completed
Bug fixing 18/01/09 10/03/09 Completed
18
CHAPTER 6
RISK ANALYSIS
6.1 Risk Management
6.1.1 Risk Assessment
A risk is a probability that some adverse circumstance will occur. It is potential
problem- it might happen or it might not. But, regardless of outcome, it is really a good idea
to identify it, assess its probability of occurrence, estimate its impact and establish a
contingency plan should the problem actually occur. For good software project management,
understanding the risks and taking proactive measures to avoid or manage them is a key
element. Risk Management is concerned with identifying risks and drawing up plans to
minimize their effects on the project.
Risk involves two characteristics:
Uncertainty - The risk may or may not happen, i.e. there is no 100% risk problem.
Loss - If the risk becomes a reality, unwanted consequences or losses will occur.
There are different categories of risks and they are as follows
6.1.2 Project Risks
Project risks threaten the Project plan. If Project risk becomes real, it is likely that
project schedule will slip and cost will increase. Project risk identify potential budgetary,
schedule, personnel, resource, customer and requirement problems and their impact on a
software project.
6.1.2.1 Product Risks
Product risks affect the quality or performance of product. It is associated with overall
size of the software to be built or modified.
6.1.2.2 Technical Risks
Technical risks threaten the quality and timeline of the software to be produced. If it
becomes a reality, implementation may become difficult or impossible. Technical risks
identify potential design, implementation, interface, verification and maintenance problems.
Technical risks occur because the problem is harder to solve than we thought it would be.
19
6.1.2.3 Technology Risks
Technology risks are associated with the availability and quality of the tools to be used
to built the product. Resources required to build the software may prove insufficient.
6.1.2.4 Staff Size and Experience Risks
Staff size and experience risks are associated with the overall technical and project
experience of the software engineers who will do the work. Project members may get sick and
this would result in a delay in completion of their respective modules. The schedules might
slip as the team members are relatively inexperienced.
6.2 Customers characteristics
Customer characteristics risks are associated with the sophistication of the customer
i.e. it includes the GUI, whether it is user friendly and guides the user in an efficient manner
and also the developer’s ability to communicate with the customer in a timely manner.
6.3 Development Environment
Development environment risks are associated with the availability and quality of
tools to be used to build the product
6.4 Risk Mitigation, Monitoring And Management (RMMM) Plan
Risk Mitigation, Monitoring and Management mean risk avoidance. Avoidance is the
best strategy by adapting the proactive strategy to risk. The project manager should monitor
i.e. keep a check on the project to see whether the risk is becoming more likely or not. Risk
management comes into play when the mitigation efforts have failed and the risk has become
a reality.
Risk #1
Sophistication of the end user’s application program
Mitigation - Develop a front end that is both user friendly and covers all needs.
Monitor - Test the application with novice, expert and intermediate users.
Management - Customer should be notified about the limitations and the scope of the API.
20
Risk #2
Delay in completion of modules due to member being sick.
Mitigation - Keep work of all members documented.
Monitor - Review is made between members and ideas, thought, plans are discussed in
meetings.
Management - Shift one or more members to sick member’s module.
Risk #3
Schedule might slip due to inexperience
Mitigation - The planned schedule should be followed strictly.
Monitor - Check whether work is going according to time.
Management - Add more members to the project or increase the working hours of already
working people.
Risk #4
Resources might prove insufficient
Mitigation - Gather all the resources that are required and check whether they are feasible.
Monitor - Check at any point of time whether the resources allocated are less and whether
more resources will be required.
Management - Increase the fund that is allocated to the resources or try and adjust with the
existing resources.
6.5 Hardware
These can also be used instead of the GP-20 and proximity passive tags. But due to
high cost they are not used.
GP 20 : This is the reader that provides reading range upto 20cm range.It receives the radio
waves transmitted by the antenna of the tags. It stores this information into the database.
RFID tags : It stores the unique number.
21
CHAPTER 7
DETAILED DESIGN
PREFACE
In Design phase actually modules are designed using the software.In this GUI is given
the first importance.It should include all the modules that satisfies the user requirements.This
is the only thing through which user interacts with the system.
7.1 Approaches for designThere are two approaches for designing.
7.7.1 Sructural
7.7.2 Object oriented
Our project is based on Object Oriented approach. In OO A, UML diagrams are
drawn.
7.2 UML Diagrams
Diagrams have been drawn in Unified Modeling Language using Rational Rose
Software. These diagrams have been classified under following 5 fields:
1) The User View : It includes use case diagrams.
2) The Structural View : It includes class diagram and object diagram.
3) Behavior View : It includes the sequence diagram, the collaboration diagram, the
machine State Chart diagram and the activity diagram.
3) Implementation View : It includes the component diagram.
4) Environment View : It includes the deployment diagram.
22
7.2.1 Use Case Diagram
Figure 7.1: Use-case Diagram
23
7.3.2 Class Diagram
Figure 7.2: Class Diagram
24
7.3.3 Package Diagram
Figure 7.3: Package Diagram
25
7.3.4 Activity Diagram
Figure 7.4: Activity Diagram
26
7.3.5 Sequence diagram for issuing book from library
Scenario
When member enters into the library, his/her I-card information is captured by reader and
is matched with the database server. If server validates it, then member enter book-id into the
system. System will search into database for its availability. If it is available then it checks
that whether user can issue more books or not. If yes then member can issue it else leaves
from library.
Figure 7.5: Sequence Diagram for issuing book
27
7.3.6 Sequence diagram for returning book into the library
Scenario
When member enters into the library, his/her I-card information is captured by reader
and is matched with the database server .Member will return the book to librarian. Librarian
will check the database and if delayed then he/she pays fine and leaves from library or can do
more transaction.
Figure 7.3.6: Sequence Diagram for returning book
28
7.3.7 Collaboration diagram for issuing book from library
Figure 7.7: Collaboration Diagram for issuing book
29
7.3.8 Collaboration diagram for returning book into the library
Figure 7.8: Collaboration Diagram for returning book
30
7.3.9 State chart diagram
Figure 7.9: State Chart Diagram
31
7.3.10 Component diagram
Figure 7.10: Component Diagram
32
7.3.11 Deployment diagram
Figure 7.11: Deployment Diagram
7.3 E-R Diagram
The Entity-Relationship (E-R) data model facilitates database design by allowing
specification of an enterprise schema that represents the overall logical structure of database.
The E-R model is very useful in mapping the meaning and interaction of real world enterprises
into conceptual schema.
In this E-R diagram we have used four entities such as Magazine, CD, Accession
register and member, which contains information about student and staff. Transaction is
considered as a aggregation relationship, as all entities have transactions.
CD-transaction and magazine-transaction follows one-to-one relationship.
33
Accession register –member has many-to-one relationship.
Figure 7.12: E-R diagram of Library Management Using RFID
34
7.4 Data Dictionary
7.4.1 Borrower Database
In this table it stores all the information of borrower i.e. borrower id, First name,
Middle name, Last name, Street address, Zip code ,Email, contact no.etc. using this
information you can perform issue/return transaction easily.
Table 7.13 : Borrower Database
7.4.2 Book Database
In this table store all the information about the books i.e. Book ID, ISBN no.,
Author, Book Title, Price, Quantity etc. This information is used at the of
issuing/returning book, searching book.
35
Table 7.14 : Book Database
7.4.3 Borrowed Database
In this table stored the information about borrowed records such as Book no.,
Borrower ID, Date borrowed, Due date, Return date, Fines , Added date etc. At the
time of returning book all the information is stored in this table automatically.
Table 7.15 : Borrowed Database
7.4.4 Category Database
In this table stored information about the which types of books are available in the
library such as Category name, Category Description Added by, Add date etc.
when student issue the book then choose the category of book from this table.
36
Table 7.4 : Category Database
7.4.5 Course Database
In this table store the information about courses such as Course name, Course
description, Added by, Add date etc. when librarian enter the borrower information
at that time librarian choose the course information from this table.
Table 7.15 : Course Database
7.4.6 Level Database
This table store level of student such as Level name, Added by, Date adds etc.
Table 7.16 : Level Database
7.4.7 Librarian Database
This table stores the information about the librarian such as Librarian ID, Name,
Street Address, Zip code, Contact number, Email, Username, Password, IP
Address etc. when librarian login into the system at that time it check the
password, username and IP address with this stored information.
37
Table 7.17 : Librarian Database
7.4.8 Zip code
In this table stores information about the Zip code such as City Town, Province,
Zip code, Added by, Date add etc. when librarian enter the borrower information at
that time librarian choose the Zip code from this table.
Table 7.18 : Zip code Database
7.4.9 Login Database
When librarian login into the system then Librarian ID, login time, logout time all
are stored in this table.
Table 7.19 : Login Database
38
CHAPTER 8
REVIEW OF DESIGN
Design phase includes that how the system is drawn, which approach does it follows
and how the database is organized.
8.1 Approach
This project follows the Object Oriented Approach. System is represented by using
structural and behavioural diagrams. Structural diagrams are class, component, deployment,
package. Behavioural diagrams includes use case, state , activity.
Structural diagrams shows the structure of the system and behavioural diagrams
indicates that how the system flow will occur.
The complete system flow is shown by using use case diagram.Various classes in
class diagram represents the total entities. State chart diagram implies the different states from
which an object passes.
8.2 E-R Diagram
This show the relationship between entities.It represents that how the entities work
into the system and how they are interrelated.Relationship can either be one-to-one,one-to-
many or many-to-one or none.
Entities require several fields for their description.These include keys such as
primary ,foreign keys.
In this system CD, Member, Magazine and Accession Register are entities.
8.3 Data Dictionary
Database is required for storage of information, transactions etc. Here for this
purpose MS-Access is being used. Various databases such as borrower, book issue/return etc
are developed.
39
CHAPTER 9
MODELLING
9.1 Working Of the Complete System
The first step is to assign the tags to the books, members and the librarian.
Tag contains the unique identity number.
When member enters the library, he/she searches the book at the helpdesk. For
searching he must know either the name or author of the book. He retrieves the information
that whether the book is available into the library or not.
If he wants to issue the book and if the book is available then he takes the book
and issues it with the help of the librarian. For issuing it, it is checked that whether his book
issue limit is not already maximum. If it is so, then he first will have to return the book.
If the book is delayed then on the last date a SMS is sent on to the member’s
phone that he should return the book today else he will have to pay the fine.
If the book is already delayed then automatically fine is calculated on his name
and whenever he returns the book, he has to pay fine.
For any kind of announcement, an e-mail can also be sent to the member by the
librarian.
9.2 Algorithms
We have used algorithms for issuing, returning books.
9.2.1 Algorithm for book issue
Step 1 :Member enters into the library.
Step 2:He searches for the book by entering the book name or author.
Step3:If it is present then he checks for the book limit.If limit is not exceeded then he
issues the book else he have to return any of the previously issued book.
Step4:If return date exceeds then SMS is sent.For due date he will have to pay fine.
40
Step 5:After issuing book he leaves the library.
9.2.2 Algorithm for Returning book
Step 1 :Member enters into the library.
Step 2: He returns the book.
Step 3:Librarian checks the due date.If due is there,then member pays fine.
Step 4: He returns the book and leaves the library.
9.3 Software Used
C#.NET 2.0 : This is used for front end i.e. for GUI.
MS-Access 2007: This is used as a back end for database.
9.4 Hardware
RFID Reader GP-20 :It reads the information from the tag using radio 9.2 frequency
upto 20 cm range only.
9.5 Modules
Overall working is divided into following 7 modules.
1. Login
This module has been designed for authentication of administrator. He will enter the
password and if password is correct then he will be considered as an administrator. His
login time is also maintained into the database.
Functions:
Check username ()
Check password ()
Check IP address ()
2. Borrower
This module has been design for displaying all the information of library members i.e.
41
Personal, academic, issue or return record etc.
Functions:
Search record ()
Update record ()
Reload record ()
Display record ()
3. Books
It stores all the information about book. Those books that are newly purchased are
given the unique accession no. and are then entered into the database. And database is
updated.
Functions:
Add book ()
Delete book ()
Search book ()
Update book record ()
Display book info ()
4. Book issue record
Book issue record will update the database as per transactions done. This database also
makes use of student/staff record, accession record. Books are only issued when user
has permission for it. This also maintains book return database and fine.
Functions:
Issue book ()
Return book ()
Renew book ()
Update record ()
5. Book purchase record
Whenever any book is purchased, then that book’s entry is made in this database. And
it has brought to library, and then accession register is updated by making the entry of
newly purchased book.
Functions:
42
Display book info ()
Search ()
Update record ()
6. Book Return record
Whenever any book is return, then that book’s entry is made in this database and then
updates the record of library member and then takes fine if not return within time
period.
Functions:
Search record ()
Calculate fine ()
Update record ()
7. SMS module
This module is used to send sms to library member if returning date is close and if any
fine.
Functions:
Search member ()
Send sms ()
8. Search module
In this module search the member info, zip code, book info or many other information.
9.6 Prototype And User Interface Screen
It shows the different prototypes designed into the system and the graphical User
Interface.
43
Figure 9.1: Login Screen
Figure 9. 2: MDI Form
44
Figure 9. 3: Books Records Form
45
Figure 9. 4: Borrower-info Form
46
Figure 9. 5: Issue Book-info Form
47
Figure 9. 6: Return Book-info Form
48
`Figure 9.7: SMS Form
49
Figure 9.8: Librarian info Form
50
Figure 9.3.9: Library Profile
Figure 9.9: Helpdesk
51
CHAPTER 10
MODELLING REVIEW
In modeling, flow of the complete project is described. A tag is assigned to the
member, book, and to the librarian. RFID reader captures the information from the tag
whenever it is scanned. This information is stored into the database. RFID provides security to
the library.
Algorithms are used for the anti collision and anti theft detection. Anti collision
algorithms avoids collision when multiple tags come into contact at the same time.
Anti theft detection algorithms provides security to the system.If any book is taken out
of the library without issuing it then these algorithms helps to detect it.
Software is used for user interface and storage purpose.For GUI C#.NET is used since it
has many functionalities such as crystal reports , list view that gives a great interaction to the
use with the system.For storage purpose MS Access 2007 is used. It provides advanced
networking functionalities.
Hardware is required for provideng the required environment to the system for
execution.This system uses RFID reader GP 20 for scanning the tag and retrieving the
information from the tag. Passive tags are used for storing information.
Prototypes are designed for user interface.They are designed in C#.NET and stores the
information in MS ACCESS.These helps user to understand that what exactly he is
doing.These includes the complete information that is required by him.
52
CHAPTER 11
TESTING
PREFACE
Testing is the phase that starts from the requirement and gathering phase and
continues till deployment phase.First testing is the unit testing that is done on a single
module.Various other testing are integration,black and white box.Testing is required for
checking correctness,completeness and quality of software.Debug is used for checking of
bugs,defects.It increases the quality of the product.
11.1 Formal Technical Reviews
In doing these Formal Technical Reviews, all the project members were in the review
team.
We had worked for around 10 hours each week for the project excluding the studies
we made for it. In these hours the formal reviews were also done. In these Formal technical
reviews there are some procedures we had followed. As per the routine of the we met twice a
week. The components being reviewed at each meeting.
As per the progress we presented the work done by each and chose the best. We work
on with it till all the requirements are met. Then we tested the component for each and every
requirement. After the testing we took decision whether to consider it or discard it. But time
we amended it and made the component better. But when there are more failures then success
then we discarded with and started it all over again.
Each time reviews decisions and suggestions were documented. This test report is a
part of all the documentation done during the reviews and decisions.
53
11.2 Test Plan
11.2.1 Introduction
Human –computer interaction currently faces the challenge of tacking advantage of
new technologies, which efficiently use the capabilities of the computing systems of today
and more efficiently complete user requirement. We identify that how RFID Reader is useful
in library system. This paper consists of a survey of RFID Reader and Tag. There is no doubt
that this software is going to be the way of the future. RFID Reader and Tag improve the
library system perform some operation atomic. RFID Reader is replaced by old Barcode
Scanner because RFID Reader is moer efficient and easily handle.
11.2.2 Testing Performed
At the development site first we performed Unit Testing.This is done on each module
individually.
After that Black Box Testing. Black box testing there is no need to view coding part. It
focuses on functional requirement of the software. In block box we give the input & check
whether output is proper or not.
After Black box testing we test modules using Regression testing. In Regression testing
we test whether changed component has introduced any error in unchanged component.
Regression testing focuses on retesting after changes are made.
After Black box testing we conduct system testing. It has to be tested against the system
specification to check it delivers the required features. It verifies the entire project after
integrating all software & hardware component and validates it according to original project
requirements.
White box testing is performed regularly whenever their was any exception or error in
output obtained from the above testing. During this we tested the code against the
requirements.
54
11.3 Test Cases
Table 11.1 : Test cases
Sr.No Test Cases Expected Result Actual result
Login Module
1 Enter the username ,
password and IP
address then click
connect
MDI form should be
open
MDI form is open
2 Enter the incorrect
username , password
and IP address then
click connect
MDI form should be
open
MDI form is not open
3 Enter the incorrect
username and
password then click
connect
Display the message
enter correct
username and
password
Display same
message
Borrower Record
1 Click on drop down
menu
Form should be open Form is open
2 Click on new button New form should be
open
New form is open
3 Click on borrower id
and book id
Can’t enter any
message into text box
Can’t enter any
message
Books Record
1 Click on new button
for issuing new book
New window should
be open
New window open
2 Enter book no. and User enter id and User can’t enter they
55
borrower ID number only scan
Books Return record
1 Click on return
button
New window should
be open
New window open
2 Click on return
button
New window should
be open with all info
of selected student
New window is open
with all information
3 Calculate fine User have to
calculate fine
Calculate fine
automatically not
manually
SMS module
1 Click on send SMS SMS window should
be open
SMS window is open
2 Enter text and
number then click on
send
Message should be
send
Message is send
3 Click on send button
without entering any
data
Message should be
send
Display message
enter data
Search
1 Click on search
button
New window should
be open
New window is open
2 Enter data in search
for text and look is
empty
Search should be
start
Display message
enter look
3 Enter data in search
for text and look is
Display message look
is empty
Display message
56
empty
CHAPTER 12
57
CONCLUSION
RFID (Radio Frequency Identification) is the latest technology to be used in library
Management. Unlike EM (Electro-Mechanical) and RF (Radio Frequency) systems, which
have been used in libraries for decades, RFID-based systems move beyond security to become
tracking systems that combine security with more efficient tracking of materials throughout
the library, including easier and faster charge and discharge, inventorying, and materials
handling.
RFID in library management reduces manual work. It leads to automation and
improves security. It ensures the correct transactions.It provides security by providing tags to
the member and book.It does not require line of site,hence reduces error.
RFID is one of the automatic identification or auto ID systems like bar codes, smart
cards, and voice recognition etc., used to help machines identify objects. This technology is
often coupled with automatic data capture systems to identify objects and capture information
and transfer them into computer without data entry. Naturally, the aim of these systems is to
increase efficiency and reduce data entry. RFID has been around for long time with many
literatures published on it. This article is just a little extract of those, and hopes to give a high
level overview of the RFID technology, its characteristics, its applications, and its relevance
to Windows CE world. It is a generic term for technologies that use radio waves to
automatically identify people or objects.
REFERENCES
58
[1] AtlasRFIDSolution.com/RFID-vs-barcode.asp
[2] Business-IT Alignment, September2008
[3] Christian Nagel, Bill Evjen, Jay Glynn, Karli Watson, Morgan Skinner,” C# 2005 with
.NET 3.0” Wrox Publication,ISBN:81-265-1332-2
[4] Patrick Dalton, Paul Whitehead, Kogent Solutions Inc “SQL Server 2005” 2007Edition
[5] Abraham Silberschatz, Henry F. Korth, S. Sudarshan “Database System Concept” Fifth
Edition
[6] http: //www.rfid.com/library management
[7] http: // www.traze.in
[8] http: // www.rfid-library.com/rfideng.swf
59