Refactoring: improving the design of existing code
Refactoring: improving the design of existing code
A Metrics Suite for Object Oriented Design
IEEE Transactions on Software Engineering
Object-Oriented Metrics in Practice
Object-Oriented Metrics in Practice
Coupling and cohesion measures for evaluation of component reusability
Proceedings of the 2006 international workshop on Mining software repositories
Using the Conceptual Cohesion of Classes for Fault Prediction in Object-Oriented Systems
IEEE Transactions on Software Engineering
DECOR: A Method for the Specification and Detection of Code and Design Smells
IEEE Transactions on Software Engineering
A two-step technique for extract class refactoring
Proceedings of the IEEE/ACM international conference on Automated software engineering
Identifying Extract Class refactoring opportunities using structural and semantic cohesion measures
Journal of Systems and Software
Identifying method friendships to remove the feature envy bad smell (NIER track)
Proceedings of the 33rd International Conference on Software Engineering
JDeodorant: identification and application of extract class refactorings
Proceedings of the 33rd International Conference on Software Engineering
| Hi-index | 0.00 |
During software evolution changes are inevitable. These changes may lead to design erosion and the introduction of inadequate design solutions, such as design antipatterns. Several empirical studies provide evidence that the presence of antipatterns is generally associated with lower productivity, greater rework, and more significant design efforts for developers. In order to improve the quality and remove antipatterns, refactoring operations are needed. In this demo, we present the Extract class features of ARIES (Automated Refactoring In EclipSe), an Eclipse plug-in that supports the software engineer in removing the “Blob” antipattern.