Navigation auf uzh.ch
Navigation auf uzh.ch
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).
| Date | Topic & Material | Deliverable |
| 16.9 |
Introduction
|
|
| 23.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.
Optional (not required!): 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.
|
ONE response paper covering both papers due on Sunday 22.9, participation in class |
| 30.09 |
Developer Productivity & Support The Work Life of Developers: Activities, Switches and Perceived Productivity. Meyer et al., TSE 2017.
What predicts software developers' productivity? Murphy-Hill et al., IEEE TSE 2019.
Code Bubbles: Rethinking the User Interface Paradigm of IDEs. Bragdon et al., ICSE 2010.
|
response paper, leading of part of the discussion, participation |
| 07.10 | Sensing and Supporting Code Difficulty
Learning a Metric for Code Readability. Buse et al., TSE 2008.
Measuring Neural Efficiency of Program Comprehension. Siegmund et al., ESEC/FSE 2017.
Helping developers help themselves: automatic decomposition of code review changesets. Barnett et al., ICSE 2015.
|
response paper, lead discussion; proposal for project by the end of the week |
| 13.10 | Project Proposal Due | Project Proposal |
| 14.10 | Week for discussing proposals | |
| 21.10 | Presenting proposals in class | Proposal presentation |
| 22.10 | Final Proposal Due | Project Proposal |
| 28.10 |
Eye-Tracking in SE & ML + Weekly Scrum Improving Automated Source Code Summarization via an Eye-Tracking Study of Programmers. Rodeghero et al., ICSE 2014.
Detecting Personality Traits Using Eye-Tracking Data. Berkovsky et al., CHI 2019.
A Brief Introduction into Machine Learning, Raetsch, 2004.
Optional:
EyeDE: Gaze-enhanced Software Development Environments, Glücker et al., CHI 2014.
|
short update report, response paper, leading of part of the discussion Machine Learning Intro 29.10.18 (PDF, 549 KB) Jupyter Notebook ML Intro (IPYNB, 78 KB)
|
| 04.11 |
Developer Support + Weekly Scrum Context-Aware Conversational Developer Assistants. Bradley et al., ICSE 2018. Augmenting Code with In Situ Visualizations to Aid Program Understanding. Hoffswell et al., CHI 2018. |
short update report, response paper, leading of part of the discussion short update report in written form by email |
| 11.11 |
Meetings & Progress Report
|
short update report, |
| 18.11 | No in person class! |
short update report in written form by email |
| 25.11 | Quick Update Presentation in Class & Discussion in Class | short presentation + one page writeup of results |
| 02.12 | Scrum + Weekly meeting (10 mins) |
almost finished version of project report with finished related work section. Draft report due on 1.12 midnight! |
|
10.12 8pm |
Project report is due & you will receive two reports for reviewing |
Project report submit here |
|
13.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 |
| 16.12 | Presenting project to class | presentation |
