Does Refactoring Improve Reusability?

Moser, Raimund; Sillitti, Alberto; Abrahamsson, Pekka; Succi, Giancarlo

doi:10.1007/11763864_21

Cited by 63 publications

(40 citation statements)

References 10 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Thus, it is questionable if their findings are valid in a different context where development teams follow a structured process and use common software engineering practices for knowledge sharing. Moser et al [18] proposed a methodology to assess whether the refactoring improves reusability and promotes adhoc reuse in an Extreme Programming (XP)-like development environment. They focused on internal software metrics that are considered to be relevant to reusability based on metric interpretation of Dandashi and Rine's work [17].…”

Section: Related Workmentioning

confidence: 99%

An Empirical Exploration of Refactoring effect on Software Quality using External Quality Factors

Kannangara¹,

Wijayanayake

2015

Int J on Adv. in ICT for Emerging Countries

View full text Add to dashboard Cite

Abstract-Quality software are robust, reliable and easy to maintain, and therefore reduces the cost of software maintenance. Since software systems undergo modifications, improvements and enhancements to cope with evolving requirements, quality of software can be decreased. While software system is evolving, refactoring is one of the methods which have been applied with the purpose of improving the software quality. Refactoring is defined as the process of improving the design of the existing code by changing its internal structure without affecting its external behavior, with the main aims of improving the quality of software product. Therefore, there is a belief that refactoring improves quality factors such as understandability, flexibility, and reusability. However, there is limited empirical evidence to support such assumptions.The objective of this study is to validate/invalidate the claims that refactoring improves software quality. Experimental research approach was used to achieve the objective and ten selected refactoring techniques were used for the analysis. The overall impact of selected refactoring techniques and the impact of individual refactoring technique were assessed based on external measures namely; analyzability, changeability, time behavior and resource utilization.After analyzing the experimental results, overall analysis ended up with the result that refactoring deteriorates the code quality. However, individual analysis shows that some refactoring techniques improve the code quality while rest is deteriorating the code quality. Furthermore, among the tested ten refactoring techniques, "Replace Conditional with Polymorphism" ranked in the highest as having high percentage of improvement in code quality and "Introduce Null Object" was ranked as worst which is having highest percentage of deteriorate of code quality among the analyzed ten refactoring techniques.

show abstract

Section: Related Workmentioning

confidence: 99%

An Empirical Exploration of Refactoring effect on Software Quality using External Quality Factors

Kannangara¹,

Wijayanayake

2015

Int J on Adv. in ICT for Emerging Countries

View full text Add to dashboard Cite

show abstract

“…Researcher adopted and extracted the set of refactoring activities and case study from Fowler catalogs 14 . The identified set of activities are analyzed to expose the impact of design security rules in context of security improvement 14,[19][20][21][22][23][24] .The details of identified refactoring activities and its effect have been discussed in Table 1. …”

Section: Formulation Of Rulesmentioning

confidence: 99%

Security Improvement of Object Oriented Design using Refactoring Rules

Khan¹,

Khan²

2015

IJMECS

View full text Add to dashboard Cite

Abstract-The main component of study is to confirm that how developed security model are helpful for security improvement of object oriented designs. Software refactoring is an essential activity during development and maintenance. It promotes the reengineering measures for improving quality and security of software. The researcher made an effort in this regard to develop security improvement guideline using refactoring activities for object oriented deign. The developed guidelines are helpful to control design complexity for improved security. A case study is adopted from refactoring example by fowler to implement the Security Improvement Guidelines (SIG). The developed Security Quantification Model (SQM OODC ) is being used to calculate the quantified value of security at each step. The proposed model SQM OODC calculates the effective security index by ensuring that revised version of object oriented design is being influenced through security improvement guidelines. There is some possibility that original code segment may have some security flaws, anomalies and exploitable entities or vulnerable information that may influence security at design stage. SIG is helpful to cease the security flaws, anomalies, exploitable entities into refactored code segment. Each refactored steps of case study match the prediction of the impact for refactoring rules on security and the impact study for security through SQM OODC model legalize the effectiveness of developed model and security improvement guidelines. The validated results of statistical analysis with different case studies of object oriented designs reflect the usefulness and acceptability of developed models and guidelines.

show abstract

“…In the approach we propose, we rely on refactoring as a key activity to enhance the reusability of assets [15]. Moser et al [16] conducted a study to assess if refactoring in agile environments improves the quality and reusability of -otherwise hard to reuse -classes. Their results support the hypothesis that continuous refactoring improves quality metrics thus promoting ad-hoc reuse of object-oriented classes.…”

Section: Related Workmentioning

confidence: 99%

“…In XP, software systems are developed without doing extensive research in the beginning or spending much time on requirement gathering [2]. These systems are developed simply to satisfy the current customer and what this customer really wants [16] without thinking much about the needs of future customers or how the systems can be reused.…”

Section: Introductionmentioning

confidence: 99%

“…Software reuse, on the other hand, promises to offer a number of advantages, and may require explicit support in the development process [16]. Despite the fact that reuse can reduce the development cost of new applications and also reduce the maintenance cost of these applications, XP does not aim at supporting developing software for possible future reuse or the creation of reusable components to be exploited by other applications instead of creating these applications from scratch.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

A Test-Driven Approach for Extracting Libraries of Reusable Components from Existing Applications

Selim

Ghanam

Burns

et al. 2011

Lecture Notes in Business Information Processing

View full text Add to dashboard Cite

Abstract.In agile approaches such as Extreme Programming, time is not spent on making sure that system components can be reused in similar systems. Therefore, there is a need to investigate whether reuse can be achieved by extracting reusable assets from existing applications. This paper presents an approach that relies on refactoring and testing practices for extracting reusable assets from existing applications. The approach creates reusable APIs in a bottom-up fashion, on demand when a new application might benefit from component in an existing application. The extraction process is guided and supported by the usage examples and the testing scenarios in the existing application and the new one. The paper presents a case study, where the approach was used to extract components from the user interface of an existing application, wrap these components in an API, and use this API in the existing and new applications.

show abstract

Does Refactoring Improve Reusability?

Cited by 63 publications

References 10 publications

An Empirical Exploration of Refactoring effect on Software Quality using External Quality Factors

An Empirical Exploration of Refactoring effect on Software Quality using External Quality Factors

Security Improvement of Object Oriented Design using Refactoring Rules

A Test-Driven Approach for Extracting Libraries of Reusable Components from Existing Applications

Contact Info

Product

Resources

About