Conceptual graph matching: a flexible algorithm and experiments
Journal of Experimental & Theoretical Artificial Intelligence - Special issue: conceptual graphs workshop
Visualizing multiple evolution metrics
SoftVis '05 Proceedings of the 2005 ACM symposium on Software visualization
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
SCQL: a formal model and a query language for source control repositories
MSR '05 Proceedings of the 2005 international workshop on Mining software repositories
Predicting the Probability of Change in Object-Oriented Systems
IEEE Transactions on Software Engineering
How do APIs evolve? A story of refactoring: Research Articles
Journal of Software Maintenance and Evolution: Research and Practice - IEEE International Conference on Software Maintenance (ICSM2005)
Modeling history to analyze software evolution: Research Articles
Journal of Software Maintenance and Evolution: Research and Practice
Software evolution: analysis and visualization
Proceedings of the 28th international conference on Software engineering
The evolution radar: visualizing integrated logical coupling information
Proceedings of the 2006 international workshop on Mining software repositories
Predicting defect densities in source code files with decision tree learners
Proceedings of the 2006 international workshop on Mining software repositories
An empirical study of fine-grained software modifications
Empirical Software Engineering
A Change-based Approach to Software Evolution
Electronic Notes in Theoretical Computer Science (ENTCS)
API-Based and Information-Theoretic Metrics for Measuring the Quality of Software Modularization
IEEE Transactions on Software Engineering
Visual Data Mining in Software Archives to Detect How Developers Work Together
MSR '07 Proceedings of the Fourth International Workshop on Mining Software Repositories
A small observatory for super-repositories
Ninth international workshop on Principles of software evolution: in conjunction with the 6th ESEC/FSE joint meeting
Change-Enabled Software Systems
Software-Intensive Systems and New Computing Paradigms
On the evaluation of recommender systems with recorded interactions
SUITE '09 Proceedings of the 2009 ICSE Workshop on Search-Driven Development-Users, Infrastructure, Tools and Evaluation
Using Meta-Model Transformation to Model Software Evolution
Electronic Notes in Theoretical Computer Science (ENTCS)
An approach to software evolution based on semantic change
FASE'07 Proceedings of the 10th international conference on Fundamental approaches to software engineering
Fifth international workshop on object-oriented reengineering
ECOOP'04 Proceedings of the 2004 international conference on Object-Oriented Technology
Information and Software Technology
Object-oriented reengineering patterns — an overview
GPCE'05 Proceedings of the 4th international conference on Generative Programming and Component Engineering
Is it dangerous to use version control histories to study source code evolution?
ECOOP'12 Proceedings of the 26th European conference on Object-Oriented Programming
Investigating the evolution of code smells in object-oriented systems
Innovations in Systems and Software Engineering
Hi-index | 0.00 |
Knowing where to start reverse engineering a large software system, when no information other than the systemýs source code itself is available, is a daunting task. Having the history of the code (i.e., the versions) could be of help if this would not imply analyzing a huge amount of data. In this paper we present an approach for identifying candidate classes for reverse engineering and reengineering efforts. Our solution is based on summarizing the changes in the evolution of object-oriented software systems by defining history measurements. Our approach, named Yesterdayýs Weather, is an analysis based on the retrospective empirical observation that classes which changed the most in the recent past also suffer important changes in the near future. We apply this approach on two case studies and show how we can obtain an overview of the evolution of a system and pinpoint its classes that might change in the next versions.