Software

Requirements

Specification

LIBRARY MANAGEMENT SYSTEM

Version 1.0 approved

Prepared by aparna semalty

LOVELY PROFESSIONAL UNIVERSITY,PUNJAB

September 25,2017
Software Requirements Specification for library management system

Table of Contents

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

11.1 Purpose .................................................................................................................

11.2 Document Conventions.........................................................................................

11.3 Intended Audience and Reading Suggestions........................................................

11.4 Project Scope.........................................................................................................

11.5 References.............................................................................................................

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

2.1 Product Perspective................................................................................................

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

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

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

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

2.6 Assumptions and Dependencies................................................................................

3. System Features ........................................................................................................................

3.1. Database Storage ...............................................................................................................

3.2. Functional Requirements......................................................................................

3.2.1 Interface Requirements...........................................................................................

4.Non Functional Requirements..................................................................................................

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

4.4. Communications Interfaces................................................................................................

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

5.1Performance Requirements...................................................................................................

5.2Safety Requirements............................................................................................................. .

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

5.4Hardware Constraints.....................................................................................................

5.5 Software Constraints............................................................................................... .....................

5.6Design Constraints.......................................................................................................... ..............

Requirements Specification for library management system Page 1

1.Introduction

1.1Purpose

The main objective of this document is to illustrate the requirements of the project

Library Management system

The document will give the detailed description of the both functional and non functional
requirements of the client proposed by the them. The document has been made after a number of
consultations with the client and we have kept in consideration all the requirement specifications of
the given Project.

1.2Document Conventions

The list of conventions used in the document and the project as well Administrator is as follow:

A login id representing a user with user administration privileges to the software.

User:

A general login id assigned which will be assigned to most users

Client:

Intended users for the software

SQL(Structured Query Language):

To retrieve information from a database

SQL Server:

A server which is used to store data in an organized format

Layer:

It represents a section of the project

User Interface Layer:

The section of the assignment referring to what the user interacts with directly

Data Storage Layer:

The section of the assignment refers to where all data is recorded

Data flow diagram(DVDs):

It shows the dataflow between the entities.

Boolean:
It gives a true/false notation

Interface:

A source to communicate across different mediums

Unique Key:

It is used to differentiate entries in a database

1.3Intended Audience and Reading Suggestions

The intended audiences for this document are as follow:

Various team members of Innovative library Solutions.

The administrative staff of LOVELY PROFESSIONAL UNIVERSITY who is theclient.

The Project Supervisor Miss Surbhi Sharma. This document will be reviewed frequently to check if
the different phases of the project are completed by meeting all the given requirements.If there is
any changes they will be updated.

1.4 Project Scope

Project Title : Library Management System Date : 25-09-2017 Prepared By :Aparna Semalty

In this project i have basically updated the manual library system into internet based application so
that the users can know the details of their account ,availability of books etc.,

Product Characteristics and Requirements :

1. 4.1Secured database.

1.4.2 User tracking

1.4.3. Search features

1.4.4.Calculating fines

1.4. 5.Checking the availability of books

1.4. 6.Students will get an E-mail before the due date in order to avoid fines

Project Management Deliverables:

Project plan, Research finding reports, Work breakdown structures,Scope statements, Project
charters, Training manuals, lessons learn report etc.,
Product-related deliverables :

Research reports ,design documents, software code, hardware,test plan, project benefit
measurement plan etc.,

Project Success Criteria:

My main goal is to complete this project within the allotted time. It is necessary to develop a
method for capturing the benefits while the Library management system is being developed, tested,
and after it is rolled out.

1.5References

Various List of other documents or Web addresses from where student can find book online. These
may include user interface style guides, standard link which will provide enough information so that
the reader could access a copy of each reference, including title, author, version number, date, and
source or location.

2.Overall Description

2.1Product Perspective

The proposed Library Management System ,which is developed to ease the Library Management
Solutions is really helpful. This System will provide a search functionality to facilitate the search of
resources. This search will be based on various categories via. book name or the ISBN. Also
Advanced Search feature will be also provided in order to search various categories simultaneously.
Further the library staff can add/update/remove the resources

Further each branch will be managed individually by that branch library staff. The System should
reflect and support this decentralized structure and the students can know the number of available
books, information about their account etc.,

2.2Product Features

There are two different users who will be using this product:

2.2.1Librarian who will be acting as the administrator

2.2.2Student of LPU who will be accessing the Library online.

The features that are available to the Librarian are:

A librarian can issue a book to the student,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 of the books to the database,Edit the information of the
existing books,Can check the report of the issued Books,Can access all the accounts of the students.
 The features available to the Students 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,history of books issued,ans can
search books.

2.3User Classes and Characteristics

There are numerious kinds of users for books, Usually web books are visited by various users for
different reasons. The users include :

Students who will be using the above features by accessing Library online.

Librarian, as the controller and of an administrator.

2.4Operating Environment

The product will be operating in windows environment. It will be compatiable on every browser.The
only requirement to use this online product would be the internet connection.

2.5Design and Implementation Constraints

The product accomplished with login facility so that specific function is available to specific student.

2.6Assumptions and Dependencies

The product needs following third party product.

Microsoft SQL server to store the database.

ASP to develop the Product

3. System Features

3.1.1 Database Storage

3.1.1.1 Description and Priority

Proposed Database is intended to store, retrieve, update, andmanipulate information related to

university which include: Books availability; Staff information;Student details;My
Account;Calculation of fines.

3.1.2. 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 Id and password is
valid, the response to this action is the administrator will be able to modify, view, add, delete and all
other functions that can be performed.
3.2. Functional Requirements

All the list of Functional and non functional requirements which are applicable to the Library
Management System.

3.2.1 Interface Requirements

Description of software interfaces with other software products or users for input or output.

3.2.1.1 UserInterfaces: It describes how this product interfaces with the user.

GUI(graphical user interface)

Here are some of the features to illustrate user interface

1.Description

The user interface must be customizable by the administrator

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

3.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,switching between interfaces with the minimum impact for the users.

4.Risks

To reduce the circumstances under which this requirements are not able satisfied, there must be a
backup.In order to reduce the probability of this occurrence the entire design team will be trained
the basic html.

5.Dependencies for other requirements

All user interfaces should be able to interact with the user management module and a part of the
interface must be dedicated to the login/logout module

4.Non Functional Requirements

4.1. User Interfaces

4.2.Hardware InterfaceOperating System: Windows10,Windows8, or linux ;Processor: Pentium 3.0

GHz or higher;RAM: 256 Mbor more;Hard Drive: 10 GB or more
4.3.Software Interfaces: Database-SQL Server;Application-ASP (Active Server Pages);Web Server-IIS
(Internet Information Services (IIS) is a powerfulWeb server that provides a highly reliable,
manageable, and scalableWeb application infrastructure)

4.4. Communications Interfaces:

The Customer must connect to the Internet to access the website

Broadband Connection with a Internet Provider.

5.Other Nonfunctional Requirements

5.1

Performance Requirements

The proposed system that we are going to develop will be used as the Chief performance system
within the university which will interact 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.

5.2Safety Requirements

The database may get crashed at any certain time due to virus or operating system failure.
Therefore, it is required to take the database backup

5.3Security Requirements

It should be user friendly .Since we are going to develop a secured database for the university
.There are different categories of users namely teaching staff,administrator,library staff ,students
etc.It means if the user is an administrator then he can be able to modify the data,delete,append
etc., All other users other than library staff only have the rights to retrieve the information about
database.

5.4Hardware Constraints

The system requires a database in order to store sequentially data. The database should have
backup capabilities.

5.5 Software Constraints

The development of the system will be constrained by the availability of required software such as
web servers, database. The availability of these tools will be governed by the University .all the new
features must be updated from time to time.

5.6Design Constraints

The system must be designed to allow web usability. That is, thesystem must be designed in such a
way that will be easy to use and visible on most of the browsers.