Library Management System
Library Management System
1.1. The user can enquire about the availability of a book in which he can search by
entering the author’s name or by entering a title of the book.
1.2. The user can borrow a book. He must provide the user name and the card number,
which is unique and confidential to each user. By confirming the authenticity of a
user, the library management system provides information about the number of
books already borrowed by the user and by referring to the data base whether the
user can borrow books or not.
The library management system allows the user to enter the title and author of
the book and hence issues the book if it is available.
1.3. By entering the user details and book details the user can return the borrowed book.
2.1. Introduction –
2.1.1. Purpose –
2.1.1.1. The purpose of this SRS is to describe the requirements involved in developing a
library management system.
2.1.1.2. The intended audience is any person, who wants to enquire, borrow and return the
books.
2.1.2. Scope –
2.1.4.1. The SRS contains an analysis of the requirements necessary to help easy design.
2.1.4.2. The overall description provides interface requirements for the library management
system, product perspective, hardware interfaces, software interfaces, communication interfaces,
memory constraints, product functions, user characteristics and other constraints.
2.1.4.3. The following sections illustrate the characteristics of typical naive users accessing
the system along with legal and functional constraints. Enforced that affect library management
system in any fashion.
2.2.1.1.2. The system must interface with the standard input/output devices such as
monitor, keyboard, mouse to interact with this software.
2.2.1.4. Operations –
2.2.1.4.1.2. By extracting the username and password the software allows the user to
borrow a maximum of three books.
2.2.1.4.1.3. By extracting the username and password the software allows the user to
return the borrowed books.
2.2.2.2. Search the availability of book by entering the title of the book.
2.2.2.3. Search the availability of the book by entering the author of the book.
2.2.2.4. The software validates the authentic user by extracting their username and
password.
2.2.2.5. After the validation of the user software allows the user to borrow a
maximum of 3 books based on the number of books which were already borrowed.
2.2.2.6. After the validation of the user software allows the user to return books,
which were borrowed.
2.2.3.1. The intended users of this software need not have specific knowledge as to what is
the internal operation of the system. Thus, the end user is at a high level of abstraction that allows
easier, faster operation and reduces the knowledge requirement of end user.
2.2.3.2. The product is absolutely user friendly, so the intended user can be the naive user.
2.2.3.3. The product doesn’t expect the user to provide any technical background. Any
person, who knows to use the mouse and the keyboard, can successfully use this product.
2.2.3. Constraints – The user has a unique username and password, there are no options
to retrieve a password or username in case it is forgotten or lost. Hence the user is required to
remember or store the username or password.
2.3.1.1. The system should contain data bases that include all necessary information for the
product to function according to the requirements. This includes relations such as user details and
book details.
2.3.1.2. The user details refer to the information such as name, card number, number of
books borrowed, the title of the book and the name of the author of the books that were borrowed.
2.3.1.3. The book details refer to the information such as the title of the book, author,
availability status and the number of copies that is available.