Siddaganga Institute of Technology, Tumkur

ONLINE LIBRARY MANAGEMENT SYSTEM Software Requirement Specification

Team Name Team Guide Team sitinnovators Guide

SARATH S. Team Guide

Asst. Prof. R.Sumathi

Team Team Members Team Members ASHES VATS Ashutosh Kumar RAVI ANAND Jitendrti AMIT KUMAR BHAGAT

Table of Contents
1.0 Introduction 1.1 Purpose 1.2 Scope 1.3 Definitions, Acronyms and Abbreviations 1.4 References 1.5 Technologies to be used 1.6 Overview 2.0 Overall Description 2.1 Product perspective 2.2 Software interface 2.3 Communication interface 2.4 Product function 2.5 Use Case Model Survey 2.6 Class diagram 2.7 Sequence diagram 2.8 Architecture diagram

2.9 Database design 2.9.1 ER Diagram 2.9.2 Schema

2.10 Assumptions and Dependencies 2.11 Constraints 3.0 Specific Requirements 3.1 Use Case Reports

Software Requirements Specification

1.0) Introduction
Online library management system is an intranet based application that can be used to access the resources of college library. Users can access the system throughout the campus
.

1.1) Purpose
Conventionally, the students and faculty have to go to college library to issue any book of their interest. Many times; the book is not present in library. This results in wastage of time as they have to go in person each time. And also the librarian has to maintain a manual card system to keep a record of issued book. Generally this is error prone. In this system, we have provided the online facility to reserve and cancel book. Librarian can also manage the books in library with ease. The students need to go to library just once at the time of
4

collecting book. Thus; the system will prove beneficial to all.

1.2) Scope
Create different system users and assign corresponding privileges. Manage all the user details such as user name, department, phone numbers, address, books reserved, current books hold, email addresses from one central location. Also manage all the book details such as title, author, publisher, number of copies from the same central location.

Track all books and users of the system.

The user can see the book details borrowed by him after logging in.

The user can search for a particular book based on title, author, and publisher. Creation of new college user requires verification by librarian.

All users are authenticated to avail the services.

5

Automatic notification like email for functions like reservation, cancellation of book, purchase request for new book.

Help-pages in the form of FAQ to facilitate user.

The librarian able to add/remove book from the inventory.

Librarian able to see the purchase request for new books made by users and able to approve/reject the same. The users able to reserve book currently borrowed by other.

1.3) Definitions, Acronyms and Abbreviations

Admin Administrator (super user), he is the controller of all the end users, librarian and books. Librarian He/she will be appointed by the college administrator and will take care of all the books and end users. He can place new orders, see end user profile; delete any book record from the system etc. End users End users are those who have registered in this site.
6

Faculty, student, author and publisher are considered as end users.

College users-college users include student and faculty of college are registered. These users will be able to reserve/cancel books. Non college users-Non college users include publisher and author books that are written/published by them only. HTML Hypertext Markup Language is to create static websites.

who

who

visit the website as registered user. These users will be able to search

J2EE Java 2 Enterprise Edition is a programming platform and it is the part of the java platform for developing and running distributed java applications. WASCE Web sphere application server community edition is an application server that runs and supports the J2EE and web service applications. WSAD Web sphere studio application developer is a designer toolkit which is designed for develop more complex projects by providing fully dynamic web service. DB2 Database 2 is the database management system that provides a flexible and efficient database business applications. EJB Enterprise java bean, it is architecture for the development and deployment of transactional, distributed object applications-based, serverside software components. platform to erect strong on demand

HTTP Hypertext transfer protocol is a transaction oriented client/server protocol between web browser and a web server. HTTPS Secure hypertext transfer protocol is a hypertext transfer protocol over secure socket layer. TCP/IP Transmission control protocol/internet protocol is the communication protocol used to connect hosts on the internet.

1.4) References
IEEE SRS format Project specification requirement (provided by IBM)

1.5) Technologies to be used

J2EE Application architecture JAVA Application architecture WSAD Development tool WASCE - Web Server DB2 Database Rational Design tool

1.6) Overview
SRS includes two sections overall description and specific requirements

Overall description will describe major role of the system components and interconnections.

Specific requirements will describe roles & functions of the actors.

2.0) Overall Description

Describe the general factors that affect the product and its requirements.

2.1) Product Perspective:

HTML Client
(end users)

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

The Client Software is to provide the user interface on system user side and for this TCP/IP protocols are used.

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),
11

DB2, OS (Windows), Web Server.

2.3) Communication Interface:

Client on Internet will be using HTTP/HTTPS protocol.

Client on Intranet will be using TCP/IP protocol.

2.4) Product Function:

Maintain user details: In this module, the details of all users of the system are maintained.

Maintaining inventory details: It contains the details of all books and magazines present in the library.

Placed order details: It maintains all the details about the book placed
12

(Author, Publisher and Number of copies) by the librarian, finally.

Book Ownership Details: It maintains the information that which user has currently borrowed the book.

Maintaining Logs: Activities of the System Users can be tracked through the logs, which is maintained by the system.

13

2.5) Use-case model survey:

Add record to database view logs manage database provide login account Manage system User <<extends>> verify details <<extends>>

approve form send mail Administrator view details

reject form

search end user details verify details view form Librarian place new order <<extends>> sign in sign up approve new order add/remove books view/update own details

view/update own detail reject new order apply for new books end user

student author

reserve/cancel book

search book publisher faculty

14

2.6) Class diagram:

15

2.7) Sequence diagram:

2.7.1) Successful login :

: end user sign up form security

: Administrator

get name

get pwd login check validity count user access

16

2.7.2) Accept sign up form:

: end user

sign up form

: Librarian

: Administrator

open

fill

submit

open

verify

accept

17

2.7.3) Reject sign up form:

: end user

sign up form

: Librarian

: Administrator

open

fill

submit open

verify

reject

18

2.7.4) Successful reservation of book:

: end user reservation form security

: Administrator

open

fill

submit get detail

check for avablity

pass

reservation conform

19

2.7.5) Accept form for placing new order for the book:

: end user form

: Librarian

: Administrator

open

fill

submit verify

accept

fill no of copies

submit

save

20

2.7.6) Reject form for placing new order for the book:

: end user

: Librarian

: Administrator

sign up form

open

fill

submit open

verify

reject

21

2.8) Architecture diagram:

22

2.9) Database design: 2.9.1) E-R diagram:

23

2.9.2) Schema diagram:

24

2.10) Assumptions and Dependencies:

The end user should have a basic knowledge of English and computer usage.

The college user should have the library card number issued by the librarian.

2.11) Constraints:
GUI is only in English. Login and password is used for identification of user 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 effected. Limited to HTTP/HTTPS .

25

3.0) Specific Requirements

3.1) Use-case reports:

? Administrator:

Responsible for managing system users, viewing logs.

Manage System Users: The Administrator will create different roles. The system users will be created and will be assigned with the different roles. More than one task and permissions can be granted or revoked from the system users.

View Logs: Responsible for checking the logs of different system user for auditing and maintaining the integrity of the system.

Verify details: Admin authenticates all the college and non college users by checking their username and password. View All Details: View the user details, details of the book in the inventory, placed order details.

26

Provides login account: After getting the sign up details from the end user, Admin provides the username and password to the end user that should be kept for future login and also admin checks for uniqueness.

Manage database: Admin maintains the entire database and he is the only authorized person to add/remove/edit end user records provided he has to get the order from the authorities .

Add records to database: Admin adds the records that are completely approved by the librarian. Send Mail: Admin sends email to all users whenever required an automatic email is send whenever he made reservation/cancellation, advance notification regarding expiry of return date, etc.

27

Librarian:

Librarian is the person who verifies the validity of students/faculty;

maintain the inventory, place new order of books, etc.

Sign in : After getting username and password from the administrator, librarian can log on to their account and access the website. View/update profile : After logging in, librarian can change his login password or can update his profile. Add/remove book: The librarian can add or remove any book in the inventory.

Verify and Approve End User Details : Librarian verifies the details of end user and approves or rejects the sign up form .He sends the approved form to the administrator.

Place order for new books : Librarian places the order for new books .He can approve/reject the request of end users regarding purchase of new books.

28

Search book : Librarian can search for any book in the inventory based on author, publisher, and title of book.

Search End User Details: Librarian can search for any registered user. This will help him to know the user who is currently having any particular book.

? College Users:
using the system. Sign up :

College users include student and faculty of the college who will be

In order to avail the services of online library system, students and faculty of college must sign up by filling the sign up form and get it verified by librarian.

Sign In : After getting the username and password from admin, users can log on to their account and can access the system.

View/Update own detail : After logging into their account, student and faculty can view their own details. They also can modify any of the details.

29

Reserve/Cancel Books: The college users can reserve any of the books in advance. The book may be present in the library or may be with another user. They can also cancel any of the books reserved earlier by them.

Apply for new books: If any book is not present in the library, the end users can request for the book from the librarian. The end user can request for new book by filling in a form which has to be approved by the librarian. Search for books: The end user can search for any book in the inventory based on the title, author, and publisher of the book. If not present in the library the users can get the information about the user who is currently having that book. He can also get other information like when the book is going to be returned.

? Non College Users: Non College Users include author and publisher who will be
using the system. Sign up: In order to use the college library, non-college users have to sign up by filling a sign up form which has to be verified by the librarian.

30

Sign In: After getting username and password from admin, non-college users can log onto their account and access the system.

Apply for new books: Author and publisher can apply for any of the new book which is currently launched in the market.

Search books: Author and publisher can search for any book in the inventory based on title of the book.

31