There is a newer version of this record available.

Preprint Open Access

Requirements fixation: How requirements inhibit creativity in software engineering?

Mohanani, Rahul; Ralph, Paul; Turhan, Burak; Mandic, Vladimir


JSON-LD (schema.org) Export

{
  "inLanguage": {
    "alternateName": "eng", 
    "@type": "Language", 
    "name": "English"
  }, 
  "description": "<p>&quot;Desiderata&quot; is a general term for stakeholder needs, desires or preferences. Recent experiments demonstrate that presenting desiderata more formally (as &quot;requirements&quot;) leads to less creative solutions. However, these experiments do not establish how the presentation of desiderata affects design creativity. This study, therefore, aims to explore the cognitive mechanisms by which presenting desiderata as requirements reduces creativity during software design. Forty-two software designers, organized into 21 pairs, participated in a dialog-based protocol study. Their interactions were transcribed and the transcripts were analyzed in two ways: (1) using inductive process coding and (2) using an a-priori coding scheme focusing on fixation and critical thinking. Process coding shows that participants exhibited seven categories of behaviour: making design moves, uncritically accepting, rejecting, grouping, questioning, assuming, and considering quality criteria. Closed coding shows that participants tend to accept given requirements and priority levels while rejecting newer, more innovative design ideas. Overall, the results suggest that more formal presentations of desiderata reduce creativity due to requirements fixation, a cognitive bias in which designers anchor on explicit requirements, hindering critical thinking. More formally, requirements fixation mediates the negative relationship between the formality of desiderata presentation and design creativity.</p>", 
  "license": "https://creativecommons.org/licenses/by/4.0/legalcode", 
  "creator": [
    {
      "affiliation": "fortiss GmbH", 
      "@id": "https://orcid.org/0000-0001-7018-8836", 
      "@type": "Person", 
      "name": "Mohanani, Rahul"
    }, 
    {
      "affiliation": "Dalhousie University", 
      "@id": "https://orcid.org/0000-0002-7411-0857", 
      "@type": "Person", 
      "name": "Ralph, Paul"
    }, 
    {
      "affiliation": "Monash University", 
      "@id": "https://orcid.org/0000-0003-1511-2163", 
      "@type": "Person", 
      "name": "Turhan, Burak"
    }, 
    {
      "affiliation": "University of Novi Sad", 
      "@id": "https://orcid.org/0000-0001-6996-2222", 
      "@type": "Person", 
      "name": "Mandic, Vladimir"
    }
  ], 
  "headline": "Requirements fixation: How requirements inhibit creativity in software engineering?", 
  "image": "https://zenodo.org/static/img/logos/zenodo-gradient-round.svg", 
  "datePublished": "2020-08-30", 
  "url": "https://zenodo.org/record/4106670", 
  "version": "1.0", 
  "keywords": [
    "cognitive bias", 
    "software design", 
    "fixation", 
    "critical thinking", 
    "requirements", 
    "requirements engineering", 
    "protocol analysis"
  ], 
  "@context": "https://schema.org/", 
  "identifier": "https://doi.org/10.5281/zenodo.4106670", 
  "@id": "https://doi.org/10.5281/zenodo.4106670", 
  "@type": "ScholarlyArticle", 
  "name": "Requirements fixation: How requirements inhibit creativity in software engineering?"
}
40
40
views
downloads
All versions This version
Views 4016
Downloads 4018
Data volume 128.3 MB73.7 MB
Unique views 3114
Unique downloads 3216

Share

Cite as