Selection of Software Requirements Elicitation Techniques- A Systematic Review

8

Journal of Multidisciplinary Approaches

in Science (JMAS)

Selection of Software Requirements Elicitation Techniques- A

Systematic Review

Fazila Shams

, Hafiz Ammar Mazhar Bhutta

1 _{Department of Software Engineering, Bahria University Islamabad, 44000 Pakistan}

ARTICLE INFO ABSTRACT

Article history:

Received 27 November 2018

Received in revised form 2 January 2019 Accepted 9 January 2019

Available online 20 January 2019

Requirements elicitation is a basic action that frames some portion of the Requirements Engineering process. since it needs to find what the product must do through a strong comprehension of the desires and needs of the different stakeholders and then to change them into Requirements list. But, despite of its significance, only a couple of Systematic reviews are present in literature that give logical proof about the adequacy of the procedures used for Software Requirements Elicitation. This paper aims to present a systematic review of literature about the Elicitation techniques. The goal is to find out the mature techniques which are used for requirements elicitation and which techniques increases efficiency of the elicitation. Preceding literature expect that maturity prompts a better understanding of client’s requirements, and hence an improved probability that a subsequent product will fulfill those requirements. This review found 30 studies to find the answers and depicts which techniques are more effective and which techniques is suitable under which situations, considering the system to be developed and information obtained from other factors.

Keywords:

Requirements Elicitation, Requirements elicitation techniques, Requirements

Elicitation Process Copyright © 2019 JMAS - All rights reserved

1. Introduction

Requirement engineering or Requirements Specification process the constraints of the system,

functionalities of the system, domain, and risks are defined [1]. In this manner, RE is one of the parts

of Software Engineering which is responsible for the crucial tasks of gathering, analyzing, and then

verification of the software requirements. Requirements Engineering is further divided into different

activities Like Requirements Elicitation process, Analysis Process, Specification Process, Verification

and validation of requirements and in the end management of requirements.

The main focus of this paper is on the first activity of RE which is elicitation of Requirements. Also,

inside the elicitation process there are some fundamental sub-activates like identification of system

stakeholders, and the selection and negotiation of method to elicit the needs and desires of the several

stakeholders [2].

Corresponding author.

E-mail address: [email protected] (Fazila Shams)

Open Access

9

For this purpose, A number of techniques or methods for finding and gathering the software

requirements exist, yet it is important to identify which techniques are the most appropriate

according to the project

requirements or situations [3]. To enhance the quality of software it is

mandatory to enhance the quality of the gathered requirements and for this, the selection of suitable

and more appropriate elicitation technique is a crucial and main step. From this point of view, it is

important to understand that elicitation of good quality requirements is not a simple task instead

elicitation is strongly associated with other factors like the Project characteristics, the environment,

organization, the knowledge and experience of requirement analyst, and the characteristics of

elicitation technique used as well.

The aim of this review is to help the analyst in the selection of technique in the light of

available evidences and empirical studies related to this field presents in the literature.

2. Literature Review

In the literature there are a number of systematic reviews available in which activities of the

elicitation process are discussed [4, 5] and some studies focuses on the effectiveness of technique

used for requirements elicitation and the characteristics of different techniques[6-9]. Some of these

are briefly discussed below:

In [6] Davis conferred a systematic review of different empirical studies related to the

effectiveness of techniques used for elicitation. This study aims to find the most efficient technique

according to the situation and results shows that that interviews is a best or more effective way to

elicit requirements because this method allow analysts to gather more information as compared to

the other techniques.

Dieste et al. [7] collected information about the maturity of techniques used to elicit requirements

by analyzing the results of different empirical studies from literature. This research paper gives some

recommendations related to the selection of technique against different situations to get best

possible outcomes. All the recommendations are given in the result of a Systematic review

accomplished to find the effective technique. The findings show that the structured interviews are

more effective under some conditions. because the information collected in result of this technique

is complete and precise.

Research by Svensson et al. [8], Performed a Systematic review of 18 different empirical studies

emphases on quality requirements. The concluded results of this review recommend five techniques

to elicit quality requirements, but this study also supports the concept that there is no one best

technique for elicitation of quality requirements.

In [9] Dieste and Juristo presents the results of a Systematic review over 30 different empirical

studies related to elicitation techniques. This study extract information from literature to test 43

different elicitation techniques against different response variables. The results states that interviews

are the effective technique and use of introspective techniques are not recommended.

In [10] Wong et al. reviewed the literature to find out what aspects are covered by the previous

studies and which factors influence the elicitation process existing gap in this field and their research

conclude that requirement elicitation process still needs more research and improvement.

10

Joseph et al. [11], also suggest the techniques according to their effectiveness are impact on

application development. Their results show that for getting best possible results in most of the

projects a combination of techniques is used to elicit techniques and some techniques can be

effective if analyst has some set of skills also in case of low budget questionnaires can be adopted.

In [12]. Carrizo et al. match the theoretical proposed attributes and their empirical studies which

effects the effectiveness of elicitation technique. Results show that 60 percent theoretically proposed

attributes are studied in empirical studies but a third of proposed impact of attributes proposed

theoretically are confirmed empirically.

Instead of all these above systematic reviews, some of the latest studies are also examined to

deduce the results. The summary of the studies used for this review are presented in the following

table.

Table 1

Summary of literature review

Study Purpose/ Research Questions Findings

Effectiveness of requirements elicitation techniques:

Empirical results derived from a systematic

review

What is the most efficient elicitation

technique in a particular setting? 1. The Structured interviews are one of the most effective technique 2. Various other techniques presented in

literature are less effective as compared to interviews 3. Most Empirical studies don not

recommend prototyping. Updating a Systematic Review

about Selection of Software Requirements Elicitation Techniques

What elicitation techniques are most

effective? 1. Structured interviews are more efficient than scaling techniques 2. Efficiency of laddering technique and

scaling techniques is at same level. 3. Scaling techniques are difficult as compared to unstructured interviews Managing quality requirements:

A systematic review What empirical research has been performed on quality requirements? What empirical methods have been used to evaluate the quality requirements?

1. Quality requirements need detailed analysis so better to not address in the scope of functional requirements 2. To ensure better understanding of

problem, it is essential to examine the inter-dependencies exist b/w software design and quality requirements Systematic review and

aggregation of empirical studies on elicitation techniques

The purpose of this study is to test numerous techniques and response variable by gathering information from previous empirical studies.

1. unstructured-interviews are more effective as compared to sorting techniques.

2. unstructured interviews yields more complete info as compared to the info obtained from laddering.

3. if you have a choice b/w laddering and sorting the recommended one is laddering.

Requirements engineering: a

roadmap The purpose is to present an overview of the field (RE). Effective RE process has a pivotal role to determine the success and failure of Software projects, and also in defining the quality of delivered systems.

11

elicitation technique selection: model for two knowledge-intensive software development processes,

This paper presents a mathematical model for the process of requirements elicitation.

By the help of presented model, an analyst can accomplish elicitation for any project by moving through different steps. Each activity has aim to bring the stakeholders closer to a common understanding of system’s requirements which they want to address.

A systematic mapping study on empirical evaluation of software requirements specifications techniques

Which are the most investigated quality aspects of the SRS techniques?

What research method was used in the evaluation of the aspects most studied?

This paper concluded that in the light of empirical study understandability is the most commonly evaluated aspect of SRS, experiments are the most

commonly used method of research, and most empirical studies takes place in academic environment.

The role of domain knowledge in requirements elicitation via interviews: an exploratory study

The purpose of this paper is to presents an empirical study to examined the apparent and actual effects of previous domain knowledge

on elicitation through interviews.

The results specify that domain knowledge show impact on elicitation through interview in two aspects: communication and understanding of client’s needs.

The results offer understandings of both the positive and negative impacts of domain knowledge on process of elicitation through interview. Effectiveness of traditional

software requirement elicitation techniques applied in

distributed software development scenarios

The purpose of this paper is to presents comparative study of the use of traditional elicitation methods for distributed scenarios of development

The Results shows that the combination of interviews and brainstorming are more effective techniques used for eliciting requirements in distributed scenarios

A Comparison of Questionnaire-Based and GUI-Based Requirements Gathering

This study has compared the use of Graphical Requirements Collector(GRC) with

questionnaire-based technique.

1.This study specifies the GRC approach has potential to elicit user

requirements.

2.It also demonstrate how improving the GRC approach could improve the outcomes.

Systematizing requirements elicitation technique selection

The purpose of this study is to proposes a framework that support requirements engineers to select the most acceptable elicitation techniques.

A novel validated approach for selection of Elicitation technique. The proposed approach picks techniques other than interview, and suggests a wide range of possible techniques and captures the information requirements more deeply.

Using Scenarios to Discover Requirements for Engine Control Systems

The purpose of this Study is to investigate either the ART-SCENE process could enable engineers to recognize exception behaviors earlier in the system design process.

1.Derived Requirements are identified earlier by using the discussed approach which aids the program.

2.This approach helps system, Safety and verification engr. To find more inconsistencies.

Supporting Collaborative Requirements Elicitation Using Focus Group Discussion Technique

The purpose of this study is to present a prototype of Focus Group Discussion for elicitation, FGD-RElicit

FGD-RElicit is aimed to improve the requirements elicitation process, enhances the SRS, and produce better software

On eliciting requirements from end-users in the ICT4D domain

This purpose of this study is to suggest enhancements to the elicitation methodology precisely adapted to address existing shortcomings

The presented novel technique of Structured Digital Storytelling elicit input from end-users who have limited literacy and applies a conceptual model

12

Mind-mapping: An Effective Technique to Facilitate Requirements Engineering in Agile Software Development

The aim of this paper is to evaluate how elicitation-related

activities within an agile development can be helped by using "mind-mapping" technique

The data they represent show that, when mind mapping is adopted, the overall quality of the

product backlog is significantly higher with less expert users

Achieving quality in software

requirements The purpose of this study is to find the situations for receiving best results from different elicitation methods

1.Interviews are best option if the requirement analyst is an open-minded person and have patience to listen. 2.Questionnaires based methods are

preferable in case of diverse stakeholders

3.Prototyping is recommended is stakeholders are incapable to tell their need.

Modern trends towards

requirement elicitation In this paper, analysis of information of techniques is provided, gathered from practitioners.

1.Analyses leads to extract modeled guidelines for elicitation techniques 2.This Study also suggest an efficient plan used for requirements elicitation which aims to overcome on different constraints, confronted by

Practitioners. Requirements elicitation

techniques selection survey This paper analyzes many elicitation techniques to understand features of each method.

1.The results show that interviews and workshops are most famous methods 2.The least used techniques are card

sorting and JAD

3.Technique ability is the factor which affects the most in selection of technique and least important factor is familiarity

Selecting requirement elicitation techniques for software projects

The purpose of this paper is to develop a framework to select elicitation

methods for a given software project based on context of project

The state of the practice

in requirement engineering is yet a major problem in development because it is very difficult to find a fixed conclusion about selection of eliciting techniques

Elicitation Technique Selection:

How Do Experts Do It? The purpose of this paper is to deduce results from detailed interviews of some of most experienced requirement analysts.

The results shows that for every elicitation technique, some basic analyst skills are mandatory otherwise technique will not give effective results. The authors called these skills as “Success Enhancers.”

Interview Review: An Empirical Study on Detecting Ambiguities in Requirements

Elicitation Interviews The purpose of this paper is to find a way to identify ambiguities in

requirements, elicit through interviews.

1.The interviews should audio recorded and reviewed by the analyst with one more reviewer.

2. This protocol can able to find 68% of ambiguities and remaining can be identify during interview The Role of Ethnography in

Agile Requirements Analysis The purpose of this paper is to propose a model which helps ethnographic analyst to know how people actually work and

1.The model needs that ethnographic analyst stay in organization to observe the working of People, instead of

13

functionality formal way of requirements documentation. 2.This helps to recognize the implicit

requirements which are not defined by organization.

Prototyping Use as a Software Requirements

Elicitation Technique: A Case Study

The purpose of this study is to find the cases in which prototyping technique can able to achieve high courage of requirements.

1.The system is applied on two different stakeholders with different familiarity level of domain.

2.Result recommend prototyping if stakeholders have more knowledge of domain. A SYSTEMATIC LITERATURE REVIEW ABOUT SOFTWARE REQUIREMENTS ELICITATION

What aspects have been covered by different proposal of requirements elicitation?

What activities of the requirements elicitation process have been covered? What factors influence on requirements elicitation and how?

1.About 30% corresponds to framework. 2.Stakeholders as an important part is

not considered in many studies. 3.In most of the proposals the

identification of requirements is under focus.

4.Many studies do not use collaborative approach

5.Knowledge is an important factor which influence the process Selecting a Software Elicitation

Technique According to Layers of Knowledge and Preciseness:

A Case Study

The aim of this paper is to explain that preciseness and completeness are two basic criteria should be incorporate in selecting an Elicitation technique.

1.In domain knowledge layer, for eliciting requirements Concept Mapping technique does good 2.In case of specialized requirements

brainstorming is appropriate.

3.In the kind of the elicited requirements are not clear than product pattern techniques is best.

Survey on Requirement Elicitation

Techniques: It’s Effect on Software

Engineering

The aim of this paper is to present a guideline to choose particular technique against application domain and environment which helps the developer to understand the system well.

1.In most of the projects to get best results, combination of techniques are used.

2.Many techniques like interview demands some level of analyst skills to give effective results

3.Questionaries’ are best for low budget projects

Contextual attributes impacting the effectiveness of

requirements

elicitation Techniques: Mapping theoretical and empirical research

The purpose of this paper is to match theoretical and empirical study on different contextual attributes which influence effectiveness

1.Empirically 60 percent of theoretical attributes have been considered 2.However only a third of impact of

attributes is confirmed empirically.

3. Elicitation Techniques

According to [2], the techniques are divided into following categories.

3.1 Traditional techniques

This classification incorporates a wide class of strategies for the elicitation of generic information

so as to decide and recognize the needs and desires of the stakeholders and project constraints.

Interviews, Surveys, Task analysis and Questionnaires are traditional techniques.

14

These techniques are recommended when there are various types of system stakeholders involve

gathering system’s concepts and specifications. The Examples include Focus group, Brainstorming

and workshops.

3.3 Prototyping techniques

These techniques are utilized when there is a high vulnerability in requirements with the point of

getting a reasonable thought of the software in real life by obtaining detail information. Example of

this technique is prototyping.

3.4 Modelling techniques

These techniques use models like scenarios based on objectives and goals. Examples includes

goal-based method, Scenarios, Use cases.

3.5 Cognitive techniques

This class of strategies plans to elicit requirements through representation and structuring of

stakeholders’ knowledge as far as how they examine a problem and its answer. Examples are

ontology and card sorting.

3.6 Agile techniques

According to [13], Mind mapping, user stories and storytelling are procedural method

participating in agile development to accomplish the requirements elicitation.

4. Characteristics of elicitation techniques

The characteristics of each mature technique, which improves its effectiveness according to

literature is summarized is the following table.

Table 2

Characteristics of elicitation techniques

Techniques Characteristics Referred Studies

Interviews

1.Effective for innovation and automation processes. 2.Able to find errors and explain mistakes in requirements,

through feedback.

3.capable to identify opinions and facts from stakeholders. 4.Beneficial to know a general and clear view of a requirement 5.Useful for obtaining complete and precise information of the

System.

[14, 15]

Prototyping

1.Effective for obtaining a graphical representation of system requirements.

2.Easy to mix with scenarios for graphical representation of tasks.

3.Beneficial for understanding the communications with the system, and also taking adequate details of GUI.

4. Gifted to understand and clarify the requirement

15

2.Effective for the requirements refinement. [17, 18]

Workshops

1.Valuable because this method consider the needs of multiple stakeholders.

2. Effective for offering a set of requirements of diverse type and 3.Eliciting requirements for complex and big systems.

4.handles the expectations of stakeholders. [17]

JAD

1.Convenient to resolve conflict between stakeholders and also for enabling instant decision-making.

2. Effective for primary requirements elicitation with direct

correspondence of stakeholders. [17]

Focus groups 1.Beneficial in conflict resolution with in a group

2.Good for encouraging a cooperative environment. [17, 19] Group storytelling 1.Efficient in recognizing vague requirements.

2. Good for promoting corporation and response from stakeholders.

[20] Mind mapping 1.Effective for enhancing the quality of system requirements.

2.Effective to elicit complete info about requirements. [21]

Brainstorming 1.2.Effective In case of specialized requirements. Effective for knowing stakeholder’s opinion [11, 22]

5. Recommended conditions

Previous reviews and studies also recommend situations in which a technique gives its best

results. Some of the techniques with its suitable conditions are summarized in following table.

Table 3

Recommended conditions for elicitation techniques

Technique Recommended conditions Referred studies

Interviews

1. Requirements engineer must be unprejudiced and have patience to listen the stakeholders.

2. Analyst has domain knowledge [11, 23, 24]

Surveys 1. Involve diverse stakeholders [23]

Ethnography 1.2.The goal is the system replacement. no schedule restrictions. 3.User is very expressive

4.Play an effective tole to elicit requirements in Agile development

[25, 26]

Scenarios 1.Limited Schedule 2.Low budget

16

3.If Stakeholders have more familiarity with the domain 1.

[23, 28, 29]

Workshops 1.Many stakeholders that required collaboration to acquire a precise picture of the system 2.Geographically dispersed Stakeholders

3.Expressive stakeholders.

[23, 27]

Storyboarding 1. Close involvement of used for quick feedback [30]

Laddering 1. Stakeholders do not have previous experience of same problem [9]

6. Conclusions

According to literature, one of the central mistakes which cause a software fail is mostly done in

requirements phase. A software System can satisfy the stated requirements if the RE process is

provided by necessary resources. Inside Requirements engineering phase, the elicitation is a critical

step which is responsible to determine what we are going to developed. So, it is mandatory to find the

stakeholders and their actual requirements. In Addition, during the elicitation phase the context of the

system and domain are acknowledged to acquire high-quality requirements, by means of elicitation

methods that assist the engineers to negotiate with the interest of stakeholders. The goal of this paper

is to present a review to find the Efficient techniques which are mostly used for elicitation purpose

under its suitable situations.

7. Recommendations

A lot of theoretically Proposed techniques and systematic reviews has been proposed time to time

but the effectiveness of only few Proposed approaches are confirmed by the empirical studies.

As for future research, it is recommended to perform several empirical studies on selection of

requirement elicitation technique and report the effectiveness of Proposed theoretical techniques or

methods in order to help the Requirement Engineers to choose the best possible technique under

different environments to achieve best outcomes.

References

[1] K. Pohl, Requirements engineering: fundamentals, principles, and techniques. Springer Publishing Company,

Incorporated, 2010.

[2] B. Nuseibeh and S. Easterbrook, "Requirements engineering: a roadmap," in Proceedings of the Conference on the

Future of Software Engineering, 2000, pp. 35-46: ACM.

[3] A. M. Hickey and A. M. Davis, "Requirements elicitation and elicitation technique selection: model for two

knowledge-intensive software development processes," in System Sciences, 2003. Proceedings of the 36th Annual

Hawaii International Conference on, 2003, p. 10 pp.: IEEE.

[4] N. Condori-Fernandez, M. Daneva, K. Sikkel, R. Wieringa, O. Dieste, and O. Pastor, "A systematic mapping study on

empirical evaluation of software requirements specifications techniques," in Empirical Software Engineering and

Measurement, 2009. ESEM 2009. 3rd International Symposium on, 2009, pp. 502-505: IEEE.

[5] N. Riegel and J. Doerr, "A systematic literature review of requirements prioritization criteria," in International

Working Conference on Requirements Engineering: Foundation for Software Quality, 2015, pp. 300-317: Springer.

[6] A. Davis, O. Dieste, A. Hickey, N. Juristo, and A. M. Moreno, "Effectiveness of requirements elicitation techniques:

Empirical results derived from a systematic review," in Requirements Engineering, 14th IEEE International

Conference, 2006, pp. 179-188: IEEE.

17

[7] O. Dieste Tubio, M. López, and F. Ramos, "Updating a Systematic Review about Selection of Software Requirements

Elicitation Techniques," 2009.

[8] R. B. Svensson, M. Host, and B. Regnell, "Managing quality requirements: A systematic review," in Software

Engineering and Advanced Applications (SEAA), 2010 36th EUROMICRO Conference on, 2010, pp. 261-268: IEEE.

[9] O. Dieste and N. J. I. T. o. S. E. Juristo, "Systematic review and aggregation of empirical studies on elicitation

techniques," vol. 37, no. 2, pp. 283-304, 2011.

[10] L. R. Wong, D. S. Mauricio, G. D. J. J. o. E. S. Rodriguez, and Technology, "A SYSTEMATIC LITERATURE REVIEW ABOUT

SOFTWARE REQUIREMENTS ELICITATION," vol. 12, no. 2, pp. 296-317, 2017.

[11] E. Joseph, Survey on Requirement Elicitation Techniques: It's Effect on Software Engineering. 2017, pp. 9201-9215.

[12] D. Carrizo, O. Dieste, N. J. I. Juristo, and S. Technology, "Contextual attributes impacting the effectiveness of

requirements elicitation Techniques: Mapping theoretical and empirical research," vol. 92, pp. 194-221, 2017.

[13] A. M. Hickey and A. M. Davis, "Elicitation technique selection: how do experts do it?," in Requirements engineering

conference, 2003. proceedings. 11th ieee international, 2003, pp. 169-178: IEEE.

[14] I. Hadar, P. Soffer, and K. J. R. E. Kenzi, "The role of domain knowledge in requirements elicitation via interviews:

an exploratory study," vol. 19, no. 2, pp. 143-159, 2014.

[15] S. Zapata, E. Torres, G. Sevilla, L. Aballay, and M. Reus, "Effectiveness of traditional software requirement elicitation

techniques applied in distributed software development scenarios," in Informatica (CLEI), 2012 XXXVIII Conferencia

Latinoamericana En, 2012, pp. 1-7: IEEE.

[16] J. M. Moore and F. M. Shipman, "A comparison of questionnaire-based and GUI-based requirements gathering," in

Automated Software Engineering, 2000. Proceedings ASE 2000. The Fifteenth IEEE International Conference on,

2000, pp. 35-43: IEEE.

[17] D. Carrizo, O. Dieste, N. J. I. Juristo, and S. Technology, "Systematizing requirements elicitation technique selection,"

vol. 56, no. 6, pp. 644-669, 2014.

[18] A. Mavin, M. Novak, P. Wilkinson, N. Maiden, and P. Lynch, "Using Scenarios to Discover Requirements for Engine

Control Systems," in International Requirements Engineering, 2008. RE'08. 16th IEEE, 2008, pp. 235-240: IEEE.

[19] M. J. I. J. o. S. E. Zarinah and I. Applications, "Supporting collaborative requirements elicitation using focus group

discussion technique," vol. 3, no. 3, pp. 59-70, 2009.

[20] K. Pitula and T. J. R. E. Radhakrishnan, "On eliciting requirements from end-users in the ICT4D domain," vol. 16, no.

4, p. 323, 2011.

[21] I. Mahmud and V. Veneziano, "Mind-mapping: An effective technique to facilitate requirements engineering in agile

software development," in Computer and Information Technology (ICCIT), 2011 14th International Conference on,

2011, pp. 157-162: IEEE.

[22] M.-I. Sanchez-Segura, F. Medina-Dominguez, D.-M. Vásquez-Bravo, G. Illescas, and C. G. J. J. o. U. C. S. de Jesús,

"Selecting a Software Elicitation Technique According to Layers of Knowledge and Preciseness: A Case Study," vol.

23, no. 4, pp. 385-403, 2017.

[23] A. M. J. G. S. D. Davis, "Achieving quality in software requirements," pp. 143-154, 2015.

[24] P. Spoletini, A. Ferrari, M. Bano, D. Zowghi, and S. Gnesi, "Interview Review: An Empirical Study on Detecting

Ambiguities in Requirements Elicitation Interviews," in International Working Conference on Requirements

Engineering: Foundation for Software Quality, 2018, pp. 101-118: Springer.

[25] S. Kausar, S. Tariq, S. Riaz, and A. Khanum, "Guidelines for the selection of elicitation techniques," in Emerging

Technologies (ICET), 2010 6th International Conference on, 2010, pp. 265-269: IEEE.

[26] A. Meligy, W. Dabour, and A. Farhat, "The Role of Ethnography in Agile Requirements Analysis," in Proceedings of

the 7th International Conference on Software and Information Engineering, 2018, pp. 27-31: ACM.

[27] A. Sajid, A. Nayyar, and A. Mohsin, "Modern trends towards requirement elicitation," in Proceedings of the 2010

national software engineering conference, 2010, p. 9: ACM.

[28] F. Anwar and R. Razali, "Requirements Elicitation Techniques Selection Survey," in SoMeT, 2014, pp. 280-294.

[29] D. Carrizo and I. Quintanilla, "Prototyping Use as a Software Requirements Elicitation Technique: A Case Study," in

World Conference on Information Systems and Technologies, 2018, pp. 341-350: Springer.

[30] S. Tiwari, S. S. Rathore, and A. Gupta, "Selecting requirement elicitation techniques for software projects," in

Software Engineering (CONSEG), 2012 CSI Sixth International Conference on, 2012, pp. 1-10: IEEE.