Srs of Lms

Download as doc, pdf, or txt
Download as doc, pdf, or txt
You are on page 1of 8

SOFTWARE REQUIREMENTS

SPECIFICATION
FOR

LIBRARY MANAGEMENT SYSTEM


CREATED BY : PRIYANKA
KHURANA

ITB(G1)

9 MAY 2014

Table of Contents
Table of Contents............................................................................................... ii
1. Introduction.................................................................................................. 1

1.1 Purpose............................................................................................................ 1
1.2 Scope............................................................................................................... 1
1.3 Definition, Aggregation and Abbreviation.........................................................1
1.4 References........................................................................................................ 1
1.5 Overview.......................................................................................................... 2
2. Overall Description.......................................................................................2

2.1 Product Perspective.......................................................................................... 2


2.2 Product Function............................................................................................... 2
2.3 User Characterstics.......................................................................................... 2
2.4 Assumption and Analysis.................................................................................. 2
3. Specific Requirements...................................................................................3

3.1 External Diagram............................................................................................. 3


3.2 Diagrams.......................................................................................................... 3

INTRODUCTION
PURPOSE
The library management system maintains the information about various books available in
the library. The LMS also maintains records of all the students, faculty and employees in the
university. These records are maintained in order to provide membership to them.

SCOPE
The proposed LMS must be able to perform the following functions

Issue of login ID and password to system operators

Maintain details of books available in the library

Maintain details of the student in the university to provide student membership

Issue books

Reserve books

Generate reports

The donts of LMS are:

Periodical section is not covered

Book bank is not covered

Records of digital books are not available

Benefits of LMS are:

Easy searching of books

Efficient issue and return of books

Printing of reports

DEFINITION,

ACRONYMS AND ABBREVIATIONS

SRS: Software Requirement Specification

LMS: Library Management System

RAM: Random Access Memory

Student: any candidate admitted in a program offered by a school

REFERENCES

IEEE standard for software test documentation

Software Engineering book by Genius publications

OVERVIEW
The subsection of the SRS gives the overview of the software system. Explains what the rest of
SRS contains and also gives details about the organization of the SRS document

OVERALL DESCRIPTION
The LMS maintains records of books in the library and membership detail of students, faculty
and employees in the university. It is assumed that approved books have already been
purchased by acquisition section. It is also assumed that the student has already been
admitted in the university for a specific program.
The administrator will have to maintain the following information:

Bok details

Student membership details

Faculty and employee membership details

PRODUCT PERSPECTIVE
The LMs shall be developed using client/ server architecture and will be compatible with Microsoft
windows OS. The front end of the system will be developed using visual basic 2010 and the back
end wil be developed using Ms SQL server
Front
end
client
application(isu
ue,return and
reporting
facility)

Back
end
database

2.1.1USER INTERFACE
The LMs will have the following user friendly and menu driven interfaves:

Login: to allow the entry of only authorized user

Book details

Student membership details

Issue and return books

Reserve books

queries

2.1.2 HARDWARE INTERFACES

Proper screen resolution

printer support

computer system will be in the network environment

2.1.3 SOFTWARE

INTERFACE

MS window operating system

Microsoft visual basic

SQL server

2.1.4C OMMUNICATION INTERFACES


This subsection specifies the various interfaces to communicate such as LAN , Protocol etc.

2.1.5 MEMORY CONSTRAINTS


Any constraints related to primary and secondary memories are specified. at least 512 Mb
memory RAM and 500 MB space of hard disk will be required to run the software.

PRODUCT FUNCTION
A summary of major functions that the LMS shall perform includes:

A login facility for enabling only authorized user

The system DEO will be able to add, modify, delete or view book, student, faculty and
login information

The system administrator will be able to issue, bring back, and reserve books

The library staff will be able to generate various reports from the LMS.

USER CHARACTERISTICS
Qualification: at least matriculation and comfortable with English.
Experience: should be well versed about the processes of university library

Technically qualified

ASSUMPTIONS

AND ANALYSIS

The acquisition section of the library will provide the list of books purchased by the library.
The academic section will provide the list of admitted student.
The login ID and password must be created by the system administrator

3 SYSTEM REQUIREMENTS
EXTERNAL

INTERFACES

This section contains the software requirements in detail along with the various forms to be
developed

Issue book
This form will be accessible only to the system administrator and library staff

You might also like