Paper Info
Title
Requirement ambiguity not as important as expected: results of an empirical evaluation
Abstract
[Context and motivation] Requirement ambiguity is seen as an important factor for project success. However, empirical data about this relation are limited. [Question/problem] We analyze how ambiguous requirements relate to the success of software projects. [Principal ideas/results] Three methods are used to study the relation between requirement ambiguity and project success. First, data about requirements and project outcome were collected for 40 industrial projects. We find that, based on a correlation analysis, that the level of ambiguity in the requirements for a project does not correlate with the project's success. Second, using a root-cause analysis, we observe that ambiguity does not cause more defects during the test phase. Third, expert interviews were conducted to validate these results. This resulted in a framework that outlines factors influencing requirement-ambiguity risk. [Contribution] Empirical data are presented about the relationship between requirement ambiguity and project success. A framework is created to describe nine factors that increase or mitigate requirement-ambiguity risk.
Year
DOI
Venue
2013
10.1007/978-3-642-37422-7_5
REFSQ
Keywords
Field
DocType
project outcome,software project,root-cause analysis,requirement-ambiguity risk,requirement ambiguity,industrial project,correlation analysis,ambiguous requirement,project success,empirical data,empirical evaluation,requirements engineering,empirical study
Systems engineering,Computer science,Requirements engineering,Natural language analysis,Software,Ambiguity,Correlation analysis,Empirical research,Management science,Project success
Conference
Citations 
PageRank 
References 
4
0.48
5
Authors
5
Name
Order
Citations
PageRank
Erik Jan Philippo140.48
Werner Heijstek2876.76
Bas Kruiswijk340.48
Michel R. V. Chaudron469366.15
Daniel M. Berry51091148.76