Joel Greenyer's research while affiliated with Fachhoschule für die Wirtschaft Hannover-FHDW and other places

... 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]. ...

... • C 2: We implemented the process. Therefore, we integrated the project management tool Jira 2 , with the requirements specification and modeling tool BeSoS [9]. In this way, we can manage and specify requirements using scenario descriptions in natural language to support the stakeholder view. ...

... The importance of Requirements Engineering (RE) in software development has been mentioned in many works of literature including in Gregory, [8], Hidellaarachchi et al., [10], Liu et al., [13] Wiecher et al., [26]. In general, the generic RE activities are requirements elicitation, analysis and modelling, negotiation, validation, documentation, and management. ...

... 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]. ...

... These last can be divided into global methods that describe the average behavior of the model, and local methods that explain individual predictions [24]. The scientific interest in explainability in software engineering is growing [1,3,5,28], for example, in the context of explainable analytical models for predictions and decision-making [28], explainable counterexamples [16], and explainable quality attribute trade-offs in software architecture selection [5,27]. Recent approaches in the area of self-adaptive systems deal with opaque requirements change [18], self-description of components [20], the decisions taken in adaptation space reduction [10], and generation of explanation strategies for human-on-the-loop systems using probabilistic model checking [23]. ...

... These usage scenarios are used to generated acceptance tests. Subsequently, we use these acceptance tests to drive the requirements modeling, following the test-driven scenario specification approach (TDSS) [10]. ...

... For instance, a semi-automatic algorithm that covers all source code will provide a similar set of configurations that a coverage algorithm provides. Alternatively, a greedy automated algorithm that aims at selecting an optimal number of configurations that test all pairs of features individually, provides a similar set of configurations that a 2-wise algorithm provides [60]. In the next section, we focus on t-wise strategies since we are interested in investigating sampling strategies that assure product sampling quality. ...

... An automated methodology to exploit braking energy recuperation though scheduling and slowing down trajectories was proposed in [12]. The proposed methodology accomplishes this in two levels. ...

... Thus, formal verification techniques can usually be applied, in order to ensure that a SBM satisfies multiple criteria of choice, either as an independent standalone model, or as a single component within a larger system. When executing scenario-based models in distributed architectures [35][36][37][38][39], these model can automatically be repaired by the use of automated analysis techniques [26,40,41]. These techniques are able to update the SBMs in various strategies, i.e., as part of the Wise Computing initiative [42][43][44][45]. ...

... Programmable Logic Controllers (PLCs) Code Generation was presented in [163] using Scenario Modeling Language (SML). In the same manner, implementation of PLC code generation was presented in [113] using Compositional Interchange Format (CIF). ...