my final srs

8/8/2019 My Final SRS

1/46


2/46

SoftwareRequirements Specification for Online Library Management System Page ii

Table of Contents

1. Introduction................................................................................................................................31.1 Purpose ............................................................................................................................................... 31.2 Project Scope....................................................................................................................................... 31.3 Abbreviations:..................................................................................................................................... 3

1.4 References:.......................................................................................................................................... 41.5 Technologies:...................................................................................................................................... 41.6 Overview:............................................................................................................................................ 4

2. Overall Description....................................................................................................................42.1 Product Perspective:............................................................................................................................ 42.2 Software Interface:.............................................................................................................................. 52.3 Hardware Interface: ............................................................................................................................ 52.4 Communication Interface:................................................................................................................... 62.5 Product Function:................................................................................................................................ 62.6 User Characteristics:........................................................................................................................... 62.7 Constraints:......................................................................................................................................... 62.8 Use-Case Model Survey:..................................................................................................................... 72.9 Architecture Diagram:......................................................................................................................... 92.10 Database Design:............................................................................................................................. 11

2.11 Assumptions and Dependencies:..................................................................................................... 123. Specific Requirements:............................................................................................................12

3.1 Use-Case Reports:............................................................................................................................. 12


3/46

SoftwareRequirements Specification for Online Library Management System Page 3

1. Introduction

1.1 Purpose

This project is an Intranet application that can be accessed throughout the campus. This system

can be used to search for books/magazines, reserve books, find out who is having a particularbook, put in requests to buy a new book etc. This is one integrated system that contains both the

user component and the librarian component.

1.2 Project Scope

Internet Library is website used to provide information regarding the books in a library to

the user.

It can be accessed by unlimited number of users.

Each user will be assigned a different set of permissions for each module of the library

including basic searching, permissions, advance booking etc.

The user can make of use his required books up to the time limit extended to him.

At the cross of his time limit he may face the fine.

Fine collection is under the control of administration.

The administrator has to generate daily/weekly/Monthly reports, which include the details of

books, issued, returned collection of fine etc.

1.3 Abbreviations:

HTML: Hypertext Markup Language is a markup language used to design static web

pages.

EJB: Enterprise Java Beans.

J2EE: Java 2 Enterprise Edition is a programming platform part of the Java Platform

for developing and running distributed multitier architecture Java applications, basedlargely on modular software components running on an application server.

DB2: DB2 Database is the database management system that delivers a flexible and cost

effective database platform to build robust on demand business applications.

WAS: Web Sphere Application server is an application server that runs business

applications and supports the J2EE and web services standards.

WSAD: Web Sphere Studio Application developer is a toolkit which is designed for the

creation of more complex projects, providing fully dynamic web application utilizingEJBs . This consist of EJB tools , CMP ,data mapping tools & a universal test client that

is designed to aid testing of EJBs.


4/46


HTTP: Hypertext Transfer Protocol is a transaction oriented client/server protocol

between web browser & a Web Server.

HTTPS: Secure Hypertext Transfer Protocol is a HTTP over SSL (secure socket layer).

TCP/IP: Transmission Control Protocol/Internet Protocol, the suite of communication

protocols used to connect hosts on the Internet. TCP/IP uses several protocols, the

two main ones being TCP and IP.

1.4 References:

IEEE SRS Format

Problem Definition (Provided by IBM)

CT Arrington. Enterprise Java with UML. OMG Press.

1.5 Technologies:

J2EE: Application Architecture

DB2: Database

WSAD: Development Tool

WAS: Web Server

Rational Rose: Design Tool

1.6 Overview:

Overall Description will describe major components of the system, interconnection andexternal interfaces.

Specific Requirements will describe the functions of actors, their role in the system and

constraints.

2. Overall Description

2.1 Product Perspective:


5/46


The web pages (XHTML/JSP) are present to provide the user interface on customer clientside. Communication between customer and server is provided through HTTP/HTTPS

protocols.

On the server side web server is for EJB and database server is for storing theinformation.

2.2 Software Interface:

Client on Internet: Web Browser, Operating System (any)

Client on Intranet: Client Software, Web Browser, Operating System (any)

Web Server: WAS, Operating System (any)

Data Base Server: DB2, Operating System (any)

Development End: WSAD (J2EE, Java, Java Bean, Servlets, HTML),

DB2, OS (Windows), Web Server.

2.3 Hardware Interface:

HTTP/HTTPS

Web

Client

WASDB2

HTML

Client

(Customer)

Web Server


6/46


2.4 Communication Interface:

Client on Internet will be using HTTP/HTTPS protocol.

Client on Intranet will be using TCP/IP protocol.

2.5 Product Function:

2.6 User Characteristics:

Every user should be comfortable of working with computer and net browsing. He

must have basic knowledge of English too.

2.7 Constraints:

GUI is only in English.

Login and password is used for identification of customer (Student/Faculty/Admin)

and there is no facility for guest. This system is working for single server.

There is no maintainability of back up. So availability will get affected.

Limited to HTTP/HTTPS.

It is an Intranet application and is limited to use within the campus.


7/46


2.8 Use-Case Model Survey:


8/46


I) Administrator: Responsible for managing system users, viewing report and managing issues,

and renewals of books/journals.

o Manage Members: The Administrator will create different members. The members will

be created and will be assigned with the different roles.

o View Reports: Responsible for checking the reports of different system user for

managing the system.o Managing Books: The administrator can add the books and delete accordingly.

o Managing Issues and Renewals: The administrator can issue and renew the book(s).

II) Student: Does registration, searching of books required, requesting of books, returning of

books taken, payment of fine on a book(s) and reserving of books.

o Registration: Registration is needed in order to login to the system. Hence after

registration he would be able to login to the system and use it as per the privileges he had.

o Search Books: Responsible for showing the status of books which are requested.

o Request Books: Responsible for issuing the books as desired by the member taking into

account the constraint of number of books to be issued.

o Return Books: Takes back the books as issued previously and collect fine (if any) inaccordance with the date of return.

o Reserve Books: Takes care of reserving a book(s) as requested by the member taking

into consideration the constraint of number of books to be issued to a particular memberas per the role he/she plays.

III) Faculty: Does registration, searching of books required, requesting of books, returning of


o Registration: Registration is needed in order to login to the system. Hence after


o Search Books: Responsible for showing the status of books which are requested.

o Request Books: Responsible for issuing the books as desired by the member taking into


o Return Books: Takes back the books as issued previously and collect fine (if any) in

accordance with the date of return.

o Reserve Books: Takes care of reserving a book(s) as requested by the member taking

into consideration the constraint of number of books to be issued to a particular memberas per the role he/she plays.


9/46


2.9 Architecture Diagram:

Application Layer Business Layer Data Layer

tbl_usermasterRegistration Valid

Registration

tbl_login

Login Valid User tbl_loginMastrer

Search

BooksSearchable

tbl_bookMaster

RequestBooks

BookAvailability

tbl_request

Return

Books

Fine tbl_bookMaster

tbl_Issues

tbl_mails


10/46


Reserve Books Existing Book tbl_reservation

tbl_bookMaster

tbl_bookMasterReports Type of Report

tbl_userMaster

Manage Valid Usertbl_bookMastrer

Manage

MembersValid User

tbl_UserMaster

Manage

Issues/

Renewal

Valid Usertbl_bookMaste

r

tbl_trans


11/46


2.10 Database Design:


12/46


2.11 Assumptions and Dependencies:

Since it is an intranet application and assuming that the authors and publishers are

not within the same college only two users are there viz; students and faculty.

Administrator is created in the system already.

Roles and tasks are predefined.

3. Specific Requirements:

3.1 Use-Case Reports:

I) Administrator: Responsible for managing system users, viewing report and managing issues,

and renewals of books/journals.

Manage Members: The Administrator will create different members. The members willbe created and will be assigned with the different roles.

View Reports: Responsible for checking the reports of different system user formanaging the system.

Managing Books: The administrator can add the books and delete accordingly.

Managing Issues and Renewals: The administrator can issue and renew the book(s).

Manage Members:

ModifyMember

DeleteMember

AddMember

ManageMembers


13/46


Name of use case: Managing Members

Description: Addition and deletion of members.

Preconditions:

Administrator is already logged in.

Members have already been created and assigned some roles, tasks andpermissions.

Normal flow of events:

The system user or a role will be selected.

Query will be submitted.

Relevant output will be displayed

Alternate flow of events:None.

Post Condition:None.

Is the user

Admin

Re-enter the username

and passwordFalse

Ask for system user to enter

Username and Password

He can modify

the members

True

Name of use case: Adding MembersDescription: Addition of members.

Preconditions:


Get into manage members task.



Manage Members task will be selected.


14/46






Is the user

Admin


and password False



He can add

members

True

Name of use case: Modify Member

Description: Modification of members.Preconditions:


Members have already been created and assigned some roles, tasks and

permissions.

Get into manage members task.






Alternate flow of events:None.Post Condition:None.


15/46


Is the user

Admin


and passwordFalse



He can modify

details of members

True

Name of use case: Delete Member

Description: Deletion of members.

Preconditions:


Members have already been created and assigned some roles, tasks and

permissions. Get into manage members task.









16/46


Is the user

Admin


and passwordFalse



He can delete

members

True

View Reports:

ListOfAuthors

ListOfPublishers

AvailableBooks

ListOfTransactions

Reports

Name of use case: View Reports

Description: Maintaining a log of transactions, look at the list of books available,authors, and publishers.

Preconditions:


17/46



Members have already been created and assigned some role.


The relevant operation will be selected.


Relevant output will be displayedAlternate flow of events:None.


Is the user

Admin


and passwordFalse



He can Viewthe reports

True

Name of use case: Available Books

Description: Displays the total number of books available.

Preconditions:



View Reports should be selected.



View Reports task is selected.






18/46


Is the user

Admin


and passwordFalse



He can view reports

on available books

True

Name of use case: List of authors.

Description: Displays the total authors of books available.

Preconditions:



View Reports should be selected.Normal flow of events:








19/46


Is the user

Admin


and passwordFalse



He can view reports

on list of authors

True

Name of use case: List Of publishers.

Description: Displays the total number of publishers of books available.

Preconditions:



View Reports should be selected.









20/46


Is the user

Admin


and passwordFalse



He can view reports

on list of publishers

True

Name of use case: List of Transactions.

Description: Displays the total number transactions done.

Preconditions:



View Reports should be selected.Normal flow of events:








21/46


Is the user

Admin


and passwordFalse



He can view reports

on list of transactions

True

Manage Books:

ModifyBookDetails

DeleteBook

AddBook

ManageBooks

Name of use case: Manage Books

Description: Managing addition, modification and deletion of books.Preconditions:








22/46




Is the user

Admin


and passwordFalse



He can Manage

the Books

True

Name of use case: Add Book.

Description: Adding a Book to the existing list.

Preconditions:



Get into Manage Books.







Name of use case: Modify Book Details.

Description: Modify the details of the existing book.

Preconditions:





23/46








Name of use case: Delete Book.

Description: Deleting a Book from the existing list.

Preconditions:










Manage Issues/Renewals:

RenewBook

IssueBook

ManageIssues/Renewals

Name of use case: Manage Issues/Renewals.

Description: Managing issues and renewals of the books.

Preconditions:










24/46


Is the user

Admin


and passwordFalse



He can Manage the

Issues/Renewals

True

Name of use case: Issue book.

Description: Managing issues regarding book issuing of books.

Preconditions:



Get into Manage Issues/ Renewal.Normal flow of events:






Name of use case: Issue book.

Description: Renew the due date on which the book has to be submitted to avoid fine.

Preconditions:



Get into Manage Issues/ Renewal.






25/46


26/46


Search Books:

ByAuthor

ByPublisher

ByName

Search

Name of use case: Search Books

Description: Searching for the books.

Preconditions:

Logging into the system.





Relevant output will be displayed.

Alternate flow of events:None.Pre Condition: User has to be logged into the system.



27/46


Is the user

registered Student


and passwordFalse



He can search

for books

True

Name of use case: By Name.

Description: Searching for the books as per the name.

Preconditions:



Normal flow of events: The relevant operation will be selected.




Pre Condition: User has to be logged into the system.

Post Condition:None


28/46


Is the user

registered Student


and passwordFalse



He can search for

books by name

True

Name of use case: By Author.

Description: Searching for the books as per the author.

Preconditions:








Post Condition:None


29/46


Is the user

registered Student


and passwordFalse



He can search for

books by Author

True

Name of use case: By Publisher

Description: Searching for the books as per the publisher.

Preconditions:








Post Condition:None


30/46


Is the user

registered Student


and passwordFalse



He can search for

books by Publisher

True

Request Books:

RequestBooks

Name of use case: Request Books.

Description: Send a request to the administrator in order to purchase new books.

Preconditions: The user has to be logged into the system.






Post Condition:None


31/46


Is the user

registered Student


and passwordFalse



He can request for

books

True

Reserve Book:

ReserveBooks

Name of use case: Reserve Book.

Description: Send a request to the administrator to reserve a book in advance.







Post Condition:None


32/46


Is the user

registered Student


and passwordFalse



He can reserve

books

True

Name of use case: Cancelling a Reserved Book.

Description: Send a request to the administrator to cancel a reserved book.

Preconditions:

The user has to be logged into the system.

Book reservation has to be selected.

Book has to be reserved earlier.Normal flow of events:





Post Condition:None


33/46


Is the user

registered Student


and passwordFalse



He can cancel

reserved book(s)

True

Book Return:

ReturnBooks Fine

Name of use case: Book Return.

Description: Returning to book(s) taken earlier.

Preconditions:

The book has to be taken by the student earlier.





Alternate flow of events:None.Post Condition:None


34/46


Is the user

registered Student


and passwordFalse



He can return

books

True

Name of use case: Fine.

Description: Paying for the delay of the book return.

Preconditions:

The student should take the book earlier.






Post Condition:None


35/46


Is the user

registered Student


and passwordFalse



He can return

books

True

Is the book returned on

or before the due date

True

Pay Fine

False

II) Faculty: Does registration, searching of books required, requesting of books, returning of


Registration: Registration is needed in order to login to the system. Hence after


Search Books: Responsible for showing the status of books which are requested.

Request Books: Responsible for issuing the books as desired by the member taking into


Return Books: Takes back the books as issued previously and collect fine (if any) inaccordance with the date of return.

Reserve Books: Takes care of reserving a book(s) as requested by the member takinginto consideration the constraint of number of books to be issued to a particular member

as per the role he/she plays.


36/46


Registration:

Registration

Name of use case: Registration.

Description: Register in order to login to the system.

Preconditions:None






Post Condition:None

Search Books:

ByAuthor

ByPublisher

ByName

Search

Name of use case: Search Books

Description: Searching for the books.

Preconditions:










37/46


Is the user

registered Faculty


and passwordFalse



He can search

for books

True

Name of use case: By Name.

Description: Searching for the books as per the name.

Preconditions:








Post Condition:None


38/46


Is the user

registered Faculty


and passwordFalse



He can search for

books by name

True

Name of use case: By Author.

Description: Searching for the books as per the author.

Preconditions:








Post Condition:None


39/46


Is the user

registered Faculty


and passwordFalse



He can search for

books by author

True

Name of use case: By Publisher

Description: Searching for the books as per the publisher.

Preconditions:








Post Condition:None


40/46


Is the user

registered Faculty


and password

False



He can search for

books by publisher

True

Request Books:

RequestBooks

Name of use case: Request Books.

Description: Send a request to the administrator in order to purchase new books.







Post Condition:None


41/46


Is the user

registered Faculty


and password

False



He can request for

books

True

Reserve Book:

ReserveBooks

Name of use case: Reserve Book.

Description: Send a request to the administrator to reserve a book in advance.







Post Condition:None


42/46


Is the user

registered Faculty


and password

False



He can reserve

books

True

Name of use case: Cancelling a Reserved Book.

Description: Send a request to the administrator to cancel a reserved book.

Preconditions:

The user has to be logged into the system.

Book reservation has to be selected.

Book has to be reserved earlier.Normal flow of events:





Post Condition:None


43/46


Is the user

registered Faculty


and password

False



He can cancel a

reserved book

True

Book Return:

ReturnBooks Fine

Name of use case: Book Return.

Description: Returning to book(s) taken earlier.

Preconditions:

The book has to be taken by the Faculty earlier.






Post Condition:None


44/46


Is the user

registered Faculty


and password

False



He can return a

book

True

Name of use case: Fine.

Description: Paying for the delay of the book return.

Preconditions:

The Faculty should take the book earlier.






Post Condition:None


45/46


Is the user

registered Faculty


and passwordFalse



He can return

books

True

Is the book returned on

or before the due date

True

Pay Fine

False

3.2) Supplementary Requirements:

? Have hours of operation that are 24 x 7 - Because system can be an automated process, so itcan stay open for 24 hours a day. If the base is now the entire world, staying open 24 hours a day

becomes critical. System is required to be available 24X7 so UPS support must be on server site

for at least 8 hours in case of power failure. System will remain inaccessible to users at 2:00 to4:00 am for backup and maintenance purpose.

? Make the existing Web site more dynamic in nature - Many early Web implementations

consisted of static HTML pages. This becomes very difficult to manage if the number of pagesgets too large. An effective system should be largely dynamic taking advantage of technology

that automates this process rather than relying on manual processes. Application should serve

dynamic user based customized web pages to its clients from server.? Tie the existing Web site into existing enterprise systems Any existing Web site that relies

on the manual duplication of data from another system is one that can be improved. Most of the


46/46


business data in the world today exists in enterprise servers that can be connected to the Web

servers to make this process far more effective.

? Provide good performance and the ability to scale the server The Web Application Servershould provide good performance and the ability to manage performance with techniques, such

as support for caching, clustering, and load balancing.

? Providing session management capability - Web application developers should not spendvaluable time worrying about how to maintain sessions within the application. The Web

Application Server should provide these services.

my final srs

Documents