Evidence-Based Guidelines to Defect Causal Analysis

Kalinowski, Marcos; Card, David N.; Travassos, Guilherme Horta

doi:10.1109/ms.2012.72

Cited by 40 publications

(40 citation statements)

References 10 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…The diagram extends the traditional cause-effect diagram [18] by (a) showing the probabilities for each possible cause to lead to the analyzed problem, and (b) representing the causes using grey tones, where causes with higher probability are shown closer to the center and in darker tones. Following the suggestion of guidelines for conducting causal analysis [8], it organizes the causes of problems into five categories: Input, Method, Organization, People, and Tool. The probabilities shown in Figure 1 were calculated with data on causes gathered in successive causal analysis sessions conducted in earlier iterations of the project.…”

Section: B Probabilistic Cause-effect Diagramsmentioning

confidence: 99%

“…Thereafter, to build the probabilistic cause-effect diagrams for each RE problem, we categorized the causes as suggested in [8] and generated probabilities based on frequency counting. Figure 2 shows the probabilistic cause-effect diagram for the problem 'Incomplete and/or hidden requirements' (#2 in Table VI).…”

Section: Causes Of Critical Re Problemsmentioning

confidence: 99%

“…Conducting causal analysis sessions [8] is an efficient means for organizations to improve their practice to overcome problems faced during software development. In these sessions, the causes of problems are identified and addressed to prevent their recurrence in future projects.…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Towards Building Knowledge on Causes of Critical Requirements Engineering Problems

Kalinowski¹,

Spínola²,

Conte³

et al. 2015

International Conferences on Software Engineering and Knowledge Engineering

Self Cite

View full text Add to dashboard Cite

Abstract-[Context] Many software projects fail due to problems in requirements engineering (RE).[Objective] The goal of this paper is to gather information on relevant RE problems and to represent knowledge on their most common causes.[Method] We replicated a global family of RE surveys in Brazil and used the data to identify critical RE problems and to build probabilistic causeeffect diagrams to represent knowledge on their common causes.[Results] The survey was answered by 74 different organizations, including small, medium and very large sized companies, conducting both, plan-driven and agile development. The most critical RE problems, according to those organizations, are related to communication and to incomplete or underspecified requirements. We provide the full probabilistic cause-effect diagrams with knowledge on common causes of the most critical identified RE problems online.[Conclusion] We believe that the knowledge presented in the diagrams can be helpful to support organizations in conducting causal analysis sessions by providing an initial understanding on what usually causes critical RE problems.

show abstract

Section: B Probabilistic Cause-effect Diagramsmentioning

confidence: 99%

Section: Causes Of Critical Re Problemsmentioning

confidence: 99%

See 1 more Smart Citation

Towards Building Knowledge on Causes of Critical Requirements Engineering Problems

Kalinowski¹,

Spínola²,

Conte³

et al. 2015

International Conferences on Software Engineering and Knowledge Engineering

Self Cite

View full text Add to dashboard Cite

show abstract

“…No-triangle [28]. However, regardless their types [25] [48], software defects shall be identified and eliminated as soon as possible to improve software quality by reducing the probability of software failures.…”

Section: Source Codementioning

confidence: 99%

Software Defects: Stay Away from Them. Do Inspections!

Travassos

2014

2014 9th International Conference on the Quality of Information and Communications Technology

View full text Add to dashboard Cite

All software system fails. However, a development team can identify and remove as probability of software to fail. Identifying and throughout the software development proce important approach to improve software qu evidence about the feasibility, efficiency and software inspections to support the identific Besides their low cost, the performance of in positively influenced by the technique used Despite all these benefits, the use of inspectio place in the software industry. Therefore, this Q speech intends to discuss the benefits of Softwa method and techniques) and their use in software

show abstract

“…It is also possible to find opportunities for improvement, and implement actions to reduce the continuous manifestation of the same type of defect in future projects [4]. Also, causal analysis is a low-cost method [5], in fact, Kalinowski et al [6] showed that the investment can vary between 0.5 % and 1.5 % of the total cost of the project, therefore, it is feasible to recover the invested money and decrease the defects rate by more than 50 %. It should be noted that the early detection of defects is beneficial, since timely treatment reduces the delay in the execution of the project [7].…”

Section: Introductionmentioning

confidence: 99%

“Defect Root-Cause Analysis and 1+n Procedure” technique to improve software quality

Honda

Yamada

2012

Int J Syst Assur Eng Manag

View full text Add to dashboard Cite

Very Small Entities (VSE) dedicated to software development lack of enough resources to adopt causal analysis practices, defined in models as CMMI, due to their complexity and costs. It is important to detect the generated defects in the development process, and to make a systematic analysis aimed at determining its causes. However, identifying those root causes is an arduous task, and failing to do so leads to wrong decisions that either fail to solve the problem or even make it worse. On this basis, this paper proposes a causal analysis procedure focused on small organizations PAC-DS (according to its initials in Spanish), which includes activities aimed at identifying the defects causes. After its evaluation in a preliminary case study, the utility of the procedure was evidenced.Keywords: Causal Analysis; Software Engineering; Software Process Improvement; Small Software Development Organizations. ResumenLas pequeñas organizaciones desarrolladoras de software no cuentan con recursos suficientes para adoptar prácticas de análisis causal, definidas en modelos como CMMI, debido a la complejidad y el costo de estas. Es importante detectar los defectos generados en el proceso de desarrollo y hacer un análisis sistemático para determinar sus causas; pero identificar esas causas principales es una labor difícil, y no lograrlo lleva a tomar decisiones erróneas que no resuelven la problemática presentada o, incluso, la empeoran. A causa de lo anterior, este artículo propone un procedimiento de análisis causal enfocado en pequeñas organizaciones (PAC-DS) que incorpora actividades para identificar las causas de los defectos. Tras su evaluación en un caso de estudio preliminar, se evidenció la utilidad del procedimiento.Palabras clave: Análisis causal; Ingeniería de Software; Mejora de procesos software; Pequeñas organizaciones de desarrollo software.* Universidad del Cauca (Popayán-Cauca, Colombia). kyzuniga@unicauca.edu.co. ORCID: 0000-0002-5181-1327. ** M. Sc. Universidad del Cauca (Popayán-Cauca, Colombia). cardila@unicauca.edu.co. *** Ph. D. Universidad del Cauca (Popayán-Cauca, Colombia). fjpino@unicauca.edu.co. Causal analysis procedure focused on small software development organizations ResumoAs pequenas organizações desenvolvedoras de software não contam com recursos suficientes para adotar práticas de análise causal, definidas em modelos como CMMI, devido à complexidade e o custo que apresentam. É importante detectar os defeitos gerados no processo de desenvolvimento e fazer uma análise sistemática para determinar suas causas; porém identificar essas causas principais é um labor difícil, e não lográ-lo leva a tomar decisões errôneas que não resolvem a problemática apresentada ou, inclusive, pioram-na. Consequentemente, este artigo propõe um procedimento de análise causal enfocado em pequenas organizações (PAC-DS) que incorpora atividades para identificar as causas dos defeitos. Após sua avaliação em um caso de estudo preliminar, evidenciouse a utilidade do procedimento.Palavras chave: Análise causal; En...

show abstract

Evidence-Based Guidelines to Defect Causal Analysis

Cited by 40 publications

References 10 publications

Towards Building Knowledge on Causes of Critical Requirements Engineering Problems

Towards Building Knowledge on Causes of Critical Requirements Engineering Problems

Software Defects: Stay Away from Them. Do Inspections!

“Defect Root-Cause Analysis and 1+n Procedure” technique to improve software quality

Contact Info

Product

Resources

About