Library Mgmt System

Only available on StudyMode
  • Topic: Requirements analysis, Software requirements, Software Requirements Specification
  • Pages : 10 (2701 words )
  • Download(s) : 328
  • Published : March 9, 2013
Open Document
Text Preview
Software Requirements Specification for Library Management System Table of Contents:
1.0 Introduction
1.1 Purpose 
1.2 Scope of Product 
1.3 Definitions, Acronyms, and Abbreviations 
1.4 References 
1.5 Overview
2.0 General Description
2.1 Product Perspective 
2.2 Product Functions 
2.3  User Characteristics 
2.4 General Constraints 
2.5 Assumptions and Dependencies
3.0  Specific Requirements
3.1  Functional Requirements
3.1.1  User Interface
3.1.1.1  Library user account manage system 
3.1.1.2  Book borrowing system 
3.1.1.3  Book recall system 
3.1.1.4  Search book record
3.1.2  Data Entry
3.1.2.1  Library user account manage system 
3.1.2.2  Book borrowing system 
3.1.2.3  Book recall system 
3.1.2.4  Search book record 
3.1.2.5 Update book database
3.1.3  Report Generation
3.2 Performance Requirements 
3.3 Design Constraints 
3.4 Security Requirements 
3.5 Reliability

1.0 Introduction
1.1 Purpose
This is the Software Requirements Specification (SRS) for the Library Management System.  The purpose of this document is to convey information about the application's requirements, both functional and non-functional, to the reader.  This document provides (a) a description of the environment in which the application is expected to operate, (b) a definition of the application's capabilities, and (c) a specification of the application's functional and nonfunctional requirements. The document is intended to serve several groups of audiences: * First, it is anticipated that the SRS will be used by the application designers.  Designers will use the information recorded here as the basis for creating the application's design. * Second, the client for the project, the library manager in our case, is expected to review this document.  The SRS will serve to establish a basis for agreement between the client and development team about the functionality to be provided by the application. * Third, the application maintainers will review the document to clarity their understanding of what the application does. * Fourth, test planners will use this document to derive test plans and test cases. * Finally, the project manager will use this document during project planning and monitoring.  

1.2 Scope of Product
The purpose of this software development project is to create a new application called: Library Management System.  The client for this project wishes to enter the PC-based LAN environment.  The Library Management System will be PC-base with a LAN, allowing library users to search for books and library staff members to manage the book inventory and user database.  The application will provide the following capabilities:  The application will be access via a LAN on a PC terminal in the Library  Library staff will be able to manage library user accounts including remove, change, and add.  Library staff will be able to manage the book inventory database including remove, change, and add.  The application will record all books that are checked out, checked in, and recalled.  The application will generate reports for administrative purposes.  The application will provide search function on books based on ISBN, subject, title, or author. The project's client has determined that this application will provide the following benefits:  Provide additional flexibility and convenience to the library users.  Provide better reliability and security of the library information.  Provide a more productive environment for the library staff member.  Reduce the cost of the library operations.

1.3 Definitions, Acronyms, and Abbreviations
SRS - Software Requirements Specification. 
PC -  Personal Computer. 
LAN - Local Area Network. 
IEEE - Institute of Electrical and Electronics Engineers. 
ISBN - International Standardized Bin Number.
1.4 References
1. Merlin Dorfman, Richard H. Thayer, "Standards, Guidelines, and Examples on System and software Requirements Engineering", IEEE,...
tracking img
http://www.studymode.com/essays/Library-Mgmt-System-1491049.html
www.studymode.com
crawl=CC-MAIN-2017-22
77419
application/http; msgtype=response
sha1:2GMRTZUYLBIZ3XPKRFWQB2X4EGBU3RIG
<urn:uuid:ffa8f277-5dca-45d0-ab1e-2106f36bcafb>
2017-05-22T16:44:31Z
64.30.136.226
application/xhtml+xml
sha1:4KCWJCEGIK7X5NYWBMA54IVOAM6HK7UG
<urn:uuid:f61be5f9-af46-430c-a12f-a01979fb5a85>
http://www.studymode.com/essays/Library-Mgmt-System-1491049.html
response
<urn:uuid:9f3d4e64-708f-4074-ad04-acb67312b4c3>
robots: classic
hostname: ip-10-185-224-210.ec2.internal
software: Nutch 1.6 (CC)/CC WarcExport 1.0
isPartOf: CC-MAIN-2017-22
operator: Common Crawl Admin
description: Wide crawl of the web for May 2017
publisher: Common Crawl
format: WARC File Format 1.0
conformsTo: http://bibnum.bnf.fr/WARC/WARC_ISO_28500_version1_latestdraft.pdf