Prof.

Debabrata Nath CSE, NITMAS 1

1. Requirements Gathering
2. Requirements Analysis
3. Requirements Problem
4. Requirements Specification

Prof. Debabrata Nath CSE, NITMAS 2

1. Requirements Gathering:

 Requirement of any business system

 System analyst do the entire jobs of this phase

 Collect all information from the customer

 Use interviews and discussions technique

Prof. Debabrata Nath CSE, NITMAS 3

2. Requirements Analysis:

 Analyzes the collected information to obtain a

clear and thorough understanding of the product

 Use interviews and discussions technique

repeatedly

Prof. Debabrata Nath CSE, NITMAS 4

Requirements Analysis: (Con..)
 System analyst should understand:
 What is the problem?
 Why is it important to solve the problem?
 What are the possible solutions to the problem?
 What exactly are the input and output data of the
system?
 What are the likely complexities of the problem?
 If external interface is required, then what exactly would
the data interchange formats with the external system
be?

Prof. Debabrata Nath CSE, NITMAS 5

3. Requirements Problem:

 Identify and resolve three problems:

 Ambiguity / Anomaly: several interpretations of the
same requirement
 Inconsistency: one requirement contradicts another
 Incompleteness: overlooked requirements

 Use interviews and discussions technique

rigorously

Prof. Debabrata Nath CSE, NITMAS 6

4. Requirements Specification:
 Prepare SRS document

 Toughest document – wide variety of audience

uses it for different purposes:
 users, customers and marketing personnel
 software developers
 test engineers
 user documentation writers
 project managers
 maintenance engineers

Prof. Debabrata Nath CSE, NITMAS 7

Requirements Specification: (Con..)

 Characteristics of good SRS document:

 Concise: unambiguous, consistent and complete
 Structured: easy to understand and modify
 Black-box view: specify what the system should do and
not how
 Response to undesired events
 Verifiable: whether or not requirements have been met
in an implementation

Prof. Debabrata Nath CSE, NITMAS 8

Requirements Specification: (Con..2)
 SRS document consists:
 Introduction: background, overall description and
environmental characteristics (hardware, peripherals,
people)
 Functional requirements: functionalities
 Nonfunctional requirements: maintainability,
portability, usability, reliability, accuracy, security,
interface, project management etc.
 Goals of implementation: revision, new device
support, reusability etc. in the future
 Behavioral description (optional): system states,
events and actions
Prof. Debabrata Nath CSE, NITMAS 9
Requirements Specification: (Con..3)
 Without developing an SRS document an
organization may face severe problems:
 Difficult to understand the problem
 Difficult to implement according to customer needs
 Difficult to modify in the future
 Difficulty in maintenance
 Difficult to write user document

 SRS document is the agreement signed by both

the parties

Prof. Debabrata Nath CSE, NITMAS 10