Software Requirement Analysis

SOFTWARE REQUIREMENT ANALYSIS DOCUMENT FOR <THE PROJECT NAME>

Software Requirement Analysis 1. Introduction

1.1. BACKGROUND

Background on the subject or the field of project

1.2. OVERALL DESCRIPTION Describe about how the current system is working or the state of the current system. FIGURE OF THE CURRENT SYSTEM ARCHITECTURE Describe how the new system will be different from the existing system or what kind of improvements would be required in the existing system.

2. GLOSSARY
List of Figures: Acronyms: Terminology:

3. INFORMATION FLOW 3.1.

DATA FLOW DIAGRAM

FIG2. Data Flow Diagram of Current System

4. FUNCTIONAL DESCRIPTION
4.1. 4.2. USER REQUIREMENTS DEFINITION FUNCTIONAL PARTITIONING FIG3. USE CASE DIAGRAM

5. INTERFACES
5.1. HARDWARE INTERFACE

Specify what additional hardware interfaces are required besides the host device
5.2. USER INTERFACE

Specify what kind of user interfaces are required by the end user
5.3. INTERFACE WITH OTHER SYSTEM

Specify if there is need of interfacing with additional system or software for the proper functioning of the system 6. SYSTEM REQUIREMENTS SPECIFICATION
The new system provides: Facility to store contact information along with birthday Facility to add birthday reminder automatically

7. NON-FUNCTIONAL REQUIREMENTS
Non-functional requirements desired for this system are: Efficient rescheduling the day notes that includes pre-pone and postpone

Software Requirement Analysis

Vibration during alarm signals

8. VALIDATION CRITERIA
8.1. PERFORMANCE BOUNDS

Specify the performance criteria that the required system should meet
8.2. CLASS OF TESTS Specify the testing mechanisms to be carried out for the system to verify the system and validate the requirements