PROGRAM: 1

1.1OBJECTIVE 1.2THEORY 1.3 PROCEDURE 1.4 OUTPUT

1.1 OBJECTIVE: Prepare a SRS document in line with the IEEE recommended
standards.

1.2 THEORY: An SRS is basically an organization's understanding (in writing) of a customer or

potential client's system requirements and dependencies at a particular point in time (usually)
prior to any actual design or development work. It's a two-way insurance policy that assures that
both the client and the organization understand the other's requirements from that perspective at
a given point in time.
Well-designed, well-written SRS accomplishes four major goals:
1. It provides feedback to the customer.
2. It decomposes the problem into component parts.
3. It serves as an input to the design specification.
4. It serves as a product validation check.

The basic issues that the SRS shall address are the following:

1 Functionality. What is the software supposed to do?

2 External interfaces. How does the software interact with people, the system’s hardware,
other hardware, and other software?
3 Performance. What is the speed, availability, response time, recovery time of various
software functions, etc.?
4 Attributes. What is the portability, correctness, maintainability, security, etc.
considerations?

1.3 PROCEDURE:

IEEE Standard SRS Template

1. Introduction
1.1. Purpose
1.2. Scope
1.3. Definitions, acronyms & abbreviations
1.4. References
1.5. Overview
2. Overall description
2.1.Product perspective
2.1.1. System interfaces
2.1.2. User interfaces
2.1.3. Hardware interfaces
2.1.4. Software interfaces
2.1.5. Communications interfaces
2.1.6. Memory constraints
2.1.7. Operations
 2.1.8. Site adaptation requirements
2.2. Product functions
2.3. User characteristics
2.4. Constraints
2.5. Assumptions and dependencies
2.6. Apportioning of requirements
3. Specific Requirements
3.1 External interface requirements
3.1.1 User interfaces
3.1.2 Hardware interfaces
3.1.3 Software interfaces
3.1.4 Communication interfaces
3.2 Specific requirements
3.2.1 Sequence diagrams
3.2.2 Classes for classification of specific requirements
3.3 Performance requirements
3.4 Design constraints
3.5 Software system attributes
3.5.1 Reliability
3.5.2 Availability
3.5.3 Security
3.5.4 Maintainability
3.6 Other requirements
4. Supporting information
4.1 Table of contents and index
4.2 Appendixes

Note: History of versions of this document with author/contributor info may be included before
the main sections of the document.

1.4 OUTPUT:

SAMPLE SRS FOR LIBRARY MANAGEMENT SYSTEM

1.0 PROBLEM DEFINITION

The library management system is software, which automates the job of a librarian.
1.1 The user can inquire about the availability of a book in which he can search by
entering the author’s name or by entering the title of the book.
1.2 The user can borrow a book. He must provide the username and the card number,
which is unique and confidential to each user. By confirming the authenticity of a
user, the library management system provides information about the number of
books already borrowed by the user and by referring to the database whether the
user can borrow books or not. The library management system allows the user to
enter the title and the author of the book and hence issues the book if it is available.
1.3 By entering the user details and the book details the user can return the borrowed
book.
2.0 SYSTEM REQUIREMENT SPECIFICATION

2.1 INTRODUCTION

2.1.1 Purpose
2.1.1.1 The purpose of this SRS is to describe the requirements involved
in developing a Library management system.
2.1.1.2 The intended audience is any person, who wants to inquire,
borrow and return the books.
2.1.2 Scope
2.1.2.1 The product is titled Library Management System.
2.1.2.2 The product will perform the following tasks
2.1.2.2.1 Enquire about the availability of books.
2.1.2.2.2 Borrow books if available.
2.1.2.2.3 Return the borrowed books.
2.1.3 Definitions, Acronyms and Abbreviations
2.1.3.1 DDBMS – Database Management System.
2.1.4 References
2.1.4.1 IEEE standard 830-1998 recommended practice for Software Requirements
Specifications-Description.
2.1.5 Overview
2.1.5.1 The SRS contains an analysis of the requirements necessary to help easy design.
2.1.5.2 The overall description provides interface requirements for the Library
Management System, product perspective, hardware interfaces, software
interfaces, communication interface, memory constraints, product functions,
user characteristics and other constraints.
2.1.5.3 Succeeding pages illustrate the characteristics of typical naïve users accessing
the system along with legal and functional constraints enforced that affect
Library Management System in any fashion.

2.2 THE OVERALL DESCRIPTION

2.2.1 Product perspective
2.2.1.1 Hardware interfaces
2.2.1.1.1 Hard disk: The database connectivity requires a hardware
configuration that is on-line. This makes it necessary to have a fast
 database system running on high rpm hard disk permitting complete
data redundancy and back-up systems to support the primary goal of
reliability.
2.2.1.1.2 The system must interface with the standard output devise, keyboard
and mouse to interact with this software.
2.2.1.2 Software interfaces
2.2.1.2.1 Back End: MS-Access 2007
2.2.1.2.2 Front End: Microsoft Visual Basic 6.0
2.2.1.3 Memory Constraints
2.2.1.3.1 No specific constraints on memory.
2.2.1.4 Operations
2.2.1.4.1 The software allows three modes of operations
Enquire about the availability and status of books.
By extracting the username and password the software allows
the user to borrow a maximum of three books.
By extracting the username and password the software allows
the user to return the borrowed books.

2.2.2 Product Functions

2.2.2.1.1 Enquire about the availability and status of books.
2.2.2.1.2 Search the availability of book by entering the title of the book.
2.2.2.1.3 Search the availability of book by entering the author of the book.
2.2.2.1.4 The software validates the authentic user by extracting their user name
and password.
2.2.2.1.5 After the validation of the user software allows the user to borrow a
maximum of three books based on the number of books which where already
borrowed.
2.2.2.1.6 After the validation of the user software allows the user to return the
books, which where borrowed.
2.2.3 User characteristics
2.2.3.1 The intended users of this software need not have specific knowledge as
to what is the internal operation of the system. Thus the end user is at a
high level of abstraction that allows easier, faster operation and reduces
the knowledge requirement of end user
2.2.3.2 The Product is absolutely user friendly, so the intended users can be the
naïve users.
2.2.3.3 The product does not expect the user to possess any technical background.
 Any person who knows to use the mouse and the keyboard can
successfully use this product.

2.2.4 Constraints
2.2.3.1 The user has a unique username and password, there are no options to
retrieve a password or username in case it is forgotten or lost hence the
user is required to remember or store the username and password.

2.3 SPECIFIC REQUIREMENTS

2.3.1 Logical Database Requirements

2.3.1.1 The system should contain databases that include all necessary information for the
product to function according to the requirements. These include relations such as
user details and book details.
2.3.1.2 The user details refer to the information such as name, card number, no. of books
borrowed, the title and the name of the author of the books that were borrowed.
2.3.1.3 The book details refer to the information such as the title of the book, author
availability status and the number of copies that is available.
2.4 FRONT – END DESCRIPTION
The library management system is automated library system where the user can
search for the book by either entering the details of the book or the author’s name.
By entering the username and the password the software, by checking the number of
books that are already borrowed enables us to borrow a maximum of three books.
And by entering the username and password (card number), which is unique, the user
can return the books.
2.5 BACK – END DESCRIPTION
The library management system consists of two tables. One contains the student
details such as the name, card number that is the password, title and the author of the
three books, which could be borrowed. The book details consist of the title of the
book, number of copies, author and the availability status.
2.6 DATA STRUCTURES

2.6.1.
2.5 BOOK DETAILS
FIELD NAME TYPE CONSTRAINTS
REGISTER_NO NUMBER NOT NULL
BOOK_ID NUMBER NOT NULL
ISSUE_DATE DATE/TIME
RETURN_DATE DATE/TIME
BOOK_NAME TEXT

2.6.2. STUDENT DETAILS

FIELD NAME TYPE CONSTRAINTS
REGISTER_NO NUMBER NOT NULL
FNAME TEXT NOT NULL
LNAME TEXT
GENDER TEXT
DEPT TEXT
EMAIL TEXT
PASSWORD TEXT

NO_OF_BOOKS NUMBER