A1 Alkuperäisartikkeli tieteellisessä aikakauslehdessä
A Root Cause Analysis Method for Preventing Erratic Behavior in Software Development: PEBA (2019)
Mohammadnazar, H., Pulkkinen, M., & Ghanbari, H. (2019). A Root Cause Analysis Method for Preventing Erratic Behavior in Software Development: PEBA. Reliability Engineering and System Safety, 191, Article 106565. https://doi.org/10.1016/j.ress.2019.106565
JYU-tekijät tai -toimittajat
Julkaisun tiedot
Julkaisun kaikki tekijät tai toimittajat: Mohammadnazar, Hojat; Pulkkinen, Mirja; Ghanbari, Hadi
Lehti tai sarja: Reliability Engineering and System Safety
ISSN: 0951-8320
eISSN: 1879-0836
Julkaisuvuosi: 2019
Volyymi: 191
Artikkelinumero: 106565
Kustantaja: Elsevier
Julkaisumaa: Britannia
Julkaisun kieli: englanti
DOI: https://doi.org/10.1016/j.ress.2019.106565
Julkaisun avoin saatavuus: Ei avoin
Julkaisukanavan avoin saatavuus:
Julkaisu on rinnakkaistallennettu (JYX): https://jyx.jyu.fi/handle/123456789/65095
Tiivistelmä
Measures 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.
YSO-asiasanat: tietokoneohjelmat; ohjelmistokehitys; ohjelmistotekniikka
Vapaat asiasanat: software reliability; fault prevention; fault removal; quality assurance; root cause analysis; software process improvement
Liittyvät organisaatiot
OKM-raportointi: Kyllä
Raportointivuosi: 2019
JUFO-taso: 2
