Requirement Documents that Win the Race : Not Overweight or Emaciated but Powerful and in Shape

Time-constrained projects ask for requirements approaches that are agile, i.e. adapted to the project needs and without comprehensive documentation. But how can this be achieved? Our approach provides the steps toward the solution of this question. It supports the identification of the essential content of the requirements document as well as the selection of the appropriate modeling technique. The essential content is determined by conducting a systematic risk analysis, which allows identifying the most important elements of the requirements documentation. For the requirement document to be useful it must be precise and understandable for all project participants. The appropriate modeling technique is selected by taking the identified content and the context of the project into account. This paper reports work in progress. It describes the motivation, related work and first ideas.

[1]  H. D. Rombach,et al.  THE EXPERIENCE FACTORY , 1999 .

[2]  Andreas Birk,et al.  A knowledge management infrastructure for systematic improvement in software engineering , 2001 .

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

[4]  Jyrki Kontio,et al.  The Riskit Method for Software Risk Management, version 1.00 , 1997 .

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

[6]  Benjamin L. Kovitz,et al.  Practical Software Requirements: A Manual of Content and Style , 1998 .

[7]  Hermann Kaindl Why is it so difficult to introduce requirements engineering research results into mainstream requirements engineering practice? , 2000, Proceedings Fourth International Conference on Requirements Engineering. ICRE 2000. (Cat. No.98TB100219).

[8]  Neil A. M. Maiden,et al.  ACRE: selecting methods for requirements acquisition , 1996, Softw. Eng. J..

[9]  W BoyerKenneth Advanced use case modeling , 2002 .

[10]  David Lorge Parnas,et al.  Documentation of requirements for computer systems , 1993, [1993] Proceedings of the IEEE International Symposium on Requirements Engineering.

[11]  Mordechai Ben-Menachem,et al.  Writing effective use cases , 2001, SOEN.

[12]  Kent L. Beck,et al.  Extreme programming explained - embrace change , 1990 .