Principles of feature modeling

Nešić, Damir; Krüger, Jacob; Stănciulescu, Ștefan; Berger, Thorsten

doi:10.1145/3338906.3338974

Cited by 55 publications

(29 citation statements)

References 69 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In this section, we answer a challenge about variability modeling for a microservice-based product line. We follow one of the feature modeling principles in [16]: "rely on domain knowledge and existing artifacts to construct the feature model." The model, represented in the feature diagram, is defined based Fig.…”

Section: Variability Modelingmentioning

confidence: 99%

See 1 more Smart Citation

Variability management

Setyautami

Fadhlillah

Adianto

et al. 2020

Proceedings of the 24th ACM Conference on Systems and Software Product Line: Volume a - Volume A

View full text Add to dashboard Cite

Combining microservices and software product line engineering (SPLE) is a challenge in variability management. This paper proposes a solution to that challenge by re-engineering existing webshop systems into a product line application. We first perform feature identification to analyze the features of subject systems. We introduce a mechanism that models the variability and designs a software product line architecture based on existing features. We use a UML diagram with the UML-DOP profile to abstract microservice variability in SPLE. Then, a transformation into a product line application is conducted to generate running applications based on selected features. We utilize a preliminary framework of microservice variability based on delta-oriented programming.

show abstract

Section: Variability Modelingmentioning

confidence: 99%

“…The first level captures variants of features in the problem space, and the other levels represent endpoints variations that are related to solution space. As suggested in the principles of feature modeling [16], we define the specific purpose for each feature model. Fig.…”

Section: Variability Modelingmentioning

confidence: 99%

Variability management

Setyautami

Fadhlillah

Adianto

et al. 2020

Proceedings of the 24th ACM Conference on Systems and Software Product Line: Volume a - Volume A

View full text Add to dashboard Cite

show abstract

“…• Perhaps dedicated support for interface feature models (cf. principle MO 3 among common feature modeling principles [44]) Open questions:…”

Section: Requirementsmentioning

confidence: 99%

“…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

“…To overcome these limitations, we propose an approach that focuses on the acquisition of all existing information about vulnerabilities in a model that is able to capture this variability. In software product line engineering, feature models have become established to manage the variability of software systems, wherein features are used to describe certain user-visible aspects, quality or characteristics [3,10,25,42]. We propose a vulnerability feature model that provides a homogeneous view of all vulnerabilities in a software system, considering the interactions with its environment.…”

Section: Introductionmentioning

confidence: 99%

Model-Based Evaluation of Vulnerabilities in Software Systems

Kenner

2020

Proceedings of the 24th ACM International Systems and Software Product Line Conference - Volume B

View full text Add to dashboard Cite

Vulnerabilities in software systems result from faults, which occur at different stages in a software's life cycle, for example, in the design (i.e., undesired feature-interactions), the development (i.e., buffer overflows), or the operation (i.e., configuration errors). Various databases provide detailed information about vulnerabilities in software systems or the way to exploit it, but face severe limitations. The information is scattered across these databases, fluctuates in quality and granularity, and provides only an insight into a single vulnerability per entry. Even for a single software system it is challenging for any security-related stakeholder to determine the threat level, which consists of all vulnerabilities of the software system and its environment (i.e., operating system). Manual vulnerability management is feasible only to a limited extend if we want to identify all configurations that are affected by vulnerabilities, or determine a system's threat level and the resulting risk we have to deal with. For variant-rich systems, we also have to deal with variability, allowing different stakeholders to understand the threats to their particular setup. To deal with this variability, we propose vulnerability feature models, which offer a homogeneous view on all vulnerabilities of a software system. These models and the resulting analyses offer advantages in many disciplines of the vulnerability management process. In this paper, we report the research plan for our project, in which we focus on the model-based evaluation of vulnerabilities. This includes research objectives that take into account the design of vulnerability feature models, their application in the process of vulnerability management, and the impact of evolution, discovery, and verification of vulnerabilities. CCS CONCEPTS • Security and privacy → Vulnerability management; • Software and its engineering → Software product lines.

show abstract

Principles of feature modeling

Cited by 55 publications

References 69 publications

Variability management

Variability management

Usage Scenarios for a Common Feature Modeling Language

Model-Based Evaluation of Vulnerabilities in Software Systems

Contact Info

Product

Resources

About