A framework for identifying software project risks
Communications of the ACM
An empirical study of global software development: distance and speed
ICSE '01 Proceedings of the 23rd International Conference on Software Engineering
Agile Software Development with Scrum
Agile Software Development with Scrum
Writing Better Requirements
Mastering the Requirements Process (2nd Edition)
Mastering the Requirements Process (2nd Edition)
An empirical analysis of risk components and performance on software projects
Journal of Systems and Software
Ambiguity in Natural Language Requirements Documents
Innovations for Requirement Analysis. From Stakeholders' Needs to Formal Designs
QuARS Express - A Tool Demonstration
ASE '08 Proceedings of the 2008 23rd IEEE/ACM International Conference on Automated Software Engineering
Requirements Engineering
Hi-index | 0.00 |
[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.