Experimental software engineering: Difference between revisions

Revision as of 14:15, 2 October 2016

Revision as of 04:44, 3 October 2016

Line 1:

{{nofootnotesmore footnotes|date=February 2013}}

{{merge|Software engineering|date=May 2016}}

{{merge|Software development process|date=May 2016}}

'''Experimental software engineering''' is a part of [[software engineering]] that focuses on [[experiment]]s involving [[software system]]s (software products, processes, and resources).{{factcitation needed|date=February 2013}} The purpose of these experiments is to collect data that can be used to validate theories about the processes involved in software engineering (theory backed by data is a fundamental tenet of the [[scientific method]]).

Empirical software engineering is a related concept, sometimes used synonymously with experimental software engineering. Empirical software engineering emphasizes the use of empirical studies of all kinds to accumulate knowledge. Methods used include experiments, case studies, surveys, and using whatever data is available.

=== Future of empirical software engineering research ===

In a recent keynote at the premier conference on empirical methods in software engineering (International Symposium on Empirical Software Engineering and Measurement http://www.esem-conferences.org/) Prof. Wohlin recommended ten commitments that the research community should follow to increase the relevance and impact of empirical software engineering research.<ref>{{Cite journal|last=Wohlin|first=Claes|date=2016-01-01|title=Is There a Future for Empirical Software Engineering?|url=http://doi.acm.org/10.1145/2961111.2962641|journal=Proceedings of the 10th ACM/IEEE International Symposium on Empirical Software Engineering and Measurement|series=ESEM '16|___location=New York, NY, USA|publisher=ACM|pages=1:1–1:1|doi=10.1145/2961111.2962641|isbn=9781450344272}}</ref>. 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.<ref>{{Cite journal|last=Ali|first=Nauman bin|date=2016-01-01|title=Is Effectiveness Sufficient to Choose an Intervention?: Considering Resource Use in Empirical Software Engineering|url=http://doi.acm.org/10.1145/2961111.2962631|journal=Proceedings of the 10th ACM/IEEE International Symposium on Empirical Software Engineering and Measurement|series=ESEM '16|___location=New York, NY, USA|publisher=ACM|pages=54:1–54:6|doi=10.1145/2961111.2962631|isbn=9781450344272}}</ref>.

==Research labs==

Line 22:

===International Software Engineering Research Network (ISERN)===

[http://isern.iese.de/ International Software Engineering Research Network (ISERN)] 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 [http://www.esem-conferences.org/ International Symposium on Empirical Software Engineering and Measurement (ESEM)] conference.

==References==

{{Reflist}}

* [[Victor Basili]], Richard W. Selby, David H. Hutchens, "Experimentation in Software Engineering", IEEE Transactions on Software Engineering, Vol. SE-12, No.7, July 1986

* [[Barry Boehm]], Hans Dieter Rombach, and Marvin V. Zelkowitz (eds.), ''[http://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]'', [[Springer-Verlag]], 2005, ISBN 3-540-24547-2.

Line 37 ⟶ 38:

[[Category:Software engineering folklore]]

[[Category:Science experiments|Software engineering]]

{{compu-sci-stub}}