Let's Talk With Developers, Not About Developers: A Review of Automatic Program Repair Research
Automatic program repair (APR) offers significant potential for automating some coding tasks. Using APR could reduce the high costs historically associated with fixing code faults and deliver significant benefits to software engineering. Adopting APR could also have profound implications for softwar...
Gespeichert in:
Veröffentlicht in: | IEEE transactions on software engineering 2023-01, Vol.49 (1), p.419-436 |
---|---|
Hauptverfasser: | , , , , , , |
Format: | Artikel |
Sprache: | eng |
Schlagworte: | |
Online-Zugang: | Volltext |
Tags: |
Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
|
container_end_page | 436 |
---|---|
container_issue | 1 |
container_start_page | 419 |
container_title | IEEE transactions on software engineering |
container_volume | 49 |
creator | Winter, Emily Nowack, Vesna Bowes, David Counsell, Steve Hall, Tracy Haraldsson, Saemundur Woodward, John |
description | Automatic program repair (APR) offers significant potential for automating some coding tasks. Using APR could reduce the high costs historically associated with fixing code faults and deliver significant benefits to software engineering. Adopting APR could also have profound implications for software developers' daily activities, transforming their work practices. To realise the benefits of APR it is vital that we consider how developers feel about APR and the impact APR may have on developers' work. Developing APR tools without consideration of the developer is likely to undermine the success of APR deployment. In this paper, we critically review how developers are considered in APR research by analysing how human factors are treated in 260 studies from Monperrus's Living Review of APR. Over half of the 260 studies in our review were motivated by a problem faced by developers (e.g., the difficulty associated with fixing faults). Despite these human-oriented motivations, fewer than 7% of the 260 studies included a human study. We looked in detail at these human studies and found their quality mixed (for example, one human study was based on input from only one developer). Our results suggest that software developers are often talked about in APR studies, but are rarely talked with . A more comprehensive and reliable understanding of developer human factors in relation to APR is needed. Without this understanding, it will be difficult to develop APR tools and techniques which integrate effectively into developers' workflows. We recommend a future research agenda to advance the study of human factors in APR. |
doi_str_mv | 10.1109/TSE.2022.3152089 |
format | Article |
fullrecord | <record><control><sourceid>proquest_ieee_</sourceid><recordid>TN_cdi_ieee_primary_9714799</recordid><sourceformat>XML</sourceformat><sourcesystem>PC</sourcesystem><ieee_id>9714799</ieee_id><sourcerecordid>2761371832</sourcerecordid><originalsourceid>FETCH-LOGICAL-c333t-72d3a2fed0b89c6926ccdb541c647c5e9497e7910f8b0ffe6a8a39759a77be893</originalsourceid><addsrcrecordid>eNpNkM1LAzEQxYMoWKt3wUvAgxe35mN3s-Ot1PoBRUUrHkM2nbVbW7Mm2Yr_vVsq4ukxM-_Ngx8hx5wNOGdwMX0eDwQTYiB5JlgBO6THQUIiu2mX9BiDIsmyAvbJQQgLxlimVNYjeoLxLNCpWb7T1zrO6RWuceka9OGc3rtIh6Vr47_tJR3SJ1zX-EVdRYdtdCsTa0sfvXvzZtXdGlP7TgIab-eHZK8yy4BHv9onL9fj6eg2mTzc3I2Gk8RKKWOixEwaUeGMlQXYHERu7azMUm7zVNkMIQWFCjiripJVFeamMBJUBkapEguQfXK6_dt499liiHrhWv_RVWqhci4VL6ToXGzrst6F4LHSja9Xxn9rzvQGo-4w6g1G_Yuxi5xsIzUi_tlB8VQByB9qfG1j</addsrcrecordid><sourcetype>Aggregation Database</sourcetype><iscdi>true</iscdi><recordtype>article</recordtype><pqid>2761371832</pqid></control><display><type>article</type><title>Let's Talk With Developers, Not About Developers: A Review of Automatic Program Repair Research</title><source>IEEE Electronic Library (IEL)</source><creator>Winter, Emily ; Nowack, Vesna ; Bowes, David ; Counsell, Steve ; Hall, Tracy ; Haraldsson, Saemundur ; Woodward, John</creator><creatorcontrib>Winter, Emily ; Nowack, Vesna ; Bowes, David ; Counsell, Steve ; Hall, Tracy ; Haraldsson, Saemundur ; Woodward, John</creatorcontrib><description>Automatic program repair (APR) offers significant potential for automating some coding tasks. Using APR could reduce the high costs historically associated with fixing code faults and deliver significant benefits to software engineering. Adopting APR could also have profound implications for software developers' daily activities, transforming their work practices. To realise the benefits of APR it is vital that we consider how developers feel about APR and the impact APR may have on developers' work. Developing APR tools without consideration of the developer is likely to undermine the success of APR deployment. In this paper, we critically review how developers are considered in APR research by analysing how human factors are treated in 260 studies from Monperrus's Living Review of APR. Over half of the 260 studies in our review were motivated by a problem faced by developers (e.g., the difficulty associated with fixing faults). Despite these human-oriented motivations, fewer than 7% of the 260 studies included a human study. We looked in detail at these human studies and found their quality mixed (for example, one human study was based on input from only one developer). Our results suggest that software developers are often talked about in APR studies, but are rarely talked with . A more comprehensive and reliable understanding of developer human factors in relation to APR is needed. Without this understanding, it will be difficult to develop APR tools and techniques which integrate effectively into developers' workflows. We recommend a future research agenda to advance the study of human factors in APR.</description><identifier>ISSN: 0098-5589</identifier><identifier>EISSN: 1939-3520</identifier><identifier>DOI: 10.1109/TSE.2022.3152089</identifier><identifier>CODEN: IESEDJ</identifier><language>eng</language><publisher>New York: IEEE</publisher><subject>automatic program repair ; Bibliographies ; Fixing ; Human factors ; Maintenance engineering ; Repair ; Software ; Software development ; Software engineering ; Systematics ; Technological innovation</subject><ispartof>IEEE transactions on software engineering, 2023-01, Vol.49 (1), p.419-436</ispartof><rights>Copyright IEEE Computer Society 2023</rights><lds50>peer_reviewed</lds50><oa>free_for_read</oa><woscitedreferencessubscribed>false</woscitedreferencessubscribed><citedby>FETCH-LOGICAL-c333t-72d3a2fed0b89c6926ccdb541c647c5e9497e7910f8b0ffe6a8a39759a77be893</citedby><cites>FETCH-LOGICAL-c333t-72d3a2fed0b89c6926ccdb541c647c5e9497e7910f8b0ffe6a8a39759a77be893</cites><orcidid>0000-0002-6524-9179 ; 0000-0003-0395-5884 ; 0000-0002-2728-9014 ; 0000-0003-3314-7300 ; 0000-0002-2939-8919 ; 0000-0001-7014-2811 ; 0000-0002-2093-8990</orcidid></display><links><openurl>$$Topenurl_article</openurl><openurlfulltext>$$Topenurlfull_article</openurlfulltext><thumbnail>$$Tsyndetics_thumb_exl</thumbnail><linktohtml>$$Uhttps://ieeexplore.ieee.org/document/9714799$$EHTML$$P50$$Gieee$$Hfree_for_read</linktohtml><link.rule.ids>314,780,784,796,27924,27925,54758</link.rule.ids></links><search><creatorcontrib>Winter, Emily</creatorcontrib><creatorcontrib>Nowack, Vesna</creatorcontrib><creatorcontrib>Bowes, David</creatorcontrib><creatorcontrib>Counsell, Steve</creatorcontrib><creatorcontrib>Hall, Tracy</creatorcontrib><creatorcontrib>Haraldsson, Saemundur</creatorcontrib><creatorcontrib>Woodward, John</creatorcontrib><title>Let's Talk With Developers, Not About Developers: A Review of Automatic Program Repair Research</title><title>IEEE transactions on software engineering</title><addtitle>TSE</addtitle><description>Automatic program repair (APR) offers significant potential for automating some coding tasks. Using APR could reduce the high costs historically associated with fixing code faults and deliver significant benefits to software engineering. Adopting APR could also have profound implications for software developers' daily activities, transforming their work practices. To realise the benefits of APR it is vital that we consider how developers feel about APR and the impact APR may have on developers' work. Developing APR tools without consideration of the developer is likely to undermine the success of APR deployment. In this paper, we critically review how developers are considered in APR research by analysing how human factors are treated in 260 studies from Monperrus's Living Review of APR. Over half of the 260 studies in our review were motivated by a problem faced by developers (e.g., the difficulty associated with fixing faults). Despite these human-oriented motivations, fewer than 7% of the 260 studies included a human study. We looked in detail at these human studies and found their quality mixed (for example, one human study was based on input from only one developer). Our results suggest that software developers are often talked about in APR studies, but are rarely talked with . A more comprehensive and reliable understanding of developer human factors in relation to APR is needed. Without this understanding, it will be difficult to develop APR tools and techniques which integrate effectively into developers' workflows. We recommend a future research agenda to advance the study of human factors in APR.</description><subject>automatic program repair</subject><subject>Bibliographies</subject><subject>Fixing</subject><subject>Human factors</subject><subject>Maintenance engineering</subject><subject>Repair</subject><subject>Software</subject><subject>Software development</subject><subject>Software engineering</subject><subject>Systematics</subject><subject>Technological innovation</subject><issn>0098-5589</issn><issn>1939-3520</issn><fulltext>true</fulltext><rsrctype>article</rsrctype><creationdate>2023</creationdate><recordtype>article</recordtype><sourceid>ESBDL</sourceid><sourceid>RIE</sourceid><recordid>eNpNkM1LAzEQxYMoWKt3wUvAgxe35mN3s-Ot1PoBRUUrHkM2nbVbW7Mm2Yr_vVsq4ukxM-_Ngx8hx5wNOGdwMX0eDwQTYiB5JlgBO6THQUIiu2mX9BiDIsmyAvbJQQgLxlimVNYjeoLxLNCpWb7T1zrO6RWuceka9OGc3rtIh6Vr47_tJR3SJ1zX-EVdRYdtdCsTa0sfvXvzZtXdGlP7TgIab-eHZK8yy4BHv9onL9fj6eg2mTzc3I2Gk8RKKWOixEwaUeGMlQXYHERu7azMUm7zVNkMIQWFCjiripJVFeamMBJUBkapEguQfXK6_dt499liiHrhWv_RVWqhci4VL6ToXGzrst6F4LHSja9Xxn9rzvQGo-4w6g1G_Yuxi5xsIzUi_tlB8VQByB9qfG1j</recordid><startdate>20230101</startdate><enddate>20230101</enddate><creator>Winter, Emily</creator><creator>Nowack, Vesna</creator><creator>Bowes, David</creator><creator>Counsell, Steve</creator><creator>Hall, Tracy</creator><creator>Haraldsson, Saemundur</creator><creator>Woodward, John</creator><general>IEEE</general><general>IEEE Computer Society</general><scope>97E</scope><scope>ESBDL</scope><scope>RIA</scope><scope>RIE</scope><scope>AAYXX</scope><scope>CITATION</scope><scope>JQ2</scope><scope>K9.</scope><orcidid>https://orcid.org/0000-0002-6524-9179</orcidid><orcidid>https://orcid.org/0000-0003-0395-5884</orcidid><orcidid>https://orcid.org/0000-0002-2728-9014</orcidid><orcidid>https://orcid.org/0000-0003-3314-7300</orcidid><orcidid>https://orcid.org/0000-0002-2939-8919</orcidid><orcidid>https://orcid.org/0000-0001-7014-2811</orcidid><orcidid>https://orcid.org/0000-0002-2093-8990</orcidid></search><sort><creationdate>20230101</creationdate><title>Let's Talk With Developers, Not About Developers: A Review of Automatic Program Repair Research</title><author>Winter, Emily ; Nowack, Vesna ; Bowes, David ; Counsell, Steve ; Hall, Tracy ; Haraldsson, Saemundur ; Woodward, John</author></sort><facets><frbrtype>5</frbrtype><frbrgroupid>cdi_FETCH-LOGICAL-c333t-72d3a2fed0b89c6926ccdb541c647c5e9497e7910f8b0ffe6a8a39759a77be893</frbrgroupid><rsrctype>articles</rsrctype><prefilter>articles</prefilter><language>eng</language><creationdate>2023</creationdate><topic>automatic program repair</topic><topic>Bibliographies</topic><topic>Fixing</topic><topic>Human factors</topic><topic>Maintenance engineering</topic><topic>Repair</topic><topic>Software</topic><topic>Software development</topic><topic>Software engineering</topic><topic>Systematics</topic><topic>Technological innovation</topic><toplevel>peer_reviewed</toplevel><toplevel>online_resources</toplevel><creatorcontrib>Winter, Emily</creatorcontrib><creatorcontrib>Nowack, Vesna</creatorcontrib><creatorcontrib>Bowes, David</creatorcontrib><creatorcontrib>Counsell, Steve</creatorcontrib><creatorcontrib>Hall, Tracy</creatorcontrib><creatorcontrib>Haraldsson, Saemundur</creatorcontrib><creatorcontrib>Woodward, John</creatorcontrib><collection>IEEE All-Society Periodicals Package (ASPP) 2005-present</collection><collection>IEEE Open Access Journals</collection><collection>IEEE All-Society Periodicals Package (ASPP) 1998-Present</collection><collection>IEEE Electronic Library (IEL)</collection><collection>CrossRef</collection><collection>ProQuest Computer Science Collection</collection><collection>ProQuest Health & Medical Complete (Alumni)</collection><jtitle>IEEE transactions on software engineering</jtitle></facets><delivery><delcategory>Remote Search Resource</delcategory><fulltext>fulltext</fulltext></delivery><addata><au>Winter, Emily</au><au>Nowack, Vesna</au><au>Bowes, David</au><au>Counsell, Steve</au><au>Hall, Tracy</au><au>Haraldsson, Saemundur</au><au>Woodward, John</au><format>journal</format><genre>article</genre><ristype>JOUR</ristype><atitle>Let's Talk With Developers, Not About Developers: A Review of Automatic Program Repair Research</atitle><jtitle>IEEE transactions on software engineering</jtitle><stitle>TSE</stitle><date>2023-01-01</date><risdate>2023</risdate><volume>49</volume><issue>1</issue><spage>419</spage><epage>436</epage><pages>419-436</pages><issn>0098-5589</issn><eissn>1939-3520</eissn><coden>IESEDJ</coden><abstract>Automatic program repair (APR) offers significant potential for automating some coding tasks. Using APR could reduce the high costs historically associated with fixing code faults and deliver significant benefits to software engineering. Adopting APR could also have profound implications for software developers' daily activities, transforming their work practices. To realise the benefits of APR it is vital that we consider how developers feel about APR and the impact APR may have on developers' work. Developing APR tools without consideration of the developer is likely to undermine the success of APR deployment. In this paper, we critically review how developers are considered in APR research by analysing how human factors are treated in 260 studies from Monperrus's Living Review of APR. Over half of the 260 studies in our review were motivated by a problem faced by developers (e.g., the difficulty associated with fixing faults). Despite these human-oriented motivations, fewer than 7% of the 260 studies included a human study. We looked in detail at these human studies and found their quality mixed (for example, one human study was based on input from only one developer). Our results suggest that software developers are often talked about in APR studies, but are rarely talked with . A more comprehensive and reliable understanding of developer human factors in relation to APR is needed. Without this understanding, it will be difficult to develop APR tools and techniques which integrate effectively into developers' workflows. We recommend a future research agenda to advance the study of human factors in APR.</abstract><cop>New York</cop><pub>IEEE</pub><doi>10.1109/TSE.2022.3152089</doi><tpages>18</tpages><orcidid>https://orcid.org/0000-0002-6524-9179</orcidid><orcidid>https://orcid.org/0000-0003-0395-5884</orcidid><orcidid>https://orcid.org/0000-0002-2728-9014</orcidid><orcidid>https://orcid.org/0000-0003-3314-7300</orcidid><orcidid>https://orcid.org/0000-0002-2939-8919</orcidid><orcidid>https://orcid.org/0000-0001-7014-2811</orcidid><orcidid>https://orcid.org/0000-0002-2093-8990</orcidid><oa>free_for_read</oa></addata></record> |
fulltext | fulltext |
identifier | ISSN: 0098-5589 |
ispartof | IEEE transactions on software engineering, 2023-01, Vol.49 (1), p.419-436 |
issn | 0098-5589 1939-3520 |
language | eng |
recordid | cdi_ieee_primary_9714799 |
source | IEEE Electronic Library (IEL) |
subjects | automatic program repair Bibliographies Fixing Human factors Maintenance engineering Repair Software Software development Software engineering Systematics Technological innovation |
title | Let's Talk With Developers, Not About Developers: A Review of Automatic Program Repair Research |
url | https://sfx.bib-bvb.de/sfx_tum?ctx_ver=Z39.88-2004&ctx_enc=info:ofi/enc:UTF-8&ctx_tim=2024-12-24T22%3A54%3A25IST&url_ver=Z39.88-2004&url_ctx_fmt=infofi/fmt:kev:mtx:ctx&rfr_id=info:sid/primo.exlibrisgroup.com:primo3-Article-proquest_ieee_&rft_val_fmt=info:ofi/fmt:kev:mtx:journal&rft.genre=article&rft.atitle=Let's%20Talk%20With%20Developers,%20Not%20About%20Developers:%20A%20Review%20of%20Automatic%20Program%20Repair%20Research&rft.jtitle=IEEE%20transactions%20on%20software%20engineering&rft.au=Winter,%20Emily&rft.date=2023-01-01&rft.volume=49&rft.issue=1&rft.spage=419&rft.epage=436&rft.pages=419-436&rft.issn=0098-5589&rft.eissn=1939-3520&rft.coden=IESEDJ&rft_id=info:doi/10.1109/TSE.2022.3152089&rft_dat=%3Cproquest_ieee_%3E2761371832%3C/proquest_ieee_%3E%3Curl%3E%3C/url%3E&disable_directlink=true&sfx.directlink=off&sfx.report_link=0&rft_id=info:oai/&rft_pqid=2761371832&rft_id=info:pmid/&rft_ieee_id=9714799&rfr_iscdi=true |