Sessions & Deadlines
- 10 February - Introductory Session 1 (Dietmar Pfahl)
- Slides
- Video
- Note that the first 2 min of the video are missing because I forgot to start the recording on time.
- General literature on research methods in Software Engineering (SE):
- Shaw M (2002) What makes good research in software engineering? Int J Softw Tools Technol Transfer 4(1):1–7. [https://link.springer.com/article/10.1007/s10009-002-0083-4]
- Kitchenham BA, Dyba T, Jørgensen M (2004) Evidence-Based Software Engineering. Proceedings of the 26th International Conference on Software Engineering (ICSE '04). IEEE Computer Society, Washington, DC, USA, 273-281.
- Claes Wohlin, Per Runeson, Martin Höst, Magnus C. Ohlsson, Björn Regnell, Anders Wesslén: Experimentation in Software Engineering, Springer 2012. [https://link.springer.com/book/10.1007/978-3-642-29044-2]
- Easterbrook S, Singer J, Storey MA, Damian D (2008) Selecting empirical methods for software engineering research. In: Shull F, Singer J, Sjøberg DIK (eds) Guide to advanced empirical software engineering, Springer Germany, pp 285–311. [https://link.springer.com/chapter/10.1007/978-1-84800-044-5_11]
- Klaas-Jan Stol and Brian Fitzgerald. 2018. The ABC of Software Engineering Research. ACM Trans. Softw. Eng. Methodol. 27, 3, Article 11 (September 2018), 51 pages. [https://doi.org/10.1145/3241743]
- Basic Statistics - online textbook
- Design Science in SE:
- Engström, E., Storey, MA., Runeson, P. et al. (2020) How software engineering research aligns with design science: a review. Empir Software Eng 25, 2630–2660. [https://doi.org/10.1007/s10664-020-09818-7]
- Controlled Experiments in SE:
- Wohlin C., Runeson P., Höst M., Ohlsson M.C., Regnell B., Wesslén A. (2012) Experiment Process. In: Experimentation in Software Engineering. Springer, Berlin, Heidelberg. [https://doi.org/10.1007/978-3-642-29044-2_6]
- Jedlitschka A., Ciolkowski M., Pfahl D. (2008) Reporting Experiments in Software Engineering. In: Shull F., Singer J., Sjøberg D.I.K. (eds) Guide to Advanced Empirical Software Engineering. Springer, London. [https://doi.org/10.1007/978-1-84800-044-5_8]
- Case Studies in SE:
- Runeson P, Höst M (2009) Guidelines for conducting and reporting case study research in software engineering. Empirical Software Engineering 14(2):131–164.
- Literature Surveys in SE:
- Kitchenham, B.A., Charters, S. (2007) Guidelines for performing systematic literature reviews in software engineering (version 2.3). Technical Report, EBSE Technical Report EBSE-2007-01, Keele University and Durham University. [https://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.117.471&rep=rep1&type=pdf]
- Mapping Studies in SE:
- Kai Petersen, Robert Feldt, Shahid Mujtaba, and Michael Mattsson (2008) Systematic mapping studies in software engineering. In Proceedings of the 12th international conference on Evaluation and Assessment in Software Engineering (EASE'08). BCS Learning & Development Ltd., Swindon, GBR, 68–77. [https://www.scienceopen.com/hosted-document?doi=10.14236/ewic/EASE2008.8]
- Kai Petersen, Sairam Vakkalanka, Ludwik Kuzniarz (2015) Guidelines for conducting systematic mapping studies in software engineering: An update. Information and Software Technology, Volume 64, Pages 1-18. [https://doi.org/10.1016/j.infsof.2015.03.007]
- 17 February - Introductory Session 2 (Dietmar Pfahl)
- Slides
- Video
- Examples of Systematic Literature Reviews (SLRs) in SE:
- SLS Example 1 - Note that there is a small issue in the structure of Section 4.2
- SLS Example 2
- SLS Example 3
- Example of a MSc Thesis containing an SLS
- Example of a Grey Literature Survey
- Examples of Systematic Mapping Studies (SMSs) in SE:
- How to get literature (journal articles and conference/workshop papers) for free: From within the university network it should work automatically with ACM DL, IEEE Explore, SpringerLink, Scopus, etc. When you are outside the university network, you must first establish a VPN connection to the university. Information on how to establish/ise VPN can be found here: https://wiki.ut.ee/pages/viewpage.action?pageId=17105590
- 24 February - Last possibility to cancel course participation in the SIS.
- 1 March - Deadline for identifying topic with RQs (submit before 23:59)
- 3 March - Individual Consultation for 2nd year students (optional & on request by student only - first come first serve principle)
- 8 March - Deadline for submitting draft reports & slides of Presentations 1 (submit before 23:59)
- 10 March - Presentations 1: 2nd year students only (individual work)
- Intro Slides
- #1: Hariti Sanchaniya: Communication Overhead In Open-Source Software Projects
#2: Muhammad Zubair: A Blockchain solution for Auditing of Timber-to-Charcoal ProcessHas been rescheduled to April 14.- #3: Vladyslav Bondarenko: Use of SZZ algorithm to identify bug-introducing changes in software repositories
- #4: Amit Kumar Singh: An exploration into BPT inside a financial institution
- Note: The presentation session is followed by a 20 min quiz (in Moodle). Only students who did not give a presentation today must take the quiz. In the quiz you must say which presentation was best and which was worst. Justifications must be given.
- 15 March - Deadline for submitting draft reports & slides of Presentations 2 (submit before 23:59)
- 17 March - Presentations 2: 2nd year students only (individual work)
- Intro Slides
- #5: Jazib Sawar: Block-chain based process execution, specifically using Hyperledger
#6: Andry Nõgols: Orchestration of services running on resource constrained IoT devicesHas been cancelled.- #7: Manish Gupta: Pipeline approach for handling data in the hybrid cloud
- #8: Kseniia Leshchenko: Hate Speech Detection and Prediction in Social Media
- Note: The presentation session is followed by a 20 min quiz (in Moodle). Only students who did not give a presentation today must take the quiz. In the quiz you must say which presentation was best and which was worst. Justifications must be given.
- 24 March - Individual Consultation for 1st year students (optional & on request by student only - first come first serve principle)
- 29 March - Deadline for submitting draft reports & slides of Presentations 3 (submit before 23:59)
- 31 March - Presentations 3: 1st year students (work in pairs)
- #11: Machine learning applications in SRE - by Karina Sein & Karl Vaba
- #12: Automatic detection of SA/D smells - by Kaarel Roots & Simo Jaanus
- #13: Methods and tools to assess SA/D quality - by Martin Põhjakivi & Erald Keshi
- #14: Evolution of software architecture paradigms in web-applications - by Karl Kuusik & Kaarel Loide
- Note: The presentation session is followed by a 20 min quiz (in Moodle). Only students who did not give a presentation today must take the quiz. In the quiz you must say which presentation was best and which was worst. Justifications must be given.
- 5 April - Deadline for submitting draft reports & slides of Presentations 4 (submit before 23:59)
- 7 April - Presentations 4: 1st year students (work in pairs)
- #15: Similarity/Difference of code smell frequency across programming languages/platforms - by Einar Linde & Lauri Leiten
- #16: Pros and cons of static tool analysers - by Liisa Sakerman & Rain Hallikas
- #17: Software engineering applied to scientific computing - by Masud Rana
& Shimul Dey - #18: empty slot
- Note: The presentation session is followed by a 20 min quiz (in Moodle). Only students who did not give a presentation today must take the quiz. In the quiz you must say which presentation was best and which was worst. Justifications must be given.
- 12 April - Deadline for submitting draft reports & slides of Presentations 5 (submit before 23:59)
- 14 April - Presentations 5: 1st year students (work in pairs)
- #19: Location-based navigation and services - by Janna-Liisa Leemets & Richard Õnnis
- #20: Control Management Tools for Building Automation - by Helen Tera & Hans Hendrik Starkopf
- #21: Frameworks for bio-feedback - by Vera Onunda & Jekaterina Gorohhova
- #22: A Blockchain solution for Auditing of Timber-to-Charcoal Process - by Muhammad Zubair
- Note: The presentation session is followed by a 20 min quiz (in Moodle). Only students who did not give a presentation today must take the quiz. In the quiz you must say which presentation was best and which was worst. Justifications must be given.
- 19 April - Deadline for submitting draft reports & slides of Presentations 6 (submit before 23:59)
- 21 April - Presentations 6: 1st year students (work in pairs)
- #23: Using machine learning to speed up automated testing - by Huseyn Garayev & Sergi Martinez
- #24: Linux web-server security - by Kaljo Valk & Rabindra Dahal
- #25: Management practices in game development - by Raigo Kõvask & Ott Saar
- #26: Blockchain applications in financial applications - by Daniel Nael & Karl Jääts
- Note: The presentation session is followed by a 20 min quiz (in Moodle). Only students who did not give a presentation today must take the quiz. In the quiz you must say which presentation was best and which was worst. Justifications must be given.
- 26 April - Deadline for submitting draft reports & slides of Presentations 7 (submit before 23:59)
- 28 April - Presentations 7: 1st year students (work in pairs)
- Info Slides - Tips on how to find a MSc topic/supervisor and how to choose the 2nd seminar (target group: 1st year students)
- #27: Effort estimation techniques/tools used in industry - by Elen Tumasyan & Karina Karimova
- #28: Impact of motivation on team productivity - by Kirill Maksimov & Rajab Azizli
- #29: Use of agile management practices in software industry - by Orkhan Jamaladdinov & Rasul Agharzayev
- Note: The presentation session is followed by a 20 min quiz (in Moodle). Only students who did not give a presentation today must take the quiz. In the quiz you must say which presentation was best and which was worst. Justifications must be given.
- 5 May - Individual Consultation for final reports (optional & on request by student only - first come first serve principle)
- 12 May - Individual Consultation for final reports (optional & on request by student only - first come first serve principle)
- 15 May - Deadline for submitting final reports (2nd year students - submit before 23:59)
- 22 May - Deadline for submitting final reports (1st year student pairs - submit before 23:59)