Regression testing is the common task of retesting software that has been changed or extended (e.g., by new features) during evolution. As whole program not feasible with reasonable time and cost, usually only a subset all test cases executed for regression testing, e.g., executing according to case prioritization. Although vast amount methods prioritization exist, they mostly require access source code (i.e., white-box). However, in industrial practice, system-level an important grants no...

In non-small cell lung cancer (NSCLC), approximately 1-3% of cases harbor an increased gene copy number (GCN) the MET gene. This alteration can be due to de novo amplification or represent a secondary resistance mechanism in response targeted therapies. To date, gold standard method evaluate GCN is fluorescence situ hybridization (FISH). However, next-generation sequencing (NGS) becoming more relevant optimize therapy by revealing mutational profile each NSCLC. Using evaluable n = 205 NSCLC...

Software Product Lines (SPLs) are a successful approach to software reuse in the large. Even though tools exist create SPLs, their evolution is widely unexplored. Evolving an SPL manually tedious and error-prone as it hard avoid unintended side-effects that may harm consistency of SPL. The main contribution this paper conceptual basis system for model-based which maintains models feature mapping. As further contribution, novel classification introduced distinguishes evolutions by potential...

The automotive industry aims for the highest possible driving range (highest energy density) in combination with a fast charge ability power of electric vehicles. With both targets being intrinsically contradictory, it is important to understand and optimize resistances within lithium-ion battery (LIB) electrodes. In this study, properties magnitude electronic resistance contributions LiMn0.7Fe0.3PO4 (LMFP)- LiNixCoyMnzO2 (NCM, x = 0.88~0.90, + y z 1)-based electrodes are comprehensively...

Software product lines (SPLs) and software ecosystems (SECOs) encompass a family of closely related systems in terms common variable assets that are configured to concrete products (variability space). Over the course time, SPLs especially SECOs subject change order meet new requirements as part evolution time). Even though both dimensions variability have be handled simultaneously, e.g., not all customers upgrade their respective immediately or completely, there currently is no approach can...

Software Product Lines (SPLs) are a mechanism for large-scale reuse where families of related software systems represented in terms commonalities and variabilities, e.g., using Feature Models (FMs). While FMs define all possible configurations the SPL, when considering dynamic SPLs not every configuration may be valid contexts. Unfortunately, common can capture this context dependence. In paper, we remedy problem by extending attributed with Validity Formulas (VFs) that constrain selection...

Software engineering faces the challenge of developing and maintaining systems that are highly variable in space (concurrent variations system at a single point time) time (sequential due to its evolution). Recent research aims address this need by managing variability simultaneously. However, such often relies on nonuniform terminologies varying understanding concepts, as it originates from different communities: software product-line configuration management. These issues complicate...

Software product lines (SPLs) and software ecosystems (SECOs) are approaches to capturing families of closely related systems in terms common variable functionality. SPLs especially SECOs subject evolution adapt new or changed requirements resulting different versions the family its assets. These may have be maintained used for products even after they were superseded by newer versions. Variability models describing valid combinations assets, such as feature models, capture variability space...

Software Product Lines (SPLs) are an approach for large-scale reuse software families by means of variabilities and commonalities. We consider three dimensions variability representing sources systems to behave differently: configuration as spatial variability, dependence on surroundings contextual evolution temporal variability. The strongly correlate: Contextual changes the set possible configurations in Temporal captures over course time. However, currently, there is no tool support...

Software Product Lines (SPLs) are an approach to capture families of closely related software systems in terms commonalities and variabilities where individual variants defined by configurations selected features. Specific (partial) may be particular importance SPL manufacturers, e.g., if they very popular or used major customers. SPLs subject evolution, which inadvertently break existing configurations, a previously feature does no longer exist. This is problematic as it delay completely...

To satisfy demand for customized products, companies commonly apply so-called clone-and-own strategies by copying functionality from existing products and modifying it to create product variants that have be developed, maintained, evolved in isolation. In previous work, we introduced a variability mining technique identify information (commonalities differences) block-based model (e.g., MATLAB/Simulink models), which can used guide manual transition managed reuse of software line (SPL). this...

Software product lines (SPLs) play a pivotal role for developing vast amount of related programs efficiently and with high quality. To this end, the SPL engineering process is separated into two levels: domain (DE), which captures variability development artifacts entire SPL, application (AE), encompasses variant-specific subset aforementioned artifacts. In industrial practice evolving an it common that evolution performed on both levels, may affect same (e.g., code, models) in different...

Testing is a fundamental task to ensure software quality. Regression testing aims that changes do not introduce new failures. As resources are often limited and comprises vast amount of test cases, different regression strategies have been proposed reduce effort by selecting or prioritizing important e.g., code coverage (to sufficient depth). However, in system testing, source available creating black-box system. In this paper, we an automated, multi-objective case selection technique...

Software Product Lines (SPLs) are a common technique to capture families of software products in terms commonalities and variabilities. On conceptual level, functionality an SPL is modeled features Feature Models (FMs). As other systems, SPLs their FMs subject evolution that may lead the introduction anomalies (e.g., non-selectable features). To fix such anomalies, developers need understand cause for them. However, large histories SPLs, explanations become very long and, as consequence,...

Block-based modeling languages, such as MATLAB/Simulink or state charts, reduce the complexity inherent to developing large-scale software systems. When creating variants for largely similar yet different systems, common practice is copy models and modify them requirements. While this allows companies save costs in short-term, these so-called clone-and-own approaches cause problems regarding long-term evolution system quality relation between of resulting family lost so that have be...

Scenario-based testing is considered state-of-the-art to verify and validate Advanced Driver Assistance Systems. However, two essential unsolved challenges prevent the practical application of scenario-based according SOTIF-standard: (1) how select a set representative test scenarios, (2) assess effectiveness scenario suite. In this paper, we leverage variability modelling techniques scenarios from space resulting suites with mutation score as metric. We capture in feature model generate...

A software ecosystem (SECO) encompasses a set of interdependent systems where individual products are created by combining common platform with variable extensions. Examples the SECOs surrounding Eclipse or Android. Due to independent release cycles multiple vendors for and extensions, evolving frequently. This makes it hard get concise impression structure SECO its artifacts during given period time. We contribute metamodel capture variability in an arbitrary evolution based on notion real...

In Model-Driven Software Development, models are automatically processed to support the creation, build, and execution of systems. A large variety dedicated model-transformation languages exists, promising efficiently realize automated processing models. To investigate actual benefit using such specialized languages, we performed a large-scale controlled experiment in which over 78 subjects solve 231 individual tasks three languages. The sheds light on commonalities differences between model...

Exploring an unfamiliar large-scale software system is challenging, especially when based solely on source code. While visualizations help in gaining overview of a system, they generally neglect architecture knowledge their representations, e.g., by arranging elements along package structures rather than functional components or locking users specific abstraction only slightly above the In this paper, we introduce automated approach for recovery and use its results immersive 3D virtual...

Technical architectures (TAs) represent the computing infrastructure of a company with all its hardware and software components. Over course time, number TAs grows companies' requirements usually large variety has to be maintained. Core challenge is missing information on relations between existing variants TAs, which complicates reuse solutions across systems. However, identifying these an expensive task as architects have manually analyze each TA individually. Restructuring poses severe...

A feature model (FM) describes commonalities and variability within a software product line (SPL) represents the configuration options at one point in time. temporal (TFM) additionally FM evolution, e.g., change history or planning of future releases. The increasing number different TFM notations hampers research collaborations due to lack interoperability regarding notations, editors, analyses. We present common API for TFMs, which provides core ecosystem, harmonize notations. identified...