Online Library Management System

Fouridiots
Online October 31
Library
Management
System
2009
Sri Jayachamrajendra College Of
Engineering, Mysore (Karnataka)
Team Mentor SRS Version
1.0
Anand Raj Ulle
Team Members
Amit Kumar Roushan
Arpit Rohatgi
Birendra Kumar
Prateek Chandra Roy
Online Library Management System Version : 1.0
Software Requirements Specification Date : October 31, 2009
REVISION HISTORY
Date Version Description Author

31/10/2009 1.0 Synopsis Fouridiots
Fouridiots KARNATAKA/TGMC 2009 Page | 2

Table of Contents
1. Introduction
1.1 Purpose
1.2 Scope
1.3 Definitions, Acronyms and Abbreviations
1.4 References
1.5 Technologies used
1.6 Tools used
1.7 Overview
2. Overall Description
2.1 Use Case Model Survey
2.2 Class diagram
2.3 Activity Diagram
2.4 Sequence diagram
2.5 ER Diagram
2.6 Assumptions and Dependencies
3. Specific Requirements
3.1 Use Case Reports

1. Introduction
Online Library Management System (LiMS):-
This project is an Intranet based 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.1 Purpose:-
The purposes of this application are as follows:
• The software is for automation of library.

• It provides following facilities to
Operator:
• Can enter details related to a particular book.

• Can provide membership to members.
Administrator:
• Can read and write information about any member.
• Can update, create and delete the record of membership as per

requirement and implementation plants
Students and Faculty:
• Can login to his account

• Can update his profile ,search for a books, CDs, journals etc and even issue
& reserve them
• Can even place requests for purchasing new books to the library.
Author & Publisher:
• Can login to the system and publish advertisement for their books
• Can request the administrator to add their new books
1.2 Scope
The different areas where we can use this application are:
• Any education institute can make use of it for providing information about
author, content of the available books.
• It can be used in offices and modifications can be easily done according to
requirements.
1.3 Definitions, Acronyms and Abbreviations
• User – A general user ID is provided to operator, administrator, students,

faculty, author and publishers.
• Data flow diagrams – It shows the data flow between entities.
• Unique key – Used to differentiate entries in a database.
• HTML – Hypertext Markup Language is to create static websites.
• 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.
• WAS – Web sphere application server community edition is an application
server that runs and supports the J2EE and web service applications.
• RSA – Rational Software Architect 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 platform to erect strong on demand
business applications.
• XML - Extensive Markup Language used for data transfer and XML is
stored naturally in DB2
• EJB – Enterprise java bean, it is architecture for the development and
deployment of transactional, distributed object applications-based, server-
side software components.
• 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 used
• HTML – Hyper Text Markup Language

• Java Script – Script Language
• XML – Extensive Mark Up Language
• JAVA – Application architecture
• J2EE – Application architecture
• EJB – Enterprise Java Bean
• AJAX – Asynchronous Java script And XML
1.6 Tools used
• RSA – Rational Software Architect 7.0

• DB2 Express – ‘C’ – Database

• WAS – Websphere Application Server 6.0
• TSM – Tivoli Storage Manager
1.7 Overview
• Project is related to library management which provides reading services

to its members.
• Any person can become a member of the library by filling a prescribed
form.
• They can get the book issued, so that they can take home and return
them.

2.1 USE CASE MODEL SURVEY
View Log Files Add Books
Add Member Remove old books
Remove Member Fine collection on late submission
Send e-mail reminder Librarian Change DB Location
Advertize for Books
Publisher
View Help Update Profile Login Change password Sign up Logout Search of books through OPAC
Reservation for a book Student

Faculty Author
Cancellation of reserved book
Request for a new book
Get feedback from other members
Status of the book issued

Issue of book
Return of books
2.2 CLASS DIAGRAM

access access
DATABASE LIBRARIAN BOOKS DATABASE
bookname : String
createAccount () • Maintenance ()
access isbn : String
updateAccount ()
author : String
deleteAccount ()
publisher : String
provide service price : Float
bookCode : String
noOfBooks : Int
rackNo : Int
Can register subjectCode : String
1 USER *
addBook ()
removeBook ()
0..1 search ()
showBokDetail ()
LOGIN showIssueHistory ()
loginID : String
password: String
STUDENT PUBLISHER REFERNCE BOOKS
verifyLogin () DATABASE
forgotPassword () search () search ()
logout () reserve () advertise () bookname : String
changePassword () cancel () isbn : String
issue () author : String
status () publisher : String
return () price : Float
request () bookCode : String
noOfBooks : Int
rackNo : Int
subjectCode : String
FACULTY AUTHOR
addBook ()
search () search ()
removeBook ()
issue () getFeedback ()
showBookDetail ()
status ()
return ()
request () 0..1
Register
loginID : String
password : String
fname : String
lname : String
e-mail : String
age : Int
sex : String
securityquestion : String
agreement : Boolean
setprofile()
getProfile()
deleteProfile()
verifyProfile()
2.3 ACTIVITY DIAGRAM OF EACH OPERATION
2.3.1 Student class
• Add Student : add a new student
validateStudent [ exists ] return error

message
[ not exists ]
add the student record to return success

Student table message
• Delete Student : delete an existing student
validat eStudent [ not exists ] return error

message
[ exists ]
delete t he student record return success

to Student table message

• Update Student : update information of existing student
Update the student record in

the Student table
• Search Student : search students
Query the student record

in Student table
return Resultset

• Validate Student : validate student
Query the student in Student

table according to studentID
Return [ not empty ] Return true

Resultset
[ empty ]
Return false
2.3.2 BOOK CLASS
ADD BOOK: ADD A NEW BOOK TO DATABASE
Check Book record

in database
yes Return "Book already

exist
exist" message
no
Insert book record

in database
return success
message

Exist: Check if the book record already exist in database.
Search Book record

in database
no return not exist

found record?
message
yes
return exist
message

Search Book: Search books in database
search book record

in database
return
resultset
Update Book: modify book info
update record in
database
return success
message

Delete Book: Delete a book in database
check
existence
no
exist?
yes
delete the
record return fail
message
return success
message

2.4 SEQUENCE DIAGRAM:
• USER LOGIN
Case 1: EXCEPTIONAL CASE
User
user service
Librarian
provi Admin DB
1: enter username and password
2: forward
3: verify
4: login incorrect
5: login failed

Case 2: NORMAL FLOW FOR USER LOGIN
User
user servivce
Librarian AdminDB
Admin DB
provider
2: forward 3: verify
4: confirmed
5: login successful

• REGISTERATION/SIGNUP
Case 1: EXCEPTIONAL CASE 1
User
user service
Librarian
provi AdminDB
Admin DB
1: request register
2: enter details
3: submit details
4: verify
5: registration failed
(Incomplete data)

Case 2: EXCEPTIONAL CASE 2
User
user Librarian
Service Admin
AdminDB
DB
provi
1: request register
2: Enter details
3: Submit details
4: forward
5: verify register
6: registered user already exists
7: registration failed

Case 3: NORMAL FLOW FOR USER REGISTRATION
User
user Service provi
Librarian Admin DB
1: request register
2: Enter details
3: submit details
4: forward
5: verify
6: confirm
7: registration successful

• SEARCH THROUGH OPAC
User
user service
Librarian
prov Admin
AdminDB
DB
1: request search for books
2: forward
3: verify availabilty
4: not available
5: display message

Case 2: NORMAL FLOW FOR SEARCH
User
user service provi
Librarian Admin
AdminDB
DB
1: request for search
2: forward search
3: verify the availability
4: available
5: display search result

• ISSUE OF BOOKS
User
user service
Librarian
provi Admin
AdminDB
DB
1: request for issue
2: forward
4: Not available
5: request failed

Case 2: NORMAL FLOW FOR ISSUE BOOKS
User
user service
Librarian
provi Admin
AdminDB
DB
1: request for issue
2: forward
4: available
5: book issued

• RETURN OF BOOKS
Case 1: RETURN WITH FINE
User
user service
Librarian
provi Admin
AdminDB
DB
1: request for return
2: forward
3: verify due date
4: date>due date
5: fine
6. Payment 7. Verify
8. Return

Case 2: NORMAL FLOW FOR RETURN WITHIN DUE DATE
User
user service
Librarian
provi Admin
AdminDB
DB
1: request for return
2: forward
3: verify due date
4: date<=due date
5: return

• ADDITION OF NEW BOOKS
User
user service
Librarian
provi Admin
AdminDB
DB
1. Enter details of new book
2: verify
3. Book added
4. ready for access

• REMOVAL OF OLD BOOKS
User
user service provi
Librarian Admin
AdminDB
DB
1. Enter details of old book
2: verify
3. Book removed

• RESERVATION OF BOOKS
User
tourist Service
Librarian
provi Admin
AdminDB
DB
1: reserve the book
2: verify login
3: yes
4: enter reservation details
5: forward
6: verify reservation
7: confirm
8: confirm

• CANCELLATION OF PREVIOUS REGISTRATION
User
tourist Service
Librarian
provi Admin DB
Admin DB
2: verify login
3: yes
4: enter cancellation details
5: forward
6: verify cancellation
7: confirm
8: confirm

• CHANGE PASSWORD
User
tourist Service
Librarian
provi Admin DB
Admin DB
2: verify login
3: yes
4: enter new password
5: forward
6: verify new password
7: confirm
8: confirm
2.5 E-R DIAGRAM

No. of
Journals Magazines Library books Rack no
ISBN
Subject
Reference Section code
Contains Book Issue Section
Book code
Book
Newspaper name
Books
Author
Price
Publisher
Issue
Date of
Login ID
Issue
Status Amount
Return Issue
Member
Department amm Department
Type Date of
Expiry
Name
Book Code Book Code

ID No. Book Name
Status of Return ID No. Status of Issue

Book Name
Date of
Date of Issue Date of Expiry Date of Issue
Expiry

2.5 ASSUMPTIONS AND DEPENDENCIES
• The end user should have a basic knowledge of English and computer
usage.
• The end user should be able to provide the appropriate information as per
the request made by the services like book name during the subscription.
• Administrator is created in the system already.
• Roles and tasks are predefined.
3.0 SPECIFIC REQUIREMENTS
3.0.1 USE CASE REPORTS
STUDENT/FACULTY
• Sign Up:
In order to register for various facility of the library he must enter all the
details like username, email, member ID, password and various personal
details.
• Sign In:
After getting the username and password, end users can log on to their
account, can change password and access the library.
• Open profile:
End user can open their profile which contains the personal details which
he/she provided during Sign up.
• View profile:
End user can view their profile which contains the personal details
which he/she provided during Signup.
• Update profile:

End user can update their profile which contains the personal details which
he/she provided during Sign up if any update required.
• Change password:
The end user can change the password after signing in.
• Issue Books:
The end user can issue the books from issue section of the library.
• Return Books:
The end user can return the books. Fine is charged if he/she submits the
book after the due date.
• Request for a new Book:
The end user can place a request to add a new book to the library.
• Reserve Books:
The end user can reserve the books prior to its issue if the book is
unavailable in the library at present.
• Cancel Books:
The end user can cancel the reservation made.
• Search Books through OPAC:
The books in the library can be searched through parameters like book
name, book code, Author, subject name and department.
• Status of a Book:
The end user can check the status of any book.
• Help:
The terms and conditions, rules and FAQs are listed in this category and can
be accessed from the end user.
• Sign out:
The user can exit from the application after the book transaction is
completed.

LIBRARIAN
• Sign in:
The librarian can sign in and do the various jobs.
• Maintenance:
The librarian maintains the databases of the books, members and gets the
feedback from the users.
• Add Books:
Add new books to the library with all the details of the book.
• Remove Books:
The old and damaged books are removed from the library and kept to the
warehouse.
• Add Member:
The members are added through the confirmation of the librarian only.
• Remove Member:
The members are removed if he/she does exist in the college.
• Search:
The librarian can search the users and books with any parameters.
• View Log Files:
The librarian can check the record of the previous database.
• Send email reminder:
The reminder is sent to the users four days prior to due date of the book.
• Fine collection:
The fine is collected from the user if he/she has submitted the book after
the due date.
• Change database location:
The librarian can change the location of the database stored.
• Sign Out:
After completing all the work the librarian comes out of the application.

AUTHOR
• Sign Up:
details.
• Sign In:
• Open profile:
• View profile:
• Update profile:
• Help:
• Get Feedback:
The Author can get feedback from the readers and do the corrections in his
next edition.

• Sign out:
completed.
PUBLISHER
• Sign Up:
details.
• Sign In:
• Open profile:
• View profile:
• Update profile:
• Help:

• Advertise:
The publisher can advertise his/her books by placing add on the
application.
• Sign out:
completed.

Online Library Management System

Uploaded by

Copyright:

Available Formats

Online Library Management System

Uploaded by

Document Information

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

Online Library Management System

Uploaded by

Copyright:

Available Formats

Fouridiots

Software Requirements Specification Date : October 31, 2009

Date Version Description Author

Fouridiots KARNATAKA/TGMC 2009 Page | 2

Software Requirements Specification Date : October 31, 2009

1.3 Definitions, Acronyms and Abbreviations

1.5 Technologies used

1.6 Tools used

2.2 Class diagram

2.3 Activity Diagram

2.4 Sequence diagram

2.6 Assumptions and Dependencies

Fouridiots KARNATAKA/TGMC 2009 Page | 3

Software Requirements Specification Date : October 31, 2009

• The software is for automation of library.

• Can enter details related to a particular book.

• Can read and write information about any member.

• Can update, create and delete the record of membership as per

Students and Faculty:

• Can login to his account

Fouridiots KARNATAKA/TGMC 2009 Page | 4

Software Requirements Specification Date : October 31, 2009

Author & Publisher:

1.3 Definitions, Acronyms and Abbreviations

• User – A general user ID is provided to operator, administrator, students,

Fouridiots KARNATAKA/TGMC 2009 Page | 5

Software Requirements Specification Date : October 31, 2009

• DB2 – Database 2 is the database management system that provides a

• IEEE SRS format

1.5 Technologies used

• HTML – Hyper Text Markup Language

1.6 Tools used

• RSA – Rational Software Architect 7.0

Fouridiots KARNATAKA/TGMC 2009 Page | 6

Software Requirements Specification Date : October 31, 2009

• DB2 Express – ‘C’ – Database

• Project is related to library management which provides reading services

Fouridiots KARNATAKA/TGMC 2009 Page | 7

Software Requirements Specification Date : October 31, 2009

2.1 USE CASE MODEL SURVEY

View Log Files Add Books

Add Member Remove old books

Remove Member Fine collection on late submission

Send e-mail reminder Librarian Change DB Location

Advertize for Books

Reservation for a book Student

Request for a new book

Get feedback from other members

Status of the book issued

Software Requirements Specification Date : October 31, 2009

2.2 CLASS DIAGRAM

Software Requirements Specification Date : October 31, 2009

2.3 ACTIVITY DIAGRAM OF EACH OPERATION

2.3.1 Student class

• Add Student : add a new student

validateStudent [ exists ] return error

add the student record to return success

• Delete Student : delete an existing student

validat eStudent [ not exists ] return error

delete t he student record return success