Luciano Marchezan

Luciano Marchezan

Auto-generated profile, based on publicly available information

Luciano Marchezan

DIRO, Université de Montréal, Montréal, Canada

Research Focus & Metrics

Academic Career Length

8Years (2019-Present)

(Calculated once Scilit publication data is synced: current year − year of first publication + 1)

Representative Publications

View All Publications
28 August 2020 in Empirical Software Engineering
Verified
Journal Article
Closed access
PDF file
AIAníbal Iung
Aníbal Iung
JCJoão Carbonell
João Carbonell
LMLuciano Marchezan
Luciano Marchezan
ERElder Rodrigues
Elder Rodrigues
MBMaicon Bernardino
Maicon Bernardino
BMBruno Medeiros
Bruno Medeiros

27 May 2025 in ACM Transactions on Software Engineering and Methodology
Verified
Journal Article
Open access
Wesley AssunçãoWesley Assunção
Wesley Assunção
LMLuciano Marchezan
Luciano Marchezan
LALawrence Arkoh
Lawrence Arkoh
AEAlexander Egyed
Alexander Egyed
RRRudolf Ramler
Rudolf Ramler
Software modernization is a common activity in software engineering, since technologies advance, requirements change, and business models evolve. Differently from conventional software evolution (e.g., adding new features, enhancing performance, or adapting to new requirements), software modernization involves re-engineering entire legacy systems (e.g., changing the technology stack, migrating to a new architecture style, or programming paradigms). Given the pervasive nature of software today, modernizing legacy systems is paramount to provide customers with competitive and innovative products and services, while keeping companies profitable. Despite the prevalent discussion of software modernization in gray literature, and the many papers in the literature, there is no work presenting a “big picture” of contemporary software modernization, describing challenges, and providing a well-defined research agenda. The goal of this work is to describe the state of the art in software modernization in the past 10 years. We collect the state of the art by performing a rapid review (searching five digital libraries), identifying potential 3,460 studies, leading to a final set of 126. We analyzed these studies to understand which strategies are employed, the driving forces that lead organizations to modernize their systems, and the challenges that need to be addressed. The results show that studies in the last 10 years have explored eight strategies for modernizing legacy systems, namely cloudification, architecture redesign, moving to a new programming language, targeting reuse optimization, software modernization for new hardware integration, practices to leverage automation, database modernization, and digital transformation. Modernization is triggered by 14 driving forces, with the most common ones being reducing operational costs, improving performance and scalability, and reducing complexity. In addition, based on the analysis of existing literature, we present a detailed discussion of research opportunities in this field. The main challenges are providing tooling support, followed by defining a modernization process and considering better evaluation metrics. The main contribution of our work is to equip practitioners and researchers with knowledge of the current state of contemporary software modernization so that they are aware of practices and challenges to be addressed when deciding to modernize legacy systems.

4 April 2022 in Software and Systems Modeling
Verified
Journal Article
Open access
PDF file
LMLuciano Marchezan
Luciano Marchezan
RKRoland Kretschmer
Roland Kretschmer
WAWesley K. G. Assunção
Wesley K. G. Assunção
ARAlexander Reder
Alexander Reder
AEAlexander Egyed
Alexander Egyed
There are many repair alternatives for resolving model inconsistencies, each involving one or more model changes. Enumerating them all could overwhelm the developer because the number of possible repairs can grow exponentially. To address this problem, this paper focuses on the immediate cause of an inconsistency. By focusing on the cause, we can generate a repair tree with a subset of repair actions focusing on fixing this cause. This strategy identifies model elements that must be repaired, as opposed to additional model elements that may or may not have to be repaired later. Furthermore, our approach can provide an ownership-based filter for filtering repairs that modify model elements not owned by a developer. This filtering can further reduce the repair possibilities, aiding the developer when choosing repairs to be performed. We evaluated our approach on 24 UML models and four Java systems, using 17 UML consistency rules and 14 Java consistency rules. The evaluation data contained 39,683 inconsistencies, showing our approach’s usability as the repair trees sizes ranged from five to nine on average per model. Also, these repair trees were generated in 0.3 seconds on average, showing our approach’s scalability. Based on the results, we discuss the correctness and minimalism with regard to the cause of the inconsistency. Lastly, we evaluated the filtering mechanism, showing that it is possible to further reduce the number of repairs generated by focusing on ownership.

8 April 2022 in Software and Systems Modeling
Verified
Journal Article
Open access
PDF file
MTMichael Alexander Tröls
Michael Alexander Tröls
LMLuciano Marchezan
Luciano Marchezan
AMAtif Mashkoor
Atif Mashkoor
AEAlexander Egyed
Alexander Egyed
Engineering projects involve a variety of artifacts such as requirements, design, or source code. These artifacts, many of which tend to be interdependent, are often manipulated concurrently. To keep artifacts consistent, engineers must continuously consider their work in relation to the work of multiple other engineers. Traditional consistency checking approaches reason efficiently over artifact changes and their consistency implications. However, they do so solely within the boundaries of specific tools and their specific artifacts (e.g., consistency checking between different UML models). This makes it difficult to examine the consistency between different types of artifacts (e.g., consistency checking between UML models and the source code). Global consistency checking can help addressing this problem. However, it usually requires a disruptive and time-consuming merging process for artifacts. This article presents a novel, cloud-based approach to global consistency checking in a multi-developer/-tool engineering environment. It allows for global consistency checking across all artifacts that engineers work on concurrently. Moreover, it reasons over artifact changes immediately after the change happened, while keeping the (memory/CPU) cost of consistency checking minimal. The feasibility and scalability of our approach were demonstrated by a prototype implementation and through an empirical validation.

1 April 2022 in Journal of Systems and Software
Verified
Journal Article
Closed access
LMLuciano Marchezan
Luciano Marchezan
ERElder Rodrigues
Elder Rodrigues
Wesley AssunçãoWesley Assunção
Wesley Assunção
MBMaicon Bernardino
Maicon Bernardino
FBFábio Paulo Basso
Fábio Paulo Basso
JCJoão Carbonell
João Carbonell

22 September 2024
Verified
Conference Paper
Open access
LMLuciano Marchezan
Luciano Marchezan
MHMarcel Homolka
Marcel Homolka
ABAndrei Blokhin
Andrei Blokhin
Wesley AssunçãoWesley Assunção
Wesley Assunção
EHEdvin Herac
Edvin Herac
AEAlexander Egyed
Alexander Egyed
Consistency checking is widely used to detect inconsistencies in engineering artifacts. In collaborative modeling environments, however, maintaining model consistency is challenging due to the frequent changes introduced by multiple engineers, leading to possibly numerous inconsistencies. These inconsistencies need to be identified and shared among engineers to collaboratively resolve them and prevent cascading problems. Despite extensive research in consistency checking, there remains a lack of tools that support collaborative consistency checking (C3). C3 is defined as the process of checking and fixing inconsistencies during collaborative modeling, whether engineers work synchronously or asynchronously. To address this gap, we introduce a prototype tool integrated into the DesignSpace environment which allows collaborative work during modeling and consistency checking. Our tool is implemented to support a streamlined version of UML (sUML) with various diagrams such as class, use case, sequence, and state-machine. We showcase the tool's features with an example of a robotic arm, highlighting its effectiveness in collaborative consistency checking. We also compare our tool with related work, showing that collaborative features are currently lacking in the proposed tools. A video showcasing the tool is available at https://www.youtube.com/watch?v=9kweKeBHx5Y