Reducing the risk of requirements volatility: findings from an empirical survey

  • Authors:

  • Susan Ferreira;Dan Shunk;James Collofello;Gerald Mackulak;AmyLou Dueck

  • Affiliations:

  • Systems Engineering Research Center, The University of Texas at Arlington, Arlington, TX, U.S.A.;School of Computing, Informatics, and Decision Systems Engineering, Arizona State University, Tempe, AZ, U.S.A.;School of Computing, Informatics, and Decision Systems Engineering, Arizona State University, Tempe, AZ, U.S.A.;School of Computing, Informatics, and Decision Systems Engineering, Arizona State University, Tempe, AZ, U.S.A.;Mayo Clinic, Scottsdale, AZ, U.S.A.

  • Venue:
  • Journal of Software Maintenance and Evolution: Research and Practice
  • Year:
  • 2011

Quantified Score

Hi-index 0.00

Visualization

Abstract

Requirements volatility is a common development project risk that can have severe impacts. An empirical survey of over 300 software project managers and other software development personnel was performed to examine effects of various software development factors on requirements volatility. This paper reports the survey data results showing relationships between a number of software development process factors and requirements volatility. Key software project factors studied for their relationship with requirements volatility include process maturity level and various process techniques used for requirements engineering activities, such as requirements elicitation, prototyping, analysis and modeling, specification, and reviews. Significant correlations between the process factors and requirements volatility resulted from the analysis of some of the factors. The use of particular requirements engineering process techniques showed correlations with lower levels of requirements volatility. Other findings indicated that projects which used some types of prototypes to elicit requirements had higher levels of requirements volatility in later phases of the development cycle than lower levels, as one might expect. The presented results can be used by software development managers to proactively address and possibly mitigate the risk of requirements volatility, and to understand the potential for increased requirements volatility when certain methods are utilized. Copyright © 2010 John Wiley & Sons, Ltd. (An empirical survey of software development managers and other software development personnel was performed to examine the effects of a number of software development factors on requirements volatility. This paper presents key findings showing relationships between factors such as process maturity and various requirements engineering process techniques and requirements volatility. The results can be used to proactively address and possibly mitigate the risk of requirements volatility, and to understand the potential for increased requirements volatility when certain methods are utilized.)