MLMatti Luukkainen

Matti Luukkainen

*This is an algorithmically generated author record based on publicly available information.

Current Organizations / Institutes

The organizations/institutes from the scholar's latest article


Matti Luukkainen has a total of 26 co-authors. Here are the top co-authors by number of shared publications:


Latest Publications

  • Open Access

    Near-Duplicate Build Failure Detection from Continuous Integration Logs

    by Mingchen Li, Mika Mäntylä, Jesse Nyyssölä, Matti Luukkainen


  • Open Access

    Flowthrough Analysis on Student Intake Paths

    by Erkki Kaila, Leo Leppänen, Matti Luukkainen, Kjell Lemström


  • Open Access

    On Changing the Curriculum Programming Language from Java to Python (Discussion Paper)

    by Erkki Kaila, Matti Luukkainen, Antti Laaksonen, Kjell Lemström

    The rapid evolution of programming languages in recent years has introduced new languages, tools, libraries, and technologies. Python has emerged as a prevalent programming language, leading many institutions and universities to adopt it as the default language for their programming curriculum. This paper examines the transition from Java to Python as the main programming language of the curriculum at the University of Helsinki. The shift to a new language of instruction is a significant and critical undertaking that profoundly impacts the curriculum. Thus, it requires careful consideration and meticulous execution. To assess our success in the change, we analyzed the pass rates and average student grades across multiple courses before and after the change. Moreover, we administered a questionnaire to teaching assistants experienced in Java and Python and collected weekly feedback from students in the first implementations of the renewed course. Based on our findings, the change was successfully executed, as the learning outcomes were not adversely affected by the language change. Thus, this article likely offers valuable insights for educational institutions considering similar transitions.


  • Benefits and Challenges of Isomorphism in Single-page Applications: Case Study and Review of Gray Literature

    by Aleksi Huotala, Matti Luukkainen, Tommi Mikkonen

    An isomorphic web application shares code between the server and the client by cleverly combining suitable parts of server-rendered applications and single-page applications. In this article, we study the benefits and challenges of isomorphism in single-page applications in terms of a gray literature review and a case study. The case study was conducted as a developer interview, where developers familiar with isomorphic web applications were interviewed. The results of both studies are then compared and the key findings are compared together. The results show that isomorphism in single-page applications brings benefits to both the developers and the end-users. Isomorphism in single-page applications is challenging to implement and has some downsides, but they mostly affect developers. Implementing isomorphism enables sharing code between the server and the client, but it increases the complexity of the application. Framework and library compatibility are issues that must be addressed by the developers.


  • Open Access

    A systematic literature review of capstone courses in software engineering

    by Saara Tenhunen, Tomi Männistö, Matti Luukkainen, Petri Ihantola


  • Open Access

    Software startup within a university -- producing industry-ready graduates

    by Saara Tenhunen, Tomi Männistö, Petri Ihantola, Jami Kousa, Matti Luukkainen

    Previous research has demonstrated that preparing students for life in software engineering is not a trivial task. Authentic learning experiences are challenging to provide, and there are gaps between what students have done at the university and what they are expected to master when getting into the industry after graduation. To address this challenge, we present a novel way of teaching industry-relevant skills in a university-led internal software startup called Software Development Academy (SDA). In addition to describing the SDA concept in detail, we have investigated what educational aspects characterise SDA and how it compares to capstone projects. The questions are answered based on 15 semi-structured interviews with alumni of SDA. Working with production-quality software and having a wide range of responsibilities were perceived as the most integral aspects of SDA and provided students with a comprehensive skill set for the future.

  • Open Access

    A systematic literature review of capstone courses in software engineering

    by Saara Tenhunen, Tomi Männistö, Matti Luukkainen, Petri Ihantola

    Tertiary education institutions aim to prepare their computer science and software engineering students for working life. While much of the technical principles are covered in lower-level courses, team-based capstone projects are a common way to provide students with hands-on experience and teach soft skills. This paper explores the characteristics of software engineering capstone courses presented in the literature. The goal of this work is to understand the pros and cons of different approaches by synthesising the various aspects of software engineering capstone courses and related experiences. In a systematic literature review for 2007-2022, we identified 127 primary studies. These studies were analysed based on their presented course characteristics and the reported course outcomes. The characteristics were synthesised into a taxonomy consisting of duration, team sizes, client and project sources, project implementation, and student assessment. We found out that capstone courses generally last one semester and divide students into groups of 4-5 where they work on a project for a client. For a slight majority of courses, the clients are external to the course staff and students are often expected to produce a proof-of-concept level software product as the main end deliverable. The courses also offer versatile assessments for students throughout the project. This paper provides researchers and educators with a classification of characteristics of software engineering capstone courses based on previous research. We further synthesise insights on the reported outcomes of capstone courses. Our review study aims to help educators to identify various ways of organising capstones and effectively plan and deliver their own capstone courses. The characterisation also helps researchers to conduct further studies on software engineering capstones.

  • Open Access

    Persistence of Time Management Behavior of Students and Its Relationship with Performance in Software Projects

    by Joonas Häkkinen, Petri Ihantola, Matti Luukkainen, Antti Leinonen, Juho Leinonen

    Teachers often preach for their students to start working on assignments early. There is even a fair amount of scientific evidence that starting early is beneficial for learning. In this work, we investigate students’ time management behavior in a second-year project-based software engineering course. In the course, students work on a software project in small groups of four to six students. We study time management from multiple angles. Firstly, we conduct an exploratory factor analysis and study how different time management related behavioral metrics are related to one another, for example, whether individual students’ time management practices in the second-year group project-based course are similar to their earlier time management practices in first-year courses where students work on assignments individually. Understanding how students’ previous time management behavior is manifested in later project-based courses would be beneficial when designing project-based education. Secondly, we study whether students’ time management practices affect the peer-review scores they get from their group members. Lastly, we explore how time management affects course performance. Our findings suggest that time management behavior, even from courses taken in the past, can be used to predict how students perform in future courses.