SRS For library managment Sysytem

                          Software Requirements Specification
                                                         For
                             Library Management System

   

Propoesd by:

       Muwadat Ali

1. Introduction

       1.1 Purpose
              The purpose of this document is to describe the Library Management System (LMS) product with the release number 0.1. This document contains the functional and non-functional requirements of the project. This document contains the guidelines for website developers system engineers and designers to start working the project.

      1.2 Overview
                    Section 2 defines the general functions of LMS, and user constraints along with our assumptions.
 Section 3 specifies functional and nonfunctional requirements; all of them are described to a level of detail sufficient for designers to design a system.

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.

     2.2 Product

           Functions 2.2.1
              Administrators  Admin should be able to insert, modify and delete books.
             ·  Can accept or reject a new user according to the library policy or      payment methods.
             ·  Increase the period for borrowing a book for specific type or group of users.
             ·  Can get the information (status report) of any member who has borrowed a book.
             ·  Add and edit book categories and arrange books by categories.
             ·  Add and edit authors and publishers information.
             ·  Can send lateness warnings to people who have exceeded deadline date.
             ·  Can record books returned by users.

2.2.2 Normal Users (Library Members)
           The member should be provided with the updated information about the books   catalog.
          ·  Members are given a provision to check their account’s information and change it.
          ·  Members have the ability to search through books by subject, title, authors or any
          · information related to the book.  Can extend the period of borrowing books according to the library policy.
          ·  The customer may suggest a book to be brought to the library book collection.

3.3 Functional requirements

              Functional requirements are the following:

1.    The LMS should store all information about librarians and patrons, their access keys, priority and etc.

2.    The LMS should store all information about items and patrons in two separated databases

3.    The LMS allow searching items by author, title or keywords

4.    The LMS should support 500 patrons and 1000 requests/min simultaneously.

5.    The LMS should allow librarians to add, delete and modify items in database, and check availability of the items.

6.    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

7.    The LMS should create notification and send to patrons by e-mail automatically after item’s overdue

8.    The LMS should allow patrons to get their personal information and status.

9.    The LMS should provide to search, request and renew items either from the library computers (LMS application) or from outside the library through College site(web-based) though the Internet.

10. The LMS should provide access to previous Access-based database, online databases

11.  The LMS will be integrated with other colleges and universities and allow interlibrary loans

Non - Functional Requirements

 Look and Feel Requirements

 According to the Customer requirements, the College LMS should include following interfaces:

Ø  The LMS interfaces will the same for patrons and librarians based on C++/Java application. Differences will depend on users’ functions. Patrons will have simple version of LMS without add, remove and modify possibilities.

Ø  The LMS interface for system administrator will include C++/Java application, Command Line, System files

Ø  Web  interface. This interface will provide search, request and renew procedures, connection with other online databases. Web  interface should work correctly in different browsers.

 Usability Requirements

As it was mentioned above, product’s users are an adults, that’s why there are no special requirements to simplicity of system.

Ø  Ergonomical and clear interface

Ø  The interface should contain prompts and help to avoid making mistakes

Ø  The product should be used by people with no training

 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 (80Gbytes for server) and 32Mbytes RAM for library workstations (256Mbytes for server)

Ø  The LMS should be correctly implemented in different Internet browsers

Ø  The LMS should correctly interface if MS Access applications and MS SQL Server

     Maintainability and Portability Requirements

Ø  Changes (new patrons addition, password changes, database changes) must be verified once per day at least

Ø  The LMS should provide automatically notification to patrons by e-mail about item’s overdue, reservation results, availability of reserved item and etc 

Ø  The LMS is expected to run under MS Windows 95/98/2000/NT/XP

     Security Requirements

Ø  The LMS should provide databases’ modification only for librarians  and system administrator after authorization procedures

Ø  Access to the LMS is permitted only for College student and staff after authorization procedures

     Legal Requirements

Ø  Personal information should be protected

Ø  The LMS should comply with quality assurance standards