• DOI:10.1109/TWINPEAKS.2015.12
• Corpus ID: 2873385

Is Requirements Engineering Inherently Counterproductive?

@article{Ralph2015IsRE,
  title={Is Requirements Engineering Inherently Counterproductive?},
  author={Paul Ralph and Rahul Mohanani},
  journal={2015 IEEE/ACM 5th International Workshop on the Twin Peaks of Requirements and Architecture},
  year={2015},
  pages={20-23}
}

• P. Ralph, Rahul Mohanani
• Published 16 May 2015
• Computer Science
• 2015 IEEE/ACM 5th International Workshop on the Twin Peaks of Requirements and Architecture

This paper explores the possibility that requirements engineering is, in principle, detrimental to software project success. Requirements engineering is conceptually divided into two distinct processes: sense making (learning about the project context) and problem structuring (specifying problems, goals, requirements, constraints, etc.). An interdisciplinary literature review revealed substantial evidence that while sense making improves design performance, problem structuring reduces design performance. Future research should therefore investigate decoupling the sense making aspects of requirements engineering from the problem structuring aspects.