[DIGITAL LIBRARY

MANAGEMENT SYSTEM]
SOFTWARE REQUIREMENTS SPECIFICATION DOCUMENT

01-04-2017

Name ROLL NO: .......]

SESSION: 2015-2017 | <CLG NAME
 Digital Library Management System

Revision History
Date Description Author Comments
<date> <Version 1> <Your Name> <First Revision>

Document Approval
The following Software Requirements Specification has been accepted and approved by the following:

Signature Printed Name Title Date

Dr. Supervisor, CSIT 21306 <date>

ii
 Digital Library Management System

Table of Contents

1. Introduction 1
1.1 Purpose 1
1.2 Scope 1
1.3 Definitions, Acronyms, and Abbreviations. 1
1.4 Reference 2
1.5 Overview 2

2. The Overall Description 3

2.1 Product Perspective 3
2.1.1 Operations 3
2.1.2 Site Adaptation Requirements 3
2.2 Product Functions 4
2.3 User Characteristics 4
2.4 General Constraints 5
2.5 Assumptions and Dependencies 5

3. Specific Requirements 6
3.1 External Interface Requirements 6
3.1.1 System Interfaces 6
3.1.2 Interfaces 6
3.1.3 Hardware Interfaces 6
3.1.4 Software Interfaces 6
3.1.5 Communications Interfaces 8
3.2 Functional Requirements 8
3.2.1 Register User 8
3.2.2 Login: 9
3.2.3 Add books: 9
3.2.4 Delete books: 10
3.2.5 Manage order: 10
3.2.6 Search book: 11
3.2.7 View book detail: 11
3.2.8 Maintain account: 12
3.2.9 Update profile: 12
3.3 Use Cases 13
3.3.1 Administrator 13
3.3.2 User 14
3.5 Non-Functional Requirements 15
3.5.1 Performance 15
3.5.2 Reliability 15
3.5.3 Availability 15

iii
 Digital Library Management System

3.5.4 Security 15
3.5.5 Maintainability 15
3.5.6 Portability 15

4. Analysis Models 16
4.1 Sequence Diagrams 16
4.2 Data Flow Diagrams (DFD) 17

iv
 Digital Library Management System

1. Introduction
The introduction of (SRS) Software Requirement Specification describes the overview of
digital library. This document describes different aspects of application that includes the design
and development of a digital library depends on the computer, communication and other specific
skills. A digital library is a particular library with a collection of digital article that can consist of
different text, audio, video and visual material about the books. The proposed system of digital
book rent is fully an automated one. In this site the customer can view the books detail and its
requirement. Online books, borrow is possible with this system. Customer and administrator are
also interacting with each other.

1.1 Purpose
The purpose of digital library is to store, collect and organize information about the books in the
form of digital. Digital library is a tool which is used in the automaton updated the books record.
We can access online library material (such as notes, lecture, books, and tutorials). The main
purpose of this project is to maintain the record using computers and to provides the different
reports about the books .

1.2 Scope
The project being developed is called (DLMS).This project is developed to provide the facility
to the users , customers barrowed a book .This software application will allow the customer to
create their own accounts to use this application. The customers search the data about the
different books. The system application also allows the administrator to manage the inventory.
The admin can add and delete books in library and also update the record of the books which is
stored in the library. The goal of a library is to store and collect data about the books.

1.3 Definitions, Acronyms, and Abbreviations.

DLMS Digital library management system
CSS Cascading styled sheet
HTML Hyper text markup language
PHP Hyper text preprocessor
MySQL Structured query language

SRS Document 1.0 Page 1 of 21 07/06/19 f

 Digital Library Management System

1.4 Reference
https://www.slideshare.net/ANASNAIN/17337071-srslibrarymanagementsystem

https://www.quora.com/What-is-a-library

Muftafa, T., Mehmood, T., Raza, H., & Saeed, I. (2007). Web Programming. Lahore: IT Series.

Shannon, R. (2012, 08 21). What Is HTML? Retrieved 04 05, 2017, from yourhtmlsource.com:
http://www.yourhtmlsource.com/starthere/whatishtml.html

https://www.cse.iitb.ac.in/~cs101/2014.2/labs/Lab-Assignment-Submissions/2014-11-
24/145280013/23:53:42-SRS.pdf

1.5 Overview
This document contains the requirements of the system software that is being
developed. This document is split into many sections for the convenience of the reader.
The first section of the document describes the purpose and scope of the software system.
The second section of the document is named Overall Description. As the name shows,
this section contains the overall description of the document and slicing it into different
parts. The third section describes all the requirements in detail. The fourth section
contains all the necessary diagrams to model the system.

SRS Document 1.0 Page 2 of 21 07/06/19 f

 Digital Library Management System

2. The Overall Description

This section describes the functionalities which can be expected from the system and
which cannot be expected, describing the scenarios in which the system can be working
successfully.

2.1 Product Perspective

2.1.1 Operations
. Users of this system can perform many operations such as:
 User can create their accounts.
 Users can browse through the library.
 Users can add books to their system.
 Users can check out from the system and complete the transactions.
 Users can change their profile details.
 Admin can browse books of the library.
 Admin can edit books of the library.
 Admin can delete books of the library.
 Admin can update details of the books available in the library.
 Admin can add new books s in the library.
 Admin can view orders of the customer

2.1.2 Site Adaptation Requirements

In order to run this system, a customer does not have to be having any specific
hardware.

SRS Document 1.0 Page 3 of 21 07/06/19 f

 Digital Library Management System

2.2 Product Functions

Each function is for general users or for the admin of the system. Admin can
perform some specific functions and not of the general user.
The functions of the system are:
1) The system can maintain the records of different books in the inventory or
library.
(a) Book name and the name of the writer, author, publisher.
(b) . Details about the book, e.g. color, size, pages, edition.
(c) The price of the book.
2) The system can keep record of many customers.
(a) Customer can have unique username, password, email address, contact
and much other information.
(b) Any user can be a member of the system.
3) Anyone may be allowed to be the member of the system.
4) System can show the list of available items in the library.
(a) Books will be sorted in alphabetically.
5) Allow users and the admin of the system to log out from the system..

2.3 User Characteristics

 Administrator :
The administrator is one who is adding all the books detail either through online
or in direct for editing books day by day presence. The administrator provides the
services of training staff in technical and special library function. Admin should
increase the date of borrowing a book for specific type of user. He can get the
data of any person who has borrowed a book. .the administrator manages the all
aspects of grant management.
 Customer :
The customer should be provided with the updated data about the books catalog.
The admin given the facility to customer to check their account and change it. The
customer may recommend a book to be brought to a library book collection.
 User :
Users have the ability to search through books by subject, title, author, edition or
other data related to the books.

SRS Document 1.0 Page 4 of 21 07/06/19 f

 Digital Library Management System

2.4 General Constraints

. There are many constraints on this software system. Password of the members of this
system is stored in the plain text in database. So, there is no security in storing the
passwords of members. If a user tries to log in to the system, but fails many times, the
system will not be locked down. Members of the system will not be forced to apply a
strong password. A strong password means the use of alphanumeric values along with
some special characters. User can store any password he likes. The username of the
account will be the email of the members

2.5 Assumptions and Dependencies

. It is assumed that the user of this software system has access to a computer with all the
necessary hardware equipment. proper web browser must be installed on it. It is also
assumed that the user have access to working web connection in order to access the
software system on the internet.
Some other assumptions are as follows:
 The username and password of the admin may be not changed.
 Only one admin can be available for the library management system.
 No new admin can be created for the library management system.
 Admin cannot be the customer of the library management system.

SRS Document 1.0 Page 5 of 21 07/06/19 f

 Digital Library Management System

3. Specific Requirements
3.1 External Interface Requirements

3.1.1 System Interfaces

As this software system is web based, it needs to have a web server to run and execute
the services and fetch the data from the database to show it to the customer and to store
data of different users. To store the order of users, there must also be a web server.

3.1.2 Interfaces

There are many interfaces included in this software system. This project basically involve
graphical user interface to interact with the user of this software system. Today, there is
must to have a graphical user interface for the application to be successful in the market.
Command line interface is not used nowadays.

3.1.3 Hardware Interfaces

As this software application needs to be running on the internet, so the hardware system
must be connecting with a working internet connection. This software system can only be
run on the computer with having a working internet connection.
 Hard disk 30 GB space
 Ram 2.0 MB
 Processor Intel(R) core (TM) i5
 Internet connect
 Keyboard
 Mouse

3.1.4 Software Interfaces

Front End: HTML, CSS
Back End: PHP, JavaScript
Database: MySQL
Server: Wamp/Xamp
Software Tools: Adobe Dreamweaver, Notepad ++

SRS Document 1.0 Page 6 of 21 07/06/19 f

 Digital Library Management System

The software system must be able to communicate with the admin in order to manage
different things in the system. It must also be able to communicate with the sales
department of the system for order management. The system must also be able to
communicate with the data storage to get the product details. It must also be able
communicate with the customer in order to get information to get them registered.
 MySQL
SQL is a structured query language .it is used to manipulate and accessing data in
database. It can delete, update, and insert data in the database.sql works with
database programs like MS Access, DB2, MS SQL Server, Oracle, Sybase, etc.
The sql statements are used to retrieve data in the database. (Muftafa, Mehmood,
Raza, & Saeed, 2007)
 PHP
Php is a server side scripting language that is embedded in HTML. It is used to
manage dynamic content, databases, session tracking, even build entire e-
commerce sites. It is integrated with a number of popular databases, including
MYSQL, Oracle Informix, and Microsoft SQL Server. Php syntax is same as C
language. (Muftafa, Mehmood, Raza, & Saeed, 2007)
 CSS
CSS stands for cascading style sheet. It is a collection of formatting styles that
can be applied to a web page. CSS are used to modify the properties of existing
HTML tags. It can control the layout of multiple web pages. The external style
sheets are stored in css files. It provides the facility of creating websites with
consistent designs and outlook. All web browsers are based on a built-in style
sheet. When a new style is defined, the built-in style sheet is overridden. Style
sheet are used to define styles for web page in many ways. (Muftafa, Mehmood,
Raza, & Saeed, 2007)
 HTML
HTML stands for hyper text markup language. It is used to define text,
graphics, audio and video in the web pages.HTML code can be written in any text
editor like notepad. HTML elements are the building blocks of HTML pages. It
also describes formatting and hypertext link, and different components of of a
document. (Muftafa, Mehmood, Raza, & Saeed, 2007) (Shannon, 2012)
 JavaScript
JavaScript is an interpreted language that is used to add dynamic contents in web
pages. JavaScript code is executed when an event is triggered. JavaScript is used
to include messages, scrolling text, animations, menus, pop-up windows etc.
JavaScript is directly embedded in HTML. It is an open language. (Muftafa,
Mehmood, Raza, & Saeed, 2007)

SRS Document 1.0 Page 7 of 21 07/06/19 f

 Digital Library Management System

3.1.4.1 Microsoft SQL Server

The system must use MYSQL as its database component. Communication with the
database is through the server itself. So there must not be any issue communicating with
the database.

3.1.5 Communications Interfaces

The E-Commerce software system must use the HTTP protocol to communicate through
different users in the world. There must not be any other protocols be used in this
software system in order to avoid ambiguity. This is a standardized way of
communicating through different clients throughout the world.

3.2 Functional Requirements

Functional requirements of the system are those requirements which describe a function
of software system and also explain its components. It also describes the behavior of the
system. A function can be defined as the set of different things, e.g. input, processing,
and output.

3.2.1 Register User

3.2.1.1 Introduction:
The new user must to register for login.
3.2.1.2 Inputs
For registration, customers enter the following:
(Full name, password, mobile no and email address)
3.2.1.3 Processing
Check the record, if the record is matched then the inputs are sent to the database.
3.2.1.4 Outputs
If the information is matched then successful register. Otherwise, the system will
generate an error message.
3.2.1.5 Error Handling
If the information is not valid then the system displays an error message.

SRS Document 1.0 Page 8 of 21 07/06/19 f

 Digital Library Management System

3.2.2 Login:
3.2.2.1 Introduction:
If any users is already register then they can access their records by enter their passwords
and user names.
3.2.2.2 Inputs
Enter password and username for login.
3.2.2.3 Processing
Check the record in database.
3.2.2.4 Outputs
If record is exist user get access in home page.
3.2.2.5 Error Handling
If the record is not valid then system display error message

3.2.3 Add books:

3.2.3.1 Introduction:
The admin can add the books in the library.
3.2.3.2 Inputs
Enter name and serial number of new book
3.2.3.3 Processing
Save the record about new book in database.
3.2.3.4 Outputs
Successfully store.
3.2.3.5 Error Handling
Display error message if not store successfully

SRS Document 1.0 Page 9 of 21 07/06/19 f

 Digital Library Management System

3.2.4 Delete books:

3.2.4.1 Introduction
Administrator can delete the books in the library.
3.2.4.2 Inputs
Enter name and serial number of book.
3.2.4.3 Processing
Delete the book in database.
3.2.4.4 Outputs
Successfully deleted if book can be delete in database.
3.2.4.5 Error Handling
Display error message if not deleted successfully.

3.2.5 Manage order:

3.2.5.1 Introduction:
Admin manage the order of the books.
3.2.5.2 Inputs:
Enter desired book name
3.2.5.3 Processing
Desired book are stored in database.
3.2.5.4 Outputs
If book exist then request is granted.
3.2.5.5 Error Handling
If book not exist in database display error message.

SRS Document 1.0 Page 10 of 21 07/06/19 f

 Digital Library Management System

3.2.6 Search book:

3.2.6.1 Introduction:
The user can search the book.
3.2.6.2 Input:
Enter the name serial no of search book.
3.2.6.3 Processing:
Search book are stored in the database.
3.2.6.4 Output:
If the search book exist in the database, then the request is complete.
3.2.6.5 Error handling:
If the searched book not exist in the database. The system generate error message.

3.2.7 View book detail:

3.2.7.1 Introduction:
The customer or user can view the whole detail of the books.
3.2.7.2 Input:
The user enters the name, edition, and serial no of the book for detail.
3.2.7.3 Processing:
The record of all books are stored in the database.
3.2.7.4 Output:
The record is successfully stored or not in database.
3.2.7.5 Error handling:
If record are not stored in database then display error message.

SRS Document 1.0 Page 11 of 21 07/06/19 f

 Digital Library Management System

3.2.8 Maintain account:

3.2.8.1 Introduction:
The user maintains the account.
3.2.8.2 Input:
The user enters the name, password, and email address for maintain account.
3.2.8.3 Processing:
Reset the account in the database.
3.2.8.4 Output:
The account is successfully reset in database.
3.2.8.5 Error handling:
If account is not reset. Display error message.

3.2.9 Update profile:

3.2.9.1 Introduction:
The user update the profile .
3.2.9.2 Input:
Enter the new profile in database.
3.2.9.3 Processing:
The new profile is stored in the database.
3.2.9.4 Output:
The profile is successfully saved .
3.2.9.5 Error handling:
If the profile is not saved successfully then display error message.

SRS Document 1.0 Page 12 of 21 07/06/19 f

 Digital Library Management System

3.3 Use Cases

Use cases are basically designed to explain which things will be interacting with
the system. It will also explain the different functionalities graphically. Given below is
the different terms of use case diagram that will help understand the diagram to the reader
of this document.

3.3.1 Administrator

SRS Document 1.0 Page 13 of 21 07/06/19 f

 Digital Library Management System

3.3.2 User

SRS Document 1.0 Page 14 of 21 07/06/19 f

 Digital Library Management System

3.5 Non-Functional Requirements

3.5.1 Performance
System must be reliable display error message if unable to request process proper.

3.5.2 Reliability
The system design is so simple of database system of digital library system.

3.5.3 Availability
The system will not available until in running condition.

3.5.4 Security
Authorize or registered user can access this system. Detail about user is secure.

3.5.5 Maintainability
No maintenance is required for database.

3.5.6 Portability
The system is not portable because the database is not shareable.

SRS Document 1.0 Page 15 of 21 07/06/19 f

 Digital Library Management System

4. Analysis Models
4.1 Sequence Diagrams

SRS Document 1.0 Page 16 of 21 07/06/19 f

 Digital Library Management System

4.2 Data Flow Diagrams (DFD)

SRS Document 1.0 Page 17 of 21 07/06/19 f