Requirement elicitation techniques for software

1. REQUIREMENT ELICITATION
TECHNIQUES FOR SOFTWARE
Arbab (23126)
Qasim Ali (22772)
Adeel hassan ( )
Submited by :

2. REQUIREMENT ELICITATION
Requirements elicitation is the
collection of the requirements
of any given system or product
from users, customers and other
important stakeholders

3. REQUIREMENT GATHERING TECHNIQUE
Stake holder analysis
Brainstorming
One on one interview
Group Interview
Document Analysis
Focus Group
Interface Analysis
Observation
Prototyping
Requirements Workshop
Reverse Engineering
Survey

4. STAKE HOLDER ANALYSIS
Definition:
 Stake holder analysis identifies all the
user and stakeholders who may
influence or be impacted by the
system. This this help ensure that the
needs of all those involved are taken
into account.
Benefits:
 Ensure that all relevant stakeholder are
considered
 All important stakeholder are captured, yet
that irrelevant actors are not included.
Drawbacks:
 There is danger that to much time is spent
on identifying roles and relationships and
the teams is swamped data.

5. BRAINSTORMING
Definition:
It is utilized in requirements elicitation to
gather good number of ideas from a
group of people. Usually brainstorming is
used in identifying all possible solutions
to problems and simplifies the detail of
opportunities.
Basic Rules
 Generate may idea as possible
 Let your imagination soar
 It casts a broad net, determining
various discreet possibilities.
Benefits
 Generate the variety of idea in a short
time
 Produce new and creative ideas

6. ONE ON ONE INTERVIEW
Definition:
 The most common technique for
gathering requirements is to sit down
with the clients and ask them that they
need. The discussion should be
planned out ahead of time based on
the type of requirements you are
looking for
benefits
 Privacy of everyone in-depth a
stakeholder thoughts and get his or her
perspective
Risks:
 Time consuming
 Misunderstanding

7. INTERVIEW
Interviews of users and
stakeholders are
important in creating
wonderful software.
Without knowing the
expectations and goal of
the stakeholders and
users, you are highly
unlikely to satiate them