Download Srs -Library Management System PDF

TitleSrs -Library Management System
File Size588.6 KB
Total Pages14
Table of Contents
                            1.Introduction
	1.1Purpose
	1.2Document Conventions
	1.3Intended Audience and Reading Suggestions
	1.4Project Scope
	1.5References
2.Overall Description
	2.1Product Perspective
	2.2Product Features
	2.3User Classes and Characteristics
	2.4Operating Environment
	2.5Design and Implementation Constraints
	2.6User Documentation
	2.7Assumptions 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
6.Other Requirements
                        
Document Text Contents
Page 1

Software Requirements
Specification

For

LIBRARY MANAGEMENT SYSTEM

Version 1.0 approved

Prepared by KAPIL B. PATIL

Sinhgad Academy of Engineering, Kondhwa Pune.

8TH JULY 2009

Page 2

Software Requirements Specification for library management system
Page ii

Table of Contents
1. Introduction................................................................................................................................1

1.1 Purpose ......................................................................................................................................... ....1
1.2 Document Conventions.................................................................................................... .................1
1.3 Intended Audience and Reading Suggestions............................................................................ ........2
1.4 Project Scope.......................................................................................................... ..........................3
1.5 References............................................................................................................................. ............4

2. Overall Description....................................................................................................................4
2.1 Product Perspective............................................................................................................ ...............4
2.2 Product Features.................................................................................................... ...........................5
2.3 User Classes and Characteristics..................................................................................................... ..6
2.4 Operating Environment............................................................................................................. ........6
2.5 Design and Implementation Constraints...................................................................... .....................6
2.6 User Documentation...................................................................................................... ...................6
2.7 Assumptions and Dependencies.................................................................................................... ....7

   7
 3. System Features ........................................................................................................................7
 3.1. Database – Storage ................................................................................................................7

 3.2. Functional Requirements...................................................................................... ..........................8
   3.2.1 Interface Requirements.............................................................................................................. ..8

 4.Non Functional Requirements..................................................................................................9
   4.1. User Interfaces.............................................................................................................................. .9
   4.4. Communications Interfaces................................................................................................ .........10

 5.Other Nonfunctional Requirements.......................................................................................10
 5.1Performance Requirements...................................................................................................11

 5.2Safety Requirements................................................................................................................... .....11
 5.3Security Requirements............................................................................................ ........................11
 5.4Hardware Constraints....................................................................................................... ...............11
 5.5  Software Constraints............................................................................................... ......................11
 5.6Design Constraints.......................................................................................................... ................12

 6.Other Requirements.................................................................................................................12

Revision History
Name Date Reason For Changes Version

Page 7

Software Requirements Specification for  library management system
Page 5

The University of Ballarat has various campuses distributed

across Australia. Further each branch is managed individually and locally

by that branch library staff. The System should reflect and support this

decentralized structure. A provision should further be allowed to add a

branch. The System will also have an ADMIN who has full-fledged rights

with regards to managing resources across branches – such as

transferring books across these branches. The users 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:

 Librarian who will be acting as the administrator

 Student 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 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

Page 8

Software Requirements Specification for  library management system
Page 6

 Can view the history of books issued to him previously

 Can search for a particular book

2.3User Classes and Characteristics

There are various kinds of users for the product. Usually web products
are visited by various users for different reasons.


The users include :


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

 Librarian who will be acting as the controller and he will have
all the privileges of an administrator.

2.4Operating 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.5Design and Implementation Constraints

he Product is developed using ASP. The backend database for this
SQL Server. The product is accomplished with login facility so that
specific function is available to specific student.



2.6User 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. The
product will be compatible with the Internet Explorer 6.0 or higher. The
databases will be created in the Microsoft SQL server 2000

Page 13

Software Requirements Specification for  library management system
Page 11

5.1Performance 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
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

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.,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 other than library staff only have
the rights to retrieve the information about database.
Software Quality Attributes
The Quality of the database is maintained in such a way so that it can be very
user friendly to all the users of the database

5.4Hardware Constraints

The system requires a database in order to store persistent 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 and development

tools.

The availability of these tools will be governed by

the University of Ballarat.

The most recent versions of software development tools may not be

installed at the University of Ballarat.

Similer Documents