Software Requirements

Specification
FOR
LIBRARY MANAGEMENT SYSTEM
Version 1.1

Prepared by
Ali Hyder
&
Ijaz Hussain Shah
30th DEC, 2018
 Revision History
Version Description Author Date
1.0 Initial Release/ Ali Hyder 30th Dec, 2018
First Release Ejaz Hussain Shah
1.1 Some correction Ali hyder 31th Dec, 2018
Ejaz Hussain Shah

LIBRARY MANAGEMENT SYSTEM (LMS)

1. Introduction
Our library management system is a desktop application which will be implemented in
library. It helps the members as well as the staff of the library for library maintenance. It
records the detail of cataloging with in no time an immense record is stored. It reduces the
human efforts with single click only.
Previously manual work, manual cataloging and staff was required to maintain the
record of the books with issue and receipt register which was time, energy and labour
oriented work.
The LMS finds a solution to reduce the human efforts. The major goal of the system
is to maintain the book and member record and provide a better working environment for
the staff to work in easy and effective way so that they can save time and work in more
efficient way.

Our library Management System is a desktop application which wiil be implemented in

library.
LMS reduces the manual work and assist the users for record tracking. It maintains the
book record, book transaction and members detail etc. Before the introduction of LMS
manual cataloging system was invouged which was a time consuming and labour oriented.
 1.2 Scope
The functional scope of the system has the following main features:
 To record details of Books
 To record information of the staff
 To record information of the books transaction
 Recording the information of Members.

The system has various modules:

 Security Management Form
 Members Management Form
 Staff Management Form
 Book Management Form
 Book Transaction Form
 Publisher Management Form
 Report Form
 Security Management Module will provide the access to the system according to the
privilages of the member. This will used to authenticate the member to access the
system.
 Member Management Module will help to manage the member information i.e. adding
new Member, updating Member & searching Member.
 Staff Management Module will help to manage the staff information i.e. adding new staff
member, updating & searching staff member.
 Book Management Module will help to manage the books catalog i.e. adding new Books,
updating & searching Books.
 Books Transaction Module will help to manage the transactions of book i.e. issue books,
return books & Due Date.
 Publisher Management Module will provide the access to librarian to add, update and
search Publisher information
 Report Module will provide to generate different kind of reports like member report,
staff report.
Terms/Abbreviation Descriptions
LMS Library Management System
GUI Graphical User Interface
RUP Rational Unified Process
C# Programming Language
VISIO Designing Tool
LIB Librarian
UML Unified Modeling Language
1.3 References
Persons involved
 Ali Hyder
 Ijaz Hussain Shah
 M. Aneeq Ul Hassan
Websites
 neveonProjects.com

1.4 Over view

This document contains the requirements of the Library Management System
(LMS). All the functional Requirements are collected by the personal visit to the “Library
Management System”
Librarian of the library Mr. Ahmed Ali provided the requirements and functionalities by
himself
1.5 System Main Features
 Security Management
 Members Management
 Staff Management
 Books Management
 Books transactions
 Publisher Management
 Report
 2. FUNCTIONAL REQUIRMENT

2.1 Security Management

2.2.1. Process Login

Users(staff/member) can enter the system by entering the

SRS-1
username and password
SRS-2 The user name should be Unique

Authentication should be provided and the suitable access of the

SRS-3
system should be given according to privileges

2.2.2. Change Password

SRS-4 Users can change the password by conforming the new password

2.2.3. Forgot Password

SRS-5 If users forgets password, no matter he/she can access the system by
entering the user name and then write the password again.

2.2 Members Management

2.2.1 Add Member

SRS-6 LIB can add a new member into the system

SRS-8 Member’s documents should be proper and legal

SRS-9 System should save this information

2.2.2 Search Member

SRS-9 LIB can search for Member information

System should give facility of searching Member information on the

SRS-10
basis of ID number

SRS-11 System should find the result based on search criteria

SRS-12 System should display search information

2.2.3 Update Member Information

SRS-13 The Member to be updated will be searched first

The information of the Member being updated should be according

SRS-14
to the standard

SRS-15 LIB should be able to update the Member’s information

SRS-16 System should update this information

2.2.4 Generate Member Information

System should generate reports of the Member by ID, Name, Status

SRS-16
they can be viewed by the DEO of the LMS on runtime
2.3 Books Management
2.3.1 Add Books

SRS-17 LIB can add a new book into the system

Book should have following attributes ID, name, Eddition, Author

SRS-18
and Published by.

SRS-19 Book should be proper and legal

SRS-20 System should save this information

2.3.2 Search Books

SRS-21 LIB can search for Book information

System should give facility of searching Book information on the

SRS-22
basis of ID number and name of book

SRS-23 System should find the result based on search criteria

SRS-24 System should display search information

2.3.3 Update Books

SRS-25 The Book to be updated will be searched first

The information of the Book being updated should be according to

SRS-26
the standard

SRS-27 LIB should be able to update the Book’s information

SRS-28 System should update this information

2.3.4 Generate Books Information

System should generate reports of the Books by ID, Name. They can
SRS-29
be viewed by the LIB of the LMS on the run time.
2.4 Book Transactions
2.4.1 Issue Books

SRS-30 System must be able to enter issue information in database

System must be able to search if book is available or not before

SRS-31
issuing books
System should be able to enter issue and return date when issuing
SRS-32
the book

2.4.2 Return Books

SRS-33 System should be able to update number of books.

SRS-34 System should be able to enter return date of books.

System should be able to calculate fine if date expires or condition

SRS-35
of the book is not so good.

2.4.3 Check For Reservation

System should be able to check that the due date of book which is
SRS-36
issued to the member.

2.5 Staff Management

2.5.1. Add Staff Member

SRS-37 LIB can add a new Staff member into the system

Staff member should have following attributes ID, name, father

SRS-38
name, cnic, Gender, Designation, Email ID, Contact number,address

SRS-39 Staff member should not be able to issue books, except LIB.

SRS-40 System should save this information

2.5.1 Search Staff Member

SRS-41 LIB can search for Staff information

System should give facility of searching Staff information on the

SRS-42
basis of ID number and name of person

SRS-43 System should find the result based on search criteria

SRS-44 System should display search information

2.5.2 Update Staff Member

SRS-45 The Staff person to be updated will be searched first

The information of the Staff person being updated should be

SRS-46
according to the standard

SRS-47 DEO should be able to update the Staff person’s information

SRS-48 System should update this information

2.5.3 Generate Staff Member

System should generate reports of the Staff persons by ID, and

SRS-49
Name. They can be viewed by the DEO of the LMS on the run time.

2.6. Publisher Management

2.6.1. Add Publisher

SRS-50 LIB can add a new publisher into the system

Publisher should have following attributes ID, name,
SRS-51 Father name, address, Gender, publish book year, publish book
Email ID, Contact number.,address.
SRS-53 System should save this information
2.6.2. Search Publisher

SRS-54 LIB can search for Publisher information

System should give facility of searching Publisher information on the

SRS-55
basis of ID number and name of publisher.

SRS-56 System should find the result based on search criteria

SRS-57 System should display search information

2.6.3. Update Publisher

SRS-58 The publisher to be updated will be searched first

The information of the publisher being updated should be according

SRS-59
to the standard

SRS-60 LIB should be able to update the Staff person’s information

SRS-61 System should update this information

2.6.4. Generate Publisher

System should generate reports of the publisher by ID. They can be

SRS-62
viewed by the LIB of the LMS on the run time.

2.6 Report

System should generate report of the Staff person and Members of

SRS-63 the librarians by ID. They can be viewed by the librarian, manager of
the LMS
3. Non-Functional Requirements

1. Security
The system requires the users to identify themselves by using login-id and
password. Any user who uses the system shall have a login-id and a password

2. Usability
With proper guidance and use of manual the required training time for a normal
users will not be more than one week

3. Reliability
Availability The system facility will be available to its users for 24 hours

Bugs or defect rate Very little

Our system will generate appropriate exceptions and will
Robustness
handle those exceptions effectively
The system will generate accurate results and will behave
Accuracy
according to the User Requirements
Our system will be according to all the requirements
Correctness collected. All the requirements will be met to the User
Requirements

4. Performance
 The LMS has a simple GUI, which is self-explanatory and user friendly
 The lists, reports and results generated by the system will not take more than
2-3 sec
 Responses to queries shall take no longer than 4-5 sec to load onto the screen
after the user submits the query
 The LMS shall display confirmation messages to user within 1-2 sec after the
user submits information to the system. In other words robustness is
maintained
 Resources Required
Hardware Minimum Recommended
Processor 1 Core 2 GHz Dual Core 2+ GHz
RAM 1 GB 2 GB
Hard-drive 20 GB As Required
5. Design Constraints
RUP will be used for the design purposes and UML will be used for the diagrams
in MS Visio. C# language will be used for the development and for the database side
Microsoft SQL server will be used. So, we must be familiar with these constraints

6. User Help/ manuals

Detailed System manuals are given to the system users and one week training
session will be held to ensure that the users of the system understands the system fully
and can get the maximum benefit from the system

7. External Interface Requirements

7.1. User Interfaces
The user interfaces will be friendly because they will be made after discussion
with the end users. The software will be interactive and self-explanatory

7.2. Hardware Interfaces

The system will interact with the printer if the user wants to print the reports

Hardware Use Version

Printer As Required As Required

7.3. Software Interfaces

Software USE Version

Windows Operating System XP,7,8,10

MS Visual Studio (C#) Front End 2010+

MS SQL Server Backend Latest is Better

Microsoft Visio For Modeling 2010+

8. Licensing requirements
This system will be developed according to the Library oriented nature of LMS,
and it is licensed by LMS.