Modern trends towards requirement elicitation

Sajid, Asma; Nayyar, Ayesha; Mohsin, Athar

doi:10.1145/1890810.1890819

Cited by 14 publications

(10 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…RQ1. What are the issues reported in literature on RE? Brief grouping was identified for ease of documentation: 1) Change-related: management and political rules [7,61], acceptance criteria changes [7], unstable requirements [67], changes in nature of requirements overtime [74], user needs and understanding changes [52] 2) Communication-related: articulation related [63,24,67] ,u naware of needs [63,24,8,40,74], mis-understanding amongst stakeholders [63,3], verbal and presentation skill [61,67], requirements-related [2,61,67], culture and perspective related [8, 9,33], language barriers [8, 65], change related [43] 7) Scope-related: scope ill-defined [25,31,30,8,59], overscoping [14] 8) Stakeholder-related: user-partIcIpation [46,42], stakeholder [25,22,33,74,16,37,56,50,41,69,59,8], staffmg [61,...…”

Section: Resultsmentioning

confidence: 99%

See 1 more Smart Citation

A study on the software requirements elicitation issues - its causes and effects

Kumari.S

Pillai

2013

2013 Third World Congress on Information and Communication Technologies (WICT 2013)

View full text Add to dashboard Cite

Software requirements elicitation is an important and essential pre-requisite to the subsequent phases in software development lifecycle. There is an increasing focus on how industry performs elicitation as this has a direct influence on the overall project success. It is important to understand broader elicitation issues and challenges, and address them on a large-scale, especially on geographically distributed software development. There are studies focusing on elicitation, but they are relatively small. There is no substantial research related to providing a comprehensive view of elicitation issues along with its causes and effects. This paper attempts to provide a summary of the systematic literature review (SLR) findings from 81 papers. The findings are based on causes of poor elicitation, elicitation issues and challenges, consequences of poor elicitation, advisable practices and classification of elicitation issues. The authors have leveraged cause-and-effect diagrams to draw conclusions on SLR.

show abstract

Section: Resultsmentioning

confidence: 99%

“…Several researches present meaningful insights into the features of different types of techniques and methods, based on which a practical guideline for method selection is also suggested [6,9,10,15,18,25,29,38,40,53,54,60,68,75].…”

Section: Introductionmentioning

confidence: 99%

A study on the software requirements elicitation issues - its causes and effects

Kumari.S

Pillai

2013

2013 Third World Congress on Information and Communication Technologies (WICT 2013)

View full text Add to dashboard Cite

show abstract

“…There are four basic categories of requirement elicitation techniques [2]. These are conversational methods, observational methods, analytical methods and synthetic methods.…”

Section: Literature Review:authorsmentioning

confidence: 99%

Requirement Elicitation issues and Challenges in Pakistan Software Industry

Zahid

Liaqat

Farooq

et al. 2018

VFAST trans. softw. eng.

View full text Add to dashboard Cite

Requirement elicitation is the actual description of the system that the software developers follow in the earlier stages of development process. It is one of the most important and primary part in developing a new application or project. It describes what a system should do and what it is capable of doing. There are some essential requirements of a system that must be met for its correct functionality. Many software systems fail due to the wrong requirement elicitation practices or poor requirement elicitation. Without the help of elicitation, it is impossible to find out the needs and the requirements of the user. In Pakistan software industry, requirement elicitation practices are not followed. In this paper, we have analyzed the issues and challenges being faced by the Pakistan software industry due to the poor requirement elicitation process. The identified issues in requirement elicitation process include a change of scope, volatility problem, change in user needs, understanding problem, uncertain requirements, communication problem, and missing requirements.

show abstract

“…1. [24]. Due to the nature of tacit knowledge, these techniques could be complemented with techniques of discourse analysis as in [1], [25].…”

Section: B Knowledge Managementmentioning

confidence: 99%

A Strategy to Requirements Engineering Based on Knowledge Management

Sanchez

Rodas-Osollo

2013

2013 Mexican International Conference on Computer Science

View full text Add to dashboard Cite

In Informal Structured Domains not all concepts and their relations are formally defined, the most of the problems does not have algorithms to obtain solutions, and the domain specialists use large amounts of tacit knowledge to solve problems.These characteristics generate ambiguous, inappropriate and incomplete requirements that could increase the development time of a software system. In order to minimize these problems, we propose a Requirements Engineering strategy based on knowledge management. As a case study, the strategy was used to the development of a software system, which evaluates the cognitive impairment in patients with sclerosis multiple.

show abstract

Modern trends towards requirement elicitation

Cited by 14 publications

References 6 publications

A study on the software requirements elicitation issues - its causes and effects

A study on the software requirements elicitation issues - its causes and effects

Requirement Elicitation issues and Challenges in Pakistan Software Industry

A Strategy to Requirements Engineering Based on Knowledge Management

Contact Info

Product

Resources

About