Software requirements specification

Software
Requirements
Specification
LIBRARY MANAGEMENT SYSTEM
By

Reddy Harish(10MSE0015)

Kishore Majety(10MSE0030)

Krishnasai Gudavalli(10MSE0263)

Slot-C1

TABLE OF CONTENTS
1. Introduction
1.1 Purpose
1.2 Scope
1.3 Intended Audience Definitions, acronyms and abbreviations

2. Overall Description
2.1 Product Perspective
2.2 Product Functions
2.3 Operating Environment
2.4 User Characteristics
2.5 Design and Implementation Constraints
2.6 Assumptions and Dependencies

3. External Interfaces Requirements
3.1 User Interfaces
3.2 Hardware Interfaces
3.3 Software Interfaces

4. Functional Requirements
5.Behaviorial Requirements
6. Non-Functional Requirements

Library Management System SRS Document By Harish-Kishore-Krishnasai

1. Introduction
1.1 Purpose
The purpose of this document is to describe the Library
Management System . This document contains the functional,
behavioral and non-functional requirements of the project and it
also contains the guidelines for system engineers and designers
to start working the project.

1.2 Scope
Library Management System is basically updating the manual
library system into a internet-based application so that the users
can know the details of their accounts, availability of books and
remaining time for borrowing.
The project is specifically designed for the use of librarians and
library users. The product will work as a complete user interface
for library management process and library usage from ordinary
users. Library Management System can be used by any existing
or new library to manage its books and book borrowing,
insertion and monitoring .

1.3 Audience Definitions, Acronyms and
Abbreviations

1.3.1 Audience Definitions

The intended readers of this document are the developers of the
site, testers, library owners and managers and coordinators.
Any suggested changes on the requirements listed on this
document should be included in the last version of it so it can be
a reference to developing and validating teams.


1.3.2 Acronyms and Meaning
Abbreviations Acronym
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
IEEE 830-1998 standard for writing SRS document.
I Sommerville, Software Engineering, 8th ed, Addison-
Wesley, 2007.

2. Overall Description

2.1 Product Perspective

Library Management System is a replacement for the ordinary
library management systems which depend on paper work for
recording book and users information.

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

2.3 Operating Environment
The Library Management System is a website and shall operate
in all famous browsers, for a model we are taking Microsoft
Internet Explorer ,Google Chrome,Mozilla Firefox with Flash
Player and JavaScript.

2.4 User Characteristics
Users of this Library Management System are members,
librarians and the administrators who maintain the website.
Members and librarians are assumed to have basic knowledge of
computers and Internet browsing. Administrators of the system
should have more knowledge of internal modules of the system
and are able to rectify small problems that may arise due to disk
crashes, power failures and other catastrophes.


2.5 Design and Implementation Constraints

 The information of all users, books and libraries must be
stored in a database that is accessible by the website.
 MS SQL Server will be used as SQL engine and database.
 The Online Library System is running 24 hours a day.
 Users may access from any computer that has Internet
browsing capabilities and an Internet connection.
 Users must have their correct usernames and passwords to
enter into their online accounts and do actions.

2.6 Assumptions and Dependencies

 The product needs the following third party products.
 Microsoft SQL server to store the database.
 ASP.net to develop the Product.


3. External Interfaces Requirements

3.1 User Interfaces
Login Interface :

In case the user is not registered yet, he can enter the details and
register.Which asks the user to type his username and password .
If the user entered either his username or password incorrectly
then an error message occurs.

Search :
The member or librarian can enter the type of book he is looking
for and the title he isinterested in them ,then he can search for
the required book by entering the book name.

Categories view :

Categories view shows the books categories view with ability to
Liberian to add/edit or delete category from the list.

Librarian’s Control Panel
This control panel will allow librarians to add, confirm, or
remove users; add, edit, orremove a medium. And manage
lending options.

3.2 Hardware Interfaces

Only the recommended configuration (basic requirements of a
computer system ) no other specific hardware is required to run
the software.

3.3 Software Interfaces
 Browser to load and view the web pages
 Operating System

4.Functional Requirements

4.1.1 Librarian:

Insert book:
This action is done to add new book to library book collection

Delete / modify book :
This event is to delete an existing book or modify its
information.

Delete member:
Admin can delete a member due to some specific rules.

Return book:
Admin should confirm the return of books borrowed by users
4.1.2 Normal User :


Register:
When new user enters for the first time then he has to
register

Extending borrowing deadline :
Member can extend the borrowing time to some limit
decided by Admin

4.1.3 Common Functions :

Login:
Both Admin and members must be logged in before
they modify any information

Search for book :
When user or admin wants to search on some book by
name, author or subject etc.

5.Behaviroal Requirements


Use case diagram:


6. Non-functional Requirements
Error handling

 Library Management System shall handle expected and
non-expected errors in ways that prevent loss in
information and long downtime period.

Performance Requirements

 The system shall accommodate high number of books and
users without any fault.

Safety Requirements

 System use shall not cause any harm to human users

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


Software requirements specification

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Viewers also liked

Viewers also liked (15)

Similar to Software requirements specification

Similar to Software requirements specification (20)

Software requirements specification