BeSoS: A Tool for Behavior-driven and Scenario-based Requirements Modeling for Systems of Systems

Systems of Systems (SoS), like connected vehicle systems, provide their functionality by the interaction of several constituent systems (CSs). [Problem] Due to the managerial, operational and evolutionary independence of the CSs in an SoS, requirements constantly change over time and linear, top-down requirements engineering methods cannot be applied without significant adaptations. New tools are needed that support the continuous and iterative specification and alignment of requirements across different levels of abstraction. [Principal Ideas] We propose to integrate the behavior-driven development (BDD) approach with an intuitive and executable scenario-based modeling of functional requirements. In this way, stakeholder expectations can be structured via features and documented in natural language as usage scenarios. Based on usage scenarios, the modeling of functional requirements can be driven by tests, allowing for the automated testing and analysis of requirements. This in turn supports the iterative specification of requirements and the alignment of stakeholder needs. [Contribution] In this paper we showcase the tool BeSoS that supports the iterative and behavior-driven specification of requirements in an SoS context. We propose a method and describe its tool components using an example. The tool is available here: https://vimeo.com/512739942

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

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

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

[4]  Johann Schumann,et al.  Generating statechart designs from scenarios , 2000, Proceedings of the 2000 International Conference on Software Engineering. ICSE 2000 the New Millennium.

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

[6]  Mark W. Maier.  Architecting Principles for Systems‐of‐Systems , 1996 .

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

[8]  Axel van Lamsweerde,et al.  Scenarios, goals, and state machines: a win-win partnership for model synthesis , 2006, SIGSOFT '06/FSE-14.

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

[10]  David Harel,et al.  Integrating Interobject Scenarios with Intraobject Statecharts for Developing Reactive Systems , 2021, IEEE Design & Test.

[11]  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).

[12]  J.S. Dahmann,et al.  Understanding the Current State of US Defense Systems of Systems and the Implications for Systems Engineering , 2008, 2008 2nd Annual IEEE Systems Conference.

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

[14]  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).

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

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