Requirements Experience in Practice: Studies of Six Companies

To understand how to apply different requirements engineering practices and where difficulties may arise when implementing a set of requirements engineering practices, it is often useful to consider how others have done and the troubles they have encountered. This chapter describes six industry cases of applied requirements engineering, with a focus on areas where further improvements are desired by or recommended to the companies. Many of these improvement areas are also identified by other, independent, requirements engineering state of practice surveys, and thus indicate areas that warrant special attention when constructing a requirements engineering process for an organization.

[1]  Ian Sommerville,et al.  Requirements Engineering: Processes and Techniques , 1998 .

[2]  Magne Jørgensen,et al.  Can you Trust a Single Data Source Exploratory Software Engineering Case Study? , 2002, Empirical Software Engineering.

[3]  Tony Gorschek,et al.  A Method for Assessing Requirements Engineering Process Maturity in Software Projects , 2002 .

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

[5]  Thilo Schwinn,et al.  An Industrial Case Study to Examine a Non-Traditional Inspection Implementation for Requirements Specifications , 2002, Proceedings Eighth IEEE Symposium on Software Metrics.

[6]  Pete Sawyer,et al.  Requirements Engineering: A Good Practice Guide , 1997 .

[7]  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.

[8]  Glen Hass Configuration Management Principles and Practice , 2003 .

[9]  Mark C. Paulk,et al.  The Capability Maturity Model: Guidelines for Improving the Software Process , 1994 .

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

[11]  Tony Gorschek,et al.  Packaging software process improvement issues: a method and a case study , 2004, Softw. Pract. Exp..

[12]  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).

[13]  Victor R. Basili,et al.  Quantitative Evaluation of Software Methodology , 1985 .

[14]  Joseph A. Goguen,et al.  Requirements engineering: social and technical issues , 1994 .

[15]  Ian Sommerville,et al.  Capturing the Benefits of Requirements Engineering , 1999, IEEE Softw..

[16]  Tony Gorschek,et al.  Software Process Assessment & Improvement in Industrial Requirements Engineering , 2004 .

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

[18]  Khaled El Emam,et al.  Elements of Software Process Assessment & Improvement , 1999 .

[19]  Steven R. Rakitin,et al.  Software verification and validation for practitioners and managers , 2001 .

[20]  Donald J Reifer The CMMI: it's formidable , 2000, J. Syst. Softw..

[21]  Sami Zahran Software process improvement - practical guidelines for business success , 1998 .

[22]  Heikki Kälviäinen,et al.  A State-of-the-Practice Survey on Requirements Engineering in Small- and Medium-Sized Enterprises , 2000 .

[23]  Forrest Shull,et al.  How perspective-based reading can improve requirements inspections , 2000, Computer.

[24]  Lionel C. Briand,et al.  AINSI: an inductive method for software process improvement: concrete steps and guidelines , 1995 .

[25]  Natalia Juristo Juzgado,et al.  Is the European Industry Moving toward Solving Requirements Engineering Problems? , 2002, IEEE Softw..