A field study of the requirements engineering practice in Australian software industry

Empirical studies have demonstrated that requirements errors introduced during software development are most numerous in the software life-cycle, making software requirements critical determinants of software quality. This article reports an exploratory study which provides insight into industrial practices with respect to requirements engineering (RE). A combination of both qualitative and quantitative data is collected, using semi-structured interviews and a detailed questionnaire from 28 software projects in 16 Australian companies. The contribution of this RE study is threefold: Firstly, it includes a detailed examination of the characteristics of the RE activities involved in the projects. Secondly, it reconstructs the underlying practiced process models. Thirdly, it compares these models to one another and with a number of well-known process models from RE literature to give insight into the gap between RE theory and practice.

[1]  Pamela J. Hinds,et al.  Distributed Work , 2002 .

[2]  Barry W. Boehm,et al.  Improving Software Productivity , 1987, Computer.

[3]  Armin Eberlein,et al.  Requirements engineering for time-to-market projects , 2002, Proceedings Ninth Annual IEEE International Conference and Workshop on the Engineering of Computer-Based Systems.

[4]  Ian Sommerville,et al.  Requirements process improvement through the phased introduction of good practice , 1997 .

[5]  Donald J. Reifer.  Is the Software Engineering State of the Practice Getting Closer to the State of the Art? , 2003, IEEE Softw..

[6]  Stephen G. MacDonell,et al.  Using prior-phase effort records for re-estimation during software projects , 2003, Proceedings. 5th International Workshop on Enterprise Networking and Computing in Healthcare Industry (IEEE Cat. No.03EX717).

[7]  Paul Dourish,et al.  Awareness and coordination in shared workspaces , 1992, CSCW '92.

[8]  Richard Berntsson-Svensson,et al.  Successful software project and products: An empirical investigation , 2006, ISESE '06.

[9]  S. Weisband.  Maintaining Awareness in Distributed Team Collaboration: Implications for Leadership and Performance , 2002 .

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

[11]  Franz Lehner,et al.  Requirements Engineering as a Success Factor in Software Projects , 2001, IEEE Softw..

[12]  Sjaak Brinkkemper,et al.  Method engineering : principles of method construction and tool support : proceedings of the IFIP TC8, WG8.1/8.2 Working Conference on Method Engineering, 26-28 August 1996, Atlanta, USA , 1996 .

[13]  Claes Wohlin,et al.  Engineering and Managing Software Requirements , 2005 .

[14]  James D. Arthur,et al.  An operational model for structuring the requirements generation process , 2004, Requirements Engineering.

[15]  Marcelo Masera,et al.  Requirements engineering and industrial uptake , 1998, Proceedings of IEEE International Symposium on Requirements Engineering: RE '98.

[16]  Aybüke Aurum,et al.  Requirements engineering practice in pharmaceutical and healthcare manufacturing , 2004, 11th Asia-Pacific Software Engineering Conference.

[17]  N.H. Madhavji,et al.  Elicit: a method for eliciting process models , 1994, Proceedings of the Third International Conference on the Software Process. Applying the Software Process.

[18]  Pamela J. Hinds,et al.  Maintaining Awareness in Distributed Team Collaboration: Implications for Leadership and Performance , 2002 .

[19]  Richard Berntsson-Svensson,et al.  Successful Software Projects and Products : A quantitative study , 2006 .

[20]  M. Roseman,et al.  A usability study of awareness widgets in a shared workspace groupware system , 1996, CSCW '96.

[21]  Linda A. Macaulay,et al.  Requirements capture and analysis: A survey of current practice , 1996, Requirements Engineering.

[22]  Olivier Liechti,et al.  Awareness and the WWW: an overview , 2000, SIGG.

[23]  Claes Wohlin,et al.  Experimentation in software engineering: an introduction , 2000 .

[24]  Claes Wohlin,et al.  A project effort estimation study , 1998, Inf. Softw. Technol..

[25]  Prodromos D. Chatzoglou,et al.  Factors affecting completion of the requirements capture stage of projects with different characteristics , 1997, Inf. Softw. Technol..

[26]  Axel van Lamsweerde,et al.  Requirements engineering in the year 00: a research perspective , 2000, Proceedings of the 2000 International Conference on Software Engineering. ICSE 2000 the New Millennium.

[27]  Khaled El Emam,et al.  A field study of requirements engineering practices in information systems development , 1995, Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE'95).

[28]  Sjaak Brinkkemper,et al.  Method engineering: engineering of information systems development methods and tools , 1996, Inf. Softw. Technol..

[29]  Alan M. Davis,et al.  Software Requirements: Objects, Functions and States , 1993 .

[30]  R. Kraut,et al.  Awareness and Coordination in Shared Work Spaces , 1992 .

[31]  Magne Jørgensen,et al.  Impact of effort estimates on software project work , 2001, Inf. Softw. Technol..

[32]  Frank Houdek,et al.  Analyzing requirements engineering processes: a case study , 2000, Proceedings 11th International Workshop on Database and Expert Systems Applications.

[33]  Ian Sommerville,et al.  An empirical study of industrial requirements engineering process assessment and improvement , 2005, TSEM.

[34]  Meliha Handzic,et al.  Managing Software Engineering Knowledge , 2010, Springer Berlin Heidelberg.

[35]  Janis A. Bubenko,et al.  Requirements Engineering and Technology Transfer: Obstacles, Incentives and Improvement Agenda , 2002, Requirements Engineering.

[36]  D. Scott McCrickard,et al.  Project management for the 21st century: supporting collaborative design through risk analysis , 2005, ACM Southeast Regional Conference.

[37]  Richard Stevens,et al.  Writing Better Requirements , 2002 .

[38]  Shari Lawrence Pfleeger,et al.  Wavefront: a goal-driven requirements process model , 1996, Inf. Softw. Technol..

[39]  Colette Rolland,et al.  A proposal for context-specific method engineering , 1996 .

[40]  Barbara Paech,et al.  Requirements Engineering Process Models in Practice , 2002 .

[41]  W. W. Royce,et al.  Managing the development of large software systems: concepts and techniques , 1987, ICSE '87.

[42]  Barry W. Boehm,et al.  Using the WinWin Spiral Model: A Case Study , 1998, Computer.

[43]  LeMai Nguyen,et al.  Managing the requirements engineering process , 2003, Requirements Engineering.

[44]  Barry W. Boehm.  Understanding and Controlling Software Costs , 1988 .

[45]  Amrit Tiwana,et al.  An empirical study of the effect of knowledge integration on software development performance , 2004, Inf. Softw. Technol..

[46]  Albert Endres,et al.  A handbook of software and systems engineering - empirical observations, laws and theories , 2003, The Fraunhofer IESE series on software engineering.

[47]  Barbara Paech,et al.  An Analysis of Empirical Requirements Engineering Survey Data , 2005 .

[48]  Pericles Loucopoulos,et al.  System Requirements Engineering , 1995, System Requirements Engineering.

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

[50]  Colin J. Neill,et al.  Requirements Engineering: The State of the Practice , 2003, IEEE Softw..

[51]  Austen Rainer,et al.  Requirements problems in twelve software companies: an empirical analysis , 2002, IEE Proc. Softw..

[52]  Colette Rolland,et al.  An Assembly Process Model for Method Engineering , 2001, CAiSE.