Proceedings of the 8th Working Conference on Mining Software Repositories 2011
DOI: 10.1145/1985441.1985458
|View full text |Cite
|
Sign up to set email alerts
|

Empirical evaluation of reliability improvement in an evolving software product line

Abstract: Reliability is important to software product-line developers since many product lines require reliable operation. It is typically assumed that as a software product line matures, its reliability improves. Since post-deployment failures impact reliability, we study this claim on an open-source software product line, Eclipse. We investigate the failure trend of common components (reused across all products), highreuse variation components (reused in five or six products) and low-reuse variation components (reuse… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

3
21
0

Year Published

2011
2011
2019
2019

Publication Types

Select...
3
3

Relationship

3
3

Authors

Journals

citations
Cited by 11 publications
(24 citation statements)
references
References 22 publications
3
21
0
Order By: Relevance
“…In previous work [16], we studied the failure and change trends at the component level for the commonalities and variations in the Eclipse product line. We found that as the product line evolves, fewer serious failures occur in components implementing commonalities than in components implementing variations, and that the common components also exhibit less change than the variable components over time.…”
Section: Eclipse Product Linementioning
confidence: 99%
See 1 more Smart Citation
“…In previous work [16], we studied the failure and change trends at the component level for the commonalities and variations in the Eclipse product line. We found that as the product line evolves, fewer serious failures occur in components implementing commonalities than in components implementing variations, and that the common components also exhibit less change than the variable components over time.…”
Section: Eclipse Product Linementioning
confidence: 99%
“…This is similar to the evolution and maintenance of a single system, except that it may happen to each system in the product line. In previous work we have shown that even files implementing commonalities experience change on an on-going basis [16].…”
Section: Introductionmentioning
confidence: 99%
“…Results show that variation components used only in individual products have the highest fault density, and are the most change prone. As in [10], common components reused in all four products had similar fault densities to the high-reuse variation components, but higher average code churn.…”
Section: Introductionmentioning
confidence: 64%
“…The only other work on this topic seems to be our previous study [10], which was based on analysis of post-release failures of an opensource SPL. Unlike [10], in this paper we study pre-release faults and change proneness of an industrial SPL. Results show that variation components used only in individual products have the highest fault density, and are the most change prone.…”
Section: Introductionmentioning
confidence: 99%
“…Extensive experiments have been conducted in [152] and the results present that evolution of libre software is not SOC. Krishnan et al analyzed the failure trend and the change trend of common/variable components in software product line, and investigated the relationship between fail-ure and change [158]. Eclipse system, regarded as the evolving product line, was selected for experiment.…”
Section: To Empirically Validate Novel Ideas and Techniquesmentioning
confidence: 99%