2009 Second International Conference on Emerging Trends in Engineering &Amp; Technology 2009
DOI: 10.1109/icetet.2009.17
|View full text |Cite
|
Sign up to set email alerts
|

A Quantitative Evaluation of Software Quality Enhancement by Refactoring Using Dependency Oriented Complexity Metrics

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
3
0
2

Year Published

2011
2011
2023
2023

Publication Types

Select...
4
2

Relationship

0
6

Authors

Journals

citations
Cited by 6 publications
(5 citation statements)
references
References 12 publications
0
3
0
2
Order By: Relevance
“…Geppert et al [23] empirically investigated the impact of refactoring on changeability, while Wilking et al [24] investigated the effect thereof on maintainability and modifiability. Reddy and Rao [31] quantitatively evaluated the quality enhancement by refactoring using dependency oriented complexity metrics. They found that the metrics successfully indicate quantitatively the presence of defects and the improvement in the quality of designs after refactoring.…”
mentioning
confidence: 99%
“…Geppert et al [23] empirically investigated the impact of refactoring on changeability, while Wilking et al [24] investigated the effect thereof on maintainability and modifiability. Reddy and Rao [31] quantitatively evaluated the quality enhancement by refactoring using dependency oriented complexity metrics. They found that the metrics successfully indicate quantitatively the presence of defects and the improvement in the quality of designs after refactoring.…”
mentioning
confidence: 99%
“…et al [13] Graph-based Maintainability, Bug severity MD=2, MQ=1, LV=3, USB=2, CA=1, AP=3, TS=2 Elish [22] Internal structure Understandability MD=-, MQ=1, LV=4, USB=3, CA=1, AP=2, TS=2 Gupta et al [27] Internal structure Understandability MD=3, MQ=1, LV=2, USB=2, CA=1, AP=2, TS=2 Gupta et al [28] Internal structure Reusability MD=3, MQ=3, LV=1, USB=2, CA=2, AP=2, TS=2 Haohua et al [29] Graph-based Complexity MD=2, MQ=1, LV=3, USB=2, CA=1, AP=2, TS=2 Hu et al [30] Specific model Maintainability MD=2, MQ=2, LV=2, USB=2, CA=1, AP=2, TS=1 Hwa et al [31] Internal structure Understandability MD=2, MQ=3, LV=2, USB=2, CA=1, AP=2, TS=2 Kanjilal et al [32] Graph-based Complexity MD=2, MQ=1, LV=2, USB=3, CA=1, AP=2, TS=1 Lindvall et al [44] Internal structure Maintainability MD=1, MQ=3, LV=2, USB=2, CA=1, AP=3, TS=2 Ma et al [45,46] Graph-based Complexity, Fault rate MD=-, MQ=1, LV=4, USB=2, CA=2, AP=2, TS=2 Misic [47] Internal structure External coherence MD=3, MQ=1, LV=1, USB=3, CA=1, AP=2, TS=1 Reddy et al [52] Graph-based Complexity MD=2, MQ=3, LV=1, USB=2, CA=2, AP=2, TS=1 Salman [54] Internal structure Maintainability, Integrability MD=3, MQ=1, LV=3, USB=3, CA=1, AP=2, TS=1 Sarkar et al [57] Internal structure Modularization MD=2, MQ=1, LV=3, USB=2, CA=1, AP=2, TS=2 Sartipi [58] Graph-based Modularization MD=2, MQ=1, LV=2, USB=2, CA=1, AP=3, TS=2 Sheresh. et al [60] Specific model -MD=2, MQ=2, LV=-, USB=1, CA=1, AP=1, TS=1 Wei et al [61] Graph-based -MD=2, MQ=1, LV=-, USB=2, CA=1, AP=1, TS=1 Yu et al [62] Specific model Fault rate MD=1, MQ=1, LV=2, USB=2, CA=1, AP=2, TS=2 Zhou et al [63] Graph-based External coherence MD=3, MQ=1, LV=2, USB=2, CA=2, AP=2, TS=2…”
Section: Referencementioning
confidence: 98%
“…Metrics values confirmed the degradation of the modularization quality. Reddy et al [52] used the dependency oriented complexity metrics to evaluate the improvement in quality (reduced complexity) after refactoring.…”
Section: Measured Software Artefacts and Attributes (Rq1)mentioning
confidence: 99%
“…Salah satu cara perbaikan kualitas adalah refactoring. Reddy and Rao [13] mengusulkan metode untuk mendeteksi cacat dari desain dan melakukan perbaikan kualitas dari perangkat lunak dengan melakukan refactoring. Metode yang diusulkan tersebut, menghitung nilai Dcoupling antar artifak pada kelas yang menjadi indikator tingkat ketergantungan kelas pada desain.…”
Section: Peningkatan Kualitas Perangkat Lunakunclassified
“…Proses evaluasi dilakukan dengan memperhatikan nilai hasil pengukuran dan threshold yang diinginkan, sehingga desain dapat disimpulkan dapat diterima, harus diperbaiki, atau harus diganti. Jika desain harus diperbaiki, maka dilakukan proses penentuan class-class yang berpotensi terdapat kesalahan pada desain melalui perhitungan metrik Coupling Between Object (CBO) [16], atau DCoupling yang diperkenalkan oleh Reddy & Rao [13]. Jika hasil perhitungan diatas nilai threshold, maka kelas-kelas tersebut memiliki kompleksitas yang tinggi dan berpotensi merupakan sumber kesalahan pada implementasi.…”
Section: Evaluation Phaseunclassified