DMCA
Verifying Executable Object-Oriented Specifications with Separation Logic
Cached
Download Links
| Citations: | 5 - 0 self |
BibTeX
@MISC{Staden_verifyingexecutable,
author = {Stephan Van Staden and Cristiano Calcagno},
title = {Verifying Executable Object-Oriented Specifications with Separation Logic},
year = {}
}
Share
 |
 |
 |
 |
||
OpenURL
Abstract
Abstract. Specifications of Object-Oriented programs conventionally employ Boolean expressions of the programming language for assertions. Programming errors can be discovered by checking at runtime whether an assertion, such as a precondition or class invariant, holds. In this work, we show how separation logic can be used to verify that these executable specifications will always hold at runtime. Both the program and its executable assertions are verified with respect to separation logic specifications. A novel notion called relative purity embraces historically problematic side-effects in executable specifications, and verification boils down to proving connecting implications. Even model-based specifications can be verified. The framework is also well-suited to separation logic proof tools and now implemented in jStar. Numerous automatically verified examples illustrate the framework’s use and utility.
Keyphrases
separation logic executable object-oriented specification executable specification model-based specification class invariant executable assertion verification boil object-oriented program boolean expression novel notion framework use problematic side-effects relative purity logic proof tool separation logic specification programming language
