Experimental software engineering: Difference between revisions

Revision as of 11:30, 18 May 2021

Latest revision as of 15:29, 5 March 2024

(8 intermediate revisions by 8 users not shown)

Line 1:

{{Short description|methodologyMethodology of software-engineering research}}

{{more footnotes|date=February 2013}}

{{see also|Software development process}}

'''Experimental software engineering''' isinvolves a part ofrunning [[software engineeringexperiment]]s thaton focusesthe onprocesses gatheringand evidence,procedures throughinvolved measurementsin andthe [[experiment]]screation involvingof [[software system]]s (software products, processes, and resources).{{citation needed|date=February 2013}} Thiswith datathe isintent intendedthat tothe data be used as the basis of theories about the processes involved in [[software engineering]] (theory backed by data is a fundamental tenet of the [[scientific method]]). A number of [httphttps://shape-of-code.coding-guidelines.com/20132021/0610/2924/empiricalevidence-based-se-groups-doing-interesting-work-20132021-version/ research groups] primarily use empirical and experimental techniques.

EmpiricalThe software engineering is a related concept, sometimes used synonymously with experimental software engineering.term Empirical[[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 empiricalEmpirical software engineering research ==

In a keynote at the [http://www.esem-conferences.org/ International Symposium on Empirical Software Engineering and Measurement] Prof. Wohlin recommended ten commitments that the research community should follow to increase the relevance and impact of empirical software engineering research.<ref>{{Cite book |doi=10.1145/2961111.2962641|isbn=9781450344272|chapter=Is there a Future for Empirical Software Engineering?|title=Proceedings of the 10th ACM/IEEE International Symposium on Empirical Software Engineering and Measurement - ESEM '16|pages=1|year=2016|last1=Wohlin|first1=Claes|s2cid=25883722 }}</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 book |doi=10.1145/2961111.2962631|isbn=9781450344272|chapter=Is effectiveness sufficient to choose an intervention?|title=Proceedings of the 10th ACM/IEEE International Symposium on Empirical Software Engineering and Measurement - ESEM '16|pages=1–6|year=2016|last1=Ali|first1=Nauman bin|s2cid=3208211 }}</ref>

The [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.

===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==

Line 20 ⟶ 18:

==Bibliography==

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

*Basili, [[BarryV.; Boehm]]Rombach, HansD.; DieterSchneider, RombachK.; [[Barbara Kitchenham|Kitchenham, andB.]]; MarvinPfahl, VD.; ZelkowitzSelby, R. (edsEds.), ''[https://www.springer.com/sgwcomputer/cdaprogramming/frontpagebook/0,11855,4978-400073-22540-5143279571300-0,00.html Foundations of5 Empirical Software Engineering —Issues. TheCritical LegacyAssessment ofand Victor R.Future BasiliDirections]'', [[Springer-Verlag]], 20052007, {{ISBN|978-3-540-2454771300-25}}.

*Basili, V.;[[Barry RombachBoehm]], D.;Hans Schneider,Dieter K.; KitchenhamRombach, B.;and Pfahl,[[Marvin D.;Victor Selby,Zelkowitz|Marvin RV. Zelkowitz]] (Edseds.), ''[https://www.springer.com/computersgw/programmingcda/bookfrontpage/9780,11855,4-340007-54022-7130051432795-50,00.html Foundations of Empirical Software Engineering Issues.— CriticalThe AssessmentLegacy andof FutureVictor DirectionsR. Basili]'', [[Springer-Verlag]], 20072005, {{ISBN|978-3-540-7130024547-52}}.

* Jones, D. [http://www.knosof.co.uk/ESEUR/ESEUR.pdf Evidence-based Software Engineering based on the publicly available data], 2020, {{ISBN|978-1-8382913-0-3}}

* H. Dieter Rombach, Victor R. Basili and Richard W. Selby (eds.), ''[Experimental Software Engineering Issues: Critical Assessment and Future Directions]'', [[Springer-Verlag]], 1993, {{ISBN|3-540-57092-6}}.

{{DEFAULTSORT:Experimental Software Engineering}}

{{Software engineering}}

[[Category:Software engineering folklore]]

[[Category:Science experiments|Software engineering]]