LiMS Version 1.

0
Software Requirements Specification 22/02/11
Gecuites

Team Name: Gecuites

Online Library Management System (LiMS)

Software Requirements Specification

Version 1.0

Team Guide: Mr. Yogesh Joshi

Members: Aditi Meharwal, Abhishek Tiwari, Neha Soni, Himanshu Singh

College Name: Ujjain Engineering College, Ujjain

Department: Computer Science & Engineering

State: Madhya Pradesh

Gecuites/LiMS Page 1
LiMS Version 1.0
Software Requirements Specification 22/02/11
Gecuites

Revision History

Date Version Description Author

22/02/11 1.0 this is the first Attempt and we are giving SRS Gecuites

Gecuites/LiMS Page 2
LiMS Version 1.0
Software Requirements Specification 22/02/11
Gecuites

Table of Contents
Description Page No.

1. Introduction 4
1.1. Purpose 4
1.2. Scope 4
1.3. Definition, Acronyms, and Abbreviations 4
1.4. References 5
1.5. Technologies to be used 5
1.6. Overview 5

2. Overall Description 5
2.1. Product Perspective 5
2.2. Software Interface 5
2.3. Hardware Interface 5
2.4. Product Function 6
2.5. User Characteristics 6
2.6. Constraints 6
2.7. Architecture Design 7
2.8. Use Case Model Diagram 8
2.9. Class Diagram 9
2.10. Sequence Diagram 10
2.10.1 ER Diagram 10

2.11. Assumptions and Dependencies 11

3. Specific Requirements 11
3.1. Use Case Reports 11
3.2. Supplementary Requirements 12

Gecuites/LiMS Page 3
LiMS Version 1.0
Software Requirements Specification 22/02/11
Gecuites

Software Requirements Specification

1. Introduction: This project is an Internet based application that can be accessed throughout
the campus. Via this project we are taking the college manual library to online. Students have
to issue and submit their books into a manual library but the benefit of Online Library
Management System is that they don’t have to come to library to check their accounts and
availability of books/magazines from their account. This system can be used for a librarian to
find out who is having a particular book. This is one integrated system that contains both the
user component and the librarian component.

1.1 Purpose: Manual work will be reduced, Time and resource management can be
easily done, Accessibility of the system 24 hours a day, 7 days a week, multiple users
can be entertained without difficulty, ease for the librarian to add/remove the
books/magazines, very easily maintain records of books/magazines, members.
1.2 Scope: The Scope of the Online Library Management includes:
It is a multi-user version and can take care of all the fundamental functions of a
Library like Issuing, Submitting, and Searching Books online, check account details
online too. It can satisfactorily cater to all the basic functions of a small library
system.

1.3 Definitions, Acronyms, and Abbreviations:

• HTML(Hyper Text Markup Language):It is used to create static web pages
• JSP (Java Server Pages): It is used to create dynamic web content.
• J2EE (Java 2 Enterprise Edition): It is programming platform, belonging to
java platform which is used for developing and running distributed java
applications.
• WASCE (WebSphere Application Server Community Edition): It is an
application server that runs and supports the J2EE and the web service
applications.
• WSAD (WebSphere Studio Application Developer): It is a designer toolkit
which is designed to develop more complex projects by providing a complete
dynamic web service.
• DB2 (IBM Database 2): It is a database management system that provides a
flexible and efficient database platform to raise a strong "on demand" business
applications
• HTTP (Hyper Text Transfer Protocol): It is a transaction oriented client/ server
protocol between a web browser and a web server.
• XML (Extensible Markup Language): It is a markup language that was designed
to transport and store data.

Gecuites/LiMS Page 4
LiMS Version 1.0
Software Requirements Specification 22/02/11
Gecuites

• Ajax (Asynchronous Java Script and XML): It is a technique used in java script
to create dynamic web pages.
• Web 2.0: It is commonly associated with web applications which facilitate
interactive information sharing, interoperability, user-centered design and
collaboration on the World Wide Web

1.4 References:
Java the Complete Reference Book
Java Script Books
Xml Learning Books
http://www.appletcollection.com/java/completereference.html
http://www.java.com/en/
http://en.wikipedia.org/wiki/Java_%28programming_language%29
http://en.wikipedia.org/wiki/Ajax_%28programming%29
http://www.ajax.org/
http://www.roseindia.net/ajax/

1.5 Technologies to be used:

• J2EE: (Servlet, JSP, Java Beans) Application architecture.
• JAVA: Application Architecture.
• WASCE : (WebSphere Application Server Community Edition) Web Server
• DB2 : IBM Database
• Ajax : Asynchronous Java Script and XML
• XML : Extension Markup Language
• Web 2.0 : RSS Feed 2.0
• Rose : Modeler
• Localization : 2 Languages (Hindi, English)

1.6 Overview: The SRS will include two sections, namely:

• Overall Description: This section will describe major components of the system,
interconnections, and external interfaces.
• Specific Requirements: This section will describe the functions of actors, their
roles in the system and the constraints faced by the system.

2. Overall Description:
2.1 Product Prospective:
This product is complete in itself. It is depending on the software that acts as an interface
like Eclipse, DB2 and WASCE.
2.2 Software Interface:
• Front End Client: JAVA
• Web Server: WASCE
• Data Base Server: DB2
• Back End: DB2
2.3 Hardware Interface:

Gecuites/LiMS Page 5
LiMS Version 1.0
Software Requirements Specification 22/02/11
Gecuites

• Client Side: Operating System: Linux, MAC or UNIX. Processor: Pentium III
or 2.0 GHz or higher, RAM: 256Mb or more
• Server Side: Operating System: Linux, Processor: Pentium 3.0 GHz or higher,
RAM: 256 Mb or more, Hard Drive: 10 GB or more

2.4 Product Functions: There are different users who will be using this product:
• Librarian who will control the library.
• Member who will be accessing library online
• Administrator who will first login into system and register the librarian.

2.4.1 Features that are available for the member:

• Member can check their account details
• Can view different categories of book in the library
• Can search books by name, author, publisher, subject
• Can view the history of books issued previously
• Can put a request for a book
2.4.2 Features that is available for the Librarian:
• Librarian can issue the book to the member
• Maintain books and member records
• Maintain issue and submit records of books by the member
• Can search, add, delete, modified, books
• Can also maintain fine

2.5 User Characteristics:

There are various kinds of user for the product. Usually web product are visited by various
products

The user includes:

• Member who will be using the above features by accessing the Library Online.
• Librarian who will be acting as a controller.
• Administrator who will first login into system and register the librarian.

2.6 Constraints:

• Hardware Constraints: The system require database in order to store persistent data. The
database should have backup capabilities.
• Software Constraints: The development of the system will be constraint by the availability
of the required software such as web servers, database and development tools.
• Design Requirements: The system must be designed to allow the web usability. That is,
the system must be designed in such a way that will be easy to use and accessible on most
of the browsers.

Gecuites/LiMS Page 6
LiMS Version 1.0
Software Requirements Specification 22/02/11
Gecuites

2.7 Architecture: The architecture design includes the GUI preference in the project, web
accessibility, and make the project user friendly; the architecture is designed in such a way that it
is flexible and can be upgraded with technologies.

The system is designed in a three level architecture which are as follows:

• External Level: This is the user side where user can sign up in library, check
account details, check book availability, maintain his profile, etc.
• Middle Level: This is the librarian side where he activates the member account,
issue/submit/reserve books, update book records, maintain records of member and
books, etc.
• Inner Level: This includes the database DB2 which is the Back End where the all
data is stored and J2EE is Front End.

Gecuites/LiMS Page 7
LiMS Version 1.0
Software Requirements Specification 22/02/11
Gecuites

2.8 Use Case Diagram:

Gecuites/LiMS Page 8
LiMS Version 1.0
Software Requirements Specification 22/02/11
Gecuites

2.9 Class Diagram:

Gecuites/LiMS Page 9
LiMS Version 1.0
Software Requirements Specification 22/02/11
Gecuites

2.10 Sequence Diagram:

2.10.1 ER Diagram:

Gecuites/LiMS Page 10
LiMS Version 1.0
Software Requirements Specification 22/02/11
Gecuites

2.11 Assumptions and Dependencies:

This is assumed that a manual library is digitized here. The product needs DB2, Eclipse, and
J2EE.

3. Specific Requirements:

3.1 Use Case Report:

Actor 1:

Administrator

Function of Administrator:

The administrator will create the database. He also gives authentication to the Librarian.

Actor 2:

Librarian

Functions of Librarian:

1. Librarian activates Member account.

2. He can manage the book records like add, delete, update, etc.
3. He can manage member records.
4. He has his own personal account.
5. He could see all the transactions made by the member

Actor 3:

Member

Functions of Member:

1. Member has his own personal account.

2. He can issue, submit, reserves or request for a book.
3. He will have to pay fine for the reasons like late submission, lost book, damage book.
4. He can maintain his profile.

Functional Requirements:
• A Person should be able to login to the system through the first page of the
application and change the password after login into the system.
• See the status of the books borrowed/reserved by him and the respective due dates

Gecuites/LiMS Page 11
LiMS Version 1.0
Software Requirements Specification 22/02/11
Gecuites

and other relevant details

• Search for a particular book based on the name of the book/name of the
author/subject/etc and also list for books based on the name of the author/subject etc
• Place requests for purchasing new books to the library, by giving details about the
name of the book, name of the author, publisher.
• See who has borrowed a particular book and when is the due date for the same
• As soon as a reservation is made for a particular book, an automatic mail should be
sent to the person who made the reservation about the details. Then, a mail should be
sent to people who are having the book currently, stating a reservation has been made
on that book
• Librarian can delete, update, and add new books
• User can see their account status
• Librarian has all the information regarding member’s transaction of books and library
books details.
Non Functional Requirements:
• 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.
• Security Requirements We are going to develop a secured database for the university
.There are different categories of users namely teaching staff, administrator, library
staff ,students etc., Depending upon the category of user the access rights are decided.
It means if the user is an administrator then he can be able to modify the data, delete,
append etc., all other users other than library staff only have the rights to retrieve the
information about database.
• Secure access of confidential data (user’s details). SSL can be used.
• 24 X 7 availability
• Flexible service based architecture will be highly desirable for future extension
3.2 Supplementary Requirements:
There are no supplementary requirements.

Gecuites/LiMS Page 12