Requirement Documents that Win the Race : Not Overweight or Emaciated but Powerful and in Shape
暂无分享,去创建一个
[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 .