requirements uncertainty: influencing factors and concrete improvements

ABSTRACT

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.

REFERENCES

• 1: Barry W. Boehm, A Spiral Model of Software Development and Enhancement, Computer, v.21 n.5, p.61-72, May 1988 [doi>10.1109/2.59]
• 2: David Bush , Anthony Finkelstein, Requirements Stability Assessment Using Scenarios, Proceedings of the 11th IEEE International Conference on Requirements Engineering, p.23, September 08-12, 2003
• 3: Mary Beth Chrissis , Mike Konrad , Sandy Shrum, CMMI Guidlines for Process Integration and Product Improvement, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 2003
• 4: Rita J. Costello , Dar-Biau Liu, Metrics for requirements engineering, Journal of Systems and Software, v.29 n.1, p.39-63, April 1995
• 5: Davis, G.B.: Strategies for information requirements determination. IBM Systems Journal, Vol. 21, No. 1, pp. 3--30, 1982.
• 6: DeMichelis, G., E. Dubois, M. Jarke, F. Matthes, J. Mylopoulos, M. Papazoglou, K. Pohl, J. Schmidt, C. Woo, E. Yu:
• 7: Holger Doernemann, Tool-Based Risk Management Made Practical, Proceedings of the 10th Anniversary IEEE Joint International Conference on Requirements Engineering, p.192, September 09-13, 2002
• 8: Joerg Doerr , Barbara Paech , Mathias Koehler, Requirements Engineering Process Improvement Based on an Information Model, Proceedings of the Requirements Engineering Conference, 12th IEEE International (RE'04), p.70-79, September 06-10, 2004 [doi>10.1109/RE.2004.42]
• 9: Christof Ebert , Reiner Dumke , Manfred Bundschuh , Andreas Schmietendorf , Rainer Dumke, Best Practices in Software Measurement, SpringerVerlag, 2004
• 10: Free On-Line Dictionary of Computing. http://foldoc.doc.ic.ac.uk/foldoc/foldoc.cgi?query=requirement&action=Search. Queried on 07.July 2004.
• 11: Galetta, D.F. and M. El Loudadi: L'effet de l'incertidue et des strategies de determination des besoins de l'utilisateur sur les projets d'informatisation. Canadian Journal of Administrative Systems. Vol. 12, No. 1, pp. 56--76, 1995.
• 12: Joachim Giesen , Axel Völker, Requirements Interdependencies and Stakeholders Preferences, Proceedings of the 10th Anniversary IEEE Joint International Conference on Requirements Engineering, p.206-212, September 09-13, 2002
• 13: Gorchels, L.: The Product Manager's Handbook : The Complete Product Management Resource. McGraw-Hill, second edition, New York, 2000.
• 14: Ann M. Hickey , Alan M. Davis, Elicitation Technique Selection: How Do Experts Do It?, Proceedings of the 11th IEEE International Conference on Requirements Engineering, p.169, September 08-12, 2003
• 15: IEEE Standard 610.12-1990. IEEE Standard Glossary of Software Engineering Terminology. IEEE, New York, NY, USA. ISBN 1-55937-067-X (1990).
• 16: Capers Jones, Software assessments, benchmarks, and best practices, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 2000
• 17: McGrath, M.E.: Next Generation Product Development: How to Increase Productivity, Cut Costs, and Reduce Cycle Times. McGraw-Hill, New York, 2004.
• 18: Naumann, J.D., A.M. Jenkins, and J.C. Wetherbe: The Information Requirements Determination Contingency Model: An Empirical Investigation. University of Minnesota, Minneapolis, MIS Research Center, Report 83--15, 1983.
• 19: Parnas, D.L.: Designing Software for Ease of Extension and Contraction. IEEE Trans. On Software Engineering. Vol. 5, No. 2, 1979.
• 20: Balasubramaniam Ramesh , Matthias Jarke, Toward Reference Models for Requirements Traceability, IEEE Transactions on Software Engineering, v.27 n.1, p.58-93, January 2001 [doi>10.1109/32.895989]
• 21: Walker Royce, Software project management: a unified framework, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 1998
• 22: Saarinen, T. and A.Vepsalainen: Managing the Risks of Information Systems Implementation. European Journal of Information Systems. Vol. 2, No. 4, pp. 283--295, 1993.
• 23: Klaus Schmid, A comprehensive product line scoping approach and its validation, Proceedings of the 24th International Conference on Software Engineering, May 19-25, 2002, Orlando, Florida [doi>10.1145/581339.581415]
• 24: The Standish Group International Inc.: CHAOS Chronicles v3.0. http://www.standishgroup.com/chaos/toc.php. West Yarmouth, USA, 2003.
• 25: M. R. Strens , R. C. Sugden, Change Analysis: A Step towards Meeting the Challenge of Changing Requirements, Proceedings of the IEEE Symposium and Workshop on Engineering of Computer Based Systems, p.278, March 11-15, 1996

INDEX TERMS

Primary Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.1 Requirements/Specifications
          Subjects: Elicitation methods (e.g., rapid prototyping, interviews, JAD)

Additional Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.1 Requirements/Specifications
          Subjects: Methodologies (e.g., object-oriented, structured)

  K. Computing Milieux
  K.6 MANAGEMENT OF COMPUTING AND INFORMATION SYSTEMS
      K.6.1 Project and People Management
          Subjects: Management techniques (e.g., PERT/CPM); Life cycle

General Terms:
Management

Keywords:
process improvement, product life cycle, product management, requirements engineering, requirements uncertainty