Decision-Model-Based Code Generation for SPLE

Weiss, David M.; Li, J.J.; Slye, H.; Dinh-Trong, T.; Sun, Hongyu

doi:10.1109/splc.2008.42

Cited by 23 publications

(22 citation statements)

References 1 publication

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…This should be expected since the templates refer to the specific syntax and rely on semantic details of these languages. Although some of the templates could be easily adapted to alternative languages and notations, including decision models (Czarnecki et al, 2012;Weiss et al, 2008), we do not explore this possibility since our focus is to understand and explain the evolution history of product lines based on the languages we consider here. The product line refinement notion, on the other hand, is independent of such languages and could be used to justify safe evolution templates specific to the alternative notations we just mentioned.…”

Section: Product Linementioning

confidence: 99%

Safe evolution templates for software product lines

Neves

Borba

Alves

et al. 2015

Journal of Systems and Software

View full text Add to dashboard Cite

Section: Product Linementioning

confidence: 99%

Safe evolution templates for software product lines

Neves

Borba

Alves

et al. 2015

Journal of Systems and Software

View full text Add to dashboard Cite

“…PolyFlow, formerly known as eXVantage, is a suite of software testing tools developed by Avaya Corporation that allows developers to generate and execute test cases and calculate associated coverage metrics [23], in addition to other tasks. Variabilities across the product line include support for various operating systems, target programming languages, and user interfaces.…”

Section: Case Study Descriptionmentioning

confidence: 99%

“…Specifically, we examine pre-release software faults and changes made in the code of four members of the PolyFlow product line family of software testing tools developed by Avaya [23]. To evaluate this SPL, we extracted data from the source code repository and the modification request tracking system.…”

Section: Introductionmentioning

confidence: 99%

An Empirical Study of Pre-release Software Faults in an Industrial Product Line

Devine

Goseva-Popstajanova

Krishnan

et al. 2012

2012 IEEE Fifth International Conference on Software Testing, Verification and Validation

Self Cite

View full text Add to dashboard Cite

Abstract-There is a lack of published studies providing empirical support for the assumption at the heart of product line development, namely, that through structured reuse later products will be less fault-prone. This paper presents results from an empirical study of pre-release fault and change proneness from four products in an industrial software product line. The objectives of the study are (1) to determine the association between various software metrics, as well as their correlation with the number of faults at the component level; (2) to characterize the fault and change proneness at various degrees of reuse; and (3) to determine how existing products in the software product line affect the quality of subsequently developed products and our ability to make predictions. The research results confirm, in a software product line setting, the findings of others that faults are more highly correlated to change metrics than to static code metrics. Further, the results show that variation components unique to individual products have the highest fault density and are the most prone to change. The longitudinal aspect of our research indicates that new products in this software product line benefit from the development and testing of previous products. For this case study, the number of faults in variation components of new products is predicted accurately using a linear model built on data from the previous products.

show abstract

“…PolyFlow was implemented as a product line [10]. Its early products include code coverage testing tool, structure recovery tool, static analysis tool, etc.…”

Section: Concluding Observationsmentioning

confidence: 99%

SoftWare IMmunization (SWIM) - A Combination of Static Analysis and Automatic Testing

Palframan

Landwehr

2011

2011 IEEE 35th Annual Computer Software and Applications Conference

Self Cite

View full text Add to dashboard Cite

Static program analysis uses many checkers to discover a very large number of programming issues, but with a high false alarm rate. With the aid of dynamic automatic testing, the actual severe defects can be confirmed by failures of test cases. After defects are fixed, similar types of defects tend to reoccur again. In this paper, we propose a SoftWare IMmunization (SWIM) method to combine static analysis and automatic testing results for detecting severe defects and preventing similar defects from reoccurring, i.e. to have the software immunized from the same type of defects. Three industrial trials of the technology demonstrated the feasibility and defect detection accuracy of the SWIM technology.

show abstract

Decision-Model-Based Code Generation for SPLE

Cited by 23 publications

References 1 publication

Safe evolution templates for software product lines

Safe evolution templates for software product lines

An Empirical Study of Pre-release Software Faults in an Industrial Product Line

SoftWare IMmunization (SWIM) - A Combination of Static Analysis and Automatic Testing

Contact Info

Product

Resources

About