The story of moose: an agile reengineering environment
Proceedings of the 10th European software engineering conference held jointly with 13th ACM SIGSOFT international symposium on Foundations of software engineering
Modeling history to analyze software evolution: Research Articles
Journal of Software Maintenance and Evolution: Research and Practice
Visual support of software engineers during development and maintenance
ACM SIGSOFT Software Engineering Notes
Assessing the impact of bad smells using historical information
Ninth international workshop on Principles of software evolution: in conjunction with the 6th ESEC/FSE joint meeting
Visually localizing design problems with disharmony maps
Proceedings of the 4th ACM symposium on Software visualization
The evolution and impact of code smells: A case study of two open source systems
ESEM '09 Proceedings of the 2009 3rd International Symposium on Empirical Software Engineering and Measurement
Using Meta-Model Transformation to Model Software Evolution
Electronic Notes in Theoretical Computer Science (ENTCS)
Refactorings of design defects using relational concept analysis
ICFCA'08 Proceedings of the 6th international conference on Formal concept analysis
Exploring, exposing, and exploiting emails to include human factors in software engineering
Proceedings of the 33rd International Conference on Software Engineering
Assessing architectural evolution: a case study
Empirical Software Engineering
Multi-criteria detection of bad smells in code with UTA method
XP'05 Proceedings of the 6th international conference on Extreme Programming and Agile Processes in Software Engineering
Proceedings of the 11th annual international conference on Aspect-oriented Software Development
Assessing technical debt by identifying design flaws in software systems
IBM Journal of Research and Development
Hi-index | 0.00 |
As systems evolve and their structure decays, maintainersneed accurate and automatic identification of the designproblems. Current approaches for automatic detectionof design problems are not accurate enough because theyanalyze only a single version of a system and consequentlythey miss essential information as design problems appearand evolve over time. Our approach is to use the historicalinformation of the suspected flawed structure to increase theaccuracy of the automatic problem detection. Our means isto define measurements which summarize how persistent theproblem was and how much maintenance effort was spenton the suspected structure. We apply our approach on alarge scale case study and show how it improves the accuracyof the detection of God Classes and Data Classes, andadditionally how it adds valuable semantical informationabout the evolution of flawed design structures.