Software Requirement Specification (SRS)

for E-Library Management System (e-LMS)

1. Introduction

1.1 Purpose:
E-Library Management System (E-LMS) is intended to help college students
borrow/return and view the catalogue of books from the college library.

This document is meant to demarcate the features of E-LMS, so as to serve as

a guide to the developers and a software document for the academic
purposes.

1.2 Scope:
We describe what features are in the scope of the software and what are not
in the scope of the software to be developed.
In Scope:
a. Managing the number of books a student has issued, along with the date
of borrowing and unique book id.
b. Viewing the list of books available.
c. Librarian authentication.
d. Viewing the list of books each student has borrowed at a particular point of
time.

Out of Scope:
a. Features for verifying whether a given book is physically available or not.
b. A separate login for users. The librarian is in charge of checking and issuing
books.

1.3 Definitions, Acronyms, and Abbreviations:

Acronyms and Abbreviations:

a. E-LMS: E-Library Management System.
b. SRS: Software Requirements Specification.
c. WWW: World Wide Web
d. ISBN: International Standard Book Number

Definitions:
a. Security: A set of books and students that a particular librarian is in
charge of.
b. Admin: An admin account which controls all the librarian accounts.
 1.5 Overview:
The rest of this SRS is organized as follows: Section 2 gives an overall
description of the software. It gives what level of proficiency is expected of
the user, some general constraints while making the software and some
assumptions and dependencies that are assumed. Section 3 gives specific
requirements which the software is expected to deliver. Functional
requirements are given by various use cases. Some performance requirements
and design constraints are also given. Section 4 gives some possible future
extensions of the system.

2. Overall Description:

2.1 Product Perspective:

E-LMS is aimed towards providing an efficient method of borrowing books
from a library in a way that can easily track any book. E-LMS should be user-
friendly, ‘quick to learn’ for librarians with non-technical background and
reliable software for the above purpose.

E-LMS is a stand-alone product and should not depend on the availability of

other software. It should run on both UNIX and Windows based platform.

2.2 Product Functions:

E-LMS should support the following use cases:

Class of use cases Use cases Description of use cases

Login Admin Login for E-LMS
Use cases related to admin login Add/ Edit Librarian Add/ Edit Details of Librarian
Remove Librarian Delete a Librarian
Use cases related to librarian Login Librarian Login
login
View Books View books available in the
library
Use cases related to librarian Issue Book Issue book at student’s
duties request
View Issued Books View list of books issued
Return Book Add book back to library
Add Book Add new book to library
 2.3 User Characteristics:
a. The librarian should be familiar with the basic concepts of borrowing and
returning books from a library with a college id.
b. The librarian should also know adding and deleting books from the catalogue
along with searching for specific books in the catalogue.

2.4 Principal Actors:

The two principal actors in E-LMS are “librarian” and “admin”.

2.5 General Constraints:

a. For full working E-LMS requires Internet connection.

2.6 Assumptions and Dependencies:

a. Full working of E-LMS is dependent on the availability of Internet connection.

b. The book(s) to be borrowed by the student must already be present in the
library database.

3 Specific Requirements:

3.1 Functional Requirements:

We describe the functional requirements by giving various use cases.

Use case related to admin login:

Use Case 1: Admin login
Primary Actor: Admin
Pre Condition: Internet connection available.
Main Scenario :
1. The admin must have installed the software package in the library
computer system.
2. The admin must login with the credentials which were bundled along
with software and it must not be shared with anyone.
3. He/she can then add librarians’ details into the database so that they
can start using the system.
Alternate Scenario:
1(a). Network failure.
1(a)1. Installation and login aborted.

Use case related to admin login:

Use Case 2: Add/Edit librarian
Primary Actor: Admin
Pre Condition: Admin must have logged in.
Main Scenario :
1. The admin, who has already logged in, must go to the page where
librarians can be given authorization.
2. When prompted, librarian details have to be entered and they must be
given a unique username.
3. If existing librarian’s details has to be edited, then the admin has to
access the edit page and then when prompted, enter the new details.
4. The new/edited librarian’s details have to be submitted.
 Alternate Scenario:
1(a). Network failure.
1(a)1. Login aborted.
2(a). New librarian isn’t given a unique username.
2(a)1. Error message will be displayed.
4(a). Not submitted, instead page refreshed.
4(a)1. All the entered data is lost, have to be entered again.

Use case related to admin login:

Use Case 3: Remove librarian
Primary Actor: Admin
Pre Condition: Admin must have logged in.
Main Scenario :
1. The admin, who has already logged in, must go to the page where
librarians can be given authorization.
2. The admin must go to the page where librarians can be removed.
3. By giving his/her username, the librarian can be made devoid of
software access.
Alternate Scenario:
1(a). Network failure.
1(a)1. Login aborted.
3(a). Librarian username is wrong.
3(a)1. Error message will be displayed.
3(b). Not submitted, instead page refreshed.
3(b)1. All the entered data is lost, have to be entered again.

Use case related to librarian login:

Use Case 4: Login
Primary Actor: Librarian
Pre Condition: Internet connection available and software installed in the
system.
Main Scenario :
1. The admin must have given the librarian system access details.
2. The librarian, when prompted in home page has to enter his/her
credentials to login.
Alternate Scenario:
1(a). Network failure.
1(a)1. Login aborted.
2(a). Librarian username is wrong or authorization not given by admin.
2(a)1. Error message will be displayed.
2(b). Not submitted, instead page refreshed.
2(b)1. All the entered data is lost, have to be entered again.

Use case related to librarian duties:

Use Case 5: View books
Primary Actor: Librarian
Pre Condition: Librarian must have logged in.
Main Scenario :
1. The librarian can search for the availability of books using the search
bar.
 2. The book details will be displayed in a list.
3. The librarian can also view the list of all the books or genre-wise
available in the library.
4. This also will be displayed in a list.
Alternate Scenario:
1(a). Book ID entered is wrong or it isn’t present in the library database.
1(a)1. Error message will be displayed.
3(a). Genre name is wrong or not present in the database.
3(a)1. Error message will be displayed.

Use case related to librarian duties:

Use Case 6: Issue books
Primary Actor: Librarian
Pre Condition: Librarian must have logged in.
Main Scenario :
1. The librarian has to go to the page from which books can be issued.
2. He/she has to enter the student ID along with the book ISBN to be
issued.
3. When submitted successfully, the book will be issued to the student.
Alternate Scenario:
2(a). Book ISBN entered is wrong or it isn’t present in the library database.
2(a)1. Error message will be displayed.
2(b). Student ID is wrong.
2(b)1. Error message will be displayed.
3(a). Not submitted, instead page refreshed.
3(a)1. All the entered data is lost, have to be entered again.

Use case related to librarian duties:

Use Case 7: View issued books
Primary Actor: Librarian
Pre Condition: Librarian must have logged in.
Main Scenario :
1. The librarian has to go to the page from which books can be issued.
2. When ‘view issued books’ button is pressed, the list of books issued
along with the borrower names will be displayed in a table.
Alternate Scenario:
2(a). No books issued at that time.
2(a)1. ‘No books issued’ message will be displayed.

Use case related to librarian duties:

Use Case 8: Return books
Primary Actor: Librarian
Pre Condition: Librarian must have logged in.
Main Scenario :
1. The librarian has to go to the page from which books can be returned.
2. He/she has to enter the student ID along with the book ISBN to be
returned.
3. When submitted successfully, the book will be returned to the library.
 Alternate Scenario:
2(a). Book ISBN entered is wrong or it isn’t present in the library database.
2(a)1. Error message will be displayed.
2(b). Student ID is wrong.
2(b)1. Error message will be displayed.
3(a). Not submitted, instead page refreshed.
3(a)1. All the entered data is lost, have to be entered again.

Use case related to librarian duties:

Use Case 9: Add books
Primary Actor: Librarian
Pre Condition: Librarian must have logged in.
Main Scenario :
1. The librarian has to go to the page from which books can be added
into the library database.
2. When prompted, the details of the book have to be entered and
submitted.
Alternate Scenario:
2(a). ISBN of the book already exists in the database.
2(a)1. Error message will be displayed.

3.2 Performance Requirements:

a) Should run on 500 MHz, 64 MB machine.
b) 90% of the responses should be within 2 sec, without any exceptions.

3.3 Design Constraints:

1. Security: The files in which the information regarding securities and
issued books should be secured against malicious deformations.
2. Fault Tolerance: Data should not become corrupted in case of system
crash or power failure.

4. Future Extensions:
a. E-LMS is intended to be used by the librarian. In future, the software can be
extended in such a way that students can themselves issue/return books by using
some fault tolerant, secure system.
b. IOT sensors can be integrated to the library computer systems such that instead of
entering book ISBN and student ID manually; it can be scanned, thereby achieving
more efficiency.