Hierarchical Clustering for Software Architecture Recovery

Maqbool, Onaiza; Babri, Haroon A.

doi:10.1109/tse.2007.70732

Cited by 308 publications

(209 citation statements)

References 70 publications

Supporting

Mentioning

199

Contrasting

Unclassified

Order By: Relevance

“…Maqbool and Babri [11] argue that Jaccard is particularly suited for asymmetric binary features and gives similar results as other distance metrics for cases where the feature vector is sparse (as it is in our case). We define the distance δ between two symbols s and t to be the Jaccard distance J δ between their sets of users U s and U t :…”

Section: Distance Metricsupporting

confidence: 70%

Using Cluster Analysis to Improve the Design of Component Interfaces

Adnan

Graaf

Deursen

et al. 2008

2008 23rd IEEE/ACM International Conference on Automated Software Engineering

View full text Add to dashboard Cite

Section: Distance Metricsupporting

confidence: 70%

Using Cluster Analysis to Improve the Design of Component Interfaces

Adnan

Graaf

Deursen

et al. 2008

2008 23rd IEEE/ACM International Conference on Automated Software Engineering

View full text Add to dashboard Cite

“…Maqbool and Babri provide an assessment of the behavior of various similarity and distance measures that may be employed during software clustering, which they applied to legacy systems comprising thirty to seventy thousand lines of code [27].…”

Section: Related Workmentioning

confidence: 99%

Splitting a large software repository for easing future software evolution—an industrial experience report

Glorie

Zaidman

Deursen

et al. 2009

J. Softw. Maint. Evol.: Res. Pract.

View full text Add to dashboard Cite

SUMMARYPhilips Medical Systems produces medical diagnostic imaging products, such as MR, X-ray and CT systems. The software of these devices is complex, has been evolving for several decades and is currently a multi-MLOC monolithic software repository. In this paper we report on splitting a single software repository into multiple smaller repositories so that these can be developed independently, easing the software's evolution. For splitting the single software repository, we set up two experiments that involve well-known analysis techniques, namely formal concept analysis and clustering. Because of the sheer size of the monolithic software repository, we also propose to use a 'leveled approach', which implies that the analysis technique is applied in several iterations, whereby in some iterations only part of the application is subjected to the analysis technique. Unfortunately, both analysis techniques failed to produce an acceptable partitioning of the monolithic software repository, even if they are combined with our newly proposed leveled approach. We provide a number of valuable lessons learned, which might prevent others from falling into the same pitfalls.

show abstract

“…However, most of the work in the field is related to techniques dealing with (semi-) automatic improvement of the design of a software system. In particular, authors have focused their attention on the identification of design problems that may represent refactoring opportunities [18], [19], [20], [21], re-modularization techniques [22], [23], [24], [25], [26], and refactoring approaches [9], [11], [27], [12], [28], [29], [30], [31], [32], [33], [34], [35]. Our approach is mostly related to the latter ones.…”

Section: Related Workmentioning

confidence: 99%

Methodbook: Recommending Move Method Refactorings via Relational Topic Models

Bavota

Oliveto

Gethers

et al. 2014

IIEEE Trans. Software Eng.

130

View full text Add to dashboard Cite

Abstract-During software maintenance and evolution the internal structure of the software system undergoes continuous changes. These modifications drift the source code away from its original design, thus deteriorating its quality, including cohesion and coupling of classes. Several refactoring methods have been proposed to overcome this problem. In this paper we propose a novel technique to identify Move Method refactoring opportunities and remove the Feature Envy bad smell from source code. Our approach, coined as Methodbook, is based on Relational Topic Models (RTM), a probabilistic technique for representing and modeling topics, documents (in our case methods) and known relationships among these. Methodbook uses RTM to analyze both structural and textual information gleaned from software to better support move method refactoring. We evaluated Methodbook in two case studies. The first study has been executed on six software systems to analyze if the move method operations suggested by Methodbook help to improve the design quality of the systems as captured by quality metrics. The second study has been conducted with eighty developers that evaluated the refactoring recommendations produced by Methodbook. The achieved results indicate that Methodbook provides accurate and meaningful recommendations for move method refactoring operations.

show abstract

Hierarchical Clustering for Software Architecture Recovery

Cited by 308 publications

References 70 publications

Using Cluster Analysis to Improve the Design of Component Interfaces

Using Cluster Analysis to Improve the Design of Component Interfaces

Splitting a large software repository for easing future software evolution—an industrial experience report

Methodbook: Recommending Move Method Refactorings via Relational Topic Models

Contact Info

Product

Resources

About