On the criteria to be used in decomposing systems into modules
Communications of the ACM
Functional Paleontology: The Evolution of User-Visible System Services
IEEE Transactions on Software Engineering
Software Evolution Observations Based on Product Release History
ICSM '97 Proceedings of the International Conference on Software Maintenance
Studying the Evolution and Enhancement of Software Features
ICSM '00 Proceedings of the International Conference on Software Maintenance (ICSM'00)
Evolution in Open Source Software: A Case Study
ICSM '00 Proceedings of the International Conference on Software Maintenance (ICSM'00)
A Reference Architecture for Web Browsers
ICSM '05 Proceedings of the 21st IEEE International Conference on Software Maintenance
IWSM '09 /Mensura '09 Proceedings of the International Conferences on Software Process and Product Measurement
CASCON '09 Proceedings of the 2009 Conference of the Center for Advanced Studies on Collaborative Research
Assessing architectural evolution: a case study
Empirical Software Engineering
| Hi-index | 0.00 |
In evolutionary software development, knowing how design evolves with features can be valuable in guiding future projects. It helps answer questions like "How much upfront design should and can be done?" and "How and why are designs changed?" To shed light on these questions, we report on a study of the evolution history of the Eclipse Java editor. We find that the MVC-based design was cleanly laid out in the beginning of the project and carefully followed and maintained, which has contributed positively to the continuous growth of the editor features. Although design changes at the individual feature level happened for reasons like extensibility and reusability, they appear to be local and manageable. The AST facility is a key service that enables more than one half of the Java editor features.