Article PDF
Avoid common mistakes on your manuscript.
References
Yourdon E. Death march. Prentice-Hall, Englewood Cliffs, NJ, 1997
Standish Group. The chaos report. www.standishgroup.com, 1995
Davis A. The harmony of rechoirments. IEEE Software 1998;15(2):6–8
Gause D, Weinberg G. Are your lights on? Dorset House, New York, 1990
Debou C, Fuchs N, Saria H. Selling believable technology. IEEE Software 1993;10(6):22–27
Potts C. Software engineering revisited. IEEE Software 1993;10(5):19–28
Robertson J, Robertson S. Requirements management: a Cinderella story. Requirements Eng 2000;5:134–136
Jackson M. Problem frames. Addison-Wesley, Reading, MA, 2001
Dean D, Lee J, Pendergast M, Hickey A, Nunamaker J. Enabling the effective involvement of multiple users: methods and tools for collaborative software engineering. J Manage Inform Syst 1997- 1998;14(3):179–222
Davis A. Achieving quality in software requirements. Software Quality Professional 1999;1:3
Robertson J, Robertson S. Mastering the requirements process. Addison-Wesley, Reading, MA, 1999
Davis A. Practitioner, heal thyself. IEEE Software 1996;13(3):4–5
Redwine S, Riddle W. Software technology maturity. In IEEE eighth international conference on software engineering, 1985, pp 189–200
Author information
Authors and Affiliations
Rights and permissions
About this article
Cite this article
Davis, A.M., Hickey, A.M. Requirements Researchers: Do We Practice What We Preach?. Requirements Eng 7, 107–111 (2002). https://doi.org/10.1007/s007660200007
Published:
Issue Date:
DOI: https://doi.org/10.1007/s007660200007