Your opinion matters! Please fill in the InfoQ Survey!

The Role of Emotions in Software Engineering

| by Michael Stal  Followers on Feb 18, 2012. Estimated reading time: less than one minute |

A note to our readers: As per your request we have developed a set of features that allow you to reduce the noise, while not losing sight of anything that is important. Get email and web notifications by choosing the topics you are interested in.

A recent study by the Carlos III University of Madrid (UC3M) investigates the importance of emotions in software engineering. In the study requirements engineering is considered. There is a good reason for this specific focus. As Ricarda Colomo from the UC3M mentions,

In the world of computer system development consultants, I have often met disappointed users whose unhappiness was produced by a deficient collection of requirements.

The scientists have applied a tool of social psychology, the affect grid invented by J. A. Russel. As the authors of the studies explain,

This instrument provides emotional outlines for different versions of the requirements, in addition to facilitating an analysis of the emotions of those involved in the development of the system.

The results of the study show that emotions need special consideration when negotiating and establishing requirements.

In the press release it is pointed out that previous studies have also shown the impoirtance of emotions in software enginering such as the finding that

listening to music improves the performance of some systems analysts.

The human factor seems to be widely underestimated in software engineering. Eventually, humans create software systems that are used by humans.

Rate this Article

Adoption Stage

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Tell us what you think

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

How ironic by Rick Verdonschot

I was a software developer and I did see the big picture and I warned the project leader that certain functional decisions would lead to unhappy customers (everybody hates slooooooow software, right?). I was told not too look at the big picture but instead focus on the technical details.
2 years later: Software went slow -> Unhappy customers, project leader made sure he was gone before SHTF and then I am the one who gets pushed under pressure to fix the problem. And then this human factor unit crashed...burnout...

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

1 Discuss

Login to InfoQ to interact with what matters most to you.

Recover your password...


Follow your favorite topics and editors

Quick overview of most important highlights in the industry and on the site.


More signal, less noise

Build your own feed by choosing topics you want to read about and editors you want to hear from.


Stay up-to-date

Set up your notifications and don't miss out on content that matters to you