Translating Clojure to ACL2 for Verification
| dc.contributor.advisor | Page, Rex | |
| dc.contributor.advisor | Hougen, Dean | |
| dc.contributor.author | Ralston, Ryan | |
| dc.contributor.committeeMember | Miller, David | |
| dc.contributor.committeeMember | Jensen, Matthew | |
| dc.contributor.committeeMember | Weaver, Christopher | |
| dc.date.accessioned | 2016-06-22T17:01:35Z | |
| dc.date.available | 2016-06-22T17:01:35Z | |
| dc.date.issued | 2016 | |
| dc.date.manuscript | 2016 | |
| dc.description.abstract | Software spends a significant portion of its life-cycle in the maintenance phase and over 20\% of the maintenance effort is fixing defects. Formal methods, including verification, can reduce the number of defects in software and lower corrective maintenance, but their industrial adoption has been underwhelming. A significant barrier to adoption is the overhead of converting imperative programming languages, which are common in industry, into the declarative programming languages that are used by formal methods tools. In comparison, the verification of software written in declarative programming languages is much easier because the conversion into a formal methods tool is easier. The growing popularity of declarative programming --- evident from the rise of multi-paradigm languages such as Javascript, Ruby, and Scala --- affords us the opportunity to verify the correctness of software more easily. Clojure is a declarative language released in 2007 that compiles to bytecode that executes on the Java Virtual Machine (JVM). Despite being a newer, declarative programming language, several companies have already used it to develop commercial products. Clojure shares a Lisp syntax with ACL2, an interactive theorem prover that is used to verify the correctness of software. Since both languages are based on Lisp, code written in either Clojure or ACL2 is easily converted to the other. Therefore, Clojure can conceivably be verified by ACL2 with limited overhead assuming that the underlying behavior of Clojure code matches that of ACL2. ACL2 has been previously used to reason about Java programs through the use of formal models of the JVM. Since Clojure compiles to JVM bytecode, a similar approach is taken in this dissertation to verify the underlying implementation of Clojure. The research presented in this dissertation advances techniques to verify Clojure code in ACL2. Clojure and ACL2 are declarative, but they are specifically functional programming languages so the research focuses on two important concepts in functional programming and verification: arbitrary-precision numbers ("bignums") and lists. For bignums, the correctness of a model of addition is verified that addresses issues that arise from the unique representation of bignums in Clojure. Lists, in Clojure, are implemented as a type of sequence. This dissertation demonstrates an abstraction that equates Clojure sequences to ACL2 lists. In support of the research, an existing ACL2 model of the JVM is modified to address specific aspects of compiled Clojure code and the new model is used to verify the correctness of core Clojure functions with respect to corresponding ACL2 functions. The results support the ideas that ACL2 can be used to reason about Clojure code and that formal methods can be integrated more easily in industrial software development when the implementation corresponds semantically to the verification model. | en_US |
| dc.identifier.uri | http://hdl.handle.net/11244/42982 | |
| dc.language | en_US | en_US |
| dc.subject | Software Verification | en_US |
| dc.subject | Formal Methods | en_US |
| dc.subject | Theorem Proving | en_US |
| dc.thesis.degree | Ph.D. | en_US |
| dc.title | Translating Clojure to ACL2 for Verification | en_US |
| ou.group | College of Engineering::School of Computer Science | en_US |
| shareok.nativefileaccess | restricted | en_US |