Show simple item record

dc.contributor.authorMohammadnazar, Hojat
dc.contributor.authorPulkkinen, Mirja
dc.contributor.authorGhanbari, Hadi
dc.date.accessioned2019-07-24T05:15:32Z
dc.date.available2019-07-24T05:15:32Z
dc.date.issued2019
dc.identifier.citationMohammadnazar, H., Pulkkinen, M., & Ghanbari, H. (2019). A Root Cause Analysis Method for Preventing Erratic Behavior in Software Development: PEBA. <i>Reliability Engineering and System Safety</i>, <i>191</i>, Article 106565. <a href="https://doi.org/10.1016/j.ress.2019.106565" target="_blank">https://doi.org/10.1016/j.ress.2019.106565</a>
dc.identifier.otherCONVID_32095328
dc.identifier.urihttps://jyx.jyu.fi/handle/123456789/65095
dc.description.abstractMeasures taken to prevent faults from being introduced or going undetected can secure development of highly reliable software systems. One such measure is analyzing root causes of recurring faults and preventing them from appearing again. Previous methods developed for this purpose have been reactive in nature and relied heavily on fault reporting mechanisms of ogranizations. Additionally, previous efforts lack a defined mechanism for innovating corrective actions. In this study, we strive to complement the existing methods by introducing a proactive and qualitative method that does not rely on fault data. During the course of the research, in addition to an extensive literature search, an empirical field study is conducted with representatives of companies active in safety-critical and business-critical domains. Our proposed method relies on identifying mismatches between development practices and development context in order to predict erratic behaviors. Corrective actions in this method are innovated by resolving these mismatches. The use of the method is demonstrated in two safety-critical projects. Evaluation of the proposed method is done by two experts with respect to proactivity, resource-intensity, and effectiveness.en
dc.format.mimetypeapplication/pdf
dc.languageeng
dc.language.isoeng
dc.publisherElsevier
dc.relation.ispartofseriesReliability Engineering and System Safety
dc.rightsCC BY-NC-ND 4.0
dc.subject.othersoftware reliability
dc.subject.otherfault prevention
dc.subject.otherfault removal
dc.subject.otherquality assurance
dc.subject.otherroot cause analysis
dc.subject.othersoftware process improvement
dc.titleA Root Cause Analysis Method for Preventing Erratic Behavior in Software Development: PEBA
dc.typearticle
dc.contributor.laitosInformaatioteknologian tiedekuntafi
dc.contributor.laitosFaculty of Information Technologyen
dc.contributor.oppiaineTietojärjestelmätiedefi
dc.contributor.oppiaineInformation Systems Scienceen
dc.type.urihttp://purl.org/eprint/type/JournalArticle
dc.type.coarhttp://purl.org/coar/resource_type/c_2df8fbb1
dc.description.reviewstatuspeerReviewed
dc.relation.issn0951-8320
dc.relation.volume191
dc.type.versionacceptedVersion
dc.rights.copyright© 2019 Elsevier Inc.
dc.rights.accesslevelopenAccessfi
dc.subject.ysoohjelmistokehitys
dc.subject.ysoohjelmistotekniikka
dc.subject.ysotietokoneohjelmat
dc.format.contentfulltext
jyx.subject.urihttp://www.yso.fi/onto/yso/p21530
jyx.subject.urihttp://www.yso.fi/onto/yso/p6297
jyx.subject.urihttp://www.yso.fi/onto/yso/p26592
dc.rights.urlhttps://creativecommons.org/licenses/by-nc-nd/4.0/
dc.relation.doi10.1016/j.ress.2019.106565
jyx.fundinginformationTekes 11011.
dc.type.okmA1


Files in this item

Thumbnail

This item appears in the following Collection(s)

Show simple item record

CC BY-NC-ND 4.0
Except where otherwise noted, this item's license is described as CC BY-NC-ND 4.0