Navigation auf


Department of Informatics s.e.a.l


Check out Important Dates & News

  • Write response papers and submit them on OLAT before 8pm on Sunday before the lecture. Write in the response paper what you think about the papers/topic and what you find important and interesting. Make sure to check the comments on response papers from the introductory slides. Sample response papers are provided on the sample files site.
  • To sign up for leading a discussion, please enter your name in an empty slot in this spreadsheet.

Tentative Course Schedule

It is important to note that this schedule is susceptible to change.

September 15th - Course Overview

Introduction Slides (PDF, 205 KB)

September 22nd - (Empirical) Research and Information Needs

Papers on Information Needs

Developers' Code Context Models for Change Tasks, Fritz et al.. 22nd ACM SIGSOFT International Symposium on the Foundations of Software Engineering (FSE), 16-21 November 2014.

Information Needs in Collocated Software Development Teams, Ko et al.. 29th International Conference on Software Engineering (ICSE), 20-26 May 2007.

Papers on (Empirical) Research

What makes good research in software engineering?, Shaw, International Journal on Software Tools for Technology, 2002.

Preliminary guidelines for empirical research in software engineering, Kitchenham et al., IEEE Transactions on Software Engineering, 2002.


Experimental models for validating technology, Zelkowitz et al., IEEE Computer, 1998.

September 29th - Biometrics and Emotions in SE

Are Happy Developers more Productive? The Correlation of Affective States of Software Developers ane their-self-assessed productivity, Graziotin et al., Proceedings of the 14th Internationl Conference on Product-Focused Software Process Improvement, 2013.

Do moods affect programmers' debug performance?, Khan et al., Cognition, Technology and Work, 2011.

Understanding Understanding Source Code with Functional Magnetic Resonance Imaging, Siegmund et al., Proceedings of the 36th International Conference on Software Engineering, 2014.

Using Psycho-physiological Measures to Assess Task Difficulty in Software Development , Fritz et al., Proceedings of the 36th International Conference on Software Engineering, 2014.

October 13th to 17th - Proposal Discussions

One on one meetings to discuss project proposal in person. Meetings can be scheduled for Tuesday afternoon and Wednesday and Thursday full day!

October 20th - Proposal Presentations in Class

Each proposal will be presented and discussed in class.

October 27th - Weekly Individual Meeting

Meeting on the progress of the project and discuss the previous and next steps.

November 10th to December 5th - Weekly Individual Meetings

Each week, we will have a meeting on the progress of the project and discuss the previous and next steps.

December 8th - Project Report Due Date

The project report is due at midnight.

December 18th 2pm to 6pm (the latest) - Project Presentations & Program Committee Meeting

Project presentations will be done in room 1.D.07. Most likely, we will take less than the allocated 4 hours.

Weiterführende Informationen


Many of the links on this page are DOIs to the ACM Digital Library, which you will be able to access for free through the UZH VPN