requirements uncertainty: influencing factors and concrete improvements

Practically all industry studies on software project results conclude that good requirements engineering plays a pivotal role for successful projects. A key reason for project failures is insufficient management of changing requirements during all stages of the project life cycle. This article investigates one of the root causes for changing requirements, namely requirements uncertainty. In an experimental field study we looked into four underlying drivers for requirements uncertainty. We found several techniques must be used simultaneously to see tangible success. Using only one such technique in isolation doesn't make a difference. The field study is supported by extensive data from well over 200 projects stemming from very different business areas of Alcatel over a period of two years. Results are presented with practical experiences to allow effective transfer.

[1]  Axel Völker,et al.  Requirements interdependencies and stakeholders preferences , 2002, Proceedings IEEE Joint International Conference on Requirements Engineering.

[2]  Klaus Schmid.  A comprehensive product line scoping approach and its validation , 2002, ICSE '02.

[3]  Matthias Jarke,et al.  Toward Reference Models of Requirements Traceability , 2001, IEEE Trans. Software Eng..

[4]  Gordon B. Davis,et al.  Strategies for Information Requirements Determination , 1982, IBM Syst. J..

[5]  M. R. Strens,et al.  Change analysis: a step towards meeting the challenge of changing requirements , 1996, Proceedings IEEE Symposium and Workshop on Engineering of Computer-Based Systems.

[6]  Michael E. McGrath.  Next Generation Product Development: How to Increase Productivity, Cut Costs, and Reduce Cycle Times , 2004 .

[7]  Dar-Biau Liu,et al.  Metrics for requirements engineering , 1995, J. Syst. Softw..

[8]  Matthias Jarke,et al.  Cooperative Information Systems: A Manifesto * , 1997 .

[9]  David Lorge Parnas,et al.  Review of David L. Parnas' "Designing Software for Ease of Extension and Contraction" , 2004 .

[10]  Barbara Paech,et al.  Requirements engineering process improvement based on an information model , 2004, Proceedings. 12th IEEE International Requirements Engineering Conference, 2004..

[11]  Walker Royce,et al.  Software Project Management: A Unified Framework , 1998 .

[12]  Barry W. Boehm,et al.  A spiral model of software development and enhancement , 1986, Computer.

[13]  Anthony Finkelstein,et al.  Requirements stability assessment using scenarios , 2003, Proceedings. 11th IEEE International Requirements Engineering Conference, 2003..

[14]  Capers Jones,et al.  Software Assessments, Benchmarks, and Best Practices , 2000 .

[15]  Alan M. Davis,et al.  Elicitation technique selection: how do experts do it? , 2003, Proceedings. 11th IEEE International Requirements Engineering Conference, 2003..

[16]  Timo Saarinen,et al.  Managing the risks of information systems implementation , 1993 .

[17]  Holger Doernemann.  Tool-based risk management made practical , 2002, Proceedings IEEE Joint International Conference on Requirements Engineering.