The document outlines the functional, non-functional, and other requirements for a library management system (LMS). The functional requirements specify that the LMS should store information on librarians, patrons, items, and transactions, and allow searching, adding/deleting items, and generating reports. Non-functional requirements include high availability, fast response times, reliability, and accuracy. The LMS must also meet operational requirements like hardware specifications, interface requirements, and security standards.

1. Name: Ahsan Riaz Sp13-bse-123
Library Management System:
 Functional requirements:-
Describe functionality or system services
Depend on the type of software, expected users and the type of system where the software is used
 Functional requirements are the following:
 The LMS should store all information about librarians and patrons, their access keys,
priority and etc.
 The LMS should store all information about items and patrons in two separated
databases
 The LMS allow searching items by author, title or keywords
 The LMS should support 500 patrons and 1000 requests/min simultaneously.
 The LMS should allow librarians to add, delete and modify items in database, and
check availability of the items.
 The LMS should generate request’s reports for librarians every day, on base of which
librarians could make decisions about acquiring or retirement the item.
Performance Requirements:-
 Any interface between a user and LMS should have a maximum response time of 5
seconds
 The response should be fast enough to avoid users’ response collisions
 The LMS should be available for use 24 hours per day, 365 days per year.
 The LMS should support 500 patrons and 1000 requests/min simultaneously
Operational Requirements:-
 The LMS should be used on IBM-compatible workstations with 50Mbytes free space
on HDD for library workstations

2.  Non-functional requirements:-
The definition for a non-functional requirement is that it essentially specifies how the system
should behave and that it is a constraint upon the systems behavior. One could also think of non-
functional requirements as quality attributes for of a system.
�
 Product requirements:-
Requirements which specify that the delivered product must behave in a particular way, e.g.
execution speed, reliability etc.
 Availability Requirement:-
The system is available 100% for the user and is used 24 hrs a day and 365 days 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.
 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.
 Inverse Requirements:-
 Inverse requirements can be functional and non-functional.
 When a customer specifies that something must not be done. For example, User ID
should only contain digits.
 The system shall not use red color in the user interface, whenever it is asking for inputs
from the end-user
 Software would be user Friendly

3.  The system will support multiple languages such as Urdu and English.
 Changes (new patron’s addition, password changes, database changes) must be verified
once per day at least.
 The system lets the library staff to check which all members have blocked the
books and whether they can borrow any more books or not.
 The system allows the Librarian to create the books catalog, add/delete books and
maintain the books catalog. The system updates the billing system as and when the
member borrows or returns a book.
 Domain requirements
 Requirements that come from the application domain of the system that reflect the
characteristics of that domain
 May be functional or non-functional.
 If domain requirements are not satisfied, the system may be unworkable.
Library system Domain Requirements :-
 Because of copyright restrictions, some documents must be deleted immediately on arrival.
Depending on the user’s requirements, these documents will either be printed locally on
the system server for manually forwarding to the user or routed to a network printer.
 Student could not download anything.
 Social websites are block for students.
 Software should be developed in Java Language.
 Software run on Windows, Linux.
Standards-Based
 A modern library management system supports a wide array of standards, including
bibliographic standards such as MARC 21, information industry standards such as the
ANSI/NISO and ISO standards, and character encoding standards such as Unicode
Integrated
 Library management systems consist of separate modules, each of which handles a
different aspect of library operation
 Operating system :-
 Window
 Hard disk :200 GB
 RAM : 2gb
 Processor : Pentium(R)Dual-core CPU

4. Software interface:-
 Java language
 Net beans IDE 7.0.1
 MS SQL server
Communication interface:-
 Windows
Security:-
 Controlling the access to the database provides security to the system.
Availability:-
 The system is online 24 hours a day and 365 days a year.
Usability:-
 The system is easy to use for all the users.
 Design and Implementation Constraints:-
They are development guidelines within which the designer must work.
Example:-
 The system shall be developed using the Microsoft .Net platform
 The system shall be developed using open source tools and shall run on Windows
operating system
 The System should be implemented using Java Language
 The software must fit into the memory of a 512Kbyte machine
 Constraints:-
 The information of all the users must be stored in a database that is accessible by the
Library Management System.
 The university information security system must be compatible with the Internet
applications.
 The Library Management System is connected to the university computer and is running
all 24 hours a day.
 The users access the Library Management System from any computer that has Internet
browsing capabilities and an Internet connection.