A Case Study on Overcoming the Requirements Tar Pit

Software requirements are defined in many industries using informal software requirements specifications that are based on standards such as IEEE 830. Also, in teams of small to medium-sized projects there are often no experienced requirements engineers. These two factors leave product development efforts in a tar pit of ambiguities and misunderstandings that is risking product success. We investigated the adoption of systematic requirements engineering techniques in such a mid-sized software development project. We show how the project found itself in this tar pit and went through several failing attempts of using methods believed appropriate to finally discover and tailor a non-standard approach that led to a massive improvement of the requirements for the product to be developed.

[1]  Kalle Lyytinen,et al.  How to Combine Tools and Methods in Practice - a Field Study , 1990, CAiSE.

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

[3]  Ivar Jacobson,et al.  The Unified Modeling Language User Guide , 1998, J. Database Manag..

[4]  Kari Smolander,et al.  Filtering, Negotiating and Shifting in the Understanding of Information System Requirements , 2005, Scand. J. Inf. Syst..

[5]  Martin Glinz,et al.  Problems and deficiencies of UML as a requirements specification language , 2000, Tenth International Workshop on Software Specification and Design. IWSSD-10 2000.

[6]  Anders Henriksson,et al.  A Definition of Round-trip Engineering , 2003 .

[7]  Brian Fitzgerald,et al.  Formalized systems development methodologies: a critical perspective , 1996, Inf. Syst. J..

[8]  Karen Holtzblatt,et al.  Contextual design , 1997, INTR.

[9]  Douglas T. Ross,et al.  Structured Analysis (SA): A Language for Communicating Ideas , 1977, IEEE Transactions on Software Engineering.

[10]  George Fairbanks,et al.  Why can't they create architecture models like "Developer X"? An experience report , 2003, 25th International Conference on Software Engineering, 2003. Proceedings..

[11]  Hans Eriksson,et al.  Business Modeling With UML: Business Patterns at Work , 2000 .

[12]  J. M. Singer,et al.  IEEE Recommended Practice for Software Requirements SpeciÞcations , 1993 .