Analyzing an automotive testing process with evidence-based software engineering
(2013) In Information and Software Technology 55(7). p.1237-1259- Abstract
- Context: Evidence-based software engineering (EBSE) provides a process for solving practical problems based on a rigorous research approach. The primary focus so far was on mapping and aggregating evidence through systematic reviews. Objectives: We extend existing work on evidence-based software engineering by using the EBSE process in an industrial case to help an organization to improve its automotive testing process. With this we contribute in (1) providing experiences on using evidence based processes to analyze a real world automotive test process and (2) provide evidence of challenges and related solutions for automotive software testing processes. Methods: In this study we perform an in-depth investigation of an automotive test... (More)
- Context: Evidence-based software engineering (EBSE) provides a process for solving practical problems based on a rigorous research approach. The primary focus so far was on mapping and aggregating evidence through systematic reviews. Objectives: We extend existing work on evidence-based software engineering by using the EBSE process in an industrial case to help an organization to improve its automotive testing process. With this we contribute in (1) providing experiences on using evidence based processes to analyze a real world automotive test process and (2) provide evidence of challenges and related solutions for automotive software testing processes. Methods: In this study we perform an in-depth investigation of an automotive test process using an extended EBSE process including case study research (gain an understanding of practical questions to define a research scope), systematic literature review (identify solutions through systematic literature), and value stream mapping (map out an improved automotive test process based on the current situation and improvement suggestions identified). These are followed by reflections on the EBSE process used. Results: In the first step of the EBSE process we identified 10 challenge areas with a total of 26 individual challenges. For 15 out of those 26 challenges our domain specific systematic literature review identified solutions. Based on the input from the challenges and the solutions, we created a value stream map of the current and future process. Conclusions: Overall, we found that the evidence-based process as presented in this study helps in technology transfer of research results to industry, but at the same time some challenges lie ahead (e.g. koping systematic reviews to focus more on concrete industry problems, and understanding strategies of conducting EBSE with respect to effort and quality of the evidence). (C) 2013 Elsevier B.V. All rights reserved. (Less)
Please use this url to cite or link to this publication:
https://lup.lub.lu.se/record/3980095
- author
- Kasoju, Abhinaya ; Petersen, Kai and Mäntylä, Mika LU
- organization
- publishing date
- 2013
- type
- Contribution to journal
- publication status
- published
- subject
- keywords
- Evidence-based software engineering, Process assessment, Automotive, software testing
- in
- Information and Software Technology
- volume
- 55
- issue
- 7
- pages
- 1237 - 1259
- publisher
- Elsevier
- external identifiers
-
- wos:000320217900007
- scopus:84877922741
- ISSN
- 0950-5849
- DOI
- 10.1016/j.infsof.2013.01.005
- language
- English
- LU publication?
- yes
- id
- fe03d6ac-bd65-4d5b-a4c3-a739ed2fe9a2 (old id 3980095)
- date added to LUP
- 2016-04-01 13:52:12
- date last changed
- 2022-02-04 17:50:37
@article{fe03d6ac-bd65-4d5b-a4c3-a739ed2fe9a2,
abstract = {{Context: Evidence-based software engineering (EBSE) provides a process for solving practical problems based on a rigorous research approach. The primary focus so far was on mapping and aggregating evidence through systematic reviews. Objectives: We extend existing work on evidence-based software engineering by using the EBSE process in an industrial case to help an organization to improve its automotive testing process. With this we contribute in (1) providing experiences on using evidence based processes to analyze a real world automotive test process and (2) provide evidence of challenges and related solutions for automotive software testing processes. Methods: In this study we perform an in-depth investigation of an automotive test process using an extended EBSE process including case study research (gain an understanding of practical questions to define a research scope), systematic literature review (identify solutions through systematic literature), and value stream mapping (map out an improved automotive test process based on the current situation and improvement suggestions identified). These are followed by reflections on the EBSE process used. Results: In the first step of the EBSE process we identified 10 challenge areas with a total of 26 individual challenges. For 15 out of those 26 challenges our domain specific systematic literature review identified solutions. Based on the input from the challenges and the solutions, we created a value stream map of the current and future process. Conclusions: Overall, we found that the evidence-based process as presented in this study helps in technology transfer of research results to industry, but at the same time some challenges lie ahead (e.g. koping systematic reviews to focus more on concrete industry problems, and understanding strategies of conducting EBSE with respect to effort and quality of the evidence). (C) 2013 Elsevier B.V. All rights reserved.}},
author = {{Kasoju, Abhinaya and Petersen, Kai and Mäntylä, Mika}},
issn = {{0950-5849}},
keywords = {{Evidence-based software engineering; Process assessment; Automotive; software testing}},
language = {{eng}},
number = {{7}},
pages = {{1237--1259}},
publisher = {{Elsevier}},
series = {{Information and Software Technology}},
title = {{Analyzing an automotive testing process with evidence-based software engineering}},
url = {{http://dx.doi.org/10.1016/j.infsof.2013.01.005}},
doi = {{10.1016/j.infsof.2013.01.005}},
volume = {{55}},
year = {{2013}},
}