Tackling combinatorial explosion: a study of industrial needs and practices for analyzing highly configurable systems

Mukelabai, Mukelabai; Nešić, Damir; Maro, Salome; Berger, Thorsten; Steghöfer, Jan-Philipp

doi:10.1145/3238147.3238201

Cited by 41 publications

(26 citation statements)

References 58 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Of course, the project partners are also very active in the scientific community. With more than 50 publications, the project has had a significant impact on the state of the art, with notable publications at ASE [20] , Isola [21] , MODELS [22] as well as in IST [22], [23] , TSE [24] and many others. Members of the project have also organised the main scientific event of the product line engineering community, SPLC in Gothenburg in 2018, with well over 100 participants and workshops and tutorials geared directly towards the topics of the projects.…”

Section: Discussionmentioning

confidence: 99%

REVaMP2 Project: Towards Round-Trip Engineering of Software Product Lines - Approach, Intermediate Results and Challenges

Sadovykh

Ziadi

Bagnato

et al. 2019

Software Technology: Methods and Tools

Self Cite

View full text Add to dashboard Cite

The REVaMP 2 Project is a major European effort towards Round-Trip Engineering of Software Product Lines for software intensive systems. Indeed, software is predominant in almost every modern industry. The importance of time-to-market has grown tremendously in many business domains. Organizations are in a constant search for approaches for mass production of highly customizable systems. The software product lines engineering approach promises to provide up to 10x speed increase benefits in time-to-market. Traditionally, automated tools proposed a top-down approach, i.e., variants were generated from a model of the product line. However, the industry used a bottom-up approach that helped to recreate a product line out of various clones of a system. This operation is very costly and error prone. The goal of REVaMP 2 is to automate the process of extracting a product line from various system artifacts and help with verification and the co-evolution of the product line. The project involves 27 partners that contribute with diverse research and industrial practices to address case study challenges stemming from 11 application domains. In this paper, we would like to present the motivation for the project, the current approach, the intermediate results and challenges.

show abstract

Section: Discussionmentioning

confidence: 99%

REVaMP2 Project: Towards Round-Trip Engineering of Software Product Lines - Approach, Intermediate Results and Challenges

Sadovykh

Ziadi

Bagnato

et al. 2019

Software Technology: Methods and Tools

Self Cite

View full text Add to dashboard Cite

show abstract

“…In practice, however, many feature combinations are not relevant. Developers are not always aware of which combinations are relevant, though, and sampling strategies are often unsystematic [19]. For continuous compliance, safety cases must at least cover those variants that are used in production and must show systematically that these variants are safe.…”

Section: Continuous Compliancementioning

confidence: 99%

Challenges of Scaled Agile for Safety-Critical Systems

Steghöfer

Knauss

Horkoff

et al. 2019

Lecture Notes in Computer Science

Self Cite

View full text Add to dashboard Cite

Automotive companies increasingly adopt scaled agile methods to allow them to deal with their organisational and product complexity. Suitable methods are needed to ensure safety when developing automotive systems. On a small scale, R-Scrum and SafeScrum ® are two concrete suggestions for how to develop safety-critical systems using agile methods. However, for large-scale environments, existing frameworks like SAFe or LeSS do not support the development of safety-critical systems out of the box. We, therefore, aim to understand which challenges exist when developing safety-critical systems within large-scale agile industrial settings, in particular in the automotive domain. Based on an analysis of R-Scrum and SafeScrum ® , we conducted a focus group with three experts from industry to collect challenges in their daily work. We found challenges in the areas of living traceability, continuous compliance, and organisational flexibility. Among others, organisations struggle with defining a suitable traceability strategy, performing incremental safety analysis, and with integrating safety practices into their scaled way of working. Our results indicate a need to provide practical approaches to integrate safety work into large-scale agile development and point towards possible solutions, e.g., modular safety cases.

show abstract

“…The language can be used in automated analysis processes where the model is used as input and an analysis result is obtained. This can comprise analyses confined to the feature model [6,29] or those that take other artifacts into account [42,54].…”

Section: Analysesmentioning

confidence: 99%

“…The commercial productline engineering tools pure::variants [17] and Gears [38], as well as the open-source tool FeatureIDE [55], are built upon feature models. In addition, many different feature-model analysis techniques and tools have been proposed [6,42,57]. Recent work also addressed the relative absence of processes for feature modeling by proposing modeling principles for engineers creating feature models [44].…”

Section: Introductionmentioning

confidence: 99%

Usage Scenarios for a Common Feature Modeling Language

Berger

Collet

2019

Proceedings of the 23rd International Systems and Software Product Line Conference - Volume B

Self Cite

View full text Add to dashboard Cite

Feature models are recognized as a de facto standard for variability modeling. Presented almost three decades ago, dozens of different variations and extensions to the original feature-modeling notation have been proposed, together with hundreds of variability management techniques building upon feature models. Unfortunately, despite several attempts to establish a unified language, there is still no emerging consensus on a feature-modeling language that is both intuitive and simple, but also expressive enough to cover a range of important usage scenarios. There is not even a documented and commonly agreed set of such scenarios.Following an initiative among product-line engineering researchers in September 2018, we present 14 usage scenarios together with examples and requirements detailing each scenario. The scenario descriptions are the result of a systematic process, where members of the initiative authored original descriptions, which received feedback via a survey, and which we then refined and extended based on the survey results, reviewers' comments, and our own expertise. We also report the relevance of supporting each usage scenario for the language, as perceived by the initiative's members, prioritizing each scenario. We present a roadmap to build and implement a first version of the envisaged common language. CCS CONCEPTS• Software and its engineering → Software product lines.

show abstract

Tackling combinatorial explosion: a study of industrial needs and practices for analyzing highly configurable systems

Cited by 41 publications

References 58 publications

REVaMP2 Project: Towards Round-Trip Engineering of Software Product Lines - Approach, Intermediate Results and Challenges

REVaMP2 Project: Towards Round-Trip Engineering of Software Product Lines - Approach, Intermediate Results and Challenges

Challenges of Scaled Agile for Safety-Critical Systems

Usage Scenarios for a Common Feature Modeling Language

Contact Info

Product

Resources

About