Abstract Context: Variant-Rich Systems (VRSs), such as Software Product Lines or variants
created through clone & own, aim at reusing existing assets. The long lifespan of families of …

Robots artificially replicate human capabilities thanks to their software, the main
embodiment of intelligence. However, engineering robotics software has become …

Tracing requirements to their implementation is crucial to all stakeholders of a software
development process. When managing software variability, requirements are typically …

Locating features is one of the most common software development activities. It is typically
done during maintenance and evolution, when developers need to identify the exact places …

Software often needs to exist in different variants, which account for varying customer
requirements, environments, or non-functional aspects, such as energy consumption …

A software product line allows to derive individual software products based on a
configuration. As the number of configurations is an indicator for the general complexity of a …

Code is often reused to facilitate collaborative development, to create software variants, to
experiment with new ideas, or to develop new features in isolation. Social-coding platforms …

For highly configurable software systems, such as the Linux kernel, maintaining and
evolving variability information along changes to source code poses a major challenge …

In clone-and-own-the predominant paradigm for developing multi-variant software systems
in practice-a new variant of a software system is created by copying and adapting an …

In clone-and-own development, new variants of a software system are typically created by
manually copying and adapting an existing variant. This approach is flexible but suffers from …