@proceedings {1759,
	title = {An Architectural Evolution Dataset},
	year = {2015},
	month = {05/2015},
	publisher = {IEEE},
	abstract = {A good evolution process and a good architecture
can greatly support the maintainability of long-lived, large software
systems. We present AREVOL, a dataset for the empirical
study of architectural evolution. The dataset comprises two
popular systems from the same domain and using the same
component model, to make comparative studies possible. Besides
the original component metadata, AREVOL includes scripts to
obtain simplified models that nevertheless support rich studies of
architectural evolution, as the authors{\textquoteright} previous work has shown.},
	url = {http://oro.open.ac.uk/42318/1/wermelinger15msr.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/wermelinger15msr.pdf},
	author = {Wermelinger, Michel and Yu, Yijun}
}
@proceedings {1514,
	title = {INVocD: Identifier Name Vocabulary Dataset },
	year = {2013},
	month = {05/2013},
	abstract = {INVocD is a database of the identifier name declarations and vocabulary found in 60 FLOSS Java projects where the source code structure is recorded and the identifier name vocabulary is made directly available, offering advantages for identifier name research over conventional source code models. The database has been used to support a range of research projects from identifier name analysis to concept location, and provides many opportunities to researchers. INVocD may be downloaded from http://oro.open.ac.uk/36992},
	author = {Simon Butler and Wermelinger, Michel and Yu, Yijun and Helen Sharp}
}
@conference {Wermelinger:2008:AEE:1370750.1370783,
	title = {Analyzing the evolution of eclipse plugins},
	booktitle = {Proceedings of the 2008 international working conference on Mining software repositories},
	series = {MSR {\textquoteright}08},
	year = {2008},
	pages = {133{\textendash}136},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Eclipse is a good example of a modern component-based complex system that is designed for long-term evolution, due to its architecture of reusable and extensible components. This paper presents our preliminary results about the evolution of Eclipse{\textquoteright}s architecture, based on a lightweight and scalable analysis of the metadata in Eclipse{\textquoteright}s sources. We find that the development of Eclipse follows a systematic process: most architectural changes take place in milestones, and maintenance releases only make exceptional changes to component dependencies. We also found a stable architectural core that remains since the first release.},
	keywords = {architectural evolution, cvs, eclipse, metadata, msr challenge, releases, source code},
	isbn = {978-1-60558-024-1},
	doi = {http://doi.acm.org/10.1145/1370750.1370783},
	url = {http://doi.acm.org/10.1145/1370750.1370783},
	author = {Wermelinger, Michel and Yu, Yijun}
}
