Important Dates & Schedule

Paper Download

Some of these links will direct you to the digital library of Springer or the ACM. In these cases, you will be able to download the paper if you are on the UZH network (or using VPN from home).

Tentative Schedule

Date Topic & Material Deliverable
14.9

Introduction

 

21.9 (Empirical) Research in Software Engineering

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

A practical guide to controlled experiments of software engineering tools with human participants. Ko, LaToza, Burnett, ESE, 2013.

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

 

Some questions that developers or data scientists ask about developers (as ideas for projects):

 

Optional (not required!):

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

ONE question/problem and a way to address/study it in a course project

 

writeup (1page) and presentation (2 slides in PDF) due on Sunday 20.9

 

present to class 21.9 and take part in discussion of papers

28.09

Developer Productivity

(P2) What predicts software developers' productivity? Murphy-Hill et al., IEEE TSE 2019.
 
response paper, leading of part of the discussion, participation
05.10 Sensing Developers
(S1) Using psycho-physiological measures to assess task difficulty in software development. Fritz, Begel, Müller,Yigit-Elliott, Züger. ICSE'14. 
(S2) Recognizing Developers' Emotions while Programming. Girardi, Novielli, Fucci, Lanubile. ICSE'20.
(S3) Learning a Metric for Code Readability. Buse et al., TSE 2008. 
response paper, lead discussion; proposal for project by the end of the week
12.10

Developer Support: Workflow & Breaks

 
 
14.10 Project Proposal due

Project Proposal

15/16.10: proposal discussions

19.10 Presenting proposals in class Proposal presentation
20.10 Final Proposal Due Project Proposal
26.10

Developer Support: Task Context and more     + Weekly Scrum

 

short update report,

response paper, leading of part of the discussion

02.11

Scrum + weekly meetings

short update report

09.11

Meetings & Progress Report

 

short update report,

16.11 Quick Update Presentation in Class & Discussion in Class short presentation + one page writeup of results
23.11 Quick Update Presentation in Class & Discussion in Class short presentation + one page writeup of results
30.11 Scrum + Weekly meeting (10 mins)

almost finished version of project report with finished related work section.

Draft report due on 29.11 midnight!

6.12

8pm

Project report is due & you will receive two reports for reviewing

 

10.12

12pm

noon

Peer reviews are due

& you will receive two peer-reviews for your project report for possible feedback before the presentation

peer-reviews of two other reports
14.12 Presenting project to class presentation