Spectrum-based Fault Localization Techniques Application on Multiple-Fault Programs: A Review

Zakari, Abubakar; Abdullahi, Shamsu; Shagari, Nura Modi; Tambawal, Abubakar Bello; Shanono, Nuruddeen Musa; Maitama, Jaafar Zubairu; Rasheed, Rasheed Abubakar; Adamu, Abubakar; Abdulrahman, Salish Mamman

doi:10.34257/gjcstgvol20is2pg41

Cited by 11 publications

(10 citation statements)

References 54 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In an SLR, researchers have to interpret and evaluate available research related to the formulated research questions and topic [17]. The SLR was conducted to summarise the existing literature and identify gaps in current research to suggest areas for further investigation [18][19][20]. These sections highlight the SLR planning and details.…”

Section: Methodsmentioning

confidence: 99%

Software Requirements Negotiation: a Systematic Literature Review

Abdullahi

Zakari

Abaker

et al. 2022

Preprint

View full text Add to dashboard Cite

Software requirements negotiation (SRN) is one of the most essential stages of software requirements engineering. SRN involves the stakeholder's interaction to reach a mutual understanding of the requirements for developing a software project. The increased research interest in requirements engineering has resulted in huge literature in the SRN domain. There is a need to investigate the broad of techniques, processes, and evaluation mechanisms used in the SRN research community. This study aims to examine and identify the existing methods, processes, evaluation mechanisms, quantity of publications, publication trends and demographics shaping SRN research domain. To accomplish our aim, we used an evidence-based systematic approach, and 67 relevant studies were ultimately chosen from the search process based on the formulated research questions. Our study result shows broad and promising SRN techniques that include agent-based negotiation, TAICOS, wikiwinwin and winbook. However, we found that the existing SRN techniques suffer from limitations that have stakeholders' communication gaps, interface issues to non-technical users, decision-making, and managing requirements changes. Moreover, our study found that 63% of the selected studies stated their SRN processes, with 22% adopting the basic SRN processes in winwin model. Five evaluation mechanisms were discovered, with case study and experiment most adopted by the selected studies with 44% and 30%, respectively. In conclusion, although research on SRN is recently gaining some traction, the works in the domain are insufficient. Concrete proposals are needed to improve SRN in software requirements engineering research domain.

show abstract

Section: Methodsmentioning

confidence: 99%

Software Requirements Negotiation: a Systematic Literature Review

Abdullahi

Zakari

Abaker

et al. 2022

Preprint

View full text Add to dashboard Cite

show abstract

“…This study adheres to systematic guidelines given by [29]. These guidelines were also adopted by existing studies in software engineering research [30,31] as a means of identifying, evaluating and interpreting all available research data relevant to a particular research question and interest in the studies.…”

Section: Methodsmentioning

confidence: 99%

Software Requirements Negotiation: A Review on Challenges

et al. 2021

Self Cite

View full text Add to dashboard Cite

Requirements negotiation involves discussion on the requirements conflict to have some compromise that will satisfy the participating stakeholders of a software project. The output of a requirement negotiation is a set of satisfied requirements of two or more parties. In this paper, we present a systematic review of requirements negotiation challenges. The study adopted 34 papers from the final study selection process which were analyzed based on the requirements negotiation challenges they addressed. The identified challenges are decision-making, communication, performance, managing requirement changes, and conflict resolution. The output of the study indicates that decision-making is addressed by 33% of the studies reviewed, followed by the performance with 22%, conflict resolution with 19%, while 16% focus on stakeholders’ communication, and managing requirements changes has 10%.

show abstract

“…In [31], [32], the authors presented the issue of multiple fault localization (MFL) of software systems in the software fault localization domain. They identified three prominent MFL debugging approaches, i.e., one-bug-at-atime debugging approach, parallel debugging approach, and multiple-bug-at-a-time debugging approach.…”

Section: Related Workmentioning

confidence: 99%

“…A bug is a program element that shows unexpected behavior when executed by a test case. In general, program failures are caused either by a single bug or multiple bugs [31], [32]. A single-bug problem is where all the failures of test cases are caused by just one bug.…”

Section: G Single and Multiple Bugsmentioning

confidence: 99%

A Survey of Challenges in Spectrum-Based Software Fault Localization

Sarhan

Beszedes

2022

IEEE Access

View full text Add to dashboard Cite

In software debugging, fault localization is the most difficult, expensive, tedious, and timeconsuming task, particularly for large-scale software systems. This is due to the fact that it requires significant human participation and it is difficult to automate its sub-tasks. Therefore, there is a high demand for automatic fault localization techniques that can help software engineers effectively find the locations of faults with minimal human intervention. This has led to the proposal of implementing different types of such techniques. However, Spectrum Based Fault Localization (SBFL) is considered amongst the most prominent techniques in this respect due to its efficiency and effectiveness. In SBFL, the probability of each program element (e.g., statement, block, or function) being faulty is calculated based on the results of executing test cases and their corresponding code coverage information. However, SBFL techniques are not yet widely adopted in the industry. The rationale behind this is that they pose a number of issues and their performance is affected by several influential factors. For example, the characteristics of bugs, target programs, test suites, and supporting tools make their effectiveness differ dramatically from one case to another. There are massive studies on SBFL that cover its usage, formulas, performance, etc. So far, no dedicated survey points out comprehensively the issues of SBFL. In this paper, various SBFL challenges and issues have been identified, categorized, and discussed alongside many directions. Also, the paper raises awareness of the works being achieved to address the identified issues and suggests some potential solutions too.INDEX TERMS Program spectra, spectrum based fault localization, software testing, challenges and issues, survey.

show abstract

Spectrum-based Fault Localization Techniques Application on Multiple-Fault Programs: A Review

Cited by 11 publications

References 54 publications

Software Requirements Negotiation: a Systematic Literature Review

Software Requirements Negotiation: a Systematic Literature Review

Software Requirements Negotiation: A Review on Challenges

A Survey of Challenges in Spectrum-Based Software Fault Localization

Contact Info

Product

Resources

About