Non Functional Requirements for Library Management System

Non Functional Requirements 1. Product Requirements • Usability Requirement The system shall allow the users to access the system from the Internet using HTML or it’s derivative technologies like XML/CSS. The system uses a web browser as an interface. Since all users are familiar with the general usage of browsers, no special training is required. The system is user friendly and online help makes using the system easy and also the product will support multiple languages such as Sinhala, Tamil and English. • Availability Requirement The system is available 100% for the user and is used 24 hrs a day and 365 days a year. The system shall be operational 24 hours a day and 7 days a week. • Efficiency Requirement Mean Time to Repair (MTTR) - Even if the system fails, the system will be recovered back up within an hour or less. • Accuracy The system should accurately provide real time information taking into consideration various concurrency issues. The system shall provide 100% access reliability. • Performance Requirement The information is refreshed at regular intervals depending upon whether some updates have occurred or not. The system shall respond to the member in not less than two seconds from the time of the request submittal. The system shall be allowed to take more time when doing large processing jobs. Responses to view information shall take no longer than 5 seconds to appear on the screen. • Reliability Requirement The system has to be 100% reliable due to the importance of data and the damages that can be caused by incorrect or incomplete data. The system will run 7 days a week, 24 hours a day. • Maintainability and Portability Requirements Changes (new patrons addition, password changes, database changes) must be verified once per day at least. The system should provide automatically notification to patrons by e-mail about item’s overdue, reservation results, availability of reserved item and etc .

Organizational Requirements • Implementation Requirements Deploying and commissioning the library system should take very short time period(one month) , and the implementation involves library system installation, user training and maintenance. Ability to cope with any number of branches, patrons, patron categories, item categories, items, currencies and other data. Easy-to-use circulation policies, strong patron management, intuitive navigation, and extensive permissions for staff accounts. • Software Quality Attributes The Quality of the database is maintained in such a way so that it can be very user friendly to all the users of the database. The database will be MySQL. • Hardware Constraints The system requires a database in order to store persistent data. The database should have backup capabilities. In some environments, RAM utilization and secondary storage (or lack of it) are very real restrictions. There are many other restrictions that may be imposed by particular hardware environments, but it is probably not beneficial to individually identify them. • Software Constraints The development of the system will be constrained by the availability of required software such as database and development tools. To develop the system we will use Java language for GUI and My SQL for the database

External Requirements • Safety Requirements The database may get crashed at any certain time due to virus or operating system failure. Therefore, it is required to take the database backup and the database should be recover within thirty minutes. • Security Requirements We are going to develop a secured database for the library.There are different categories of users namely librarian, administrator, library staff ,members etc. Depending upon the category of user the access rights are decided. It means if the user is an administrator then he can be able to modify the data,delete,append etc. All other users other than library staff only have the rights to retrieve the information about database. All system data must be backed up every 24 hours and the backup copies stored in a secure location which is not in the same building as the system. •

Legal Requirements

Personal information should be protected. The system should comply with quality assurance standards. The development process to be used must be explicitly define and must be conformant with ISO 9000 standards.