Language-agnostic specification and verification: invited talk

Over the last few years we have been working on bringing simple and pragmatic program specification and verification to programming languages targeting the Microsoft .NET platform. In this talk I will discuss the motivation and trade-offs influencing our design. The specifications and static verification are targeted at the general developer, not the verification enthusiast. It is thus important to us to use a single form of specifications that meets three simultaneous goals: 1. Specifications serve as documentation. They must be as readable as possible. 2. Specifications should be executable. This motivates writing specifications for testing and immediate perceived benefit, without consideration of static verification. 3. Finally, specifications should be usable in static verification. Our specification approach is language-agnostic in that we use idiomatic code written in the developer's source language to express pre-conditions and post-conditions. Preconditions and postconditions are expressed as calls to the static methods. Special dummy methods are used to refer to the method result value as well as referring to the old value of an expression, meaning the value of the expression on method entry.