Please use this identifier to cite or link to this item: http://bura.brunel.ac.uk/handle/2438/26020
Full metadata record
DC FieldValueLanguage
dc.contributor.authorOrtu, M-
dc.contributor.authorDestefanis, G-
dc.contributor.authorHall, T-
dc.contributor.authorBowes, D-
dc.date.accessioned2023-02-28T09:23:19Z-
dc.date.available2023-02-28T09:23:19Z-
dc.date.issued2023-02-24-
dc.identifierORCID iD: Giuseppe Destefanis https://orcid.org/0000-0003-3982-6355.-
dc.identifier107187-
dc.identifier.citationOrtu, M. et al. (2023) 'Fault-insertion and fault-fixing behavioural patterns in Apache Software Foundation Projects', Information and Software Technology, 158, 107187, pp. 1 - 21. doi: 10.1016/j.infsof.2023.107187.en_US
dc.identifier.issn0950-5849-
dc.identifier.urihttps://bura.brunel.ac.uk/handle/2438/26020-
dc.descriptionData availability: Data are available [as described in the article].en_US
dc.description.abstractCopyright © 2023 The Authors. Background: Developers inevitably make human errors while coding. These errors can lead to faults in code, some of which may result in system failures. It is important to reduce the faults inserted by developers as well as fix any that slip through. Aim: To investigate the fault insertion and fault fixing activities of developers. We identify developers who insert and fix faults, ask whether code topic ‘experts’ insert fewer faults, and experts fix more faults and whether patterns of insertion and fixing change over time. Methods: We perform a time-based analysis of developer activity on twelve Apache projects using Latent Dirichlet Allocation (LDA), Network Analysis and Topic Modelling. We also build three models (using Petri-net, Markov Chain and Hawkes Processes) which describe and simulate developers’ bug-introduction and fixing behaviour. Results: We show that: the majority of the projects we analysed have developers who dominate in the insertion and fixing of faults; Faults are less likely to be inserted by developers with code topic expertise; Different projects have different patterns of fault inserting and fixing over time. Conclusions: We recommend that projects identify the code topic expertise of developers and use expertise information to inform the assignment of project work.en_US
dc.description.sponsorshipPartly funded by grants from the UK’s Engineering and Physical Sciences Research Council (EP/S005730/1 and EP/S005749/2).en_US
dc.format.extent1 - 21-
dc.format.mediumPrint-Electronic-
dc.languageEnglish-
dc.language.isoen_USen_US
dc.publisherElsevieren_US
dc.rightsCopyright © 2023 The Authors. Published by Elsevier B.V. under a Creative Commons license (https://creativecommons.org/licenses/by/4.0/).-
dc.rights.urihttps://creativecommons.org/licenses/by/4.0/-
dc.subjectanalysisen_US
dc.subjectLDAen_US
dc.subjectMining software repositoriesen_US
dc.titleFault-insertion and fault-fixing behavioural patterns in Apache Software Foundation Projectsen_US
dc.typeArticleen_US
dc.identifier.doihttps://doi.org/10.1016/j.infsof.2023.107187-
dc.relation.isPartOfInformation and Software Technology-
pubs.publication-statusPublished-
pubs.volume158-
dc.identifier.eissn1873-6025-
dc.rights.holderThe Authors-
Appears in Collections:Dept of Computer Science Research Papers

Files in This Item:
File Description SizeFormat 
FullText.pdfCopyright © 2023 The Authors. Published by Elsevier B.V. under a Creative Commons license (https://creativecommons.org/licenses/by/4.0/).5.45 MBAdobe PDFView/Open


This item is licensed under a Creative Commons License Creative Commons