Managing changes in requirements: an empirical investigation

This paper describes the challenges of handling changing requirements in software companies. This empirical investigation deals with the different sources of changes and with the different approaches to requirements evolution. We have considered the point of view of 35 managers of software companies interviewed through a questionnaire. The final results highlight some areas to improve requirements engineering and requirements management. Copyright © 2013 John Wiley & Sons, Ltd.

[1]  Giancarlo Succi,et al.  Modeling Spontaneous Pair Programming When New Developers Join a Team , 2009, XP.

[2]  Alberto Sillitti,et al.  Knowledge Extraction from Events Flows , 2012, ArtDeco.

[3]  Alberto Sillitti,et al.  Automated Identification of Tasks in Development Sessions , 2008, 2008 16th IEEE International Conference on Program Comprehension.

[4]  Bashar Nuseibeh,et al.  Requirements engineering: a roadmap , 2000, ICSE '00.

[5]  R. Verganti.  Planned Flexibility: Linking Anticipation and Reaction in Product Development Projects , 1999 .

[6]  Alberto Sillitti,et al.  Introducing the OpenSource Maturity Model , 2009, 2009 ICSE Workshop on Emerging Trends in Free/Libre/Open Source Software Research and Development.

[7]  Daniel M. Berry,et al.  The Inevitable Pain of Software Development: Why There Is No Silver Bullet , 2002, RISSEF.

[8]  Lorin J. May.  Major Causes of Software Project Failures , 2007 .

[9]  M. Lorentzon.  Doing Qualitative Research , 1993 .

[10]  Hossein Saiedian,et al.  Requirements engineering: making the connection between the software developer and customer , 2000, Inf. Softw. Technol..

[11]  A. Sillitti,et al.  Automated Segmentation of Development Sessions Into Task-Related Subsections , 2009 .

[12]  Alberto Sillitti,et al.  A multivariate classification of open source developers , 2013, Inf. Sci..

[13]  Charles Richter,et al.  A review of the state of the practice in requirements modeling , 1993, [1993] Proceedings of the IEEE International Symposium on Requirements Engineering.

[14]  George Stark.  An Examination of the Effects of Requirements Changes on Software Releases , 1998 .

[15]  Luca Molteni,et al.  Le ricerche di mercato , 2009 .

[16]  Bill Curtis,et al.  A field study of the software design process for large systems , 1988, CACM.

[17]  Joseph A. Goguen,et al.  Techniques for requirements elicitation , 1993, [1993] Proceedings of the IEEE International Symposium on Requirements Engineering.

[18]  Marco Scotto,et al.  Open Source Development Process: a Review , 2006, SEKE.

[19]  Steve Easterbrook,et al.  Communication Problems in Requirements Engineering: A Field Study , 1996 .

[20]  Alberto Sillitti,et al.  DroidSense: A Mobile Tool to Analyze Software Development Processes by Measuring Team Proximity , 2012, TOOLS.

[21]  Khaled El Emam,et al.  Measuring the success of requirements engineering processes , 1995, Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE'95).

[22]  Robert W. Zmud,et al.  A Synthesis of Research on Requirements Analysis and Knowledge Acquisition Techniques , 1992, MIS Q..

[23]  James G. March,et al.  Theories of choice and making decisions , 1982 .

[24]  Alberto Sillitti,et al.  Understanding the impact of Pair Programming on developers attention: A case study on a large industrial experimentation , 2012, 2012 34th International Conference on Software Engineering (ICSE).

[25]  V. Basili.  Software modeling and measurement: the Goal/Question/Metric paradigm , 1992 .

[26]  S.D.P. Harker,et al.  The change and evolution of requirements as a challenge to the practice of software engineering , 1993, [1993] Proceedings of the IEEE International Symposium on Requirements Engineering.

[27]  OmanPaul,et al.  An examination of the effects of requirements changes on software maintenance releases , 1999 .

[28]  J. T. Lochner.  The Journal of Defense Software Engineering , 1999 .

[29]  S. Presser,et al.  Survey Questions: Handcrafting the Standardized Questionnaire. , 1988 .

[30]  Giorgio Orsi,et al.  Methodologies and Technologies for Networked Enterprises , 2012, Lecture Notes in Computer Science.

[31]  David A. Cook,et al.  Requirements Risks Can Drown Software Projects , 2002 .

[32]  Frederick P. Brooks,et al.  No Silver Bullet: Essence and Accidents of Software Engineering , 1987 .

[33]  Alberto Sillitti,et al.  Failure prediction based on log files using Random Indexing and Support Vector Machines , 2013, J. Syst. Softw..

[34]  Åsa Grehag.  Requirements Management in a Life Cycle Perspective – A Position Paper , 2001 .