Software Requirements Specification: Dwellers

Software Requirements Specification
For
Online Library Management System
Team
Dwellers
Team Members
H.Avinash, D.Raghavendra
M.Charan Teja, M.Sri Harsha Reddy
III/IV B.Tech, I SEM, CSE, SNIST
21/10/2009
Project Guide
Mr. N.V.Subba Reddy
M.Tech
Assoc.Professor,
CSE Dept., SNIST
Software Requirements Specification for Online Library Management System Page ii
Table of Contents
1. Introduction................................................................................................................................3
1.1 Purpose ............................................................................................................................................... 3
1.2 Project Scope....................................................................................................................................... 3
1.3 Abbreviations:..................................................................................................................................... 3
1.4 References:.......................................................................................................................................... 4
1.5 Technologies:...................................................................................................................................... 4
1.6 Overview:............................................................................................................................................ 4
2. Overall Description....................................................................................................................4
2.1 Product Perspective:............................................................................................................................ 4
2.2 Software Interface:.............................................................................................................................. 5
2.3 Hardware Interface: ............................................................................................................................ 5
2.4 Communication Interface:................................................................................................................... 6
2.5 Product Function:................................................................................................................................ 6
2.6 User Characteristics:........................................................................................................................... 6
2.7 Constraints:......................................................................................................................................... 6
2.8 Use-Case Model Survey:..................................................................................................................... 7
2.9 Architecture Diagram:......................................................................................................................... 9
2.10 Database Design:............................................................................................................................. 11
2.11 Assumptions and Dependencies:..................................................................................................... 12
3. Specific Requirements:............................................................................................................12
3.1 Use-Case Reports:............................................................................................................................. 12
Software Requirements 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 particular
book, 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, based
largely 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 utilizing
EJB’s . This consist of EJB tools , CMP ,data mapping tools & a universal test client that
is designed to aid testing of EJB’s.
• 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 and
external interfaces.
 Specific Requirements will describe the functions of actors, their role in the system and
constraints.
2. Overall Description
2.1 Product Perspective:

Web Server
HTTP/HTTPS
Web WAS DB2

Client
HTML
Client
(Customer)
 The web pages (XHTML/JSP) are present to provide the user interface on customer client
side. 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 the
information.
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:

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.
2.8 Use-Case Model Survey:

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) 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 member
as 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
o Reserve Books: Takes care of reserving a book(s) as requested by the member taking
2.9 Architecture Diagram:
Application Layer Business Layer Data Layer
tbl_usermaster
Registration Valid
Registration
tbl_login
Login Valid User

tbl_loginMastrer
Search Searchable
tbl_bookMaster
Books
Request Book tbl_request

Books Availability
tbl_mails
Return Fine tbl_bookMaster

Books
tbl_Issue
s
tbl_reservation
Reserve Books Existing Book
tbl_bookMaster
tbl_bookMaster
Reports Type of Report
tbl_userMaster
Manage Valid User

tbl_bookMastrer
Books
Manage Valid User

tbl_UserMaster
Members
tbl_bookMaste
Manage Valid User r
Issues/
Renewal
tbl_trans
2.10 Database Design:

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 will
be created and will be assigned with the different roles.
 View Reports: Responsible for checking the reports of different system user for
managing 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:
AddMember
ManageMembers ModifyMember
DeleteMember
 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 and
permissions.
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.
Ask for system user to enter

Username and Password
Re-enter the username Is the user

and password Admin
False
True
He can modify
the members
 Name of use case: Adding Members

Description: Addition of members.
Preconditions:
• Get into manage members task.
• Manage Members task will be selected.



and password Admin
False
True
He can add
members
 Name of use case: Modify Member

Description: Modification of members.
Preconditions:
permissions.


and password Admin
False
True
He can modify
details of members
 Name of use case: Delete Member

Description: Deletion of members.
Preconditions:
permissions.


and password Admin
False
True
He can delete
members
• View Reports:
AvailableBooks
ListOfAuthors
Reports
ListOfPublishers
ListOfTransactions
 Name of use case: View Reports

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

• Members have already been created and assigned some role.
• The relevant operation will be selected.


and password Admin
False
True
He can View
the reports
 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.


and password Admin
False
True
He can view reports

on available books
 Name of use case: List of authors.

Description: Displays the total authors of books available.
Preconditions:


and password Admin
False
True
He can view reports

on list of authors
 Name of use case: List Of publishers.

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


and password Admin
False
True
He can view reports

on list of publishers
 Name of use case: List of Transactions.

Description: Displays the total number transactions done.
Preconditions:


and password Admin
False
True
He can view reports

on list of transactions
• Manage Books:
AddBook
ManageBooks ModifyBookDetails
DeleteBook
 Name of use case: Manage Books

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



and password Admin
False
True
He can Manage
the Books
 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:

 Name of use case: Delete Book.

Description: Deleting a Book from the existing list.
Preconditions:
• Manage Issues/Renewals:
IssueBook
ManageIssues/Renewals
RenewBook
 Name of use case: Manage Issues/Renewals.

Description: Managing issues and renewals of the books.
Preconditions:


and password Admin
False
True
He can Manage the

Issues/Renewals
 Name of use case: Issue book.

Description: Managing issues regarding book issuing of books.
Preconditions:
• Get into Manage Issues/ Renewal.
 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.

II) Student: 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) in
 Reserve Books: Takes care of reserving a book(s) as requested by the member taking
• Registration:
Registration
 Name of use case: Registration.

Description: Register in order to login to the system.
Preconditions: None
Post Condition: None
• Search Books:
ByName
Search ByAuthor
ByPublisher
 Name of use case: Search Books

Description: Searching for the books.
Preconditions:
• Logging into the system.
• Relevant output will be displayed.
Pre Condition: User has to be logged into the system.


and password registered Student
False
True
He can search
for books
 Name of use case: By Name.

Description: Searching for the books as per the name.
Preconditions:


False
True
He can search for

books by name
 Name of use case: By Author.

Description: Searching for the books as per the author.
Preconditions:


False
True
He can search for

books by Author
 Name of use case: By Publisher

Description: Searching for the books as per the publisher.
Preconditions:


False
True
He can search for

books by Publisher
• 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.


False
True
He can request for

books
• Reserve Book:
ReserveBooks
 Name of use case: Reserve Book.

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


False
True
He can reserve
books
 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.


False
True
He can cancel
reserved book(s)
• 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.


False
True
He can return
books
 Name of use case: Fine.

Description: Paying for the delay of the book return.
Preconditions:
• The student should take the book earlier.


False
True
He can return
books
True
Is the book returned on
or before the due date
False
Pay Fine
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) in
 Reserve Books: Takes care of reserving a book(s) as requested by the member taking
• Registration:
Registration
 Name of use case: Registration.

Description: Register in order to login to the system.
Preconditions: None
• Search Books:
ByName
Search ByAuthor
ByPublisher
 Name of use case: Search Books

Description: Searching for the books.
Preconditions:


and password registered Faculty
False
True
He can search
for books
 Name of use case: By Name.

Description: Searching for the books as per the name.
Preconditions:


False
True
He can search for

books by name
 Name of use case: By Author.

Description: Searching for the books as per the author.
Preconditions:


False
True
He can search for

books by author
 Name of use case: By Publisher

Description: Searching for the books as per the publisher.
Preconditions:

Re-enter the username False Is the user

True
He can search for

books by publisher
• Request Books:
RequestBooks
 Name of use case: Request Books.

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


True
He can request for

books
• Reserve Book:
ReserveBooks
 Name of use case: Reserve Book.

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


True
He can reserve
books
 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.


True
He can cancel a
reserved book
• 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.


True
He can return a
book
 Name of use case: Fine.

Description: Paying for the delay of the book return.
Preconditions:
• The Faculty should take the book earlier.


False
True
He can return
books
True
Is the book returned on
or before the due date
False
Pay Fine
3.2) Supplementary Requirements:
? Have hours of operation that are 24 x 7 - Because system can be an automated process, so it
can 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 to
4: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 pages
gets 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
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 Server
should 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 spend
valuable time worrying about how to maintain sessions within the application. The Web
Application Server should provide these services.

Software Requirements Specification: Dwellers

Uploaded by

Copyright:

Available Formats

Software Requirements Specification: Dwellers

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Software Requirements Specification: Dwellers

Uploaded by

Copyright:

Available Formats

Software Requirements Specification

Online Library Management System

1.2 Project Scope

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

• IEEE SRS Format

 J2EE: Application Architecture

2.1 Product Perspective:

Web WAS DB2

2.2 Software Interface:

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

2.3 Hardware Interface:

2.4 Communication Interface:

 Client on Internet will be using HTTP/HTTPS protocol.

2.5 Product Function:

2.6 User Characteristics:

• GUI is only in English.

2.8 Use-Case Model Survey:

2.9 Architecture Diagram:

Application Layer Business Layer Data Layer

Login Valid User

Request Book tbl_request

Return Fine tbl_bookMaster

Manage Valid User

Manage Valid User

2.10 Database Design:

2.11 Assumptions and Dependencies:

3.1 Use-Case Reports:

 Name of use case: Managing Members

Ask for system user to enter

Re-enter the username Is the user

 Name of use case: Adding Members

• Query will be submitted.

Ask for system user to enter

Re-enter the username Is the user

 Name of use case: Modify Member

Ask for system user to enter

Re-enter the username Is the user

 Name of use case: Delete Member

Ask for system user to enter

Re-enter the username Is the user

 Name of use case: View Reports

• Administrator is already logged in.

Ask for system user to enter

Re-enter the username Is the user

 Name of use case: Available Books

Ask for system user to enter

Re-enter the username Is the user

He can view reports

 Name of use case: List of authors.

Ask for system user to enter

Re-enter the username Is the user

He can view reports

 Name of use case: List Of publishers.

Ask for system user to enter

Re-enter the username Is the user

He can view reports

 Name of use case: List of Transactions.

Ask for system user to enter