Scribd
Upload
13 views

LMS(srs)

lms srs

Uploaded by

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

LMS(srs)

lms srs

Uploaded by

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

SRS on Library Management System

(LMS)
1. INTRODUCTION

1.1 PURPOSE

The project aims to maintain the details of books and library


members of different libraries. The main purpose of this
project is to maintain a easy circulation system between
clients and the libraries, to issue books using a single library
card, also to search and reserve any book from different
available libraries and to maintain details about the user
(fine, address, phone number). Moreover, the user can check
all these features from their home.

1.2 SCOPE

• Manually updating the library system into an android-


based application so that the user can know the details
of the books available and the maximum limit on
borrowing from their computer and also through their
phones.

• The ILM System provides information’s like details of


the books, insertion of new books, deletion of lost
books, limitation on issuing and books, fine on keeping
a book more than one month from the issued date.
• Also users can provide feedback for adding some new
books to the library.

1.3 Definition, Acronyms, Abbreviation:

• JAVA -> platform independence(Programming


language)
• SQL -> Structured query Language
• DFD -> Data Flow Diagram
• CFD -> Context Flow Diagram
• ER -> Entity Relationship
• IDE -> Integrated Development Environment
• SRS -> Software Requirement Specification

1.3 Reference
• Book:- Head first JAVA
• Website:- www.wikkipedia.com
1.4 Overview
In the LMS we define various components in
different section, in section on we are defining
introduction , purpose, definition and references.
In section two we are discussing project
perspective, project function, general constrain,
assumptions and dependencies. And in section
three we are describing specific requirements of
Project.
2. GENERAL DESCRIPTION
2.1 PRODUCT PERSPECTIVE
The proposed Library Management System will take care of
the current book detail at any point of time. For the book
issue, book return will update the current book details
automatically so that the user will get the updated current
book details.
2.2 SOFTWARE REQUIREMENT
• Front end:
• HTML, CSS, Android developer tool
• Advance js

• Back end:
• MySQL
• JAVA

2.3 HARDWARE REQUIREMENT

• Android version 2.3 (minimum, android user’s)

• 2GB ram

• 1.2 GHz processor

• Intel i5

2.4.1 FUNCTIONAL REQUIREMENT

R.1:Register
• Description: First, the user will have to register/sign up.
There are two different types of users.

• The library manager/head: The manager has to


provide details about the name of the library, address,
phone number, and email id.

• Regular person/student: The user has to provide


details about his/her name, address,
phone number, and email id.

R.1.1: Sign up

• Input: Detail about the user as mentioned in the


description.

• Output: Confirmation of registration status and a


membership number and password will be generated
and mailed to the user.

• Processing: All details will be checked and if any errors


are found then an error message is displayed else a
membership number and password will be generated.

R.1.2: Login

• Input: Enter
the membership number and password provided.
• Output: The user will be able to use the features of the
software.

R.2: Manage books by the user.

R.2.1: Books issued.

Description: List of books will be displaced along with data


of return.

R.2.2: Search
• Input: Enter the name of author's name of the books to
be issued.
• Output: List of books related to the keyword.

R.2.3 : Issues book

• State : Searched the book user wants to issues.


• Input : click the book user wants.
• Output : conformation for book issue and apology for
failure in issue.
• Processing : if selected book is available then book will
be issued else error will be displayed.

R.2.4 : Renew book

• State: Book is issued and is about to reach the date of


return.
• Input: Select the book to be renewed.
• Output: confirmation message.
• Processing: If the issued book is already reserved by an
other user then an error message will be
sent and if not then a
confirmation message will be displayed.

R.2.5: Return

• Input: Return the book to the library.


• Output: The issued list will be updated and the returned
book will be listed.

R.2.6 Reserve book


• Input: Enter the details of the book.
• Output: Book successfully reserved
• Description: If a book is issued by someone then
the user can reserve it , so that later the user can issue
it.
R.2.6 Fine

Input: check for the fines.


Output: Details about fines on different books issued by the
user.
Processing: The fine will be calculated if it crossed the date
of return and the user did not renew if then the fine will be
applied by Rs 10 per day.

R.3 Manage book by librarian

R.3.1 Update details of books


R.3.1.1 Add books
• Input: Enter the details of the books such as names,
authors, editions, and quantity.
• Output: confirmation of addition.

R.3.1.2 Remove books


• Input: Enter the name of the book and the number of
books.
• Output: Update the list of the books available.

2.4.2 Non-Functional Requirements

• 2.4.2.1 Performance Requirements

• The system shall accommodate high number of


books and users without any fault.
• Responses to view information shall take no
longer than 5 seconds to appear on the screen.

• 2.4.2.2 Security Requirements


• Login operation should be performed using
transport layer security(HTTPS)
• All user ID and password information should be
encrypted using one -way hash algorithms in the
database.
• Registration process should use CAPCHA to
prevent machine/robot brute force attack.
• 2.4.2.3 Availability Requirement
• The system is available 100% for the user and is
used 24 hrs. a day and 365 days a year. The
system will be operational 24 hours a day and 7
days a week.

• 2.4.2.4 Usability Requirement


The system shall allow the users to access the system from
the phone using an android application. The system uses an
android application as an interface. Since all users are
familiar with the general usage of the mobile app, no special
training is required. The system is user friendly which
makes the system easy.

• 2.4.2.5 Performance Requirement

The information is refreshed depending on whether some


updates have occurred or not in the application. The system
shall respond to the member in not less than two seconds
from the time of the request submittal. The system shall be
allowed to take more time when doing large processing jobs.
Responses to view information shall take no longer than 5
seconds to appear on the screen.
• 2.4.2.6 Reliability Requirement

The system has to provide reliable and relevant search


result 100% of times. The system will run 7 days a week, 24
hours a day.

• 2.4.2.7 Maintainability
• All the codes artifacts should have proper
documentation.
• All code components should be thoroughly
tested and the test coverage should be more
than 80%.

2.5 USER CHARACTERISTICS


We have 3 levels of users :

User module: In the user module, the user will check the
availability of the books.

• Issue book
• Reserve book
• Return book
• Fine details

Library module:

• Add new book


• Remove books
• Update details of the f book

Administration module:
The following are the submodule in the administration
module :

• Register user
• Entry book details
• Book issue

2.6 CONSTRAINTS
• The information of all users, books and libraries
must be stored in a database accessible by the
website.
• User must have their correct username and
password to enter into their online accounts and
do action.

Any update regarding the book from the library is to be


recorded to have updated & correct values, and any fine on a
member should be notified as soon as possible and should be
correctly calculated.

2.11Assumptions and Dependencies


• Existing of an internet service to all users.
• Website interface must be friendly and easy to
use.
• The search mechanism should be simple and
fast.

You might also like