This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
March/April 1994 (vol. 11 no. 2)
pp. 12-16

Developers have plenty of reasons to avoid investing in requirements engineering: It is next to impossible to capture user needs completely, and needs are constantly evolving. The gap between software research and practice is no more evident than in the field of requirements engineering. Requirement engineering has a fairly narrow goal - determine a need and define the external behavior of a solution - but the range of research into requirements is enormous.

Index Terms:
DP management; software engineering; systems analysis; requirements engineering; user needs; software research; software practice; technology transfer
Citation:
Alan M. Davis, Pei Hsia, "Guest Editors' Introduction: Giving Voice to Requirements Engineering," IEEE Software, vol. 11, no. 2, pp. 12-16, March-April 1994, doi:10.1109/52.268949
Usage of this product signifies your acceptance of the Terms of Use.