LOVELY PROFESSIONAL

UNIVERSITY
PHAGWARA-144411
CONTINUOUS ASSESSMENT-2

COURSE TITLE-PRINCIPLE OF SOFTWARE ENGINEERING

COURSE CODE-CAP-314

SUBMITTED BY:
Tarun
12221118

SUBMITTED TO:
DR. MOHIT MISHRA
 SOFTWARE REQUIREMENT SPECIFICATION DOCUMENT

LIBRARY MANAGEMENT SYSTEM

1. INTRODUCTION
With the increase in the number of readers, better management of
libraries system is required. The library
management system focuses on improving the management of libraries
in a city or town. “What If you can
check whether a book is available in the library through your phone?” or
“what if instead of having different.
library cards for different libraries you can just have one?” or “you can
reserve a book or issue a book from
your phone sitting at your home!”. The Integrated Library Management
system provides you the ease of issuing,
renewing, or reserving a book from a library within your town through your
phone. The Integrated Library
Management system is developed on the android platform which basically
focuses on issuing, renewing and
reserving a book.

PURPOSE:
The purpose of the project is 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 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.
SCOPE:
Manually updating the library system into an android based application so
that the user can know the details of the books available and maximum
limit on borrowing from their computer and 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 books, fine on keeping
a book more than one month from the issued date. Also, user can provide
feedback for adding some new books to the library.

Definition, Acronyms, Abbreviation:

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

OVERALL DESCRIPTION:
1.PRODUCT PRESPECTIVE
The proposed Library Management System will take care of the current
book detail at any point of time. The book issue, book return will update
the current book details automatically so that user will get the update
current book details.

2.SOFTWARE REQUIREMENT
• Front end:
1. Android Studio
2.Advance java

 Back end:
1.MySQL

3.HARDWARE REQUIREMENT
• Android version 2.3 gingerbread (minimum, android user’s)
• 2GB ram
• 1.2 GHz processor
4.FUNCTIONAL REQUIREMENT
• Register
 Description: First the user will have to register/sign up. There are two
different types of users.
 The library manager/head: The manager must provide details about
the name of library, address, phone number, email id.
 Regular person/student: The user has to provide details about his/her
name of address, phone number, email id.
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 error is found then an
error message is displayed else a membership number and password
will be generated.
Login
 Input: Enter the membership number and password provided.
 Output: User will be able to use the features of software.
Manage books by user
Books issued.
 Description: List of books will be displaced along with data of return.
Search
 Input: Enter the name of author's name of the books to be issued.
 Output: List of books related to the keyword.
Issues book
 State: Searched the book user wants to issue.
 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.
Renew book
 State: Book is issued and is about to reach the date of return.
 Input: Select the book to be renewed.
 Output: conformation message.
 Processing \: If the issued book is already reserved by another user,
then error message will be sent and if not, then conformation message
will be displayed.
Return
 Input; Return the book to the library.

 Output: The issued list will be updated, and the returned book will be listed out.

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.

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 fine will be applied by Rs 10 per day.
Manage book by librarian
Update details of books
• Add books
 Input: Enter the details of the books such as names, author, edition,
quantity.
 Output: confirmation of addition.
• Remove books
 Input: Enter the name of the book and quantity of books.
 Output: Update the list of the books available.

Non-Functional Requirements

• Usability Requirement
The system shall allow the users to access the system from the phone
using android application. The system uses a android application as an
interface. Since all users are familiar with the general usage of mobile
app, no special training is required. The system is user friendly which
makes the system easy.
• Availability Requirement
The system is available 100% for the user and is used 24 hrs a day and
365 days a year. The system shall be operational 24 hours a day and 7
days a week.
• Efficiency Requirement
Mean Time to Repair (MTTR) - Even if the system fails, the system will
be recovered back up within an hour or less.
• Accuracy
The system should accurately provide real time information taking into
consideration various concurrency issues. The system shall provide
100% access reliability.
• Performance Requirement
The information is refreshed depending upon 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.
• Reliability Requirement
The system must be 100% reliable due to the importance of data and
the damages that can be caused by incorrect or incomplete data. The
system will run 7 days a week, 24 hours a day.

USER CHARACTERSTICS
We have 3 levels of users.
 User module: In the user module, 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 book

 Administration module:
The following are the sub module in the administration module
 Register user
 Entry book details
 Book issue
CONSTRAINTS
Any update regarding the book from the library is to be recorded to have
update & correct values, and any fine on a member should be notified as
soon as possible and should be correctly calculated.

ER diagram of LMS
Thank you