SRS - Library Management System

Download as pdf or txt
Download as pdf or txt
You are on page 1of 16

Atal Bihari Vajpayee Indian Institute of Information

Technology and Management Gwalior

SOFTWARE REQUIREMENT
SPECIFICATION REPORT

Library Management System

Submitted by -

Khumanshu singh (2021BCS-036)

Abhishek Singh (2021BCS-005)

Saad Ahmad (2021BCS-057)

Submitted to -

Dr Santosh Singh Rathore Sir


TABLE OF CONTENT

1. ACKNOWLEDGEMENT
2. ABSTRACT
3. SCOPE
4. OVERALL DESCRIPTION
5. FUNCTIONAL REQUIREMENTS
6. NON-FUNCTIONAL REQUIREMENTS
7. USE-CASE DIAGRAM
8. CLASS-DIAGRAMS
9. CONSTRAINS
10. ASSUMPTIONS AND DEPENDENCIES
ACKNOWLEDGEMENT

Apart from the efforts of the team, the success of any


project depends largely on the encouragement and
guidelines of many others. We take this opportunity to
express our gratitude to the people who have been
instrumental in the successful completion of this project.
The completion of any inter-disciplinary project depends
upon cooperation, coordination and combined efforts of
several sources of knowledge. We are eternally grateful to
our teacher Mr Santosh Singh Rathore for her willingness
to give us valuable advice and direction under which we
executed this project. Her constant guidance and
willingness to share her vast knowledge made us
understand this project and its manifestations in great
depth and helped us to complete the assigned tasks.

Khumanshu Singh (2021BCS-036)

Abhishek Singh (2021BCS-005)

Saad Ahmad (2021BCS-057)


ABSTRACT
With the increase in the number of readers, better
management of the library 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 allows you to issue, renew, or reserve 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

The purpose of the project is to maintain the details of


books and library members of different libraries. The main
goal of this project is to maintain an easy circulation
system between clients and the libraries and to issue books
using a single library card.
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 like details of the books,
insertion of new books, deletion of lost books, limitation on
issuing books, and 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.
OVERALL DESCRIPTION

PRODUCT PERSPECTIVE
The proposed Library Management System will take care of the
current book detail at any point in 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.

SOFTWARE REQUIREMENT
Front end: • Android developer tool • Advance java

Back end: • MySQL

HARDWARE REQUIREMENT
Android version 2.3 gingerbread(minimum, android user’s)
2GB ram 1.2 GHz processor Intel i5 Windows 7/8/8.1/10
FUNCTIONAL REQUIREMENT

Register
1. 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.
2. Regular person/student: The user has to provide details
about his/her name, address, phone number, and email id.

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

Manage books by the user.


Books issued.
1. Description: A list of books will be displaced along with
the date of return.
Search
1. Input: Enter the name of the author name of the books to
be issued.
2. Output: List of books related to the keyword.

Issues book
1. State: Searched for the book the user wants to issue.
2. Input: click the book the user wants.
3. Output: confirmation for book issue and apology for
failure in the issue.
4. Processing: if the selected book is available then the
book will be issued else an error will be displayed.

Renew book
1. State: The book is issued and is about to reach the date
of return.
2. Input: Select the book to be renewed.
3. Output: confirmation message.
4. Processing: If the issued book is already reserved by
another user then an error message will be sent and if
not the end confirmation message will be displayed.
Return
1. Input; Return the book to the library.
2. Output: The issued list will be updated and the returned
book will be listed.

Reserve book
1. Input; Enter the details of the book.
2. Output: Book successfully reserved.
3. Description: If a book is issued by someone then the user
can reserve it so that later the user can issue it.

Fine
1. Input: check for the fines.
2. Output: Details about fines on different books issued by
the user.
3. 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.
Manage book by librarian

Update details of books


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

Remove books
1. Input: Enter the name of the book and the number of
books.
2. 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 an android application. The system uses an android
application as an interface. Since all users are familiar with the
general usage of mobile apps, 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 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 submission. 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 has to 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 CHARACTERISTICS

We have 3 levels of users :

User module: In the user module, the user will check the
availability of the books.
1. Issue book
2. Reserve book
3. Return book
4. Fine details

Library module:
1. Add new book
2. Remove books
3. Update details of the book

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

1. Register user
2. Entry book details
3. Book issue
USE CASE DIAGRAM
ClASS DIAGRAM
CONSTRAINTS
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.

ASSUMPTION AND DEPENDENCIES


1. Each user must have a valid user id and password.
2. The server must be running for the system to function.
3. Users must log in to the system to access any record.
4. Only the Administrator can delete records.

You might also like