The case for dumb requirements engineering tools

  • Authors:
  • Daniel Berry;Ricardo Gacitua;Pete Sawyer;Sri Fatimah Tjong

  • Affiliations:
  • Cheriton School of Computer Science, University of Waterloo, Canada;School of Computing and Communications, Lancaster University, UK;School of Computing and Communications, Lancaster University, UK and INRIA Paris -- Rocquencourt, Le Chesnay, France;University of Nottingham Malaysia Campus, Malaysia

  • Venue:
  • REFSQ'12 Proceedings of the 18th international conference on Requirements Engineering: foundation for software quality
  • Year:
  • 2012

Quantified Score

Hi-index 0.00

Visualization

Abstract

[Context and Motivation] This paper notes the advanced state of the natural language (NL) processing art and considers four broad categories of tools for processing NL requirements documents. These tools are used in a variety of scenarios. The strength of a tool for a NL processing task is measured by its recall and precision. [Question/Problem] In some scenarios, for some tasks, any tool with less than 100% recall is not helpful and the user may be better off doing the task entirely manually. [Principal Ideas/Results] The paper suggests that perhaps a dumb tool doing an identifiable part of such a task may be better than an intelligent tool trying but failing in unidentifiable ways to do the entire task. [Contribution] Perhaps a new direction is needed in research for RE tools.