EDBT 2026 Demo / reviewers in the wild / expert
Inderjot Kaur Ratol
dblp:207/7143
· DBLP profile ↗
1ranked-venue papers
1as first author
0since 2021 · last 2017
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 1 · 1 first-author
Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.
| Software engineering, system software, and programming languages
1 paper |
Software maintenance and evolution · 100% |
Topics — the 3 heaviest of 3, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Software maintenance and evolution › software documentation
code comments |
0.3 | 1 | 2017 | Detecting fragile comments · ASE 2017 |
Software maintenance and evolution › refactoring
identifier renaming |
0.3 | 1 | 2017 | Detecting fragile comments · ASE 2017 |
Software maintenance and evolution
refactoring |
0.3 | 1 | 2017 | Detecting fragile comments · ASE 2017 |
Methods — techniques the papers use, named apart from their topics
rule-based detection · 0.3
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2017 | Detecting fragile commentsabstractRefactoring is a common software development practice and many simple refactorings can be performed automatically by tools. Identifier renaming is a widely performed refactoring activity. With tool support, rename refactorings can rely on the program structure to ensure correctness of the code transformation. Unfortunately, the textual references to the renamed identifier present in the unstructured comment text cannot be formally detected through the syntax of the language, and are thus fragile with respect to identifier renaming. We designed a new rule-based approach to detect fragile comments. Our approach, called Fraco, takes into account the type of identifier, its morphology, the scope of the identifier and the location of comments. We evaluated the approach by comparing its precision and recall against hand-annotated benchmarks created for six target Java systems, and compared the results against the performance of Eclipse's automated in-comment identifier replacement feature. Fraco performed with near-optimal precision and recall on most components of our evaluation data set, and generally outperformed the baseline Eclipse feature. As part of our evaluation, we also noted that more than half of the total number of identifiers in our data set had fragile comments after renaming, which further motivates the need for research on automatic comment refactoring. Inderjot Kaur Ratol, Martin P. Robillard |
ASE | 1 |