Automated refactoring to the Strategy design pattern

Christopoulou, Aikaterini; Giakoumakis, E. A.; Zafeiris, Vassilis; Soukara, Vasiliki

doi:10.1016/j.infsof.2012.05.004

Cited by 34 publications

(18 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Aikaterini et al [20] proposed a method to automatically transform/refactor source code to comply with the Strategy design pattern. Their method complements JDeodorant [21] that focuses mainly on the State pattern, by taking into account behavioral properties of the Strategy design pattern during candidate selection phase.…”

Section: State Vs Strategy Design Patternsmentioning

confidence: 99%

Reverse Engineering State and Strategy Design Patterns using Static Code Analysis

Mohamed¹,

Kamel²

2018

ijacsa

View full text Add to dashboard Cite

Abstract-This paper presents an approach to detect behavioral design patterns from source code using static analysis techniques. It depends on the concept of Code Property Graph and enriching graph with relationships and properties specific to Design Patterns, to simplify the process of Design Pattern detection. This approach used NoSQL graph database (Neo4j) and uses graph traversal language (Gremlin) for doing graph matching. Our approach, converts the tasks of design pattern detection to a graph matching task by representing Design Patterns in form of graph queries and running it on graph database.

show abstract

Section: State Vs Strategy Design Patternsmentioning

confidence: 99%

Reverse Engineering State and Strategy Design Patterns using Static Code Analysis

Mohamed¹,

Kamel²

2018

ijacsa

View full text Add to dashboard Cite

show abstract

“…Jensen et al used genetic programming for automated refactoring and the introduction of design patterns [13]. Also, there are many approaches to support specific refactoring techniques, like extract method [3,26], refactoring to design patterns [1] and performing clone refactoring [33].…”

Section: Related Workmentioning

confidence: 99%

Automating the Refactoring Process

Szőke¹

2017

Acta Cybern

View full text Add to dashboard Cite

To decrease software maintenance cost, software development companies use static source code analysis techniques. Static analysis tools are capable of finding potential bugs, anti-patterns, coding rule violations, and they can also enforce coding style standards. Although there are several available static analyzers to choose from, they only support issue detection. The elimination of the issues is still performed manually by developers. Here, we propose a process that supports the automatic elimination of coding issues in Java. We introduce a tool that uses a third-party static analyzer as input and enables developers to automatically fix the detected issues for them. Our tool uses a special technique, called reverse AST-search, to locate source code elements in a syntax tree, just based on location information. Our tool was evaluated and tested in a two-year project with six software development companies where thousands of code smells were identified and fixed in five systems that have altogether over five million lines of code.

show abstract

“…3,4 Previous studies have made use of design patterns to indicate refactoring suggestions and remove bad smells. [5][6][7][8][9] However, design patterns may also introduce complex structures in the source code, such as the bad smells occurrences, when they are not correctly applied. [10][11][12][13][14] Previously, we carried out systematic literature mapping, and we concluded that these two structures have been studied under three aspects: impact on software quality, refactoring, and cooccurrences.…”

Section: Introductionmentioning

confidence: 99%

An exploratory study on cooccurrence of design patterns and bad smells using software metrics

2019

View full text Add to dashboard Cite

Summary A design pattern is a general reusable solution to commonly recurring problems in software projects. Bad smells are symptoms existing in the source code that possibly indicate the presence of a structural problem that requires code refactoring. Although design pattern and bad smells be different concepts, literature has shown that they may be related and cooccur during the evolution of a software system. This paper presents an empirical study that investigates cooccurrences of design patterns and bad smells as well as identifies the main factors that contribute to the emergence of the relationship between them. We carried out a case study with five Java systems to: (1) investigate if the use of design pattern reduces bad smell occurrence, (2) identify cooccurrences of design patterns and bad smells, and (3) identify situations that contribute for the cooccurrence emergence. As the main result, we found that the application of design pattern not necessarily avoid bad smell occurrences. The results also show that some design patterns such as composite, factory method, and singleton, are intrinsically modular and might be useful in creating high‐quality systems. However, other design patterns such as adapter‐command, proxy, and state‐strategy, have presented high cooccurrence frequency with bad smells; therefore, they require attention in their implementation. Finally, via manual inspection in the components with cooccurrence, we found that the identified cooccurrences appeared due to poor planning and inadequate application of design patterns.

show abstract

Automated refactoring to the Strategy design pattern

Cited by 34 publications

References 8 publications

Reverse Engineering State and Strategy Design Patterns using Static Code Analysis

Reverse Engineering State and Strategy Design Patterns using Static Code Analysis

Automating the Refactoring Process

An exploratory study on cooccurrence of design patterns and bad smells using software metrics

Contact Info

Product

Resources

About