Stanford Library

By S. Vaishnavi-Cohort 2

STAKEHOLDERS

ACTOR What he can do on the Software Created

Student ● The student can easy search for the desired material via web
access and onsite
● The student can easily return the books at the required return
stations
● The student can find the details of the materials issued under
their ID and their due details

Library Staff ● The library staff can easily search for the desired material via
web access and onsite
● The library staff can easily replace the book taken with other
books
● The library staffs can easily calculate the due dates of the
materials
● The library staff can determine the accurate penalty
calculations for the client
● The library staff can generate materials reporting

Management  The management should maintain the database

 Database should be secured and should grant access via
multiple entry points for student and staff users
 Reporting Interface will allow users to access material data via
standard and Ad Hoc reporting
 User Interface will allow users to manage material access
regarding:
a) Search and locate materials
b) Penalty calculations
c) Determine return date
d) Issue and return materials

PROBLEM DEFINITION AND SOLUTION

LMS system is needed for library for the following reasons:

a) Reduces the cost for staffing, material tracking and maintenance
b) Reputational benefit for school and management
c) Trend analysis
 d) Materials data reporting

LMS system is needed for students for the following reasons:

a) Learning experience, knowledge ain and ease of use
b) Avoid penalty
c) Time reduction for accessing, managing, and returning

Advantages of LMS

Advantages of Library Management System for the library:

a) Cost reduction
b) Improve student engagement
c) Generates dynamic report
d) Up to date records

Advantages of Library Management System for student:

a) Improved learning experience
b) Saves time
c) Avoid penalties

EXISTING SYSTEM

a) Existing system is completely manual and offers currently none of the mentioned
features

PROPOSED SYSTEM

a) User friendly interface

b) Ease of use
c) Improved learning experience
d) Time saving for access and return of materials
e) Convenient return stations
f) Easy access points like mobile, desktop, kiosk
Flowchart for LMS

Add records

Store records

Access records
Delete records

Return or Issue Materials

Reissue
Monitor/Notify
Materials

SCOPE using Use Case Diagram (UML)

Login to LMS

Student Access Library Staff

materials

Manage issued
material

Returns RFID Anti-

theft

LMS system
reporting
Library
Management
SCOPE using Context Diagram

Kiosk Access (Onsite

LMS System
staff/student access

Web access

Mobile access

LMS System
Dropbox returns (RFID RFID-Anti-theft system
Reporting
Tracking to manage returns)

DATA FLOW DIAGRAM

Add materials
metadata

Material Return
Access material
Repository location
metadata

Materials reporting
Interface

Return/Reissue
IN SCOPE

b) Kiosk access point on location for students and staffs to manage materials
c) Website access for students and staffs
d) Mobile access
e) Dropbox locations will allow collection of materials and transmit data to LMS for statu
and location update
f) LMS will access materials metadata, location, status and overdue penalties

OUT OF SCOPE

a) Materials not available in electronic formats will not be accessible within mobile and
web access points
b) Material access is subjected to governing copyright laws
c) Limited to android OS service

Wireframes:

https://

Search all Material Type

Enter search criteria Add record Delete Record Book

Date and Year of Publication 15-08-2022 Date of Purchase 15-08-2022

Cost

Author

Title

Publisher

Editor
ER DIAGRAM FOR THE SOFTWARE

Student Materials Staff Materials

Student Name Type Staff Name RFID

Student ID Status Staff ID Author
Location Title
Publisher
Edition
Publish Date
Purchase Date
Pricing

FUNCTIONAL REQUIREMENTS

a) LMS should keep record of different categories in the library like books, journals and
newspapers

b) Books should be classified subject wise

c) Each category should have different issue period

d) Each record should have RFID tag on it

e) System records issue date and return date of book

f) System automatically calculates fines in terms of delay

g) Library staffs can search books through author and name of book

h) Access through free e-book and journals

i) System should send automated emails to students 3 days before return day to avoid
penalty
NON-FUNCTIONAL REQUIREMENTS
System Requirement:
a) Data should be stored in cloud
b) Highly secure, scalable, and reliable

Usability:
a) Users need active Internet connection
Environments:
a) LMS support limited to latest 3 versions of safari, chrome, and edge
b) LMS Can be use on any Windows run computer
c) LMS can be used on any MacOS run computers