A Software Fault Tree Metric

Needham, Donald M.; Jones, Sara

doi:10.1109/icsm.2006.8

Cited by 10 publications

(3 citation statements)

References 14 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Year A B C 1 Condron [16] A domain approach to test automation of product lines 2004 2 0 2 2 Feng et al [22] A product line based aspect-oriented generative unit testing approach to building quality components 2007 1.5 0 2.5 3 Nebut et al [60] A requirement-based approach to test product families 2003 2.5 1 1.5 4 Reis and Metzger [72] A reuse technique for performance testing of software product lines 2006 1.5 2 3 5 Kolb [45] A risk-driven approach for efficiently testing software product lines 2003 2 1 2.5 6 Needham and Jones [62] A software fault tree metric 2006 0 0 1 7…”

Section: Appendix a Quality Studies Scoresmentioning

confidence: 99%

A systematic mapping study of software product lines testing

Neto

Machado

McGregor

et al. 2011

Information and Software Technology

196

View full text Add to dashboard Cite

a b s t r a c tContext: In software development, Testing is an important mechanism both to identify defects and assure that completed products work as specified. This is a common practice in single-system development, and continues to hold in Software Product Lines (SPL). Even though extensive research has been done in the SPL Testing field, it is necessary to assess the current state of research and practice, in order to provide practitioners with evidence that enable fostering its further development.Objective: This paper focuses on Testing in SPL and has the following goals: investigate state-of-the-art testing practices, synthesize available evidence, and identify gaps between required techniques and existing approaches, available in the literature. Method: A systematic mapping study was conducted with a set of nine research questions, in which 120 studies, dated from 1993 to 2009, were evaluated. Results: Although several aspects regarding testing have been covered by single-system development approaches, many cannot be directly applied in the SPL context due to specific issues. In addition, particular aspects regarding SPL are not covered by the existing SPL approaches, and when the aspects are covered, the literature just gives brief overviews. This scenario indicates that additional investigation, empirical and practical, should be performed. Conclusion:The results can help to understand the needs in SPL Testing, by identifying points that still require additional investigation, since important aspects regarding particular points of software product lines have not been addressed yet.

show abstract

Section: Appendix a Quality Studies Scoresmentioning

confidence: 99%

A systematic mapping study of software product lines testing

Neto

Machado

McGregor

et al. 2011

Information and Software Technology

196

View full text Add to dashboard Cite

show abstract

“…Needham and Jones [40] propose a measure with which to compare the safety represented by the structure and composition of software fault trees with the same root hazard. Unfortunately, we did not find any measure for compatibility and transferability.…”

Section: Criterion 1 Quality Characteristic Evaluated By the Measurementioning

confidence: 99%

“…Depending on the specification used, some measures can be used and others cannot. For example, the Software Fault Tree measure [40] uses a representation with logic gates, the measures proposed by [50] or [2] use the source code, and the measures proposed by [61] to specify the product line architecture with using vADL language (a product line architecture description language) that was designed for this purpose. Each measure is thus defined for a particular specification of the artifact and it is not possible to use all of measures definitions in different artifacts.…”

Section: Strengths and Weaknessesmentioning

confidence: 99%

A systematic review of quality attributes and measures for software product lines

2011

View full text Add to dashboard Cite

It is widely accepted that software measures provide an appropriate mechanism for understanding, monitoring, controlling and predicting the quality of software development projects. In Software Product Lines (SPL), quality is even more important than in a single software product since, owing to systematic reuse, a fault or an inadequate design decision could be propagated to several products in the family. Over the last few years, a great number of quality attributes and measures for assessing the quality of SPL have been reported in literature. However, no studies summarizing the current knowledge about them exist. This paper presents a systematic literature review with the objective of identifying and interpreting all the available studies from 1996 to date that present quality attributes and/or measures for SPL. These attributes and measures have been classified using a set of criteria that includes the life cycle phase in which the measures are applied; the corresponding quality characteristics; their support for specific SPL characteristics (e.g., variability, compositionality); the procedure used to validate the measures, etc. We found 165 measures related to 98 different quality attributes. The results of the review indicated that 92% of the measures evaluate attributes that are related to maintainability. In addition, 67% of the measures are used during the design phase of Domain Engineering, and 56% are applied to evaluate the product line architecture. However, only 25% of them have been empirically validated.In conclusion, the results provide a global vision of the state of the research within this area in order to help researchers in detecting weaknesses, directing research efforts, and identifying new research lines. In particular, there is a need for new measures with which to evaluate both the quality of the artifacts produced during the entire SPL life cycle and other quality characteristics. There is also a need for more validation (both theoretical and empirical) of existing measures. In addition, our results may be useful as a reference guide for practitioners to assist them in the selection or the adaptation of existing measures for evaluating their software product lines.

show abstract

Internet Fault Tree Analysis for Reliability Estimation

2011

Systems and Software Engineering With Applications

View full text Add to dashboard Cite

A Software Fault Tree Metric

Cited by 10 publications

References 14 publications

A systematic mapping study of software product lines testing

A systematic mapping study of software product lines testing

A systematic review of quality attributes and measures for software product lines

Internet Fault Tree Analysis for Reliability Estimation

Contact Info

Product

Resources

About