Requirements Elicitation Problems: A Literature Analysis

Davey, Bill; Parker, Kevin R.

doi:10.28945/2137

Cited by 19 publications

(17 citation statements)

References 51 publications

(80 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Requirements Elicitation (RE) is the process of seeking, determining and capturing all relevant knowledge to produce software requirements. The elicitation process is a core activity requirements engineering [1] and has a direct influence on the developed software quality [2]. Moreover, this process depends on deliberation and discussion between stakeholders.…”

Section: Introductionmentioning

confidence: 99%

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

2020

View full text Add to dashboard Cite

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.

show abstract

Section: Introductionmentioning

confidence: 99%

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

2020

View full text Add to dashboard Cite

show abstract

“…Without an accurate understanding of what the stakeholders" specification, tendency of projects to be failed is at high degree. It is observed about 12% to 71% of the project failure are attributed to poor requirements [5]. Standish report in 2014 revealed that most of significant factors contribute to the software project challenges are Lack of User Input and Incomplete Requirements.…”

Section: Introductionmentioning

confidence: 99%

Comparative Study between Lean Six Sigma and Lean-Agile for Quality Software Requirement

Salleh¹,

Nohuddin²

2019

IJACSA

View full text Add to dashboard Cite

Requirement Elicitation is one of the challenging phases in the entire software development life cycle. It is the process of extracting and analyzing the requirements from customers to understand thoroughly of what system needs to be built. Despite all the advances in methodologies and practice approaches, extracting and establishing the right requirements are still part of the research debate. The objective of this paper is to compare the characteristics of two hybrid development approaches; Lean Six Sigma vs. Lean Agile. Most of the comparative studies done by most of the research compared within its relative knowledge such as; Lean vs. Six Sigma, Define-Measure-Analyze-Improve-Control vs. Design-For-Six-Sigma or Lean vs. Six Sigma vs Lean Six Sigma. Whereas in software industries, the comparative studies were focused on Lean vs. Agile, Agile vs. Waterfall, Lean vs. Kanban vs.Agile, which compared the project size, process cycle time, sequential or iterative process. The following parts of the study is to explore the differences and similarities in principles and practices. The study contributes significantly to the business analysts to systematically address the solutions and actions to ensure continuous improvement in producing quality software requirement.

show abstract

“…The software risks are more prone during the early phases of software development [4,5]. Moreover, it is critical to define, estimate, and manage risks during the planning phase [6]. The matter of a fact is that the risk of changing requirements cannot be predicted at the planning phase [4,7].…”

Section: Introductionmentioning

confidence: 99%

Proposed Risk Management Model to Handle Changing Requirements

Aljohani¹,

Qureshi²

2019

IJEME

View full text Add to dashboard Cite

The change in requirements while construction of a software may bring into several risks like over budget and extra schedule. The changes in requirements are considered as a high risk to fail the software projects. A good project manager always incorporates risk management paradigm to manage the risks of changing requirements. This research uses available statistical techniques to estimate the cost of risk management with respect to the changing requirement. In addition, a hybrid cost estimation model is proposed using action strategy model to counteract, mitigate and manage the risks of changing requirements. The proposed model is validated using an industrial case study in Saudi Electricity Company (SEC) to conclude the results. The results are found supportive because the proposed model shows significant improvement to estimate the costs of changing requirements as compared to the existing cost estimation models.

show abstract

Requirements Elicitation Problems: A Literature Analysis

Cited by 19 publications

References 51 publications

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

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

Comparative Study between Lean Six Sigma and Lean-Agile for Quality Software Requirement

Proposed Risk Management Model to Handle Changing Requirements

Contact Info

Product

Resources

About