Requirement

Elicitation
and its
techniques
 Requirement Elicitation

“REQUIREMENT ELICITATION” is the practice of researching and

discovering the requirements of a system from users, customers, and
other stakeholders. The practice is also sometimes referred to as
“requirement gathering”.
Requirement elicitation is a complex process that consists of Gathering, Researching, Defining,
Structuring, and Clarifying a product’s requirements. These objectives have to be
understandable for each team member and represent all of the client’s demands and needs.
Requirements elicitation is an important step of the Software development discovery phase.

It is the most difficult, most critical, most error- prone and most communicative aspect of
software development. it can succeed only through an effective “customer developer
partnership”.
 Key Benefits Of Requirements Elicitation
 Establishes the precise scope of work and the budget.

 Avoids confusion during development.

 Adds business value.

 Reveals hidden and assumed requirements.

 Allows for developing only relevant functionality.

 Techniques of Requirement Elicitation
1. Interviews

2. Brainstorming Sessions

3. Facilitated Application Specification Technique (FAST)

4. Quality Function Deployment

5. The Use Case Approach

 Interviews
These interviews are held after receiving the problem statement. The objective of conducting these
interview is to understand the customer’s expectations from the software.

Interviews are of two types

1. Open Ended Interviews:- In Open Ended Interviews ,there is no pre set agenda. Context free
questions may be asked to understand the problem and to have an overview of the situation .

2. Structured Interviews:- In Structured Interviews ,agenda of fairly open question is prepared even
sometimes a proper questionnaire is designed for the interview.
 Brainstorming Sessions
Brainstorming is a group technique that may be used during requirement elicitation to understand the
requirements. The group discussions may lead to new ideas quickly and help to promote creative
thinking.

Brainstorming has become very popular and is being used by most of the companies as it promotes
creative thinking ,generates new ideas and provides platform to share views, apprehensions
expectations and difficulties of implementations.
 Facilitated Application
Specification Technique (FAST)
This technique is similar to brainstorming session and the objective is to bridge the expectation gap (A
difference between what developer think what to develop and what customer think they are will get)

In order to reduce this gap, a team oriented approach is developed for requirements gathering and is
called Facilitated Application Specification Technique (FAST).

This technique encourages a joint team of customer and developer who works together to understand
the expectations and propose
 Quality Function Deployment
It is a Quality management technique that helps to incorporate the voice of the customer. Technical
requirements are documented and results is the software requirements and specification document.

Quality function development emphasizes an understanding of what is valuable to the customer and
then deploys these values throughout the software engineering process.
 The Use Case Approach
This approach uses a combination of text and pictures in order to improve the understanding of
requirements.

USE CASES are structured outline or templates for the description of user requirements, modeled in a
structured language like English.

USE CASE SCENARIOS are unstructured description of user requirements.

USE CASE DIAGRAM are graphical representation that may be decomposed into further levels of
abstraction.
Thank you