Site icon

Library management system Functional & Non Functional requirements

Functional requirements of Library management system

  1. Definitions:
    • All terms used by the system should have clear definitions.
  2. Membership Data (Member Data):
    • There should be membership integration in the system.
    • Membership data should include name, date of birth, address, and contact number.
  3. Book Data:
    • Each book should have a unique identification number.
    • Books data should include title, author, reputation, and availability status.
  4. Issue Data:
    • When a member issues a book, his data should be recorded.
    • This data should include the book, member, and issue date.
  5. Reports:
    • Daily, weekly, and monthly reports should be possible.
    • Reports on membership, availability of books, and exits should be included.
  6. Items Integration:
    • In addition to books, it should be possible to integrate items such as CDs, DVDs, and other items.
  7. Reservation:
    • Members should be able to reserve a book.
    • Reserved books should be kept for a specified period.
  8. Availability Tracking:
    • The availability of books should be kept up-to-date at all times.
    • Released books should be available immediately.
  9. Notification Access (Notifications):
    • Members should be able to have notification access to the system to inform about the return and reserve of books.
  10. Renewal:
    • Members should have the possibility to renew books, but this should be limited.

Non Functional requirements of Library management system


The system should work quickly so that members and officials do not have to wait for long.


All membership and book data must be kept secure.

Only brief personnel should have access to membership and book settings.


Every member, every book, and every technique should be recorded so that inquiry can be made at any point.


The system should be configured according to the current technology and should have the possibility to be updated in the future.

Training and Usability:

There should be a training program for personnel using the system.

The system should be user-friendly and easy to use.


The system should be able to cope with growing opportunities in membership and data.

Legal and Ethical:

The system should comply with local and international laws and ethical principles.


Data must be protected even in the event of a chronic or malfunctioning system.


The system should be available 24/7 so that members can access their accounts and data at any time.

Dismissal methods (Disaster Recovery):

The system should have data backup so that the data is safe in case of any data loss.

Exit mobile version