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… 

Figures from this paper

Implications of Requirements Engineering on Software Design: A Cognitive Insight
  • Rahul Mohanani
  • Business
    2016 IEEE/ACM 38th International Conference on Software Engineering Companion (ICSE-C)
  • 2016
TLDR
The foremost objective of this research will be to explore the harmful effects of human cognitive biases on the designers’ ability to generate conceptual designs from a set of requirements, and then to mitigate the harmful results of biases by developing specific de-biasing technique(s) to enhance creativity of such design concepts.
How Templated Requirements Specifications Inhibit Creativity in Software Engineering
TLDR
The results suggest that designers fixate on desiderata presented as templated requirements specifications, hindering critical thinking and requirements fixation mediates the negative relationship between specification formality and creativity.
The Product Backlog
TLDR
The product backlog is simultaneously a model of work to be done and a boundary object that helps bridge the gap between the processes of generating user stories and realizing them in working code.
Requirements Framing Affects Design Creativity
TLDR
The results suggest that more formal, structured presentations of desiderata are less appropriate where more innovative solutions are desired, and that design performance is highly susceptible to minor changes in the vernacular used to communicate Desiderata.
The two paradigms of software development research
  • P. Ralph
  • Computer Science
    Sci. Comput. Program.
  • 2018
RASAECO: Requirements Analysis of Software for the AECO Industry
TLDR
An approach and a tool for collecting AECO-specific software requirements with the aim to foster reuse and leverage domain knowledge is presented and a novel choice of an ubiquitous language well-suited for this particular industry is proposed.
Cross-Functional Teams That Grok It: The Collective Empathic Understanding of Product Requirements
  • R. Fuller
  • Business
    2018 IEEE 26th International Requirements Engineering Conference (RE)
  • 2018
Software development has become increasingly software 'product' development, without the authoritative 'customer' stakeholder role that many requirements engineering processes assume exists in some
A Controlled Experiment with Novice Developers on the Impact of Task Description Granularity on Software Quality in Test-Driven Development
TLDR
For novice TDD practitioners, the outcome of TDD is highly coupled with the ability to break down the task into smaller parts, and task description granularity should be taken into account in secondary studies.
Cognitive Biases in Software Engineering: A Systematic Mapping Study
TLDR
This paper systematically maps, aggregates and synthesizes the literature on cognitive biases in software engineering to generate a comprehensive body of knowledge, understand state-of-the-art research and provide guidelines for future research and practise.
Blurring Boundaries: Toward the Collective Empathic Understanding of Product Requirements
...
...

References

SHOWING 1-10 OF 71 REFERENCES
The illusion of requirements in software development
  • P. Ralph
  • Computer Science
    Requirements Engineering
  • 2012
TLDR
This viewpoint explores the possibility that many software development projects may have no useful requirements, and analysts may misrepresent design decisions as requirements, creating an illusion of requirements in software development.
Requirements engineering: a roadmap
TLDR
An overview of the field of software systems requirements engineering (RE) is presented, describing the main areas of RE practice, and highlights some key open research issues for the future.
A framework for understanding creativity in requirements engineering
The dimensions of software engineering success
TLDR
Investigation of the dimensions of software engineering success suggests that participants view their work as time-constrained projects with explicit clients and other stakeholders, and a proto-theory of success is proposed, which models success as the net impact on a particular stakeholder at a particular time.
Introducing an Empirical Model of Design
TLDR
The Empirical Model is intended to replace the Rational Model as a foundation for design methods and practices, design education and design science research.
Requirements fixation
TLDR
It is concluded that framing desiderata as “requirements” may cause requirements fixation where designers’ preoccupation with satisfying explicit requirements inhibits their creativity.
Knowledge Exploited by Experts during Software System Design
  • R. Guindon
  • Computer Science
    Int. J. Man Mach. Stud.
  • 1990
Systems Thinking, Systems Practice
...
...