The Experts below are selected from a list of 150 Experts worldwide ranked by ideXlab platform
Yves Le Traon - One of the best experts on this subject based on the ideXlab platform.
-
combining multi objective search and constraint solving for configuring Large Software Product lines
International Conference on Software Engineering, 2015Co-Authors: Christopher Henard, Mike Papadakis, Mark Harman, Yves Le TraonAbstract:Software Product Line (SPL) feature selection involves the optimization of multiple objectives in a Large and highly constrained search space. We introduce SATIBEA, that augments multi-objective search-based optimization with constraint solving to address this problem, evaluating it on five Large real-world SPLs, ranging from 1,244 to 6,888 features with respect to three different solution quality indicators and two diversity metrics. The results indicate that SATIBEA statistically significantly outperforms the current state-of-the-art (p
-
ICSE (1) - Combining multi-objective search and constraint solving for configuring Large Software Product lines
2015Co-Authors: Christopher Henard, Mike Papadakis, Mark Harman, Yves Le TraonAbstract:Software Product Line (SPL) feature selection involves the optimization of multiple objectives in a Large and highly constrained search space. We introduce SATIBEA, that augments multi-objective search-based optimization with constraint solving to address this problem, evaluating it on five Large real-world SPLs, ranging from 1,244 to 6,888 features with respect to three different solution quality indicators and two diversity metrics. The results indicate that SATIBEA statistically significantly outperforms the current state-of-the-art (p
-
bypassing the combinatorial explosion using similarity to generate and prioritize t wise test configurations for Software Product lines
IEEE Transactions on Software Engineering, 2014Co-Authors: Christopher Henard, Mike Papadakis, Gilles Perrouin, Jacques Klein, Patrick Heymans, Yves Le TraonAbstract:Large Software Product Lines (SPLs) are common in industry, thus introducing the need of practical solutions to test them. To this end, $t$-wise can help to drastically reduce the number of Product configurations to test. Current $t$-wise approaches for SPLs are restricted to small values of $t$. In addition, these techniques fail at providing means to finely control the configuration process. In view of this, means for automatically generating and prioritizing Product configurations for Large SPLs are required. This paper proposes (a) a search-based approach capable of generating Product configurations for Large SPLs, forming a scalable and flexible alternative to current techniques and (b) prioritization algorithms for any set of Product configurations. Both these techniques employ a similarity heuristic. The ability of the proposed techniques is assessed in an empirical study through a comparison with state of the art tools. The comparison focuses on both the Product configuration generation and the prioritization aspects. The results demonstrate that existing $t$-wise tools and prioritization techniques fail to handle Large SPLs. On the contrary, the proposed techniques are both effective and scalable. Additionally, the experiments show that the similarity heuristic can be used as a viable alternative to $t$ -wise.
Tomi Mannisto - One of the best experts on this subject based on the ideXlab platform.
-
transitioning towards continuous experimentation in a Large Software Product and service development organisation a case study
Product Focused Software Process Improvement, 2016Co-Authors: Sezin Gizem Yaman, Fabian Fagerholm, Myriam Munezero, Jurgen Munch, Mika Aaltola, Christina Palmu, Tomi MannistoAbstract:Context: Companies need capabilities to evaluate the customer value of Software-intensive Products and services. One way of systematically acquiring data on customer value is running continuous experiments as part of the overall development process. Objective: This paper investigates the first steps of transitioning towards continuous experimentation in a Large company, including the challenges faced. Method: We conduct a single-case study using participant observation, interviews, and qualitative analysis of the collected data. Results: Results show that continuous experimentation was well received by the practitioners and practising experimentation helped them to enhance understanding of their Product value and user needs. Although the complexities of a Large multi-stakeholder business-to-business (B2B) environment presented several challenges such as inaccessible users, it was possible to address impediments and integrate an experiment in an ongoing development project. Conclusion: Developing the capability for continuous experimentation in Large organisations is a learning process which can be supported by a systematic introduction approach with the guidance of experts. We gained experience by introducing the approach on a small scale in a Large organisation, and one of the major steps for future work is to understand how this can be scaled up to the whole development organisation.
-
PROFES - Transitioning Towards Continuous Experimentation in a Large Software Product and Service Development Organisation – A Case Study
Product-Focused Software Process Improvement, 2016Co-Authors: Sezin Gizem Yaman, Fabian Fagerholm, Myriam Munezero, Jurgen Munch, Mika Aaltola, Christina Palmu, Tomi MannistoAbstract:Context: Companies need capabilities to evaluate the customer value of Software-intensive Products and services. One way of systematically acquiring data on customer value is running continuous experiments as part of the overall development process. Objective: This paper investigates the first steps of transitioning towards continuous experimentation in a Large company, including the challenges faced. Method: We conduct a single-case study using participant observation, interviews, and qualitative analysis of the collected data. Results: Results show that continuous experimentation was well received by the practitioners and practising experimentation helped them to enhance understanding of their Product value and user needs. Although the complexities of a Large multi-stakeholder business-to-business (B2B) environment presented several challenges such as inaccessible users, it was possible to address impediments and integrate an experiment in an ongoing development project. Conclusion: Developing the capability for continuous experimentation in Large organisations is a learning process which can be supported by a systematic introduction approach with the guidance of experts. We gained experience by introducing the approach on a small scale in a Large organisation, and one of the major steps for future work is to understand how this can be scaled up to the whole development organisation.
Christopher Henard - One of the best experts on this subject based on the ideXlab platform.
-
combining multi objective search and constraint solving for configuring Large Software Product lines
International Conference on Software Engineering, 2015Co-Authors: Christopher Henard, Mike Papadakis, Mark Harman, Yves Le TraonAbstract:Software Product Line (SPL) feature selection involves the optimization of multiple objectives in a Large and highly constrained search space. We introduce SATIBEA, that augments multi-objective search-based optimization with constraint solving to address this problem, evaluating it on five Large real-world SPLs, ranging from 1,244 to 6,888 features with respect to three different solution quality indicators and two diversity metrics. The results indicate that SATIBEA statistically significantly outperforms the current state-of-the-art (p
-
ICSE (1) - Combining multi-objective search and constraint solving for configuring Large Software Product lines
2015Co-Authors: Christopher Henard, Mike Papadakis, Mark Harman, Yves Le TraonAbstract:Software Product Line (SPL) feature selection involves the optimization of multiple objectives in a Large and highly constrained search space. We introduce SATIBEA, that augments multi-objective search-based optimization with constraint solving to address this problem, evaluating it on five Large real-world SPLs, ranging from 1,244 to 6,888 features with respect to three different solution quality indicators and two diversity metrics. The results indicate that SATIBEA statistically significantly outperforms the current state-of-the-art (p
-
bypassing the combinatorial explosion using similarity to generate and prioritize t wise test configurations for Software Product lines
IEEE Transactions on Software Engineering, 2014Co-Authors: Christopher Henard, Mike Papadakis, Gilles Perrouin, Jacques Klein, Patrick Heymans, Yves Le TraonAbstract:Large Software Product Lines (SPLs) are common in industry, thus introducing the need of practical solutions to test them. To this end, $t$-wise can help to drastically reduce the number of Product configurations to test. Current $t$-wise approaches for SPLs are restricted to small values of $t$. In addition, these techniques fail at providing means to finely control the configuration process. In view of this, means for automatically generating and prioritizing Product configurations for Large SPLs are required. This paper proposes (a) a search-based approach capable of generating Product configurations for Large SPLs, forming a scalable and flexible alternative to current techniques and (b) prioritization algorithms for any set of Product configurations. Both these techniques employ a similarity heuristic. The ability of the proposed techniques is assessed in an empirical study through a comparison with state of the art tools. The comparison focuses on both the Product configuration generation and the prioritization aspects. The results demonstrate that existing $t$-wise tools and prioritization techniques fail to handle Large SPLs. On the contrary, the proposed techniques are both effective and scalable. Additionally, the experiments show that the similarity heuristic can be used as a viable alternative to $t$ -wise.
-
Bypassing the Combinatorial Explosion: Using Similarity to Generate and Prioritize T-wise Test Suites for Large Software Product Lines
arXiv: Software Engineering, 2012Co-Authors: Christopher Henard, Mike Papadakis, Gilles Perrouin, Jacques Klein, Patrick Heymans, Yves Le TraonAbstract:Software Product Lines (SPLs) are families of Products whose commonalities and variability can be captured by Feature Models (FMs). T-wise testing aims at finding errors triggered by all interactions amongst t features, thus reducing drastically the number of Products to test. T-wise testing approaches for SPLs are limited to small values of t -- which miss faulty interactions -- or limited by the size of the FM. Furthermore, they neither prioritize the Products to test nor provide means to finely control the generation process. This paper offers (a) a search-based approach capable of generating Products for Large SPLs, forming a scalable and flexible alternative to current techniques and (b) prioritization algorithms for any set of Products. Experiments conducted on 124 FMs (including Large FMs such as the Linux kernel) demonstrate the feasibility and the practicality of our approach.
Jurgen Munch - One of the best experts on this subject based on the ideXlab platform.
-
transitioning towards continuous experimentation in a Large Software Product and service development organisation a case study
Product Focused Software Process Improvement, 2016Co-Authors: Sezin Gizem Yaman, Fabian Fagerholm, Myriam Munezero, Jurgen Munch, Mika Aaltola, Christina Palmu, Tomi MannistoAbstract:Context: Companies need capabilities to evaluate the customer value of Software-intensive Products and services. One way of systematically acquiring data on customer value is running continuous experiments as part of the overall development process. Objective: This paper investigates the first steps of transitioning towards continuous experimentation in a Large company, including the challenges faced. Method: We conduct a single-case study using participant observation, interviews, and qualitative analysis of the collected data. Results: Results show that continuous experimentation was well received by the practitioners and practising experimentation helped them to enhance understanding of their Product value and user needs. Although the complexities of a Large multi-stakeholder business-to-business (B2B) environment presented several challenges such as inaccessible users, it was possible to address impediments and integrate an experiment in an ongoing development project. Conclusion: Developing the capability for continuous experimentation in Large organisations is a learning process which can be supported by a systematic introduction approach with the guidance of experts. We gained experience by introducing the approach on a small scale in a Large organisation, and one of the major steps for future work is to understand how this can be scaled up to the whole development organisation.
-
PROFES - Transitioning Towards Continuous Experimentation in a Large Software Product and Service Development Organisation – A Case Study
Product-Focused Software Process Improvement, 2016Co-Authors: Sezin Gizem Yaman, Fabian Fagerholm, Myriam Munezero, Jurgen Munch, Mika Aaltola, Christina Palmu, Tomi MannistoAbstract:Context: Companies need capabilities to evaluate the customer value of Software-intensive Products and services. One way of systematically acquiring data on customer value is running continuous experiments as part of the overall development process. Objective: This paper investigates the first steps of transitioning towards continuous experimentation in a Large company, including the challenges faced. Method: We conduct a single-case study using participant observation, interviews, and qualitative analysis of the collected data. Results: Results show that continuous experimentation was well received by the practitioners and practising experimentation helped them to enhance understanding of their Product value and user needs. Although the complexities of a Large multi-stakeholder business-to-business (B2B) environment presented several challenges such as inaccessible users, it was possible to address impediments and integrate an experiment in an ongoing development project. Conclusion: Developing the capability for continuous experimentation in Large organisations is a learning process which can be supported by a systematic introduction approach with the guidance of experts. We gained experience by introducing the approach on a small scale in a Large organisation, and one of the major steps for future work is to understand how this can be scaled up to the whole development organisation.
Sezin Gizem Yaman - One of the best experts on this subject based on the ideXlab platform.
-
transitioning towards continuous experimentation in a Large Software Product and service development organisation a case study
Product Focused Software Process Improvement, 2016Co-Authors: Sezin Gizem Yaman, Fabian Fagerholm, Myriam Munezero, Jurgen Munch, Mika Aaltola, Christina Palmu, Tomi MannistoAbstract:Context: Companies need capabilities to evaluate the customer value of Software-intensive Products and services. One way of systematically acquiring data on customer value is running continuous experiments as part of the overall development process. Objective: This paper investigates the first steps of transitioning towards continuous experimentation in a Large company, including the challenges faced. Method: We conduct a single-case study using participant observation, interviews, and qualitative analysis of the collected data. Results: Results show that continuous experimentation was well received by the practitioners and practising experimentation helped them to enhance understanding of their Product value and user needs. Although the complexities of a Large multi-stakeholder business-to-business (B2B) environment presented several challenges such as inaccessible users, it was possible to address impediments and integrate an experiment in an ongoing development project. Conclusion: Developing the capability for continuous experimentation in Large organisations is a learning process which can be supported by a systematic introduction approach with the guidance of experts. We gained experience by introducing the approach on a small scale in a Large organisation, and one of the major steps for future work is to understand how this can be scaled up to the whole development organisation.
-
PROFES - Transitioning Towards Continuous Experimentation in a Large Software Product and Service Development Organisation – A Case Study
Product-Focused Software Process Improvement, 2016Co-Authors: Sezin Gizem Yaman, Fabian Fagerholm, Myriam Munezero, Jurgen Munch, Mika Aaltola, Christina Palmu, Tomi MannistoAbstract:Context: Companies need capabilities to evaluate the customer value of Software-intensive Products and services. One way of systematically acquiring data on customer value is running continuous experiments as part of the overall development process. Objective: This paper investigates the first steps of transitioning towards continuous experimentation in a Large company, including the challenges faced. Method: We conduct a single-case study using participant observation, interviews, and qualitative analysis of the collected data. Results: Results show that continuous experimentation was well received by the practitioners and practising experimentation helped them to enhance understanding of their Product value and user needs. Although the complexities of a Large multi-stakeholder business-to-business (B2B) environment presented several challenges such as inaccessible users, it was possible to address impediments and integrate an experiment in an ongoing development project. Conclusion: Developing the capability for continuous experimentation in Large organisations is a learning process which can be supported by a systematic introduction approach with the guidance of experts. We gained experience by introducing the approach on a small scale in a Large organisation, and one of the major steps for future work is to understand how this can be scaled up to the whole development organisation.
