How Developers Copy

Balint, Mihai; Marinescu, Radu

doi:10.1109/icpc.2006.25

Cited by 27 publications

(17 citation statements)

References 13 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Our taxonomy is not simply guesswork -it is derived from the large body of published work on existing clone definitions [8,19,24,29,34], clone types [10,31], clone taxonomies [6,26,36], studies of developer copy/paste activities [27] and other empirical studies [3,7,25,28]. We have validated the taxonomy by studying the copy/paste patterns of function clones in an empirical study that analyzed 17 open source C and Java systems including the entire Linux Kernel (6265 KLOC C, 154977 functions), Apache httpd (275 KLOC C, 4301 functions) and j2sdk-swing (204 KLOC Java, 10971 methods) [41].…”

Section: Figure 1 Example Application Of the Editing Taxonomy For CLmentioning

confidence: 99%

A Mutation/Injection-Based Automatic Framework for Evaluating Code Clone Detection Tools

Roy

Cordy

2009

2009 International Conference on Software Testing, Verification, and Validation Workshops

145

116

View full text Add to dashboard Cite

show abstract

Section: Figure 1 Example Application Of the Editing Taxonomy For CLmentioning

confidence: 99%

A Mutation/Injection-Based Automatic Framework for Evaluating Code Clone Detection Tools

Roy

Cordy

2009

2009 International Conference on Software Testing, Verification, and Validation Workshops

145

116

View full text Add to dashboard Cite

show abstract

“…That enables us to know where arbitrary code fragment were derived from, and to modify all of the code fragments derived from the same source simultaneously. 'Copy and paste' is one reason why there are code clones in the source code; for example, Kim et al reported that developers do block or method level coy-and-paste actions approximately four times per hour [22]; also, Balint et al reported that there often happens inconsistencies between 'copy and pasted' code [7]. Tracking 'copy and paste' should be able to identify many code clones.…”

Section: Related Workmentioning

confidence: 99%

Simultaneous Modification Support based on Code Clone Analysis

Higo¹,

Ueda²,

Kusumoto³

et al. 2007

14th Asia-Pacific Software Engineering Conference (APSEC'07)

View full text Add to dashboard Cite

Maintaining software systems becomes more difficult as their size and complexity increase. One factor that makes software maintenance more difficult is the presence of code clones. A code clone is defined as a code fragment occurring more than once in identical or similar form into a software system. For example, the presence of code clones is a big factor of overlooking some places that should be modified simultaneously. One technique that helps the number of code clones is Refactoring. There are several research efforts that provide support to refactor code clones, but unfortunately some code clones cannot or should not be refactored (ex. stereotyped process, absence of abstraction functionality, performance enhancement). In order to support maintaining the consistency among code clones, we propose a simultaneous modification support method. Given a software system, firstly, a maintainer identifies a code fragment that must be modified. Then, only the code clones between the identified code fragment and the source files of the software system are detected. We developed a simultaneous modification support tool, Libra, and applied it to open source software systems. The results showed that Libra was a good searching tool as much as grep, which is a useful tool of UNIX.

show abstract

“…. This is the topic of a separate publication 4 [12]. We therefore here only give a summary of the AspectMaps visualization, adapted from [12], before discussing the tool.…”

Section: The Aspectmaps Visualizationmentioning

confidence: 99%

“…Moose offers various facilities for building software engineering tools, ranging from importing data, source-code modeling, querying, to building software visualizations. In the past, Moose has been successfully leveraged for building a wide variety of tools, such as Torch [27] (a tool supporting source-code change integration), SmallDude [4] (a duplication detector), and eDSM [19] (a tool to detect cyclic dependencies). Within the context of this work, we opted to base our tool on Moose for the following reasons:…”

Section: Adding Aspect Support To Moosementioning

confidence: 99%

AspectMaps: Extending Moose to visualize AOP software

Fabry¹,

Kellens²,

Denier³

et al. 2014

Science of Computer Programming

View full text Add to dashboard Cite

When using Aspect-Oriented programming the application implicitly invokes the functionality contained in the aspects. Consequently program comprehension of such software is more intricate. To alleviate this difficulty we developed the AspectMaps visualization and tool. AspectMaps extends the Moose program comprehension and reverse engineering platform with support for aspects, and is implemented using facilities provided by Moose. In this paper we present the AspectMaps tool, and show how it can be used by performing an exploration of a fairly large aspectoriented application. We then show how we extended the FAMIX meta-model family that underpins Moose to also provide support for aspects. This extension is called ASPIX, and thanks to this enhancement Moose can now also treat aspect-oriented software. Lastly, we report on our experiences using some of the tools in Moose; Mondrian to implement the visualization, and Glamour to build the user interface. We discuss how we were able to implement a sizable visualization tool using them and how we were able to deal with some of their limitations.Note: This paper uses colors extensively. Please use a color version to better understand the ideas presented here.

show abstract

How Developers Copy

Cited by 27 publications

References 13 publications

A Mutation/Injection-Based Automatic Framework for Evaluating Code Clone Detection Tools

A Mutation/Injection-Based Automatic Framework for Evaluating Code Clone Detection Tools

Simultaneous Modification Support based on Code Clone Analysis

AspectMaps: Extending Moose to visualize AOP software

Contact Info

Product

Resources

About