Practicing Continuous Integration in a Multi-Supplier Environment for the Development of Automotive Software
| dc.contributor.author | Abazi, Evio | |
| dc.contributor.department | Chalmers tekniska högskola / Institutionen för data och informationsteknik | sv |
| dc.contributor.examiner | Steghöfer, Jan-Philipp | |
| dc.contributor.supervisor | Durisic, Darko | |
| dc.contributor.supervisor | Staron, Miroslaw | |
| dc.date.accessioned | 2019-08-21T12:22:16Z | |
| dc.date.available | 2019-08-21T12:22:16Z | |
| dc.date.issued | 2019 | sv |
| dc.date.submitted | 2019 | |
| dc.description.abstract | Background: Software development in the automotive industry is in transition from the traditional V-Model to the adoption of Agile methods. Continuous Integration (CI) is one of the most adopted practices when working Agile since it enables faster feedback, workflow automation and allows constant testing activities. However, in the automotive software development process are involved OEMs and multiple suppliers; the practice of continuous integration in similar projects may present several challenges. Objective: The study aims to investigate the problems related to the practice of continuous integration in a multi-supplier environment for the development of automotive software. Moreover, it identifies the root causes of such problems and provides potential solutions for preventing them. Methodology: The thesis is based on qualitative research. An explorative case study was conducted at the development sections of an OEM company and a Tier 2 software vendor. Observations and interviews at both companies allowed to discover the main problems related to the adoption of continuous integration. A Pareto analysis, in combination with Cause-and-Effect diagrams, identified the root causes that had a major impact on the discovered challenges. Results: Eight challenges are identified; their root causes are related to the development tools adopted, lack of synchronization and barriers to effective communication. In addition, potential solutions for the causes are provided and implemented in a demonstrative CI environment for the development of a sample application. Conclusions: The study reports the challenges of practicing continuous integration in automotive software development. In addition, the results show opportunities for improvement for the identified problems. Since it is a single case study, the generalizability of the results is still limited; however, inputs are provided to the companies for improving their development process, and valuable research insights are provided into the obstacles associated with the practice of continuous integration in automotive software development. | sv |
| dc.identifier.coursecode | DATX05 | sv |
| dc.identifier.uri | https://hdl.handle.net/20.500.12380/300144 | |
| dc.language.iso | eng | sv |
| dc.setspec.uppsok | Technology | |
| dc.subject | software development | sv |
| dc.subject | automotive | sv |
| dc.subject | embedded systems | sv |
| dc.subject | agile | sv |
| dc.subject | continuous integration | sv |
| dc.subject | cinders | sv |
| dc.subject | challenges | sv |
| dc.title | Practicing Continuous Integration in a Multi-Supplier Environment for the Development of Automotive Software | sv |
| dc.type.degree | Examensarbete för masterexamen | sv |
| dc.type.uppsok | H | |
| local.programme | Software engineering and technology (MPSOF), MSc |