Diagnosing and correcting design inconsistencies in source code with logical abduction

  • Authors:

  • Sergio Castro;Coen De Roover;Andy Kellens;Angela Lozano;Kim Mens;Theo DHondt

  • Affiliations:

  • Université catholique de Louvain, Place Sainte Barbe 2, 1348 Louvain-la-Neuve, Belgium;Vrije Universiteit Brussel, Pleinlaan 2, 1050 Brussels, Belgium;Vrije Universiteit Brussel, Pleinlaan 2, 1050 Brussels, Belgium;Université catholique de Louvain, Place Sainte Barbe 2, 1348 Louvain-la-Neuve, Belgium;Université catholique de Louvain, Place Sainte Barbe 2, 1348 Louvain-la-Neuve, Belgium;Vrije Universiteit Brussel, Pleinlaan 2, 1050 Brussels, Belgium

  • Venue:
  • Science of Computer Programming
  • Year:
  • 2011

Quantified Score

Hi-index 0.00

Visualization

Abstract

Correcting design decay in source code is not a trivial task. Diagnosing and subsequently correcting inconsistencies between a software system's code and its design rules (e.g., database queries are only allowed in the persistence layer) and coding conventions can be complex, time-consuming and error-prone. Providing support for this process is therefore highly desirable, but of a far greater complexity than suggesting basic corrective actions for simplistic implementation problems (like the ''declare a local variable for non-declared variable'' suggested by Eclipse). We present an abductive reasoning approach to inconsistency correction that consists of (1) a means for developers to document and verify a system's design and coding rules, (2) an abductive logic reasoner that hypothesizes possible causes of inconsistencies between the system's code and the documented rules and (3) a library of corrective actions for each hypothesized cause. This work builds on our previous work, where we expressed design rules as equality relationships between sets of source code artifacts (e.g., the set of methods in the persistence layer is the same as the set of methods that query the database). In this paper, we generalize our approach to design rules expressed as user-defined binary relationships between two sets of source code artifacts (e.g., every state changing method should invoke a persistence method). We illustrate our approach on the design of IntensiVE, a tool suite that enables defining sets of source code artifacts intensionally (by means of logic queries) and verifying relationships between such sets.