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

Abstract

By its very nature, software development consists of many knowledge-intensive processes. One of the most difficult to model, however, is requirements elicitation. This paper presents a mathematical model of the requirements elicitation process that clearly shows the critical role of knowledge in its performance. One metaprocess of requirements elicitation, selection of an appropriate elicitation technique, is also captured in the model. The values of this model are: (1) improved understanding of what needs to be performed during elicitation helps analysts improve their elicitation efforts, (2) improved understanding of how elicitation techniques are selected helps less experienced analysts be as successful as more experienced analysts, and (3) as we improve our ability to perform elicitation, we improve the likelihood that the systems we create will meet their intended customers' needs. Many papers have been written that promulgate specific elicitation methods. A few have been written that model elicitation in general. However, none have yet to model elicitation in a way that makes clear the critical role played by knowledge. This paper's model captures the critical roles played by knowledge in both elicitation and elicitation technique selection.

Manufacturing knowledge verification in design support systems

“…The system engineer's first task is the elicitation of requirements from the designer, followed by the elicitation of product and process knowledge from the appropriate experts. Elicitation refers to the learnmg, uncovering, extracting, surfacing, and/or discovering the needs of customers, users, and other potential stakeholders (Hickey and Davis, 2002). Elicitation is often complicated by the fact that an expert's knowledge may be implicit (i.e.…”

“…This research therefore follows the iterative model of software development, as discussed by Hickey and Davis (2002). This is a well established technique that results in a time series of successively more sophisticated descriptions.…”

“…Elicitation refers to the learning, uncovering, extracting, surfacing, and/or dIscovering the needs of customers, users, and other potential stakeholders (Hickey and Davis, 2002). In the context of developing a decision support system, this describes the task of uncovering and documenting the requirements of the end user (i.e.…”

“…the designer), and of eliciting knowledge from product and manufacturing experts. Hickey and Davis (2002) shows the iterative model of Software Development (Hickey and Davis, 2002). This is based on a time series of successively more sophisticated systems.…”

Requirement Elicitation Techniques for Open Source Systems: A Review

“…As discussed in the previous sections that there multiple techniques for requirement elicitation in developing a software system [10], [11]. There are some requirement elicitation techniques which can be as it is used for open source systems as they are used for traditional systems for example [13].…”