Code clones in feature-oriented software product lines

Schulze, Sandro; ApelSven,; Kästner, Christian

doi:10.1145/1942788.1868310

Cited by 13 publications

(4 citation statements)

References 50 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Code cloning can result in larger code sizes, which can hinder software maintenance. Additionally, code cloning can lead to the creation of unnecessary or dead code, which can further complicate software maintenance [9], [10].…”

Section: Maintainabilitymentioning

confidence: 99%

A literature review for measuring maintainability of code clone

Khaleel,

Al-Khatouni

2023

IJEECS

View full text Add to dashboard Cite

Software organizations face constant pressure due to stakeholder requirements and the increasing complexity of software systems. This complexity, combined with defects in code quality and failures, can pose risks to software systems. To ensure code is understood before maintenance, developers must spend over 60% of their time modifying and improving code quality, which is costly. This study examines the impact of code refactoring activities on software maintainability and quality by reviewing relevant research and explaining key terms. The research finds that refactoring activities can enhance specific quality characteristics, including maintainability, understandability, and testability. The study also identifies important factors that should be considered when developing refactoring tools. Refactoring enables code improvement without altering program behavior and can be applied multiple times to source code.

show abstract

Section: Maintainabilitymentioning

confidence: 99%

A literature review for measuring maintainability of code clone

Khaleel,

Al-Khatouni

2023

IJEECS

View full text Add to dashboard Cite

show abstract

“…To efficiently implement SPL, novel programming paradigms, such as Feature Oriented Programming has gained momentum over the years, which subsequently help in overcoming certain limitations of Object Oriented Programming (OOP). FOP has higher level of modularity and reusability in comparison to OOP [3]. Although FOP has potential to alleviate OOP related code clones, it is possible that it may introduce some of its own -FOP related code clones.…”

Section: Introductionmentioning

confidence: 99%

A Study on the Nature of Code Clone Occurrence Predominantly in Feature Oriented Programming and the Prospects of Refactoring

Devi¹,

Sharma²,

Kesswani³

2016

IJCA

View full text Add to dashboard Cite

In this position paper, it is tried to analyze the diverse type of code clones which is present and can easily be perpetuated in feature oriented programming. Along with that, a brief summary of the type of code clones and the use of Refactoring methodologies and tools which is effectively known to remove the problem of code clones is also discussed. The main observation that is made in this paper is the various type of code clones which are present in FOP. Through this discussion, it is intended to draw the attention to the various ways in which code clones could propagate and how important it is to curb it at the initial stages to reduce the complexities.

show abstract

“…These studies show that designers may intentionally create certain clones to fulfill some design goals (e.g., for performance, readability, or yet other reasons) [5]. Other clones may result from careless design and can be refactored [6] [8], and yet others may not play any useful role, but cannot be eliminated using conventional design techniques [7]. Nevertheless, cloning is a reality and there is need to deal with it [9].…”

Section: Introductionmentioning

confidence: 99%

Managing Big Clones to Ease Evolution: Linux Kernel Example

Kumar

Jarzabek

Dan³

2016

Annals of Computer Science and Information Systems

View full text Add to dashboard Cite

Abstract-Successful software is often enhanced and adapted to the needs of new users. During evolution, a software system grows in size, becomes more complex, and costly to maintain. In this paper, we point to big clones-large granular duplicated program structures such as files or directories-as one of many reasons why this happens. Using the Linux kernel as an example, we show that big clones arise in the Linux kernel despite careful architecture design and a systematic approach for managing variability. We propose a solution to avoid these big clones by representing them as generalized templates in ART (Adaptive Reuse Technique). ART templates are constructed on top of the Linux code, without conflicts with the state-of-art techniques and tools used to manage the Linux kernel. Benefits include simplification of the Linux kernel due to non-redundancy, easier comprehension, and traceability of the change impact during evolution. The proposed technique is general and the Linux example discussed in this paper also illustrates general phenomena.

show abstract

Code clones in feature-oriented software product lines

Cited by 13 publications

References 50 publications

A literature review for measuring maintainability of code clone

A literature review for measuring maintainability of code clone

A Study on the Nature of Code Clone Occurrence Predominantly in Feature Oriented Programming and the Prospects of Refactoring

Managing Big Clones to Ease Evolution: Linux Kernel Example

Contact Info

Product

Resources

About