Extended Rationale-Based Model for Tacit Knowledge Elicitation in Requirements Elicitation Context

Abstract

The Requirements elicitation involves knowledge intensive and collaborative activities. Requirements engineering research has proposed a range of knowledge elicitation and requirements gathering techniques, few of which apply specific strategies for eliciting tacit knowledge from stakeholders. The difficulty of taking the deliberate advantage of important tacit knowledge of stakeholders is one of the eminent problems in requirements elicitation. This paper proposes a model to define and elicit the tacit knowledge that has been generated during the requirements elicitation process. The model is based on adopting and extending the rationale model for requirements rationale knowledge elicitation in the requirements elicitation process context. Moreover, this paper presents a representation code to express the tacit knowledge in this context. Finally, to evaluate the feasibility of the model, a survey instrument was applied on domain experts to gather their opinion regarding the ability of the proposed model in facilitating tacit knowledge elicitation. In addition, controlled experiment used to evaluate the proposed model. To explore the model, a post-questionnaire was used to identify participants' feedback. The findings of the evaluation methodologies that were used showed that the proposed model can facilitate tacit knowledge elicitation in the requirements elicitation context. Also, the proposed model has a significant effect on improving the requirements elicitation. INDEX TERMS Requirements engineering, requirements elicitation process, rationale-based model, tacit knowledge.

Valuating requirements arguments in the online user's forum for requirements decision‐making: The CrowdRE‐VArg framework

“…Their proposed model is inspired by the ASPIC+ argumentation framework. Similarly, Al‐Alshaikh et al 24 proposed a rationale based approach to define and identify tacit knowledge that is generated during the requirements elicitation process. Their proposed ERBeTK methodology uses the question option criteria rationale representation model.…”

“…Whereas argumentation theory is that an argument is trusted if it can defend itself successfully against the attacking arguments. 21 Such as, it is utilized to eradicate requirements ambiguities during interviews, 22 recognize conflict-free user requirements by removing inconsistencies, 23 identify tacit knowledge during requirements elicitation, 24 and bring most important issues upfront to the development team. 25,26 Besides, some researchers have started using argumentation theory and machine learning (ML) algorithms to mine user comments from the Reddit forum 27 and issue tracking systems 8 to identify conflict-free new features, issues and usability requirements.…”

Enhancing Software Feature Extraction Results Using Sentiment Analysis to Aid Requirements Reuse

“…Requirement elicitation is the process of searching and acquiring stakeholders' interests in a software development [1][2][3]. This aims to help produce new requirements from relevant stakeholders [4], which can be taken from various sources and are available in a range of formats.…”