This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Status Report: Requirements Engineering
November/December 1993 (vol. 10 no. 6)
pp. 75-79

It is argued that, in general, requirements engineering produces one large document, written in a natural language, that few people bother to read. Projects that do read and follow the document often build systems that do not satisfy needs. The reasons for the current state of the practice are listed. Research areas that have significant payoff potential, including improving natural-language specifications, rapid prototyping and requirements animation, requirements clustering, requirements-based testing, computer-aided requirements engineering, requirements reuse, research into methods, knowledge engineering, formal methods, and a unified framework, are outlined.

Index Terms:
requirements engineering; natural language; natural-language specifications; rapid prototyping; requirements animation; requirements clustering; requirements-based testing; computer-aided requirements engineering; requirements reuse; research; knowledge engineering; formal methods; formal specification; software engineering; software prototyping
Citation:
Pei Hsia, Alan Davis, David Kung, "Status Report: Requirements Engineering," IEEE Software, vol. 10, no. 6, pp. 75-79, Nov.-Dec. 1993, doi:10.1109/52.241974
Usage of this product signifies your acceptance of the Terms of Use.