To the top

Page Manager: Webmaster
Last update: 9/11/2012 3:13 PM

Tell a friend about this page
Print version

The impact of requirement… - University of Gothenburg, Sweden Till startsida
Sitemap
To content Read more about how we use cookies on gu.se

The impact of requirements on systems development speed: a multiple-case study in automotive

Journal article
Authors Magnus Ågren
Eric Knauss
Rogardt Heldal
Patrizio Pelliccione
Gösta Malmqvist
Jonas Bodén
Published in Requirements Engineering
Volume 24
Issue 3
Pages 315-340
ISSN 0947-3602
Publication year 2019
Published at Institutionen för data- och informationsteknik, Software Engineering (GU)
Pages 315-340
Language en
Links dx.doi.org/10.1007/s00766-019-00319...
Keywords requirements engineering; continuous software engineering; automotive systems engineering
Subject categories Software Engineering

Abstract

Context: Automotive manufacturers have historically adopted rigid requirements engineering processes. This allowed them to meet safety-critical requirements when producing a highly complex and differentiated product out of the integration of thousands of physical and software components. Nowadays, few software-related domains are as rapidly changing as the automotive industry. In particular, the needs of improving development speed are increasingly pushing companies in this domain towards new ways of developing software. Objectives: In this paper, we investigate how the goal to increase development speed impacts how requirements are managed in the automotive domain. We start from a manager perspective, which we then complement with a more general perspective. Methods: We used a qualitative multiple-case study, organized in two steps. In the first step, we had 20 semi- structured interviews, at two automotive manufacturers. Our sampling strategy focuses on manager roles, complemented with technical specialists. In the second step, we validated our results with 12 more interviews, covering 9 additional respondents and 3 recurring from the first step. In addition to validating our qualitative model, the second step of interviews broadens our perspective with technical experts and change managers. Results: Our respondents indicate and rank six aspects of the current requirements engineering approach that impact development speed. These aspects include the negative impact of a requirements style dominated by safety concerns as well as decomposition of requirements over many levels of abstraction. Furthermore, the use of requirements as part of legal contracts with suppliers is seen as hindering fast collaboration. Six additional suggestions for potential improvements include domain-specific tooling, model-based requirements, test automation, and a combination of lightweight upfront requirements engineering preceding development with precise specifications post-development. Out of these 12 aspects, 7 can likely be addressed as part of an ongoing agile transformation. Conclusions: We offer an empirical account of expectations and needs for new requirements engineering approaches in the automotive domain, necessary to coordinate hundreds of collaborating organizations devel- oping software-intensive and potentially safety-critical systems.

Page Manager: Webmaster|Last update: 9/11/2012
Share:

The University of Gothenburg uses cookies to provide you with the best possible user experience. By continuing on this website, you approve of our use of cookies.  What are cookies?