Reference for Problem Statement 2 – Stanford Library

STAKEHOLDERS

ACTOR What he can do on the Software Created

Student ● Should be able to login online to the LMS.
● Should be able to submit feedback
● Should be able to borrow books and other reading material
● Will be paying the fine in case of delayed return or
library
material

Library Staff ● Shall be creating record for each book, journal,

newspaper and
other reading material.
● Shall be checking in and out the reading material
● Shall collect the fine paid by student

Management ● Shall generate reports of library management system

usage.

PROBLEM DEFINITION AND SOLUTION

● A lot of time is wasted due to manual library.

● Fine calculation is a tedious and time-consuming affair.
● No reports could be generated on books issued and not-issued due to manual
system
● Difficult to manage 4 million books present in the library
● Student could deposit the books only in the library timings. With automated
drop box
the students could deposit the book at any time of the day.

Advantages of LMS

Advantages of Library Management System:

● Reduce overheads and increase productivity of Library Staff.
● Cost reduction
● Up-to-date record of all books, research papers, magazines and other
materials available
in the library.
● Improve student engagement in the library
● It will generate dynamic reports for better decision making
EXISTING SYSTEM

● There is no existing software system as the library is manual. Not choosing

an
automated system may be very time consuming, complex, manual, requires more
manpower, leads to a lot of time wastage, thus it is not at all cost
effective. So, after
doing the feasibility study it was decided to create a Library Management
System.

PROPOSED SYSTEM

The proposed system is a software system for tracking day to day management
of the
library. The proposed system has the following advantages:

● User friendly interface

● Fast access to database
● Search Facility
● Report generation
● 24 by 7 book dropping mechanism
● Automated emails sent to students
Flowchart for LMS
SCOPE using Use Case Diagram (UML)

SCOPE using Context Diagram

DATA FLOW DIAGRAM

IN SCOPE

● Login – The users of the system library employees, students and management
will be
able to login using their IDs & passwords.
● Creating record of books – The library employees will be able to add new
books and
other reading material in the library records.
● Modify Records – The library employees will be able to modify any item
existing in the
system
● Delete Books/records – The library employees will be able to delete any
existing books
under the selected category.
● Handle issue and return of books and other reading material
● Automated emails before the return date to the student
● Calculation of Fines by the system
● Automated drop box for books to be handled by the system.
● Fetching Reports – The management will be able to extract different types of
reports
based on the requirements specified.
● A log out feature will be added so that the employees, students and
management using
the system can log out once they are done with their work.
OUT OF SCOPE

● This is handling the library of only one campus of Stanford University

● Any demand for training to new or existing user after two weeks.
● Any maintenance request after two months of system rollout.

Wireframes:

The below shown screen will be shown to the library employees to create records for
each book.

The below shown screen will be the view shown for each book when searched.
Report wireframe:
Total Books report shown to management
ER DIAGRAM FOR THE SOFTWARE
FUNCTIONAL REQUIREMENTS

1. Book record creation

2. Book record deletion
3. Book record editing / updation by library employees
4. Issue and return of books
5. Login – The users of the system library employees, students and management
will be
able to login using their IDs & passwords.
6. Delete Books/records
7. Automated emails before the return date to the student
8. Calculation of Fines by the system
9. Automated drop box for books to be handled by the system.
10. A log out feature will be added so that the employees, students and
management using
the system can log out once they are done with their work.
11. Access to free e-journals and e-books through the software
12. Following Report generation
● Which books are most rented?
● Records of issued and unissued materials in the library (management will
decide
whether to stock them or not)?
● Amount of fines collected in a day, week and month.
● Number of lost books
● Report on total number of books, journals etc
● Age of books i.e. which books are more than 20 years old. College
generally would
prefer not to have very old books since new versions come up every few
years.

NON-FUNCTIONAL REQUIREMENTS

System Requirement:
● LMS can be used on any Windows & MacOS run computers
● Users will need an active internet connection.
● It will be RFID Ready (NCIP 2.0 HTTP Server Available)
● Auto Scheduled Tasks - eMails, Database Maintenance
● Data should be stored in cloud
● Highly Secure, Scalable & Reliable

Usability:

The screens should be self-explanatory and very user friendly. The users should not
find
the system cumbersome.

Environments
We are going to be creating and maintaining the program in Java. We chose Java
because it will
not change much over time and if we make it well, there will be very little
maintenance to be
done on the code.