Program evolution: processes of software change
Program evolution: processes of software change
Lessons from the design of the Eiffel libraries
Communications of the ACM
Refactoring: improving the design of existing code
Refactoring: improving the design of existing code
An Incremental Class Reorganization Approach
ECOOP '92 Proceedings of the European Conference on Object-Oriented Programming
Proceedings of the First JSSST International Symposium on Object Technologies for Advanced Software
A Visual Analytics Tool for Software Project Structure and Relationships among Classes
SG '09 Proceedings of the 10th International Symposium on Smart Graphics
How developers use the dynamic features of programming languages: the case of smalltalk
Proceedings of the 8th Working Conference on Mining Software Repositories
Extensions during software evolution: do objects meet their promise?
ECOOP'12 Proceedings of the 26th European conference on Object-Oriented Programming
How (and why) developers use the dynamic features of programming languages: the case of smalltalk
Empirical Software Engineering
| Hi-index | 0.00 |
With the widespread adoption of object-oriented programming, changing the inheritance hierarchy became an inherent part of today's software maintenance activities. Unfortunately, little is known about the "state-of-thepractice" with respect to changing an application's inheritance hierarchy, and consequently we do not know how the change process can be improved. In this paper, we report on a study of the hierarchy changes stored in a versioning system to explore the answers to three research questions: (1) why are hierarchy changes made? (2) what kind of hierarchy changes are made? (3) what is the impact of these changes? Based on the results of this study, we formulate 7 hypotheses which should be investigated further to make conclusive interpretations on how hierarchy changes fit in the actual change process.