Library Management System For Stanford.
Library Management System For Stanford.
STAKEHOLDERS
Library Staff ● Library staff should be able to search for books on the LMS by
search criteria like name of the book or author.
EXISTING SYSTEM
The paper based maintaining, organizing, and handling of countless books. Finding a
book based on requirement is all human dependent. Assuming a person who manages
books is on leave, no backup to understand, which book is placed in which section.
No Tracking of
Problem 1 Book Issued Entry in Register
time left
Time consuming
Report Calculate in
Problem 2 and chances of
Requirement Register
Human Error
PROPOSED SYSTEM
A library management system will enable the librarians to track the status of books
along with subscriptions & a complete user database. Right from managing the
acquisition, cataloguing to serial control, issued/borrowed books, returned books & due
date calculation, it helps in managing the daily work process in the library. The library
management system tracks all the books borrowed with due dates, fees, etc. This system
completely automates all your library’s activities.
It will simplify the daily operations of the library. The purpose of a library management
system is to manage & track the daily work of the library such as issuing books, return
books, due calculations, etc.
Flowchart for LMS
Internet
User
Above diagram depicts that books issuance made easy with added security and
immediate availability detection system. If book is issued, details are recorded, that is
stored in the DB. If book is bought, details are recorded in same DB. Easy access to
report any latest information related to the library inventory and transactions. A
scheduled job detects and trigger notifications to all the tenants to remind the time left
which enables them to be on time and return as per there convenience through drop
box station installed outside library.
DATA FLOW DIAGRAM
IN SCOPE
OUT OF SCOPE
● What are the facilities or features—for the library and the students—the are out of
scope or cannot be implemented now.
Wireframes:
Create sample wireframes for the system. Capture what screen will be show to the library
employees to create records for each book and at what stage in the system.
ER DIAGRAM FOR THE SOFTWARE
FUNCTIONAL REQUIREMENTS
● GEO redundancy
● RFID integration
● Internet browser
NON-FUNCTIONAL REQUIREMENTS
In House, Resource management system
System Requirement: Windows Server, RFID procurements, budget allocation.
Usability:
Environments