
doi: 10.1109/seaa.2014.77
Collecting, understanding, and managing requirements are critical aspects in all development methods including agile methods as well. Nevertheless, little contemporary data exists for document actual practices of software professionals for software requirements engineering activities in agile environments. To remedy this deficiency and provide useful data to other researchers we conducted a survey study that drew participants from wide range of professions, industries and geographic locations. We filtered the survey responses according to the Software Development Life Cycle, then we analyzed how agile processes (compared to traditional waterfall model) deal with a paradox of requirements engineering. In this paper, we present this exploratory survey and its quantitative results.
| selected citations These citations are derived from selected sources. This is an alternative to the "Influence" indicator, which also reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | 21 | |
| popularity This indicator reflects the "current" impact/attention (the "hype") of an article in the research community at large, based on the underlying citation network. | Top 10% | |
| influence This indicator reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | Top 10% | |
| impulse This indicator reflects the initial momentum of an article directly after its publication, based on the underlying citation network. | Average |
