SOFTWARE REQUIREMENT SPECIFICATION

Size: px

Start display at page:

Download "SOFTWARE REQUIREMENT SPECIFICATION"

Gervase Walton
5 years ago
Views:

1 SOFTWARE REQUIREMENT SPECIFICATION

2 AIM The aim of the experiment is to prepare and document the Software Requirements Specification for the project Library Management System

3 1. INTRODUCTION 1.1 Purpose 1.2 Scope 1.3 Definition, Acronyms, and Abbreviations 1.4 Reference 1.5 Overview

4 2.Overall Description 2.1 Product Perspective System Interfaces User Interfaces Hardware Interfaces software Interfaces Communication Interfaces Memory Interfaces Operations

5 Cont Site Adaptation Requirements 2.2 Product Functions 2.3 User Characteristics 2.4 Constraints 2.5 Assumptions and Dependencies

6 3. Specific Requirements 3.1 External Interfaces Requirements User Interfaces Login Screen Main Menu Screen Book Detains Screen Book Issue/Receive Screen Hardware Interfaces Software Interfaces Communication Interfaces

7 3.2 Software Product Features Book Details Maintenance Student Details Maintenance Book Issue Maintenance Book Issue/Receive Report Generation Report Generation User Account Information Maintenance

8 Cont 3.3 Performance Requirements 3.4 Design Constraints 3.5 Software System Attributes 3.6 Logical Database Requirements 3.7 Other Requirements

9 1. Introduction This document aim to defining the overall software requirements for Library Management system. The final product will entirely depend on this documentation.

10 Purpose This specific documentation describes the capabilities that will be provided by the software application Library Management System. It also defines the required constraints of the system and it is useful for developrment team, testing and end users of the product

11 Scope Problem statement

12 Definitions Acronyms and Abbreviation (i) LMS- Library Management System

13 Reference (i) IEEE Recommended practice for SRS- IEEE Standard (ii) Object Oriented Analysis and design

14 Overview The SRS document gives an idea about the requirements and features of the system.

15 Overall Description The system LMS is developed to automate the Library Management in Colleges.

16 Product Perspective The application will be a window-based, independent software product.

17 None System Interfaces

18 User Interfaces The following are the screen provided in the application. Login Screen. Student details. Book issue Search

19 Hardware Interface Minimum Requirements of the system. Processor-? Memory-? Monitor-? Hard Disk-5GB CD RW Drive-52X USB Port] Printer

20 Software Interfaces Operating system-? Front End Tool? Back End Tool-? UML Software- Star UML5.0

21 Communication Interfaces Not required

22 Memory Constraints Minimum system requirements

23 Operation LMS Insert Delete Updation

24 Site Adaptation Requirements The stand alone system must able to support the hardware and software interfaces.

25 Product Functions A summary of major functions that the software will perform.

26 User Characteristics Librarian- he must only have the information about the books and student details. Student- he must know how to operate the software. He must have a technical knowledge to handle the system.

27 Constraints The developed system is meant for standalone system only. So it cannot be used for on line management.

28 Assumptions and Dependencies The book details in the database entirely depend upon the information provided in books that are available in the Library. LMS system works on the assumption that the Student must come to the Library to take or return his/her book of their own interest.

29 Specific Requirements This section contains the software requirements to a level of detail sufficient to enable designers to design the system and tester to test the system.

30 External Interface Requirements USER INTERFACES Login Screen: Main Menu Screen: Book Details Screen: Student Details Screen:

31 Login screen Username: String of the alphabets of length up to 8 Password: String of Alphabets of Length up to 6 Role: Two types of role will be there- Administrator and user.

32 Book Details Screen Book_Id: Numeric, 4 Digit No Book_ Name: Alphabetic, Up to a length of 50 characters Department :Alphabetic,up to a length of 50 characters Publisher: Edition: Cost:

33 Hardware Interface Same as that defined in 2.1.3

34 Software Interfaces Same as that defined in 2.1.4

35 Communication Interfaces Not Required

36 Software Product features Book Details maintenance. Student details maintenance Book Issue Maintenance

37 Book Details Maintenance Description Validity checks Sequencing information Error Handling/Response to abnormal situations

38 Student details maintenance Description Validity checks Sequencing information Error Handling/Response to abnormal situations

39 Book Issue Maintenance Description Validity checks Sequencing information Error Handling/Response to abnormal situations

40 Book Issue /Receive Generation Report Generation i) Book details Report ii) Students Details Report

41 None Performance requirements

42 None Design Constraints

43 Software System Attributes Security Usability

44 Logical Database Requirements The following information will be placed in the database Book Details: Student Details: Book Issue/Receive Details:

45 None Other Requirements

46 Result The Software Requirements Specification for the project Library Management System has been analyzed and documented Successfully.

Delimited. Interfaced. Readable. Modifiable. Verifiable. Prioritized* Endorsed

Delimited. Interfaced. Readable. Modifiable. Verifiable. Prioritized* Endorsed 15 quality goals for requirements Justified Correct Complete Consistent Unambiguous Feasible Abstract Traceable Delimited Interfaced Readable Modifiable Verifiable Prioritized* Endorsed Marked attributes