|
| Reference | Technique | Description |
|
| [6] | Survey of requirement elicitation techniques, approaches, and tools | Significant aspects of tools, techniques, and approaches are covered along with the trends, issues, and challenges in the field |
| [8] | Roadmap of requirement engineering | This research work provides an overview about requirement engineering (RE) of the software systems. It defines the core areas of RE practice and points out some main issues of open research for the future. |
| [9] | Techniques of knowledge elicitation | The main reason of this survey is (1) knowledge elicitation techniques identification and the related bibliographic information, (2) techniques organization into categories based on methodological resemblance, and (3) summarizing techniques strengths, weaknesses, and suggested applications. |
| [10] | Elicitation technique selection: how do experts do it? | This study provides in-depth interviews results conducted from some of the world’s most experienced analysts. The results produced show how the selection is carried out for elicitation techniques based on a variety of situational assessments. |
| [11] | Framework for matching requirement engineering techniques | This paper proposed a framework in which the typical requirement engineering techniques are characterized, which in turn provides a base for the selection of most adequate techniques at the time when the project starts and at the time of identifying a change in nature of the project or experiencing difficulties in describing a appropriate set of requirements. |
| [12] | Framework for selection of requirement elicitation techniques | In this paper, a framework is introduced; this framework helps analysts select the most suitable elicitation technique that is fit for the elicitation session, the project environment, and problem domain. After applying this framework, it provides a priority list of elicitation techniques that best suits the project. |
| [14] | Utilizing online serious games to facilitate distributed requirement elicitation | This paper proposed a new approach, i.e., online serious games, in order to gather requirements from the stakeholders distributed. Empirical study was conducted in this approach to evaluate the feasibility and find the effectiveness. The results produced by this approach were good enough and helped out less experienced analysts gather higher number of requirements. The results produced also recognized that this approach provides simple and easy way to individuals that are technically less experienced and allows them to contribute in requirement elicitation. |
| [15] | A theoretical and empirical study of topic importance in requirement engineering elicitation interviews | This study proposed the elicitation topic map (ETM), which helps engineers formulate interviews. ETM shows topics in the form of diagrams; these diagrams are then discussed in interviews and represents how likely to discuss these topics spontaneously by the stakeholders. If a topic to be discussed spontaneously, it is less likely, then suggestions to engineers are that they might wish to make questions on it just before the interview. ETM was shaped through empirical and theoretical research. |
| [16] | Gamifying requirement elicitation | This study examines that how much web collaborative tools are useful and accepted, in which development was done by using approach of the six thinking hats method and gamification to get dispersed stakeholders altogether. The document discusses the implication and results in order to improve collaboration among stakeholders. |
| [21] | Requirement elicitation techniques selection | The study was conducted in knowledge-based systems based on previous works, evaluating and building upon their efforts, and extended the knowledge-based approach by considering taxonomy of project characteristics. It has mainly bridged the gap to provide necessary support for the analyst by taxonomy of the software project types. The method proposed provides support in terms of selection of appropriate elicitation technique and knowledge base related to it. The method evaluation is done through a case study and prototype to check its effectiveness and feasibility. |
| [22] | Review of techniques of requirement elicitation | This paper presented elicitation techniques understanding and how to use them in applications of real time. The implementation of these techniques of requirement gathering provides base to know clearly requirements of the stakeholders and also helps developers better understand the requirements of the developing system. |
| [23] | Requirement elicitation problems | This paper presented problem types classification that requirement elicitation process faces. To derive this classification, a literature analysis has been carried out. Papers reporting on techniques for improving requirement elicitation practice were examined for the problem the technique was designed to address. The classification contains the most prominent or recent techniques for solving the problems. The requirement engineer is allowed by the classification to be sensitive on the rise of the problems and the educator to structure delivery of requirement elicitation training. |
| [24] | Assessment of requirement elicitation tools and techniques | This paper provides the understanding of requirement elicitation tools and techniques. The paper also presented the comparison of elicitation techniques and software requirement tools in a summarized form, and this comparison is based on different parameters. |
| [25] | Requirement elicitation framework | This study proposed a framework of requirement elicitation, which starts with an organization’s business process model and builds the system’s CRUD matrix. This matrix actually provides all possible relationships between entities and functions of the system in order to gather complete requirements of the system. |
| [26] | Analysis of elicitation techniques for design of smart requirements | This paper presented elicitation techniques comparison in detail, along with its characteristics as well as situational characteristics. The main aim of comparative analysis is to support analyst for selection of suitable requirement elicitation technique on the basis of different situational characteristics. The model presented will be quite helpful to automate the process of technique selection for elicitation. |
| [18] | An exploration into the process of requirement elicitation | In this study for RE, an integrative process model is presented. The suggestion comes from the study’s finding that there are four collaborative states from which RE is composed. This research explains these four states, and important factors are identified, which tend to trigger transitions from one state to another. |
| [19] | Review and aggregation of empirical studies on elicitation techniques | This research has provided empirical studies results on the techniques used for elicitation, and empirical evidence has been provided after the results aggregated. The methodology chosen for surveying was systematic review, whereas comparative analysis method is adopted for aggregation because the applicability of meta-analysis techniques is not possible. In review, identification of 564 publications is done from ACM DL databases, IE EEXPLORE, SCOPUS, and Google. In this research, 26 publications are selected, and then data is extracted from them. The 30 empirical studies are found in the selected publications. These studies were designed to test 43 elicitation techniques and 50 different response variables. The study got 100 separate results from the experiments. The 17 pieces of knowledge are generated by the aggregation about sorting, laddering, protocol analysis, and interviewing elicitation techniques. In this research, the gathered knowledge provides guidelines set. |
|
