The illusion of requirements in software development
@article{Ralph2012TheIO, title={The illusion of requirements in software development}, author={Paul Ralph}, journal={Requirements Engineering}, year={2012}, volume={18}, pages={293-296} }
This viewpoint explores the possibility that many software development projects may have no useful requirements. Specifically, for problems (e.g., knowledge worker burnout) with two completely different solutions (e.g., better tool support or hire more employees), an analyst may state a goal (e.g., decrease work hours) but more specific desiderata are contingent on the chosen solution. Furthermore, without fully exploring the design space, the designer cannot be sure whether there exists…
40 Citations
Is Requirements Engineering Inherently Counterproductive?
- Computer Science2015 IEEE/ACM 5th International Workshop on the Twin Peaks of Requirements and Architecture
- 2015
This paper explores the possibility that requirements engineering is, in principle, detrimental to software project success and investigates decoupling the sense making aspects of requirements engineering from the problem structuring aspects.
The dimensions of software engineering success
- Computer ScienceICSE
- 2014
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.
The Two Paradigms of Software Design
- Computer ScienceArXiv
- 2013
An Alternative Design Paradigm is synthesized, which views software development as an amethodical, improvisational, emotional process of simultaneously framing the problem and building artifacts to address it.
Developing and Evaluating Software Engineering Process Theories
- Business2015 IEEE/ACM 37th IEEE International Conference on Software Engineering
- 2015
This paper attempts to clarify the nature and types of process theories, explore their development and provide specific guidance for their empirically evaluation.
Implications of Requirements Engineering on Software Design: A Cognitive Insight
- Business2016 IEEE/ACM 38th International Conference on Software Engineering Companion (ICSE-C)
- 2016
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.
New Frontiers for Requirements Engineering
- Computer Science2017 IEEE 25th International Requirements Engineering Conference (RE)
- 2017
An alternative perspective on, and de-scription of, the discipline of RE is discussed and an advocate for the evolution of RE toward a discipline that supports the application of RE prac-tice to any domain is advocated.
Evaluating process theories in software engineering
- BusinessGTSE 2014
- 2014
This paper attempts to clarify the nature of process theories, address some common misconceptions and elucidate the unique issues of process theory evaluation.
Requirements fixation: the effect of specification formality on design creativity
- Business
- 2019
The results of this dissertation suggest that more formal and structured presentations of Desiderata cause requirements fixation, the tendency to attribute undue confidence and importance to desiderata presented as formal requirements statements---that affects design creativity, and thus undermines software engineering success.
How Templated Requirements Specifications Inhibit Creativity in Software Engineering
- Computer ScienceIEEE Transactions on Software Engineering
- 2021
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.
Measuring Customer Satisfaction on Software-Based Products and Services: A Requirements Engineering Perspective
- Computer ScienceICICT
- 2019
To improve customer satisfaction on software products and services, a 2D4E framework based on requirements and reconfiguration engineering (RRE) and total quality management (TQM) is proposed in this study.
References
SHOWING 1-10 OF 35 REFERENCES
Toward a Theory of Debiasing Software Development
- Computer ScienceSIGSAND
- 2011
A theory of the role of cognitive biases in software development project success is proposed and it is posited that such errors are mutual properties of people and tasks; they may therefore be avoided by modifying the person-task system using specific sociotechnical interventions.
The Unified Software Development Process
- Computer Science
- 1999
This book provides a comprehensive guide to The Objectory Software Development Process derived from the three market leading OOA&D methods: Booch, OOSE (Use-Case), and OMT.
Discovering system requirements
- Computer Science
- 1996
This report provides a high-level overview of the system requirements process, explaining types, sources, and characteristics of good requirements, as well as terminology commonly used in the requirements development field.
On Non-Functional Requirements in Software Engineering
- Computer ScienceConceptual Modeling: Foundations and Applications
- 2009
This chapter reviews the state of the art on the treatment of non-functional requirements (hereafter, NFRs), while providing some prospects for future directions.
A taxonomy of current issues in requirements engineering
- Computer ScienceComputer
- 1985
A discussion of various classification criteria for existing requirements specification techniques follows a brief review of requirements specification contents and concerns.
Goal-Oriented Requirements Engineering: A Guided Tour
- Computer ScienceRE
- 2001
The paper compares the main approaches to goal modeling, goal specification and goal-based reasoning in the many activities of the requirements engineering process and suggests what a goal-oriented requirements engineering method may look like.
Experience with user-centred requirements engineering
- Computer ScienceRequirements Engineering
- 2011
The application of human–computer interaction (HCI) principles and methods to requirements engineering in a case study development of a visualisation tool, ADVISES, to support epidemiological research is described.
An analysis of the requirements traceability problem
- Computer ScienceProceedings of IEEE International Conference on Requirements Engineering
- 1994
The distinction between pre-requirements specification (pre-RS) traceability and post-RS traceability is introduced to demonstrate why an all-encompassing solution to the problem is unlikely, and to provide a framework to understand its multifaceted nature.
Towards modelling and reasoning support for early-phase requirements engineering
- Computer ScienceProceedings of ISRE '97: 3rd IEEE International Symposium on Requirements Engineering
- 1997
This paper argues that a different kind of modelling and reasoning support is needed for the early phase of requirements engineering, which aims to model and analyze stakeholder interests and how they might be addressed, or compromised, by various system-and-environment alternatives.
Toward Reference Models of Requirements Traceability
- Computer ScienceIEEE Trans. Software Eng.
- 2001
Four kinds of traceability link types are identified and critical issues that must be resolved for implementing each type and potential solutions are discussed, and implications for the design of next-generation traceability methods and tools are discussed and illustrated.