The history of software systems tracked by version control systems is often incomplete
because many file movements are not recorded. However, static code analyses that mine …

The literature describes several approaches to identify the artefacts of programs that change
together to reveal the (hidden) dependencies among these artefacts. These approaches …

Software systems evolve continuously, requiring continuous maintenance and development.
Consequently, their architecture tends to degrade with time as it becomes less relevant to …

Software maintenance accounts for the largest part of the costs of any program. During
maintenance activities, developers implement changes (sometimes simultaneously) on …

Identifiers play an important role in source code understandability, maintainability, and fault-
proneness. This paper reports a study of identifier renamings in software systems, studying …

Change impact analysis aims at identifying software artefacts that are being affected by a
change. It helps developers to assess their change efforts and perform more adequate …

In this paper, we investigate heuristics for Approximate Graph Matching (AGM), in particular
when it can be formulated as a Maximum Common Edge Subgraph (MCES) problem. First …

Software systems usually evolve constantly, which requires constant development and
maintenance. Subsequently, the architecture of these systems tends to degrade with time …

Testing activity is the most widely adopted practice to ensure software quality. Testing effort
should be focused on defect prone and critical resources ie, on resources highly coupled …

Analyzing and understanding the evolution of large object‐oriented software systems is an
important but difficult task in which matching algorithms play a fundamental role. An error …