Srs Library Mangement121

8/6/2019 Srs Library Mangement121

http://slidepdf.com/reader/full/srs-library-mangement121 1/14

1

CHAITANYA BHARATHI INSTITUTE OF

TECHNOLOGYGANDIPET, HYDERABAD – 500075

Software Requirements Specification

For

ONLINE LIBRARY MANAGEMNET

Prepared by

Roll no: 0209-8121 K.Venkatesh

Roll no:0209-8116 L.Subba Reddy

Roll no:0209-8117 G.Suresh Kumar

Roll no:0209-8118 V. Surya Rama Vamsi



2

Table of Contents

1) Introduction---------------------------------------------------------------------------3

1.1purpose------------------------------------------------------------------------3

1.2Scope--------------------------------------------------------------------------4

1.3Glossary-----------------------------------------------------------------------5

1.4Overview----------------------------------------------------------------------5

2) Overall Description------------------------------------------------------------------6

2.1 System Environment--------------------------------------------------------7

2.2. Functional Requirements Specification------------------------------7

2.2.1. Librarian------------------------------------------------------------7

2.2.2 Administrator------------------------------------------------------7

2.2.3 User------------------------------------------------------------------7

2.2.4 Member-------------------------------------------------------------7

2.3 User Characteristics---------------------------------------------------------8

3) Non- Functional Requirements----------------------------------------------------8

3.1 Security Features------------------------------------------------------------8

3.1.1 constraints---------------------------------------------------------8

3.1.2 Safety Requirements---------------------------------------------8

4. Diagrams for Library management------------------------------------------------9

4.1 Class Diagram---------------------------------------------------------------9

4.2 Sequence Diagrams--------------------------------------------------------10

4.3 Collaboration Diagrams--------------------------------------------------11



3

4.4 State Diagrams-------------------------------------------------------------12

4.5 Activity Diagrams---------------------------------------------------------13

4.6 Component Diagrams-----------------------------------------------------13

4.7 Deployment Diagrams ---------------------------------------------------14



4

Software Requirement Specifications

1. Introduction:

Borrowing books, returning books or viewing the available books at the Library of the local University is

currently done manually where in the student has to go to the Library and check the available books at theLibrary. Students check the list of books available and borrow the books if the book is a borrow book

otherwise it is of waste for the student to come to the library to come to check for the books if the student

doesn’t get the book. Then the librarian checks the student id and allows the member to check out the

book and the librarian then updates the member database and also the books database.

This system would be used by members who may be students or professors of that University to check the

availability of the books and borrow the books, and by the librarian 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 of Software Requirements Specification (SRS) document is to describe the external behavior

of the Online Library System. Requirements Specification defines and describes the operations,

interfaces, performance, and quality assurance requirements of the Online Library System. The document

also describes the nonfunctional 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.

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, 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 OnlineLibrary 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 libraryhours.

The system allows the members to block the books 24 hours a day and all the through thesemester.

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.



5

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

Term Definition

Librarian Person who is the administrator of the

system. He is the main actor of the system.

User Person who utilizes the services of a Online

Library.

Database Collection of all the information monitored

by the system.

Software Requirements Specification A document that completely describes all of

the functions of a specific system.

1.4 Overview:

SRS will include two Major sections:

1) Overall Description: This section of the SRS will provide the general factors that affect the

product and its requirements. It provides the background for those requirements. The items suchas product perspective, product function, user characteristics, constraints, assumptions anddependencies and requirements subsets are described in this section.

2) Requirement Specification: This section of SRS contains all the software requirements

mentioned in section 2 in detail sufficient enough to enable designers to design the system tosatisfy the requirements and testers to test if the system satisfies those requirements.



6

2)Overall Description:

2.1 System Environment:

addItem

addMember

craeteRoles

adminuser

search

member

issue

viewReport

accountInfo

return

calculateFine

librarian

Online users have four actors

1) Administrator

2) User

3) Librarian

4) Member

2.2. Functional Requirements Specification

This section outlines the use cases for each of the actors separately.



7

2.2.1. Librarian

Use case: issue books, account info, calculate fine, view report.

The role performed by librarian is

1) Librarian issues the book to the students

2) Later while the student returns the book, he checks the account of the student

3) Based on the last return date, he calculates the fine

4) Later he return the card, updates the database and views the report

2.2.2 Administrator

Use case: addItem, addMember, createRoles, search for user.

The role performed by Administrator is

1) He can add members to the library i.e user

2) he can create new roles in the library to manage the library

3) he also can search for user to make further verification

4) he can add new item to the library database

2.2.3 User

Use case: search

1) he can search for the book and get the book issued

2) later he returns the book based on the return date

2.2.4 Member

Use case: return, search

1) a member can search for the book

2) later he returns the book based on the return data

2.3. User Characteristics



8

A librarian can add, delete and update book status and search from the database. A user can borrow,

return books, reserve books and search for books. He can also renew his loan period. If a book is overdue,

the user will be fined $0.10 each day over the due. If a book is reported lost, the user will pay the full cost

of the book.

The library is a nation-wide library with several branches. When the users searches the books, the systemwill output which branches have the books, and which branch is the nearest to user's home address. The

search function allows both users and librarians to search by title, rating, category, author, publisher,

ISBN, language, branch, keywords. The system also allows browsing by the same parameters.

There is a feedback system where the users can give a rating and comments to the book after they

have returned it

3. Non Functional Requirements

3.1 Security Features:

Only the authorized members can access the database. This is done by giving a separate id to everyone

accessing the database.

3.1.1 Constraints:

1) The person whose name is on the id is responsible for all the books taken on it.

2) When the book is returned to the library, make sure that the database is updated.

3) Keep the id in secret, in order to avoid others misusing it.

4) If the books is not returned in time , the students will be fined.

5) When the last date is crossed, the fine database will automatically be updated.

3.1.2 Safety 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.

4. DIAGRAMS FOR LIBRARY MANAGEMENT

4.1 Class Diagram



9

S U P P L I E R

S - I D

S _ N A M E

S E A R C H ( )

T E L L A V A I L A B I L I T Y ( )

O P N A M E ( )

S T U D E N T

S _ n a m eS _ i d

S _ d e p a r t m e n t

b o r r o w b o o k ( )

r e t u r n b o o k ( )

D A T A B A S E

f i l e n a m e

u p d a t e ( )

d e l e t e ( )

l i b r a r i a n

l _ i d

l _ n a m el - d o j

i s s u e b o o k ( )

c h e c k i d ( )

g r a n t p e r m i s s i o n ( )

a d d b o o k ( )

1 . . * 1

1 . . *

4.2 Sequence Diagram



10

u s e r L M S

L i b r a r i a n D a t a B a s e

1 : a u th e n i c a te u s e r

2 : s u c c e s f u l lo g i n

3 : is s u e b o o k

4 : c h e c k f o r b o o k s t a tu s

5 : a v a i la b le o r w a i ti n g

6 : s u u c e s s f ully is s u e d

7 : r e tu rn b o o k

8 : c h e c k s ta tu s

9 : c a l c u la t e f i n e

1 0 : r e t u rn c a r d



11

4.3Collaboration Diagra

D a t a B a se

u s e r

L M S L i b r a r i a n

1 : a u t he n i c a t e u s e r

2 : s u c c e s f ul lo g i n

3 : i s s ue b o o k

4 : c h e c k f o r b o o k s t a tu s

5 : a v a i la b le o r w a i ti n g

6 : s u u c e s s f u lly i s s u e d

7 : re t u rn b o o k

8 : c h e c k s ta t u s

9 : c a l c u la t e f in e

1 0 : re t u r n c a rd



12

4.4 State Diagram

e n te r lo g i nn a m e

v e r i f y a u t h e n i ca te

i s s u eb o o k

c h e c k fo r

b o o k

r e t u r nb o o k

c a l u c u l a te fi n e

l o g u t



13

4.5 Activity Diagram

authenicate

check for book

issuebook

return

returncard

calculatefine

logout

available

late

in time pay fine

4.6 Component diagram

student

librarian

borrow book



14

4.7 Deployment Diagram

client program

web server

Srs Library Mangement121

Documents

Transcript of Srs Library Mangement121