Navigation auf uzh.ch
Navigation auf uzh.ch
| Date | Topic & Material | Deliverable |
| 17.9 |
Introduction
|
|
| 24.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.
|
response papers, participation in class |
| 01.10 |
Developer Productivity & Support The Work Life of Developers: Activities, Switches and Perceived Productivity. Meyer et al., TSE 2017.
Code Bubbles: Rethinking the User Interface Paradigm of IDEs. Bragdon et al., ICSE 2010.
Evaluating Cues for Resuming Interrupted Programming Tasks, Parnin et al., CHI 2010.
|
response papers, leading of part of the discussion, participation |
| 08.10 | Sensing and Supporting Code Difficulty
Learning a Metric for Code Readability. Buse et al., TSE 2008.
Using Bio(Metrics) to Predict Code Quality Online. Müller et al., ICSE 2016.
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 |
| 14.10 | Project Proposal Due | Project Proposal |
| 15.10 | Week for discussing proposals | |
| 22.10 | Presenting proposals in class | Proposal presentation |
| 24.10 | Final Proposal Due | Project Proposal |
| 29.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.
An eye-tracking study on the role of scan time in finding source code defects. Sharif et al., ETRA 2012.
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)
|
| 05.11 | <written progress report> | short update report in written form by email |
| 12.11 |
Mood & Emotions in SE + Weekly Scrum Do moods affect programmers' debug performance? Khan et al., Cognition, Technology and Work, 2011. |
short update report, response paper, leading of part of the discussion |
| 19.11 | Scrum + Weekly meetings (10 mins) | short update report |
| 26.11 | Scrum + Weekly meetings (10 mins) | one page writeup of results |
| 03.12 | Scrum + Weekly meeting (10 mins) |
almost finished version of project report with finished related work section. Draft report due on 2.12 midnight! |
| 10.12. | Project report is due & you will receive two reports for reviewing |
Project report |
| 14.12 |
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 |
| 17.12 | Presenting project to class | presentation |
