Finding software faults is a problematic activity in many systems. Existing approaches usually work close to the system implementation and require developers to perform different code analyses. Although these approaches are effective, the amount of information to be managed by developers is often overwhelming. This problem calls for complementary approaches able to work at higher levels of abstraction than code, helping developers to keep intellectual control over the system when analyzing faults. In this context, we present an expert-system approach, called FLABot, which assists developers in fault-localization tasks by reasoning about faults using software architecture models. We have evaluated a prototype of FLABot in two medium-size case studies, involving novice and non-novice developers. We compared time consumed, code browsed and faults found by these developers, with and without the support of FLABot, observing interesting effort reductions when applying FLABot. The results and lessons learned have shown that our approach is practical and reduces the efforts for finding individual faults.

-- DanielAmyot - 03 Apr 2014


FormForVirtualLibrary edit

Title Architecture-driven assistance for fault-localization tasks
Authors A. Soria, J.A. Diaz-Pace, and M. Campo
Type Journal
Conference/Journal Title Expert Systems
Volume/Number TBD
Publisher Wiley
Month August
Year 2013
DOI 10.1111/exsy.12047
Keywords Software architecture, Fault analysis, Tool support, Use-Case Maps, Java, FLABot
Topic revision: r1 - 03 Apr 2014, DanielAmyot
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Foswiki? Send feedback