Scenarios in the loop

Abstract

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.

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

“…Due to frequent changing stakeholder requirements, practitioners increasingly fail to specify high-quality system requirements and tests for complex automotive systems. 3,9 We already addressed this research gap in previous work and proposed an integrated and iterative requirements analysis and test specification approach to support both the analysis and specification of requirements and tests in an early development phase [10][11][12][13][14] Motivated by the test-driven development paradigm, 15 this approach is based on the idea that requirements modeling can be driven by test cases to create immediate feedback in short iterations and increase the applicability of formal requirements modeling in practice. Instead of deriving test cases from system requirements manually, we use existing stakeholder requirements to generate acceptance tests that drive the modeling of system requirements.…”

“…Due to frequent changing stakeholder requirements, practitioners increasingly fail to specify high‐quality system requirements and tests for complex automotive systems 3,9 . We already addressed this research gap in previous work and proposed an integrated and iterative requirements analysis and test specification approach to support both the analysis and specification of requirements and tests in an early development phase 10–14 …”

Desarrollo guiado por comportamiento: buenas prácticas para la calidad de software

“…Como afirma [31] los escenarios siempre prueban una funcionalidad, son representaciones de historias de usuario en que es necesaria la especificación en detalle de cada componente y método funcional con palabras clave. [32] y [33] argumentan que el uso de Gherkin permite obtener documentación en 60 lenguajes bajo sintaxis descriptiva del comportamiento. Asimismo [34] y [35] expresan que la prueba de escenarios nos facilita conocer ampliamente cada parte funcional del sistema con la posibilidad de Desarrollo guiado por comportamiento: buenas prácticas para la calidad de software Aldo Emanuel Soraluz Soraluz, Miguel Ángel Valles Coral, Danny Lévano Rodríguez observar errores mediante pruebas dirigidas, y así realizar la corrección respectiva de manera anticipada.…”

Specifying Internet of Things Behaviors in Behavior-Driven Development: Concurrency Enhancement and Tool Support

“…With an ample amount of the literature (e.g., [9][10][11][12]) and many supporting tools available (e.g., [13]), BDD makes a good candidate methodology for IoT system development. Indeed, we are beginning to see positive results in applying BDD for developing real-time embedded systems [14], automotive systems [15,16], and avionic systems [17]. In our own experience, we have also benefited from BDD in the development of a smart cone system for protecting road maintenance crews working on highways [18].…”