Scribd
Upload
47 views

Week 8 - ST (Online Library Management)

The document outlines requirements for a library management system (LMS) to replace traditional paper-based systems. The LMS will provide an advanced book search mechanism and make it easy to borrow, insert, and index books. It will manage the library's daily activities electronically, including functions like registering users and books, searching for books, calculating overdue fines, and more. Non-functional requirements include maintainability, portability, scalability, reliability, usability, performance, safety, and security. User stories are also provided to illustrate desired system behaviors from the perspectives of readers and library managers.

Uploaded by

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

Week 8 - ST (Online Library Management)

The document outlines requirements for a library management system (LMS) to replace traditional paper-based systems. The LMS will provide an advanced book search mechanism and make it easy to borrow, insert, and index books. It will manage the library's daily activities electronically, including functions like registering users and books, searching for books, calculating overdue fines, and more. Non-functional requirements include maintainability, portability, scalability, reliability, usability, performance, safety, and security. User stories are also provided to illustrate desired system behaviors from the perspectives of readers and library managers.

Uploaded by

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

Identify a problem and prepare Requirement document For

LIBRARY MANAGEMENT SYSTEM


1.PROBLEM STATEMENT:
In traditional libraries, the user has to search for books which are hassle process and
there is no proper maintenance of database about issues/fines. The overall progress
of work is slow and it is impossible to generate a fast report.

Chapter 2
Overall Description
2.1 Product Perspective
LMS is a replacement for the ordinary library management systems which depend on
paper
work for recording book and users’ information.
LMS will provide an advanced book search mechanism and will make it easy to
borrow, insert
and index a book in the library.
Chapter 2
Overall Description
2.1 Product Perspective
LMS is a replacement for the ordinary library management systems which depend on
paper
work for recording book and users’ information.
LMS will provide an advanced book search mechanism and will make it easy to
borrow, insert
and index a book in the library.
Product Perspective
LMS is a replacement for the ordinary library management systems which depend on
paper
work for recording book and users’ information.
LMS will provide an advanced book search mechanism and will make it easy to
borrow, insert
and index a book in the library.
Product Perspective
LMS is a replacement for the ordinary library management systems which depend on
paper
work for recording book and users’ information.
LMS will provide an advanced book search mechanism and will make it easy to
borrow, insert
and index a book in the library.
2.PRODUCT DESCRIPTION:
Library Management System is a computerized system which helps user(librarian) to
manage the library daily activity in electronic format. It provides the ability to find
books, manage books, track borrowed books, managing fines and bills all in one place.
FUNCTIONAL REQUIREMENTS
Register new user: Allow the librarian to add and remove new members.
User Login: User logins to the system by entering valid user id and password.
Register new book: Librarian can add new books and their information to the
database.
Issue Book: Librarian can issue a book to the users
Return Book: Librarian should confirm the return of books borrowed by users
Search Book: Allow the user to search for books based on title, publication date,
author, etc.
Calculates fine: The system calculates the fine for overdue books on their return.

NON FUNCTIONAL REQUIREMENTS:


1. Maintainability
2. Portability
3. Scalability
4. Reliability
5. Usability
6. Performance
7. Safety
8. Security

2. Risk for the above case


6.3 User Stories for LIBRARY MANAGEMENT SYSTEM
User Story 1: login
As a reader,
I want to login to my account
So that I can borrow books online
Acceptance Criteria:
1. Reader can log in the system using valid username & password or mobile phone.
2. If the user enters wrong username or password, error message should be
displayed.

User Story 2: Search books


As a reader,
I want to search books in library
so that I can borrow books more conveniently.
Acceptance Criteria:
1. Books in library can be search by multiple ways, such as by title, by classification,
by author etc.
2. Books' current borrowing states can be showed.

User Story 3: Comment


As a reader,
I want to comment books I have borrowed
so that can provide reference to others.
Acceptance Criteria:
1. Readers can comment with words.
2. Readers can comment by scoring stars.

User Story 4: Remainder


As a reader,
I want to receive a reminder message when books I borrowed will reach the return
deadline
So that I can return books on time.
Acceptance Criteria:
1. Remind readers one week before the return deadline.

User Story 5: ISSUE BOOKS


As a library manager,
I want to issue books to the reader so that reader can borrow it for certain period of
time .
Acceptance Criteria:
1. Book's issuing states in library should be changed.
2. Librarian can issue up to three books at a time.

User Story 6: Update


We have 2 levels of users
• User module: In the user module, user will check the availability of the books.
– Book return
• Administration module: The following are the sub module in the administration
module.
– Register user
– Entry book details
– Book issue
We have 2 levels of users
• User module: In the user module, user will check the availability of the books.
– Book return
• Administration module: The following are the sub module in the administration
module.
– Register user
– Entry book details
– Book isUser Story 1:
As a library manager,
I want to update information of books on bookshelf in system
so that I can manage books conveniently.
Acceptance Criteria:
1. Information of book can be added in detail.
2. Information of book can be removed from the system.

User Story 7: Messages


As a library manager,
I want to push messages related library activities to readers
So that readers get latest updates
Acceptance Criteria:
1. Messages can be edited and submitted in a page.
2. The published information can be deleted.

6.4 Draw UML diagram for library management system

You might also like