Evaluating the Impact of Software Evolution on Software Clustering

Beck, Fabian; Diehl, Stephan

doi:10.1109/wcre.2010.19

Cited by 30 publications

(16 citation statements)

References 24 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…In another set of studies [8], [10], [22], [33], [34], researchers evaluate their proposed recovery techniques using authoritative architecture recoveries of several additional systems. Since none of these were ground-truth architectures, it is likely that they suffered from inaccuracies.…”

Section: A Related Workmentioning

confidence: 99%

“…Hence, a straightforward architecture recovery method could be to simply consider packages and/or directories to be software components. In fact, this approach has been adopted by some existing work [10], [34]. To evaluate the validity of such a method, we examined the extent to which packages or directories represent the components in the four ground-truth architectures.…”

Section: Packages and Directory Structurementioning

confidence: 99%

See 1 more Smart Citation

Obtaining ground-truth software architectures

Garcia¹,

Krka²,

Mattmann³

et al. 2013

2013 35th International Conference on Software Engineering (ICSE)

View full text Add to dashboard Cite

Undocumented evolution of a software system and its underlying architecture drives the need for the architecture's recovery from the system's implementation-level artifacts. While a number of recovery techniques have been proposed, they suffer from known inaccuracies. Furthermore, these techniques are difficult to evaluate due to a lack of "ground-truth" architectures that are known to be accurate. To address this problem, we argue for establishing a suite of ground-truth architectures, using a recovery framework proposed in our recent work. This framework considers domain-, application-, and contextspecific information about a system, and addresses an inherent obstacle in establishing a ground-truth architecture -the limited availability of engineers who are closely familiar with the system in question. In this paper, we present our experience in recovering the ground-truth architectures of four open-source systems. We discuss the primary insights gained in the process, analyze the characteristics of the obtained ground-truth architectures, and reflect on the involvement of the systems' engineers in a limited but critical fashion. Our findings suggest the practical feasibility of obtaining ground-truth architectures for large systems and encourage future efforts directed at establishing a large scale repository of such architectures.

show abstract

Section: A Related Workmentioning

confidence: 99%

Section: Packages and Directory Structurementioning

confidence: 99%

Obtaining ground-truth software architectures

Garcia¹,

Krka²,

Mattmann³

et al. 2013

2013 35th International Conference on Software Engineering (ICSE)

View full text Add to dashboard Cite

show abstract

“…It is reasonable to assume the package structure to be a good approximation of the decomposition of the system into architecturally significant elements, as packages are created by the developers of the system. In fact, package structuring has been used as a decomposition reference in prior research as well [4]. Therefore, one can say that package structuring of a Java project is representative of Module View architecture in which each architectural module consists of several Java classes (as a package) and the relation between them is is-part-of.…”

Section: A Package Viewmentioning

confidence: 99%

A Study on the Role of Software Architecture in the Evolution and Quality of Software

Kouroshfar

Mirakhorli

Bagheri

et al. 2015

2015 IEEE/ACM 12th Working Conference on Mining Software Repositories

View full text Add to dashboard Cite

Conventional wisdom suggests that a software system's architecture has a significant impact on its evolution. Prior research has studied the evolution of software using the information of how its files have changed together in their revision history. No prior study, however, has investigated the impact of architecture on the evolution of software from its change history. This is mainly because most open-source software systems do not document their architectures. We have overcome this challenge using several architecture recovery techniques. We used the recovered models to examine if co-changes spanning multiple architecture modules are more likely to introduce bugs than co-changes that are within modules. The results show that the co-changes that cross architectural module boundaries are more correlated with defects than co-changes within modules, implying that, to improve accuracy, bug predictors should also take the software architecture of the system into consideration.

show abstract

“…for various software engineering tasks. Beck and Diehl [6] found correlation between software evolution and concern clustering. They showed that using evolutionary information along with other information improves the accuracy of concern clustering.…”

Section: Introductionmentioning

confidence: 99%

Probabilistic component identification

Sajnani

Lopes

2014

Proceedings of the 7th India Software Engineering Conference

View full text Add to dashboard Cite

Automatic component identification is an important step for many software engineering tasks and tools, from reverse engineering to program comprehension. Although being a topic of research for a long time, generally applicable solutions remain elusive with very low recall. Most component identification techniques impose structure on the software, therefore requiring substantial knowledge about the software, instead of inferring such structure.We propose PCI, a non-parametric, probabilistic algorithm to the problem of automatic component identification. The proposed approach uses structural, behavioural and lexical features of the software to infer the underlying structure and identify the components. In order to evaluate this approach, multiple experiments are performed on a software system for which components have previously been identified [by others]. The proposed algorithm is compared to two existing algorithms. The experiments measure precision and recall, and attempt to unveil the impact of each source of information on the accuracy of the approach. We find PCI outperforms the others most notably on recall, with improvements that go from 4x to 10x better recall.

show abstract

Evaluating the Impact of Software Evolution on Software Clustering

Cited by 30 publications

References 24 publications

Obtaining ground-truth software architectures

Obtaining ground-truth software architectures

A Study on the Role of Software Architecture in the Evolution and Quality of Software

Probabilistic component identification

Contact Info

Product

Resources

About