Note: Once it is clear who does which topic, the presentations will be scheduled. There will be two schedules, one for 2nd year students (presentation slots 1 and 2), and one for 1st year students (presentation slots 3 and higher). Within each student group, the presentations will be scheduled following the order of the topics shown below, i.e., starting with topics in the field of Software Requirements Engineering and ending with topics in the field of Software Management. Each selected topic must focus on specific aspects within a chosen topic, e.g., a specific activity (scope), a specific population, a specific intervention, a specific context, a specific outcome, etc.
Proposed topics for 1st year students
These topics can be picked by 1st year students for presentation sessions 3 and higher. Additions/replacements are possible but must be agreed with the seminar teacher.
Software Requirements Engineering (SRE)
- Topic SR-1: Machine learning applications in SRE - taken by Karina Sein & Karl Vaba
- Topic SR-2: The use of natural language processing in SRE
- Topic SR-3: Tool support in SRE
- Topic SR-4: Methods and techniques of agile SRE
Software Architecture/Design (SA/D)
- Topic AD-1: Automatic detection of SA/D smells - taken by Kaarel Roots & Simo Jaanus
- Topic AD-2: Methods and tools to assess SA/D quality (or: to support SA/D evolution) taken by Martin Põhjakivi & Erald Keshi
- Topic AD-3: Evolution of software architecture paradigms in web-applications - taken by Karl Kuusik & Kaarel Loide
- Topic AD-4: Use of SA Description Languages (SADLs) in industry
- Topic SI-1: Similarity/Difference of code smell frequency across programming languages/platforms - taken by Einar Linde & Lauri Leiten
- Topic SI-2: Pros and cons of static tool analysers - taken by: Liisa Sakerman & Rain Hallikas
- Topic SI-3: Software engineering applied to scientific computing - taken by Masud Rana & Shimul Dey
- Topic SI-4: Tool support in scientific computing
- Topic SI-5: Location-based navigation and services - taken by Janna-Liisa Leemets & Richard Õnnis
- Topic SI-6: Building Control Tools and Dashboards - taken by Helen Tera & Hans Hendrik Starkopf
- Topic SI-7: Frameworks for bio-feedback - taken by Vera Onunda & Jekaterina Gorohhova
- Topic TQ-1: Automatic unit test generation
- Topic TQ-2: Automatic end-to-end test generation
- Topic TQ-3: Using machine learning to solve the test oracle problem
- Topic TQ-4: Using machine learning to speed up automated testing - taken by Huseyn Garayev & Sergi Martinez
- Topic TQ-5: (Automated) Security testing of mobile applications (or: web-applications)
- Topic TQ-6: Automatic test oracle generation
- Topic TQ-7: Linux web-server security - taken by Kaljo Valk & Rabindra Dahal
- Topic PM-1: Adoption of agile development practices in embedded systems
- Topic PM-2: Teaching agile software development to students and engineers
- Topic PM-3: Teaching software testing to university students
- Topic PM-4: Management practices in game development - taken by Raigo Kõvask & Ott Saar
- Topic BP-1: Blockchain applications in financial applications - taken by Daniel Nael & Karl Jääts
- Topic BP-1: Methods to extract security issues from business process models
- Topic BP-1: Evolution of business process description languages
- Topic BP-1: Teaching business process management
- Topic SM-1: Use software requirements management methods/tools in industry
- Topic SM-2: Effort estimation techniques/tools used in industry - taken by Elen Tumasyan & Karina Karimova
- Topic SM-3: Impact of motivation on team productivity - taken by: Kirill Maksimov & Rajab Azizli
- Topic SM-4: Use of agile management practices in software industry - taken by Orkhan Jamaladdinov & Rasul Agharzayev
Note 1: All topics may be tailored (scoped), e.g., made activity, domain, platform or programming language specific. Also, the time frame may be limited (e.g., since 2010, or even since 2015) to limit the number of papers to be analysed.
Note 2: Second year students work alone. First year students work in pairs.
Note 3: For each chosen topic a set of research questions (RQs) must be formulated. Second year students must address at least 3 RQs while pairs of 1st year students must handle at least 4 RQs in their report/presentation.
Research Questions - Example
Example taken from: 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]
- RQ1: Which guidelines are followed to conduct the systematic mapping studies in software engineering?
- RQ2: Which software engineering topics are covered?
- RQ3: Where and when were mapping studies published?
- RQ4: How was the systematic mapping process performed?
- This includes, for example:
- Identification of studies (search, inclusion and exclusion)
- Categorization and Classification schemes and processes
- Visualization of results
- This includes, for example: