Integrated and Iterative Requirements Analysis and Test Specification: A Case Study at Kostal

Currently, practitioners follow a top-down approach in automotive development projects. However, recent studies have shown that this top-down approach is not suitable for the implementation and testing of modern automotive systems. Specifically, practitioners increasingly fail to specify requirements and tests for systems with complex component interactions (e.g., e-mobility systems). In this paper, we address this research gap and propose an integrated and iterative scenario-based technique for the specification of requirements and test scenarios. Our idea is to combine both a top-down and a bottom-up integration strategy. For the top-down approach, we use a behavior-driven development (BDD) technique to drive the modeling of high-level system interactions from the user's perspective. For the bottom-up approach, we discovered that natural language processing (NLP) techniques are suited to make textual specifications of existing components accessible to our technique. To integrate both directions, we support the joint execution and automated analysis of system-level interactions and component-level behavior. We demonstrate the feasibility of our approach by conducting a case study at Kostal (Tierl supplier). The case study corroborates, among other things, that our approach supports practitioners in improving requirements and test specifications for integrated system behavior.

[1]  Eric Knauss,et al.  Requirements engineering challenges and practices in large-scale agile system development , 2021, J. Syst. Softw..

[2]  Joel Greenyer,et al.  Scenarios in the loop: integrated requirements analysis and automotive system validation , 2020, MoDELS.

[3]  Alistair G. Sutcliffe,et al.  Scenario-based requirements engineering , 2003, Proceedings. 11th IEEE International Requirements Engineering Conference, 2003..

[4]  Daniel Pacheco Lacerda,et al.  Design Science Research: A Method for Science and Technology Advancement , 2014 .

[5]  Andreas Vogelsang,et al.  Bridging the Gap between Systems and Software Engineering by Using the SPES Modeling Framework as a General Systems Engineering Philosophy , 2014, CSER.

[6]  Oscar Ljungkrantz,et al.  Organisation and communication problems in automotive requirements engineering , 2018, Requirements Engineering.

[7]  David Harel,et al.  LSCs: Breathing Life into Message Sequence Charts , 1999, Formal Methods Syst. Des..

[8]  Guy Katz,et al.  ScenarioTools - A tool suite for the scenario-based modeling and analysis of reactive systems , 2017, Sci. Comput. Program..

[9]  Gary Rushton,et al.  A System of Systems Approach to Automotive Challenges , 2018 .

[10]  Birgit Penzenstadler,et al.  DeSyRe: decomposition of systems and their requirements: transition from system to subsystem using a criteria catalogue and systematic requirements refinement , 2010 .

[11]  Manfred Broy,et al.  Guiding requirements engineering for software-intensive embedded systems in the automotive industry , 2014, Computer Science - Research and Development.

[12]  Matthias Tichy,et al.  Use, potential, and showstoppers of models in automotive requirements engineering , 2019, Software & Systems Modeling.

[13]  Carsten Wiecher,et al.  A feature-oriented approach: from usage scenarios to automated system of systems validation in the automotive domain , 2020, MoDELS.

[14]  Andreas Vogelsang,et al.  Automatic Detection of Causality in Requirement Artifacts: the CiRA Approach , 2021, REFSQ.

[15]  David Schmelter,et al.  Cutting through the Jungle: Disambiguating Model-based Traceability Terminology , 2020, 2020 IEEE 28th International Requirements Engineering Conference (RE).

[16]  Albert Albers,et al.  Verifikation und Validierung im Produktentstehungsprozess , 2016 .

[17]  Jo Ann Lane,et al.  What is a System of Systems and Why Should I Care , 2013 .

[18]  Cornelius Ncube,et al.  On Systems of Systems Engineering: A Requirements Engineering Perspective and Research Agenda , 2018, 2018 IEEE 26th International Requirements Engineering Conference (RE).

[19]  Joel Greenyer,et al.  Iterative and Scenario-based Requirements Specification in a System of Systems Context , 2021, REFSQ.

[20]  Matthias Tichy,et al.  Challenges concerning test case specifications in automotive software testing: assessment of frequency and criticality , 2020, Software Quality Journal.

[21]  Joel Greenyer,et al.  BeSoS: A Tool for Behavior-driven and Scenario-based Requirements Modeling for Systems of Systems , 2021, REFSQ Workshops.

[22]  Robert L. Probert,et al.  Cause-effect graphing analysis and validation of requirements , 1995, CASCON.

[23]  Joel Greenyer,et al.  Test-Driven Scenario Specification of Automotive Software Components , 2019, 2019 ACM/IEEE 22nd International Conference on Model Driven Engineering Languages and Systems Companion (MODELS-C).

[24]  Hermann de Meer,et al.  E-Mobility Systems Architecture: a model-based framework for managing complexity and interoperability , 2019 .

[25]  H. D. Rombach,et al.  The Goal Question Metric Approach , 1994 .

[26]  Jan Peleska,et al.  Systems of Systems Engineering , 2015 .

[27]  Christoph Schmittner,et al.  Status of the Development of ISO/SAE 21434 , 2018, EuroSPI.

[28]  Andreas Vogelsang,et al.  SPECMATE: Automated Creation of Test Cases from Acceptance Criteria , 2020, 2020 IEEE 13th International Conference on Software Testing, Validation and Verification (ICST).

[29]  David Harel,et al.  Specifying and executing behavioral requirements: the play-in/play-out approach , 2003, Software & Systems Modeling.