Scribd
Upload
267 views2 pages

SRS Document

The document outlines requirements for an e-library system. It includes functional requirements for librarians, users, and admins to manage books and user accounts. Non-functional requirements address usability on mobile apps, 100% system availability, authentication security for users and librarians, and efficient data recovery if the system fails. The system will allow users to search for books, order books based on availability, and renew books. Librarians can add or remove books, collect fines, and add or remove users.

Uploaded by

Pavithra
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
267 views2 pages

SRS Document

The document outlines requirements for an e-library system. It includes functional requirements for librarians, users, and admins to manage books and user accounts. Non-functional requirements address usability on mobile apps, 100% system availability, authentication security for users and librarians, and efficient data recovery if the system fails. The system will allow users to search for books, order books based on availability, and renew books. Librarians can add or remove books, collect fines, and add or remove users.

Uploaded by

Pavithra
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

e- Library System

Table of Contents
1. Introduction
1.1 Purpose
1.2 Scope

2. Functional Requirements
2.1 Librarian
2.2 User
2.3 Admin
2.4 Book

3. Non-Functional Requirements
3.1 Usability requirement
3.2 Availability requirement
3.3 Security requirement
3.4 Efficiency requirement

1 Introduction:
With the increase in the number of book readers, a proper library management system
is needed. It is very much easier to order the book in library through online like shopping and
banking. We can check whether the book is available in the library or not? We can order or
renewing a book through the mobile in our home town.

1.1 Purpose:
The main objective of this document is to illustrate the requirement for the Library
Management System. This document will contain all the requirements given by the user. This
document contain both functional and non-functional requirements.

1.2 Scope:

The e-Library system must have the following features:

 This system must authenticate users at their login


 It will show the availability of the book
 The user will be able to update their status
 The librarian will be able add or delete books, collecting the fine if the due date is
exceeded
 Admin should handle all the process in this system

2 Functional Requirement:
The functional requirements will contain many functional blocks. They are listed below
2.1 L i b r a r i a n
 The librarian should login the system with their userid and password.
 Librarian will be able to add or delete books
 The fine amount will be collected by the librarian.
 Librarian will be able to add or delete the user
 Libraraian will be able to search the books

2.2 Admin
 The admin should login the system with their userid and password.
 Admin should be able to add or delete books
 Admin can add or delete the user
 Admin will be able to search the books

2.3 User
 The user can register in this website
 The users should login the system with their userid and password.
 Users will be able to search the books
 The books are ordered based on availability
 Users should renewing the book
 Able to see all the available books

2.3 Book
Books are categorised into Journels and the Reference.
 All the type of books will have published year, Author name and price.
 The availability and the status of the book is described below every book
 Based on the status the books are reserved and issued
 The books are removed if it is not available
 New books are added based on user requirements

3 Non-FunctionalRequirement:
Various non-Functional Requirement for the product could be-

3.1 Usability Requirement


The system should allow the user to access the system through the mobile app.

3.2 Availability Requirement


The system is available 100% for the user in all time.

3.3 Security Requirement


Authentication is provided to all the users and librarians, only authenticated users can use
the system.

3.3 Efficiency Requirement


If the system fails, the system will recover all the data very efficiently with less time

You might also like