VAMOS

For years, the software reuse community (including the variability community) has used cost reduction as the main argument for software reuse. Software reuse methods are often contrasted with cloning[9]. We commonly hear that already when a piece of ...

One of the basic principles in product lines is to delay design decisions related to offered functionality and quality to later phases of the life cycle [25]. Instead of deciding on what system to develop in advance, a set of assets and a common ...

Configurable systems are widely used for families of products that share multiple configuration options. These systems often induce a large configuration space. Handling the variability of such a system is difficult without being able to measure its ...

Configurable systems allow users to derive customized software variants with behavior and functionalities tailored to individual needs. Developers of these configurable systems need to ensure that each configured software variant works as intended. Thus,...

Modern software systems often provide configuration options for customizing of the system's functional and non-functional properties, such as response time and energy consumption. The valid configurations of a software system are commonly documented in ...

Handling configurable systems with thousands of configuration options is a challenging problem in research and industry. One of the most common approaches to manage the configuration options of large systems is variability modelling. The verification ...

Nowadays, the requirements for software and therefore also the required complexity is increasing steadily. Consequently, various techniques to handle the growing demand for software variants in one specific domain are used. These techniques often rely ...

Context: Software metrics, as one form of static analyses, is a commonly used approach in software engineering in order to understand the state of a software system, in particular to identify potential areas prone to defects. Family-based techniques ...

Software branching and merging allows collaborative development and creating software variants, commonly referred to as clone & own. While simple and cheap, a trade-off is the need to merge code and to resolve merge conflicts, which frequently occur in ...

A software system's security is constantly threatened by vulnerabilities that result from faults in the system's design (e.g., unintended feature interactions) and which can be exploited with attacks. While various databases summarize information on ...

We present a framework for quantitative security modeling and analysis of highly customizable attack scenarios, which resulted as a spin-off from our research in software product line engineering. The graphical security models are based on attributed ...

In this short paper, we report on the motivation, background and ambition of the ITEA3 project XIVT - e<u>x</u>cellence <u>i</u>n <u>v</u>ariant <u>t</u>esting. We describe a work flow and tool chain for testing of configurable and highly-variant ...

The project EXtracting Product Lines from vAriaNTs (EXPLANT) funded by the German Research Foundation (DFG) is currently in its second phase. In this project, we are concerned with the stepwise migration of cloned variants into a software product line (...

The manufacturing domain faces new challenges due to market changes. One of these changes affects consumer behavior, i.e. customers demand individualized products in small batches. Varying production requests require different configurations of ...

Dynamically Adaptive Systems (DAS) modify their behaviours in response to (sometimes unpredictable) changes in their environment or to the evolution of their own abilities (sensors and actuators). To support adaptation, a reference architecture (such as ...

Configurable systems offer advantages compared to single systems since developers should maintain a unique platform to address a diversity of deployment contexts and usages. To ensure that all configurations correctly execute, developers spend ...

Program slicing is an important technique for various follow-up activities like program understanding or feature identification. So far only little work exists on program slicing of product lines. A key challenge in this context is to identify a slice ...

In Cyber-Physical Production System (CPPS) engineering, Assembly Sequence (AS) models of products are primary engineering artifacts. Product variants are often designed as Product-Process-Resource (PPR) AS models that are initiated with clone-and-own ...

Clone-and-own prevails as an ad-hoc reuse strategy that addresses changing requirements by copying and modifying existing system variants. Proper documentation is typically not cherished and knowledge about common and varying parts between individual ...

In Software Product Line (SPL) engineering, mapping domain features to existing code assets is essential for variability management. When variability is already implemented through Object-Oriented (OO) techniques, it is too costly and error-prone to ...

Many software systems need to exist in multiple variants. Organizations typically develop variants using clone&own---copying and adapting systems towards new requirements. However, while clone & own is a simple and readily available strategy, it does ...

Software product line engineering (SPLE) aims at increasing productivity by relying on the principles of organized reuse and variability. In annotative approaches to SPLE the realization artifacts carry presence conditions, we refer to as annotations ...

The increasing complexity of software variants demands for variation management techniques suitable for industrial practice. As "clone-and-own" with subsequent manual evolution still is a popular method to create software variants, this leads to product ...

Annotation-based and composition-based variability mechanisms have complementary strengths regarding software maintenance and evolution. Consequently, several proposals have been made to combine, integrate, and substitute both mechanisms. An open ...

Model-based software product lines (MBSPLs) are implemented using various variability mechanisms. These are commonly categorized whether they separate features virtually (e.g., using annotations) or physically (e.g., using modules). Each of these ...