Debugging formal specifications: a practical approach using model-based diagnosis and counterstrategies

• Published in: International journal on software tools for technology transfer Vol. 15; no. 5-6; pp. 563 - 583
• Main Authors: Könighofer, Robert, Hofferek, Georg, Bloem, Roderick
• Format: Journal Article
• Language: English
• Published: Berlin/Heidelberg Springer Berlin Heidelberg 01.10.2013; Springer Nature B.V
• Subjects: Algorithms; Computer programs; Computer Science; Debugging; Diagnosis; Errors; Formal specification; Games; Information processing; Interactive; Software Engineering; Software Engineering/Programming and Operating Systems; Specifications; Synthesis; Theory of Computation; Counterstrategies; Formal specification; Unrealizability; Model-based diagnosis; Debugging
• ISSN: 1433-2779; 1433-2787
• DOI: 10.1007/s10009-011-0221-y

Creating a formal specification for a design is an error-prone process. At the same time, debugging incorrect specifications is difficult and time consuming. In this work, we propose a debugging method for formal specifications that does not require an implementation. We handle conflicts between a formal specification and the informal design intent using a simulation-based refinement loop, where we reduce the problem of debugging overconstrained specifications to that of debugging unrealizability. We show how model-based diagnosis can be applied to locate an error in an unrealizable specification. The diagnosis algorithm computes properties and signals that can be modified in such a way that the specification becomes realizable, thus pointing out potential error locations. In order to fix the specification, the user must understand the problem. We use counterstrategies to explain conflicts in the specification. Since counterstrategies may be large, we propose several ways to simplify them. First, we compute the counterstrategy not for the original specification but only for an unrealizable core. Second, we use a heuristic to search for a countertrace, i.e., a single input trace which necessarily leads to a specification violation. Finally, we present the countertrace or the counterstrategy as an interactive game against the user, and as a graph summarizing possible plays of this game. We introduce a user-friendly implementation of our debugging method and present experimental results for GR(1) specifications.