2011 IEEE 19th International Conference on Program Comprehension 2011
DOI: 10.1109/icpc.2011.22
|View full text |Cite
|
Sign up to set email alerts
|

Design Defects Detection and Correction by Example

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

1
91
0
1

Year Published

2012
2012
2019
2019

Publication Types

Select...
4
3
1

Relationship

6
2

Authors

Journals

citations
Cited by 85 publications
(93 citation statements)
references
References 12 publications
1
91
0
1
Order By: Relevance
“…Our previous work treats the detection and correction as two different steps. In this paper, we generate also new form of detection-correction rules that are completely different from [11].…”
Section: Related Workmentioning
confidence: 99%
See 1 more Smart Citation
“…Our previous work treats the detection and correction as two different steps. In this paper, we generate also new form of detection-correction rules that are completely different from [11].…”
Section: Related Workmentioning
confidence: 99%
“…Both works do not need a formal definition of defects to detect them. In another work [11], we generate detection rules defined as combinations of metrics/thresholds that better conform to known instances of design defects (defect examples). Then, the correction solutions, a combination of refactoring operations, should minimize, as much as possible, the number of defects detected using the detection rules.…”
Section: Related Workmentioning
confidence: 99%
“…A number of detection approaches [10,16,21] exist for object-oriented (OO) antipatterns. However, OO approaches are not applicable to the detection of SOA antipatterns because: (1) SOA is concerned with services as building blocks, whereas OO is concerned with classes, i.e., services are coarser than classes in terms of granularity and (2) the highly dynamic nature of SOA compared to OO systems.…”
Section: Related Workmentioning
confidence: 99%
“…How does NSGA-III perform compared to mono-objective refactoring approaches [19][23]? It is important to determine if considering each conflicting metric as a separate objective to optimize performs better than a mono-objective approach that aggregates all metrics in one objective.…”
Section: Rq2mentioning
confidence: 99%
“…We implemented our approach and evaluated it on seven large open source systems and found that, on average, more than 92% of code smells were corrected. The statistical analysis of our experiments over 31 runs shows that NSGA-III performed significantly better than two other many-objective techniques (IBEA and MOEA/D), a multiobjective algorithm (NSGA-II) and two mono-objective approaches [19][23].…”
Section: Introductionmentioning
confidence: 99%