Test-Driven Scenario Specification of Automotive Software Components

Wiecher, Carsten; Greenyer, Joel; Korte, Jan

doi:10.1109/models-c.2019.00009

Cited by 13 publications

(32 citation statements)

References 11 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Kotlin concepts such as higher-order functions, extension functions, channels and coroutines are used to create an internal DSL that enables a concise specification of scenarios. A first application of SMLK is described in [41] and the underlying concepts are described in [14]. In SMLK, several scenarios are combined within a scenario specification and can be executed as a scenario program.…”

Section: Scenario Modeling Language For Kotlin (Smlk)mentioning

confidence: 99%

“…SMLK also allows scenario programs to be open, which means that they can receive events from external programs, possibly again scenario programs. This way, we can use the same language to also model/program tests and environment models for a given scenario program, even allowing for a test-first scenario-based modeling/programming approach, which we described previously [41].…”

Section: Scenario Modeling Language For Kotlin (Smlk)mentioning

confidence: 99%

“…Based on the context and principles outlined above, this section describes the SCIL approach. The SCIL approach is built on three process layers (Communication and Documentation Layer, Modeling Layer, Validation Layer), which, via suitable tool support, enable an iterative and scenario-based requirements analysis [41] and automated system validation. The individual process steps on the different layers, their relationships and the required or arising artifacts are outlined in Fig.…”

Section: Scenarios In the Loop (Scil)mentioning

confidence: 99%

“…Now we enter the test-driven scenario specification (TDSS) subprocess (as described in previous work [41]). In step (5), the validation engineer completes the generated test skeletons to a test that sends SMLK object events as input to an SMLK program and formulates assertions on the reactions of that SMLK program.…”

Section: Listing 3: Generated Test Skeleton -Based On Req2mentioning

confidence: 99%

“…SCIL was developed following the design science research (DSR) approach [8]. A central component of SCIL is the Scenario Modeling Language for Kotlin (SMLK), which allows for an intuitive yet executable modeling of system behavior [41]. SMLK is based on the concepts of Live Sequence Charts (LSC) [5], Behavioral Programming (BP) [14] and the Scenario Modeling Language (SML) [12].…”

Section: Introductionmentioning

confidence: 99%

See 4 more Smart Citations

Scenarios in the loop

Wiecher

Japs

Kaiser

et al. 2020

Proceedings of the 23rd ACM/IEEE International Conference on Model Driven Engineering Languages and Systems: Companion Proceedi

Self Cite

View full text Add to dashboard Cite

The development of safety-relevant systems in the automotive industry requires the definition of high-quality requirements and tests for the coordination and monitoring of development activities in an agile development environment. In this paper we describe a Scenarios in the Loop (SCIL) approach. SCIL combines (1) natural language requirements specification based on Behavior-Driven Development (BDD) with (2) formal and test-driven requirements modeling and analysis, and (3) integrates discipline-specific tools for software and system validation during development. A central element of SCIL is a flexible and executable scenario-based modeling language, the Scenario Modeling Language for Kotlin (SMLK). SMLK allows for an intuitive requirements formalization, and supports engineers to move iteratively, and continuously aided by automated checks, from stakeholder requirements to the validation of the implemented system. We evaluated the approach using a real example from the field of e-mobility. CCS CONCEPTS • Software and its engineering → System modeling languages; Agile software development.

show abstract

Section: Scenario Modeling Language For Kotlin (Smlk)mentioning

confidence: 99%

Section: Scenario Modeling Language For Kotlin (Smlk)mentioning

confidence: 99%

Section: Scenarios In the Loop (Scil)mentioning

confidence: 99%

Section: Listing 3: Generated Test Skeleton -Based On Req2mentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

Scenarios in the loop

Wiecher

Japs

Kaiser

et al. 2020

Proceedings of the 23rd ACM/IEEE International Conference on Model Driven Engineering Languages and Systems: Companion Proceedi

Self Cite

View full text Add to dashboard Cite

show abstract

Model‐based analysis and specification of functional requirements and tests for complex automotive systems

Wiecher,

Mandel,

Günther

et al. 2024

Systems Engineering

Self Cite

View full text Add to dashboard Cite

The specification of requirements and tests are crucial activities in automotive development projects. However, due to the increasing complexity of automotive systems, practitioners fail to specify requirements and tests for distributed and evolving systems with complex interactions when following traditional development processes. To address this research gap, we propose a technique that starts with the early identification of validation concerns from a stakeholder perspective, which we use to systematically design tests that drive a scenario‐based modeling and analysis of system requirements. To ensure complete and consistent requirements and test specifications in a form that is required in automotive development projects, we develop a Model‐Based Systems Engineering (MBSE) methodology. This methodology supports system architects and test designers in the collaborative application of our technique and in maintaining a central system model, in order to automatically derive the required specifications. We evaluate our methodology by applying it at KOSTAL (Tier1 supplier) and within student projects as part of the masters program Embedded Systems Engineering. Our study corroborates that our methodology is applicable and improves existing requirements and test specification processes by supporting the integrated and stakeholder‐focused modeling of product and validation systems, where the early definition of stakeholder and validation concerns fosters a problem‐oriented, iterative and test‐driven requirements modeling.

show abstract