Georgios Gousios, http://gousios.org/
|3/9||1||1||Course introduction, Quantitative methods in Software Engineering||MB|
|10/9||2||1||Process Analytics||AR / GG|
|12/9||2||2||Testing Analytics, Testing Paper||students, MB|
|17/9||3||1||Build Analytics, Building Paper||students, MB|
|19/9||3||2||Bug Prediction||students, MB|
|24/9||4||1||Software Ecosystem Analytics||JH|
|26/9||4||2||Release Engineering Analytics||students, AR|
|1/10||5||1||Results: Survey on software analytics||students|
|3/10||5||2||Code review||students, GG|
|8/10||6||1||Runtime and Performance Analytics, Analytics at work: Adyen||Mauricio Aniche, MK|
|10/10||6||2||App store analytics||students, MK|
|15/10||7||1||Analytics at work: ING||Hennie Huijgens|
|17/10||7||2||Results: Replication project results||students|
The course is a seminar. Therefore:
We will work together on a survey of modern software analytics. The topics we will cover are:
|Product||source code, repository, builds, static analysis, ecosystems|
|Process||PR/Code reviews, release engineering, communities, agile, testing etc|
|Runtime||logs, crashes, security, performance|
|Community||app stores, social media, user acceptance|
All topics to work on correspond to the contents of the project’s TOC.
All topics have an instructor attached to them. You can find the responsible instructor on the course’s home page
Each topic page lists 5-10 publications that can serve as a starting point to get you aquainted with the research area.
We will follow Kitchenham’s survey protocol .
Each group will select a topic. You can express interest in a topic. All topics need to be covered. Some groups may get topics they don’t like.
Software Analytics is very applied; outside of the scientific literature we will therefore also write a section covering
The survey is a Bookdown document (template), available on GitHub. Fork it and file PRs. Every group works on one chapter (one file).
Keshav, Srinivasan. “How to read a paper.” ACM SIGCOMM Computer Communication Review 37.3 (2007): 83-84.
D Read the above paper. After 10 minutes, we will discuss it.
Via VPN (to Uni). TU Delft has contracts with most major Tech publishers to get you free access to papers.
Q How much does one article cost?
D Use the different services to derive number of reads, number of citations, and the BibTeX entry for: Beller, Moritz, Georgios Gousios, and Andy Zaidman. “How (much) do developers test?.” Software Engineering (ICSE), 2015 IEEE/ACM 37th IEEE International Conference on. Vol. 2. IEEE, 2015. [beller2015much]
Replication: Redoing a published study following exactly the same research protocol, using the same (exact) or different subjects.
Replication is often touted, seldom practiced. To change this, we will replicate existing studies, as follows:
Each week: i) you produce a reviewable deliverable, ii) review the deliverables of two other groups, and iii) prepare for the classes.
Survey task duration: 5 weeks (starting today!)
Replication task duration: 5 weeks (starting on week 3)
A deliverable is either a document and/or source code.
How to review:
Preparation for classes comprises reading a set of papers for the lecture topic (usually 2-3).
The final course grade will be calculated as:
All deliverables will be peer-reviewed and cross-graded by 2 other teams. The peer-review grade is 50% of the final grade per grade item. The results add up to 110%.
Q A question with a known answer; this will be revealed, but we should work together towards it!
D An open discussion item; we need to think and discuss.
Freely available on the web, on Georgios’s homepage (http://gousios.org/teaching.html)
You can print/download them before the lecture and bring them along to make additional notes.
We are looking forward to improve them! If you have suggestions, find mistakes etc, let me know!
The course contents are copyrighted (c) 2018 - onwards by TU Delft and their respective authors and licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International license.