Library management system Functional & Non Functional requirements
By: Prof. Dr. Fazal Rehman | Last updated: February 22, 2024
Functional requirements of Library management system
Definitions:
All terms used by the system should have clear definitions.
Membership Data (Member Data):
There should be membership integration in the system.
Membership data should include name, date of birth, address, and contact number.
Book Data:
Each book should have a unique identification number.
Books data should include title, author, reputation, and availability status.
Issue Data:
When a member issues a book, his data should be recorded.
This data should include the book, member, and issue date.
Reports:
Daily, weekly, and monthly reports should be possible.
Reports on membership, availability of books, and exits should be included.
Items Integration:
In addition to books, it should be possible to integrate items such as CDs, DVDs, and other items.
Reservation:
Members should be able to reserve a book.
Reserved books should be kept for a specified period.
Availability Tracking:
The availability of books should be kept up-to-date at all times.
Released books should be available immediately.
Notification Access (Notifications):
Members should be able to have notification access to the system to inform about the return and reserve of books.
Renewal:
Members should have the possibility to renew books, but this should be limited.
Non Functional requirements of Library management system
Performance:The system should work quickly so that members and officials do not have to wait for long.Security:All membership and book data must be kept secure.Only brief personnel should have access to membership and book settings.Traceability:Every member, every book, and every technique should be recorded so that inquiry can be made at any point.Technology: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.Scalability: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.Reliability:Data must be protected even in the event of a chronic or malfunctioning system.Availability: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.
