Menu
Home
People
Places
Arts
History
Plants & Animals
Science
Life & Culture
Technology
Reference.org
Experimental software engineering
open-in-new
<h2 id="empirical-software-engineering-research">Empirical software engineering research</h2> <p>In a keynote at the <a href="http://www.esem-conferences.org/">International Symposium on Empirical Software Engineering and Measurement</a> Prof. Wohlin recommended ten commitments that the research community should follow to increase the relevance and impact of empirical software engineering research.<a class="footnote-ref" id="fnref:1" href="#fn:1"><sup>1</sup></a> However, at the same conference Dr. Ali effectively argued that solely following these will not be enough and we need to do more than just show the evidence substantiating the claimed benefits of our interventions but instead what is required for practical relevance and potential impact is the evidence for cost-effectiveness.<a class="footnote-ref" id="fnref:2" href="#fn:2"><sup>2</sup></a> </p><p>The <a href="http://isern.iese.de/">International Software Engineering Research Network (ISERN)</a> is a global community of research groups who are active in experimental software engineering. Its purpose is to advance the practice of and foster university and industry collaborations within experimental software engineering. ISERN holds annual meetings in conjunction with the <a href="http://www.esem-conferences.org/">International Symposium on Empirical Software Engineering and Measurement (ESEM)</a> conference. </p> <h2 id="bibliography">Bibliography</h2> <ul><li><a href="/facts/Victor_Basili/EeX4MnyS">Victor Basili</a>, Richard W. Selby, David H. Hutchens, "Experimentation in Software Engineering", IEEE Transactions on Software Engineering, Vol. SE-12, No.7, July 1986</li> <li>Basili, V.; Rombach, D.; Schneider, K.; <a href="/facts/Barbara_Kitchenham/uKtlBAoV">Kitchenham, B.</a>; Pfahl, D.; Selby, R. (Eds.),<i><a href="https://www.springer.com/computer/programming/book/978-3-540-71300-5">Empirical Software Engineering Issues. Critical Assessment and Future Directions</a></i>, <a href="/facts/Springer-Verlag/nAesf6nT">Springer-Verlag</a>, 2007, <a href="/facts/ISBN_(identifier)/15AdSPa9">ISBN</a> 978-3-540-71300-5.</li> <li><a href="/facts/Barry_Boehm/dVrXr74F">Barry Boehm</a>, Hans Dieter Rombach, and <a href="/facts/Marvin_Victor_Zelkowitz/wBIwgQrb">Marvin V. Zelkowitz</a> (eds.), <i><a href="https://www.springer.com/sgw/cda/frontpage/0,11855,4-40007-22-51432795-0,00.html">Foundations of Empirical Software Engineering — The Legacy of Victor R. Basili</a></i>, <a href="/facts/Springer-Verlag/nAesf6nT">Springer-Verlag</a>, 2005, <a href="/facts/ISBN_(identifier)/15AdSPa9">ISBN</a> 3-540-24547-2.</li> <li>Jones, D. <a href="http://www.knosof.co.uk/ESEUR/ESEUR.pdf">Evidence-based Software Engineering based on the publicly available data</a>, 2020, <a href="/facts/ISBN_(identifier)/15AdSPa9">ISBN</a> 978-1-8382913-0-3</li> <li>H. Dieter Rombach, Victor R. Basili and Richard W. Selby (eds.), <i>[Experimental Software Engineering Issues: Critical Assessment and Future Directions]</i>, <a href="/facts/Springer-Verlag/nAesf6nT">Springer-Verlag</a>, 1993, <a href="/facts/ISBN_(identifier)/15AdSPa9">ISBN</a> 3-540-57092-6.</li></ul> <h2 id="references">References</h2> <ol> <li id="fn:1"><p>Wohlin, Claes (2016). "Is there a Future for Empirical Software Engineering?". Proceedings of the 10th ACM/IEEE International Symposium on Empirical Software Engineering and Measurement - ESEM '16. p. 1. doi:10.1145/2961111.2962641. ISBN 9781450344272. S2CID 25883722. <a href="9781450344272" target="_blank">9781450344272</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li> <li id="fn:2"><p>Ali, Nauman bin (2016). "Is effectiveness sufficient to choose an intervention?". Proceedings of the 10th ACM/IEEE International Symposium on Empirical Software Engineering and Measurement - ESEM '16. pp. 1–6. doi:10.1145/2961111.2962631. ISBN 9781450344272. S2CID 3208211. <a href="9781450344272" target="_blank">9781450344272</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></p></li> </ol>