Name
Abstract | ||
|---|---|---|
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. |
Year | DOI | Venue |
|---|---|---|
2007 | 10.1109/MSR.2007.30 | MSR |
Keywords | DocType | ISBN |
change process,software maintenance activity,research question,hierarchy change,versioning information,understand inheritance hierarchy changes,inherent part,inheritance hierarchy,object-oriented programming,versioning system,actual change process,conclusive interpretation,software maintenance,object oriented programming,computer languages,software systems,java,history,data mining,testing,configuration management | Conference | 0-7695-2950-X |
Citations | PageRank | References |
6 | 0.56 | 4 |
Authors | ||
2 | ||
Name | Order | Citations | PageRank |
|---|---|---|---|
| Filip Van Rysselberghe | 1 | 183 | 13.97 |
| Serge Demeyer | 2 | 2250 | 291.74 |