Software diversity: state of the art and perspectives

Schaefer, Ina; Rabiser, Rick; Clarke, Dave; Bettini, Lorenzo; Benavides, David; Botterweck, Goetz; Pathak, Animesh; Trujillo, Salvador; Villela, Karina

doi:10.1007/s10009-012-0253-y

Cited by 136 publications

(80 citation statements)

References 207 publications

(248 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Feature modeling is currently the most widely used approach for modeling variability [12,9]. A feature model is typically designed to capture stakeholder-visible characteristics and aspects of a system, such as functional and non-functional features of individual products.…”

Section: Background: Software Product Lines and Variability Modelsmentioning

confidence: 99%

Supporting distributed product configuration by integrating heterogeneous variability modeling approaches

Galindo

Dhungana

Rabiser

et al. 2015

Information and Software Technology

Self Cite

View full text Add to dashboard Cite

Context: In industrial settings products are developed by more than one organization. Software vendors and suppliers commonly typically maintain their own product lines, which contribute to a larger (multi) product line or software ecosystem. It is unrealistic to assume that the participating organizations will agree on using a specific variability modeling technique-they will rather use different approaches and tools to manage the variability of their systems. Objective: We aim to support product configuration in software ecosystems based on several variability models with different semantics that have been created using different notations. Method: We present an integrative approach that provides a unified perspective to users configuring products in multi product line environments, regardless of the different modeling methods and tools used internally. We also present a technical infrastructure and a prototype implementation based on web services. Results: We show the feasibility of the approach and its implementation by using it with the three most widespread types of variability modeling approaches in the product line community, i.e., feature-based, OVM-style, and decision-oriented modeling. To demonstrate the feasibility and flexibility of our approach, we present an example derived from industrial experience in enterprise resource planning. We further applied the approach to support the configuration of privacy settings in the Android ecosystem based on multiple variability models. We also evaluated the performance of different model enactment strategies used in our approach. Conclusions: Tools and techniques allowing stakeholders to handle variability in a uniform manner can considerably foster the initiation and growth of software ecosystems from the perspective of software reuse and configuration.

show abstract

Section: Background: Software Product Lines and Variability Modelsmentioning

confidence: 99%

Supporting distributed product configuration by integrating heterogeneous variability modeling approaches

Galindo

Dhungana

Rabiser

et al. 2015

Information and Software Technology

Self Cite

View full text Add to dashboard Cite

show abstract

“…The integration of variability concepts into architectural specifications is essential in order to successfully develop SPLs [6], [3]. Most mechanisms for describing architectural variability specify what we have called external variation of the architecture.…”

Section: A Variability In Software Architecturementioning

confidence: 99%

“…In fact, variability is one of the most important drivers of these kinds of architectures that support a set of members of a product-line. However, the modeling of the architectural variability has become a challenge for SPLE [3].…”

Section: Introductionmentioning

confidence: 99%

Model-to-Code Transformation from Product-Line Architecture Models to AspectJ

Díaz

Pérez

Fernández-Sánchez

et al. 2013

2013 39th Euromicro Conference on Software Engineering and Advanced Applications

View full text Add to dashboard Cite

Abstract-Software Product Line Engineering has significant advantages in family-based software development. The common and variable structure for all products of a family is defined through a Product-Line Architecture (PLA) that consists of a common set of reusable components and connectors which can be configured to build the different products. The design of PLA requires solutions for capturing such configuration (variability). The Flexible-PLA Model is a solution that supports the specification of external variability of the PLA configuration, as well as internal variability of components. However, a complete support for product-line development requires translating architecture specifications into code. This complex task needs automation to avoid human error. Since Model-Driven Development allows automatic code generation from models, this paper presents a solution to automatically generate AspectJ code from Flexible-PLA modelspreviously configured to derive specific products. This solution is supported by a modeling framework and validated in a software factory.

show abstract

“…Modern software systems come in many variants in order to satisfy multiple varying user requirements [24]. Such variant-rich, configurable systems are developed and managed by techniques from the field known as software product line engineering (SPLE) [23].…”

Section: Introductionmentioning

confidence: 99%

From Featured Transition Systems to Modal Transition Systems with Variability Constraints

Beek

Damiani

Gnesi

et al. 2015

Software Engineering and Formal Methods

View full text Add to dashboard Cite

Abstract. We present an automatic technique to transform a subclass of featured transition systems into modal transition systems with additional sets of variability constraints in the specific format accepted by the variability model checker VMC. Both formal models are widely used in the field of software product line engineering and both come with a dedicated model checker. The transformation serves two purposes. First, it contributes to a better understanding of the fundamental differences between the two approaches, basically concerning the way in which variability constraints are represented (in terms of features and actions, respectively). Second, it paves the way to compare the modelling and analysis of product line behaviour in two different settings.

show abstract

Software diversity: state of the art and perspectives

Cited by 136 publications

References 207 publications

Supporting distributed product configuration by integrating heterogeneous variability modeling approaches

Supporting distributed product configuration by integrating heterogeneous variability modeling approaches

Model-to-Code Transformation from Product-Line Architecture Models to AspectJ

From Featured Transition Systems to Modal Transition Systems with Variability Constraints

Contact Info

Product

Resources

About