Requirements Practices: A Comparative Industrial Survey

Evidence suggests that some of the most common and serious problems associated with developing software can be traced back to requirements management [12]. Organizations that implement effective requirements engineering (RE) practices reap multiple benefits, with great rewards coming from the reduction of rework during later development stages and throughout maintenance [26]. We believe that it is important to examine what RE practices are actually used and which of these practices lead to good requirements. If we know what is really going on we are able to position our research within an appropriate context [5]. A survey, developed by Verner and Cerpa was used to describe requirements and project management practices in organizations in the United States and Australia [21, 22, 23, 24]. The survey was originally developed as a result of discussions held with U.S. developers and includes factors they considered important for project success. The Verner and Cerpa survey is used here to provide data on Chilean practitioners’ views regarding software project success and failure, and the practices they consider important to software development projects. We compare the Chilean practices with those from the U.S. to help in understanding which practices are universal and which may be culturally dependent.

[1]  Gerald M. Weinberg,et al.  Exploring Requirements: Quality Before Design , 1989 .

[2]  Capers Jones,et al.  Assessment and control of software risks , 1994, Yourdon Press Computing Series.

[3]  Tor Guimaraes,et al.  Successful Strategies for User Participation in Systems Development , 1997, J. Manag. Inf. Syst..

[4]  Sergio Bandinelli,et al.  Supporting Cooperation in the SPADE-1 Environment , 1996, IEEE Trans. Software Eng..

[5]  Robert L. Glass,et al.  How not to prepare for a consulting assignment, and other ugly consultancy truths , 1998, CACM.

[6]  C. Clavadetscher User involvement: key to success , 1998 .

[7]  Buford D. Tackett,et al.  Process Control for Error-Free Software: A Software Success Story , 1999, IEEE Softw..

[8]  June M. Verner,et al.  In the 25 years since The Mythical Man-Month what have we learned about project management? , 1999, Inf. Softw. Technol..

[9]  Dean Leffingwell,et al.  Managing software requirements: a unified approach , 1999 .

[10]  Karl E. Wiegers,et al.  Software Requirements , 1999 .

[11]  James Robertson,et al.  Requirements Management: A Cinderella Story , 2000, Requirements Engineering.

[12]  Mark C. Paulk,et al.  Capability Maturity Model for Software , 2001 .

[13]  Barry Boehm,et al.  Top 10 list [software development] , 2001 .

[14]  Robert L. Glass,et al.  Loyal Opposition - Frequently Forgotten Fundamental Facts about Software Engineering , 2001, IEEE Softw..

[15]  T. Addison,et al.  Controlling software project risks: an empirical study of methods used by experienced project managers , 2002 .

[16]  B. Aubert,et al.  A dream project turns nightmare: how flawless software never got implemented , 2003 .

[17]  Joe Saur Review of “Professional Software Development: Shorter Schedules, Higher Quality Products, More Successful Projects, Enhanced by Steve McConnell.” Addison Wesley 2004 , 2003, SOEN.

[18]  Karl Cox,et al.  Requirements Engineering and Software Project Success: an industrial survey in Australia and the U.S , 2005, Australas. J. Inf. Syst..

[19]  June M. Verner,et al.  Australian software development: what software project management practices lead to success? , 2005, 2005 Australian Software Engineering Conference.

[20]  June M. Verner,et al.  In-house software development: what project management practices lead to success? , 2005, IEEE Software.