Online library management system Software Requirement Specifications

Subject: Subject code: Prepared by: Web engineering CS 850 Anirban Chakraborty Md. Enayat Ansari Arijit Mallik Mr. Annappa (Asst prof., CSE dept.) M. Tech CSE I 31-08-2012
Page | 1

Under the guidance of: Course: Branch: Semester: Submitted on:

Contents
Page No.

1. Introduction
1.1 Purpose -----------------------------------------------------------------------------------1.2 Scope --------------------------------------------------------------------------------------1.3 Glossary ---------------------------------------------------------------------------------1.4 References --------------------------------------------------------------------------------2. Overall description 2.1 System environment --------------------------------------------------------------------2.2 Use-case diagram ------------------------------------------------------------------------2.3 Assumptions and dependencies --------------------------------------------------------2.4 Constraints ------------------------------------------------------------------------------- -

3
3 3 4 4

5
5 6 7 7

3. Specific requirements

3.1 Functional requirements ---------------------------------------------------------------- 8 3.2 Non-functional requirements ----------------------------------------------------------- 11

Page | 2

1. Introduction
A library is an organized collection of resources made accessible to a defined community for reference or borrowing. It provides physical or digital access to materials like Books, Journals or Periodicals, Newspaper etc. Mostly libraries are managed manually by librarians or support staffs. A library is organized for use and maintained by a public body, an institution, a corporation, or a private individual. The process of borrowing, returning books, checking the availability of books is done manually. But in the age of digitization and automation Library Management System should also be made online. Keeping this requirement in mind we intend to present the Online Library Management System which would be beneficial for the students, teachers as well as the library staffs.

1.1. Purpose
The purpose of this document is to provide a high-level description of the system and analyze the needs or requirements. It intends to focus on the facilities to be provided by the system. The main aim of this Software Requirement Specification (SRS) is to describe the external behavior of the system and to define the operations, performance and other nonfunctional requirements.

1.2. Scope
The Online Library Management System to be developed will be of great use to the students, faculties and library staffs; they can login to the system and search for books; books could be borrowed and returned also. Book rating system will also be there. Librarians will be given certain privileges like adding a new book, adding a new user, deleting a book from the database etc. Librarians can also search for the particular physical location in the library where a book is located.

Page | 3

1.3. Glossary

Term SRS IEEE

Definition Software Requirement Specifications Institute of Electrical and Electronic Engineers Hyper Text Transfer Protocol

HTTP

1.4. References 1. SRS Format, IEEE Standards Collection, 2001 edition. 2. Library [online] 2012, http://en.wikipedia.org/wiki/Library (Accessed: 29 August 2012).

Page | 4

2. Overall description
The online library system is a complete package to be used by library in order to improve the efficiency of the library staffs. The online library system benefits all the users such as faculties and students.

2.1. System environment

The online library management web site will be operated from central server. The database will be divided into online and offline stores. The application server will communicate with the database servers. Both online and offline stores will consist of central and departmental sections. Communication of the client and server sides will take place using HTTP.

Client web browsers

HTTP

Application server

Database server

Clients i. Students ii. Faculties iii. Library staffs

Online store Offline store

Central

Departmental

Central

Departmental

Client Side

Server Side

Page | 5

2.2. Use case diagram

Approves new user request Creates account Administrator Puts up notice Library staff

Adds new book

Searches location of book

Deletes user account Feedback

Modify book details Issues book Request for e-book

Search book Download e-book

Faculty

Request for book Check profile

Student

Rate books

Access SW library Access other materials

Page | 6

2.3. Assumptions and dependencies

1. There is a central library and several departmental libraries in the campus. 2. Users, i.e. stakeholders are broadly classified as students, faculties, library staffs and the

administrator. 3. All the library materials are associated an id with it. 4. Users should have sufficient basic knowledge to use computers and internet.

2.4. Constraints
Hardware constraints The system which will contain the database needs to have backup facility in order to maintain the persistence. Software constraints The system is able to run in the client side only if it has the internet facility. Future constraints There is always the scope of arising new constraints in the design and development phase which cant be measured a-prior. Such constraints will be mentioned in the subsequent documentations if they arise.

Page | 7

3. Specific Requirements
Under this section, we will have a look at functional and non-functional requirements in details.

3.1. Functional requirements

Function name: Login details Users will enter their login credentials on the fields provided. Upon successful validation they will be presented with a profile page where they can use the available services.

Function name: Student Registration Students and faculties will register themselves filling up all the details in the space provided. Upon successful validation a new account will be created and administrator will be notified. Once after their account is verified the account will be activated and then they can avail the services of the system.

Function name: Put up notice Administrator can put notices for the staffs or students. To put up a new notice administrator will select the audiences (staff or student) for the notice then after writing and submission of notice it will be flashed to homepage of respective users.

Function name: Approval of account requests Administrator is notified after creation of student account. Then after the verification of student details accounts can be activated or administrator can disapprove any account not having correct details.

Page | 8

Function name: Add library staff Administrator can add library staff to the system. To create a new account administrator will have to provide all the details about staff and after the successful validation new library staff will be added to the database and usernames/passwords are generated by the system to log in to the system by the staff.

Function name: Add book Library staffs can add new book details in the library. After successful validation acc. numbers for book is generated and details are saved in the database.

Function name: Search book location All users can search for the location of particular book. To search a book location users will provide keywords (title, author and publisher), if found location of book will be returned by the system.

Function name: Issue book User requests for a particular book providing their roll/id then and book can be issued only if the request is valid. A request is valid only if the user has not borrowed maximum numbers of books which is 6.

Function name: Search book It is one of most important functions of the library system meant for faculties and students. User can provided primary (necessary) and secondary (optional) search parameters. Primary keywords consist of subject, title, publisher and author. Secondary keywords consist of edition and rating.

Function name: Modify book details Library staffs will enter the search keyword for the book to be modified After Selecting the book details can be modified by providing details in the form provided upon successful validation details saved to the database.

Page | 9

Function name: Check history Users can check which books they have borrowed currently with their due dates. Users can also view the history that which books they borrowed in past.

Function name: Request for e-books Users can search for e-books after entering to e-book section providing different search parameters (author, title and publication). After selection of e-book they can request it, they will be provided with a download link if they have not exceeded the limit.

Function name: Rate books Users can rate books on a scale of 1 to 10. Students can rate only the books they have borrowed. Faculty can rate all the books.

Function name: Download online materials Users can have access to online papers, journals, thesis etc. There is no limitation to access these.

Function name: Access software library Links for downloading all relevant software will be provided in SW lib section. Any user can download it without any restriction.

Function name: Delete user Administrator can delete the users when their usage period has been expired. To delete a user (student, faculty and library staff) administrator will have to search for the user using roll numbers for student and employee id for faculty and library staff then after the selection of user their account can be deleted from the database.

Function name: Feedback Any user can leave his feedback with name and e-mail id. It will be stored in the database and will be informed to the administrator in feedback section.
Page | 10

3.2. Non functional requirements

1. Safety The database may get crashed any time due to some failures by operating system, due to power failure etc. Therefore backup should be always available in another backup system. 2. Reliability The database is accessed very frequently. Thus, all modifications in the database should be persistent and there shouldnt be any inconsistency in the database. 3. Portability The technologies used for development should be such that it is supported in almost all highly used web browsers available for different operating systems. 4. Extensibility In future, it might be possible that further features will be added to the system or some features will be removed or modified. Thus, system has to be developed in such a way that extension of functionalities is permitted with minimum efforts.

Page | 11