@conference {SNH15,
	title = {Do Automatic Refactorings Improve Maintainability? An Industrial Case Study},
	booktitle = {Proceedings of the 31st International Conference on Software Maintenance and Evolution (ICSME 2015)},
	year = {2015},
	pages = {429{\textendash}438},
	publisher = {IEEE Computer Society},
	organization = {IEEE Computer Society},
	address = {Bremen, Germany},
	abstract = {Refactoring is often treated as the main remedy against the unavoidable code erosion happening during software evolution. Studies show that refactoring is indeed an elemental part of the developers{\textquoteright} arsenal. However, empirical studies about the impact of refactorings on software maintainability still did not reach a consensus. Moreover, most of these empirical investigations are carried out on open-source projects where distinguishing refactoring operations from other development activities is a challenge in itself. We had a chance to work together with several software development companies in a project where they got extra budget to improve their source code by performing refactoring operations. Taking advantage of this controlled environment, we collected a large amount of data during a refactoring phase where the developers used a (semi)automatic refactoring tool. By measuring the maintainability of the involved subject systems before and after the refactorings, we got valuable insights into the effect of these refactorings on large-scale industrial projects. All but one company, who applied a special refactoring strategy, achieved a maintainability improvement at the end of the refactoring phase, but even that one company suffered from the negative impact of only one type of refactoring.},
	keywords = {automatic refactoring, coding issues, ISO/IEC 25010, Software maintainability},
	doi = {10.1109/ICSM.2015.7332494},
	url = {http://ieeexplore.ieee.org/document/7332494/},
	author = {Sz{\H o}ke, G{\'a}bor and Csaba Nagy and P Heged{\H u}s and Rudolf Ferenc and Tibor Gyim{\'o}thy}
}
@article {HBL13,
	title = {A Drill-Down Approach for Measuring Maintainability at Source Code Element Level},
	journal = {Electronic Communications of the {EASST}},
	volume = {60},
	year = {2013},
	pages = {1{\textendash}21},
	abstract = {Measuring source code maintainability has always been a challenge for software engineers. To address this problem, a number of metrics-based quality models have been proposed by researchers. Besides expressing source code maintainability in terms of numerical values, these models are also expected to provide explicable results, i.e. to give a detailed list of source code fragments that should be improved in order to reach higher overall quality. In this paper, we propose a general method for drilling down to the root causes of a quality rating. According to our approach, a relative maintainability index can be calculated for each source code element for which metrics are calculated (e.g. methods, classes). The index value expresses the source code element{\textquoteright}s contribution to the overall quality rating. We empirically validated the method on the jEdit open source tool, by comparing the results with the opinions of software engineering students. The case study shows that there is a high, 0.68 Spearman{\textquoteright}s correlation, which suggests that relative maintainability indices assigned by our method express the subjective feelings of humans fairly well.},
	keywords = {ISO/IEC 9126, Method level maintainability, Metrics-based quality model, Relative maintainability index},
	issn = {1863-2122},
	doi = {10.14279/tuj.eceasst.60.852},
	url = {https://journal.ub.tu-berlin.de/eceasst/article/view/852},
	author = {P Heged{\H u}s and Tibor Bakota and Lad{\'a}nyi, Gergely and Farag{\'o}, Csaba and Rudolf Ferenc}
}
@conference {HBL13b,
	title = {A Drill-Down Approach for Measuring Maintainability at Source Code Element Level},
	booktitle = {Proceedings of the 7th International Workshop on Software Quality and Maintainability (SQM 2013)},
	year = {2013},
	month = {mar},
	pages = {20{\textendash}29},
	address = {Genova, Italy},
	abstract = {Measuring source code maintainability has always been a challenge for software engineers. To address this problem, a number of metrics-based quality models have been proposed by researchers. Besides expressing source code maintainability in terms of numerical values, these models are also expected to provide explicable results, i.e. to give a detailed list of source code fragments that should be improved in order to reach higher overall quality. In this paper, we propose a general method for drilling down to the root causes of a quality rating. According to our approach, a relative maintainability index can be calculated for each source code element for which metrics are calculated (e.g. methods, classes). The index value expresses the source code element{\textquoteright}s contribution to the overall quality rating. We empirically validated the method on the jEdit open source tool, by comparing the results with the opinions of software engineering students. The case study shows that there is a high, 0.68 Spearman{\textquoteright}s correlation, which suggests that relative maintainability indices assigned by our method express the subjective feelings of humans fairly well.},
	keywords = {ISO/IEC 9126, Method level maintainability, Metrics-based quality model, Relative maintainability index},
	author = {P Heged{\H u}s and Tibor Bakota and Lad{\'a}nyi, Gergely and Farag{\'o}, Csaba and Rudolf Ferenc}
}
@article {16345,
	title = {A Drill-Down Approach for Measuring Maintainability at Source Code Element Level},
	journal = {ELECTRONIC COMMUNICATIONS OF THE EASST},
	volume = {60},
	year = {2013},
	pages = {20{\textendash}29},
	issn = {1863-2122},
	url = {http://www.inf.u-szeged.hu/ ferenc/papers/SQM2013_pre_proceedings.pdf},
	author = {P Heged{\H u}s and Tibor Bakota and G. Lad{\'a}nyi and Csaba Farag{\'o} and Rudolf Ferenc}
}
@conference {Schrettner:2010:DMS:1955601.1955983,
	title = {Development of a Methodology, Software {\textendash} Suite and Service for Supporting Software Architecture Reconstruction},
	booktitle = {Proceedings of the 2010 14th European Conference on Software Maintenance and Reengineering},
	series = {CSMR {\textquoteright}10},
	year = {2010},
	pages = {190{\textendash}193},
	publisher = {IEEE Computer Society},
	organization = {IEEE Computer Society},
	address = {Washington, DC, USA},
	keywords = {architecture evolution, architecture management, architecture reconstruction, architecture visualization},
	isbn = {978-0-7695-4321-5},
	doi = {http://dx.doi.org/10.1109/CSMR.2010.32},
	url = {http://dx.doi.org/10.1109/CSMR.2010.32},
	author = {Schrettner, L. and P Heged{\H u}s and Rudolf Ferenc and F{\"u}l{\"o}p, L.J. and Tibor Bakota}
}
@conference {KBH10,
	title = {{DPDX} {\textendash} A Common Exchange Format for Design Pattern Detection Tools},
	booktitle = {14th European Conference on Software Maintenance and Reengineering (CSMR 2010)},
	year = {2010},
	month = {mar},
	pages = {232-235},
	author = {G. Kniesel and A. Binun and P Heged{\H u}s and F{\"u}l{\"o}p, L.J. and A. Chatzigeorgiou and Y.-G. Gueheneuc and N. Tsantalis}
}
