Abstract

Project success in the automotive industry is highly influenced by requirements engineering (RE), for which communication and organisation structure play a major role, much due to the scale and distribution of these projects. However, empirical research is scarce on these aspects of automotive RE and warrants closer examination. Therefore, the purpose of this paper is to identify problems or challenges in automotive RE with respect to communication and organisation structure. Using a multiple-case study approach, we collected data via 14 semi-structured interviews at one car manufacturer and one supplier. We tested our findings from the case study with a questionnaire distributed to practitioners in the automotive industry. Our results indicate that it is difficult but increasingly important to establish communication channels outside the fixed organisation structure and that responsibilities are often unclear. Product knowledge during early requirements elicitation and context knowledge later on is lacking. Furthermore, abstraction gaps between requirements on different abstraction levels leads to inconsistencies. For academia, we formulate a concrete agenda for future research. Practitioners can use the findings to broaden their understanding of how the problems manifest and to improve their organisations.

Highlights

  • In order to successfully manage the rapid increase in software size and complexity in the embedded systems domain [20], requirements need to be communicated and coordinated [8]

  • We describe each of the seven identified problems/challenges and discuss them in relation to our cases

  • The Area row depicts the percentage of interviewees who brought up the problem in the areas of embedded software engineering (EmbSE), systems engineering (SysEng) and application software engineering (AppSE)

Read more

Summary

Introduction

In order to successfully manage the rapid increase in software size and complexity in the embedded systems domain [20], requirements need to be communicated and coordinated [8]. This need arises in particular as an organisation is broken down into independent pieces [35], i.e., for large companies which are common in this domain. Demands on compatibility of subsystems are high, as components are reused across vehicle models. This means that vehicle projects rarely start from scratch but rather evolve existing specifications. The high degree of safety critical functions and the large production volume greatly influence the costs of errors made during development [37], making automotive projects highly cost

Objectives
Results
Conclusion
Full Text
Paper version not known

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call