Flexible feature binding in software product lines

Abstract

A software product line (SPL) is a family of programs that share assets from a common code base. The programs of an SPL can be distinguished in terms of features, which represent units of program functionality that satisfy stakeholders' requirements. The features of an SPL can be bound either statically at program compile time or dynamically at run time. Both binding times are used in SPL development and have different advantages. For example, dynamic binding provides high flexibility whereas static binding supports finegrained customizability without any impact on performance (e.g., for use on embedded systems). However, contemporary techniques for implementing SPLs force a programmer to choose the binding time already when designing an SPL and to mix different implementation techniques when multiple binding times are needed. We present an approach that integrates static and dynamic feature binding seamlessly. It allows a programmer to implement an SPL once and to decide per feature at deployment time whether it should be bound statically or dynamically. Dynamic binding usually introduces an overhead regarding resource consumption and performance. We reduce this overhead by statically merging features that are used together into dynamic binding units. A program can be configured at run time by composing binding units on demand. We use feature models to ensure that only valid feature combinations can be selected at compile and at run time. We provide a compiler and evaluate our approach on the basis of two non-trivial SPLs.

Towards flexible and reusable saas for multi-tenancy to design, implement and bind multi-functional variability for Rich-Variant services

“…In fact, module system allows developers to decompose a large system into manageable subsystems (modules), which can be developed and checked in isolation [25]. proposal based on feature-oriented programming [2].…”

“…In the literature, some works have been performed to facilitate the customization of SaaS applications tailored to the ten ant specific needs by combining the benefits of Software Product Line Engineering (SPLE) [1] [2] with those of variability management and multi-tenancy [3][4] [5]. We aim to create a flexible and reusable environment enabling greater flexibility and suppleness for customers, while leveraging the economies of scale.…”

Using document-oriented GUIs in dynamic software product lines

“…By combining static and dynamic feature binding, we can apply an approach used in FOP, whereby features are joined to create composite features, also known as dynamic binding units Figure 5. Composition of Home screen [34]. Using dynamic binding units can be seen to follow a staged configuration [15], whereby product derivation is not carried out within a single step, but more over a number of steps, each specialising the product more.…”

“…If these specific method calls are found within any class or class refinement, we can simply alter the parameter to instead get the variant from the management class, as shown in Figure 6. These refinements can then be developed using existing adaptation approaches for example dynamic binding FOP langauges like FeatureC++ [33] and rbFeatures [21], Context Oriented Programming (COP) languages [40], or SOA approaches [29]. …”

“…A feature of an SPL has been defined as "a prominent or distinctive user-visible aspect, quality, or characteristic of a software system or systems" [23]. Features can be implemented in feature modules, incrementing software functionality [33], by extending the base functionality of a program with additional logic.…”