CloneMap: A Clone-aware Code Inspection Tool in Evolving Software
2018
- 54Usage
Metric Options: CountsSelecting the 1-year or 3-year option will change the metrics count to percentiles, illustrating how an article or review compares to other articles or reviews within the selected time period in the same journal. Selecting the 1-year option compares the metrics against other articles/reviews that were also published in the same calendar year. Selecting the 3-year option compares the metrics against other articles/reviews that were also published in the same calendar year plus the two years prior.
Example: if you select the 1-year option for an article published in 2019 and a metric category shows 90%, that means that the article or review is performing better than 90% of the other articles/reviews published in that journal in 2019. If you select the 3-year option for the same article published in 2019 and the metric category shows 90%, that means that the article or review is performing better than 90% of the other articles/reviews published in that journal in 2019, 2018 and 2017.
Citation Benchmarking is provided by Scopus and SciVal and is different from the metrics context provided by PlumX Metrics.
Example: if you select the 1-year option for an article published in 2019 and a metric category shows 90%, that means that the article or review is performing better than 90% of the other articles/reviews published in that journal in 2019. If you select the 3-year option for the same article published in 2019 and the metric category shows 90%, that means that the article or review is performing better than 90% of the other articles/reviews published in that journal in 2019, 2018 and 2017.
Citation Benchmarking is provided by Scopus and SciVal and is different from the metrics context provided by PlumX Metrics.
Metrics Details
- Usage54
- Abstract Views54
Interview Description
Mining software repositories is a frequent tactic in the evaluation of software in our research. Software modification of large code bases often consists of recurring changes, similar but slightly different changes across multiple locations and revisions. It is a high-effort, time consuming process for developers to find all the relevant locations to maintain such changes among bugfixes, refactorings, and new code being added to the code base for new features. This process is highly error-prone leading to many mistakes, such as inconsistent or incorrect updates. To address this problem, we present a tool that helps developers ensure correctness of recurring changes to multiple locations in an evolving software. CloneMap is a clone-aware code inspection tool which allows developers to specify the older and newer revisions of a software. It then applies a clone detection technique to (1) mine repositories for extracting differences of recurring changes, (2) visualize the clone evolution, and (3) help developers focus their attention to potential anomalies, such as inconsistent and missing updates as the software evolves from one revision to the next.
Bibliographic Details
Provide Feedback
Have ideas for a new metric? Would you like to see something else here?Let us know