There is a newer version of this record available.

Preprint Open Access

How Formal Requirements Specifications Inhibit Creativity in Software Engineering

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

Dublin Core Export

<?xml version='1.0' encoding='utf-8'?>
<oai_dc:dc xmlns:dc="" xmlns:oai_dc="" xmlns:xsi="" xsi:schemaLocation="">
  <dc:creator>Mohanani, Rahul</dc:creator>
  <dc:creator>Ralph, Paul</dc:creator>
  <dc:creator>Turhan, Burak</dc:creator>
  <dc:creator>Mandic, Vladimir</dc:creator>
  <dc:description>Desiderata is a general term for stakeholder needs, desires or preferences. Recent experiments demonstrate that presenting desiderata as formal requirements specifications 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 formal requirements specifications 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 representation of desiderata reduce creativity because designers fixate on desiderata presented as formal requirements specifications, hindering critical thinking. More formally, requirements fixation mediates the negative relationship between specification formality and creativity.</dc:description>
  <dc:description>Under-review at IEEE TSE</dc:description>
  <dc:source>IEEE Transactions on Software Engineering</dc:source>
  <dc:subject>cognitive bias</dc:subject>
  <dc:subject>software design</dc:subject>
  <dc:subject>critical thinking</dc:subject>
  <dc:subject>requirements engineering</dc:subject>
  <dc:subject>protocol analysis</dc:subject>
  <dc:title>How Formal Requirements Specifications Inhibit Creativity in Software Engineering</dc:title>
All versions This version
Views 4013
Downloads 4812
Data volume 149.8 MB29.7 MB
Unique views 3110
Unique downloads 4011


Cite as