Srs of Online Library Management

7/30/2019 Srs of Online Library Management

1/20

Online Library Management

Software Requirements Specification

1.0

31.1.2013

Aniruddha Banerjee -IT 45

Avrajit Bhattacharjee -IT 52

Snigdhodeb Mitra -IT 44

Projjwal Chowdhury -IT 54

Prasun Mukherjee -IT 42

Sheily Ghosh -IT 32

Prepared for

WBUT IT 693Software Engineering Lab


2/20

Online Library Management System

Document Approval

The following Software Requirements Specification has been accepted and approved by the

following:

Signature Printed Name Title Date

Software Requirements Specification Page ii


3/20


Table of Contents

DOCUMENT APPROVAL.........................................................................................................................................II

1. INTRODUCTION.....................................................................................................................................................1

1.1 PURPOSE............................................................................................................................................................... 1

1.2 SCOPE....................................................................................................................................................................1

1.3 DEFINITIONS, ACRONYMS, AND ABBREVIATIONS................................................................................................ 2

1.4 REFERENCES......................................................................................................................................................... 2

1.5 OVERVIEW............................................................................................................................................................ 3

2. GENERAL DESCRIPTION............... .............. .............. .............. ............... .............. .............. .............. .............. .... 3

2.1 PRODUCT PERSPECTIVE........................................................................................................................................ 3

2.2 PRODUCT FUNCTIONS........................................................................................................................................... 5

2.3 USER CHARACTERISTICS...................................................................................................................................... 5

2.4 GENERAL CONSTRAINTS.......................................................................................................................................5

2.5 ASSUMPTIONSAND DEPENDENCIES......................................................................................................................6

3. SPECIFIC REQUIREMENTS................ .............. .............. .............. .............. .............. ............... .............. ............. 6

3.1 EXTERNAL INTERFACE REQUIREMENTS............................................................................................................... 7

3.1.1 User Interfaces.............................................................................................................................................7

3.1.2 Hardware Interfaces................ .............. ............... .............. .............. .............. .............. .............. ............... .. 7

3.1.3 Software Interfaces............... .............. ............... .............. .............. .............. .............. .............. ............... ..... 7

3.2 FUNCTIONAL REQUIREMENTS...............................................................................................................................7

3.2.1 .............. .............. .............. .............. .............. ............... ............. 7

The User can change their details in case of wrong information entered............................................................8

3.2.2 Functional Requirement or Feature ............. .............. .............. ............... .............. .............. .............. .........8

3.3 MAIN USE CASE................................................................................................................................................. 8

3.3.1 Sub Use Cases..............................................................................................................................................9

3.4 CLASSES .............................................................................................................................................................14

3.4.1 Books..........................................................................................................................................................143.5 NON-FUNCTIONAL REQUIREMENTS....................................................................................................................15

3.5.1 Performance...............................................................................................................................................15

3.5.2 Reliability......... .............. .............. .............. .............. ............... .............. .............. .............. .............. ........... 16

3.5.3 Availability......... .............. .............. ............... .............. .............. .............. .............. .............. ............... ........ 16

3.5.4 Security.......................................................................................................................................................16

3.5.5 Maintainability...........................................................................................................................................16

3.5.6 Portability.......... .............. .............. .............. .............. ............... .............. .............. .............. .............. ......... 16

3.7 DESIGN CONSTRAINTS............. .............. ............... .............. .............. .............. .............. ............... .............. ......... 16

3.8 LOGICAL DATABASE REQUIREMENTS.................................................................................................................16

3.9 OTHER REQUIREMENTS...................................................................................................................................... 16

4. ANALYSIS MODELS.................. .............. .............. .............. ............... .............. .............. .............. .............. ......... 17

4.1 SEQUENCE DIAGRAMS........................................................................................................................................ 17

4.3 DATA FLOW DIAGRAMS (DFD)..........................................................................................................................17

A. APPENDICES.............. .............. .............. .............. .............. ............... .............. .............. .............. .............. ........... 17

A.1 APPENDIX 1........................................................................................................................................................17

,

Software Requirements Specification Page iii


4/20


1. Introduction

Borrowing books, returning books or viewing the available books at the library of

the local Library & other libraries is currently done manually where in the User has

to go to the library and check the available books at the library. Users check the listof books available and borrow the books if the book is a borrow book otherwise it

is of waste for the User to come to the library to come to check for the books if the

User doesnt get the book. Then the librarian checks the User id and allows the

member to check out the book and the librarian then updates the member database

and also the books database. This takes at least one to two hours if the member is

available at the nearby place otherwise it may take more time.

We have decided to investigate the use of an online library management system.

This system would be used by members who may be Users or professors of that

Library to check the availability of the books and borrow the books, and by thelibrarian to update the databases. The purpose of this document is to analyze and

elaborate on the high-level needs and features of the online library system. It

focuses on the capabilities and facilities provided by a library. The details of what

all are the needs of the online library system and if it fulfils these needs are

detailed in the use-case and supplementary specifications.

1.1 Purpose

The purpose ofSoftware Requirements Specification (SRS) document is to

describe the external Behaviour of the Online Library System. RequirementsSpecification defines and describes the Operations, interfaces, performance, and

quality assurance requirements of the Online Library System. The document also

describes the non functional requirements such as the user interfaces. It also

Describes the design constraints that are to be considered when the system is to be

designed, and other Factors necessary to provide a complete and comprehensive

description of the requirements for the Software. The Software Requirements

Specification (SRS) captures the complete software Requirements for the system,

or a portion of the system. Requirements described in this document are Derived

from the Vision Document prepared for the Online Library System.

1.2 Scope

The Software Requirements Specification captures all the requirements in a single

document. The Online Library System that is to be developed provides the

members of the Library and employees of The library with books information,

Software Requirements Specification Page 1


5/20


online blocking of books and many other facilities. The Online Library System is

supposed to have the following features.

The product provides the members with online blocking of books capabilities and

the Online Library System is up and running all day.

The system provides logon facility to the users.

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.

The features that are described in this document are used in the future phases of the

software Development cycle. The features described here meet the needs of all the

users. The success criteria of The system are based in the level up to which the

features described in this document are implemented In the system.

1.3 Definitions, Acronyms, and Abbreviations

This subsection should provide the definitions of all terms, acronyms, and abbreviations

required to properly interpret the SRS. This information may be provided by reference to one or

more appendixes in the SRS or by reference to other documents.

1.4 References

This subsection should:(1) Provide a complete list of all documents referenced elsewhere in the SRS, or in a separate,

specified document.

(2) Identify each document by title, report number - if applicable - date, and publishing

organization.

(3) Specify the sources from which the references can be obtained.

This information may be provided by reference to an appendix or to another document.



6/20


1.5 Overview

The SRS will provide a detailed description of the Online Library System. This

document will provide the outline of the requirements, overview of the

characteristics and constraints of the system.

2. General Description

This section of the SRS should describe the general factors that affect 'the product and its

requirements. It should be made clear that this section does not state specific requirements; it

only makes those requirements easier to understand.

2.1 Product Perspective

The Online Library System is a package 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 Universities andLibrarian of Schools. 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

(Users 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 Users and Teachers of Schools & Colleges.



7/20


Overview of the proposed Online Library Management system



8/20


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 Product functions are moreor less the same as described in the product perspective. The functions of the

system include the system providing different type of services based on the type of

users [User/Librarian/Staff].

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 can get the information about the members who have borrowed or

returned the books.

The librarian is provided with interfaces to add/delete the books available in the

book catalog.

The members when complete the book borrowing or returning process, the due to

be paid by the member must be calculated and the information about the member

and the due amount is sent to the Library billing system.

The system uses the Library information security requirements to provide thelogin facility to the users.

2.3 User Characteristics

The users of the system are members, librarian of the Library 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,users 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 General Constraints

The information of all the users must be stored in a database that is accessible by

the Online Library System.



9/20


The Library information security system must be compatible with the Internet

applications.

The Online Library System is connected to the Library computer and is running

all 24 hours a day.

The users access the Online Library System from any computer that has Internet

browsing capabilities and an Internet connection.

The billing system is connected to the Online Library System and the database

used by the billing system must be compatible with the interface of the Online

Library System.

The users must have their correct usernames and passwords to enter into the

Online Library System.

2.5 Assumptions and Dependencies

The users have sufficient knowledge of computers.

The Library computer should have Internet connection and Internet servercapabilities.

The users know the English language, as the user interface will be provided in

English.

The product can access the Library User database.

3. Specific Requirements

This will be the largest and most important section of the SRS. The customer

requirements will be embodied within Section 2, but this section will give the D-

requirements that are used to guide the projects software design, implementation, andtesting.

Each requirement in this section should be:

Correct

Traceable (both forward and backward to prior/future artifacts)

Unambiguous

Verifiable (i.e., testable)

Prioritized (with respect to importance and/or stability)

Complete

Consistent

Uniquely identifiable (usually via numbering like 3.4.5.6)

Attention should be paid to the carefully organize the requirements presented in this

section so that they may easily accessed and understood. Furthermore, this SRS is not



10/20


the software design document, therefore one should avoid the tendency to over-constrain

(and therefore design) the software project within this SRS.

3.1 External Interface Requirements

This section deals with the software and hardware requirements for user and theserver side.

3.1.1 User Interfaces

Windows 98,xp,vista,7,8 , Linux or Unix operating system

Web Browser Chrome, Firefox, Internet Explorer, Oprea , etc.

Java Runtime Environment

3.1.2 Hardware Interfaces

Intel Celeron and higher processor

Minimum 512MB RAM

3.1.3 Software Interfaces

Eclipse Galileo or above.

Firefox or Chrome

MySQL Server 5.1

JBoss 4.2.1 GA

3.2 Functional RequirementsThis section describes specific features of the software project. If desired, some

requirements may be specified in the use-case format and listed in the Use Cases Section.

3.2.1

3.2.1.1 Introduction

The main players in this software are library users and the librarian. The users act

by borrowing book and the librarian act as the administrator which maintains the

library.

3.2.1.2 Inputs

Librarian:- The librarian inputs the Book details for a new book to be entered.

User:- The user inputs their own details for registering.



11/20


3.2.1.3 Processing

The librarian processes on Book request, new user registration request , updation

of book details.

3.2.1.4 Outputs

The user gets to see the Books that are present in the Library and their details.

They can also see their Book transactions over the past.

The Librarian gets to see all the books in library and the details of users registered

in library system.

3.2.1.5 Error Handling

The User can change their details in case of wrong information entered.

The Librarian can change the details of books in case of wrong details.

3.2.2 Functional Requirement or Feature

3.3 Main Use Case



12/20


3.3.1 Sub Use Cases

Register



13/20


Log in

#3



14/20


#4

#5



15/20


#6

#7



16/20


#8



17/20


3.4 Classes

3.4.1 Books

3.4.1.1Attributes

1.Bookid

2.Book name

3.Book author

4.Type

5.Description

3.4.1.2 Functions

UpdateBook Details()

DisplayBook Details()

SearchBook()

AddnewBooks()

3.4.2 Librarian

3.4.2.1 Attributes

Username

Name



18/20


Password

Contact

EmailId

3.4.2.2 Functions

Grantbook()

ReturnBooks()

Enternewbooks()

verifyMember()

UpdateIssue()

3.4.3 User

3.4.3.1 Attributes

3.4.3.2 Functions

3.5 Non-Functional Requirements

Non-functional requirements may exist for the following attributes. Often these requirements

must be achieved at a system-wide level rather than at a unit level. State the requirements in the

following sections in measurable terms (e.g., 95% of transaction shall be processed in less than

a second, system downtime may not exceed 1 minute per day, > 30 day MTBF value, etc).

3.5.1 Performance3.5.1.1Response time

Information regarding any 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. Administrators/librarians response the system shall take as less

time as possible to provide service to the administrator or the librarian.

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



19/20


3.5.1.3 Capacity

The system is capable of handling 250 users at a time.

3.5.2 Reliability

The system has to be very reliable due to the importance of data and thedamages incorrect or incomplete data can do.

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

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

3.5.2.3 Access Reliability

The system shall provide 100% access reliability.

3.5.3 Availability

3.5.4 Security

3.5.5 Maintainability

3.5.6 Portability

3.7 Design Constraints

Specify design constrains imposed by other standards, company policies, hardware limitation,

etc. that will impact this software project.

3.8 Logical Database Requirements

Will a database be used? If so, what logical requirements exist for data formats, storage

capabilities, data retention, data integrity, etc.

3.9 Other Requirements

Catch all section for any additional requirements.



20/20


4. Analysis Models

List all analysis models used in developing specific requirements previously given in this SRS.

Each model should include an introduction and a narrative description. Furthermore, each

model should be traceable the SRSs requirements.

4.1 Sequence Diagrams

4.3 Data Flow Diagrams (DFD)

A. Appendices

Appendices may be used to provide additional (and hopefully helpful) information. If present,

the SRS should explicitly state whether the information contained within an appendix is to be

considered as a part of the SRSs overall set of requirements.

Example Appendices could include (initial) conceptual documents for the software project,marketing materials, minutes of meetings with the customer(s), etc.

A.1 Appendix 1


Documents

Srs of Online Library Management