A case study in root cause defect analysis

Leszak, Marek; Perry, Dewayne E.; Stoll, Dieter

doi:10.1145/337180.337232

Cited by 115 publications

(33 citation statements)

References 9 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…The defect causal analysis approach is originally a team‐based quality improvement technique used to analyze samples of previous defects, to suggest software process changes and to prevent future defects. The existing literature relevant to software defects causes analysis tended to focus on the taxonomy of causes or the implementation process as a KPA of CMM Level 5 , rather than empirical analysis.…”

Section: Related Workmentioning

confidence: 99%

The impact of software process consistency on residual defects

Huang

Liu

Wang

et al. 2015

J Software Evolu Process

View full text Add to dashboard Cite

Residual defects at the time of delivery are an important concern for safety critical software systems. Suppliers and customers are urged to get evidence for what they can do to reduce residual defects. Thus, it is meaningful to learn from historical data concerning the kinds of defects that have escaped from the existing quality assurance approaches and the factors that lead to the residual defects. A total of 3747 defects from 70 software systems developed by 29 Chinese aviation organizations were collected from acceptance tests during the last 5 years. For all these organizations, 38 domain experts from the industry assessed the process consistency to the standard built in the framework of Capability Maturity Model (CMM). Results demonstrate that the process improvement in the range of high consistency is effective in reducing total defects, as well as the minor and severe defects. The high consistency adoption of the practices in CMM Level 1 to Level 3 is more effective in reducing minor defects than severe defects. Causal analysis was performed to investigate the underlying mechanisms. Results reveal that individual cognitive failures cause 87% of severe defects. More approaches to help software developers manage their interior cognitive process are needed for improving software quality in the future. Figure 6. The effect of process consistency on the density of total defects. 638 FUQUN HUANG ET AL.

show abstract

Section: Related Workmentioning

confidence: 99%

The impact of software process consistency on residual defects

Huang

Liu

Wang

et al. 2015

J Software Evolu Process

View full text Add to dashboard Cite

show abstract

“…[39]. The idea of combining the field of (combinatorial) testing with (root) cause analysis is not new, e.g.…”

Section: Test Evaluationmentioning

confidence: 99%

Automating Test Case Design within the Classification Tree Editor

Zeppetzauer¹,

Kruse

2014

Annals of Computer Science and Information Systems

View full text Add to dashboard Cite

Abstract-This paper describes how the proven test design technique of the classification tree method is extended within the classification tree editor in order to contribute to current test design matters. The classification tree editor not only provides the tooling to use the method but also to apply new and helpful features in the test design process. This includes the automatic generation of test cases and test sequences according to desired test depth and focus, automated boundary value analysis, various tool couplings to integrate in each individual test process and supporting features like test evaluation or test coverage analysis amongst others.

show abstract

“…The mistakes were related to human factors -individual errors and lack of domain knowledge about a specific industry and system [1].…”

Section: Introductionmentioning

confidence: 99%

“…Almost all of the studies under review [1], [8], [9] indicated that the revealed defects were related to testing problems. Other reasons were related with change management, lack of knowledge, requirements faults, data processing problems, and defects in code logic.…”

Section: Introductionmentioning

confidence: 99%

A Case Study: Software Defect Root Causes

Bergmane

Grabis

Žeiris³

2017

Information Technology and Management Science

View full text Add to dashboard Cite

-Software quality assurance to comply with user requirements enables software development companies to be competitive. Maintaining a high quality level requires continuous monitoring and development. If there are quality problems, the company's reputation is suffering and its costs increase because of investing in time and eliminating the consequences of the problems. The aim of the present article is to identify the most essential root causes of software defect. The e-service "Invoice Submission" of Riga City Municipality is used as an example. The results of the study can provide useful information for developing improvement activities for e-service higher quality. The analysis is based on the information that is available in the developer's user request database. The Ishikawa method is used to analyse the causes of defects.

show abstract

A case study in root cause defect analysis

Cited by 115 publications

References 9 publications

The impact of software process consistency on residual defects

The impact of software process consistency on residual defects

Automating Test Case Design within the Classification Tree Editor

A Case Study: Software Defect Root Causes

Contact Info

Product

Resources

About