Thiago Henrique Burgos de Oliveira
Elisa Yumi Nakagawa
ABSTRACT
The term bug prevalence is derived from the medical world vocabulary and applied to Software Product Line (SPL), meaning all products that are affected by one particular bug. In single systems development, this concept is not relevant since a bug is either present or not. However, when it comes to SPL, analyzing the bug prevalence of a certain bug is still a challenge and a highly relevant topic, since the same bug may be present in several products. To support this analysis, the main contribution of this paper is the Product Genealogy approach. A core concept in our approach is the Product Genealogy Tree, in which the hierarchy of products in the SPL is represented, reflecting how each product evolved or was derived from another or from the core assets. In this context, the benefit of such a tree is the rapid visualization of the product's structure in the SPL, providing input on which products are to be examined initially. Besides that, in this paper we introduce a novel analogy between the medical genetics world and SPL in order to better explain the principles of our approach.
- J. Díaz, J. Pérez, J. Garbajosa, and A. L. Wolf. Change impact analysis in product-line architectures. In ECSA - European Cnference on Software Architecture, pages 114--129, Essen, Germany, 2011. Google Scholar
Digital Library
- O. Document and Associated. O. M. G. unified modeling language, infrastructure. Object Management Group ed Object Management Group, 21(May), 2010.Google Scholar
- S. Duszynski, J. Knodel, and M. Becker. Analyzing the source code of multiple software variants for reuse potential. In WCRE - Working Conference on Reverse Engineering, pages 303--307, Limerick, Ireland, 2011. Google ScholarDigital Library
- S. Duszynski, J. Knodel, and M. Lindvall. SAVE: Software architecture visualization and evaluation. In CSMR - Software Maintenance and Reengineering, pages 323--324, Kaiserslautern, Germany, 2009. Google ScholarDigital Library
- C. W. Krueger. Variation management for software production lines. In SPLC - International Software Product Line Conference, pages 37--48, San Diego, CA, USA, 2002. Google ScholarDigital Library
- B. Michalik and D. Weyns. Towards a solution for change impact analysis of software product line products. In WICSA - Working IEEE/IFIP Conference on Software Architecture, pages 290--293, Boulder, Colorado, USA, 2011. Google ScholarDigital Library
Index Terms
- Supporting the analysis of bug prevalence in software product lines with product genealogy
Recommendations
A New Parameter for Product Configuration in Software Product Lines
KAM '09: Proceedings of the 2009 Second International Symposium on Knowledge Acquisition and Modeling - Volume 02Software product line development is a new software engineering method. It promotes the predictive software reuse by developing similar software systems together. One of the key artifacts of a software product line is the feature model, which represents ...
Supporting Online Updates of Software Product Lines: A Controlled Experiment
ESEM '11: Proceedings of the 2011 International Symposium on Empirical Software Engineering and MeasurementThe evolution of Software Product Lines (SPL) is challenging because stakeholders have to deal with both regular evolution and the co-existence of different products. Our focus of product evolution is on the tasks integrators have to perform to update ...
Evaluating Bug-Fixing in Software Product Lines: an Industrial Case Study
ESEM '16: Proceedings of the 10th ACM/IEEE International Symposium on Empirical Software Engineering and Measurement[Background] Bug-fixing could be complex in industrial practice since thousands of products share features in their configuration. Despite the importance and complexity of bug-fixing, there is still a lack of empirical data about the difficulties found ...
Comments