Home > Research > Publications & Outputs > Requirements fixation

Research

Associated organisational units

Links

Text available via DOI:

Keywords

View graph of relations

Requirements fixation

Research output: Contribution in Book/Report/Proceedings - With ISBN/ISSN › Conference contribution/Paper › peer-review

Published

Standard

Requirements fixation. / Mohanani, Rahul; Ralph, Paul; Shreeve, Ben.
ICSE 2014 Proceedings of the 36th International Conference on Software Engineering . New York: ACM, 2014. p. 895-906.

Research output: Contribution in Book/Report/Proceedings - With ISBN/ISSN › Conference contribution/Paper › peer-review

Harvard

Mohanani, R, Ralph, P & Shreeve, B 2014, Requirements fixation. in ICSE 2014 Proceedings of the 36th International Conference on Software Engineering . ACM, New York, pp. 895-906, the 36th International Conference, United Kingdom, 31/05/14. https://doi.org/10.1145/2568225.2568235

APA

Mohanani, R., Ralph, P., & Shreeve, B. (2014). Requirements fixation. In ICSE 2014 Proceedings of the 36th International Conference on Software Engineering (pp. 895-906). ACM. https://doi.org/10.1145/2568225.2568235

Vancouver

Mohanani R, Ralph P, Shreeve B. Requirements fixation. In ICSE 2014 Proceedings of the 36th International Conference on Software Engineering . New York: ACM. 2014. p. 895-906 doi: 10.1145/2568225.2568235

Author

Mohanani, Rahul ; Ralph, Paul ; Shreeve, Ben. / Requirements fixation. ICSE 2014 Proceedings of the 36th International Conference on Software Engineering . New York : ACM, 2014. pp. 895-906

Bibtex

@inproceedings{ab969639a10e45998781ea9186ddf6f4,
title = "Requirements fixation",
abstract = "There is a broad consensus that understanding system desiderata (requirements) and design creativity are both important for software engineering success. However, little research has addressed the relationship between design creativity and the way requirements are framed or presented. This paper therefore aims to investigate the possibility that the way desiderata are framed or presented can affect design creativity. Forty two participants took part in a randomized control trial where one group received desiderata framed as “requirements” while the other received desiderata framed as “ideas”. Participants produced design concepts which were judged for originality. Participants who received requirements framing produced significantly less original designs than participants who received ideas framing (Mann-Whitney U=116.5, p=0.004). We conclude that framing desiderata as “requirements” may cause requirements fixation where designers{\textquoteright} preoccupation with satisfying explicit requirements inhibits their creativity. ",
keywords = "Design Creativity, Requirements, Cognitive Bias, Randomized",
author = "Rahul Mohanani and Paul Ralph and Ben Shreeve",
year = "2014",
doi = "10.1145/2568225.2568235",
language = "English",
isbn = "9781450327565 ",
pages = "895--906",
booktitle = "ICSE 2014 Proceedings of the 36th International Conference on Software Engineering",
publisher = "ACM",
note = "the 36th International Conference ; Conference date: 31-05-2014 Through 07-06-2014",

}

RIS

TY - GEN

T1 - Requirements fixation

AU - Mohanani, Rahul

AU - Ralph, Paul

AU - Shreeve, Ben

PY - 2014

Y1 - 2014

N2 - There is a broad consensus that understanding system desiderata (requirements) and design creativity are both important for software engineering success. However, little research has addressed the relationship between design creativity and the way requirements are framed or presented. This paper therefore aims to investigate the possibility that the way desiderata are framed or presented can affect design creativity. Forty two participants took part in a randomized control trial where one group received desiderata framed as “requirements” while the other received desiderata framed as “ideas”. Participants produced design concepts which were judged for originality. Participants who received requirements framing produced significantly less original designs than participants who received ideas framing (Mann-Whitney U=116.5, p=0.004). We conclude that framing desiderata as “requirements” may cause requirements fixation where designers’ preoccupation with satisfying explicit requirements inhibits their creativity.

AB - There is a broad consensus that understanding system desiderata (requirements) and design creativity are both important for software engineering success. However, little research has addressed the relationship between design creativity and the way requirements are framed or presented. This paper therefore aims to investigate the possibility that the way desiderata are framed or presented can affect design creativity. Forty two participants took part in a randomized control trial where one group received desiderata framed as “requirements” while the other received desiderata framed as “ideas”. Participants produced design concepts which were judged for originality. Participants who received requirements framing produced significantly less original designs than participants who received ideas framing (Mann-Whitney U=116.5, p=0.004). We conclude that framing desiderata as “requirements” may cause requirements fixation where designers’ preoccupation with satisfying explicit requirements inhibits their creativity.

KW - Design Creativity

KW - Requirements

KW - Cognitive Bias

KW - Randomized

U2 - 10.1145/2568225.2568235

DO - 10.1145/2568225.2568235

M3 - Conference contribution/Paper

SN - 9781450327565

SP - 895

EP - 906

BT - ICSE 2014 Proceedings of the 36th International Conference on Software Engineering

PB - ACM

CY - New York

T2 - the 36th International Conference

Y2 - 31 May 2014 through 7 June 2014

ER -