Software Requirements Specification

for

Library Management System

Version 1.0 approved

Prepared by

Adrees Shahbaz 20011598-051

Ali Usman 20011598-052

Gullam Muhayudin Tayyab 20011598-055

Copyright © 1999 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document.
 University of Gujrat

Feb 26, 2022

Copyright © 1999 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document.
Software Requirements Specification for <Project> Page iii

Table of Contents
1. Introduction ..............................................................................................................................1
1.1 Purpose ........................................................................................................................................ 1
1.2 Document Conventions ............................................................................................................... 1
1.3 Intended Audience and Reading Suggestions.............................................................................. 1
1.4 Product Scope .............................................................................................................................. 1
1.5 References ................................................................................................................................... 2
2. Overall Description ..................................................................................................................2
2.1 Product Perspective ..................................................................................................................... 2
2.2 Product Functions ........................................................................................................................ 3
2.3 User Classes and Characteristics ................................................................................................. 3
2.4 Operating Environment ............................................................................................................... 4
2.5 Design and Implementation Constraints...................................................................................... 4
2.6 User Documentation .................................................................................................................... 4
2.7 Assumptions and Dependencies .................................................................................................. 4
3. External Interface Requirements ...........................................................................................5
3.1 User Interfaces ............................................................................................................................. 5
3.2 Hardware Interfaces..................................................................................................................... 5
3.3 Software Interfaces ...................................................................................................................... 5
4. System Features .......................................................................................................................6
4.1 Functional Requirements ............................................................................................................. 6
5. Other Nonfunctional Requirements .......................................................................................7
5.1 Performance Requirements.......................................................................................................... 7
5.2 Safety Requirements .................................................................................................................... 7
5.3 Security Requirements................................................................................................................. 7

Revision History
Name Date Reason For Changes Version
Software Requirements Specification for <Project> Page 1

1. Introduction

1.1 Purpose

The purpose of this project is to provide a friendly environment to maintain the details of
books and library members. The main purpose of this project is to maintain easy
circulation system using computers and to provide different reports.

1.2 Document Conventions

▪ For Main Title

Font size is 14. Font face is Time New Roman & Font style is Bold.
▪ For Body
Font size is 12. Font face Time New Roman
▪ NFR refers Non-functional requirements
▪ FR refers Functional requirements
▪ OS refers Operating System.

1.3 Intended Audience and Reading Suggestions

This SRS is designed and intended for the developers of the system, UE Librarians,
andadministration of as well the project managers, designers, and testers.
Project managers are responsible for planning, organizing, and directing the
completion of specific projects for an organization while ensuring these projects are
on time,on budget, and within scope.
The designers will use this SRS as a basis for creating the system’s design. The
designers will continually refer back to this SRS to ensure that the system they are
designingwill fulfil the customer’s needs.
The developers will use this SRS as a basis for developing the system’s functionality.
The testers will use this SRS to derive test plans and test cases for each
documentedrequirement.

1.4 Product Scope

The system enables to perform the following functions:

• Keep the proper Records of Available and Issued Books.

Software Requirements Specification for <Project> Page 2

• Modify the record of a Book

• Manage the massive amount of Data generated by libraries.
• Record every Transaction in a Computerized System
• Improved and optimized service

1.5 References

https://www.google.com/videohp

https://www.libsys.co.in/products/library-solutions/library-management-system

2. Overall Description

2.1 Product Perspective

The proposed Library Management System will take care of the current book detail at
any point of time. The book issue, book return will update the current book details
automatically so thatuser will get the update current book details.

The system suffered from the following Problem before this type of project:

• This has led to inconsistency and inaccuracy in the maintenance of data.

• The data, which is stored on the paper only, may be lost, stolen or destroyed
due to natural calamity like fire and water.
• The existing system is sluggish and consumes a lot of time causing
inconvenience to customers and the staff. Due to manual nature, it is difficult
to update, delete, add or view the data.

This project is proposed with the followings:

• The computerization of the reservation system will reduce a lot of paperwork

and hencethe load on the administrative staff.
• The machine performs all calculations. Hence chances of error are nil.
• The passenger, reservation, cancellation list can easily be retrieved and any required
addition, deletion or updating can be performed.
Software Requirements Specification for <Project> Page 3

2.2 Product Functions

The Online Library System provides online real time information about the books
available in the Library and the user information. The main purpose of this project is
to

• Reduce the manual work.

• Managing Book issues, returns, calculating/managing fine,
• Generating various reports for Record-Keeping according to end user requirements.
• The Librarian will act as the administrator to control members and manage books.
• The member's status of issue/return is maintained in the library database.
• The member's details can be fetched by the librarian from the database as
and whenrequired.
• The valid members are also allowed to view their account information.

2.3 User Classes and Characteristics

The system provides different types of services based on the type of users

1. Member/ Librarian
2. Students
3. administration

The features that are available to the Librarian are:

• A librarian can issue a book to the member

• Can view the different categories of books available in the Library
• Can view the List of books available in each category
• Can add books and their information to the database
• Can edit the information of existing book
• Can check the report of the existing books
• Can check the report of the issued books.
Software Requirements Specification for <Project> Page 4

2.4 Operating Environment

The product will be operating in windows OS. The Library Management System is a
website and will operate in all famous browsers. i.e., Google Chrome, IE, and
Mozilla Firefox. The hardware configuration includes Hard Disk: 40 GB, Monitor:
15" Color monitor,Keyboard: 122 keys.

2.5 Design and Implementation Constraints

Any update regarding the book from the library is to be recorded to have update
& correctvalues, and any fine on a member should be notified as soon as possible
and should be correctly calculated.

2.6 User Documentation

The User documentation will include the following:

• User will be able to download User Manual from website's help section.
• Video tutorials will be available for further guidance.
• Help Button will be available everywhere.

2.7 Assumptions and Dependencies

• The coding should be error free.

• The system should be user-friendly so that it is easy to use for the users.
• he information of all users, books and libraries must be stored in a
database that isaccessible by the website.
• The system should have more storage capacity and provide fast
access to thedatabase.
• The system should provide search facility.
• The Library System is running 24/7.

The dependencies are:

• Based on listing requirements and specification the project will be

developed.
• The end users (admin) should have proper understanding of the product
Software Requirements Specification for <Project> Page 5

and run.
• The system should have the general report stored.
• The information of all the users must be stored in a database that is
accessible by thesystem.

3. External Interface Requirements

3.1 User Interfaces

The software provides good graphical interface for the user and the administrator can
operate on the system, performing the required task such as create, update, viewing
the details of the book. User interference Management system are as follow:
• Administrator
• Students
• Librarian

3.2 Hardware Interfaces

The IEEE 830-1998 standard defines 'Hardware Interfaces' as. 'the logical
characteristics of each interface between the software product and the hardware
components of the system
• Operating system window.
• Hard disk:40 GB.
• RAM: 256 MB.
• Processor: Pentium(R)Dual-core CPU.

3.3 Software Interfaces

• This software package is developed using java as front end which is

supported by sunmicro system.
• Microsoft SQL Server as the back end to store the database.
• Operating System: Windows XP, windows 7 and higher versions.
• Language: Java Runtime Environment, Net beans 7.0.1 (front end)
• Database: MS SQL Server (back end)
Software Requirements Specification for <Project> Page 6

4. System Features
The users of the system should be provided the surety that their account is secure.
This is possible by providing:
• User authentication and validation of members using their unique member ID.
• Proper monitoring by the administrator which includes updating account
status, showing a popup if the member attempts to issue number books that
exceed the limit provided by the library policy, assigning fine to members
who skip the date of return.
• Proper accountability which includes not allowing a member to see other
member's account. Only administrator will see and manage all member
accounts.

4.1 Functional Requirements

REQ-1: Only authentic user must have the access to the system.
REQ-2: Only the user must be able to provide the information related to the library.
REQ-3: Provide the information regarding books.
REQ-4: Search for the required books from database.
REQ-5: Add new book to the database.
REQ-6: Update the number of books in database.
REQ-7: Enter data of issued book in Database.
REQ-8: Information of returned books.
REQ-9: User must have the knowledge about the no of copies of a book.
REQ-10: Same Id’s for 2 or more books shall not be allowed.
REQ-11: User must check if the book is available or not before issuing.
REQ-12: User must enter issue and return date in database.
REQ-13: The user must know the number of shelves in the library.
REQ-14: System shall allow to view record.
REQ-15: System shall allow to update records.
REQ-16: System shall allow to delete records
Software Requirements Specification for <Project> Page 7

5. Other Nonfunctional Requirements

5.1 Performance Requirements

• The proposed system that we are going to develop will be used as the Chief
performance system within the different campuses of the university which
interacts with the university staff and students. Therefore, it is expected that
the database would perform functionally all the requirements that are
specified by the university.
• The performance of the system should be fast and accurate. Library
Management System shall handle expected and non-expected errors in ways
that prevent loss in information and long downtime period. Thus, it should
have inbuilt error testing to identify invalid username/password
• The system should be able to handle large amount of data. Thus, it should
accommodatehigh number of books and users without any fault

5.2 Safety Requirements

• The database may get crashed at any certain time due to virus or
operating systemfailure.
• Therefore, it is required to take the database backup so that the database is not lost.
• Proper UPS/inverter facility should be there in case of power supply failure.

5.3 Security Requirements

System will use secured database

• Normal users can just read information, but they cannot edit or modify
anything except their personal and some other information.
• System will have different types of users and every user has access constraints
• Proper user authentication should be provided
• No one should be able to hack users' password
• There should be separate accounts for admin and members such that no
member canaccess the database and only admin has the rights to update the
database.