You are on page 1of 11

Software Requirements

Specification

For

Library Management System

Prepared by Gagandeep

Lovely Professional University


- ii -

Table of Contents

1. Introduction ..............................................................................................................................1

1.1 Purpose.................................................................................................................................1

1.2 Document Conventions ........................................................................................................1

1.3 Intended Audience and Reading Suggestions ......................................................................1

1.4 Definitions, acronyms, abbreviations...................................................................................1

1.5 Scope 1

2. Overall Description ..................................................................................................................2

2.1 Product Description .............................................................................................................3

2.2 Product Features...................................................................................................................3

2.3 User Classes and Characteristics..........................................................................................4

2.4 Operating Environment ........................................................................................................4

2.5 Design and Implementation Constraints ..............................................................................5

3. Specific Requirements .............................................................................................................5

3.1 Functional Requirement .......................................................................................................5

4. External Interface Requirements ...........................................................................................6

4.1 User Interfaces .....................................................................................................................6

4.2 Hardware Interfaces .............................................................................................................7

4.3 Software Interfaces...............................................................................................................7

5. Other Nonfunctional Requirements .......................................................................................7

5.1 Look and Feel Requirements ...............................................................................................7

5.2 Performance Requirements ..................................................................................................7

5.3 Security Requirements .........................................................................................................8


- iii -
Page 1

1.Introduction

1.1 Purpose

The main objective of this document is to illustrate the requirements of the project Library
Management system. The document gives the detailed description of the both functional and non-
functional requirements proposed by the client. The purpose of this project is to provide a friendly
environment to maintain the details of books and library members. The main purpose of this project
is to maintain easy circulation system using computers and to provide different reports.

1.2 Document Conventions:

Throughout this documentation, the following conventions have been used: -

Fonts: Times New Roman

Size 16 For Main Headings

Size 14 For Sub Headings

Size 12 For the Rest of the Document

Words in Bold are important terms, and have been formatted to grab the attention

of the reader

1.3 Intended Audience and Reading Suggestions

The document is intended for all the stakeholders customer and the developer (designers, testers,
maintainers). This SRS document contains the complete set of functionalities of the developed
web-application Library Management System, the various requirements to make use of it. It is
suggested that the individuals referring it to go through the introduction and overall description
before studying various aspects of it

1.4 Definitions, abbreviations

1.4.1 Definitions
Page 2

Library management system

Software requirements specification

Personal Computer

Microsoft Internet Explorer

1.4.2 Abbreviations

LMS Library management system

SRS Software requirements specification

PC Personal Computer

HDD - Hard Disc Drive

RAM Random Access Memory

LUT Lappeenranta University of Technology

IE Microsoft Internet Explorer

1.5 Project Scope

LPU Library Management System will allow to perform all necessary procedures for librarians and
students. According to customer requirements the software to be developed will consist of three
databases: Items database (books, journals, magazines, newspapers, diploma thesis, etc.) Patrons
database a small Access-based database with information that University has integrated with Items
database.

LMS will also provide all necessary services for databases such as creating, deleting, updating and
searching information. Patrons will be able to access to the library site (web-based) through the
Internet or through the LAN-connected computers, scattered throughout the University for sending
request, receiving information about current status of the books or status of fine. User interfaces will
be easy-to-use.
Page 3

There are several motivations to order new computer-based College LMS:

To modernize University Library database, where data was stored in a card-based catalog

To optimize librarians work and time.

To expand services of library and patrons possibilities

To check ability of commercial using of library management systems.

The LMS will allow remote access to library database via Internet and LAN for patrons after
authorization procedures. The patrons could search, send requests.

2. Overall Description

2.1 Product Description

Library Management System is a computerized system which helps user(librarian) to manage the
library daily activity in electronic format. It reduces the risk of paper work such as file lost, file
damaged and time consuming. It can help students, faculties and librarian to manage the transaction
or record more effectively and timesaving.

2.2 Product Features

Features provided by the LPU library management system:


1. Store necessary information about items in the library:
- Author
- Items title
- Call number
- Account Number
- Year of publication
- Number of copies
- Current status
- Keywords
2. Allow a search item by author, title or keywords.
3. System will provide librarian to add, modify, and remove items to/from the library
database, and check availability of the item.
4. System will allow students, faculties to get information about his/her status after
authorization procedures:
Page 4

- Registration ID
- Number and information about checked out items
- Requested items information
5. Possibility to search items though the Internet after authorization procedures.

2.3 User Classes and Characteristics

The system provides different types of services based on the type of users [Member/Librarian].
The Librarian will be acting as the controller and he will have all the privileges of an administrator.
The member can be either a student or staff of the university who will be accessing the Library
online.
The features that are available to the Librarian are: -
A librarian can issue a book to the member.
Can view the different categories of books available in the Library
Can view the List of books available in each category
Can take the book returned from students
Add books and their information to the database
Edit the information of existing books
Can check the report of the existing books
Can check the report of the issued books
Can access all the accounts of the students

The features that are available to the Members are: -


Can view the different categories of books available in the Library
Can view the List of books available in each category
Can own an account in the library.
Can view the books issued to him
Can put a request for a new book
Can view the history of books issued to him previously
Can search for a particular book

2.4 Operating Environment

The product will be operating in windows environment. The Library Management System is a
website and shall operate in all famous browsers, for a model we are taking Microsoft Internet
Page 5

Explorer, Google Chrome, and Mozilla Firefox. Also, it will be compatible with the IE 6.0. Most of
the features will be compatible with the Mozilla Firefox & Opera 7.0 or higher version. The only
requirement to use this online product would be the internet connection. The hardware configuration
includes a smart device.

Libraries will also be occupied with automatic book detecting system which will automatically
detect the book when a student or faculty will come to get book issued. Also, librarians should be
having barcode scanners to scan the ID of the student or faculty and issue them a book.

2.5 Design and Implementation Constraints

Validate Username/Password:

Validate that password and username matches.

If password is not correct, prompt error message Password is Incorrect.

Login Again

3. Specific Requirements

3.1 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 requests 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 items
overdue
Page 6

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.

3.1.2 Requirements of the AAs Management interface

Authorization

The User Login to login to his account.

Functional requirement 1:

Description: The Login interface checks if the LMS accounts is valid. If user name and
password is write it will match and login to website.

Input: Request from the LMS to verify login (User name and password.)

Processing: Check if accounts exists.

Output: Valid or invalid accounts.

4. External Interface Requirements

4.1 User Interfaces

The software provides graphical interface for the user and the administrator can operate on the
system, performing the required task such as create, update, viewing the details of the book.
It allows user to view quick reports like Book Issued/Returned in between particular time.
It provides stock verification and search facility based on different criteria.
All the modules provided with the software must fit into this graphical user interface and
accomplish to the standard defined.
The design should be simple and all the different interfaces should follow a standard template
The user interface should be able to interact with the user management module and a part of the
interface must be dedicated to the login/logout module
Page 7

4.2 Hardware Interfaces

Since the application must run over the internet, all the hardware shall require to connect
internet will be hardware interface for the system. As for e.g. Modem, WAN LAN,
Ethernet cross Cable. The device also contains a SD card slot for extra storage of cache of
application. The website periodically gets updated by the page developers.

The basic interfaces will be barcode reader to read the details from the Id card.

4.3 Software Interfaces

Database: SQL Server.

Application: ASP (Active Server Pages)

Web Server: IIS (Internet Information Services (IIS) is a powerful Web server that provides
a highly reliable, manageable, and scalable Web application infrastructure)

5. Other Nonfunctional Requirements


5.1 Look and Feel Requirements

According to the requirements, the LPU LMS should include following interfaces:

The LMS interfaces will the same for patrons and librarians based on Web 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 also include Web interface. This interface
will provide search, request and renew procedures, connection with other online databases. Web
interface should work correctly in different browsers.

5.2 Performance Requirements

The proposed system that we are going to develop will be used as the Chief performance system
within the different campuses of the university which interacts with the university staff and students.
Therefore, it is expected that the database would perform functionally all the requirements that are
specified by the university.

The performance of the system should be fast and accurate


Page 8

Library Management System shall handle expected and non-expected errors in ways that
prevent loss in information and long downtime period. Thus, it should have inbuilt error
testing to identify invalid username/password

The system should be able to handle large amount of data. Thus, it should accommodate
high number of books and users without any fault

5.3 Security Requirements

System will use secured database

Normal users can just read information but they cannot edit or modify anything except their
personal and some other information.

System will have different types of users and every user has access constraints

Proper user authentication should be provided

No one should be able to hack users password

There should be separate accounts for admin and members such that no member can access
the database and only admin has the rights to update the database.

6. Other Requirements

6.1 Data and Category Requirement

There are different categories of users namely teaching staff, Librarian, Admin, students 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 except the
Librarian only have the rights to retrieve the information about database. Similarly, there will be
different categories of books available. According to the categories of books their relevant data
should be displayed. The categories and the data related to each category should be coded in the
particular format.