Assessing Software Product Maintainability Based on Class-Level Structural Measures

Benestad, Hans Christian; Anda, Bente; Arisholm, Erik

doi:10.1007/11767718_11

Cited by 21 publications

(19 citation statements)

References 24 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…For Table 1, eight articles describing Java softwares were considered: (Shatnawi and Li, 2008); (Benestad et al, 2006); (Subramanyam and Krishnan, 2003); (Stroggylos and Spinellis, 2007); (Johari and Kaur, 2012); (Abuasad and Alsmadi, 2012); (Kakarontzas et al, 2012); (Nair and Selvarani, 2011).…”

Section: Resultsmentioning

confidence: 99%

“…The model proposed by this work is often used in software visualization models. Works as CodeCrawler (Lanza, 2003) and CodeCity (Wettel and Lanza, 2007) (Benestad et al, 2006) 0 0 0 0 11.4 12.5 - (Benestad et al, 2006) uses this method to guide the visualization model. In this work, a classification modified from the original proposition with regard to the "High values" is proposed.…”

Section: Methodsmentioning

confidence: 99%

See 1 more Smart Citation

Detection of Software Anomalies Using Object-oriented Metrics

Juliano

Travençolo

Soares

2014

Proceedings of the 16th International Conference on Enterprise Information Systems

View full text Add to dashboard Cite

The development of quality software has always been the aim of many studies in past years, in which the focus was on seeking for better software production with high effectiveness and quality. In order to evaluate software quality, software metrics were proposed, providing an effective tool to analyze important features such as maintainability, reusability and testability. The Chidamber and Kemerer metrics (CK metrics) are frequently applied to analyze Object-Oriented Programming (OOP) features related to structure, inheritance and message calls. The main purpose of this article is to gather results from studies that used the CK metrics for source code evaluation, and based on the CK metrics, perform a review related to software metrics and the values obtained. Results on the mean and standard deviation obtained in all the studied papers is presented, both for Java and C++ projects. Therefore, software anomalies are identified comparing the results of software metrics described in those studies. This article contributes by suggesting values for software metrics that, according to the literature, can present high probabilities of failures. Another contribution is to analyze which CK metrics are successfully used (or not) in some activities such as to predict proneness error, analyze the impact of refactoring on metrics and examine the facility of white-box reuse based on metrics. We discovered that, in most of the studied articles, CBO, RFC and WMC are often useful and hierarchical metrics as DIT and NOC are not useful in the implementation of such activities. The results of this paper can be used to guide software development, helping to manage the development and preventing future problems.

show abstract

Section: Resultsmentioning

confidence: 99%

Section: Methodsmentioning

confidence: 99%

Detection of Software Anomalies Using Object-oriented Metrics

Juliano

Travençolo

Soares

2014

Proceedings of the 16th International Conference on Enterprise Information Systems

View full text Add to dashboard Cite

show abstract

“…Their framework includes measures of size, coupling, cohesion, and lexical SoC. Then, a number of studies (Benestad et al 2006;Greenwood et al 2007;Hoffman and Eugster 2009;Katić et al 2013;Kulesza et al 2006;Lobato et al 2008;Mguni and Ayalew 2013;Shen et al 2008) used those metrics as predictors of the maintenance effort. Unfortunately, using Sant'Anna's framework to compare evolvability between OO and AO software is problematic due to several reasons.…”

Section: Measuring Maintainability Of Ao Softwarementioning

confidence: 99%

An empirical study on the impact of AspectJ on software evolvability

Przybyłek

2017

Empir Software Eng

View full text Add to dashboard Cite

Since its inception in 1996, aspect-oriented programming (AOP) has been believed to reduce the effort required to maintain software systems by replacing cross-cutting code with aspects. However, little convincing empirical evidence exists to support this claim, while several studies suggest that AOP brings new obstacles to maintainability. This paper discusses two controlled experiments conducted to evaluate the impact of AspectJ (the most mature and popular aspect-oriented programming language) versus Java on software evolvability. We consider evolvability as the ease with which a software system can be updated to fulfill new requirements. Since a minor language was compared to the mainstream, the experiments were designed so as to anticipate that the participants were much more experienced in one of the treatments. The first experiment was performed on 35 student subjects who were asked to comprehend either Java or AspectJ implementation of the same system, and perform the corresponding comprehension tasks. Participants of both groups achieved a high rate of correct answers without a statistically significant difference between the groups. Nevertheless, the Java group significantly outperformed the AspectJ group with respect to the average completion time. In the second experiment, 24 student subjects were asked to implement (in a noninvasive way) two extension scenarios to the system that they had already known. Each subject evolved either the Java version using Java or the AspectJ version using AspectJ. We found out that a typical AspectJ programmer needs significantly fewer atomic changes to implement the change scenarios than a typical Java programmer, but we did not observe a significant difference in completion time. The overall result indicates that AspectJ has a different effect on two sub-characteristics of the evolvability: understandability and changeability. While AspectJ decreases the former, it improves one aspect of the latter.Empir Software Eng

show abstract

“…The code of the four systems was measured using the complete set of CK-metrics as well as additional metrics. The measurement procedure and all the resulting values are described in [3].…”

Section: Evolvability Assessmentmentioning

confidence: 99%

Assessment of software system evolvability

Anda

2007

Ninth International Workshop on Principles of Software Evolution: In Conjunction With the 6th ESEC/FSE Joint Meeting

Self Cite

View full text Add to dashboard Cite

The evolvability, the ease of further development, of a software systems is difficult to assess, but may have large economic consequences. Many studies have investigated the relations between particular software metrics and effort on evolving individual classes, but little attention has been given to methods for assessing and measuring evolvability of complete software systems. This paper discusses such methods, and motivates that they should use a combination of structural code measures and expert assessments. This is exemplified in a case study assessing the evolvability of four functionally equivalent systems. The paper also gives with directions for future work on evolvability assessments.

show abstract

Assessing Software Product Maintainability Based on Class-Level Structural Measures

Cited by 21 publications

References 24 publications

Detection of Software Anomalies Using Object-oriented Metrics

Detection of Software Anomalies Using Object-oriented Metrics

An empirical study on the impact of AspectJ on software evolvability

Assessment of software system evolvability

Contact Info

Product

Resources

About