In requirements engineering, requirements elicitation is the practice of researching and discovering the requirements of a system from users, customers, and other stakeholders. ... Commonly used elicitation processes are the stakeholder meetings or interviews.

1. M AbdulTawab Khalil
REQUIREMENTS
ELICITATION:
A SURVEY OFTECHNIQUES,
APPROACHES, ANDTOOLS
Book Chapter by
Didar Zowghi and Chad Coulin
University ofTechnology, Sydney, Australia

2. Abstract -1
■ Requirements elicitation is the process of seeking, uncovering, acquiring, and
elaborating requirements for computer based systems.
■ It is generally understood that requirements are elicited rather than just captured or
collected.
■ This implies there are discovery, emergence, and development elements in the
elicitation process.

3. Abstract - 2
■ Requirements elicitation is a complex process involving many activities with a variety
of available techniques, approaches, and tools for performing them.The relative
strengths and weaknesses of these determine when each is appropriate depending on
the context and situation.
■ The objectives of this chapter are to present a comprehensive survey of important
aspects of the techniques, approaches, and tools for requirements elicitation, and
examine the current issues, trends, and challenges faced by researchers and
practitioners in this field.

4. What is Requirement Elicitation?
■ Requirements elicitation is concerned with learning and understanding the needs of
users and project sponsors.
■ The objective of requirement elicitation is communicating these needs to the system
developers.
■ A substantial part of elicitation is dedicated to uncovering, extracting, and surfacing
the wants of the potential stakeholders.

5. Requirement Elicitation - 2
■ The extensive process of requirement elicitation is sometimes called “trawling for
requirements”.
■ Due to the trawling, we often get more requirements than expected which is good
thing.
■ More recently the concepts of inventing and creating requirements have been used.

6. Requirement Elicitation Process
1. Understanding the Application Domain – examining the real world where the system
will ultimately reside
2. Identifying the source of requirement
3. Analyzing the stakeholders
4. Selecting theTechniques, Approaches, andTools to Use
5. The actual Elicitation

7. Requirement ElicitationTechniques &
Approaches
■ A “Technique” is a way of doing something or a practical method applied to some
particular task.
■ An “Approach” is a systematic arrangement (usually in steps) of ideas or actions
intended to deal with a problem or situation.

8. List ofTechniques & Approaches - 1
1. Interviews
2. Questionnaires
3. TaskAnalysis
4. DomainAnalysis
5. Introspection
6. Repertory Grids
7. Card Sorting
8. Laddering

9. List ofTechniques & Approaches - 2
9. GroupWork
10. Brain Storming
11. JointApplication Development (JAD)
12. Requirements Workshop
13. Ethnography
14. Observation
15. ProtocolAnalysis
16. Prototyping

10. List ofTechniques & Approaches - 3
17. Goal Based Approaches
18. Scenarios
19. Viewpoints

11. Comparison ofTechniques & Approaches - 1

12. Comparison ofTechniques & Approaches - 2
■ C = Complementary
■ A = Alternate

13. Tools (Software) for Requirement
Elicitation
■ IEEE Std 830 Software Requirements
Specification –Template
■ Volere Requirements Specification –
Template
■ DOORS - Format Based
■ CaliberRM - Format Based
■ RequisitPro provide - Format Based
■ Objectiver - Goal Based
■ ART-SCENE - Scenario Elicitation
■ ACME/PRIME
■ AbstFinder
■ AMORE
■ TeamWave