Michele Lanza
Current Organizations / Institutes
The organizations/institutes from the scholar's latest article
Research Subjects
Michele Lanza has a total of 116 co-authors. Here are the top co-authors by number of shared publications:
- Gabriele Bavota
Università Della Svizzera italiana, Lugano, Switzerland
11 shared publications - Marco Raglianti
REVEAL @ Software Institute, Università della Svizzera italiana, Lugano, Switzerland
7 shared publications - Romain Robbes
Univ. Bordeaux CNRS Bordeaux INP LaBRI UMR 5800 France
7 shared publications - Csaba Nagy
Università della Svizzera Italiana
5 shared publications - Bin Lin
Hangzhou Dianzi University, Hangzhou, China
4 shared publications - Csaba Nagy
REVEAL @ Software Institute, Università della Svizzera italiana, Lugano, Switzerland
4 shared publications
Latest Publications
- Open Access
- 5 July 2026
- Published by Association for Computing Machinery (ACM)
- p. 1341-1345
Class Archetypes: Principles, Detection, Evolution
- 5 July 2026
- Published by Association for Computing Machinery (ACM)
- p. 1341-1345
Open AccessClass Archetypes: Principles, Detection, Evolution
- Open Access
- 5 July 2026
- Published by Association for Computing Machinery (ACM)
- p. 162-166
ZION: System Exploration With Class Contours
Understanding the structure and behavior of classes and their roles in a software system is essential for maintaining and evolving object-oriented software. Reading source code provides limited support for quick comprehension or pattern identification. A class as a long stream of text in the IDE fails to communicate crucial information about its different components (e.g., attributes, methods, instance vs. class side code), while IDE outlines are just a band-aid solution. We present ZION, our tool to visualize the source code by representing classes as 2D architectural structures. ZION defines Class Contours by encoding class components (e.g., attributes, methods) into customizable building features (e.g., doors, windows). This allows tailored visualizations for identifying class roles and patterns, common archetypes, and hotspots for application logic. We present ZION's design, its features, alongside examples to highlight how the emerging visual patterns and the interactive visualization navigation enhance understanding complex software systems.
- 5 July 2026
- Published by Association for Computing Machinery (ACM)
- p. 162-166
Open AccessZION: System Exploration With Class Contours
Understanding the structure and behavior of classes and their roles in a software system is essential for maintaining and evolving object-oriented software. Reading source code provides limited support for quick comprehension or pattern identification. A class as a long stream of text in the IDE fails to communicate crucial information about its different components (e.g., attributes, methods, instance vs. class side code), while IDE outlines are just a band-aid solution. We present ZION, our tool to visualize the source code by representing classes as 2D architectural structures. ZION defines Class Contours by encoding class components (e.g., attributes, methods) into customizable building features (e.g., doors, windows). This allows tailored visualizations for identifying class roles and patterns, common archetypes, and hotspots for application logic. We present ZION's design, its features, alongside examples to highlight how the emerging visual patterns and the interactive visualization navigation enhance understanding complex software systems.
- Open Access
- 13 April 2026
- Published by Association for Computing Machinery (ACM)
- p. 662-666
PoolinGH: Fast, Efficient, and Robust GitHub Repository Mining
- 13 April 2026
- Published by Association for Computing Machinery (ACM)
- p. 662-666
Open AccessPoolinGH: Fast, Efficient, and Robust GitHub Repository Mining
- Open Access
- 12 April 2026
- Published by Association for Computing Machinery (ACM)
- p. 1-5
Forecasting Developer Environments with GenAI: A Research Perspective
Generative Artificial Intelligence (GenAI) models are achieving remarkable performance in various tasks, including code generation, testing, code review, and program repair. The ability to increase the level of abstraction away from writing code has the potential to change the Human-AI interaction within the integrated development environment (IDE). To explore the impact of GenAI on IDEs, 33 experts from the Software Engineering, Artificial Intelligence, and Human-Computer Interaction domains gathered to discuss challenges and opportunities at Shonan Meeting 222, a four-day intensive research meeting. Four themes emerged as areas of interest for researchers and practitioners.
- 12 April 2026
- Published by Association for Computing Machinery (ACM)
- p. 1-5
Open AccessForecasting Developer Environments with GenAI: A Research Perspective
Generative Artificial Intelligence (GenAI) models are achieving remarkable performance in various tasks, including code generation, testing, code review, and program repair. The ability to increase the level of abstraction away from writing code has the potential to change the Human-AI interaction within the integrated development environment (IDE). To explore the impact of GenAI on IDEs, 33 experts from the Software Engineering, Artificial Intelligence, and Human-Computer Interaction domains gathered to discuss challenges and opportunities at Shonan Meeting 222, a four-day intensive research meeting. Four themes emerged as areas of interest for researchers and practitioners.
- Open Access
Forecasting Developer Environments with GenAI: A Research Perspective
Generative Artificial Intelligence (GenAI) models are achieving remarkable performance in various tasks, including code generation, testing, code review, and program repair. The ability to increase the level of abstraction away from writing code has the potential to change the Human-AI interaction within the integrated development environment (IDE). To explore the impact of GenAI on IDEs, 33 experts from the Software Engineering, Artificial Intelligence, and Human-Computer Interaction domains gathered to discuss challenges and opportunities at Shonan Meeting 222, a four-day intensive research meeting. Four themes emerged as areas of interest for researchers and practitioners.
Open AccessForecasting Developer Environments with GenAI: A Research Perspective
Generative Artificial Intelligence (GenAI) models are achieving remarkable performance in various tasks, including code generation, testing, code review, and program repair. The ability to increase the level of abstraction away from writing code has the potential to change the Human-AI interaction within the integrated development environment (IDE). To explore the impact of GenAI on IDEs, 33 experts from the Software Engineering, Artificial Intelligence, and Human-Computer Interaction domains gathered to discuss challenges and opportunities at Shonan Meeting 222, a four-day intensive research meeting. Four themes emerged as areas of interest for researchers and practitioners.
- Open Access
An Empirical Study on Database Usage in Microservices
Microservices architectures are an integral part of modern software development. Their adoption brings significant changes to database management. Instead of relying on a single database, a microservices architecture is typically composed of multiple, smaller, heterogeneous, and distributed DBs. In these data-intensive systems, the variety and combination of database categories and technologies play a crucial role in storing and managing data. While data management in microservices is a major challenge, research literature is scarce. We present an empirical study on how databases are used in microservices. On the dataset we collected (and released as open data for future research), considering 15 years of microservices, we examine ca. 1,000 GitHub projects that use databases selected among 180 technologies from 14 categories. We perform a comprehensive analysis of current practices, providing researchers and practitioners with empirical evidence to better understand database usage in microservices. We report 18 findings and 9 recommendations. We show that microservices predominantly use Relational, Key-Value, Document, and Search databases. Notably, 52% of microservices combine multiple database categories. Complexity correlates with database count, with older systems favoring Relational databases and newer ones increasingly adopting Key-Value and Document technologies. Niche databases (e.g., EventStoreDB, PostGIS), while not widespread, are often combined with a mainstream one.
Open AccessAn Empirical Study on Database Usage in Microservices
Microservices architectures are an integral part of modern software development. Their adoption brings significant changes to database management. Instead of relying on a single database, a microservices architecture is typically composed of multiple, smaller, heterogeneous, and distributed DBs. In these data-intensive systems, the variety and combination of database categories and technologies play a crucial role in storing and managing data. While data management in microservices is a major challenge, research literature is scarce. We present an empirical study on how databases are used in microservices. On the dataset we collected (and released as open data for future research), considering 15 years of microservices, we examine ca. 1,000 GitHub projects that use databases selected among 180 technologies from 14 categories. We perform a comprehensive analysis of current practices, providing researchers and practitioners with empirical evidence to better understand database usage in microservices. We report 18 findings and 9 recommendations. We show that microservices predominantly use Relational, Key-Value, Document, and Search databases. Notably, 52% of microservices combine multiple database categories. Complexity correlates with database count, with older systems favoring Relational databases and newer ones increasingly adopting Key-Value and Document technologies. Niche databases (e.g., EventStoreDB, PostGIS), while not widespread, are often combined with a mainstream one.
- Open Access
Understanding Code Change with Micro-Changes
A crucial activity in software maintenance and evolution is the comprehension of the changes performed by developers, when they submit a pull request and/or perform a commit on the repository. Typically, code changes are represented in the form of code diffs, textual representations highlighting the differences between two file versions, depicting the added, removed, and changed lines. This simplistic representation must be interpreted by developers, and mentally lifted to a higher abstraction level, that more closely resembles natural language descriptions, and eases the creation of a mental model of the changes. However, the textual diff-based representation is cumbersome, and the lifting requires considerable domain knowledge and programming skills. We present an approach, based on the concept of micro-change, to overcome these difficulties, translating code diffs into a series of pre-defined change operations, which can be described in natural language. We present a catalog of micro-changes, together with an automated micro-change detector. To evaluate our approach, we performed an empirical study on a large set of open-source repositories, focusing on a subset of our micro-change catalog, namely those related to changes affecting the conditional logic. We found that our detector is capable of explaining more than 67% of the changes taking place in the systems under study.
Open AccessUnderstanding Code Change with Micro-Changes
A crucial activity in software maintenance and evolution is the comprehension of the changes performed by developers, when they submit a pull request and/or perform a commit on the repository. Typically, code changes are represented in the form of code diffs, textual representations highlighting the differences between two file versions, depicting the added, removed, and changed lines. This simplistic representation must be interpreted by developers, and mentally lifted to a higher abstraction level, that more closely resembles natural language descriptions, and eases the creation of a mental model of the changes. However, the textual diff-based representation is cumbersome, and the lifting requires considerable domain knowledge and programming skills. We present an approach, based on the concept of micro-change, to overcome these difficulties, translating code diffs into a series of pre-defined change operations, which can be described in natural language. We present a catalog of micro-changes, together with an automated micro-change detector. To evaluate our approach, we performed an empirical study on a large set of open-source repositories, focusing on a subset of our micro-change catalog, namely those related to changes affecting the conditional logic. We found that our detector is capable of explaining more than 67% of the changes taking place in the systems under study.
- Open Access
- 15 April 2024
- Published by Association for Computing Machinery (ACM)
- p. 346-357
Collaborative Software Exploration with Multimedia Note Taking in Virtual Reality
Exploring and comprehending a software system, e.g., as preparation for its re-engineering, is a relevant, yet challenging endeavour often conducted by teams of engineers. Collaborative exploration tools aim to ease the process, e.g., via interactive visualizations in virtual reality (VR). However, these neglect to provide engineers with capabilities for persisting their thoughts and findings. We present an interactive VR visualization method that enables (distributed) teams of engineers to collaboratively (1) explore a subject system, while (2) persisting insights via free-hand diagrams, audio recordings, and in-visualization VR screenshots. We invited pairs of software engineering practitioners to use our method to collaboratively explore a software system. We observed how they used our method and collected their feedback and impressions before replaying their findings to the original developers of the subject system for assessment. Video Demonstration---youtube.com/watch?v=32EIpf4V3b4
- 15 April 2024
- Published by Association for Computing Machinery (ACM)
- p. 346-357
Open AccessCollaborative Software Exploration with Multimedia Note Taking in Virtual Reality
Exploring and comprehending a software system, e.g., as preparation for its re-engineering, is a relevant, yet challenging endeavour often conducted by teams of engineers. Collaborative exploration tools aim to ease the process, e.g., via interactive visualizations in virtual reality (VR). However, these neglect to provide engineers with capabilities for persisting their thoughts and findings. We present an interactive VR visualization method that enables (distributed) teams of engineers to collaboratively (1) explore a subject system, while (2) persisting insights via free-hand diagrams, audio recordings, and in-visualization VR screenshots. We invited pairs of software engineering practitioners to use our method to collaboratively explore a software system. We observed how they used our method and collected their feedback and impressions before replaying their findings to the original developers of the subject system for assessment. Video Demonstration---youtube.com/watch?v=32EIpf4V3b4
- Open Access
- 15 April 2024
- Published by Association for Computing Machinery (ACM)
- p. 387-391
Immersive Software Archaeology: Collaborative Exploration and Note Taking in Virtual Reality
Understanding software systems is a vital task, often undertaken by teams of engineers, for the development and maintenance of systems. Collaborative software visualization tools are essential in this context, yet they are limited. Existing tools, particularly in virtual reality, allow exploration but lack the crucial feature of note-taking, which is a significant limitation. We present Immersive Software Archaeology (ISA), a virtual reality tool that enables engineering teams to collaboratively explore and comprehend software systems. Unique to ISA, it facilitates notetaking during exploration with virtual multimedia whiteboards that support freehand diagramming, audio recordings, and VR screenshots. Notes taken on these whiteboards are synchronized with an Integrated Development Environment (IDE), providing easy access to the results of a VR exploration while performing changes to the system's source code. Video Demonstration---https://youtu.be/32EIpf4V3b4
- 15 April 2024
- Published by Association for Computing Machinery (ACM)
- p. 387-391
Open AccessImmersive Software Archaeology: Collaborative Exploration and Note Taking in Virtual Reality
Understanding software systems is a vital task, often undertaken by teams of engineers, for the development and maintenance of systems. Collaborative software visualization tools are essential in this context, yet they are limited. Existing tools, particularly in virtual reality, allow exploration but lack the crucial feature of note-taking, which is a significant limitation. We present Immersive Software Archaeology (ISA), a virtual reality tool that enables engineering teams to collaboratively explore and comprehend software systems. Unique to ISA, it facilitates notetaking during exploration with virtual multimedia whiteboards that support freehand diagramming, audio recordings, and VR screenshots. Notes taken on these whiteboards are synchronized with an Integrated Development Environment (IDE), providing easy access to the results of a VR exploration while performing changes to the system's source code. Video Demonstration---https://youtu.be/32EIpf4V3b4
- Open Access
- 15 April 2024
- Published by Association for Computing Machinery (ACM)
- p. 382-386
Capturing and Understanding the Drift Between Design, Implementation, and Documentation
UML artifacts constitute a key (but often neglected) asset supporting the comprehension of a system. Design documents "bind" developers in implementation phases and close the loop as documentation of the implemented system itself. Nevertheless, the intended system (design), its current version (implementation), and its documentation, naturally tend to drift apart, negatively impacting the usefulness of UML diagrams contained in such artifacts. We present a novel approach to capture and understand the Design-Implementation-Documentation (DID) drift. We connect UML references in human-readable text-based UML formats (e.g., PlantUML) to the corresponding source code entities (e.g., Java classes), implementing novel metrics to capture the UML coverage of the system. We analyze project and file coverage evolution across releases and commits, with overall, method-level, and attributelevel detailedness, showing how they support DID drift analysis. We present interesting case studies exemplifying how through Drifter, the visual exploration tool we developed to validate our approach, we identify DID drift and ways to tackle it in the future.
- 15 April 2024
- Published by Association for Computing Machinery (ACM)
- p. 382-386
Open AccessCapturing and Understanding the Drift Between Design, Implementation, and Documentation
UML artifacts constitute a key (but often neglected) asset supporting the comprehension of a system. Design documents "bind" developers in implementation phases and close the loop as documentation of the implemented system itself. Nevertheless, the intended system (design), its current version (implementation), and its documentation, naturally tend to drift apart, negatively impacting the usefulness of UML diagrams contained in such artifacts. We present a novel approach to capture and understand the Design-Implementation-Documentation (DID) drift. We connect UML references in human-readable text-based UML formats (e.g., PlantUML) to the corresponding source code entities (e.g., Java classes), implementing novel metrics to capture the UML coverage of the system. We analyze project and file coverage evolution across releases and commits, with overall, method-level, and attributelevel detailedness, showing how they support DID drift analysis. We present interesting case studies exemplifying how through Drifter, the visual exploration tool we developed to validate our approach, we identify DID drift and ways to tackle it in the future.