This topic comes under Requirements Engineering

1. Software Requirements Elicitation Methods
Muhammad Naeem

2. Software Requirement Elicitation Methods
 Introduction
 Problems in Requirements Elicitation
 Requirements Elicitation Methods
 New Techniques for Requirements Elicitation
 Building Operational definitions based on keyword mapping
 Process Flow
 Requirements Elicitation using QFD
 Risk Analysis Using CMM
 Evaluation Methods
 Conclusion

3. Introduction

4. Introduction
 Requirements elicitation is the practice of collecting the
requirements of a system from users, customers and
other stakeholders

5. Problems in Requirements
Elicitation

6. Problems in Requirements Elicitation
 Problems of scope
 Problems of understanding.
 Problems of volatility.

7. Requirements Elicitation Methods

8. Requirements Elicitation Methods
 Dealing with the problem of lack of user input
 Structured and Unstructured Interview with stakeholders
 Template document for keywords
 Define precise system requirements
 Requirements should be meaningful, precise and realistic

10. New Techniques for Requirements
Elicitation

11. New Techniques for Requirements Elicitation
 Training sessions to eliminate “lack of user input” and
“poor understanding”
 Recording keywords
 Pictorial representation of needs and wants to reduce
language barriers
 Keyword Mapping
 Operational definition extraction

12. Building Operational definitions
based on keyword mapping

13. Building operational definitions based on
keyword mapping
 Collection and Identification of Keywords
 Categorization of Keywords
 Attribute Set = {(k1), (k2), (k3), (k4),(k6), (k7)}
 Behavioral Keyword set = {(k1), (k2), (k3), (k4)}
 Non-functional Keyword set = {(k1), (k2), (k3),(k4)}
 Functional Keyword set = {(k1), (k2), (k3), (k4)}

14. Building operational definitions based on
keyword mapping
 Mapped Keywords
representation
Map(Att,Behav) =
{(k2,k3), ( k4,k2)}
Map(Non-funct,Att) =
{(k4,k3) , (k3,k7)}

15. Building operational definitions based on
keyword mapping
 Mapping Nested Sets
Map(Map(Attr, Behav), Map (Nonfunct,Attr)) =
{ [(k2,k3), (k3,k7)], [(k4,k2), (k4,k3)] }
Now the keywords k2,k3,k3,k7,k4,k2,k4,k3 form a
sentence.

16. Process Flow
The process flow diagram is another representation of the
elicitation process,

17. Domain Specific
Requirement
Classifying & Prioritizing system
requirements using QFD
Domain Specific Req
Quality Inspection
Requirement Specification
Risk Analysis Using CMM
Analyze and build
Product
User Training
Sessions
Available Resources and
Computer Limitations
Development and
other stakeholder’s
abilities and skills
Available Resources and
Computer Limitations
Interview1 Interview2 Interview3 Interview4
New Technique for
requirement
Extraction
Keyword recording and
Extraction
Keyword mapping
Technique
Operational Definitions for
system Requirements

18. Requirements Elicitation using QFD

19. Requirements Elicitation using QFD
 What is QFD?
 A systematic process for motivating a business to focus on its
customers.
 Based on market research: understanding customers’ needs
and desires, and the effectiveness of relevant products in
meeting those needs and desires.
 Why QFD?
 To improve the communication of customer needs
throughout the organization.
 To improve the completeness of specifications and to
make them traceable directly to customer wants and
needs.

20. Components of QFD

22. Risk Analysis Using CMM

23. Risk Analysis Using CMM
 The Capability Maturity Model for Risk Management
is a model for describing both the present maturity of
risk management processes in an organization, and
for studying those processes in order to develop a
more mature, i.e. effective, risk management process.
 The CMM is divided into five maturity levels
 1. Initial.
 2. Repeatable.
 3. Defined.
 4. Managed.
 5. Optimizing

24. Evaluation Methods

25. Evaluation Methods
 Effective data collection method for evaluating software
development methodologies
 Evaluated by collecting data from domain experts and from other
users who have studied the technique thoroughly
 Evaluate the technique subjectively, by questions including the
following:
 (true/false) In current software elicitation, many important things are overlooked.
 (true/false) Pictorial representations of keywords help to make their meanings
clear and unambiguous.
 (true/false)The sentences generated by collecting, mapping and relating keywords
can easily be converted to accurate system requirements.
 (true/false)The technique eliminates irrelevant, redundant or trivial requirements.
 (true/false)When many keywords (e.g. several hundred or thousand) are collected,
the mapping process and its results are still manageable.
 Is this technique simple?
 Is this technique effective?

26. Evaluation Methods(cont..)
 The technique will be applied to actual elicitation situations of
various scales, and stakeholders will be asked about their satisfaction
with various parameters of the elicitation:
 Are the requirements complete?
 Are they within the scope of the system?
 Have irrelevant, redundant and trivial requirements been avoided?
 Do the requirements accurately represent the expressed needs of the users?

27. Conclusion

28. Conclusion
 Goal
 To develop a new methodology for improved requirements elicitation
 Proposal
 Training of users in the capabilities and limits of the computer and of
software developers;
 Collection of keywords from stakeholders in all categories;
 Pictorial representation of keywords to facilitate agreement on their
meaning;
 Keyword mapping to generate system requirements;
 Quality Function Deployment (QFD) to make sure that requirements
are relevant to the task and to the users’ needs;
 Capability Maturity Model (CMM) to make sure that requirements take
into account the risks the system will encounter or generate.

29. References

30. References
 [1]. Requirements Engineering A good practice guide, Ramos Rowel and Kurts Alfeche, JohnWiley and Sons,
1997
 [2].A. Umber, M.S. Naweed, andT. Bashir, I. S. Bajwa, (2012). Requirements Elicitation Methods,Advanced
Materials Research, 433-440 pp.6000-6006,2012
 [3]. Prasad Rajagopal, Roger Lee,Thomas Ahlswede, Chia-Chu Chiang, Dale Karolak. "A New Approach for
Software Requirements Elicitation". Proceedings of the Sixth International Conference on Software
Engineering,Artificial Intelligence, Networking and Parallel/Distributed Computing and First ACIS
InternationalWorkshop on Self-AssemblingWireless Networks (SNPD/SAWN’05) 0-7695-2294-7/05
$20.00 © 2005 IEEE
 [4]. Soto,Alejandro and Preeti S. Malik,“QFD”. iSixSigma Dictionary,
http://www.isixsigma.com/dictionary/QFD-103.htm, 2003


 [5] InternationalTechneGroup Inc.,“The Basics of QFD”,
 http://www.iti-oh.com/cppd/qfd/qfd_basics.htm,2004
 [6] Squires,Ted,“Description of the QFD Process”,
 http://www.masetllc.com/products/418.shtml, 2005

 [7] Fox, Nevill,“Capability Maturity Model (RM-CMM) for Risk Management”, Silicon Rose,
 http://www.siliconrose.com.au/Articles/RiskCMM.htm, 2005.

 [8] Sullivan, L.P. Quality function deployment. Quality Progress 19, 6 (June 1986).