Documente Academic
Documente Profesional
Documente Cultură
Submitted by:
1) DIVYANSHU D V Usn: 1NT16CS025
2) D ARUN SAKETH Usn: 1NT16CS030
3) MIHIR M Usn: 1NT16CS048
4) P SANJEEV TEJA Usn: 1NT16CS098
CERTIFICATE
Course In-charge
Vinay.T.R
Assistant. Professor, Dept. Of CSE,
NMIT, Bangalore
ACKNOWLEDGEMENT
The completion of this undertaking could not have been possible without the
participation and assistance of so many people. Their contribution are sincerely
appreciated and gratefully acknowledged. However the group would like to express our
sincere gratitude to our Software Engineering lecturer Mr. Vinay. T.R for his vital
support, guidance and constant supervision as well as for providing necessary
information regarding the Software Requirement Document of library management
system
We have taken efforts in this project. However, it would not have been possible without
the kind support and help of many individuals who in one or the another shared their
support, either morally or physically . We would like to extend our sincere thanks to all
of them.
LIBRABY MANAGEMENT SOFTWARE
Project
FOR
ABSTRACT
The main objective of the document is to develop a software for "NATIONAL PUBLIC
SCHOOL” library management software. The purpose of the document is to collect all
the requirements from the client and analyze all assorted ideas along with the budget
that have come up to define and develop the system, its functional and non-functional
requirements with respect to consumers.
The main purpose of this SRS document is to provide a detailed overview of our
software product planned to develop, its parameters and goals. This document
describes the project's target audience and its user interface, hardware and software
requirements. It defines how our client, team and audience see the product and its
functionality.
Table of Contents
2. Glossary
4. System Architecture
7. System Evolution
8. Financial Aspects
10. Conclusion
11. Bibliography
1. INTRODUCTION
The introduction of the Software Requirements Specification (SRS) provides an overview
of the entire SRS with purpose, scope, definitions, acronyms, abbreviations, references
and overview of the SRS. The aim of this document is to gather and analyze and give an
in-depth insight of the complete National Public School Library Management Software
System that needs to be developed by defining the problem statement in detail.
Nevertheless, it also concentrates on the capabilities required by stakeholders and their
needs while defining high-level product features. The detailed requirements of the
National Public School Library Management are provided in this document.
1.1 Scope
This project is developed in response to the need to maintain the details of books and library
members of different libraries.
The maintenance of a physical log book could be tedious and might require higher expense in
long term which cannot be backed up. Also searching and updating records in such a system
could be tiresome.
The Client is staff member of the school which is located in Jeevan Bheema Nagar, Bangalore.
The school’s library contains various books that can be issued to users based on the availability
of the books and many more. We interacted with the client and collected all the requirements
needed for client organisation’s software.
Client Name : Hima Bindu D
Contact Number of the Client : 9900975826
R.1:Register
Description : First the user will have to register/sign up. There are two different type of
users.
The library manager/head : The manager have to provide details about the name of
library ,address, phone number, email id.
Regular person/student : The user have to provide details about his/her name of address,
phone number, 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 error 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 : User will be able to use the features of software.
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.5 : Return
Input ; Return the book to the library.
Output : The issued list will be updated and the returned book will be listed out.
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 renewed if then fine will be applied by Rs 10 per day.
USABILITY SCALABILITY
NON- FUNCTIONAL
REQUIREMENTS
User module: In the user module, user will check the availability of the books.
1. Issue book
2. Reserve book
3. Return book
4. Fine details
Library module:
2. Remove books
Administration module: The following are the sub module in the administration module :
1. Register user
3. Book issue
FLOW DIAGRAM :-
Start
The system shall provide a convenient interface for a user to avail membership in the
library.
The system shall have connectivity to an online database to verify IDs of new users.
The system must allow the user to have a unique ID and password to authenticate with
the library system.
The system must have an interface where the user can enter his/her credentials and
login with proper authentication methods.
The system must also provide an option to reset/change password in case the user
forgets the password or faces trouble logging in.
The user must be able to see the books issued by him/her, the due date and the fine to
be paid.
The user must be able to read a detailed description about the issue books along with its
details.
The user must be able to search for specific books in the library and get details about the
book
The system must provide options to search book by name, author or subject.
The user must be able to issue books online and pick them up later.
The user must be able to select the number of days he/she wants to issue the book for.
The user must be able to know when the library can accept return of issued books
The user must be able to renew the already issued books online, thereby avoiding fine.
The system must provide a mechanism to accept online payments for dues and fines
The Librarian must be able to update, add, remove books and book details
The Librarian must be able to keep a track of library users and the books issued by them.
7. SYSTEM EVOLUTION
Software change is inevitable to meet all the expectations and demands of the client. As
technology, market and business changes along with time it is very essential to build a
software which is flexible. The necessity to change the Software may occur due to
following reasons :-
New requirements emerge when the software is used
The school requirement environment changes
Errors must be repaired
New computers and equipment is added to the system
The performance or reliability of the system may have to be improved
A key problem for developers is implementing and managing change to the existing
software. We planned to keep the copy of the software and it's code and improve it
using new technologies whenever client demands and provide it to client.
After the application is installed on the server, no additional installation will be
necessary since the end-users will be using their desktop client to access.
The application is estimated to be developed and deployed within the budget of 200000.
For the proposed software there is no requirements of any additional hardware. Only
Basic computer system requirement along with installation of required software is to be
provided. The number of people chosen to work for the project is approximately around
10 members among whom one is a project manager who can be assigned with different
parts of software development.
9. DURATION
1. On the part of the library staff, a lot time in issuing,returning and searching for the
details of books and students which could be saved and channeled into a more
productive and innovative business for the library.
2. Also, this project is very useful to students as they can access materials on time.
4. Staff cannot manipulate the system for their personnel interest since the generation
of fine and the number of days a student keeps a book is predetermined in the system.
6. It can be concluded that the application has met the requirements set by the National
Public School Library.
11. Bibliography
a. HTTP://WWW.bplans.com/retail_and_online_store_business_plan_templates.php -
Free Retail Online Store Project Plans.