Mapping the design-space of textual variability modeling languages: a refined analysis

Eichelberger, Holger; Schmid, Klaus

doi:10.1007/s10009-014-0362-x

Cited by 31 publications

(18 citation statements)

References 54 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Eichelberger and Schmid report a certain trend in product line engineering towards textual variability modeling languages [9]. The survey and analysis of textual variability languages presented in their work characterizes eleven textual languages, including their own proposal the INDENICA Variability Modeling Language (IVML).…”

Section: Related Workmentioning

confidence: 99%

The High-Level Variability Language

Villota

Mazo

Salinesi

2019

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

View full text Add to dashboard Cite

Given its relevance, there is an extensive body of research for modeling variability in diverse domains. Regretfully, the community still faces issues and challenges to port or share variability models among tools and methodological approaches. There are researchers, for instance, implementing the same algorithms and analyses again because they use a specific modeling language and cannot use some existing tool. This paper introduces the High-Level Variability Language (HLVL), an expressive and extensible textual language that can be used as a modeling and an intermediate language for variability. HLVL was designed following an ontological approach, i.e., by defining their elements considering the meaning of the concepts existing on different variability languages. Our proposal not only provides a unified language based on a comprehensive analysis of the existing ones but also sets foundations to build tools that support different notations and their combination. CCS CONCEPTS• Software and its engineering → Domain specific languages; Software product lines.

show abstract

Section: Related Workmentioning

confidence: 99%

The High-Level Variability Language

Villota

Mazo

Salinesi

2019

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

View full text Add to dashboard Cite

show abstract

“…Numerous dialects of graphical FM notations have been proposed [2,17] and even textual FM languages have emerged (cf., [8]) -some of these also introduce new concepts. The full semantics of the concepts or notations has also been provided, although often as an afterthought [17].…”

Section: I3: Separate Domain Phenomena Concepts and Representationsmentioning

confidence: 99%

“…An example from KBC is described in [20] where a model is kept in internal data structures and it can be edited in textual representation, as called for also in SVM (cf. [8]), and via a graphical editor.…”

Section: I3: Separate Domain Phenomena Concepts and Representationsmentioning

confidence: 99%

Carrying Ideas from Knowledge-Based Configuration to Software Product Lines

Tiihonen

Raatikainen

Myllärniemi

et al. 2016

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Abstract. Software variability modelling (SVM) has become a central concern in software product lines -especially configurable software product lines (CSPL) require rigorous SVM. Dynamic SPLs, service oriented SPLs, and autonomous or pervasive systems are examples where CSPLs are applied. Knowledge-based configuration (KBC) is an established way to address variability modelling aiming for the automatic product configuration of physical products. Our aim was to study what major ideas from KBC can be applied to SVM, particularly in the context of CSPLs. Our main contribution is the identification of major ideas from KBC that could be applied to SVM. First, we call for the separation of types and instances. Second, conceptual clarity of modelling concepts, e.g., having both taxonomical and compositional relations would be useful. Third, we argue for the importance of a conceptual basis that provides a foundation for multiple representations, e.g., graphical and textual. Applying the insights and experiences embedded in these ideas may help in the development of modelling support for software product lines, particularly in terms of conceptual clarity and as a basis for tool support with a high level of automation.

show abstract

“…Examples are cardinality-based feature models [23], which support the multiple instantiation of features; attributed (a.k.a., extended) feature models [6], which allow features to have non-Boolean attributes (carrying, for instance, non-functional properties); more expressive (i.e., non-Boolean) constraint languages [46]; or even more radical approaches that combine feature and class modeling in one language [5]. Furthermore, while most academic featuremodeling notations are visual, many languages exhibiting a textual syntax have been developed for feature modeling [13,14,20,27,28].…”

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

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

Mapping the design-space of textual variability modeling languages: a refined analysis

Cited by 31 publications

References 54 publications

The High-Level Variability Language

The High-Level Variability Language

Carrying Ideas from Knowledge-Based Configuration to Software Product Lines

Usage Scenarios for a Common Feature Modeling Language

Contact Info

Product

Resources

About