The Illusion of requirements in software development

Ralph, Paul (2013) The Illusion of requirements in software development. Requirements Engineering, 18 (3). pp. 293-296. ISSN 0947-3602

Full text not available from this repository.


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 another approach, which would achieve the goal without any commonality with known approaches. In these situations of sparse requirements, analysts may misrepresent design decisions as requirements, creating an illusion of requirements in software development.

Item Type:
Journal Article
Journal or Publication Title:
Requirements Engineering
Uncontrolled Keywords:
ID Code:
Deposited By:
Deposited On:
22 Nov 2012 13:10
Last Modified:
21 Nov 2022 23:07