Software Requirment Specification

for

Web based Library Management System

version<1.0>

Prepared By:

Harshal Khanolkar T.E COMP A (25) harshalkhanolkar143@gmail.com

Chetan Londhe T.E COMP A (33) chetanblondhe1@gmail.com

Instructor. Mr.Kadam S B
Course: Software Engineering
 CONTENTS
1. INTRODUCTION
1.1 PURPOSE..........................................................................................................................................................................1
1.2 SCOPE...............................................................................................................................................................................1
1.3 INTENDED AUDIENCE, DEFINITION, ACRONYMS AND ABBREVIATION........................................................2
1.4 REFERENCES...................................................................................................................................................................2
1.5 OVERVIEW.......................................................................................................................................................................2

2. OVERALL DESCRIPTION
2.1 PRODUCT PERSPECTIVE.............................................................................................................................................3
2.2 PRODUCT FUNCTIONS..................................................................................................................................................3
2.3 USER CHARACTERISTICS............................................................................................................................................3
2.4 OPERATING ENVIRONMENT.......................................................................................................................................3
2.5 DESIGN AND IMPLEMENTATION CONSTRAIN.......................................................................................................4
2.6 ASSUMPTIONS AND DEPENDENCIES .......................................................................................................................4
2.7 USER DOCUMENTATION..............................................................................................................................................4

3. EXTERNAL INTERFACE REQUIREMENT

3.1 USER INTERFACE ..........................................................................................................................................................5
3.2 HARDWARE INTERFACE .............................................................................................................................................5
3.3 SOFTWARE INTERFACE ...............................................................................................................................................5
3.4 COMMUNICATION INTERFACE ..................................................................................................................................5

4. SYSTEM FEATURES
4.1 DESCRIPTION AND PRIORITIES .................................................................................................................................6
4.2 STIMULUS / RESPONSE SEQUENCES ........................................................................................................................6
4.3 FUNCTIONAL REQUIREMENTS...................................................................................................................................6

5. OTHER NON-FUNCTIONAL REQUIREMENT

5.1 PERFORMANCE REQUIREMENTS...............................................................................................................................7
5.2 SAFETY REQUIREMENTS..............................................................................................................................................7
5.3 SECURITY REQUIREMENTS..........................................................................................................................................7
5.4 SOFTWARE QUALITY ATTRIBUTES...........................................................................................................................8

6. SUMMERY

1. Introduction
 Borrowing books, returning books or viewing the available books at the Library of the local college is
currently done manually where in the student has to go to the Library. Librarian checks the student ID
and allows the member to check the list of books available and borrow the books if the book is available.
The librarian then updates the member database and also the books database. This process takes more
time and it is waste of time and money for the student to come to the library to check for the book if
book is not available and also there is burden of record keeping.
We have decided to investigate the use of Web based Library Management System (WLMS). This
system would be used by members who may be students or professors of that college to check the
availability of the books and borrow the books, and by the librarian to update the databases.
This document is developed after a number of consultations with the client and considering the complete
requirement specifications of the given Project. The final product will be meeting all the requirements of
this document.

1.1 Purpose
The purpose of Software Requirements Specification (SRS) document is to describe the behavior
of the Web based Management Library System with the release number 0.1. The document describes
the function and nonfunctional requirements such as the user interfaces. Requirements Specification
defines and describes the operations, interfaces, performance, and quality assurance requirements of
the WLMS. It also describes the design constraints that are to be considered when the system is to be
designed. It also involves all hardware and software requirements for product, behavior of it and its
components. The main purpose of this project is to maintain easy circulation system using
computers.

1.2 Scope
The Software Requirements Specification captures all the requirements in a single document. The
Web Based Library Management System that is to be developed provides the members of the Library
and employees of the library with books information, online booking of books and many other
facilities. The Online Library System is supposed to have the following features.
 The product provides the members with online booking of books capabilities and the Online
Library System is up and running all day.
 The system provides login facility to the users and librarian and administrator.
 The system provides the members with the option to check their account and/or change their
options like password of the account whenever needed all through the day during the library
hours.
 The system allows the members to block the books 24 hours a day and all the through the
semester.
 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.
 The book catalog is automated and the decision of offering the book based on the category of the
book is automatically decided.
 We also have an order department, which manages to add or remove a book from the Library.

1.3 Intended Audience, Definition, Acronyms and Abbreviation

 Intended Audience
 The intended readers of this document are the developers of the site, testers, library owners and
managers and client and stakeholder. This document also includes sections relevant to the
operational and maintenance group. This document will be reviewed frequently by the above
audiences to check if the different phases of the project are being completed by meeting the
given requirements. It is expected that the intended audience shall critically review this
document for functional accuracy and revert to team with their feedback and comments within a
less time

 Acronyms and Abbreviation

Acronym Meaning
WLMS Web Library Management System
MS SQL Microsoft Structured Query Language
ASP Active Server Pages
ISBN International Standard Book Number
IEEE Institute of Electrical and Electronics
Engineers

1.4 References
The SRS document uses the following documents as references
 IEEE. IEEE Std. 830-1998 IEEE Recommended Practice for Software Requirements
 http://www.pdfebooklibrary.com/ebooks/srs-library-management-system.pdf

1.5 Overview
This document will provide the outline of the requirements, overview of the characteristics and
constraints of the WLMS.
 Section 2: The items such as product perspective, product function, user characteristics,
constraints, assumptions and dependencies and requirements subsets are described in this section.
 Section 3: This section of SRS contains all the software requirements mentioned in section 2 in
detail sufficient enough to enable designers to design the system to satisfy the requirements and
testers to test if the system satisfies those requirements.

2. Overall Description
2.1 Product Perspective
The Web based Library Management System is to be used by Libraries to improve the efficiency of
Librarians, Library employees and Users. The Online Library System to be developed benefits
greatly the members and the Librarian of college. The system provides books catalog and
 information to members and helps them decide on the books to borrow from the library. The
Librarian can keep the books catalog updated all the time so that the members (students and the
professors) get the updated information all the time.
The complete overview of the system is as shown in the overview diagram below:
The product to be developed has interactions with the users: Librarian, Members who are the
students and professors
The product has to interact with other systems like: Internet, Billing System and the College Security
System.

Librarian Billing System

The proposed Web based Library

Management System

Internet
Users College Security System
Overview of the proposed system

2.2 Product functions

The Online Library System provides online real time information about the books available in the
Library and the user information. The functions of the system include the system providing different
type of services based on the type of users [Member/Librarian].
 The member should be provided with the updated information about the books catalog.
 Provisions for the members to borrow the books they want, if all the other required rules hold
good.
 The member is given a provision to check his account information and change the account
information any time in the given valid period.
 The members are provided with the books available roster and allowed to choose the books,
which they want to use in the coming up days.
 The librarian is provided with interfaces to add/delete the books available in the book catalog.
 The members when book returning process, if book is broken condition the member has to pay
and fine is calculated by billing system.
 The system uses the College security requirements to provide the login facility to the users.

2.3 User characteristics

The users of the system are members, librarian of the college and the administrators who maintain
the system. The members and the librarian are assumed to have basic knowledge of the computers
and Internet browsing. The administrators of the system to have more knowledge of the internals of
the system and is able to rectify the small problems that may arise due to disk crashes, power failures
and other catastrophes to maintain the system. The proper user interface, user’s manual, online help
and the guide to install and maintain the system must be sufficient to educate the users on how to use
the system without any problems.
 2.4 Operating Environment
The product will be operating in windows environment. 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.

2.5 Design and Implementation Constrain

 The information of all the users must be stored in a database that is accessible by the Web based
Library System.
 The college security system must be compatible with the Internet applications.
 The Online Library System is running all 24 hours a day.
 The users access the WLMS from any computer that has Internet browsing capabilities and an
Internet connection.
 The billing system is connected to the Web based Library System and the database.
 The users must have their correct usernames and passwords to enter into the Web based Library
System.

2.6 Assumptions and Dependencies

 The users have sufficient knowledge of computers.
 The college computer should have Internet connection and Internet server capabilities.
 The users know the English language, as the user interface will be provided in English
 The product can access the college student database

2.7 User Documentation

The product will include user manual. The user manual will include product overview, complete
configuration of the used software (such as SQL server), technical details, backup procedure and
contact information which will include email address. There will be no online help for the product at
this moment.

3. External Interface Requirement

3.1 User Interface
Describes how this product interfaces with the user.
 GUI - Describes the graphical user interface if present. This section should include a set of screen
dumps or mockups to illustrate user interface features.
Description - The user interface must be customizable by the administrator
Criticality- This issue is essential to the overall system. All the modules provided with the software
must fit into this graphical user interface and accomplish to the standard defined.
Technical issues - In order to satisfy this requirement the design should be simple and all the
different interfaces should follow a standard template. There will be the possibility of changing
colors and images, plus switching between interfaces with the minimum impact for the users.

3.2 Hardware Interface

 Server Side
 Operating System: Windows 9x/XP, Windows ME
 Processor: Pentium 5.0 GHz or higher
 RAM: 512 Mb or more
 Hard Drive: 10 GB or more
 Client Side
 Operating System: Windows 7, 8, 10 or MAC or UNIX
 Processor: Pentium IV or 2.0 GHz or higher.
 RAM: 512 Mb or more

3.3 Software Interface

 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)

3.4 Communication Interface

 Broadband Internet
 Dialup or Broadband Connection with an Internet Provider.

4. System Features
4.1 Description and Priorities
Proposed Database is intended to store, retrieve, update, and manipulate information related to
college which include
 Books availability
 Student details
 My Account
  Calculation of fines
4.2 Stimulus / Response Sequences
Responses for Administrator: The administrator can Login and Logout. When the Administrator
Logs into the Library system. The system will check for validity of login .If the Login and password
are valid, the response to this action is the administrator will be able to modify, view, add, deleting
and all other functions that can be performed on the database
4.3 Functional Requirements
 Librarian
Prerequisite (admin signed in) for all requirements below
Requirement Title Description Priority
ID
R1.01.01 insert book This action is done to add new book to library 2
book collection
R1.01.02 delete / modify This event is to delete an existing book or modify 2
book its information.
R1.01.03 Validate user When a new member sign up then he should wait 1
account for acceptance by Administrator according to
library policies (e.g. fees required).
R1.01.04 Delete member Admin can delete a member due to some specific 2
rules.
R1.01.05 modify Admin can extend the borrowing time or number 2
member rank of book borrowed simultaneity to a user.
 Normal User
Requirement Title Description Priority
ID
R1.02.01 register when new user enters WLMS for the first 3
time then he has to register
R1.02.02 Extending borrowing member can extend the borrowing time to 2
deadline. some limit decided by Admin
R1.03.03 reset password When a member forgets his password he 1
can claim it back via e-mail.
R1.04.04 Edit personal If some user changes for example his 2
information mobile number, he can modify it.

 Common User
Requirement Title Description Priority
ID
R1.03.01 Login Both Admin and members must be logged in before 1
they modify any information
R1.03.02 Search for When user or admin wants to search on some book 1
book by name, author or subject etc.

5. Other Non-functional requirement

5.1 Performance Requirements
 Response Time
The Splash Page or Information page should be able to be downloaded within a minute using a
56K modem. The information is refreshed every two minutes. The access time for a mobile
device should be less than a minute. 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.
 Administrator and Librarian Response
The system shall take as less time as possible to provide service to the administrator or the
librarian
 Throughput
The number of transactions is directly dependent on the number of users; the users may be the
Librarian, employees of the Library and also the people who use the Library for checking-out
books, returning books and checking online library account.
 Capacity
The system is capable of handling 250 users at a time.

5.2 Safety Requirements

 Availability
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.
 Mean Time Between Failure(MTBF)
The system will be developed in such a way that it may fail once in a year.
 Mean Time to Repair (MTTR )
Even if the system fails, the system will be recovered back up within an hour or less
 Accuracy
The accuracy of the system is limited by the accuracy of the speed at which the employees of
the library and users of the library use the system

5.3 Security Requirements

 The WLMS should provide databases modification only for librarians and system administrator
after authorization procedure.
 Access to the WLMS is permitted only for College student and staff after authorization.

5.4 Software Quality Attributes

 Usability
The system shall allow the users to access the system from the Internet using HTML or its
derivative technologies.
Since all users are familiar with the general usage of browsers, no specific training is required.
The system is user friendly and self-explanatory.
 Supportability
Internet Protocol
The system shall be comply with the TCP/IP protocol standards and shall be designed
accordingly.
Billing System data capability
The member balance amount that will be calculated and sent to the billing system shall be
compatible with the data types and design constraints of the billing system Capacity.
Maintenance
The maintenance of the system shall be done as per the maintenance contract.
 Standard
The coding standards and naming conventions will be as per the American standards.

6. Summary
We have prepared Software Requirement Specification for Web-Base Library Management System. This
document is developed after a number of consultations with the client and considering the complete
requirement specifications of the given Project. The document describes the function and nonfunctional
requirements such as the user interfaces. Requirements Specification defines and describes the operations,
interfaces, performance, and quality assurance requirements of the WLMS. It also describes the design
constraints that are to be considered when the system is to be designed. The main purpose of this project
is to maintain easy circulation system using computers.